We have found that Remote Administrator V2.1 tool from Famatech.com can conflict with JBoss 4.0.2 to the point of causing JBoss to shut down. An example of the JBoss log entry that occurs at the time of the shutdown is: 2006-01-11 09:34:50,332 DEBUG [org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread] Notified to shutdown.
The problem occurred on a Windows 2000 Server platform with the "server component" of Remote Administrator V2.1. The JBoss shutdown occurs a short time after a Remote Administrator client connects to the Remote Administrator server from a networked PC. The Remote Administrator server component was using port 4899. Our JBoss was setup on port 8050, but I know JBoss uses a lot of ports. We had removed the JBoss "jmx-console.war" and "management" folders from the deploy directory and still had the shutdown problems. Do know of any use of port 4899 by JBoss 4.0.2, or do you have any other ideas on a possible reason for the conflict? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3917127#3917127 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3917127 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
