Jason,
> At this point, I've achieved some functionality with the shared JVM. I'm > just not clear on when reconnect_JVM is required. Is this only required > after a fork to deal with closing the parents sockets/registering with > the shared JVM? reconnect_JVM() is required after a fork in order to get the child it's own connection. Or else you have parent an child reading/writing from the same file descriptor and that's trouble. > Is there a way to see if the JVM is already running > besides checking $Inline::Java::JVM? Not really. You can try connecting to it and see if that works but that's about it. > Is there a way to find out the pid > that started the JVM besides the pid member variable in Inline::Java::JVM? No. The pid member variable in Inline::Java::JVM is the pid of the JVM itself, not that of the process that started it. > I have a few issues remaining which I believe are caused by a fork() > call I haven't tracked down yet. The symptom is that JNDI lookups fail, > or EJB calls result in authorization failures. I just want to ensure > that I'm not misunderstanding how/when to use reconnect. If you have multiple processes uing the same connection you can get pretty unpredictable results (just like in most client/server apps). Patrick -- ===================== Patrick LeBoutillier Laval, Québec, Canada