Error during deployment war: Incompatible argument to function

After we changed the JDK of the OC4J container from 1.5 to 1.6 we had problems deploying applications.

BUILD FAILED
build.xml:115: Deploy error: Operation failed with error:
(class: xx/xx/xxx , method: YyyyyY signature: (Ljava/util/Map;)RRR/rrr/RRR;) Incompatible argument to function

Did this post help you in any way can you please leave a comment? This will motivate me writing more posts.

Apache Address already in use: make_sock: could not bind to port xxxx

Error in the Apache error.log

Apache Address already in use: make_sock: could not bind to port xxxx


Find the process which is using the port:
netstat -tulpn| grep :xxxxx

Kill the process:

kill -9 httpd

Did this post help you in any way can you please leave a comment? This will motivate me writing more posts.

ESB Console: no systems. Error in log.xml: WSDL parsing failed : WSDL Parsing Failed: Connection timed out

In the metalink note: 467440.1 a possible solution is provided but in our case this was not working. We had a big application which was using Oracle BPEL en Oracle ESB. In the new release the Oracle ESB was replaced by another ESB (mule) but the old ESB systems were still deployed in the Oracle ESB. The ESB Console was not able to retrieve the ESB systems anymore, so everything was empty in the screen. The only error in log.xml in $ORACLE_HOME/j2ee/oc4j_soa/log/oc4j/.../log.xml was

WSDL parsing failed :WSDL Parsing Failed: Connection timed out

We did an undeploy of the esb system with ant and this solved the problem.

This is how we did the undeployment:

build.xml:

<?xml version="1.0" encoding="windows-1252" ?>
<project name="deploy" default="undeploy-esb">

  <property file="build.properties"/>

  <import file="../etc/ESBMetadataMigrationTaskdefs.xml"/>
  <target name="undeploy-esb">

      <undeployESBEntities
            esbMetadataServerHostname="[HOSTNAME]"
            esbMetadataServerPort="[PORT]"
            userName="oc4jadmin"
            password="[PASSWORD]">
         <system guid="[ESBSYSTEM GUID]"/>
      </undeployESBEntities>

  </target>

</project>

[ESBSYSTEM GUID] can be found in de dehydration store of the SOA suite:

select name, guid from oraesb.wf_systems;

You need some extra files to make ant work, these files can be found in $ORACLE_HOME/integration/esb/deployment there is an zip file: documentation.zip. In this zip file the files you need are there.

Did this post help you in any way can you please leave a comment? This will motivate me writing more posts.

Oracle Application Server 10.1.2.3: oidldapd process, high load on server

On the production environment of the customer there was a problem that the servers sometimes did not respond on anything anymore. The oidldapd process was consuming 100% CPU and the load on the servers was very high (100+). The only thing we could do was an hard reboot of the server.

We solved this issue bij tuning the OID. We replaced the default index by a bitmap index:

To recreate the ei_attrstore index perform the following steps: 

a.  Use sqlplus to connect to the OID database as user "ods" or connect as system and set the schema to ods, e.g. 

$ sqlplus system/ 
SQL> alter session set current_schema=ods; 

b.  Drop the existing ei_attrstore index: 

SQL> drop index ei_attrstore; 

c.  Recreate the ei_attrstore index: 

SQL> create bitmap index ei_attrstore on ds_attrstore(entryid, attrname) tablespace olts_attrstore nologging compute statistics; 

SQL> alter index ei_attrstore noparallel;

And we changed the configset0

$ORACLE_HOME/bin/ldapmodify -h [SERVERNAME] -p [PORT] -D cn=orcladmin -w [PASSWORD] -v <<EOF
dn: cn=configset0,cn=osdldapd,cn=subconfigsubentry
changetype: modify
replace: orclmaxcc
orclmaxcc: 10
-
replace: orclserverproces
orclserverprocs: 2
EOF

After these changes the oidldapd did not have the strange behavior anymore.

Did this post help you in any way can you please leave a comment? This will motivate me writing more posts.

Oracle Application Server 10.1.3 / JDBC connections based on tnsnames.ora

The customer wants to use DataGuard as backend for the applications that are hosted on the Oracle Application Server 10.1.3. To implement this solution it is necessary to configure the JDBC connections with the tnsnames.ora, because with this solution it is possible to put more databases (on different servers) in one JDBC connection.

Oracle has an java program to check if this connection is working:

// -- begin : cut here : ThinTnsnames.java -- cut there
import java.sql.*;
import oracle.jdbc.pool.*;

