[esb-issues] [JBoss JIRA] Commented: (JBESB-980) wiretap QS : Illegal property name "JMSXDeliveryCount"

[Daniel Bevenius (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBESB-980?page=comments#action_12375075 ] 
            
Daniel Bevenius commented on JBESB-980:
---------------------------------------

I believe that this is a problem with DefaultJMSPropertiesSetter, I only check for invalid property names and not for the ones reserved by the JMS spec. 
Simply removeing the call to setProperties in DefaultJMSPropertiesSetter's setJMSProperties() method will take care of this. If users need to set custom properties they can specify their own implementation. 
Sorry about this.

 

> wiretap QS : Illegal property name "JMSXDeliveryCount"
> ------------------------------------------------------
>
>                 Key: JBESB-980
>                 URL: http://jira.jboss.com/jira/browse/JBESB-980
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Examples
>            Reporter: Tom Cunningham
>         Assigned To: Kevin Conner
>             Fix For: 4.2
>
>
> During deploy of the wiretap QS to the appserver as an .esb archive, I get an error on executing the runtest-cbr target :
> org.jboss.soa.esb.notification.NotificationException: javax.jms.JMSException: Illegal property name: JMSXDeliveryCount
>         at org.jboss.soa.esb.notification.NotifyJMS.sendNotification(NotifyJMS.java:212)
>         at org.jboss.soa.esb.notification.NotificationList.notifyAll(NotificationList.java:164)
>         at org.jboss.soa.esb.actions.Notifier.notifyOK(Notifier.java:91)
>         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.soa.esb.listeners.message.ActionProcessorMethodInfo.processSuccess(ActionProcessorMethodInfo.java:154)
>         at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.processSuccess(OverriddenActionLifecycleProcessor.java:108)
>         at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.notifySuccess(ActionProcessingPipeline.java:516)
>         at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:320)
>         at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:297)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
>         at java.lang.Thread.run(Thread.java:613)
> Caused by: javax.jms.JMSException: Illegal property name: JMSXDeliveryCount
>         at org.jboss.mq.SpyMessage.checkProperty(SpyMessage.java:1006)
>         at org.jboss.mq.SpyMessage.setIntProperty(SpyMessage.java:715)
>         at org.jboss.soa.esb.notification.jms.DefaultJMSPropertiesSetter.setProperties(DefaultJMSPropertiesSetter.java:126)
>         at org.jboss.soa.esb.notification.jms.DefaultJMSPropertiesSetter.setJMSProperties(DefaultJMSPropertiesSetter.java:66)
>         at org.jboss.soa.esb.notification.NotifyJMS.setJMSProperties(NotifyJMS.java:225)
>         at org.jboss.soa.esb.notification.NotifyJMS.sendNotification(NotifyJMS.java:200)
>         ... 14 more

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira