1 Reply Latest reply on Jan 31, 2006 1:58 PM by jlsimpson

    Conflict With Remote Administrator Tool


      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?

        • 1. Re: Conflict With Remote Administrator Tool

          Last night we solved the Remote Admin / JBoss conflict we had been experiencing.

          The root of the problem was found to be the method used to start JBoss as a service. Prior to last night, we had used a 3rd party product called ServiceMill. Last night we switched to use the Run As Service tool that is provided by JBoss. That made the difference. Remote Admin is now able to be used on the server platform without interfering with JBoss.