Yesterday, a colleague of mine had an issue with their test WebSphere Process Server contained inside of WebSphere Integration Developer. It was a very peculiar issue. The server would just hang in the middle of starting various EARs. We tried to start the server outside of WID and still could not get the server back it’s hang point.

I recommended that we clean out the WSTEMP directory of the profile in question. We then started the server and actually got a window popup from the JVM informing us that an illegal operation occured.

I then recommeded that we reboot the machine in question. We started the server and everything was good.

So, I don’t really have an answer as to what happened other than trying to clean out that unruly WSTemp directory and restarting your machine if you see JVM crashes. In my experience JVM crashes are usually attributed to a corrupted operating system and not usually a corrupted server.

If the reboot didn’t work, I was going to recommend profile re-creation.

Related Posts

• IBM TechNote: Content and maintenance of the wstemp directory for WebSphere Process Server V6
• Problem Determination and WebSphere Integration Developer
• Tip: WebSphere Process Server - Do not delete the ‘tranlog’ on a production server
• WebSphere Process Server Discussions
• The lack of a non-IBM WebSphere Community

You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.