What is happening here is that the JMSXDeliveryCount property is set on the incoming message. Since the incoming and outgoing transports are the same, the transport headers (i.e. the JMS properties in this case) are preserved. This causes a problem because JMSXDeliveryCount is a reserved property. Probably we should just ignore these properties in JMSSender. As a workaround you can try to remove this property from the transport headers during the mediation. Note that this however will not solve the problem with 'Content-Type' (see my previous mail).
Andreas On Tue, Nov 4, 2008 at 10:46, Irantha <[EMAIL PROTECTED]> wrote: > Here's my config file. > > JBoss SpyMessage (javax.jms.Message instance) throw following exception for > all properties set inside JMSUtils.setTransportHeaders method: > [EMAIL PROTECTED]"javax.jms.JMSException: Illegal property name: > XXX" > > and following exception when content type is set inside > JMSSender.createJMSMessage method: > [EMAIL PROTECTED]"java.lang.IllegalArgumentException: > The property name 'Content-Type' is not a valid java identifier." > > I couldn't find anybody who tested Synapse with JBossMQ over here. > > -Irantha > > > ----- Original Message ----- From: "Andreas Veithen" > <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Tuesday, November 04, 2008 2:42 PM > Subject: Re: JMS transport with JBossMQ error > > >> Can you share your Synapse configuration with us? >> >> Andreas >> >> On Tue, Nov 4, 2008 at 07:54, Irantha <[EMAIL PROTECTED]> wrote: >>> >>> When using a JMS endpoint with JBossMQ I get the following error. >>> >>> [Axis2 Task] ERROR JMSSender Error creating a JMS message from the axis >>> message context >>> javax.jms.JMSException: Illegal property name: JMSXDeliveryCount >>> at org.jboss.mq.SpyMessage.checkProperty(SpyMessage.java:1006) >>> at org.jboss.mq.SpyMessage.setStringProperty(SpyMessage.java:750) >>> at >>> >>> org.apache.synapse.transport.jms.JMSUtils.setTransportHeaders(JMSUtils.java:618) >>> at >>> >>> org.apache.synapse.transport.jms.JMSSender.createJMSMessage(JMSSender.java:483) >>> at >>> >>> org.apache.synapse.transport.jms.JMSSender.sendMessage(JMSSender.java:204) >>> at >>> >>> org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:104) >>> at >>> >>> org.apache.axis2.engine.AxisEngine$TransportNonBlockingInvocationWorker.run(AxisEngine.java:614) >>> at >>> >>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) >>> at >>> >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) >>> at java.lang.Thread.run(Thread.java:619) >>> >>> >>> Synapse is running within JBoss. Is this a known issue? >>> >>> -Irantha >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
