[jboss-user] [JBoss Messaging] - Re: JBM 1.4.0.SP3 JMSX properties bug
Clearly the extra sem-colon is a bug. But regarding the issue of not allowing JMSX properties to be set: The JMS spec (1.1, section 3.5.8, table 3.3) makes it clear that the only JMSX properties that can be set by the client are JMSXGroupID and JMSXGroupSeq. So I think the current behaviour is correct. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4131050#4131050 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4131050 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: JBM 1.4.0.SP3 JMSX properties bug
Also this is related to http://jira.jboss.org/jira/browse/JBMESSAGING-1185 View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4131051#4131051 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4131051 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: JBM 1.4.0.SP3 JMSX properties bug
Yes, this is related to the other issue. The Oracle provider is setting the JMSX properties which causes the exception within JBoss. My workaround was for JBoss is to ignore those properties and NOT throw the exception. JBossMesage.java: public void setObjectProperty(String name, Object value) throws JMSException |{ | | if (JMS_JBOSS_SCHEDULED_DELIVERY_PROP_NAME.equals(name) value instanceof Long) | { | this.scheduledDeliveryTime = ((Long)value).longValue(); | return; | } | | // Ignore JMSX properties. | // Click Commerce workaround for using bridge with OC4J JMS Provider. | if (isJMSXProperty(name)) | return; | | | |/** | * Click Commerce workaround for using bridge with OC4J JMS Provider. | * | * Check the property name to see if it is a JMXS property. JMSX properties | * should not be propagated. This method is used to determine if the given property | * is eligable to be ignored. | * | * Note this method was introduced as a work around to JBoss JBM JIRA ticket See: | * http://jira.jboss.org/jira/browse/JBMESSAGING-1224 | * | * Note checkProperty() will throw an exception when a JMSX propery is encountered. | * | * @param name the property name | * @return boolean true indicating the property is a JMSX property or | * false if the property is not a JMSX property. | */ |boolean isJMSXProperty(String name) |{ |if (name.startsWith(JMSX) | !name.equals(JMSXGroupID) | !name.equals(JMSXGroupSeq) | !name.equals(JMSXDeliveryCount)) | { | return true; | } |else |{ |return false; |} |} | | This was used with Oracle Application Server 10.1.2 View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4131060#4131060 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4131060 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: JBM 1.4.0.SP3 JMSX properties bug
Thanks for the report. :) We'll get in fixed in the next release http://jira.jboss.org/jira/browse/JBMESSAGING-1224 View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4124039#4124039 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4124039 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: JBM 1.4.0.SP3 JMSX properties bug
Thanks. Let me know if you want the source for the workaround I added. It's not ideal, but may assist to understand the problem. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4124160#4124160 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4124160 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user