App Server doesn't complete initialization

Message Edited by DELL-AndrewH on 09-15-2003 10:13 AM

No Firewalls install

here is Netstat output

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    superdad:epmap         superdad:0             LISTENING
  TCP    superdad:microsoft-ds  superdad:0             LISTENING
  TCP    superdad:1027          superdad:0             LISTENING
  TCP    superdad:1035          superdad:0             LISTENING
  TCP    superdad:1037          superdad:0             LISTENING
  TCP    superdad:1038          superdad:0             LISTENING
  TCP    superdad:1039          superdad:0             LISTENING
  TCP    superdad:1041          superdad:0             LISTENING
  TCP    superdad:1042          superdad:0             LISTENING
  TCP    superdad:1043          superdad:0             LISTENING
  TCP    superdad:1099          superdad:0             LISTENING
  TCP    superdad:1350          superdad:0             LISTENING
  TCP    superdad:1352          superdad:0             LISTENING
  TCP    superdad:1354          superdad:0             LISTENING
  TCP    superdad:1359          superdad:0             LISTENING
  TCP    superdad:3306          superdad:0             LISTENING
  TCP    superdad:4444          superdad:0             LISTENING
  TCP    superdad:oscssd        superdad:0             LISTENING
  TCP    superdad:8009          superdad:0             LISTENING
  TCP    superdad:8080          superdad:0             LISTENING
  TCP    superdad:8083          superdad:0             LISTENING
  TCP    superdad:netbios-ssn   superdad:0             LISTENING
  TCP    superdad:netbios-ssn   IPAQ:4933              ESTABLISHED
  TCP    superdad:1039          superdad:1037          CLOSE_WAIT
  TCP    superdad:1352          66.77.165.136:http     CLOSE_WAIT
  TCP    superdad:1354          66.77.165.153:http     CLOSE_WAIT
  TCP    superdad:1359          a209-202-96-198.deploy.akamaitechnologies.com:https  CLOSE_WAIT
  TCP    superdad:4331          superdad:3306          TIME_WAIT
  TCP    superdad:4342          superdad:3306          TIME_WAIT
  TCP    superdad:4354          superdad:3306          TIME_WAIT
  TCP    superdad:4365          superdad:3306          TIME_WAIT
  TCP    superdad:oscssd        superdad:1036          CLOSE_WAIT
  UDP    superdad:epmap         *:*                   
  UDP    superdad:microsoft-ds  *:*                   
  UDP    superdad:1029          *:*                   
  UDP    superdad:1031          *:*                   
  UDP    superdad:1034          *:*                   
  UDP    superdad:45566         *:*                   
  UDP    superdad:54321         *:*                   
  UDP    superdad:netbios-ns    *:*                   
  UDP    superdad:netbios-dgm   *:*                   
  UDP    superdad:isakmp        *:*                   
  UDP    superdad:1047          *:*                   
  UDP    superdad:1048          *:*                   
  UDP    superdad:4500          *:*                   

What applications are installed/services are running on this system?

If it's not a straight-up port conflict, such as we initially suspected, we need to know what was installed prior to attempting to load Network Manager.

Installed Microsoft Hotfixes  

DataAccess
    Q318202  (details...)  on 01/26/03
    Q318203  (details...)  on 01/26/03
    Q328797  (details...)  on 04/08/03
    Q329414-26  (details...)  on 01/26/03
    Q823718  (details...)  on 08/22/03
DirectX
    DX819696  (DirectX Update 819696)  
Internet Explorer
    Q324929  (details...)  
    Q330994  (details...)  
    Q810847  (details...)  
    Q813489  (details...)  
    Q813951  (details...)  
    Q818529  (details...)  
    Q822925  (details...)  
    SP1  (SP1)  
MSXML4
    Q317244  (details...)  
