Erro JBoss ESB

vanderlanio:

Pessoal , estou configurando meu web service no Jboss ESB e estou obtendo o erro a seguir :

javax.jms.JMSException: There is no administratively defined queue with name:queue/jmsCalendarioRequestGateway
	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(SessionAdvised.java:105)
	at org.jboss.jms.server.endpoint.advised.SessionAdvised$createQueue_6431069199924553036.invokeNext(SessionAdvised$createQueue_6431069199924553036.java)
	at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)
....

5:51:52,377 WARN  [ServiceController] Problem starting service jboss.esb:deployment=webservice_calendario.esb
org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Unexpected JMS error from prepareMessageReceiver
at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.doInitialise(JmsGatewayListener.java:117)
	at org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.initialise(AbstractManagedLifecycle.java:134)
	at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.initialiseInstances(ManagedLifecycleController.java:105)
	at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.start(ManagedLifecycleController.java:62)

Seggue abaixo meu arquivo jboss-esb.xml

<providers>
		<jms-provider name="JBossMQ" connection-factory="ConnectionFactory"
			jndi-URL="jnp://127.0.0.1:1099" jndi-context-factory="org.jnp.interfaces.NamingContextFactory"
			jndi-pkg-prefix="org.jboss.naming:org.jnp.interfaces">

			<jms-bus busid="servicoCalendarioGwChannel">
				<jms-message-filter dest-type="QUEUE"
					dest-name="queue/jmsCalendarioRequestGateway" />
			</jms-bus>

			<jms-bus busid="servicoCalendarioEsbChannel">
				<jms-message-filter dest-type="QUEUE"
					dest-name="queue/calendarioEsb" />
			</jms-bus>

		</jms-provider>

	</providers>

	<services>
		<service category="MyServiceCategory" name="Webservice_calendario"
			description="Calendario Webservice Consumer">
			<listeners>
				<jms-listener name="jmsESBListener" busidref="servicoCalendarioEsbChannel"
					maxThreads="1" />
				<jms-listener name="jmsGateway" busidref="servicoCalendarioGwChannel"
					maxThreads="1" is-gateway="true" />
			</listeners>

			<actions mep="OneWay">
				<action name="request-mapper"
					class="soa.esb.actions.CalendarioSOARequestAction" />

				<action name="soapui-client-action" class="org.jboss.soa.esb.actions.soap.wise.SOAPClient">
					<property name="wsdl"
						value="http://dominio/calendarioWS?wsdl" />
					<property name="SOAPAction" value="isDiaUtilSessao" />
					<property name="EndPointName" value="CalendarioWSPort" />
				</action>

				<action name="response-mapper"
					class="soa.esb.actions.CalendarioSOAResponseAction" />

			</actions>
		</service>
	</services>

Socorro ! :lol:

Opa foi mals esqueci do arquivo queue-service.xml

Bom agora rodo só que não estou conseguindo chega até a classe de resposta , estou recebendo a seguinte msg :

[ActionProcessingPipeline] No fault address defined for fault message! To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/CalendarioEsb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: b5acfc98-33d6-4860-8b51-8d9f1cf75828 RelatesTo: jms:correlationID#b5acfc98-33d6-4860-8b51-8d9f1cf75828

Consegui pessoal , para quem tiver com problemas vai uma dica eu estava usando a versão jbossesb-server-4.5 , como estava dando muito estouro de memoria e uma
serie de outros problemas , resolvi então troca a versão para jbossesb-server-4.2, com algumas correções consegui colocar meu serviço para rodar