[Design of Messaging on JBoss (Messaging/JBoss)] - Re: jms examples in 2.0 Beta1 - jboss-dev-forums

Monday, 8 June 2009

Andy, I got this error message one time with symmetric-clustered example (java 5)

$ ant
Buildfile: build.xml

clean:
   [delete] Deleting directory
/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/build
   [delete] Deleting directory
/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/server0/data
   [delete] Deleting directory
/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/server1/data
   [delete] Deleting directory
/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/server2/data
   [delete] Deleting directory
/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/server3/data
   [delete] Deleting directory
/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/server4/data
   [delete] Deleting directory
/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/server5/data

delete-files:
   [delete] Deleting:
/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/server0/KILL_ME
   [delete] Deleting:
/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/server1/KILL_ME
   [delete] Deleting:
/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/server2/KILL_ME

run:

init:
    [mkdir] Created dir:
/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/build
    [mkdir] Created dir:
/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/build/classes

compile:
     [echo]
src.example.dir=/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/src
    [javac] Compiling 6 source files to
/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/build/classes

runExample:
     [echo] client classpath =
/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-jms-api.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/common/config:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/config:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/build/classes:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/client/jbm-core-client.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/client/jbm-jms-client.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/client/jnp-client.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-transports.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/netty-3.1.0.BETA3.jar
     [java] serverProps = -XX:+UseParallelGC -Xms50M -Xmx100M -XX:+AggressiveOpts
-XX:+UseFastAccessorMethods -Dcom.sun.management.jmxremote
-Djava.util.logging.config.file=/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/common/config/logging.properties
-Dorg.jboss.logging.Logger.pluginClass=org.jboss.messaging.integration.logging.JBMLoggerPlugin
-Djava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
-Djava.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces 
     [java] Jun 8, 2009 5:10:43 PM org.jboss.common.example.JBMExample run
     [java] INFO: jbm.example.runServer is true
     [java] Jun 8, 2009 5:10:43 PM org.jboss.common.example.JBMExample startServer
     [java] INFO: starting server with config 'server3' logServerOutput true
     [java] Jun 8, 2009 5:10:43 PM org.jboss.messaging.core.logging.Logger info
     [java] INFO: command line: java -XX:+UseParallelGC -Xms50M -Xmx100M
-XX:+AggressiveOpts -XX:+UseFastAccessorMethods -Dcom.sun.management.jmxremote
-Djava.util.logging.config.file=/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/common/config/logging.properties
-Dorg.jboss.logging.Logger.pluginClass=org.jboss.messaging.integration.logging.JBMLoggerPlugin
-Djava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
-Djava.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces  -cp
/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-bootstrap.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-core.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-jboss-as-security.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-jms-api.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-jms.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-logging.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-transports.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jboss-mc.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jnpserver.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/netty-3.1.0.BETA3.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/common/config:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/config:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/build/classes:.
-Djava.library.path=-Djava.library.path=/home/howard/apps/jdk1.5.0_16/jre/lib/i386/server:/home/howard/apps/jdk1.5.0_16/jre/lib/i386:/home/howard/apps/jdk1.5.0_16/jre/../lib/i386:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/common/../native/bin
org.jboss.common.example.SpawnedJBMServer jbm-jboss-beans.xml 
     [java] JBMServer err:17:10:44,629 INFO
[org.jboss.messaging.core.server.impl.MessagingServerImpl]  Backup server will await live
server before becoming operational 
     [java] JBMServer err:17:10:44,780 INFO
[org.jboss.messaging.core.server.impl.MessagingServerImpl]  JBoss Messaging Server version
2.0.0.BETA1-SNAPSHOT (tadpole, 102) started 
     [java] Jun 8, 2009 5:10:44 PM org.jboss.common.example.JBMExample startServer
     [java] INFO: starting server with config 'server4' logServerOutput true
     [java] Jun 8, 2009 5:10:44 PM org.jboss.messaging.core.logging.Logger info
     [java] INFO: command line: java -XX:+UseParallelGC -Xms50M -Xmx100M
-XX:+AggressiveOpts -XX:+UseFastAccessorMethods -Dcom.sun.management.jmxremote
-Djava.util.logging.config.file=/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/common/config/logging.properties
-Dorg.jboss.logging.Logger.pluginClass=org.jboss.messaging.integration.logging.JBMLoggerPlugin
-Djava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
-Djava.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces  -cp
/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-bootstrap.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-core.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-jboss-as-security.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-jms-api.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-jms.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-logging.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-transports.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jboss-mc.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jnpserver.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/netty-3.1.0.BETA3.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/common/config:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/config:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/build/classes:.
-Djava.library.path=-Djava.library.path=/home/howard/apps/jdk1.5.0_16/jre/lib/i386/server:/home/howard/apps/jdk1.5.0_16/jre/lib/i386:/home/howard/apps/jdk1.5.0_16/jre/../lib/i386:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/common/../native/bin
org.jboss.common.example.SpawnedJBMServer jbm-jboss-beans.xml 
     [java] JBMServer out:STARTED::
     [java] JBMServer err:17:10:46,437 INFO
[org.jboss.messaging.core.server.impl.MessagingServerImpl]  Backup server will await live
server before becoming operational 
     [java] JBMServer err:17:10:46,640 INFO
