File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes EJB and other Java EE Technologies and the fly likes Interesting problem in starting up j2ee 1.2 reference implementation. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Interesting problem in starting up j2ee 1.2 reference implementation." Watch "Interesting problem in starting up j2ee 1.2 reference implementation." New topic
Author

Interesting problem in starting up j2ee 1.2 reference implementation.

Vivek Viswanathan
Ranch Hand

Joined: Mar 03, 2001
Posts: 350
Hi
I am facing some problem in starting up the j2ee 1.2 (sun reference implementation) I am using jdk1.3.0_02. I didn�t have the problem about a few days back everything was working fine, with the current configuration, since then till now I have not changed anything at all but the j2ee server just wont start up. The documentation of the j2ee1.2 says that it has been tested with jdk1.2, but I am using jdk1.3, but I dont think that this is the problem, since the server was working perfectly fine all this time.
More details on my problem.
Extract from Error.log file : This extract contains only two entries the first log entry show that the server was running successfully, and next entry indicates that the problem. In the actual log file there were many more entries but all those entries indicated sucessfully working of j2ee server.
----------------------------------------------------------------------------------------------------
Logging for J2EE Server Version: 1.2-BL started at: Fri Aug 31 15:54:18 GMT+01:00 2001..
Using the Java HotSpot(TM) Client VM and the version number 1.3.0_02 from Sun Microsystems Inc..
VM is using the classpath: c:\TEMP\prog\j2sdkee1.2\lib\classes;c:\TEMP\prog\j2sdkee1.2\lib\locale;c:\TEMP\prog\j2sdkee1.2\lib\j2ee.jar;C:\TEMP\prog\jdk1.3.0_02\jre\lib\rt.jar;C:\TEMP\prog\jdk1.3.0_02\lib\too ls.jar;.;;c:\TEMP\prog\j2sdkee1.2\lib\cloudscape\RmiJdbc.jar;c:\TEMP\prog\j2sdkee1.2\lib\cloudscape\client.jar;c:\TEMP\prog\j2sdkee1.2\lib\jhall.jar .
J2EE Home Directory has been set to: c:\TEMP\prog\j2sdkee1.2.

Cannot find keystore file : C:\WINNT\Profiles\vviswanathan\.keystore

Logging for J2EE Server Version: 1.2-BL stopped at: Fri Aug 31 17:03:26 GMT+01:00 2001.
Logging for J2EE Server Version: 1.2-BL started at: Wed Sep 05 09:34:20 GMT+01:00 2001..
Using the Java HotSpot(TM) Client VM and the version number 1.3.0_02 from Sun Microsystems Inc..
VM is using the classpath: c:\TEMP\prog\j2sdkee1.2\lib\classes;c:\TEMP\prog\j2sdkee1.2\lib\locale;c:\TEMP\prog\j2sdkee1.2\lib\j2ee.jar;C:\TEMP\prog\jdk1.3.0_02\jre\lib\rt.jar;C:\TEMP\prog\jdk1.3.0_02\lib\too ls.jar;.;;c:\TEMP\prog\j2sdkee1.2\lib\cloudscape\RmiJdbc.jar;c:\TEMP\prog\j2sdkee1.2\lib\cloudscape\client.jar;c:\TEMP\prog\j2sdkee1.2\lib\jhall.jar .
J2EE Home Directory has been set to: c:\TEMP\prog\j2sdkee1.2.

