Thursday, November 26, 2009

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.

Tuesday, November 24, 2009

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.

Thursday, November 19, 2009

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.

Wednesday, November 11, 2009

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.