[esb-issues] [JBoss JIRA] Updated: (JBESB-845) HSQLDB Problem when starting up second ESB instance

HSQLDB Problem when starting up second ESB instance --------------------------------------------------- Key: JBESB-845 URL: http://jira.jboss.com/jira/browse/JBESB-845 Project: JBoss ESB Issue Type: Bug Security Level: Public(Everyone can see) Components: Deployment, Rosetta Environment: Mac OS X Reporter: Tom Cunningham Assigned To: Kevin Conner Priority: Critical Fix For: 4.2 When starting up a second ESB instance, I see the following error: 12:00:49,049 INFO [STDOUT] [Server@30d644]: Loaded properties from [/Users/tcunning/esb/jboss-4.2.1.GA/bin/server.properties] 12:00:49,050 INFO [STDOUT] [Server@30d644]: Initiating startup sequence... 12:00:49,053 ERROR [STDERR] [Server@30d644]: [Thread[HSQLDB Server @30d644,5,jboss]]: run()/openServerSocket(): 12:00:49,053 ERROR [STDERR] java.net.BindException: Address already in use at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359) at java.net.ServerSocket.bind(ServerSocket.java:319) at java.net.ServerSocket.<init>(ServerSocket.java:185) at org.hsqldb.HsqlSocketFactory.createServerSocket(Unknown Source) at org.hsqldb.Server.openServerSocket(Unknown Source) at org.hsqldb.Server.run(Unknown Source) at org.hsqldb.Server.access$000(Unknown Source) at org.hsqldb.Server$ServerThread.run(Unknown Source) Here's my steps to reproduce : 1) Install ESB on a fresh AS 2) Make a copy of the "default" directory called "second" 3) Edit server/default/conf/jboss-service.xml - change ServerName to ports-default and point StoreURL to wherever you are going to put your sample-bindings.xml file 4) Edit server/second/conf/jboss-service.xml - change ServerName to ports-01 and point StoreURL to wherever you are going to put your sample-bindings.xml file 5) Edit server/second/deploy/jbossesb.sar/esb.juddi.properties - change java.naming.provider.url to look at port 1199 6) Start first server 7) ./run.sh -c second From my understanding, the -b option isn't needed if we're using the port-bindings.