Re: JMS transport with JBossMQ error

[Irantha]

Andreas,




-Irantha



To: <dev@synapse.apache.org>
Sent: Wednesday, November 05, 2008 4:36 AM
Subject: Re: JMS transport with JBossMQ error

Here's a patch for SYNAPSE-424 and SYNAPSE-478. I can't proceed without resolving them. Piggybacked "Content-Type" on a property named "ContentType" when former is not available. Seems ther property errors (SYNAPSE-478) can be ignored. ----- Original Message ----- From: "Andreas Veithen" <[EMAIL PROTECTED]>

Irantha,

I'm going to work on SYNAPSE-424. Can you open another JIRA for the
issue related to reserved JMS property names?

Andreas

On Tue, Nov 4, 2008 at 11:32, Irantha <[EMAIL PROTECTED]> wrote:

Exception is thrown for following properties:
JMSXDeliveryCount, JMS_DESTINATION, JMS_JBOSS_REDELIVERY_COUNT,
JMS_REDELIVERED

when all exceptions are ignored message is correctly delivered to
destination jms queue, but Axis2Server (simple stock quote sample) throw
following exception,

2008-11-04 15:52:27,359 [-] [jms-Worker-1] ERROR AxisEngine The service
cannot be found for the endpoint reference (EPR)
org.apache.axis2.AxisFault: The service cannot be found for the endpoint
reference (EPR)
      at
org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPha
se.java:64)
      at org.apache.axis2.engine.Phase.invoke(Phase.java:333)
      at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:264)
      at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:163)
      at
org.apache.synapse.transport.base.AbstractTransportListener.handleInc
omingMessage(AbstractTransportListener.java:256)
      at
org.apache.synapse.transport.jms.JMSMessageReceiver$Worker.run(JMSMes
sageReceiver.java:218)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source
)

      at java.lang.Thread.run(Unknown Source)
org.apache.axis2.AxisFault: The service cannot be found for the endpoint
referen
ce (EPR)
      at
org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPha
se.java:64)
      at org.apache.axis2.engine.Phase.invoke(Phase.java:333)
      at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:264)
      at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:163)
      at
org.apache.synapse.transport.base.AbstractTransportListener.handleInc
omingMessage(AbstractTransportListener.java:256)
      at
org.apache.synapse.transport.jms.JMSMessageReceiver$Worker.run(JMSMes
sageReceiver.java:218)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source
)

      at java.lang.Thread.run(Unknown Source)

JMS
session
2008-11-04 15:52:27,390 [-] [jms-Worker-1] ERROR JMSListener Error
processing re
ceived message
org.apache.axis2.AxisFault: Could not create JMS session
      at
org.apache.synapse.transport.base.AbstractTransportSender.handleExcep
tion(AbstractTransportSender.java:243)
      at
org.apache.synapse.transport.jms.JMSSender.sendMessage(JMSSender.java
:195)

-Irantha


----- Original Message ----- From: "Andreas Veithen"
<[EMAIL PROTECTED]>
To: <dev@synapse.apache.org>
Sent: Tuesday, November 04, 2008 3:33 PM
Subject: Re: JMS transport with JBossMQ error

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 2008-11-04 15:52:27,390 [-] [jms-Worker-1] ERROR JMSSender Could not create

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: <dev@synapse.apache.org>
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.


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

[Axis2 Task] ERROR JMSSender Error creating a JMS message from the axis

---------------------------------------------------------------------
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]

---------------------------------------------------------------------
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]

commons_jms.patch
Description: Binary data

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]