[org.jboss.messaging.core.server.impl.MessagingServerImpl]  JBoss Messaging Server version
2.0.0.BETA1-SNAPSHOT (tadpole, 102) started 
     [java] Jun 8, 2009 5:10:46 PM org.jboss.common.example.JBMExample startServer
     [java] INFO: starting server with config 'server5' logServerOutput true
     [java] Jun 8, 2009 5:10:46 PM org.jboss.messaging.core.logging.Logger info
     [java] INFO: command line: java -XX:+UseParallelGC -Xms50M -Xmx100M
-XX:+AggressiveOpts -XX:+UseFastAccessorMethods -Dcom.sun.management.jmxremote
-Djava.util.logging.config.file=/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/common/config/logging.properties
-Dorg.jboss.logging.Logger.pluginClass=org.jboss.messaging.integration.logging.JBMLoggerPlugin
-Djava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
-Djava.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces  -cp
/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-bootstrap.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-core.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-jboss-as-security.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-jms-api.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-jms.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-logging.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-transports.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jboss-mc.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jnpserver.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/netty-3.1.0.BETA3.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/common/config:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/config:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/build/classes:.
-Djava.library.path=-Djava.library.path=/home/howard/apps/jdk1.5.0_16/jre/lib/i386/server:/home/howard/apps/jdk1.5.0_16/jre/lib/i386:/home/howard/apps/jdk1.5.0_16/jre/../lib/i386:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/common/../native/bin
org.jboss.common.example.SpawnedJBMServer jbm-jboss-beans.xml 
     [java] JBMServer out:STARTED::
     [java] JBMServer err:17:10:48,107 INFO
[org.jboss.messaging.core.server.impl.MessagingServerImpl]  Backup server will await live
server before becoming operational 
     [java] JBMServer err:17:10:48,271 INFO
[org.jboss.messaging.core.server.impl.MessagingServerImpl]  JBoss Messaging Server version
2.0.0.BETA1-SNAPSHOT (tadpole, 102) started 
     [java] JBMServer out:STARTED::
     [java] Jun 8, 2009 5:10:48 PM org.jboss.common.example.JBMExample startServer
     [java] INFO: starting server with config 'server0' logServerOutput true
     [java] Jun 8, 2009 5:10:48 PM org.jboss.messaging.core.logging.Logger info
     [java] INFO: command line: java -XX:+UseParallelGC -Xms50M -Xmx100M
-XX:+AggressiveOpts -XX:+UseFastAccessorMethods -Dcom.sun.management.jmxremote
-Djava.util.logging.config.file=/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/common/config/logging.properties
-Dorg.jboss.logging.Logger.pluginClass=org.jboss.messaging.integration.logging.JBMLoggerPlugin
-Djava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
-Djava.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces  -cp
/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-bootstrap.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-core.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-jboss-as-security.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-jms-api.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-jms.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-logging.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-transports.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jboss-mc.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jnpserver.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/netty-3.1.0.BETA3.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/common/config:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/config:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/build/classes:.
-Djava.library.path=-Djava.library.path=/home/howard/apps/jdk1.5.0_16/jre/lib/i386/server:/home/howard/apps/jdk1.5.0_16/jre/lib/i386:/home/howard/apps/jdk1.5.0_16/jre/../lib/i386:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/common/../native/bin
org.jboss.common.example.SpawnedJBMServer jbm-jboss-beans.xml 
     [java] JBMServer err:17:10:49,795 INFO
[org.jboss.messaging.core.persistence.impl.journal.JournalStorageManager]  AIO journal
selected 
     [java] JBMServer err:17:10:49,817 WARNING
[org.jboss.messaging.core.persistence.impl.journal.JournalStorageManager]  AIO wasn't
located on this platform, it will fall back to using pure Java NIO. If your platform is
Linux, install LibAIO to enable the AIO journal 
     [java] JBMServer err:17:10:49,821 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:10:51,951 INFO
[org.jboss.messaging.core.persistence.impl.journal.JournalStorageManager]  AIO journal
selected 
     [java] JBMServer err:17:10:51,954 WARNING
[org.jboss.messaging.core.persistence.impl.journal.JournalStorageManager]  AIO wasn't
located on this platform, it will fall back to using pure Java NIO. If your platform is
Linux, install LibAIO to enable the AIO journal 
     [java] JBMServer err:17:10:51,956 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:10:53,452 INFO
[org.jboss.messaging.core.server.impl.MessagingServerImpl]  Backup server is now
operational 
     [java] JBMServer err:17:10:53,497 INFO
[org.jboss.messaging.core.server.impl.MessagingServerImpl]  JBoss Messaging Server version
2.0.0.BETA1-SNAPSHOT (tadpole, 102) started 
     [java] Jun 8, 2009 5:10:53 PM org.jboss.common.example.JBMExample startServer
     [java] JBMServer out:STARTED::
     [java] INFO: starting server with config 'server1' logServerOutput true
     [java] Jun 8, 2009 5:10:53 PM org.jboss.messaging.core.logging.Logger info
     [java] INFO: command line: java -XX:+UseParallelGC -Xms50M -Xmx100M
