the other possible culprit i forgot to mention was Websphere App server 6.0. even though the same error occurred after WAS was taken down, it might have left some residual side effects. the z/os 1.7 lpar where TOMCAT/JBOSS does work does not run Websphere App server (just HTTP server) and the z/os 1.9 lpar where they work is not currently running WAS either.
the JDK being used on z/os 1.9 is the same as on the 1.7 lpar. thanks again for your advice Rob. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Rob Schramm Sent: Thursday, February 07, 2008 11:07 PM To: [email protected] Subject: Re: I'm back Eileen, I am glad it is working. I am more than a bit skeptical that ICSF was somehow interfering with the startup. If you come across something like it in the future, the other thing I can suggest is turning on some of the debugging for the JVM. If JZOS had ceded control over to the JVM, then it may have been something with the JDK. I know that with Tomcat 5 there was a weird bug with the startup that would only occur occasionally. Ah well.. you are on 1.9 and life is good. As I guy I used to work with would say... "It's a fluke". <vbg> -Rob ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
