You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "ant elder (JIRA)" <tu...@ws.apache.org> on 2008/03/13 15:23:46 UTC
[jira] Closed: (TUSCANY-2051) JMS binding: Exception while sending
a FaultReply
[ https://issues.apache.org/jira/browse/TUSCANY-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ant elder closed TUSCANY-2051.
------------------------------
Resolution: Fixed
There was some more discussion about this on the ML: http://apache.markmail.org/message/kmdzotqlosermrve?q=TUSCANY-2051
The JMS binding has been updated so exceptions get sent back in a JMS object message with a property set to indicate its a fault response, and while not completly perfect that fixes the reported problem so I'll close this JIRA.
> JMS binding: Exception while sending a FaultReply
> -------------------------------------------------
>
> Key: TUSCANY-2051
> URL: https://issues.apache.org/jira/browse/TUSCANY-2051
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA JMS Binding Extension
> Affects Versions: Java-SCA-1.1
> Environment: Win XP
> Reporter: Ph.Konradi
> Fix For: Java-SCA-Next
>
>
> Class: JMSBindingListener.java
> Method: public void onMessage(Message requestJMSMsg)
>
> calling sendFaultReply(requestJMSMsg, e) fails
> with the following exception:
> Exception while processing message: java.lang.ClassCastException: org.apache.tuscany.sca.binding.jms.impl.JMSBindingException
> java.lang.ClassCastException: org.apache.tuscany.sca.binding.jms.impl.JMSBindingException
> at org.apache.tuscany.sca.binding.jms.provider.JMSMessageProcessorImpl.createXMLJMSMessage(JMSMessageProcessorImpl.java:140)
> at org.apache.tuscany.sca.binding.jms.provider.JMSMessageProcessorImpl.insertPayloadIntoJMSMessage(JMSMessageProcessorImpl.java:85)
> at org.apache.tuscany.sca.binding.jms.provider.JMSBindingListener.sendReply(JMSBindingListener.java:125)
> at org.apache.tuscany.sca.binding.jms.provider.JMSBindingListener.sendFaultReply(JMSBindingListener.java:152)
> at org.apache.tuscany.sca.binding.jms.provider.JMSBindingListener.onMessage(JMSBindingListener.java:65)
> at org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:854)
> at org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:99)
> at org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:166)
> at org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:117)
> at org.apache.activemq.thread.PooledTaskRunner.access$100(PooledTaskRunner.java:26)
> at org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:44)
> at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
> at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> at java.lang.Thread.run(Thread.java:595)
> A quick, but not optimal, resolution would be:
> change: sendFaultReply(requestJMSMsg, e)
> to: sendFaultReply(requestJMSMsg, new Object[]{e})
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org