-XX:+AggressiveOpts -XX:+UseFastAccessorMethods -Dcom.sun.management.jmxremote
-Djava.util.logging.config.file=/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/common/config/logging.properties
-Dorg.jboss.logging.Logger.pluginClass=org.jboss.messaging.integration.logging.JBMLoggerPlugin
-Djava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
-Djava.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces  -cp
/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-bootstrap.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-core.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-jboss-as-security.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-jms-api.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-jms.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-logging.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-transports.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jboss-mc.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jnpserver.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/netty-3.1.0.BETA3.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/common/config:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/config:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/build/classes:.
-Djava.library.path=-Djava.library.path=/home/howard/apps/jdk1.5.0_16/jre/lib/i386/server:/home/howard/apps/jdk1.5.0_16/jre/lib/i386:/home/howard/apps/jdk1.5.0_16/jre/../lib/i386:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/common/../native/bin
org.jboss.common.example.SpawnedJBMServer jbm-jboss-beans.xml 
     [java] JBMServer err:17:10:53,568 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:10:53,578 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:10:55,456 INFO
[org.jboss.messaging.core.persistence.impl.journal.JournalStorageManager]  AIO journal
selected 
     [java] JBMServer err:17:10:55,478 WARNING
[org.jboss.messaging.core.persistence.impl.journal.JournalStorageManager]  AIO wasn't
located on this platform, it will fall back to using pure Java NIO. If your platform is
Linux, install LibAIO to enable the AIO journal 
     [java] JBMServer err:17:10:55,479 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:10:57,525 INFO
[org.jboss.messaging.core.persistence.impl.journal.JournalStorageManager]  AIO journal
selected 
     [java] JBMServer err:17:10:57,528 WARNING
[org.jboss.messaging.core.persistence.impl.journal.JournalStorageManager]  AIO wasn't
located on this platform, it will fall back to using pure Java NIO. If your platform is
Linux, install LibAIO to enable the AIO journal 
     [java] JBMServer err:17:10:57,530 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:10:58,993 INFO
[org.jboss.messaging.core.server.impl.MessagingServerImpl]  Backup server is now
operational 
     [java] JBMServer err:17:10:59,025 INFO
[org.jboss.messaging.core.server.impl.MessagingServerImpl]  JBoss Messaging Server version
2.0.0.BETA1-SNAPSHOT (tadpole, 102) started 
     [java] Jun 8, 2009 5:10:59 PM org.jboss.common.example.JBMExample startServer
     [java] INFO: starting server with config 'server2' logServerOutput true
     [java] Jun 8, 2009 5:10:59 PM org.jboss.messaging.core.logging.Logger info
     [java] INFO: command line: java -XX:+UseParallelGC -Xms50M -Xmx100M
-XX:+AggressiveOpts -XX:+UseFastAccessorMethods -Dcom.sun.management.jmxremote
-Djava.util.logging.config.file=/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/common/config/logging.properties
-Dorg.jboss.logging.Logger.pluginClass=org.jboss.messaging.integration.logging.JBMLoggerPlugin
-Djava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
-Djava.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces  -cp
/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-bootstrap.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-core.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-jboss-as-security.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-jms-api.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-jms.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-logging.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jbm-transports.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jboss-mc.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/jnpserver.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/lib/netty-3.1.0.BETA3.jar:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/common/config:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/config:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/jms/symmetric-cluster/build/classes:.
-Djava.library.path=-Djava.library.path=/home/howard/apps/jdk1.5.0_16/jre/lib/i386/server:/home/howard/apps/jdk1.5.0_16/jre/lib/i386:/home/howard/apps/jdk1.5.0_16/jre/../lib/i386:/home/howard/apps/messaging-2.0.0.BETA1-SNAPSHOT/examples/common/../native/bin
org.jboss.common.example.SpawnedJBMServer jbm-jboss-beans.xml 
     [java] JBMServer out:STARTED::
     [java] JBMServer err:17:10:59,134 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:10:59,135 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:10:59,204 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:10:59,302 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:10:59,303 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:10:59,303 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:10:59,317 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:10:59,318 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:10:59,321 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:10:59,321 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:10:59,448 WARNING
[org.jboss.messaging.core.server.cluster.impl.ClusterConnectionImpl]  Remoting queue
binding jms.queue.exampleQueue460a3bab-540c-11de-b583-99f8be6715dd has already been bound
in the post office. Most likely cause for this is you have a loop in your cluster due to
cluster max-hops being too large or you have multiple cluster connections to the same
nodes using overlapping addresses 
     [java] JBMServer err:17:10:59,449 WARNING
[org.jboss.messaging.core.server.cluster.impl.ClusterConnectionImpl]  Remote queue binding
jms.queue.exampleQueue460a3bab-540c-11de-b583-99f8be6715dd has already been bound in the
post office. Most likely cause for this is you have a loop in your cluster due to cluster
max-hops being too large or you have multiple cluster connections to the same nodes using
overlapping addresses 
     [java] JBMServer err:17:10:59,450 WARNING
