These are the ports I know about. It looks like the each one of these services has to either have the port settings modified or to use an optional attribute line bindAddress or serverAddress to change the IP used.
8080 - default Jetty HTTP port. The default port can be changed using: -Djetty.port=80. The following ports are used for the specified optional service: 1099 - default JBoss Naming Service listener. 1100 - default JBoss HA Naming Service. 1102 - default JBoss HA Naming Service Automated Discovery. 1476 - default JBoss HSQLDB Listener. 3528 - default JBoss IIOP Listener. 4444 - default JBoss RMI Object Listener. 8009 - default JBoss AJP13 Listener. 8083 - default JBoss Web Server. 8443 - default Jetty HTTPS Listener. 8090 - default JBossMQ OIL Listener. 8091 - default JBossMQ UIL Listener. HTH, Fred -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of John Barnes Sent: Wednesday, January 08, 2003 4:03 PM To: [EMAIL PROTECTED] Subject: [JBoss-dev] Multiple JBoss/Jetty Instances - BindException: Address already in use I have been unable to get a second instance of JBoss running on my Solaris Server. I'm using JBoss 3.0.4 and Jetty for the HTTP/Servlet engine. Based on what I've read on the Jboss forum's I have tried to do the following: I've changed the ports defined in {JBOSS_2_DIR}/server/default/conf/jboss-service.xml & {JBOOS_2_DIR}/server/default/deploy/jbossweb.sar/META-INF/jboss-service.xml However upon startup I still get a message regarding a BindException: mbeans: , org.jboss.deployment.DeploymentInfo@538b6dbd { url=file:/export/home/agentis1/jboss_qa/jboss-3.0.4/server/default/deploy/jb oss-ser vice.xml } deployer: org.jboss.deployment.SARDeployer@a786c3 status: Deployment FAILED reason: Trying to install an already registered mbean: jboss:type=Service,name=BootstrapEditors state: FAILED watch: file:/export/home/agentis1/jboss_qa/jboss-3.0.4/server/default/deploy/jboss- service.xml lastDeployed: 1042059465556 lastModified: 1042059465000 mbeans: , org.jboss.deployment.DeploymentInfo@ef747d17 { url=file:/export/home/agentis1/jboss_qa/jboss-3.0.4/server/default/deploy/jm x-conso le.war/ } deployer: null status: null state: INIT_WAITING_DEPLOYER watch: file:/export/home/agentis1/jboss_qa/jboss-3.0.4/server/default/deploy/jmx-co nsole.war/ lastDeployed: 1042059467654 lastModified: 1036282165000 mbeans: , org.jboss.deployment.DeploymentInfo@525ca96c { url=file:/export/home/agentis1/jboss_qa/jboss-3.0.4/server/default/deploy/Se ction8S ervices.war } deployer: null status: null state: INIT_WAITING_DEPLOYER watch: file:/export/home/agentis1/jboss_qa/jboss-3.0.4/server/default/deploy/Sectio n8Services.war lastDeployed: 1042059467866 lastModified: 1042059467000 mbeans: ]MBeans waiting for classes: <none> MBeans waiting for other MBeans: [ObjectName: jboss.mq:service=InvocationLayer,type=OIL state: FAILED I Depend On: jboss.mq:service=Invoker Depends On Me: java.net.BindException: Address already in use, ObjectName: jboss.mq:service=InvocationLayer,type=UIL state: FAILED I Depend On: jboss.mq:service=Invoker Depends On Me: java.net.BindException: Address already in use] 14:58:07,090 INFO [URLDeploymentScanner] Started 14:58:07,090 INFO [MainDeployer] Deployed package: file:/export/home/agentis1/jboss_qa/jboss-3.0.4/server/default/conf/jboss-se rvic e.xml 14:58:07,094 INFO [Server] JBoss (MX MicroKernel) [3.0.4 Date:200211021607] Started in 0m:32s:745ms Any ideas, I've tried all I can think of. Thanks in advance, John Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
