Skip to Main Content

Integration

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

JDev Client freezes doing a jndi lookup for a remote EJB

534612Sep 13 2007 — edited Oct 18 2007
I'm trying to access a remote EJB deployed on OAS from my JDev client. I've configured OPMN and RMI of the OAS like the manual said, but when I try to make a lookup the client freezes forever in the line below with no exception.

Object obj = context.lookup(pJNDIname);

Take a look at my properties:

INITIAL_CONTEXT_FACTORY_CLASS="oracle.j2ee.naming.ApplicationClientInitialContextFactory"
PROVIDER_URL="opmn:ormi://170.10.2.179:6006:PMNComum/PMNComum/"
APPLICATION_NAME="PMNComum"
SECURITY_PRINCIPAL="admin"
SECURITY_CREDENTIAL="xxxx"

------------
rmi.xml

<rmi-server port="23791" host="170.10.2.179">
<!-- A remote server connection example -->
<!-- <server host="the.remote.server.com" username="adminUser" password="123abc" /> -->

<!-- path to the log-file where RMI-events/errors are stored -->
<log>
<file path="../log/rmi.log"/>
<!-- Uncomment this if you want to use ODL logging capabilities
<odl path="../log/rmi/" max-file-size="1000" max-directory-size="10000"/>
-->
</log>
</rmi-server>

------------
opmn.xml

<?xml version = '1.0' encoding = 'UTF-8'?>
<opmn xmlns="http://www.oracle.com/ias-instance">
<notification-server>
<port local="6104" remote="6203" request="6006"/>
...
<process-type id="PMNComum" module-id="OC4J">
<module-data>
<category id="start-parameters">
<data id="java-options" value="-server -Djava.security.policy=/opt/oracle/OraComplHm/j2ee/PMNComum/config/java2.policy -Djava.awt.headless=true"/>
<data id="oc4j-options" value="-properties"/>
</category>
<category id="stop-parameters">
<data id="java-options" value="-Djava.security.policy=/opt/oracle/OraComplHm/j2ee/PMNComum/config/java2.policy -Djava.awt.headless=true"/>
</category>
</module-data>
<start timeout="900" retry="2"/>
<stop timeout="120"/>
<restart timeout="720" retry="2"/>
<port id="ajp" range="12501-12600"/>
<port id="rmi" range="12401-12500"/>
<port id="jms" range="12601-12700"/>
<process-set id="default_island" numprocs="1"/>
</process-type>

-----------

If I use netstat -a I can see the ESTABLISHED connection with the server in the right RMI port.

TCP PORTAL35:1581 caapiranga:12405 ESTABLISHED

Could anyone help me?

Thanks.
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Nov 15 2007
Added on Sep 13 2007
5 comments
807 views