3 Replies Latest reply on Jun 5, 2008 11:30 AM by tfennelly

webservice_producer sample..

fil78 Jun 5, 2008 9:19 AM

Hi,

I am trying to understand this sample - client side is quite simple, but the question is about jboss-esb.xml. I could not find any information about jbr-providers - as I understand from the quickstart - there is no need configure it somewhere, but when I try to implement - there is deployement exception:

17:11:47,332 INFO [TomcatDeployer] undeploy, ctxPath=/HRtoCFesbTrigger, warUrl=.../tmp/deploy/tmp27670HRtoCFesbTrigger.esb-contents/HRtoCFesbTrigger-exp.war/
17:11:47,364 INFO [request_esb] Unbinding JNDI name: queue/request_esb
17:11:47,379 INFO [DefaultEndpointRegistry] remove: jboss.ws:context=HRtoCFesbTrigger,endpoint=ESBTriggerWS
17:11:47,832 INFO [DefaultEndpointRegistry] register: jboss.ws:context=HRtoCFesbTrigger,endpoint=ESBTriggerWS
17:11:47,942 INFO [JBoss4ESBDeployer] create esb service, HRtoCFesbTrigger.esb
17:11:48,145 INFO [request_esb] Bound to JNDI name: queue/request_esb
17:11:48,473 WARN [ServiceController] Problem starting service jboss.esb:deployment=HRtoCFesbTrigger.esb
java.lang.RuntimeException: org.jboss.soa.esb.ConfigurationException: Service configuration for Service 'HRtoCFCategory:WSProducerService' doesn't define a Message-Aware Listener (i.e. is-gateway='false').
 at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration.java:132)
 at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startService(JBoss4ESBDeployment.java:82)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
 at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
 at $Proxy0.start(Unknown Source)
 at org.jboss.system.ServiceController.start(ServiceController.java:417)
 at org.jboss.system.ServiceController.start(ServiceController.java:435)
 at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
 at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
 at $Proxy4.start(Unknown Source)
 at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
 at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
 at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
 at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
 at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
 at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
 at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
 at $Proxy9.deploy(Unknown Source)
 at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
 at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610)
 at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
 at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
 at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
Caused by: org.jboss.soa.esb.ConfigurationException: Service configuration for Service 'HRtoCFCategory:WSProducerService' doesn't define a Message-Aware Listener (i.e. is-gateway='false').
 at org.jboss.soa.esb.listeners.config.Generator$XMLBeansModel.getListeners(Generator.java:392)
 at org.jboss.soa.esb.listeners.config.Generator$XMLBeansModel.getESBAwareListeners(Generator.java:262)
 at org.jboss.soa.esb.listeners.config.ESBAwareGenerator.generate(ESBAwareGenerator.java:92)
 at org.jboss.soa.esb.listeners.config.Generator.generate(Generator.java:148)
 at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration.java:98)
 ... 49 more
17:11:48,660 INFO [TomcatDeployer] deploy, ctxPath=/HRtoCFesbTrigger, warUrl=.../tmp/deploy/tmp27673HRtoCFesbTrigger.esb-contents/HRtoCFesbTrigger-exp.war/
17:11:52,878 INFO [WSDLFilePublisher] WSDL published to: file:/C:/jboss-4.2.2.GA/server/default/data/wsdl/HRtoCFesbTrigger.esb/HRtoCFesbTrigger.war/TestESBWebServiceService27674.wsdl
17:11:53,127 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- MBeans waiting for other MBeans ---
ObjectName: jboss.esb:deployment=HRtoCFesbTrigger.esb
 State: FAILED
 Reason: java.lang.RuntimeException: org.jboss.soa.esb.ConfigurationException: Service configuration for Service 'HRtoCFCategory:WSProducerService' doesn't define a Message-Aware Listener (i.e. is-gateway='false').
 I Depend On:
 jboss.esb:deployment=jbpm.esb
 jboss.esb.destination:service=Queue,name=request_esb
 jboss.esb:deployment=jbossesb.esb
 jboss.esb:deployment=soap.esb

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.esb:deployment=HRtoCFesbTrigger.esb
 State: FAILED
 Reason: java.lang.RuntimeException: org.jboss.soa.esb.ConfigurationException: Service configuration for Service 'HRtoCFCategory:WSProducerService' doesn't define a Message-Aware Listener (i.e. is-gateway='false').
 I Depend On:
 jboss.esb:deployment=jbpm.esb
 jboss.esb.destination:service=Queue,name=request_esb
 jboss.esb:deployment=jbossesb.esb
 jboss.esb:deployment=soap.esb