[org.jboss.messaging.core.server.cluster.impl.ClusterConnectionImpl]  Remoting queue
binding jms.topic.exampleTopic460a3bab-540c-11de-b583-99f8be6715dd has already been bound
in the post office. Most likely cause for this is you have a loop in your cluster due to
cluster max-hops being too large or you have multiple cluster connections to the same
nodes using overlapping addresses 
     [java] JBMServer err:17:10:59,455 WARNING
[org.jboss.messaging.core.server.cluster.impl.ClusterConnectionImpl]  Remote queue binding
jms.topic.exampleTopic460a3bab-540c-11de-b583-99f8be6715dd has already been bound in the
post office. Most likely cause for this is you have a loop in your cluster due to cluster
max-hops being too large or you have multiple cluster connections to the same nodes using
overlapping addresses 
     [java] JBMServer err:17:11:00,931 INFO
[org.jboss.messaging.core.persistence.impl.journal.JournalStorageManager]  AIO journal
selected 
     [java] JBMServer err:17:11:00,953 WARNING
[org.jboss.messaging.core.persistence.impl.journal.JournalStorageManager]  AIO wasn't
located on this platform, it will fall back to using pure Java NIO. If your platform is
Linux, install LibAIO to enable the AIO journal 
     [java] JBMServer err:17:11:00,955 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:02,811 INFO
[org.jboss.messaging.core.persistence.impl.journal.JournalStorageManager]  AIO journal
selected 
     [java] JBMServer err:17:11:02,815 WARNING
[org.jboss.messaging.core.persistence.impl.journal.JournalStorageManager]  AIO wasn't
located on this platform, it will fall back to using pure Java NIO. If your platform is
Linux, install LibAIO to enable the AIO journal 
     [java] JBMServer err:17:11:02,816 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:04,349 INFO
[org.jboss.messaging.core.server.impl.MessagingServerImpl]  Backup server is now
operational 
     [java] JBMServer err:17:11:04,400 INFO
[org.jboss.messaging.core.server.impl.MessagingServerImpl]  JBoss Messaging Server version
2.0.0.BETA1-SNAPSHOT (tadpole, 102) started 
     [java] JBMServer out:STARTED::
     [java] JBMServer err:17:11:04,499 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:04,500 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:04,570 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:04,570 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:04,599 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:04,599 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:04,694 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:04,710 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:04,711 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:04,771 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:04,778 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:04,780 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:04,781 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:04,802 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:04,819 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:04,819 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:04,820 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:04,820 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:04,983 WARNING
[org.jboss.messaging.core.server.cluster.impl.ClusterConnectionImpl]  Remoting queue
binding jms.topic.exampleTopic4948ebee-540c-11de-bb74-2da8dbc10427 has already been bound
in the post office. Most likely cause for this is you have a loop in your cluster due to
cluster max-hops being too large or you have multiple cluster connections to the same
nodes using overlapping addresses 
     [java] JBMServer err:17:11:04,984 WARNING
[org.jboss.messaging.core.server.cluster.impl.ClusterConnectionImpl]  Remoting queue
binding jms.queue.exampleQueue4948ebee-540c-11de-bb74-2da8dbc10427 has already been bound
in the post office. Most likely cause for this is you have a loop in your cluster due to
cluster max-hops being too large or you have multiple cluster connections to the same
nodes using overlapping addresses 
     [java] JBMServer err:17:11:04,985 WARNING
[org.jboss.messaging.core.server.cluster.impl.ClusterConnectionImpl]  Remote queue binding
jms.topic.exampleTopic4948ebee-540c-11de-bb74-2da8dbc10427 has already been bound in the
post office. Most likely cause for this is you have a loop in your cluster due to cluster
max-hops being too large or you have multiple cluster connections to the same nodes using
overlapping addresses 
     [java] JBMServer err:17:11:04,985 WARNING
[org.jboss.messaging.core.server.cluster.impl.ClusterConnectionImpl]  Remote queue binding
jms.queue.exampleQueue4948ebee-540c-11de-bb74-2da8dbc10427 has already been bound in the
post office. Most likely cause for this is you have a loop in your cluster due to cluster
max-hops being too large or you have multiple cluster connections to the same nodes using
overlapping addresses 
     [java] JBMServer err:17:11:04,985 WARNING
[org.jboss.messaging.core.server.cluster.impl.ClusterConnectionImpl]  Remoting queue
binding jms.topic.exampleTopic4948ebee-540c-11de-bb74-2da8dbc10427 has already been bound
in the post office. Most likely cause for this is you have a loop in your cluster due to
cluster max-hops being too large or you have multiple cluster connections to the same
nodes using overlapping addresses 
     [java] JBMServer err:17:11:04,986 WARNING
[org.jboss.messaging.core.server.cluster.impl.ClusterConnectionImpl]  Remoting queue
binding jms.queue.exampleQueue4948ebee-540c-11de-bb74-2da8dbc10427 has already been bound
in the post office. Most likely cause for this is you have a loop in your cluster due to
cluster max-hops being too large or you have multiple cluster connections to the same
nodes using overlapping addresses 
     [java] JBMServer err:17:11:04,987 WARNING
[org.jboss.messaging.core.server.cluster.impl.ClusterConnectionImpl]  Remote queue binding
jms.topic.exampleTopic4948ebee-540c-11de-bb74-2da8dbc10427 has already been bound in the
post office. Most likely cause for this is you have a loop in your cluster due to cluster
max-hops being too large or you have multiple cluster connections to the same nodes using
overlapping addresses 
     [java] JBMServer err:17:11:04,987 WARNING
