I recently upgraded from AwareIM Developer version 2.0 to Developer 2.2. I used productKey.bat to update the product key. Now JBOSS fails to start. Please advise.
Thanks,
Jason
The following is the JBOSS log:
08:11:14,565 INFO [Server] Starting JBoss (MX MicroKernel)...
08:11:14,565 INFO [Server] Release ID: JBoss [WonderLand] 3.2.8.SP1 (build: CVSTag=JBoss_3_2_8_SP1 date=200603031235)
08:11:14,575 INFO [Server] Home Dir: C:\AwareIM\JBoss
08:11:14,575 INFO [Server] Home URL: file:/C:/AwareIM/bin/../JBoss/
08:11:14,575 INFO [Server] Patch URL: null
08:11:14,575 INFO [Server] Server Name: bas
08:11:14,575 INFO [Server] Server Home Dir: C:\AwareIM\JBoss\server\bas
08:11:14,575 INFO [Server] Server Home URL: file:/C:/AwareIM/JBoss/server/bas/
08:11:14,575 INFO [Server] Server Temp Dir: C:\AwareIM\JBoss\server\bas\tmp
08:11:14,575 INFO [Server] Root Deployment Filename: jboss-service.xml
08:11:17,741 INFO [ServerInfo] Java version: 1.4.2_05,Sun Microsystems Inc.
08:11:17,741 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.2_05-b04,Sun Microsystems Inc.
08:11:17,741 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
08:11:19,134 INFO [Server] Core system initialized
08:11:54,079 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
08:11:56,674 INFO [NamingService] JNDI bootstrap JNP=/0.0.0.0:1099, RMI=/0.0.0.0:1098, backlog=50, no client SocketFactory, Server SocketFactory=class org.jboss.net.sockets.DefaultSocketFactory
08:14:03,571 INFO [RARMetaData] Required license terms present. See deployment descriptor.
08:15:00,567 INFO [RARMetaData] Loading JBoss Resource Adapter for JDBC 2 XA drivers
08:15:00,567 INFO [RARMetaData] Required license terms present. See deployment descriptor.
08:15:10,005 INFO [RARMetaData] Required license terms present. See deployment descriptor.
Problem starting JBOSS.
I had exactly the some problem twice recently.
The first time I don't know what happened exactly but I guess a out of memory error due to some other issue.
The second time I wanted to create a new Minor version from the current productive version of a business space when the configuration tool hang.
I had to kill AwareIM and when trying to restart JBoss didn't work anymore.
I came around this by reinstalling the same version again. Since it was a productive environment I didn't have to time to do any further investigations. But in case anyone is intersted I have a backupcopy.
Hubertus
The first time I don't know what happened exactly but I guess a out of memory error due to some other issue.
The second time I wanted to create a new Minor version from the current productive version of a business space when the configuration tool hang.
I had to kill AwareIM and when trying to restart JBoss didn't work anymore.
I came around this by reinstalling the same version again. Since it was a productive environment I didn't have to time to do any further investigations. But in case anyone is intersted I have a backupcopy.
Hubertus
-
aware_support
- Posts: 7526
- Joined: Sun Apr 24, 2005 12:36 am
- Contact:
The most likely cause of this problem is that if Aware IM is killed or if you upgrade to a new version of Aware IM that includes the new version of JBoss, JBoss leaves certain files hanging and tries to load them when it starts up again. This can take ages and can even run out of memory if there are many files.
The solution is to clear these files before starting Aware IM. The problem is that we haven't been able to track down exactly where JBoss leaves these files - sometimes it is in AwareIM/JBoss/server/bas/temp directory, sometimes in AwareIM/JBoss/server/bas/db directory and sometimes elsewhere.
The cleanest solution is to install evaluation version of Aware IM in a new folder somewhere, then delete the entire AwareIM/JBoss directory from the production machine and copy the entire AwareIM/JBoss directory from the second copy of Aware IM to the production machine - this is what Alan did.
The solution is to clear these files before starting Aware IM. The problem is that we haven't been able to track down exactly where JBoss leaves these files - sometimes it is in AwareIM/JBoss/server/bas/temp directory, sometimes in AwareIM/JBoss/server/bas/db directory and sometimes elsewhere.
The cleanest solution is to install evaluation version of Aware IM in a new folder somewhere, then delete the entire AwareIM/JBoss directory from the production machine and copy the entire AwareIM/JBoss directory from the second copy of Aware IM to the production machine - this is what Alan did.
Aware IM Support Team