-
1. Re: [JBossWeb] Failed to startConnectors
akazakov Jun 21, 2011 1:33 PM (in response to kike_skater)It's exactly what the exception says: Address already in use: JVM_Bind:8009
You seem to try to start JBoss AS when you already have another running.
-
2. Re: [JBossWeb] Failed to startConnectors
kike_skater Jun 21, 2011 2:21 PM (in response to akazakov)Hi Alexey..
I did netstat on my cmd - and appears that the port 8009 is listening .. http://tinypic.com/r/2rfzrix/7 ; http://tinypic.com/r/2rfzrix/7
Now .. in my jboss configuration script there appear 2 ports 8080 and 8009 .. This is ok?? The port that is give me problem is 8009.
This is part of the script of C:\Jboss\server\default\deploy\jboss-web.deployer\server
<code>
<Connector port="8080" address="${jboss.bind.address}"
maxThreads="250" maxHttpHeaderSize="8192"
emptySessionPath="true" protocol="HTTP/1.1"
enableLookups="false" redirectPort="8443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true" />
<code>
<code>
<Connector port="8009" address="${jboss.bind.address}" protocol="AJP/1.3"
emptySessionPath="true" enableLookups="false" redirectPort="8443" />
<Engine name="jboss.web" defaultHost="localhost">
<code>
-
3. Re: [JBossWeb] Failed to startConnectors
akazakov Jun 21, 2011 2:35 PM (in response to kike_skater)Port 8080 is used for HTTP connections by default. Port 8009 is used for AJP connections (needed for communication between JBoss AS and Apache). So just change this port number to any available one.
-
4. Re: [JBossWeb] Failed to startConnectors
kike_skater Jun 21, 2011 4:13 PM (in response to akazakov)I just change the port 8009 for 8081 and I recive this error
<code>
14:50:31,989 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
14:50:32,007 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
14:50:32,009 INFO [RAMJobStore] RAMJobStore initialized.
14:50:32,010 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
14:50:32,010 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
14:50:32,010 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
14:50:32,422 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
14:50:32,620 INFO [A] Bound to JNDI name: queue/A
14:50:32,622 INFO [B] Bound to JNDI name: queue/B
14:50:32,623 INFO [C] Bound to JNDI name: queue/C
14:50:32,625 INFO [D] Bound to JNDI name: queue/D
14:50:32,626 INFO [ex] Bound to JNDI name: queue/ex
14:50:32,640 INFO [testTopic] Bound to JNDI name: topic/testTopic
14:50:32,642 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
14:50:32,643 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
14:50:32,646 INFO [testQueue] Bound to JNDI name: queue/testQueue
14:50:32,676 INFO [UILServerILService] JBossMQ UIL service available at : localhost/127.0.0.1:8093
14:50:32,700 INFO [DLQ] Bound to JNDI name: queue/DLQ
14:50:32,787 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
14:50:32,808 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
14:50:32,954 INFO [Http11Protocol] Arrancando Coyote HTTP/1.1 en puerto http-localhost%2F127.0.0.1-8080
14:50:32,981 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8081
14:50:33,005 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)] Started in 10s:988ms
15:07:11,609 ERROR [AjpMessage] Invalid message recieved with signature 18245
<code>