[org.jboss.messaging.core.server.cluster.impl.ClusterConnectionImpl]  Remote queue binding
jms.queue.exampleQueue4948ebee-540c-11de-bb74-2da8dbc10427 has already been bound in the
post office. Most likely cause for this is you have a loop in your cluster due to cluster
max-hops being too large or you have multiple cluster connections to the same nodes using
overlapping addresses 
     [java] JBMServer err:17:11:06,907 WARNING
[org.jboss.messaging.core.server.cluster.impl.ClusterConnectionImpl]  Remoting queue
binding 2da3aaaa-9a1a-47f2-a60a-6918eb768a3c4948ebee-540c-11de-bb74-2da8dbc10427 has
already been bound in the post office. Most likely cause for this is you have a loop in
your cluster due to cluster max-hops being too large or you have multiple cluster
connections to the same nodes using overlapping addresses 
     [java] JBMServer err:17:11:06,909 WARNING
[org.jboss.messaging.core.server.cluster.impl.ClusterConnectionImpl]  Remote queue binding
2da3aaaa-9a1a-47f2-a60a-6918eb768a3c4948ebee-540c-11de-bb74-2da8dbc10427 has already been
bound in the post office. Most likely cause for this is you have a loop in your cluster
due to cluster max-hops being too large or you have multiple cluster connections to the
same nodes using overlapping addresses 
     [java] JBMServer err:17:11:06,912 WARNING
[org.jboss.messaging.core.server.cluster.impl.ClusterConnectionImpl]  Remoting queue
binding 2da3aaaa-9a1a-47f2-a60a-6918eb768a3c4948ebee-540c-11de-bb74-2da8dbc10427 has
already been bound in the post office. Most likely cause for this is you have a loop in
your cluster due to cluster max-hops being too large or you have multiple cluster
connections to the same nodes using overlapping addresses 
     [java] JBMServer err:17:11:06,913 WARNING
[org.jboss.messaging.core.server.cluster.impl.ClusterConnectionImpl]  Remote queue binding
2da3aaaa-9a1a-47f2-a60a-6918eb768a3c4948ebee-540c-11de-bb74-2da8dbc10427 has already been
bound in the post office. Most likely cause for this is you have a loop in your cluster
due to cluster max-hops being too large or you have multiple cluster connections to the
same nodes using overlapping addresses 
     [java] JBMServer err:17:11:06,986 WARNING
[org.jboss.messaging.core.server.cluster.impl.ClusterConnectionImpl]  Remoting queue
binding c349ba39-8b8c-486d-bd75-ef44105994b442ab8108-540c-11de-8fb9-7fafb236eb41 has
already been bound in the post office. Most likely cause for this is you have a loop in
your cluster due to cluster max-hops being too large or you have multiple cluster
connections to the same nodes using overlapping addresses 
     [java] JBMServer err:17:11:06,987 WARNING
[org.jboss.messaging.core.server.cluster.impl.ClusterConnectionImpl]  Remote queue binding
c349ba39-8b8c-486d-bd75-ef44105994b442ab8108-540c-11de-8fb9-7fafb236eb41 has already been
bound in the post office. Most likely cause for this is you have a loop in your cluster
due to cluster max-hops being too large or you have multiple cluster connections to the
same nodes using overlapping addresses 
     [java] JBMServer err:17:11:06,990 WARNING
[org.jboss.messaging.core.server.cluster.impl.ClusterConnectionImpl]  Remoting queue
binding c349ba39-8b8c-486d-bd75-ef44105994b442ab8108-540c-11de-8fb9-7fafb236eb41 has
already been bound in the post office. Most likely cause for this is you have a loop in
your cluster due to cluster max-hops being too large or you have multiple cluster
connections to the same nodes using overlapping addresses 
     [java] JBMServer err:17:11:06,992 WARNING
[org.jboss.messaging.core.server.cluster.impl.ClusterConnectionImpl]  Remote queue binding
c349ba39-8b8c-486d-bd75-ef44105994b442ab8108-540c-11de-8fb9-7fafb236eb41 has already been
bound in the post office. Most likely cause for this is you have a loop in your cluster
due to cluster max-hops being too large or you have multiple cluster connections to the
same nodes using overlapping addresses 
     [java] JBMServer err:17:11:07,034 WARNING
[org.jboss.messaging.core.server.cluster.impl.ClusterConnectionImpl]  Remoting queue
binding 925545cb-b539-4432-9598-04c065ddf801460a3bab-540c-11de-b583-99f8be6715dd has
already been bound in the post office. Most likely cause for this is you have a loop in
your cluster due to cluster max-hops being too large or you have multiple cluster
connections to the same nodes using overlapping addresses 
     [java] JBMServer err:17:11:07,035 WARNING
[org.jboss.messaging.core.server.cluster.impl.ClusterConnectionImpl]  Remote queue binding
925545cb-b539-4432-9598-04c065ddf801460a3bab-540c-11de-b583-99f8be6715dd has already been
bound in the post office. Most likely cause for this is you have a loop in your cluster
due to cluster max-hops being too large or you have multiple cluster connections to the
same nodes using overlapping addresses 
     [java] JBMServer err:17:11:07,041 WARNING