public class ThinTnsnames {
  // private static OracleConnection connection = null;
  static String sql = null;

  public static void main(String[] args) {
    String entry_name = args [0];
    String userId = args [1];
    String password = args [2];
    test (entry_name, userId, password);
  }

  public static void test (String entry_name, String userId, String password) {
    Connection pconnection = null;
    try {
      String l_url = "jdbc:oracle:thin:@" + entry_name;
      System.out.println( " Connection string = " + l_url );

      OracleDataSource ods = new OracleDataSource();
      ods.setUser(userId);
      ods.setPassword(password);
      ods.setURL(l_url);
      pconnection = ods.getConnection ();
      version (pconnection );
    }
    catch(SQLException e) {
      e.printStackTrace();
    }
    finally {
      try {
        if (pconnection != null )pconnection .close();
      }
      catch(Exception e) {
        e.printStackTrace();
      }
    }
  }

  public static void version (Connection pconnection) {
    try {
      DatabaseMetaData dmd = pconnection.getMetaData();
      System.out.println("DriverVersion: ["+dmd.getDriverVersion()+"]");
      System.out.println("DriverMajorVersion: ["+dmd.getDriverMajorVersion()+"]");
      System.out.println("DriverMinorVersion: ["+dmd.getDriverMinorVersion()+"]");
      System.out.println("DriverName: ["+dmd.getDriverName()+"]");
      System.out.println("URL: ["+dmd.getURL()+"]");
      System.out.println("UserName: ["+dmd.getUserName()+"]");
      System.out.println(dmd.getDatabaseProductName() );
      System.out.println(dmd.getDatabaseProductVersion() );

      String ver;
      ver = System.getProperty("java.version");
      System.out.println("The JDK version is " + ver);
    }
    catch(SQLException e) {
      e.printStackTrace();
    }

  }
}

// --end : cut here : ThinTnsnames.java -- cut there

compile the program:
javac -classpath ojdbc14.jar:. ThinTnsnames.java

Execute the program:
java -Doracle.net.tns_admin=$ORACLE_HOME/network/admin -classpath .:ojdbc14.jar ThinTnsnames [DATABASE] [USER] [PASSWORD]

Output:

 Connection string = jdbc:oracle:thin:@[DATABASE]
Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 221
        at oracle.net.nl.NVTokens.parseTokens(Unknown Source)
        at oracle.net.nl.NVFactory.createNVPair(Unknown Source)
        at oracle.net.nl.NLParamParser.addNLPListElement(Unknown Source)
        at oracle.net.nl.NLParamParser.initializeNlpa(Unknown Source)
        at oracle.net.nl.NLParamParser.(Unknown Source)
        at oracle.net.resolver.TNSNamesNamingAdapter.loadFile(Unknown Source)
        at oracle.net.resolver.TNSNamesNamingAdapter.checkAndReload(Unknown Source)
        at oracle.net.resolver.TNSNamesNamingAdapter.resolve(Unknown Source)
        at oracle.net.resolver.NameResolver.resolveName(Unknown Source)
        at oracle.net.resolver.AddrResolution.resolveAndExecute(Unknown Source)
        at oracle.net.ns.NSProtocol.establishConnection(Unknown Source)
        at oracle.net.ns.NSProtocol.connect(Unknown Source)
        at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:858)
        at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:268)
        at oracle.jdbc.driver.PhysicalConnection.(PhysicalConnection.java:441)
        at oracle.jdbc.driver.T4CConnection.(T4CConnection.java:165)
        at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)
        at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801)
        at oracle.jdbc.pool.OracleDataSource.getPhysicalConnection(OracleDataSource.java:297)
        at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:221)
        at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:165)
        at ThinTnsnames.test(ThinTnsnames.java:26)
        at ThinTnsnames.main(ThinTnsnames.java:13)

I could not find the problem for this issue. But after logging an SR on metalink the problem was the tnsnames.ora file.

We had one database entry in the tnsnames.ora:

[DATABASE] =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = [SERVERNAME] l)(PORT = 1521)))
(CONNECT_DATA = (SERVICE_NAME = [DATABASE] )(SERVER = DEDICATED)))

But this entry was not correct.

We changed the tnsnames.ora:

[DATABASE] =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = [SERVERNAME] )(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = [DATABASE])
)
)

And now execute the program:

java -Doracle.net.tns_admin=$ORACLE_HOME/network/admin -classpath .:ojdbc14.jar ThinTnsnames [DATABASE] [USER] [PASSWORD]

