Wednesday, January 20, 2010

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

Thursday, January 14, 2010

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.

Wednesday, January 13, 2010

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.

Friday, January 8, 2010

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.

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.

Friday, October 2, 2009

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.

Friday, August 14, 2009

Apache error_log: mod_oc4j: request to OC4J [hostname]:[port] failed: Connect failed

I found out that the error below was caused by wrong configuration of the security provider of the application opm-public. When we changed jazn.xml in $ORACLE_HOME/j2ee/[oc4j_container]/config directory with the correct settings and that solved this problem.


[Thu Aug 13 16:09:08 2009] [error] [client 10.8.192.155] [ecid: 1250172548:10.9.8.44:23073:0:7,0] mod_oc4j: Failed to find a failover oc4j process for session request for destination: application://opm-public (no island or jgroup).
[Thu Aug 13 16:09:08 2009] [error] [client [ip_address]] [ecid: 1250172548:10.9.8.44:23073:0:7,0] mod_oc4j: request to OC4J [hostname]:[port] failed: Connect failed


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

Tuesday, August 11, 2009

Automatic BPEL deployment with ant error: A problem occured while connecting to server II

The following error can occur:

Embedded error: The following error occurred while executing this line:
[INSTALL_DIR]/ant/bpel/common-build.xml:84: A problem occured while connecting to server "[hostname]" using port "[port]": java.security.AccessControlException: access denied (com.collaxa.security.DomainPermission HetRotterdamseHuwelijk read)
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
at java.security.AccessController.checkPermission(AccessController.java:427)
at com.collaxa.security.OC4JSecurityService.checkAccess(OC4JSecurityService.java:16)
at com.collaxa.security.SecurityService.checkDomainAccess(SecurityService.java:26)
at com.collaxa.cube.fe.util.ServletUtils.getLocatorWithoutUrlRewrite(ServletUtils.java:76)
at _deployHttpClientProcess._jspService(_deployHttpClientProcess.java:332)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:462)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:400)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:414)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:234)
at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:29)
at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:879)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)


This can be solved by change the orion-application.xml in the deploy_services application.

$ORACLE_HOME/j2ee/oc4j_soa/application-deployments/deploy_service/orion-application.xml and $ORACLE_HOME/j2ee/oc4j_soa/applications/deploy_service/META-INF/orion-application.xml



<jazn provider="XML" jaas-mode="doAsPrivileged" />


Replace by:


<jazn provider="LDAP" jaas-mode="doAsPrivileged" />


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

Monday, August 10, 2009

Automatic BPEL deployment with ant error: A problem occured while connecting to server

Our BPEL deployments with ant were always succesfull but after an while it was not working anymore during the deployment of an BPEL process we got the error as shown below:


[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error executing ant tasks

Embedded error: The following error occurred while executing this line:
[INSTALL_DIR]/common-build.xml:82: A problem occured while connecting to server "[host]" using port "[port]":


Deployment of an BPEL process by placing it in the $ORACLE_HOME/bpel/domains/[BPEL_DOMAIN]/deploy was successfull.

After we enabled the verbose option I noticed which url is used to deploy the BPEL process http://hostname:port/integration/services/deploy/deployHttpClientProcess.jsp . The application used is deploy_services in the oc4j_soa container. When the url is executed in an browser an popup is shown on which you should log on. But we got an other error:


Authorization Required
This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.


This error was caused by an change in the file $ORACLE_HOME/Apache/Apache/conf/mod_oc4j.conf. A while ago we put an line in this config file:


Oc4jUseOHSErrors on


After we removed Oc4jUseOHSErrors on. Everything worked like it supposed to.

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

Wednesday, August 5, 2009

High Available Oracle Access Manager with BIG-F5

High Available Oracle Access Manager with BIG-F5

http://www.f5.com/pdf/deployment-guides/f5-oracle-oam-dg.pdf

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

Wednesday, July 29, 2009

Find the orasso password

With the following command the ORASSO database user password can be obtained:

ldapsearch -D cn=orcladmin -w [ORCLADMIN PASSWORD] -p [LDAP_PORT] \
-h [LDAP_URL] -b "cn=IAS,cn=Products,cn=OracleContext" \
-s sub -v OrclresourceName=ORASSO | grep \
orclpasswordattribute


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

Ldap_Search: DSA Is Unwilling To Perform

Today I wanted to make an shell script that checks if an attribute of an user in the OID had a specific value. I tried to make an ldapsearch statement but it failed with the error:

DSA Is Unwilling To Perform
ldap_search: additional info: Function Not Implemented


I found out that it is not possible to search on an uncataloged (unindexed) attribute.

This can be fixed by:

Create an index on the attribute used in the search using catalog.

For this example:
$ORACLE_HOME/ldap/bin/catalog connect="[ORACLE_SID_METADATA REPOSITORY]" add=true attribute="[SEARCH ATTRIBUTE]"

Output:
This tool can only be executed if you know database user password for OID
Enter OID Password ::

Password of het orcladmin user should be entered now!



Restart the OID server.

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

Thursday, July 23, 2009

SOA suite clustering FAQ document (feb 2009)

http://www.oracle.com/technology/tech/soa/pdf/oracle-soa-suite-ha-faq.pdf

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

Wednesday, July 15, 2009

An unhandled exception has been thrown in the ESB system. The exception reported is: "java.io.IOException: Delete failed

When the following error occurs, it is possible to reset the oraesb schema in the database. The reset.sh is not recommended on a production system. First we had this problem on some development machines, we did a reset of the oraesb schema, this solved our issue.

But when we had this problem on production we first tried this:

Metalink note: 863024.1. The note describes another problem but it also helped us with the delete failed error.


[deployESBProjects] Deployment Attempt Response :
[deployESBProjects]
[deployESBProjects]
[deployESBProjects] An unhandled exception has been thrown in the ESB system. The exception reported is: "java.io.IOException: Delete failed
[deployESBProjects] at oracle.tip.esb.server.bootstrap.ESBBaseResourceAdapter.createIOException(ESBBaseResourceAdapter.java:630)
[deployESBProjects] at oracle.tip.esb.server.bootstrap.ESBBaseResourceAdapter.access$200(ESBBaseResourceAdapter.java:130)
[deployESBProjects] at oracle.tip.esb.server.bootstrap.ESBBaseResourceAdapter$2.delete(ESBBaseResourceAdapter.java:550)
[deployESBProjects] at oracle.tip.esb.lifecycle.AuxiliaryFileHandler.deleteProject(AuxiliaryFileHandler.java:555)
[deployESBProjects] at oracle.tip.esb.console.XMLConsoleManagerImpl.cleanSlideRepositoryForProject(XMLConsoleManagerImpl.java:2364)
[deployESBProjects] at oracle.tip.esb.console.XMLConsoleManagerImpl.commit(XMLConsoleManagerImpl.java:2405)
[deployESBProjects] at oracle.tip.esb.configuration.deployment.JDevDeploymentManager.deploy(JDevDeploymentManager.java:226)
[deployESBProjects] at oracle.tip.esb.configuration.deployment.DeploymentServlet.doPost(DeploymentServlet.java:120)
[deployESBProjects] at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
[deployESBProjects] at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
[deployESBProjects] at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
[deployESBProjects] at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:400)
[deployESBProjects] at java.security.AccessController.doPrivileged(Native Method)
[deployESBProjects] at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
[deployESBProjects] at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:414)
[deployESBProjects] at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
[deployESBProjects] at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
[deployESBProjects] at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
[deployESBProjects] at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
[deployESBProjects] at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)
[deployESBProjects] at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
[deployESBProjects] at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
[deployESBProjects] at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:234)
[deployESBProjects] at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:29)
[deployESBProjects] at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:879)
[deployESBProjects] at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
[deployESBProjects] at java.lang.Thread.run(Thread.java:595)
[deployESBProjects] Caused by: Service org.apache.slide.store.impl.rdbms.J2EEStore@1966d52 access error : ORA-02292: integrity constraint (ORAESB.SYS_C005694) violated - child record found


