Comments on: Resolve OAS Startup Issue: “Port Information in the ONS Notification is Incorre… http://www.dbuggr.com/smallwei/resolve-oc4j-startup-issue-port-information-ons-notification-incorr/ Share Knowledge & Be Rewarded Fri, 03 Feb 2012 23:13:48 -0600 http://wordpress.org/?v=2.8.6 hourly 1 By: smallwei http://www.dbuggr.com/smallwei/resolve-oc4j-startup-issue-port-information-ons-notification-incorr/comment-page-1/#comment-490 smallwei Tue, 08 Dec 2009 03:14:12 +0000 http://www.dbuggr.com/smallwei/resolve-oc4j-startup-issue-port-information-ons-notification-incorr/#comment-490 <ol> <li>Make sure there is no network or IP change recently.</li> <li>Shutdown OAS, delete everything located under $OAS_HOME\j2ee\home\persistence\ (do not delete persistence folder itself) and restart the server.</li> <li>Try to identify which process actually caused this error by disable "one process" at a time (if you have multiple processes):</li> </ol> In my case, I have two processes. <ul> <li>Shutdown OAS, edit opmn.xml and disable "home" process first.</li> <code><process-type id="home" module-id="OC4J" status="disabled"></code> <li>Startup OAS and see if you are getting the error.</li> <li>If there is no error, I then shutdown OAS, re-enable "home" process, and then I disable "oc4j_soa" process.</li> <code><process-type id="oc4j_soa" module-id="OC4J" status="disabled"></code> <li>Startup OAS and see if you are getting the error.</li> <li>In my case, OAS also comes up without error this time.</li> <li>This tells me there is a conflict (possibily port) between "oc4j_soa" and "home" process.</li> <li>I then decided to give both oc4j_soa and home processes different "range" of port for RMI, RMIS and JMS:</li> <code><port id="rmi" range="12401-12500"/> <port id="rmis" range="12701-12800"/> <port id="jms" range="12601-12700"/></code> </ul> This resolved my issues.
  • Make sure there is no network or IP change recently.
  • Shutdown OAS, delete everything located under $OAS_HOME\j2ee\home\persistence\ (do not delete persistence folder itself) and restart the server.
  • Try to identify which process actually caused this error by disable “one process” at a time (if you have multiple processes):

    • In my case, I have two processes.

    • Shutdown OAS, edit opmn.xml and disable “home” process first.

      • <process-type id="home" module-id="OC4J" status="disabled">

    • Startup OAS and see if you are getting the error.
    • If there is no error, I then shutdown OAS, re-enable “home” process, and then I disable “oc4j_soa” process.

      • <process-type id="oc4j_soa" module-id="OC4J" status="disabled">

    • Startup OAS and see if you are getting the error.
    • In my case, OAS also comes up without error this time.
    • This tells me there is a conflict (possibily port) between “oc4j_soa” and “home” process.
    • I then decided to give both oc4j_soa and home processes different “range” of port for RMI, RMIS and JMS:

      • <port id="rmi" range="12401-12500"/>
<port id="rmis" range="12701-12800"/>
<port id="jms" range="12601-12700"/>

    This resolved my issues.

    ]]>