JBoss 3.2.3 restarts involuntarily on Windows NT

[erik777]

Can someone please help shed some light on why I may be having deployment problems?

PROBLEM: JBoss restarts every time you try to access an application on Windows NT.

NT and 2000 setup:
JAVA_HOME: $JAVA_INSTALL\j2sdk1.4.0_03
J2EE_HOME: $JAVA_INSTALL\j2sdkee1.3.1

In the process of upgrading an NT box from 3.0.6 to 3.2.3 I got JBoss 3.2.3 completely working on Windows 2000. The out of the box install works on Windows 2000. You can immediately access jmx-console or web-console applications via localhost:8080. I reconfigured it to work with the EAR applications I deployed to it, and it works great on Windows 2000.

To upgrade the NT box, I copied the reconfigured and solidly working copy of JBoss 3.2.3 from Windows 2000 to NT. Every time I tried to access it the application on port 8080, it restarted JBoss, and the web browser reports that it couldn't get a connection. The first line of output on the console is:

[Server] Starting JBoss (MX MicroKernel)...

When I removed the root application, attempts to access it correctly return the HTTP Status 500 from Apache Tomcat/4.1.29, and the JBoss console correctly shows a MAPPING configuration error. However, correct URLs pointing to remaining applications still restarted JBoss.

I decided to try a clean install without any applications, since this worked on Windows 2000. Sure enough, attempts to access jmx-console or web-console, two applications that work out of the box, resulted in the same problem.

The only difference I can discern between the two machines, since they are using the same versions of JBoss and Java, is one is Windows NT and one is Windows 2000.

If I rerun JBoss 3.0.6, it runs without problems. This issue is specific to JBoss 3.2.3.

Some people may be asking why I choose to continue to use Windows NT. The reason is simple. It runs several server programs, and runs them well. If it isn't broken, don't fix it. However, this is the first time it appears to be "broken", although the problem is spefic to an upgrade of JBoss 3.2.3. Does it work on NT on other people's machines?

[erik777]

This is a critical production issue and I need help.

Here's the update... I tried Cygwin. I could swear it worked a couple of times before it finally repeated the same problem with a twist... instead of restarting JBoss, it just outright stops it. No shutdown or nothing. It just ends the run.sh script without any logging or errors. It's also worth noting that startup of JBoss takes 50% longer with Cygwin, not inspiring optimism for production performance.

I've spent two days investigating upgrading the NT box to Linux, but have had nothing but problems getting Postfix and the firewall (iptables) to work correctly. The sad truth is that a free email server from 1998 with an easy to use web front and just about every feature I've desired cannot be easily replaced.

I need a miracle. Production and development are both on hold because of this.

[darranl]

erik,

Have you tried using a slightly later JDK at all, I have some scenarios with JDK 1.4.0 and JBoss where I can cause it to core dump at will which I feel should never happen with a stable JVM suitable for production use.

[erik777]

The Java version shouldn't matter since it is the exact version that works on W2K. To rule it out, though, I upgraded to the latest J2SE (1.4.2_xx) and J2EE. It still did the same thing.

[darranl]

I have never tried using anything to do with Java on Windows NT so I am not sure what else to check.

I am not sure if there is anything you would be able to achieve by configuring log4j to output more information.


I upgraded to the latest J2SE (1.4.2_xx) and J2EE

What do you mean by 'and J2EE'? All you need to provide is a J2SE JDK, anything that is required for J2EE is provided by JBoss.

[juha]

"erik777" wrote:

I need a miracle. Production and development are both on hold because of this.

Miracles are performed here.