[org.jboss.messaging.core.server.cluster.impl.ClusterConnectionImpl]  Remoting queue
binding 925545cb-b539-4432-9598-04c065ddf801460a3bab-540c-11de-b583-99f8be6715dd has
already been bound in the post office. Most likely cause for this is you have a loop in
your cluster due to cluster max-hops being too large or you have multiple cluster
connections to the same nodes using overlapping addresses 
     [java] JBMServer err:17:11:07,046 WARNING
[org.jboss.messaging.core.server.cluster.impl.ClusterConnectionImpl]  Remote queue binding
925545cb-b539-4432-9598-04c065ddf801460a3bab-540c-11de-b583-99f8be6715dd has already been
bound in the post office. Most likely cause for this is you have a loop in your cluster
due to cluster max-hops being too large or you have multiple cluster connections to the
same nodes using overlapping addresses 
     [java] Killing server 1
     [java] Jun 8, 2009 5:11:10 PM org.jboss.messaging.core.logging.Logger warn
     [java] WARNING: Connection failure has been detected Channel disconnected:2
     [java] JBMServer err:17:11:10,361 WARNING
[org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl]  Connection failure has
been detected Channel disconnected:2 
     [java] JBMServer err:17:11:10,407 WARNING
[org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl]  Connection failure has
been detected Channel disconnected:2 
     [java] JBMServer err:17:11:10,415 WARNING
[org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl]  Connection failure has
been detected Channel disconnected:2 
     [java] JBMServer err:17:11:10,421 WARNING
[org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl]  Connection failure has
been detected Channel disconnected:2 
     [java] JBMServer err:17:11:10,511 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:10,512 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:10,513 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:10,513 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:10,514 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:10,514 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:10,515 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:10,516 WARNING
[org.jboss.messaging.core.security.impl.SecurityStoreImpl]  It has been detected that the
cluster admin password which is used to replicate management operation from one node to
the other has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this. 
     [java] JBMServer err:17:11:15,545 WARNING
[org.jboss.messaging.core.server.cluster.impl.BridgeImpl]  Unable to connect. Bridge is
now disabled. 
     [java] JBMServer err:MessagingException[errorCode=2 message=Unable to connect to
server using configuration
org-jboss-messaging-integration-transports-netty-NettyConnectorFactory?jbm-remoting-netty-port=5446]
     [java] JBMServer err:	at
org.jboss.messaging.core.client.impl.ConnectionManagerImpl.createSession(ConnectionManagerImpl.java:297)
     [java] JBMServer err:	at
org.jboss.messaging.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:962)
     [java] JBMServer err:	at
org.jboss.messaging.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:706)
     [java] JBMServer err:	at
org.jboss.messaging.core.server.cluster.impl.BridgeImpl.createObjects(BridgeImpl.java:571)
     [java] JBMServer err:	at
org.jboss.messaging.core.server.cluster.impl.BridgeImpl.access$1100(BridgeImpl.java:80)
     [java] JBMServer err:	at
org.jboss.messaging.core.server.cluster.impl.BridgeImpl$CreateObjectsRunnable.run(BridgeImpl.java:770)
     [java] JBMServer err:	at
org.jboss.messaging.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:105)
     [java] JBMServer err:	at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
     [java] JBMServer err:	at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
     [java] JBMServer err:	at java.lang.Thread.run(Thread.java:595)
     [java] JBMServer err:17:11:17,437 SEVERE
[org.jboss.messaging.core.management.impl.ManagementServiceImpl]  Failed to call listener

     [java] JBMServer err:java.lang.IllegalStateException: Cannot find queue info for
queue jms.queue.exampleQueue4948ebee-540c-11de-bb74-2da8dbc10427
     [java] JBMServer err:	at
org.jboss.messaging.core.postoffice.impl.PostOfficeImpl.onNotification(PostOfficeImpl.java:387)
     [java] JBMServer err:	at
org.jboss.messaging.core.management.impl.ManagementServiceImpl.sendNotification(ManagementServiceImpl.java:593)
     [java] JBMServer err:	at
org.jboss.messaging.core.server.impl.ServerConsumerImpl.close(ServerConsumerImpl.java:261)
     [java] JBMServer err:	at
org.jboss.messaging.core.server.impl.ServerSessionImpl.doHandleCloseConsumer(ServerSessionImpl.java:1223)
     [java] JBMServer err:	at
org.jboss.messaging.core.server.impl.ServerSessionImpl.handleCloseConsumer(ServerSessionImpl.java:921)
     [java] JBMServer err:	at
org.jboss.messaging.core.server.impl.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:257)
     [java] JBMServer err:	at
org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl$ChannelImpl.handlePacket(RemotingConnectionImpl.java:1553)
     [java] JBMServer err:	at
org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl$ChannelImpl.access$400(RemotingConnectionImpl.java:878)
     [java] JBMServer err:	at
org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:474)
     [java] JBMServer err:	at
org.jboss.messaging.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:556)
     [java] JBMServer err:	at