Windows 2000
    SP-1
        Q816093  (details...)  on 04/11/03
    SP4
        Q327194  (details...)  on 07/14/03
    SP5
        KB822831  (Windows 2000 Hotfix - KB822831)  on 08/16/03
        KB823559  (Windows 2000 Hotfix - KB823559)  on 07/11/03
        KB823980  (Windows 2000 Hotfix - KB823980)  on 07/17/03
        KB824105  (Windows 2000 Hotfix - KB824105)  on 09/04/03
        KB824146  (Windows 2000 Hotfix - KB824146)  on 09/11/03
        Q818043  (details...)  on 08/16/03
Windows Media Player
    WM320920.1  (details...)  
    WM819639  (details...)
 
Software Versions

321Studio™ - 321Studio™ Version 4.02 *
ACD FotoAngelo 2.0 Version 2, 0, 0, 13 *
ACD Systems, Ltd. - FotoCanvas Version 2, 0, 0, 8 *
ACDSee Version 5, 0, 0, 25 *
AcroTray - Adobe Acrobat Distiller helper application. Version 5, 0, 0, 0 *
Adobe Acrobat Version 5.0.0.0 *
Adobe ImageReady (tm) 7.0 Version 7.0 *
Adobe Photoshop Version 7.0 *
Adobe Premiere Version 6.0 *
Adobe Systems Incorporated. - Acrobat ® Distiller ® for Windows Version 5.0.000 *
Adobe Systems, Inc. Adobe Gamma Loader Version 1, 0, 0, 1 *
Analog Devices, Inc. - DLSLoader Application Version 3, 0, 210, 0 *
Analog Devices, Inc. - SoundMAX Integrated Digital Audio Version 3, 2, 10, 0 *
Analog Devices, Inc. - SoundMAX service agent Version 3, 2, 5, 0 *
Apple Computer, Inc. - QuickTime QuickTime 6.0 *
Application mpeg_encode Version 1, 0, 0, 1 *
ATI Desktop Component Version 6.14.10.4019 *
ATI External Event Utility for WindowsNT and Windows9X Version 6.14.4065 *
ATI Multimedia Center Version 7.5 *
ATI Smart Version 5.13.0004 *
Avery Media Software *
Belarc, Inc. - BelManage Client Version 6.0g *
blindman.exe *
Cinematronics - 3D Pinball Version 5.00.2134.1 *
CMCEI - NewsbinPro Application Version 4, 0, 0, 1 *
Cpqlcd *
CyberLink Corp. - PowerDVD Version 2.50.1307 *
Decoder Configuration *
Dell OpenManage Network Manager *
DivX Player 2.1 *
DivXNetworks, Inc. - DivX Video for Windows Codec Version 5, 0, 3 *
DVDXCopy Application Version 1, 0, 0, 1 *
Eastman Software, Inc., A Kodak Business - Imaging for Windows® Version 5.00.2138.1 *
FlasK CO FlasKMPEG Version 0, 6, 0, 0 *
Gemstar Technology Development Limited - GUIDE PLUS+(TM) for Windows® System Version 1, 1, 0, 18 *
Gemstar Technology Development Ltd. - EPGUpdate Application Version 1, 0, 1, 34 *
GEOCKWIN *
Hewlett-Packard - HP Install Network Printer Wizard Version 3.04.014.0 *
Indigo Rose Corporation - Setup Factory 6.0 Runtime Module Version 6.0.1.1 *
InstallShield unInstaller Version 2.20.926.0 *
Intel(R) Application Accelerator Version 2.2.0.2126 *
Intel(R) Network Configuration Services Version 1.2.26.0 *
Intel(R) Network Configuration Services Version 6.2.35.0 *
Ipswitch, Inc. 81 Hartwell Ave. Lexington, MA 02173 - WS_FTP95 Version 4, 0, 3, 1 *
Java Web Start *
javaw.exe *
Jordan Russell - If you want to undo changes made by Spybot-S&D, use the Recovery instead! *
Macromedia, Inc. - Director 8 Shockwave Studio Version 8.0 *
Micro Logic Corp. - DiskMapper 2 Version 2, 1, 1, 0 *
Microsoft (R) Visual C++ Version 6.0.000 *  Microsoft (R) Visual Studio Version 6.0.000 *
Microsoft (R) Visual Studio Version 6.00.8168.0 *
Microsoft - PDMan98 Version 6.00.8450 *
Microsoft Clip Gallery Version 5.2.01.0405 *
Microsoft Corporation - Dependency Walker Version 1.0 *
Microsoft Corporation - Internet Explorer Version 6.00.2800.1106 *
Microsoft Corporation - OLEViewer Version 2.1 *
Microsoft Corporation - VB 6 API Declaration Loader Version 6.00.8169 *
Microsoft Corporation - Visual Basic Version 6.00.8988 *
Microsoft Corporation - Windows Installer - Unicode Version 2.0.2600.1183 *
Microsoft Corporation - Windows® NetMeeting® Version 3.01 *
Microsoft Object Linking and Embedding Client Test for Windows Version 1.01.000 *
Microsoft Object Linking and Embedding Server Test for Windows Version 1.01.000 *
Microsoft Office 2000 Version 9.0.6926 *
Microsoft Open Database Connectivity Version 3.520.9030.0 *
Microsoft Outlook Version 9.0.6604 *
Microsoft Photo Editor Version 3.01.3 *
Microsoft PowerPoint for Windows Version 9.0.6620 *
Microsoft Visio 2000 Version 6.0 *
Microsoft Windows Media Player Version 6.4.09.1125 *
Microsoft(R) Windows Media Player Version 9.00.00.2980 *
Microsoft® Access Version 9.0.6620 *
Microsoft® Developer Studio Version 6.0.000 *
Microsoft® FrontPage® 2000 Version 4.0.2.6625 *
Microsoft® Internet Services Version 6.1.33.0 *
Microsoft® Query Version 9.00.4430 *
MindVision - Installer VISE 2.8.3 Version 2.8.3 *
MindVision Software - Installer VISE Version 3.1.1 *
Neodio Corp. - Disk Monitor Version 1.5.0819.1 *
Nico Mak Computing, Inc. - WinZip Version 7.0 *
PepiMK Software - SpyBot-S&D Version 1.2 *
Radium MP3 codec configuration tool Version 1.0.0.0 *
Roxio - Disc Copier Application Version 6.1.1.17 *
Roxio - DVD Builder Version 1.1.1.17 *
Roxio - Easy CD Creator Version 6.0.0.171 *
Roxio - Easy CD Creator Version 6.1.1.17 *
Roxio DVD Player Version 6.0.1615.1 *
Roxio Engine Compatibility Wizard Version 6.1.0.7 *
Roxio PhotoSuite Version 5.0.1366.0 *
Roxio, Inc. - AudioCentral Media Manager Version 1.0.100 *
Roxio, Inc. - AudioCentral Version 1.0.98 *
S.A.D. - PowerCDR Express Version 1, 0, 0, 0 *
Server Monitor *
Sharman Networks - Kazaa Media Desktop Version 2, 0, 2, 0 *
SmartRipper *
SunJavaUpdateSched *
System Diagnostic *
Terran Interactive - Cleaner Version 5, 0, 1, 0 *
tslaunch Application Version 1.01 *
VERSANTD * 

