App Server doesn't complete initialization

Hi there,

I have the same problem: APPServer keeps in initializing mode. Tried adjusting the .cmd-file: no result.

Last log-line is :

Dec 31, 2003 9:02:56 AM), stdout:  at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
(Dec 31, 2003 9:02:56 AM), stdout:  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
(Dec 31, 2003 9:02:56 AM), stdout:  at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324)
(Dec 31, 2003 9:02:56 AM), stdout:  at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
(Dec 31, 2003 9:02:56 AM), stdout:  at org.jboss.Main.boot(Main.java:148)
(Dec 31, 2003 9:02:56 AM), stdout:  at org.jboss.Main$1.run(Main.java:381)
(Dec 31, 2003 9:02:56 AM), stdout:  at java.lang.Thread.run(Thread.java:484)
(Dec 31, 2003 9:02:56 AM), stdout:

When i try to start the manager-app, I can login, but when I change my password, I get another error message, like in one of the previous message.

App is installed on a PE2550, W2000 server SP4, 2 NIC's, 1 disabled/not connected.

I will try to put the NIC out in BIOS, en let you know my findings.

OK Guys :

I removed the OM-Network thing. Rebooted the server, turned 2nd NIC off in BIOS. Removed NIC from Windows. reboot. Reinstall OM-network thing.

Adjusted the cmd-file as suggested.

However: no result. APPServer still keeps initializing.

I'd like to point out that the full appserver log is available in:

{$WHEREVER_YOU_INSTALLED}/oware/jboss-3.0.8/server/oware/log/server.log

and the jms log (and it's jms that it failing to start) is located at:

{$WHEREVER_YOU_INSTALLED}/oware/temp/sonicmq_appserver.log

The appserver.log, which is available via the tray icon is quite abbreviated.

Depending on what version of the software you are running, you may also have a:

{$WHEREVER_YOU_INSTALLED}/oware/bin/getlogs.cmd which grabs a whole

bunch of logs and jars them up.  These are quite handy.  It would be extremely

helpful if this info would be added to a FAQ.

Once you take a look at the jms log, you'll have a much better idea of what the problem is.

If you see something about a line being too long, it is most likely due to the length of an

existing path or classpath.  I'm not sure what version you may be running, but generally it's

a good idea to eliminate unneeded path entries and make sure paths with spaces in them

are quoted.

Some issues which may be related to this problem:

The software does not currently support dual NICs.  While we will support it in the future,

currently, it causes many problems.  My testing indicates that if you have one of the

NICs disabled, you should be fine in that regard, but if you have two enabled NICs, it's not 

going to work.

Also, multiple cygwin installations are not supported.  Sorry, folks, but I suggest you talk to the

cygwin people about this, because they use registry entries for mount points (I'm still wondering

why) and it isn't possible to share there with another installation.  I've tried.  They even address

this on their site.