org.jboss.messaging.integration.transports.netty.MessagingChannelHandler.messageReceived(MessagingChannelHandler.java:75)
     [java] JBMServer err:	at
org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:105)
     [java] JBMServer err:	at
org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:567)
     [java] JBMServer err:	at
org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:803)
     [java] JBMServer err:	at
org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:387)
     [java] JBMServer err:	at
org.jboss.netty.handler.codec.frame.FrameDecoder.fireMessageReceived(FrameDecoder.java:284)
     [java] JBMServer err:	at
org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:261)
     [java] JBMServer err:	at
org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:184)
     [java] JBMServer err:	at
org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:87)
     [java] JBMServer err:	at
org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:567)
     [java] JBMServer err:	at
org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:562)
     [java] JBMServer err:	at
org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:344)
     [java] JBMServer err:	at
org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:331)
     [java] JBMServer err:	at
org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:303)
     [java] JBMServer err:	at
org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:255)
     [java] JBMServer err:	at
org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:176)
     [java] JBMServer err:	at
org.jboss.netty.util.internal.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:72)
     [java] JBMServer err:	at
org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:49)
     [java] JBMServer err:	at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
     [java] JBMServer err:	at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
     [java] JBMServer err:	at java.lang.Thread.run(Thread.java:595)
     [java] JBMServer err:17:11:17,484 SEVERE
[org.jboss.messaging.core.management.impl.ManagementServiceImpl]  Failed to call listener

     [java] JBMServer err:java.lang.IllegalStateException: Cannot find queue info for
queue jms.queue.exampleQueue4948ebee-540c-11de-bb74-2da8dbc10427
     [java] JBMServer err:	at
org.jboss.messaging.core.postoffice.impl.PostOfficeImpl.onNotification(PostOfficeImpl.java:387)
     [java] JBMServer err:	at
org.jboss.messaging.core.management.impl.ManagementServiceImpl.sendNotification(ManagementServiceImpl.java:593)
     [java] JBMServer err:	at
org.jboss.messaging.core.server.impl.ServerConsumerImpl.close(ServerConsumerImpl.java:261)
     [java] JBMServer err:	at
org.jboss.messaging.core.server.impl.ServerSessionImpl.doHandleCloseConsumer(ServerSessionImpl.java:1223)
     [java] JBMServer err:	at
org.jboss.messaging.core.server.impl.ServerSessionImpl.access$2300(ServerSessionImpl.java:109)
     [java] JBMServer err:	at
org.jboss.messaging.core.server.impl.ServerSessionImpl$25.run(ServerSessionImpl.java:949)
     [java] JBMServer err:	at
org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl$ChannelImpl.replicateResponseReceived(RemotingConnectionImpl.java:1439)
     [java] JBMServer err:	at
org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl$ChannelImpl.handlePacket(RemotingConnectionImpl.java:1506)
     [java] JBMServer err:	at
org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl$ChannelImpl.access$400(RemotingConnectionImpl.java:878)
     [java] JBMServer err:	at
org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:474)
     [java] JBMServer err:	at
org.jboss.messaging.core.client.impl.ConnectionManagerImpl$DelegatingBufferHandler.bufferReceived(ConnectionManagerImpl.java:1219)
     [java] JBMServer err:	at
org.jboss.messaging.integration.transports.netty.MessagingChannelHandler.messageReceived(MessagingChannelHandler.java:75)
     [java] JBMServer err:	at
org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:105)
     [java] JBMServer err:	at
org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:567)
     [java] JBMServer err:	at
org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:803)
     [java] JBMServer err:	at
org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:387)
     [java] JBMServer err:	at
org.jboss.netty.handler.codec.frame.FrameDecoder.fireMessageReceived(FrameDecoder.java:284)
     [java] JBMServer err:	at
org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:261)
     [java] JBMServer err:	at
org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:184)
     [java] JBMServer err:	at
org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:87)
     [java] JBMServer err:	at
org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:567)
     [java] JBMServer err:	at
org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:562)
     [java] JBMServer err:	at
org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:344)
     [java] JBMServer err:	at
org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:331)
     [java] JBMServer err:	at
org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:303)
     [java] JBMServer err:	at
org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:255)
     [java] JBMServer err:	at
org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:176)
     [java] JBMServer err:	at
org.jboss.netty.util.internal.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:72)
     [java] JBMServer err:	at
org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:49)
     [java] JBMServer err:	at
org.jboss.messaging.integration.transports.netty.VirtualExecutorService$ChildExecutorRunnable.run(VirtualExecutorService.java:184)
     [java] JBMServer err:	at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
     [java] JBMServer err:	at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
     [java] JBMServer err:	at java.lang.Thread.run(Thread.java:595)
     [java] JBMServer err:17:11:17,505 SEVERE
[org.jboss.messaging.core.management.impl.ManagementServiceImpl]  Failed to call listener

     [java] JBMServer err:java.lang.IllegalStateException: Cannot find queue info for
queue 2da3aaaa-9a1a-47f2-a60a-6918eb768a3c4948ebee-540c-11de-bb74-2da8dbc10427
     [java] JBMServer err:	at
org.jboss.messaging.core.postoffice.impl.PostOfficeImpl.onNotification(PostOfficeImpl.java:387)
     [java] JBMServer err:	at
