1 Reply Latest reply on Feb 10, 2012 1:21 AM by mageshbk

Problem to deploy a simple soa app with Jboss Studio

elcioa Feb 9, 2012 6:46 AM

Hi !

I m trying to deploy a simple SOA app with jboss esb using Jboss Studio. The idea was use the wizzard screens from Jboss Studio to setup an ESB app that read a XML file from same folder and write it on other folder. No transformation on the content is required and I follow the instructions on an article from this link: http://architecture-journal.blogspot.com/2009/09/jboss-soa-platform-solucoes-soa-com.html

I did the listner and actions registration as discribed on the article, using only the wizard screens as proposed on the article. The app should look for the XML file on the folder each 5 seconds, and then copy it to the other folder, but when I started the jboss server (proper ESB 4.1 configured and tested), what I got is only this error message: javax.jms.JMSException: There is no administratively defined queue with name:queue/testQueue I got this error each 5 seconds, so the app is trying to get the file, but something is goinf wrong...

Different from que quickstart samples, the Jboss Studio wizards did not generate a deployment.xml file or a jbm-queue-service.xml file, it only generate the jboss-esb.xml config file that atteched bellow...

Here is the error dump:

09:03:34,911 WARN [MessageAwareListener] Error processing courier, backing off for 32000 milliseconds

09:04:06,912 INFO [MessageAwareListener] State reached : false

09:04:06,925 ERROR [ExceptionUtil] SessionEndpoint[nb-xz2gofyg-1-2lreofyg-22sb6a-x41o4c5] createQueue [xb-1rojofyg-1-2lreofyg-22sb6a-x41o4c5]

javax.jms.JMSException: There is no administratively defined queue with name:queue/testQueue

at org.jboss.jms.server.endpoint.ServerSessionEndpoint.createQueue(ServerSessionEndpoint.java:299)

at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$createQueue$aop(SessionAdvised.java:105)

at org.jboss.jms.server.endpoint.advised.SessionAdvised$createQueue_6431069199924553036.invokeTarget(SessionAdvised$createQueue_6431069199924553036.java)

at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)

at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)

at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)

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:891)

at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)

at org.jboss.remoting.Client.invoke(Client.java:1724)

at org.jboss.remoting.Client.invoke(Client.java:629)

at org.jboss.remoting.Client.invoke(Client.java:617)

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(ClientSessionDelegate.java:319)

at org.jboss.jms.client.delegate.ClientSessionDelegate$createQueue_6431069199924553036.invokeTarget(ClientSessionDelegate$createQueue_6431069199924553036.java)

at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)

at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92)

at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86)

at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)

at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)

at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86)

at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)

at org.jboss.jms.client.delegate.ClientSessionDelegate.createQueue(ClientSessionDelegate.java)

at org.jboss.jms.client.JBossSession.createQueue(JBossSession.java:250)

at org.jboss.internal.soa.esb.rosetta.pooling.WrappedSession.createQueue(WrappedSession.java:294)

at org.jboss.internal.soa.esb.rosetta.pooling.JmsSession.createQueue(JmsSession.java:282)

at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageConsumer(JmsCourier.java:597)

at org.jboss.internal.soa.esb.couriers.JmsCourier.internalPickupPayload(JmsCourier.java:490)

at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:466)

at org.jboss.internal.soa.esb.couriers.JmsCourier.pickup(JmsCourier.java:459)

at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:228)

at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:204)

at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:298)

at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:254)

at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115)

at java.lang.Thread.run(Thread.java:662)

09:04:07,926 WARN [MessageAwareListener] Error processing courier, backing off for 32000 milliseconds

And this is my jboss-esb.xml config file:

<?xml version="1.0"?>

<jbossesb parameterReloadSecs="5"

xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.3.0.xsd"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.3.0.xsd http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.3.0.xsd">

<jms-provider connection-factory="ConnectionFactory" name="JBoss Messaging">

<jms-bus busid="jmsChannel">

<jms-message-filter dest-name="queue/testQueue" dest-type="QUEUE"/>

</jms-bus>

</jms-provider>

<fs-provider name="File Provider">

<fs-bus busid="fsChannel">

<fs-message-filter directory="C:\Workspace\Tools\testFS"

input-suffix="pedidoCompra.xml" post-delete="false"

post-directory="C:\Workspace\Tools\testFSout" post-suffix=".OK"/>

</fs-bus>

</fs-provider>

</providers>

<service category="Proxy Servers"

description="Serviços de Processamento de Pedidos" name="PedidoService">

<jms-listener busidref="jmsChannel" name="jmsListener"/>

<fs-listener busidref="fsChannel" is-gateway="true"

name="fsListener" schedule-frequency="5"/>

</listeners>

</action>

</actions>

</service>

</services>

</jbossesb>

Could some one help me to find out what is happed ???

Thanks to much !

1. Re: Problem to deploy a simple soa app with Jboss Studio

mageshbk Feb 10, 2012 1:21 AM (in response to elcioa)

I beleive you have missed to include the appropriate JMS destinations file along with the deployment. These have been explained in more detail in our JBoss ESB Beginners Guide.
Actions