here is my jboss-esb.xml:

<?xml version = "1.0" encoding = "UTF-8"?>
<jbossesb
 xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.0.1.xsd"
 parameterReloadSecs="5">

 <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="esbChannel">
 <jms-message-filter dest-type="QUEUE"
 dest-name="queue/request_esb" />
 </jms-bus>

 </jms-provider>

 <jbr-provider name="JBR-Http-HR-CF" protocol="http" host="localhost">
 <jbr-bus busid="Http-2" port="8766"/>
 </jbr-provider>
 </providers>

 <services>
 <service category="HRtoCFCategory" name="CandidateListener"
 description="Main ESB Gate">
 <listeners>
 <jms-listener name="helloWorld"
 busidref="esbChannel" maxThreads="5" />
 </listeners>

 <actions mep="OneWay">
 <action name="action1"
 class="com.tsystems.tintra4.esb.listeners.CandidateToEmplListenerAction"
 process="displayMessage" />

 <action name="register_a_new_employee_process"
 class="org.jboss.soa.esb.services.jbpm.actions.BpmProcessor">

 <property name="command"
 value="StartProcessInstanceCommand" />

 <property name="process-definition-name"
 value="CFjBPM" />



 <property name="esbToBpmVars">
 <mapping esb="BODY_CONTENT" bpm="theBody" />
 </property>



 </action>

 </actions>
 </service>

 <service category="HRtoCFCategory" name="WSProducerService" description="WS Frontend speaks natively to the ESB">

 <listeners>

 <jbr-listener name="Http-Gateway" busidref="Http-2" is-gateway="true" maxThreads="1"/>

 </listeners>
 <actions>
 <action name="print-before" class="org.jboss.soa.esb.actions.SystemPrintln">
 <property name="id"
 value="BEFORE invoking jbossws endpoint"/>
 </action>
 <action name="JBossWSAdapter" class="org.jboss.soa.esb.actions.soap.SOAPProcessor">
 <property name="jbossws-endpoint" value="TestESBWebService"/>
 </action>
 <action name="print-after" class="org.jboss.soa.esb.actions.SystemPrintln">
 <property name="id"
 value="AFTER invoking jbossws endpoint"/>
 </action>
 </actions>
 </service>


 </services>

</jbossesb>

, deployement.xml:

<jbossesb-deployment>
 <depends>jboss.esb.destination:service=Queue,name=request_esb</depends>
</jbossesb-deployment>

and jbmq-queue-service.xml:

<?xml version="1.0" encoding="UTF-8"?>
<server>
 <mbean code="org.jboss.mq.server.jmx.Queue"
 name="jboss.esb.destination:service=Queue,name=request_esb">
 <depends optional-attribute-name="DestinationManager">
 jboss.mq:service=DestinationManager
 </depends>
 </mbean>
</server>

Does anybody know what amI doing wrong? - Please, I appreciate any help.

1. Re: webservice_producer sample..

tfennelly Jun 5, 2008 9:26 AM (in response to fil78)

I'm confused... the subject refers to the webservice_produce quickstart, ye nothing I see in the post looks like anything in that quickstart.

Could you email you quickstart please?
Actions
2. Re: webservice_producer sample..

fil78 Jun 5, 2008 9:48 AM (in response to fil78)

I have sent you - but the question is more about jbr-providers then quickstart itself... So the snippets are not the webservice_producer sample but I tried to create them according to webservice_producer...
Actions
3. Re: webservice_producer sample..

tfennelly Jun 5, 2008 11:30 AM (in response to fil78)

Looking back at your original post... your exception relates to the fact that you don't have a "Message Aware Listener" installed on your "HRtoCFCategory:WSProducerService" Service.

Which ESB version are you using?

If you're using 4.3.GA you can configure your Server to deploy an InVM transport for every service, which would mean you wouldn't get the above error from the above config.
Actions

Go to original post