[olug] JBoss port conflicts - how to resolve them?

[Eric P]

*slaps forehead*  Doh!  I had a stand alone instance of Tomcat running that I forgot all about.  Of course that is what
was taking port 8009 from JBoss' own included Tomcat service.  All is working now.

Thanks for the info all the same.  I'm just getting up to speed on JBoss, so it's good info to know.

Eric P



Kevin wrote:
> Are you trying to run a second instance of JBoss on your machine? If
> you are, then you'll run into more than one port conflict. Best way to
> resolve that would be to add a second IP to your machine(eth0:1,
> eth0:2, eth0:3, etc) and tell JBoss to listen on the second IP.
> 
> If this is the only instance of JBoss on your machine, then you could
> change just the one port in the bindings file. `grep "StoreURL"
> jboss/server/jboss-service/conf/jboss-service.xml` will show where
> that is.
> 
> On Wed, Aug 13, 2008 at 6:22 PM, Eric P <eric.maillist at gmail.com> wrote:
>> Hi,
>>
>> I'm trying to run JBoss on my local machine, but I'm running into a port conflict.  In particular, port 8009 is already
>> in use which is needed by some JBoss service (AJP to be exact).
>>
>> So I try (btw. i'm no netstat guru):
>> $ netstat -a |grep 8009
>> tcp6       0      0 [::]:8009               [::]:*                  LISTEN
>>
>>
>> Is that something I can mess with?
>>
>> Thanks for reading,
>> Eric P