Error in initialization of DLQ

[sidnim]

I am not able to successfully start jboss 4.0.1sp1... as the DLQ is not configured and it gives the following error:

Some excerpts of the error messages:

Failed to connect to localhost:1100
javax.naming.CommunicationException: Failed to connect to server localhost:1100 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1100 [Root exception is java.net.ConnectException: Connection refused: connect]]

11:23:18,909 ERROR [DLQHandler] Initialization failed DLQHandler
javax.jms.JMSException: Error creating the dlq connection: Failed to connect to server 0.0.0.0:1100

11:23:19,144 WARN [JMSContainerInvoker] JMS provider failure detected:
javax.jms.JMSException: Error creating the dlq connection: Failed to connect to server 0.0.0.0:1100

11:23:31,597 ERROR [DLQHandler] Initialization failed DLQHandler
javax.jms.JMSException: Error creating the dlq connection: Failed to connect to server 0.0.0.0:1100

Why is it not able to connect to the port 1100? all the other services start up and run fine without giving out any errors? Then why is just this service not able to start up?

Did a netstat -a and found that there is no service that is listening/waiting on port 1100, so why is it not able to connect? There is are no restrictions/firewalls on my local machine...

Am I missing any configuration settings but where?

Also noticed one more thing; so how is one supposed to configure the DLQ when the config xml files (like jbossmq-service.xml & the related xml files) are missing in the 'all' configuration of jboss4.0.1sp1. And this configuration is just out-of-the-box installation.

thanks

[darranl]

"sidnim" wrote:
Also noticed one more thing; so how is one supposed to configure the DLQ when the config xml files (like jbossmq-service.xml & the related xml files) are missing in the 'all' configuration of jboss4.0.1sp1. And this configuration is just out-of-the-box installation.

The files you are looking for are in 'deploy-hasingleton\jms' which is found in the deploy folder. This is so that JMS will only be deployed on one node in the cluster.

[darranl]

Sorry, I meant to say the 'deploy-hasingleton' folder is in the 'all' folder adjacent to the deploy folder.

[sidnim]

OK i noticed that. So it most probably would pick up the config files from 'deploy-hasingleton' folder...
So do any suggestions on why the JMS Provider is not able to connect to port 1100

[marksigep]

check the hajndi-jms-ds.xml file in ${jboss.home}/server/<server_name>/deploy/jms.

look at the Properties attribute of the jboss.mq:service=JMSProviderLoader,name=HAJNDIJMSProvider mbean.

your Properties attribute probably has java.naming.provider.url=localhost:1100 when it should look like below:


java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
java.naming.provider.url=${jboss.bind.address}:1100