org.jboss.messaging.core.management.impl.ManagementServiceImpl.sendNotification(ManagementServiceImpl.java:593)
     [java] JBMServer err:	at
org.jboss.messaging.core.server.impl.ServerConsumerImpl.close(ServerConsumerImpl.java:261)
     [java] JBMServer err:	at
org.jboss.messaging.core.server.impl.ServerSessionImpl.doHandleCloseConsumer(ServerSessionImpl.java:1223)
     [java] JBMServer err:	at
org.jboss.messaging.core.server.impl.ServerSessionImpl.handleCloseConsumer(ServerSessionImpl.java:921)
     [java] JBMServer err:	at
org.jboss.messaging.core.server.impl.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:257)
     [java] JBMServer err:	at
org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl$ChannelImpl.handlePacket(RemotingConnectionImpl.java:1553)
     [java] JBMServer err:	at
org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl$ChannelImpl.access$400(RemotingConnectionImpl.java:878)
     [java] JBMServer err:	at
org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:474)
     [java] JBMServer err:	at
org.jboss.messaging.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:556)
     [java] JBMServer err:	at
org.jboss.messaging.integration.transports.netty.MessagingChannelHandler.messageReceived(MessagingChannelHandler.java:75)
     [java] JBMServer err:	at
org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:105)
     [java] JBMServer err:	at
org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:567)
     [java] JBMServer err:	at
org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:803)
     [java] JBMServer err:	at
org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:387)
     [java] JBMServer err:	at
org.jboss.netty.handler.codec.frame.FrameDecoder.fireMessageReceived(FrameDecoder.java:284)
     [java] JBMServer err:	at
org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:261)
     [java] JBMServer err:	at
org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:184)
     [java] JBMServer err:	at
org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:87)
     [java] JBMServer err:	at
org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:567)
     [java] JBMServer err:	at
org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:562)
     [java] JBMServer err:	at
org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:344)
     [java] JBMServer err:	at
org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:331)
     [java] JBMServer err:	at
org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:303)
     [java] JBMServer err:	at
org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:255)
     [java] JBMServer err:	at
org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:176)
     [java] JBMServer err:	at
org.jboss.netty.util.internal.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:72)
     [java] JBMServer err:	at
org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:49)
     [java] JBMServer err:	at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
     [java] JBMServer err:	at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
     [java] JBMServer err:	at java.lang.Thread.run(Thread.java:595)
     [java] JBMServer err:17:11:17,515 SEVERE
[org.jboss.messaging.core.management.impl.ManagementServiceImpl]  Failed to call listener

     [java] JBMServer err:java.lang.IllegalStateException: Cannot find queue info for
queue 2da3aaaa-9a1a-47f2-a60a-6918eb768a3c4948ebee-540c-11de-bb74-2da8dbc10427
     [java] JBMServer err:	at
org.jboss.messaging.core.postoffice.impl.PostOfficeImpl.onNotification(PostOfficeImpl.java:387)
     [java] JBMServer err:	at
org.jboss.messaging.core.management.impl.ManagementServiceImpl.sendNotification(ManagementServiceImpl.java:593)
     [java] JBMServer err:	at
org.jboss.messaging.core.server.impl.ServerConsumerImpl.close(ServerConsumerImpl.java:261)
     [java] JBMServer err:	at
org.jboss.messaging.core.server.impl.ServerSessionImpl.doHandleCloseConsumer(ServerSessionImpl.java:1223)
     [java] JBMServer err:	at
org.jboss.messaging.core.server.impl.ServerSessionImpl.access$2300(ServerSessionImpl.java:109)
     [java] JBMServer err:	at
org.jboss.messaging.core.server.impl.ServerSessionImpl$25.run(ServerSessionImpl.java:949)
     [java] JBMServer err:	at
org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl$ChannelImpl.replicateResponseReceived(RemotingConnectionImpl.java:1439)
     [java] JBMServer err:	at
org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl$ChannelImpl.handlePacket(RemotingConnectionImpl.java:1506)
     [java] JBMServer err:	at
org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl$ChannelImpl.access$400(RemotingConnectionImpl.java:878)
     [java] JBMServer err:	at
org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:474)
     [java] JBMServer err:	at
org.jboss.messaging.core.client.impl.ConnectionManagerImpl$DelegatingBufferHandler.bufferReceived(ConnectionManagerImpl.java:1219)
     [java] JBMServer err:	at
org.jboss.messaging.integration.transports.netty.MessagingChannelHandler.messageReceived(MessagingChannelHandler.java:75)
     [java] JBMServer err:	at
org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:105)
     [java] JBMServer err:	at
org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:567)
     [java] JBMServer err:	at
org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:803)
     [java] JBMServer err:	at
org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:387)
     [java] JBMServer err:	at
org.jboss.netty.handler.codec.frame.FrameDecoder.fireMessageReceived(FrameDecoder.java:284)
     [java] JBMServer err:	at
org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:261)
     [java] JBMServer err:	at
org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:184)
     [java] JBMServer err:	at org.jboss.netty.channel.SimpleChannelUpstreamHandler.h

View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235930#...

Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: jms examples in 2.0 Beta1