Connection string = jdbc:oracle:thin:@[DATABASE]
DriverVersion: [10.2.0.4.0]
DriverMajorVersion: [10]
DriverMinorVersion: [2]
DriverName: [Oracle JDBC driver]
URL: [jdbc:oracle:thin:@[database]]
UserName: [USER]
Oracle
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
The JDK version is 1.5.0_06

If this program is working it is also possible to make a JDBC connection in enterprise managers like this:
jdbc:oracle:thin:@[DATABASE]

In the start parameters of the OC4J container there should be an extra option:
-Doracle.net.tns_admin=[TNSNAMES LOCATION]

Note:
It is also possible to configure the JDBC connection like an tnsnames.ora entry in the enterprise manager:

jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(failover=on)(ADDRESS=(PROTOCOL=TCP)(HOST=[SERVERNAME1])(PORT=1521))(address=(protocol=tcp)(host=[SERVERNAME2])(port=1521)))(CONNECT_DATA=(SERVICE_NAME=[DATABASE])))

Did this post help you in any way can you please leave a comment? This will motivate me writing more posts.

Upgrade Default JDK to new version Oracle Application Server 10.1.3

Metalink note: 396096.1]

Did this post help you in any way can you please leave a comment? This will motivate me writing more posts.

upgrade 10.1.2.x to 10.1.2.3: Oracle Internet Directory Patch Configuration Assistant fails

When I upgraded the infra 10.1.2.x to 10.1.2.3 I got an failed on Oracle Internet Directory Patch Configuration Assistant. I found out that in the $ORACLE_HOME/ldap/log/patchca.log there was an error:

Wed Mar 10 09:51:41 CET 2010OID PatchCA started..
Check if OID is configured.
oracle.sysman.assistants.util.NetAPIException: TNS-04404: no error
  caused by: oracle.net.config.ConfigException: TNS-04414: File error
  caused by: TNS-04612: Null RHS for "oaiinfra"
        at oracle.sysman.assistants.util.NetworkUtils.getNetServiceNameValue(NetworkUtils.java:2241)
        at oracle.ldap.oidinstall.OIDPatchCA.run(OIDPatchCA.java:255)
        at oracle.ldap.oidinstall.OIDPatchCA.main(OIDPatchCA.java:443)

After some investigation I found out that the tnsnames.ora was not correct. We changed this an now everything is working.

Did this post help you in any way can you please leave a comment? This will motivate me writing more posts.

Make Access Server debug log (oblog.log) more readable

tail -f oblog.log | sed 's/\%25253d/=/g' | sed 's/\%253d/=/g' | sed 's/\%20/ /g' | sed 's/\%3d/=/g' | sed 's/\%2520/ /g' | sed 's/\%2525253/=/g' | tr ' ' '\n'


Did this post help you in any way can you please leave a comment? This will motivate me writing more posts.

After CPU patch OC4J containers will not start anymore

We applied a CPU patch an Oracle Infrastructure 10.1.2.3 and after that the OC4J containers did not start anymore.

In de $ORACLE_HOME/ldap/log/oidldapd01.log the following error:

Bind failed on communication endpoint (13)  

With an opmnctl status the OID seems to be up.

When this problem occurs you need to execute root.sh.

Did this post help you in any way can you please leave a comment? This will motivate me writing more posts.

The requested resource could not be mapped to a policy domain in the Policy database. Check if the corresponding directory service is up

In the browser we got an 401 Unauthorized error when we tried to start an application behind Oracle Access manager.