[deployESBProjects] at org.apache.slide.macro.MacroImpl.delete(MacroImpl.java:522)
[deployESBProjects] at org.apache.slide.macro.MacroImpl.delete(MacroImpl.java:482)
[deployESBProjects] at org.apache.slide.macro.MacroImpl.delete(MacroImpl.java:463)
[deployESBProjects] at oracle.tip.esb.server.bootstrap.slide.DeleteFolder.delete(DeleteFolder.java:76)
[deployESBProjects] at oracle.tip.esb.server.bootstrap.slide.DeleteFolder.executeRequest(DeleteFolder.java:58)
[deployESBProjects] at oracle.tip.esb.server.bootstrap.slide.AbstractSlideMethod.execute(AbstractSlideMethod.java:142)
[deployESBProjects] at oracle.tip.esb.server.bootstrap.slide.SlideHandler.delete(SlideHandler.java:153)
[deployESBProjects] at oracle.tip.esb.server.bootstrap.ESBBaseResourceAdapter$2.delete(ESBBaseResourceAdapter.java:548)
[deployESBProjects] ... 24 more
[deployESBProjects] ".

[deployESBProjects]
[deployESBProjects]

[deployESBProjects]
[deployESBProjects]





Two timers need to be extended in order to make the registration successful. It is assumed here that the HTTP server being used is the Oracle HTTP Server.

(1) At the HTTP Server that is hosting the ESB Designtime container edit the following file:

$ORACLE_HOME/Apache/Apache/conf/httpd.conf

(2) Change the value of "Timeout" to a higher value, e.g. from:

Timeout 300

to:

Timeout 3600

A value of 3600 (seconds) is high enough to cover most cases, but it could be possible that a higher value may be needed.

(3) Restart the HTTP server to make the change affective.

(4) At the ESB Designtime container edit the following file:

$ORACLE_HOME/j2ee//config/transaction-manager.xml

(5) Change the value or transaction-timeout to a higher value, e.g. from:

transaction-timeout="30"

to:

transaction-timeout="3600"
In most cases this timeout should match that of the value set at the HTTP Server.

(6) Restart the SOA server or ESB Designtime container to make the change affective.

(7) Retry the large ESB project registration.


If this solution does not work you can try the reset.sh.

Before executing the command read the whole post!!!!! Otherwise your ESB can be corrupted.

With the following command you can clean up your oraesb schema:

cd $ORACLE_HOME/integration/esb/bin
./reset.sh -DDB_URL=jdbc:oracle:thin:@//db_host:db_port/sid -DDB_USER=oraesb -DDB_PASSWORD=oraesb


WATCH OUT when using this on SOA 10.1.3.4 MLR 8

It looks like the database schema of oraesb is corrupted after the reset.sh script. In our case the ESB deployments failed after this. I ran the sql script form the latest patch again and now everything seems fine.

During deployment this error can occur:


[deployESBProjects] Deployment Attempt Response :
[deployESBProjects]
[deployESBProjects] Entity Deployment Failed
[deployESBProjects]
[deployESBProjects]
[deployESBProjects] Failed to create Service "ProcesServic e".
[deployESBProjects] Ensure that the (a) Repository is available. ( b) The Connection information for the Repository is Valid. Verify the detailed c ause of error if available. Contact Oracle Support if error not fixable.
[deployESBProjects]

[deployESBProjects]

[deployESBProjects]



There is also another problem the BPELSystem in the ESB is gone.
Did this post help you in any way can you please leave a comment? This will motivate me writing more posts.

Monday, July 6, 2009

Howto Configuring Canon MP620 on ubuntu

Today I found a site about configuring a Canon MP620 printer on ubuntu.

https://help.ubuntu.com/community/HardwareSupportComponentsPrintersCanonPrintersCanonMP620

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

Wednesday, June 24, 2009

Oracle Application Server 10.1.3 Associate OID with OC4J instance

In the EM console of the Oracle Application Server you can connect an OID to an OC4J instance by doing the following:

Click on an oc4j instance - Click on link Administration: Under security you will find Identity Management.

This text is shown:

You can associate an installed Oracle Internet Directory with this OC4J instance. You can then choose to use this Oracle Internet Directory for runtime authentication and authorization for deployed applications.


I assumed that this means that you can associate multiple OID's to different OC4J instances but this is not true. When you change the OID here, it wil change the OID for all OC4J instances on this application server.

When you want to user different OID's for different applications you should put this in the orion-application.xml file of the application.

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