org.omg.CORBA.INTERNAL: minor code: 1398079496 completed: No
at com.sun.corba.ee.internal.iiop.GIOPImpl.createListener(GIOPImpl.java:193)
at com.sun.corba.ee.internal.iiop.GIOPImpl.getEndpoint(GIOPImpl.java:152)
at com.sun.corba.ee.internal.POA.POAORB.setPersistentServerPort(POAORB.java:402)
at com.sun.enterprise.iiop.POAEJBORB.setPersistentServerPort(POAEJBORB.java:299)
at com.sun.enterprise.iiop.POAProtocolMgr.setPersistentServerPort(POAProtocolMgr.java:168)
at com.sun.enterprise.server.EJBServer.setPersistentServerPort(EJBServer.java:467)
at com.sun.enterprise.server.EJBServer.setPersistentServerInfo(EJBServer.java:415)
at com.sun.enterprise.server.EJBServer.init(EJBServer.java:197)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:233)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:829)
----------------------------------------------------------------------------------------------
As you can see from this log entry the server was working fine on the 31st of Sep2001, but it would not work on the 5th Aug 2001 when I tried starting it.
Initially I thought that that may be a problem since a particular port that the j2ee server uses may already be in use by some other application, so I changed the default ports and tried it again about I used to get exactly the same error. Also the problem is not because of some incorrect JAVA_HOME, J2EE_HOME or PATH environment variable setting because I have crosschecked these variables, and I have not modified them from the last successfully start up of j2ee server.
As you can see from the stack trace above
-----------------------------------------------------------------------
org.omg.CORBA.INTERNAL: minor code: 1398079496 completed: No
at com.sun.corba.ee.internal.iiop.GIOPImpl.createListener(GIOPImpl.java:193)
.......
-------------------------------------------------------------------------
This shows that the error originates from com.sun.corba.ee.internal.iiop.GIOPImpl.createListener method so I opened up the j2ee.jar from the lib dir of j2ee installation, and decompiled the class com.sun.corba.ee.internal.iiop.GIOPImpl
Here are the contents of decompiled class (only the createListener method that caused the error)
------------------------------------------------------------------------------------------
private synchronized ListenerThread createListener(int i)
{
ConnectionTable connectiontable = table;
ListenerThread listenerthread;
try
{
ServerSocket serversocket = orb.getSocketFactory().createServerSocket(i);
listenerthread = (ListenerThread)AccessController.doPrivileged(new Object(connectiontable, serversocket) /* anonymous class not found */
class _anm1 {}
);
listenerthread.start();
}
catch(Exception _ex)
{
throw new INTERNAL(0x53550008, CompletionStatus.COMPLETED_NO);
}
return listenerthread;
}
-------------------------------------------------------------------------------------------
As you can see from the above code extract in the catch block it throws an internal exception (whatever that is???) with an Hex Code of 0x53550008, now when you convert this Hex code to a decimal code it is 1398079496, this exactly matches the �minor code number� in the error.log file, this confirms that the exception is being thrown from the createListener(int i) method.
Any Ideas on what the problem could be, I could probably reinstall jdk and j2ee and the problem may go away, but I don�t wan to do that I am mainly interested in solving this problem and trying to understand how the j2ee server just stopped working.
I feel that there is some problem with the native code ioser12.dll ( this is the same dll that should be in the path when I start up j2ee)...please confirm
Does any CORBA prgrogrammer know what this internal error code : 1398079496 stands for ?
When I started up the j2ee server on the 31st Sep 2001 (when it was working fine), I didn�t deploy any ejb�s all that I did was run a few simple jsp pages.
Vivek Viswanathan SCJP, SCJD, SCEA Part I
What are the legal problems in decompiling the j2ee reference implementation classes, is it ok ?, in this case when I am trying to solve a problem !!!


Vivek Viswanathan SCJP 1.2, SCJP 1.6,SCJD,SCEA,SCWCD,IBM-484,IBM-486,IBM-141,Ms.NET C# 70-316,SCMAD, LPIC-I
Vivek Viswanathan
Ranch Hand

Joined: Mar 03, 2001
Posts: 350
Hi
This may seem tottally crazy, but I started the server today it is working perfectly fine. It is working as smoothly as before. I also tried changeing the date back and started up the server, but I do not face any problem at all.
Vivek Viswanathan
Rainer Schulz
Greenhorn

Joined: Jan 30, 2005
Posts: 1
I did restart my pc, then I did "ipconfig /renew" - and it worked again.

VERY STRANGE!!!
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Interesting problem in starting up j2ee 1.2 reference implementation.
 
Similar Threads
J2EE server still crashes
J2EE server crashes
J2EE and winNT
J2EE - Download
J2EE server still crashes