In the log.xml in $ORACLE_HOME/j2ee/[OC4J_CONTAINER]/log/[OC4J_CONTAINER/oc4j/ the error:

[CoreIDLoginModule]: Could not authentication user using ObSSOCookie token. Exception: [CoreIDLoginModule]: Could not fetch groups from Access Server. Exception: The requested resource could not be mapped to a policy domain in the Policy database. Check if the corresponding directory service is up.

In the SDK log directory $SDK_HOME/oblix/logs

2010/01/29@07:24:43.738335      7278    7278    ACCESS_SDK      ERROR   0x00001830      /usr/abuild/Oblix/10142hf/palantir/access_api/src/obresource_request.cpp:715  "The requested resource could not be mapped to a policy domain in the Policy database. Check if the corresponding directory service is up."   raw_code^305

I forgot to create the policy for /myresourceurl in the policy manager.



Did this post help you in any way can you please leave a comment? This will motivate me writing more posts.

java.lang.OutOfMemoryError: PermGen space

Nice blog post about Perm Gen

http://oraclebpelindepth.blogspot.com/2009/04/javalangoutofmemoryerror-permgen-space.html
http://www.freshblurbs.com/explaining-java-lang-outofmemoryerror-permgen-space

Install WebGate 10.1.4.2.3 on Apache2 RHEL 5.x 64bit

Download the WebGate software from:
http://download.oracle.com/otn/linux/ias/101401/oam_int_linux_v8_cd1.zip

Login with putty on the server:
su - root

mkdir -p $WEBGATE_HOME/gcc

cp /lib64/libgcc_s.so.1 /appl/oracle/access_10.1.4/gcc/
cp /usr/lib64/libstdc++.so.5 /appl/oracle/access_10.1.4/gcc/

unzip oam_int_linux_v8_cd1.zip

./Oracle_Access_Manager10_1_4_2_3_linux64_APACHE22_WebGate

Did this post help you in any way can you please leave a comment? This will motivate me writing more posts.

Identity Service Authentication failure.

We had an problem in de $ORACLE_HOME/opmn/logs/soa_group....log

<2010-01-13 10:19:05,694> <ERROR> <ari.collaxa.cube.services> <PCException::<init>> Identity Service Authentication failure.
<2010-01-13 10:19:05,695> <ERROR> <ari.collaxa.cube.services> <PCException::<init>> Identity Service Authentication failure.
<2010-01-13 10:19:05,695> <ERROR> <ari.collaxa.cube.services> <PCException::<init>> Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.

Our SOA is integrated with the OID.

The problem was that the account of the oc4jadmin was locked out in the OID.

This can be tested by starting oidadmin and try to login with cn=oc4jadmin, cn=users, dc=oracle, dc=com.

Did this post help you in any way can you please leave a comment? This will motivate me writing more posts.

Tuning Oracle Access Manager

Metalink:

https://support.oracle.com/CSP/main/article?cmd=show&id=404902.1&type=NOT

Did this post help you in any way can you please leave a comment? This will motivate me writing more posts.

ESB cluster: both ESBDT instances up.

In the documentation of the clustering is described that the opmn.xml must be changed.

The oc4j_esbdt container should look like:

<process-type id="OC4J_ESBDT" module-id="OC4J" service-failover="1" status="enabled">

And the numprocs entry should be removed:

<process-set id="default_group"/>

This change will still make it possible to have two esbdt applications live at the same time.

There must be made another change:
service-weight="value" should be added athe the process-type.

<process-type id="OC4J_ESBDT" module-id="OC4J" service-failover="1" service-weight="100" status="enabled">

The instances that run the actual service-failover processes are selected based upon the configured (or default) service-weight value. Instances with higher weights are selected over instances with lower weights.

The expected behavior is that upon startup (opmnctl startall) both ESB-DT instances will startup; however after a very short period of time the OPMN will shutdown the less weighted instance and it will keep running only the higher weighted one.

See metalink note: 733536.1

Did this post help you in any way can you please leave a comment? This will motivate me writing more posts.

ESB-DT: org.apache.slide.webdav.WebdavServlet - ERROR - org.apache.slide.webdav.WebdavException: Internal Server Error

The error: "org.apache.slide.webdav.WebdavServlet - ERROR - org.apache.slide.webdav.WebdavException: Internal Server Error" somethings is shown in the log file of the ESB-DT (design time) by deployment of Large ESB systems. On metalink we found the error: note: 863024.1

09/11/24 12:59:35 24 Nov 2009 12:59:35 - org.apache.slide.webdav.WebdavServlet - ERROR - org.apache.slide.webdav.WebdavException: Internal Server Error
09/11/24 12:59:35 org.apache.slide.webdav.WebdavException: Internal Server Error
09/11/24 12:59:35       at org.apache.slide.webdav.method.AbstractWebdavMethod.run(AbstractWebdavMethod.java:424)
09/11/24 12:59:35       at org.apache.slide.webdav.WebdavServlet.service(WebdavServlet.java:155)
09/11/24 12:59:35       at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
09/11/24 12:59:35       at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
09/11/24 12:59:35       at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:400)
09/11/24 12:59:35       at java.security.AccessController.doPrivileged(Native Method)
09/11/24 12:59:35       at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
09/11/24 12:59:35       at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:414)
09/11/24 12:59:35       at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
09/11/24 12:59:35       at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
09/11/24 12:59:35       at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
09/11/24 12:59:35       at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
09/11/24 12:59:35       at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)
09/11/24 12:59:35       at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
09/11/24 12:59:35       at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
09/11/24 12:59:35       at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:234)
09/11/24 12:59:35       at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:29)
09/11/24 12:59:35       at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:879)
09/11/24 12:59:35       at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
09/11/24 12:59:35       at java.lang.Thread.run(Thread.java:595)