Im getting exactly the same message. and symptom.

I have tried installing this on 2 different pc's after downloading it last week. Is it a duff installation?

one pc is our network management pc, and one is a dvdburner with only nero installed.

Regards

Bertie 

We've installed the Network Manager in our lab using the download from the website, so I don't believe there's a problem with the download.

What are the specs for the systems on which you were trying to install Network Manager?  (i.e. processor speed, memory, available HD space, etc.)

Also, were both systems installed with the same OS image, or some other means by which these two systems might be common to one another?

Message Edited by DELL-AndrewH on 09-18-2003 11:54 AM

Hi,

I have had the same problem as the other two posters here.  Same error where the Server doesn't ever initialize.  (Same error in the log.)  I have also tried it on two different systems.  (One was a PIII-800, the other a P4-2.4GHZ)  Both running Windows XP.  No other software installed.  (Other than all the MS patches...)

It's just a hunch, but if embeejay's log says:

(14-Sep-03 1:53:10 PM), stdout: [104] progress.message.client.ENetworkFailure: java.net.ConnectException: Connection refused: connect: 192.168.1.106:2606

and his Netstat output shows nothing listening on that port,

doesn't it follow that the reason that the connection was refused was that there is a problem in the Network Manager software?  (Since JMS is what was requesting access in the first place?)

