Quickstart-FTP_Action- Error when modify the 'Q' name

[iamnew2jboss]

Hello Friends,

I could successfully run the FTP_Action quickstart. However, when I modified the "dest-name="queue/quickstart_helloworld_ftp_esb" to "dest-name="queue/quickstart_helloworld_ftp_esb1", received following error on the server prompt. The app seemed to work fine inspite of the error.

javax.jms.JMSException: There is no administratively defined queue with name:queue/quickstart_helloworld_ftp_esb
 at org.jboss.jms.server.endpoint.ServerSessionEndpoint.createQueue(ServerSessionEndpoint.java:289)
 at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$createQueue$aop(Sessio
Advised.java:105)
 at org.jboss.jms.server.endpoint.advised.SessionAdvised$createQueue_6431069199924553036.invokeNext(SessionAdvised$createQueue_64310
9199924553036.java)
 at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)
 at org.jboss.jms.server.endpoint.advised.SessionAdvised$createQueue_6431069199924553036.invokeNext(SessionAdvised$createQueue_64310

Does anybody know why am I getting this error? What's the solution?

Thanks for your help.

[beve]

Hi,

if you want to change the queue name you must change the name in the queue definition file, which is jbm-queue-service.xml if you are using JBoss Messaging and jbmq-queue-service.xml in you are using JBossMQ. Then change queue name in jboss-esb.xml.
Also, the queue is set as a dependency in the file deployment.xml, so you'll need to update that file too.

Regards,

/Daniel

[kconner]

Stale EPRs would be my guess, especially if you have not closed down cleanly.

Try setting the org.jboss.soa.esb.failure.detect.removeDeadEPR property to true within the "core" section. This will cause any stale EPRs to be removed as they are encountered.

The other thing to check would be that you have actually deployed the modified jboss-esb.xml file as this is the place that specifies which queue is used by the client code in the gateway.

[iamnew2jboss]

Thank you both!

Beve, yes, i made sure that I've modified all the corresponding config files for the queue name.

Also, added the property in "jbossesb-properties.xml" as per Kevin's suggestion. The error persists! However, I can see the results successfully.

Here is the error:

13:51:12,265 ERROR [ExceptionUtil] SessionEndpoint[c3-a4uiewhf-1-18pgewhf-au2ow7-y1n404a] createQueue [d3-p4uiewhf-1-18pgewhf-au2ow7-y1n404
]
javax.jms.JMSException: There is no administratively defined queue with name:queue/quickstart_helloworld_ftp_esb
 at org.jboss.jms.server.endpoint.ServerSessionEndpoint.createQueue(ServerSessionEndpoint.java:289)
 at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$createQueue$aop(Sessio
Advised.java:105)
 at org.jboss.jms.server.endpoint.advised.SessionAdvised$createQueue_6431069199924553036.invokeNext(SessionAdvised$createQueue_64310
9199924553036.java)
 at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)
 at org.jboss.jms.server.endpoint.advised.SessionAdvised$createQueue_6431069199924553036.invokeNext(SessionAdvised$createQueue_64310
9199924553036.java)
 at org.jboss.jms.server.endpoint.advised.SessionAdvised.createQueue(SessionAdvised.java)
 at org.jboss.jms.wireformat.SessionCreateQueueRequest.serverInvoke(SessionCreateQueueRequest.java:74)
 at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
 at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:795)
 at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:101)
 at org.jboss.remoting.Client.invoke(Client.java:1634)
 at org.jboss.remoting.Client.invoke(Client.java:548)
 at org.jboss.remoting.Client.invoke(Client.java:536)
 at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189)
 at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:160)
 at org.jboss.jms.client.delegate.ClientSessionDelegate.org$jboss$jms$client$delegate$ClientSessionDelegate$createQueue$aop(ClientSe
sionDelegate.java:297)
 at org.jboss.jms.client.delegate.ClientSessionDelegate$createQueue_6431069199924553036.invokeNext(ClientSessionDelegate$createQueue
6431069199924553036.java)
 at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92)
 at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)

Any other reason(s) I'm getting this?
Thanks.

[kconner]

You will see the error the first time the EPR is used but this failure should result in the EPR being removed from the registry.

Do you still see it if you rerun the test?