Solution:

1) In httpd.conf set timeout to 3600
2) $ORACLE_HOME/j2ee//config/transaction-manager.xml

set transaction-timeout="3600"
3) Restart SOA suite.


Did this post help you in any way can you please leave a comment? This will motivate me writing more posts.

An unhandled exception has been thrown in the ESB system. The exception reported is: "".

When the error An unhandled exception has been thrown in the ESB system. The exception reported is: "". occures by deployment of the ESB. It can be a problem in the source of the ESB / BPEL.

In our situation the SOAP Services and the ESB were not in sync, that gave the problems. So the source of the ESB and BPEL is changed, that solved the problem.

DeployESBSuitcase:
log4j:WARN No appenders could be found for logger (org.apache.commons.httpclient.params.DefaultHttpParams).
log4j:WARN Please initialize the log4j system properly.
Deployment Attempt Response :

   Entity Deployment Failed
   
      
         An unhandled exception has been thrown in the ESB system. The exception reported is: "".
         
      
   



Deployment Failed ...Unhandled Exception
java.lang.Exception: Deployment attempt failed, please review deployment attempt response above
        at oracle.tip.esb.client.anttasks.DeploymentHelper.deploy(DeploymentHelper.java:112)
        at oracle.tip.esb.client.anttasks.DeploymentHelper.deploy(DeploymentHelper.java:159)
        at oracle.tip.esb.client.anttasks.DeployESBSuitcaseTask.execute(DeployESBSuitcaseTask.java:510)
        at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
        at org.apache.tools.ant.Task.perform(Task.java:364)
        at org.apache.tools.ant.Target.execute(Target.java:341)
        at org.apache.tools.ant.Target.performTasks(Target.java:369)
        at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
        at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37)
        at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
        at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
        at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
        at org.apache.tools.ant.Task.perform(Task.java:364)
        at org.apache.tools.ant.Target.execute(Target.java:341)
        at org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:108)
        at org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:83)
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

Did this post help you in any way can you please leave a comment? This will motivate me writing more posts.

Identity service cannot get roles in realm "{0}". BPEL identity service fails

We had problems while invoking the service getGrantees on /integration/services/IdentityService/identity.

Identity service cannot get roles in realm "{0}".
Error occurs while getting roles in realm "[REALM]".
Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.

After we did a new configure on both instances in the cluster:
$ORACLE_HOME/bpel/system/services/install/ant-tasks
./configure_oid.sh orcladmin [password] [port] false [realm] seedRequiredUsers oc4jadmin [password] oc4j_soa

And we checked the differences between the $ORACLE_HOME/j2ee/oc4j_soa/config/system-jazn-data.xml and $ORACLE_HOME/j2ee/home/config/system-jazn-data.xml. And changed some of the lines.

Another reason can be that the jazn.xml in the $ORACLE_HOME/j2ee/oc4j_soa/config/jazn.xml is not correct. This file should automaticaly be changed by changing the security provider in em, sometimes this fails. You can change the security provider to the original value and after that back to the OID in em and look in $ORACLE_HOME/j2ee/home/config/jazn.xml. The contents should be changed with the correct values for your OID.

Everything worked again.






Did this post help you in any way can you please leave a comment? This will motivate me writing more posts.

Form-Based Authentication for J2EE application, Netpoint/Oblix/CoreId/Oracle Access Manager, logon second time does not work

A customer of mine was using form based authetication with Oracle Access Manager. When the users logged in for the first time through the login.html screen everyting was ok. But when they logged out and tried to login again the form was not working anymore.

We used the logout.html code from the installation directory of the webgate. After some investigation we found out that the problem was that the registration of the webgates and access gates had different values for the cookie settings.

Primary HTTP Cookie Domain [hostname]
Preferred HTTP Host [virtual hostname]

Did this post help you in any way can you please leave a comment? This will motivate me writing more posts.

SOA 10.1.3.x: SOAP Endpoint URI returns 404 error

When the SOAP Endpoint URI returns an 404 error a possible solution can be: metalink note: 741792.1

1. Backup and edit $ORACLE_HOME/j2ee//config/default-web-site.xml
2. Change the ohs-routing value from false to true:

ohs-routing="true" />

Did this post help you in any way can you please leave a comment? This will motivate me writing more posts.