Skip to Content
author's profile photo Former Member
0
Former Member

Upgrading OS Win2k3 to SP1, Java engines will not start.

Posted on Nov 17, 2005 at 12:46 PM 15 Views

On a development box that I have is NW04 SPS11 Patch3. It runs fine, no problems to speak of.

My task was to upgrade the OS, Win2k3 to SP1. I searched sdn and notes for issues and problems and found only one, a permission change.

I shut down the WAS and patched the OS. Uneventful. Windows is fine. The dispatcher starts, but the two instances die. They never come up leaving only two lines on the developers trace to go on.

JlaunchIAbortjava: abort hook is called

JlaunchCloseProgram: Good Bye (exit code=-2)

Questions are:

Has anyone patched 2003 server to SP1 and has this happen?

Has anyone done this and it work?

Was there a little known note somewhere that I missed?

Yes, everything is backed up. (I love Ghosts) So I have a day or so to play with this to see what did blew up.

Again, the portal did not change. Windows was just patched to SP1.

This might be a quick 10 points for someone...........

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Nov 18, 2005 at 08:35 AM
    1

    Hello David,

    You can check the other logs in work directory of the J2EE engine for additional error messages. I suppose the server cannot be started with more than 1024M heap but you have to check the logs for confirmation. You also can try to decrease the JVM memory settings of the server note.

    There is a known issue with some Windows patches that cause space fragmentation. This problem is described in note 664607 and http://www.microsoft.com/technet/security/bulletin/MS05-008.mspx

    I hope this will help.

    Best Regards

    Vyara

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member
      Nov 18, 2005 at 01:14 PM

      Going through the dispatch log, there are no errors to say that something is worng. Even the MMC says that it is up and running. As for the two engines, a log file does not even start. The last log entries are from when I shut them down to upgrade to SP1.

      I am going to assign points to you though for responding, I have to image back that portal now to do some work. The next time I try this I will set my log levels higher.

      Oh, also, IIS is fine. Just getting a 503 error, that just tells me the portal engines are not up.

      Thank you again, maybe we can pick this up again at a later date.

    Comment on This Answer

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.