JDev - J2EE Deployment Problem

Question

I'm not sure if I should be posting this here or in the J2EE forum but here is my problem. Whenever I try to deploy a web application to our J2EE server I get the following error.
Invoking Oracle9iAS admin tool...
D:\jdk1.3.1\jre\bin\javaw.exe -jar D:\jdev9i_902\j2ee\home\admin.jar ormi://some.remote.host:23791/ admin **** -deploy -file D:\jdev9i_902\jdev\mywork\JSPTest\HW\HW.ear -deploymentName HW
Communication error: Disconnected: Connection reset by peer: JVM_recv in socket input stream read
Exit status of Oracle9iAS admin tool (-deploy): 0
-If i try to deploy a war file I get this slightly different error.
D:\jdk1.3.1\jre\bin\javaw.exe -Xmx128m -jar D:\jdev9i_902\j2ee\home\admin.jar ormi://some.remote.host:23791/ admin **** -deploy -file D:\jdev9i_902\jdev\mywork\JSPTest\Project1\webapp1.ear -deploymentName webapp1
Communication error: Disconnected: Connection reset by peer: JVM_recv in socket input stream read
Exit status of Oracle9iAS admin tool (-deploy): 0
D:\jdk1.3.1\jre\bin\javaw.exe -jar D:\jdev9i_902\j2ee\home\admin.jar ormi://some.remote.host:23791/ admin **** -bindWebApp webapp1 webapp1 http-web-site /JSPTest-Project1-context-root
Error: com.evermind.server.rmi.OrionRemoteException: Disconnected: Connection reset by peer: JVM_recv in socket input stream read
Exit status of Oracle9iAS admin tool (-bindWebApp): 1
Here is what I do to run our J2EE server.
java -Xmx268435456 -jar $j2ee_home/orion.jar
Oracle9iAS (1.0.2.2.1) Containers for J2EE initialized
I'm running JDev 9.0.2.829
I have confirmed that the J2EE server is listening on port 23791 and I can browse to it on port 8888. Any help would be appreciated.
-Eric Dalquist

Answer 1

See Infrastructure Serrver is down and Re: Lov values filtered by the value selected in other LOV for related discussions.
Here is a cut-and-paste of the important part:
When JDeveloper deploys to a remote OC4J, JDeveloper must use client-side classes to communicate with the server-side administrative objects via RMI. Since communication over RMI uses object serialization to send object instances across the wire, if there is a difference in version in the client-side objects and the server-side objects, there are likely to be deploy-time problems. The incompatibility would be due to implementation decisions made by the OC4J development team.
By default, JDeveloper uses the client-side OC4J classes that ship with JDeveloper. However, if you need to deploy to a different version of OC4J than what ships with JDeveloper, you can tell JDeveloper to use a different set of client-side classes when defining an OC4J connection in the JDeveloper connection manager. On step 3 of the Connection Wizard, there is a field labeled "Local Directory Where admin.jar for Oracle9iAS is Installed". Point that to the OC4J 1.0.2.2 directory containing admin.jar, and you should then be able to deploy from JDev 9i (9.0.2) production to OC4J 1.0.2.2.
There are a few other less common causes for hanging at deploy-time. Let's say you've specified a target server URL of "ormi://myserver".
1) Try specifying the full host name instead of the abbreviated name -- works around problems with hostname resolution.
2) Try specifying the IP address of the target server instead of the hostname -- works around problems with DNS lookups.
3) Try specifying "http:ormi://myserver" as the URL instead -- works around problems with a proxy server that is between the JDeveloper machine and the server (by using HTTP tunnelling).
Hope that helps.