When you tried to run this on the Windows XP system, was it XP Home, or XP Professional?

We have seen similar issues with Windows XP Home during testing(and thus is why Home isn't a supported OS for Network Manager).

We are currently investigating this issue, and will let you know if we require further information or have any suggestions.

As a side note, I just installed this on a P-III 1Ghz machine with 512 MB of RAM.  After about 10 minutes, the app server was in 'Ready' status.  The download itself appears to be fine.

If possible, could we get a list of the systems on which you've attempted the installation?  I'd like to know manufacturer(if any), OS version, processor speed, and amount of memory.

Message Edited by DELL-AndrewH on 09-18-2003 04:08 PM

Here's my info

Operating System
Windows 2000 Professional Service Pack 4 (build 2195)

Processor
2400 megahertz Intel Pentium 4
8 kilobyte primary memory cache
512 kilobyte secondary memory cache  

Main Circuit Board
Board: ASUSTeK Computer INC. P4PE REV 1.xx
Bus Clock: 133 megahertz
BIOS: Award Software, Inc. ASUS P4PE ACPI BIOS Revision 1001 09/03/2002

Drives  
80.03 Gigabytes Usable Hard Drive Capacity
20.51 Gigabytes Hard Drive Free Space

HL-DT-ST DVDRAM GSA-4040B [CD-ROM drive]
3.5" format removeable media [Floppy drive]

MAXTOR 6L080L4 [Hard drive] (80.05 GB) -- drive 0
USB Storage-CFC [Hard drive] -- drive 2
USB Storage-MMC [Hard drive] -- drive 3
USB Storage-MSC [Hard drive] -- drive 4
USB Storage-SMC [Hard drive] -- drive 1  

Memory Modules
512 Megabytes Installed Memory

Slot 'DIMM 1' has 512 MB
Slot 'DIMM 2' is Empty
Slot 'DIMM 3' is Empty

Local Drive Volumes
    
c: (on drive 0) 80.03 GB 20.51 GB free
 

I have tried it on 3 pc's now

My systems are

Windows nt4 workstation

Windows Xp home

Windows 2000 sp3

All give the same error...

Also, just before the error message complaining it cant connect to port 2606 on the local ip there is a message

CORBA Services disabled in owcorba.properties !

How can we check/enable this? Maybe it is causing the JMS startup failure.

Maybe its the fact that we are trying to put the whole app on one system. Does it work in client server?

Well, for two of the operating systems, Network Manager is not supported:  XP Home and NT 4.0.

Only the following operating systems have been validated for this product:

Windows 2000 Professional, Server, Advanced Server

Windows XP Professional

As I said, we need detailed information to investigate this issue - we've gotten one response thus far, but need more so we can try to find some kind of common ground between these systems.

As for the CORBA message, I received that as well, and the app server still went into ready state, so I believe that's normal.  I will, however, look into the matter once I receive the data we need.

The first system I tried it on used an MSI MS-6315 (Version 5) motherboard, with a Pentium III 800 MHZ processor, 512MB RAM, running Windows 2000 Professional (SP4).  This system was VERY heavily loaded with software, at least two versions of Sun's Java, etc.  The installation hung during the initial database build.  (The system wasn't hung, but the program wasn't doing anything for over an hour...)  I decided to try a different system, since it wasn't suprising that I had trouble here.

The second system was a scratch install of Windows XP Professional on a Soyo P4-ISR motherboard with a P4-2.4GHZ processor, and 512MB RAM.  Other than service packs and updates from MS, this one has nothing else on it.  I tried the installation again today, and the app server is still initializing after about an hour.  The log shows the "connection refused. connect:  IP Address:2606" as reported earlier.

Hope this helps...

Thanks for the information.  We've currently opened this up as an issue with engineering, and will keep folks posted if we need further information or have any leads.

I left the server run overnight, but it still didn't initialize.  Here is the beginning of the log, up to and including the first error report.  (I guess I can't post more than 20,000 characters, so the very beginning of the log isn't there...)  The last error is repeated a billion times.  (Approximately...)

(Sep 19, 2003 1:07:37 PM), stdout: 13:07:37,765 INFO  [PropertyEditorManagerService] Starting
(Sep 19, 2003 1:07:37 PM), stdout: 13:07:37,765 INFO  [PropertyEditorManagerService] Started
(Sep 19, 2003 1:07:37 PM), stdout: 13:07:37,765 INFO  [SystemPropertiesService] Starting
(Sep 19, 2003 1:07:37 PM), stdout: 13:07:37,765 INFO  [SystemPropertiesService] Started
(Sep 19, 2003 1:07:37 PM), stdout: 13:07:37,765 INFO  [Log4jService] Starting
(Sep 19, 2003 1:07:37 PM), stdout: 13:07:37,765 INFO  [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
(Sep 19, 2003 1:07:37 PM), stdout: 13:07:37,765 INFO  [AbstractDeploymentScanner$ScannerThread] Running
(Sep 19, 2003 1:07:38 PM), stdout: 13:07:38,218 INFO  [org.jboss.deployment.MainDeployer] Adding deployer: org.jboss.ejb.EJBDeployer@4520eb
(Sep 19, 2003 1:07:38 PM), stdout: 13:07:38,218 INFO  [org.jboss.deployment.MainDeployer] Adding deployer: org.jboss.deployment.EARDeployer@742700
(Sep 19, 2003 1:07:38 PM), stdout: 13:07:38,296 INFO  [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/Program Files/Dell/OpenManage/Network Manager/oware/jboss-3.0.8/server/oware/deploy/http-invoker.sar/
(Sep 19, 2003 1:07:38 PM), stdout: 13:07:38,328 INFO  [org.jboss.deployment.MainDeployer] deployment waiting for deployer: file:/C:/Program Files/Dell/OpenManage/Network Manager/oware/jboss-3.0.8/server/oware/deploy/http-invoker.sar/invoker.war/
(Sep 19, 2003 1:07:38 PM), stdout: 13:07:38,375 INFO  [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/Program Files/Dell/OpenManage/Network Manager/oware/jboss-3.0.8/server/oware/deploy/http-invoker.sar/
(Sep 19, 2003 1:07:38 PM), stdout: 13:07:38,375 INFO  [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/Program Files/Dell/OpenManage/Network Manager/oware/jboss-3.0.8/server/oware/deploy/jboss-jca.sar
(Sep 19, 2003 1:07:38 PM), stdout: 13:07:38,453 INFO  [org.jboss.deployment.MainDeployer] Adding deployer: org.jboss.resource.RARDeployer@34b07e
(Sep 19, 2003 1:07:38 PM), stdout: 13:07:38,453 INFO  [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/Program Files/Dell/OpenManage/Network Manager/oware/jboss-3.0.8/server/oware/deploy/http-invoker.sar/invoker.war/
(Sep 19, 2003 1:07:38 PM), stdout: 13:07:38,453 INFO  [org.jboss.deployment.MainDeployer] deployment waiting for deployer: file:/C:/Program Files/Dell/OpenManage/Network Manager/oware/jboss-3.0.8/server/oware/deploy/http-invoker.sar/invoker.war/
(Sep 19, 2003 1:07:38 PM), stdout: 13:07:38,453 INFO  [org.jboss.deployment.MainDeployer] Deployment of package: file:/C:/Program Files/Dell/OpenManage/Network Manager/oware/jboss-3.0.8/server/oware/deploy/http-invoker.sar/invoker.war/ is waiting for an appropriate deployer.
(Sep 19, 2003 1:07:38 PM), stdout: 13:07:38,468 INFO  [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/Program Files/Dell/OpenManage/Network Manager/oware/jboss-3.0.8/server/oware/deploy/jboss-jca.sar
(Sep 19, 2003 1:07:38 PM), stdout: 13:07:38,468 INFO  [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/Program Files/Dell/OpenManage/Network Manager/oware/jboss-3.0.8/server/oware/deploy/jbossweb.sar/
(Sep 19, 2003 1:07:39 PM), stdout: 13:07:39,312 INFO  [org.jboss.deployment.MainDeployer] Adding deployer: org.jboss.jetty.JettyService@5ddb6e
(Sep 19, 2003 1:07:39 PM), stdout: 13:07:39,312 INFO  [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/Program Files/Dell/OpenManage/Network Manager/oware/jboss-3.0.8/server/oware/deploy/http-invoker.sar/invoker.war/
(Sep 19, 2003 1:07:40 PM), stdout: 13:07:40,250 INFO  [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/Program Files/Dell/OpenManage/Network Manager/oware/jboss-3.0.8/server/oware/deploy/http-invoker.sar/invoker.war/
(Sep 19, 2003 1:07:40 PM), stdout: 13:07:40,265 INFO  [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/Program Files/Dell/OpenManage/Network Manager/oware/jboss-3.0.8/server/oware/deploy/jbossweb.sar/
(Sep 19, 2003 1:07:40 PM), stdout: 13:07:40,265 INFO  [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/Program Files/Dell/OpenManage/Network Manager/oware/jboss-3.0.8/server/oware/deploy/jmx-ejb-connector-server.sar
(Sep 19, 2003 1:07:40 PM), stdout: 13:07:40,328 INFO  [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/Program Files/Dell/OpenManage/Network Manager/oware/jboss-3.0.8/server/oware/deploy/jmx-ejb-connector-server.sar
(Sep 19, 2003 1:07:40 PM), stdout: 13:07:40,328 INFO  [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/Program Files/Dell/OpenManage/Network Manager/oware/jboss-3.0.8/server/oware/deploy/jmx-invoker-adaptor-server.sar
(Sep 19, 2003 1:07:40 PM), stdout: 13:07:40,390 INFO  [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/Program Files/Dell/OpenManage/Network Manager/oware/jboss-3.0.8/server/oware/deploy/jmx-invoker-adaptor-server.sar
(Sep 19, 2003 1:07:40 PM), stdout: 13:07:40,390 INFO  [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/Program Files/Dell/OpenManage/Network Manager/oware/jboss-3.0.8/server/oware/deploy/jmx-rmi-adaptor.sar/
(Sep 19, 2003 1:07:40 PM), stdout: 13:07:40,437 INFO  [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/Program Files/Dell/OpenManage/Network Manager/oware/jboss-3.0.8/server/oware/deploy/jmx-rmi-adaptor.sar/
(Sep 19, 2003 1:07:40 PM), stdout: 13:07:40,437 INFO  [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/Program Files/Dell/OpenManage/Network Manager/oware/jboss-3.0.8/server/oware/deploy/oware.sar/
(Sep 19, 2003 1:07:53 PM), stdout: 13:07:53,421 INFO  [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/Program Files/Dell/OpenManage/Network Manager/oware/jboss-3.0.8/server/oware/deploy/oware.sar/
(Sep 19, 2003 1:07:53 PM), stdout: 13:07:53,421 INFO  [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/Program Files/Dell/OpenManage/Network Manager/oware/jboss-3.0.8/server/oware/deploy/cluster-service.xml
(Sep 19, 2003 1:07:54 PM), stdout: 13:07:54,156 INFO  [STDOUT]
(Sep 19, 2003 1:07:54 PM), stdout: -------------------------------------------------------
(Sep 19, 2003 1:07:54 PM), stdout: GMS: address is 192.168.2.124:1137
(Sep 19, 2003 1:07:54 PM), stdout: -------------------------------------------------------
(Sep 19, 2003 1:08:02 PM), stdout: 13:08:02,218 WARN  [com.dorado.mbeans.OWClusterPeerActiveImpl] Found no other cluster members when verifying First Primary Server
(Sep 19, 2003 1:08:08 PM), stdout: 13:08:08,171 INFO  [STDOUT] CORBA Services disabled in owcorba.properties !
(Sep 19, 2003 1:11:53 PM), stdout: 13:11:53,468 WARN  [com.dorado.mbeans.OWJMSStartupMBean] Likely JMS startup failure, exception message follows:
(Sep 19, 2003 1:11:53 PM), stdout: [104] progress.message.client.ENetworkFailure: java.net.ConnectException: Connection refused: connect: 192.168.2.124:2606
(Sep 19, 2003 1:11:53 PM), stdout:  at progress.message.zclient.Connection.lMB_(:718)
(Sep 19, 2003 1:11:53 PM), stdout:  at progress.message.zclient.Connection.connect(:454)
(Sep 19, 2003 1:11:53 PM), stdout:  at progress.message.tools.BrokerManager.connect(:231)
(Sep 19, 2003 1:11:53 PM), stdout:  at com.dorado.mbeans.OWJMSStartupMBean.testIfUp(OWJMSStartupMBean.java:302)
(Sep 19, 2003 1:11:53 PM), stdout:  at com.dorado.mbeans.OWJMSStartupMBean.startService(OWJMSStartupMBean.java:100)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:165)
(Sep 19, 2003 1:11:53 PM), stdout:  at java.lang.reflect.Method.invoke(Native Method)
(Sep 19, 2003 1:11:53 PM), stdout:  at com.dorado.mbeans.OWMBeanBase.invoke(OWMBeanBase.java:318)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:1003)
(Sep 19, 2003 1:11:53 PM), stdout:  at $Proxy5.start(Unknown Source)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.system.ServiceController.start(ServiceController.java:413)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.system.ServiceController.start(ServiceController.java:433)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.system.ServiceController.start(ServiceController.java:433)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.system.ServiceController.start(ServiceController.java:433)
(Sep 19, 2003 1:11:53 PM), stdout:  at java.lang.reflect.Method.invoke(Native Method)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
(Sep 19, 2003 1:11:53 PM), stdout:  at $Proxy2.start(Unknown Source)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.deployment.SARDeployer.start(SARDeployer.java:232)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.deployment.MainDeployer.start(MainDeployer.java:814)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:627)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591)
(Sep 19, 2003 1:11:53 PM), stdout:  at java.lang.reflect.Method.invoke(Native Method)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
(Sep 19, 2003 1:11:53 PM), stdout:  at $Proxy3.deploy(Unknown Source)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:435)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymentScanner.java:656)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:507)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:266)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:165)
(Sep 19, 2003 1:11:53 PM), stdout:  at java.lang.reflect.Method.invoke(Native Method)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:1003)
(Sep 19, 2003 1:11:53 PM), stdout:  at $Proxy0.start(Unknown Source)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.system.ServiceController.start(ServiceController.java:413)
(Sep 19, 2003 1:11:53 PM), stdout:  at java.lang.reflect.Method.invoke(Native Method)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
(Sep 19, 2003 1:11:53 PM), stdout:  at $Proxy2.start(Unknown Source)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.deployment.SARDeployer.start(SARDeployer.java:232)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.deployment.MainDeployer.start(MainDeployer.java:814)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:627)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:575)
(Sep 19, 2003 1:11:53 PM), stdout:  at java.lang.reflect.Method.invoke(Native Method)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.Main.boot(Main.java:148)
(Sep 19, 2003 1:11:53 PM), stdout:  at org.jboss.Main$1.run(Main.java:381)
(Sep 19, 2003 1:11:53 PM), stdout:  at java.lang.Thread.run(Thread.java:484)
.

.

.