Remote activation exception

Question

Hi,
I have an rmi server registered with the rmi registry for remote activation. I get the following error when activated.
I started rmid in debug mode using the following command:
rmid -port 9242 -log c:\temp\rmid.log -J-Djava.security.policy="c:\temp\java.policy" -J-Dsun.rmi.log.debug=true -J-Dsun.rmi.server.activation.debugExec=true -J-Dsun.rmi.dgc.logLevel=10 -J-Dsun.rmi.dgc.logLevel=10 -J-Dsun.rmi.loader.logLevel=10 -J-Djava.class.path=C:\\temp\\test1.jar;C:\\temp\\wasspi_jmx_JSpiCola.jar;C:\\temp\\wasspi_JSpiCola.jar;C:\\temp\\castor.jar;C:\\temp\\xalan.jar;C:\\temp\\xerces.jar;C:\\temp\\log4j-1.2.15.jar
output:
May 12, 2009 6:46:13 PM sun.rmi.server.LoaderHandler loadClass
FINE: main: name = "sun.rmi.server.Activation$DefaultExecPolicy", codebase = ""
log.debug: recover()
log.debug: recovering from c:\temp\rmid.log\Snapshot.1
May 12, 2009 6:46:13 PM sun.rmi.server.LoaderHandler loadClass
FINE: main: name = "sun.rmi.server.Activation", codebase = ""
May 12, 2009 6:46:13 PM sun.rmi.server.LoaderHandler loadClass
FINE: main: name = "java.util.HashMap", codebase = ""
log.debug: reading updates from c:\temp\rmid.log\Logfile.1
log.debug: rdUpdate size 1436
FINE: RMI TCP Connection(2)-15.154.106.14: name = "java.rmi.activation.ActivationID", codebase = ""
May 12, 2009 6:46:20 PM sun.rmi.server.LoaderHandler loadClass
FINE: RMI TCP Connection(2)-15.154.106.14: name = "java.rmi.server.UID", codebase = ""
rmid: debugExec: running "C:\temp\JDK\bin\java.exe -Djava.class.path=C:\temp\test1.jar;C:\temp\w
asspi_jmx_JSpiCola.jar;C:\temp\wasspi_JSpiCola.jar;C:\temp\castor.jar;C:\temp\xalan.jar;C:\temp\xerc
es.jar;C:\temp\log4j-1.2.15.jar -Djava.security.policy=c:\temp\java.policy sun.rmi.server.Activation
GroupInit"
Tue May 12 18:46:21 GMT+05:30 2009:ExecGroup-0:err:Exception in starting ActivationGroupInit:
Tue May 12 18:46:21 GMT+05:30 2009:ExecGroup-0:err:java.io.StreamCorruptedException: invalid streamheader
Tue May 12 18:46:21 GMT+05:30 2009:ExecGroup-0:err: at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:768)
Tue May 12 18:46:21 GMT+05:30 2009:ExecGroup-0:err: at java.io.ObjectInputStream.<init>(ObjectInputStream.java:283)
Tue May 12 18:46:21 GMT+05:30 2009:ExecGroup-0:err: at sun.rmi.server.MarshalInputStream.<init>(MarshalInputStream.java:122)
Tue May 12 18:46:21 GMT+05:30 2009:ExecGroup-0:err: at sun.rmi.server.ActivationGroupInit.main(ActivationGroupInit.java:63)
Here is the server class:
collectorAndServerProps.put("java.security.policy", "c:\\temp\\java.policy");
collectorAndServerProps.put("java.class.path", "C:\\temp\\test1.jar;C:\\temp\\wasspi_jmx_JSpiCola.jar;C:\\temp\\wasspi_JSpiCola.jar;C:\\temp\\castor.jar;C:\\temp\\xalan.jar;C:\\temp\\xerces.jar;C:\\temp\\log4j-1.2.15.jar");
String javaCommand = "C:\\temp\\JDK\\bin\\java.exe";
String srcURL = "file:///c:/temp/wasspi_jmx_JSpiCola.jar";
ActivationGroupDesc.CommandEnvironment cmdEnv = new ActivationGroupDesc.CommandEnvironment(javaCommand, null);
ActivationGroupDesc groupDesc = new ActivationGroupDesc(collectorAndServerProps, cmdEnv);
ActivationGroupID groupID = ActivationGroup.getSystem().registerGroup(groupDesc);
MarshalledObject args = new MarshalledObject(bindName);
ActivationDesc desc = new ActivationDesc(groupID, "com.hp.openview.wasspi.collector.rmi.RemoteJSpiColaImpl", srcURL, args);
RemoteJSpiCola jSpiColaStub = (RemoteJSpiCola) Activatable.register(desc);
Registry reg = LocateRegistry.getRegistry(Integer.parseInt(rmidPort));
reg.rebind(bindName, jSpiColaStub);
RemoteJSpiCola remoteJSpiCola = (RemoteJSpiCola) Naming.lookup(url);
remoteJSpiCola.getData(argv);
Any clues?
Thanks,
Thiyagu

Answer 1

Looks like rmid.log is corrupt.
Your server class shouldn't do its own registration. That causes the rmid.log file to grow every time you start it. You should have a separate registration program that you only run once, and serializes the activatable stub to a file, and another program that runs every system startup that reads that file and binds the stub to the registry. That will conserve the size of the rmid.log file and also eliminate most writing to it, which is when corruption can occur.