Synapse ESB and IBM MQ issue

View: New views
18 Messages — Rating Filter:   Alert me  

Synapse ESB and IBM MQ issue

by Sunil.2.Tiwari :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hi,

I am trying to evaluate Apache Synapse. Goal is  to pick message from IBM-MQ queue and log it using a ESB Proxy Service.

Successfully enabled JMS transport in asix2.xml.

Synapse ESB Proxy Service is picking the message from MQ queue but through error before logging as (PFA for complete Error) <<ReleventConsoleLog.txt>>

<<CompleteConsole.txt>>

 

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.validateTransport(DispatchPhase.java:218)

        at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:95)

        at org.apache.axis2.engine.Phase.invoke(Phase.java:333)

        at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:264)

 

 

 

PROXY SERVICE CODE

 

==

<proxy name="TestMQProxy" transports="jms" startOnLoad="true" statistics="enable">

    <parameter name="transport.jms.Destination">MyMDBQueue</parameter>

        <target>

            <inSequence>

                <property action="set" name="OUT_ONLY" value="true"/>

            </inSequence>

           

            <outSequence>

                             <log level="full" separator=", "/>

                <send/>

            </outSequence>

        </target>

      

    </proxy>

==

 

Help will be appreciated.

 

 

 

 

 

Thanks & Regards

Sunil Kumar Tiwari | I&B2B | Tech Mahindra Ltd.

(Office: 009120 6641 7136  Mobile: 0091 9767644210)

Email: sunil.tiwari2@...

 

============================================================================================================================


Disclaimer:

This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally and http://tim.techmahindra.com/Disclaimer.html internally within Tech Mahindra.

============================================================================================================================

2009-07-31 10:51:39,829 [localhost] [WrapperSimpleAppMain]  INFO ServerManager Starting transport jms
2009-07-31 10:51:39,829 [localhost] [WrapperSimpleAppMain] DEBUG NativeWorkerPool Using native util.con
current package..
2009-07-31 10:51:39,829 [localhost] [WrapperSimpleAppMain]  INFO JMSListener JMS Transport Receiver/Lis
tener initialized...
2009-07-31 10:51:39,829 [localhost] [WrapperSimpleAppMain] DEBUG JMSConnectionFactory Initializing the
JMS connection factory : default
2009-07-31 10:51:39,829 [localhost] [WrapperSimpleAppMain]  INFO JMSConnectionFactory Connected to the
JMS connection factory : ReceiverQCF
2009-07-31 10:51:39,844 [localhost] [WrapperSimpleAppMain]  INFO JMSConnectionFactory Connection factor
y : default initialized...
2009-07-31 10:51:39,844 [localhost] [WrapperSimpleAppMain]  INFO JMSListener JMS Listener started
2009-07-31 10:51:39,844 [localhost] [WrapperSimpleAppMain] DEBUG JMSUtils JMS destination type not give
n. default queue
2009-07-31 10:51:39,844 [localhost] [WrapperSimpleAppMain]  INFO JMSListener Starting to listen on dest
ination : MyMDBQueue of type queue for service TestMQProxy
2009-07-31 10:51:39,844 [localhost] [WrapperSimpleAppMain]  INFO JMSConnectionFactory Mapped JNDI name
: MyMDBQueue and JMS Destination name : queue://testqmgr/MyMDBQueue against service : TestMQProxy
2009-07-31 10:51:39,907 [localhost] [WrapperSimpleAppMain]  INFO ServerManager Ready for processing
2009-07-31 10:52:02,173 [localhost] [asyncDelivery0] DEBUG JMSMessageReceiver Received JMS message to d
estination : null
Message ID : ID:414d512074657374716d677220202020e66c704a20082d02
Correlation ID : null
ReplyTo ID : null
2009-07-31 10:52:02,173 [localhost] [asyncDelivery0] TRACE JMSMessageReceiver
Message : <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body xmlns:ns1="http://capabilitie
s.nat/xsd/ManageCustomer/2008/09/26"><ns1:queryCustomerRequest></ns1:queryCustomerRequest></soap:Body></soap:Enve
lope>
2009-07-31 10:52:02,282 [localhost] [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.validateTransport(DispatchPhase.java:218)
        at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:95)
        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.handleIncomingMessage(AbstractTransportListener.j
ava:256)
        at org.apache.synapse.transport.jms.JMSMessageReceiver$Worker.run(JMSMessageReceiver.java:218)
        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:595)
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR)
        at org.apache.axis2.engine.DispatchPhase.validateTransport(DispatchPhase.java:218)
        at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:95)
        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.handleIncomingMessage(AbstractTransportListener.j
ava:256)
        at org.apache.synapse.transport.jms.JMSMessageReceiver$Worker.run(JMSMessageReceiver.java:218)
        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:595)
2009-07-31 10:52:02,282 [localhost] [jms-Worker-1] DEBUG JMSListener Error receiving message
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR)
        at org.apache.axis2.engine.DispatchPhase.validateTransport(DispatchPhase.java:218)
        at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:95)
        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.handleIncomingMessage(AbstractTransportListener.j
ava:256)
        at org.apache.synapse.transport.jms.JMSMessageReceiver$Worker.run(JMSMessageReceiver.java:218)
        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:595)
2009-07-31 10:52:02,298 [localhost] [jms-Worker-1] ERROR JMSSender Could not create JMS session
2009-07-31 10:52:02,298 [localhost] [jms-Worker-1] ERROR JMSListener Error processing received message
org.apache.axis2.AxisFault: Could not create JMS session
        at org.apache.synapse.transport.base.AbstractTransportSender.handleException(AbstractTransportSender.java:243)
        at org.apache.synapse.transport.jms.JMSSender.sendMessage(JMSSender.java:195)
        at org.apache.synapse.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:127)
        at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:530)
        at org.apache.synapse.transport.base.AbstractTransportListener.handleIncomingMessage(AbstractTransportListener.j
ava:263)
        at org.apache.synapse.transport.jms.JMSMessageReceiver$Worker.run(JMSMessageReceiver.java:218)
        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:595)
2009-07-31 10:52:02,298 [localhost] [jms-Worker-1] ERROR JMSMessageReceiver Axis fault creating a Messa
geContext
org.apache.axis2.AxisFault: Could not create JMS session
        at org.apache.synapse.transport.base.AbstractTransportSender.handleException(AbstractTransportSender.java:243)
        at org.apache.synapse.transport.jms.JMSSender.sendMessage(JMSSender.java:195)
        at org.apache.synapse.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:127)
        at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:530)
        at org.apache.synapse.transport.base.AbstractTransportListener.handleIncomingMessage(AbstractTransportListener.j
ava:263)
        at org.apache.synapse.transport.jms.JMSMessageReceiver$Worker.run(JMSMessageReceiver.java:218)
        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:595)
Exception in thread "jms-Worker-1" org.apache.synapse.transport.jms.AxisJMSException: Axis fault creating a MessageConte
xt
        at org.apache.synapse.transport.jms.JMSMessageReceiver.handleException(JMSMessageReceiver.java:127)
        at org.apache.synapse.transport.jms.JMSMessageReceiver.access$400(JMSMessageReceiver.java:41)
        at org.apache.synapse.transport.jms.JMSMessageReceiver$Worker.run(JMSMessageReceiver.java:230)
        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:595)
Caused by: org.apache.axis2.AxisFault: Could not create JMS session
        at org.apache.synapse.transport.base.AbstractTransportSender.handleException(AbstractTransportSender.java:243)
        at org.apache.synapse.transport.jms.JMSSender.sendMessage(JMSSender.java:195)
        at org.apache.synapse.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:127)
        at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:530)
        at org.apache.synapse.transport.base.AbstractTransportListener.handleIncomingMessage(AbstractTransportListener.j
ava:263)
        at org.apache.synapse.transport.jms.JMSMessageReceiver$Worker.run(JMSMessageReceiver.java:218)
        ... 3 more


G:\B2BProgramFiles\synapse-1.2\bin>synapse.bat
"Starting Synapse/Java ..."
Using SYNAPSE_HOME:        G:\B2BPRO~1\SYNAPS~1.2\bin\..
Using JAVA_HOME:       G:\B2BProgramFiles\jdk160_05
--> Wrapper Started as Console
Launching a JVM...
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
  Copyright 1999-2006 Tanuki Software, Inc.  All Rights Reserved.

2009-07-31 10:51:38,438 [-] [WrapperSimpleAppMain]  INFO ServerManager Using Synapse home as : .
2009-07-31 10:51:38,438 [-] [WrapperSimpleAppMain]  INFO ServerManager Using the Axis2 Repository : G:\B2BPRO~1\SYNAPS~1
.2\repository
2009-07-31 10:51:38,438 [-] [WrapperSimpleAppMain]  INFO ServerManager Using the axis2.xml : G:\B2BPRO~1\SYNAPS~1.2\repo
sitory\conf\axis2.xml
2009-07-31 10:51:38,438 [-] [WrapperSimpleAppMain]  INFO ServerManager Using server name : localhost
2009-07-31 10:51:38,438 [-] [WrapperSimpleAppMain]  INFO ServerManager The timeout handler will run every : 15s
2009-07-31 10:51:39,126 [-] [WrapperSimpleAppMain]  INFO SynapseInitializationModule Initializing Synapse at : Fri Jul 3
1 10:51:39 BST 2009
2009-07-31 10:51:39,141 [localhost] [WrapperSimpleAppMain]  INFO SynapseInitializationModule Loading me
diator extensions...
2009-07-31 10:51:39,141 [localhost] [WrapperSimpleAppMain]  INFO SynapseInitializationModule Initializi
ng the Synapse configuration ...
2009-07-31 10:51:39,141 [localhost] [WrapperSimpleAppMain] DEBUG SynapseConfigurationBuilder synapse.pr
operties file is loading from classpath
2009-07-31 10:51:39,141 [localhost] [WrapperSimpleAppMain] DEBUG DataSourceRegistrar No DataSources def
ined for initialization..
2009-07-31 10:51:39,141 [localhost] [WrapperSimpleAppMain]  INFO XMLConfigurationBuilder Generating the
 Synapse configuration model by parsing the XML configuration
2009-07-31 10:51:39,157 [localhost] [WrapperSimpleAppMain] DEBUG ConfigurationFactoryAndSerializerFinde
r getConfiguration({http://ws.apache.org/ns/synapse}definitions)
2009-07-31 10:51:39,204 [localhost] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder Added MediatorFa
ctory class org.apache.synapse.mediators.spring.SpringMediatorFactory to handle {http://ws.apache.org/ns/synapse/spring}
spring
2009-07-31 10:51:39,204 [localhost] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder Added MediatorFa
ctory class org.apache.synapse.mediators.bsf.ScriptMediatorFactory to handle {http://ws.apache.org/ns/synapse}script
2009-07-31 10:51:39,204 [localhost] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder Added MediatorFa
ctory class org.apache.synapse.mediators.throttle.ThrottleMediatorFactory to handle {http://ws.apache.org/ns/synapse}thr
ottle
2009-07-31 10:51:39,204 [localhost] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder Added MediatorFa
ctory class org.apache.synapse.mediators.xquery.XQueryMediatorFactory to handle {http://ws.apache.org/ns/synapse}xquery
2009-07-31 10:51:39,204 [localhost] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder getMediator({htt
p://ws.apache.org/ns/synapse}in)
2009-07-31 10:51:39,204 [localhost] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder getMediator({htt
p://ws.apache.org/ns/synapse}log)
2009-07-31 10:51:39,204 [localhost] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder getMediator({htt
p://ws.apache.org/ns/synapse}filter)
2009-07-31 10:51:39,251 [localhost] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder getMediator({htt
p://ws.apache.org/ns/synapse}send)
2009-07-31 10:51:39,251 [localhost] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder getMediator({htt
p://ws.apache.org/ns/synapse}out)
2009-07-31 10:51:39,251 [localhost] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder getMediator({htt
p://ws.apache.org/ns/synapse}send)
2009-07-31 10:51:39,251 [localhost] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder getMediator({htt
p://ws.apache.org/ns/synapse}property)
2009-07-31 10:51:39,251 [localhost] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder getMediator({htt
p://ws.apache.org/ns/synapse}log)
2009-07-31 10:51:39,251 [localhost] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder getMediator({htt
p://ws.apache.org/ns/synapse}send)
2009-07-31 10:51:39,251 [localhost] [WrapperSimpleAppMain]  INFO SynapseConfigurationBuilder Loaded Syn
apse configuration from : G:\B2BPRO~1\SYNAPS~1.2\bin\..\repository\conf\synapse.xml
2009-07-31 10:51:39,266 [localhost] [WrapperSimpleAppMain] DEBUG SynapseConfiguration Initializing the
Synapse Configuration
2009-07-31 10:51:39,266 [localhost] [WrapperSimpleAppMain] DEBUG SequenceMediator Initializing child me
diators
2009-07-31 10:51:39,266 [localhost] [WrapperSimpleAppMain] DEBUG SequenceMediator Initializing child me
diators
2009-07-31 10:51:39,266 [localhost] [WrapperSimpleAppMain] DEBUG SequenceMediator Initializing child me
diators
2009-07-31 10:51:39,266 [localhost] [WrapperSimpleAppMain] DEBUG InMediator Initializing child mediator
s
2009-07-31 10:51:39,266 [localhost] [WrapperSimpleAppMain] DEBUG FilterMediator Initializing child medi
ators
2009-07-31 10:51:39,266 [localhost] [WrapperSimpleAppMain] DEBUG OutMediator Initializing child mediato
rs
2009-07-31 10:51:39,266 [localhost] [WrapperSimpleAppMain] DEBUG SequenceMediator Initializing child me
diators
2009-07-31 10:51:39,266 [localhost] [WrapperSimpleAppMain]  INFO SynapseInitializationModule Deploying
the Synapse service..
2009-07-31 10:51:39,282 [localhost] [WrapperSimpleAppMain]  INFO SynapseInitializationModule Synapse se
rver name : localhost
2009-07-31 10:51:39,282 [localhost] [WrapperSimpleAppMain]  INFO SynapseInitializationModule Deploying
Proxy services...
2009-07-31 10:51:39,282 [localhost] [WrapperSimpleAppMain]  INFO ProxyService Building Axis service for
 Proxy service : TestMQProxy
2009-07-31 10:51:39,282 [localhost] [WrapperSimpleAppMain]  INFO ProxyService Adding service TestMQProx
y to the Axis2 configuration
2009-07-31 10:51:39,282 [localhost] [WrapperSimpleAppMain]  INFO ProxyService Successfully created the
Axis2 service for Proxy service : TestMQProxy
2009-07-31 10:51:39,282 [localhost] [WrapperSimpleAppMain]  INFO SynapseInitializationModule Deployed P
roxy service : TestMQProxy
2009-07-31 10:51:39,282 [localhost] [WrapperSimpleAppMain]  INFO SynapseInitializationModule Synapse in
itialized successfully...!
2009-07-31 10:51:39,313 [localhost] [WrapperSimpleAppMain]  INFO HttpCoreNIOSSLSender Loading Identity
Keystore from : lib/identity.jks
2009-07-31 10:51:39,329 [localhost] [WrapperSimpleAppMain]  INFO HttpCoreNIOSSLSender Loading Trust Key
store from : lib/trust.jks
2009-07-31 10:51:39,391 [localhost] [WrapperSimpleAppMain]  INFO HttpCoreNIOSender HTTPS Sender startin
g
2009-07-31 10:51:39,423 [localhost] [WrapperSimpleAppMain]  INFO HttpCoreNIOSender HTTP Sender starting

2009-07-31 10:51:39,423 [localhost] [WrapperSimpleAppMain]  INFO VFSTransportSender VFS Sender started
2009-07-31 10:51:39,454 [localhost] [HttpCoreNIOSender] DEBUG NativeWorkerPool Using native util.concur
rent package..
2009-07-31 10:51:39,454 [localhost] [HttpCoreNIOSender] DEBUG NativeWorkerPool Using native util.concur
rent package..
2009-07-31 10:51:39,563 [localhost] [WrapperSimpleAppMain]  INFO JMSSender JMS Sender started
2009-07-31 10:51:39,579 [localhost] [WrapperSimpleAppMain] DEBUG JMSConnectionFactory Initializing the
JMS connection factory : default
2009-07-31 10:51:39,704 [localhost] [WrapperSimpleAppMain]  INFO JMSConnectionFactory Connected to the
JMS connection factory : SenderQCF
2009-07-31 10:51:39,798 [localhost] [WrapperSimpleAppMain]  INFO JMSConnectionFactory Connection factor
y : default initialized...
2009-07-31 10:51:39,813 [localhost] [WrapperSimpleAppMain]  INFO ServerManager Starting transport https
 on port 8243
2009-07-31 10:51:39,813 [localhost] [WrapperSimpleAppMain]  INFO HttpCoreNIOSSLListener Loading Identit
y Keystore from : lib/identity.jks
2009-07-31 10:51:39,813 [localhost] [WrapperSimpleAppMain]  INFO HttpCoreNIOSSLListener Loading Trust K
eystore from : lib/trust.jks
2009-07-31 10:51:39,813 [localhost] [WrapperSimpleAppMain] DEBUG HttpCoreNIOListener Starting Listener.
..
2009-07-31 10:51:39,813 [localhost] [WrapperSimpleAppMain]  INFO HttpCoreNIOListener HTTPS Listener sta
rting on port : 8243
2009-07-31 10:51:39,813 [localhost] [WrapperSimpleAppMain]  INFO ServerManager Starting transport http
on port 8280
2009-07-31 10:51:39,813 [localhost] [WrapperSimpleAppMain] DEBUG HttpCoreNIOListener Starting Listener.
..
2009-07-31 10:51:39,813 [localhost] [WrapperSimpleAppMain]  INFO HttpCoreNIOListener HTTP Listener star
ting on port : 8280
2009-07-31 10:51:39,813 [localhost] [WrapperSimpleAppMain]  INFO ServerManager Starting transport vfs
2009-07-31 10:51:39,813 [localhost] [WrapperSimpleAppMain] DEBUG NativeWorkerPool Using native util.con
current package..
2009-07-31 10:51:39,829 [localhost] [HttpCoreNIOListener] DEBUG NativeWorkerPool Using native util.conc
urrent package..
2009-07-31 10:51:39,829 [localhost] [HttpCoreNIOListener] DEBUG NativeWorkerPool Using native util.conc
urrent package..
2009-07-31 10:51:39,829 [localhost] [WrapperSimpleAppMain]  INFO VFSTransportListener VFS Listener star
ted
2009-07-31 10:51:39,829 [localhost] [WrapperSimpleAppMain]  INFO ServerManager Starting transport mailt
o
2009-07-31 10:51:39,829 [localhost] [WrapperSimpleAppMain] DEBUG NativeWorkerPool Using native util.con
current package..
2009-07-31 10:51:39,829 [localhost] [WrapperSimpleAppMain]  INFO MailTransportListener MAILTO Listener
started
2009-07-31 10:51:39,829 [localhost] [WrapperSimpleAppMain]  INFO ServerManager Starting transport jms
2009-07-31 10:51:39,829 [localhost] [WrapperSimpleAppMain] DEBUG NativeWorkerPool Using native util.con
current package..
2009-07-31 10:51:39,829 [localhost] [WrapperSimpleAppMain]  INFO JMSListener JMS Transport Receiver/Lis
tener initialized...
2009-07-31 10:51:39,829 [localhost] [WrapperSimpleAppMain] DEBUG JMSConnectionFactory Initializing the
JMS connection factory : default
2009-07-31 10:51:39,829 [localhost] [WrapperSimpleAppMain]  INFO JMSConnectionFactory Connected to the
JMS connection factory : ReceiverQCF
2009-07-31 10:51:39,844 [localhost] [WrapperSimpleAppMain]  INFO JMSConnectionFactory Connection factor
y : default initialized...
2009-07-31 10:51:39,844 [localhost] [WrapperSimpleAppMain]  INFO JMSListener JMS Listener started
2009-07-31 10:51:39,844 [localhost] [WrapperSimpleAppMain] DEBUG JMSUtils JMS destination type not give
n. default queue
2009-07-31 10:51:39,844 [localhost] [WrapperSimpleAppMain]  INFO JMSListener Starting to listen on dest
ination : MyMDBQueue of type queue for service TestMQProxy
2009-07-31 10:51:39,844 [localhost] [WrapperSimpleAppMain]  INFO JMSConnectionFactory Mapped JNDI name
: MyMDBQueue and JMS Destination name : queue://testqmgr/MyMDBQueue against service : TestMQProxy
2009-07-31 10:51:39,907 [localhost] [WrapperSimpleAppMain]  INFO ServerManager Ready for processing
2009-07-31 10:52:02,173 [localhost] [asyncDelivery0] DEBUG JMSMessageReceiver Received JMS message to d
estination : null
Message ID : ID:414d512074657374716d677220202020e66c704a20082d02
Correlation ID : null
ReplyTo ID : null
2009-07-31 10:52:02,173 [localhost] [asyncDelivery0] TRACE JMSMessageReceiver
Message : <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body xmlns:ns1="http://capabilitie
s.nat/xsd/ManageCustomer/2008/09/26"><ns1:queryCustomerRequest></ns1:queryCustomerRequest></soap:Body></soap:Enve
lope>
2009-07-31 10:52:02,282 [localhost] [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.validateTransport(DispatchPhase.java:218)
        at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:95)
        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.handleIncomingMessage(AbstractTransportListener.j
ava:256)
        at org.apache.synapse.transport.jms.JMSMessageReceiver$Worker.run(JMSMessageReceiver.java:218)
        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:595)
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR)
        at org.apache.axis2.engine.DispatchPhase.validateTransport(DispatchPhase.java:218)
        at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:95)
        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.handleIncomingMessage(AbstractTransportListener.j
ava:256)
        at org.apache.synapse.transport.jms.JMSMessageReceiver$Worker.run(JMSMessageReceiver.java:218)
        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:595)
2009-07-31 10:52:02,282 [localhost] [jms-Worker-1] DEBUG JMSListener Error receiving message
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR)
        at org.apache.axis2.engine.DispatchPhase.validateTransport(DispatchPhase.java:218)
        at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:95)
        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.handleIncomingMessage(AbstractTransportListener.j
ava:256)
        at org.apache.synapse.transport.jms.JMSMessageReceiver$Worker.run(JMSMessageReceiver.java:218)
        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:595)
2009-07-31 10:52:02,298 [localhost] [jms-Worker-1] ERROR JMSSender Could not create JMS session
2009-07-31 10:52:02,298 [localhost] [jms-Worker-1] ERROR JMSListener Error processing received message
org.apache.axis2.AxisFault: Could not create JMS session
        at org.apache.synapse.transport.base.AbstractTransportSender.handleException(AbstractTransportSender.java:243)
        at org.apache.synapse.transport.jms.JMSSender.sendMessage(JMSSender.java:195)
        at org.apache.synapse.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:127)
        at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:530)
        at org.apache.synapse.transport.base.AbstractTransportListener.handleIncomingMessage(AbstractTransportListener.j
ava:263)
        at org.apache.synapse.transport.jms.JMSMessageReceiver$Worker.run(JMSMessageReceiver.java:218)
        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:595)
2009-07-31 10:52:02,298 [localhost] [jms-Worker-1] ERROR JMSMessageReceiver Axis fault creating a Messa
geContext
org.apache.axis2.AxisFault: Could not create JMS session
        at org.apache.synapse.transport.base.AbstractTransportSender.handleException(AbstractTransportSender.java:243)
        at org.apache.synapse.transport.jms.JMSSender.sendMessage(JMSSender.java:195)
        at org.apache.synapse.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:127)
        at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:530)
        at org.apache.synapse.transport.base.AbstractTransportListener.handleIncomingMessage(AbstractTransportListener.j
ava:263)
        at org.apache.synapse.transport.jms.JMSMessageReceiver$Worker.run(JMSMessageReceiver.java:218)
        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:595)
Exception in thread "jms-Worker-1" org.apache.synapse.transport.jms.AxisJMSException: Axis fault creating a MessageConte
xt
        at org.apache.synapse.transport.jms.JMSMessageReceiver.handleException(JMSMessageReceiver.java:127)
        at org.apache.synapse.transport.jms.JMSMessageReceiver.access$400(JMSMessageReceiver.java:41)
        at org.apache.synapse.transport.jms.JMSMessageReceiver$Worker.run(JMSMessageReceiver.java:230)
        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:595)
Caused by: org.apache.axis2.AxisFault: Could not create JMS session
        at org.apache.synapse.transport.base.AbstractTransportSender.handleException(AbstractTransportSender.java:243)
        at org.apache.synapse.transport.jms.JMSSender.sendMessage(JMSSender.java:195)
        at org.apache.synapse.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:127)
        at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:530)
        at org.apache.synapse.transport.base.AbstractTransportListener.handleIncomingMessage(AbstractTransportListener.j
ava:263)
        at org.apache.synapse.transport.jms.JMSMessageReceiver$Worker.run(JMSMessageReceiver.java:218)
        ... 3 more

Re: Synapse ESB and IBM MQ issue

by Asankha C. Perera :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Sunil

First of all, please subscribe to the mailing list to receive our
replies off the list. For this time, I have copied this reply directly
to you

> I am trying to evaluate Apache Synapse. Goal is  to pick message from
> IBM-MQ queue and log it using a ESB Proxy Service.
The problem seems to be here:
2009-07-31 10:51:39,844 [localhost] [WrapperSimpleAppMain]  INFO
JMSListener Starting to listen on destination : MyMDBQueue of type queue
for service TestMQProxy
2009-07-31 10:51:39,844 [localhost] [WrapperSimpleAppMain]  INFO
JMSConnectionFactory Mapped JNDI name : MyMDBQueue and JMS Destination
name : queue://testqmgr/MyMDBQueue against service : TestMQProxy
2009-07-31 10:51:39,907 [localhost] [WrapperSimpleAppMain]  INFO
ServerManager Ready for processing
2009-07-31 10:52:02,173 [localhost] [asyncDelivery0] DEBUG
JMSMessageReceiver Received JMS message to destination : null

Note that the JMS message received, cannot give out its Destination name
(in the last line above) - I think its caused by MQ using a Queue name
and a JNDI destination name that differs. However I think this is
already fixed in the trunk, could you try with the latest snapshot build
found here:

http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/lastStableBuild/

>             <inSequence>
>                 <property action="set" name="OUT_ONLY" value="true"/>
>             </inSequence>
>             <outSequence>
>                              <log level="full" separator=", "/>
>                 <send/>
>             </outSequence>
>
BTW, if you just want to dump the message, move the <log...> into the
inSequence, and after that place a <drop/>. You wont need anything else
there..

cheers
asankha

--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org

http://esbmagic.blogspot.com





RE: Synapse ESB and IBM MQ issue

by Sunil.2.Tiwari :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Hi Asankha,
Could you please detail how can I use the latest stable build to upgrade Synapse version (Steps)?
So that I overcome MQ-JMS connection factory name/ destination queue name mismatch problem.

http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/lastStableBuild/


That is the only solution I can see for this problem.



Thanks & Regards

Sunil Kumar Tiwari | Tech Mahindra Ltd.

(Office: 009120 6641 7136  Mobile: 0091 9767644210)

Email: sunil.tiwari2@...

________________________________
From: Asankha Perera [mailto:asankha.apache@...] On Behalf Of Asankha C. Perera
Sent: Friday, July 31, 2009 6:14 PM
To: user@...; Sunil.2.Tiwari
Subject: Re: Synapse ESB and IBM MQ issue

Hi Sunil

First of all, please subscribe to the mailing list to receive our replies off the list. For this time, I have copied this reply directly to you


I am trying to evaluate Apache Synapse. Goal is  to pick message from IBM-MQ queue and log it using a ESB Proxy Service.
The problem seems to be here:
2009-07-31 10:51:39,844 [localhost] [WrapperSimpleAppMain]  INFO JMSListener Starting to listen on destination : MyMDBQueue of type queue for service TestMQProxy
2009-07-31 10:51:39,844 [localhost] [WrapperSimpleAppMain]  INFO JMSConnectionFactory Mapped JNDI name : MyMDBQueue and JMS Destination name : queue://testqmgr/MyMDBQueue against service : TestMQProxy
2009-07-31 10:51:39,907 [localhost] [WrapperSimpleAppMain]  INFO ServerManager Ready for processing
2009-07-31 10:52:02,173 [localhost] [asyncDelivery0] DEBUG JMSMessageReceiver Received JMS message to destination : null

Note that the JMS message received, cannot give out its Destination name (in the last line above) - I think its caused by MQ using a Queue name and a JNDI destination name that differs. However I think this is already fixed in the trunk, could you try with the latest snapshot build found here:

http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/lastStableBuild/


            <inSequence>
                <property action="set" name="OUT_ONLY" value="true"/>
            </inSequence>
            <outSequence>
                             <log level="full" separator=", "/>
                <send/>
            </outSequence>
BTW, if you just want to dump the message, move the <log...> into the inSequence, and after that place a <drop/>. You wont need anything else there..

cheers
asankha


--

Asankha C. Perera

AdroitLogic, http://adroitlogic.org



http://esbmagic.blogspot.com








============================================================================================================================

 
Disclaimer:

This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at <a href="http://www.techmahindra.com/Disclaimer.html">http://www.techmahindra.com/Disclaimer.html</a> externally and <a href="http://tim.techmahindra.com/Disclaimer.html">http://tim.techmahindra.com/Disclaimer.html</a> internally within Tech Mahindra.

============================================================================================================================

Re: Synapse ESB and IBM MQ issue

by Asankha C. Perera :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Sunil
>
> Could you please detail how can I use the latest stable build to
> upgrade Synapse version (Steps)?
>
None in particular.. just extract the last nightly build from the
location I specified, extract the Zip file, and just change the
synapse.xml found at the same place as before in the 1.2 release
>
> So that I overcome MQ-JMS connection factory name/ destination queue
> name mismatch problem.
>
If you hit any issues, do keep the user@ list informed, so you do not
need to Cc: emails direct to me

cheers
asankha

--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org

http://esbmagic.blogspot.com





RE: Synapse ESB and IBM MQ issue

by Sunil.2.Tiwari :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hi,

I am getting exception while deploying MQ-Queue listener proxy service. Using latest synapse built for development. When trying to deploy proxy service getting attached error.

Proxy Service Synapse.xml::

<definitions xmlns="http://ws.apache.org/ns/synapse">

 <proxy name="ReceiverQCFPS" transports="jms" startOnLoad="true" statistics="enable">

    <parameter name="transport.jms.Destination">MyMDBQueue</parameter>

        <target>

            <inSequence>

              <log level="full" separator=", "/>

            <drop/>

            </inSequence>

          </target>

        </proxy>

</definitions>

 

Eception snap shot (PFA for complete log)::

2009-08-03 15:00:32,218 [-] [jms-Worker-1] ERROR ServiceTaskManager Error creating JMS consumer for service : ReceiverQC

FPS

javax.jms.IllegalStateException: MQJMS1112: JMS1.1 Invalid operation for domain specific object

        at com.ibm.mq.jms.MQQueueSession.createConsumer(MQQueueSession.java:398)

        at org.apache.axis2.transport.jms.JMSUtils.createConsumer(JMSUtils.java:634)

        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConsumer(ServiceTaskManager.java:

835)

 

Any idea how overcome this exception.

 

Thanks & Regards

Sunil Kumar Tiwari | Tech Mahindra Ltd.

(Office: 009120 6641 7136  Mobile: 0091 9767644210)

Email: sunil.tiwari2@...

 

-----Original Message-----
From: Asankha Perera [mailto:asankha.apache@...] On Behalf Of Asankha C. Perera
Sent: Saturday, August 01, 2009 8:50 PM
To: user@...
Subject: Re: Synapse ESB and IBM MQ issue

 

Hi Sunil

> 

> Could you please detail how can I use the latest stable build to

> upgrade Synapse version (Steps)?

> 

None in particular.. just extract the last nightly build from the

location I specified, extract the Zip file, and just change the

synapse.xml found at the same place as before in the 1.2 release

> 

> So that I overcome MQ-JMS connection factory name/ destination queue

> name mismatch problem.

> 

If you hit any issues, do keep the user@ list informed, so you do not

need to Cc: emails direct to me

 

cheers

asankha

 

--

Asankha C. Perera

AdroitLogic, http://adroitlogic.org

 

http://esbmagic.blogspot.com

 

 

 

 

============================================================================================================================


Disclaimer:

This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally and http://tim.techmahindra.com/Disclaimer.html internally within Tech Mahindra.

============================================================================================================================

G:\B2BProgramFiles>
G:\synapse-1.4.0-SNAPSHOT\bin>synapse.bat
"Starting Synapse/Java ..."
Using SYNAPSE_HOME:        G:\SYNAPS~1.0-S\bin\..
Using JAVA_HOME:       G:\jdk160_05
--> Wrapper Started as Console
Launching a JVM...
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
  Copyright 1999-2006 Tanuki Software, Inc.  All Rights Reserved.

2009-08-03 14:32:55,951 [-] [WrapperSimpleAppMain]  INFO SynapseServer Starting Apache Synapse...
2009-08-03 14:32:55,967 [-] [WrapperSimpleAppMain]  INFO SynapseControllerFactory Using Synapse home : G:\SYNAP
S~1.0-S\.
2009-08-03 14:32:55,967 [-] [WrapperSimpleAppMain]  INFO SynapseControllerFactory Using Axis2 repository : G:\B2BPRO~1\S
YNAPS~1.0-S\repository
2009-08-03 14:32:55,967 [-] [WrapperSimpleAppMain]  INFO SynapseControllerFactory Using axis2.xml location : G:\B2BPRO~1
\SYNAPS~1.0-S\repository\conf\axis2.xml
2009-08-03 14:32:55,967 [-] [WrapperSimpleAppMain]  INFO SynapseControllerFactory Using synapse.xml location : G:\B2BPRO
~1\SYNAPS~1.0-S\bin\..\repository\conf\synapse.xml
2009-08-03 14:32:55,967 [-] [WrapperSimpleAppMain]  INFO SynapseControllerFactory Using server name : localhost
2009-08-03 14:32:55,998 [-] [WrapperSimpleAppMain]  INFO SynapseControllerFactory The timeout handler will run every : 1
5s
2009-08-03 14:32:56,045 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Initializing Synapse at : Mon Aug 03 14:
32:56 BST 2009
2009-08-03 14:32:57,326 [-] [WrapperSimpleAppMain] ERROR SandeshaModule Could not load module policies. Using default va
lues.
2009-08-03 14:32:57,358 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSSLSender Loading Identity Keystore from : lib/ident
ity.jks
2009-08-03 14:32:57,373 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSSLSender Loading Trust Keystore from : lib/trust.jk
s
2009-08-03 14:32:57,483 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSender HTTPS Sender starting
2009-08-03 14:32:57,498 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSender HTTP Sender starting
2009-08-03 14:32:57,498 [-] [WrapperSimpleAppMain]  INFO VFSTransportSender VFS Sender started
2009-08-03 14:32:57,639 [-] [WrapperSimpleAppMain]  INFO JMSSender JMS Sender started
2009-08-03 14:32:57,764 [-] [WrapperSimpleAppMain]  INFO JMSConnectionFactory JMS ConnectionFactory : default initialize
d
2009-08-03 14:32:57,764 [-] [WrapperSimpleAppMain]  INFO JMSSender JMS Transport Sender initialized...
2009-08-03 14:32:57,795 [-] [WrapperSimpleAppMain]  WARN JmxAdapter Using unsecured JMX remote access!
2009-08-03 14:32:57,842 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSSLListener Loading Identity Keystore from : lib/ide
ntity.jks
2009-08-03 14:32:57,842 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSSLListener Loading Trust Keystore from : lib/trust.
jks
2009-08-03 14:32:57,873 [-] [WrapperSimpleAppMain]  INFO JMSConnectionFactory JMS ConnectionFactory : default initialize
d
2009-08-03 14:32:57,873 [-] [WrapperSimpleAppMain]  INFO JMSListener JMS Transport Receiver/Listener initialized...
2009-08-03 14:32:57,873 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Loading mediator extensions...
2009-08-03 14:32:57,905 [-] [WrapperSimpleAppMain]  INFO XMLConfigurationBuilder Generating the Synapse configuration mo
del by parsing the XML configuration
2009-08-03 14:32:58,092 [-] [WrapperSimpleAppMain]  INFO SynapseConfigurationBuilder Loaded Synapse configuration from :
 G:\SYNAPS~1.0-S\bin\..\repository\conf\synapse.xml
2009-08-03 14:32:58,092 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Deploying the Synapse service...
2009-08-03 14:32:58,123 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Deploying Proxy services...
2009-08-03 14:32:58,123 [-] [WrapperSimpleAppMain]  INFO ProxyService Building Axis service for Proxy service : Receiver
QCF
2009-08-03 14:32:58,123 [-] [WrapperSimpleAppMain]  INFO ProxyService Adding service ReceiverQCF to the Axis2 configurat
ion
2009-08-03 14:32:58,123 [-] [WrapperSimpleAppMain]  INFO ProxyService Successfully created the Axis2 service for Proxy s
ervice : ReceiverQCF
2009-08-03 14:32:58,123 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Deployed Proxy service : ReceiverQCF
2009-08-03 14:32:58,123 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Deploying EventSources...
2009-08-03 14:32:58,155 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOListener HTTPS Listener started on port : 8243
2009-08-03 14:32:58,170 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOListener HTTP Listener started on port : 8280
2009-08-03 14:32:58,170 [-] [WrapperSimpleAppMain]  INFO VFSTransportListener VFS Listener started
2009-08-03 14:32:58,170 [-] [WrapperSimpleAppMain]  INFO MailTransportListener MAILTO Listener started
2009-08-03 14:32:58,170 [-] [WrapperSimpleAppMain]  INFO JMSListener JMS Listener started
2009-08-03 14:32:58,186 [-] [WrapperSimpleAppMain]  INFO ServiceTaskManager Task manager for service : ReceiverQCF [re-]
initialized
2009-08-03 14:32:58,483 [-] [jms-Worker-1] ERROR ServiceTaskManager Error creating JMS consumer for service : ReceiverQC
F
javax.jms.IllegalStateException: MQJMS1112: JMS1.1 Invalid operation for domain specific object
        at com.ibm.mq.jms.MQQueueSession.createConsumer(MQQueueSession.java:398)
        at org.apache.axis2.transport.jms.JMSUtils.createConsumer(JMSUtils.java:634)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConsumer(ServiceTaskManager.java:
835)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.getMessageConsumer(ServiceTaskManager.j
ava:706)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.receiveMessage(ServiceTaskManager.java:
474)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:405)
        at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
        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:595)
2009-08-03 14:32:58,483 [-] [jms-Worker-1] ERROR NativeWorkerPool Uncaught exception
org.apache.axis2.transport.jms.AxisJMSException: Error creating JMS consumer for service : ReceiverQCF
        at org.apache.axis2.transport.jms.ServiceTaskManager.handleException(ServiceTaskManager.java:959)
        at org.apache.axis2.transport.jms.ServiceTaskManager.access$700(ServiceTaskManager.java:48)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConsumer(ServiceTaskManager.java:
842)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.getMessageConsumer(ServiceTaskManager.j
ava:706)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.receiveMessage(ServiceTaskManager.java:
474)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:405)
        at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
        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:595)
Caused by: javax.jms.IllegalStateException: MQJMS1112: JMS1.1 Invalid operation for domain specific object
        at com.ibm.mq.jms.MQQueueSession.createConsumer(MQQueueSession.java:398)
        at org.apache.axis2.transport.jms.JMSUtils.createConsumer(JMSUtils.java:634)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConsumer(ServiceTaskManager.java:
835)
        ... 7 more
2009-08-03 14:33:01,186 [-] [WrapperSimpleAppMain]  WARN JMSListener Polling tasks on destination : MyReplyQueue of type
 Queue for service ReceiverQCF have not yet started after 3 seconds ..
2009-08-03 14:33:01,186 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Management using JMX available via: serv
ice:jmx:rmi:///jndi/rmi://sinpunap072:1099/synapse
2009-08-03 14:33:01,186 [-] [WrapperSimpleAppMain]  INFO ServerManager Server ready for processing...
2009-08-03 14:33:01,186 [-] [WrapperSimpleAppMain]  INFO SynapseServer Apache Synapse started successfully

2009-08-03 13:21:55,159 [-] [WrapperSimpleAppMain]  INFO JMSSender JMS Sender started
2009-08-03 13:21:55,299 [-] [WrapperSimpleAppMain]  INFO JMSConnectionFactory JMS ConnectionFactory : default initialize
d
2009-08-03 13:21:55,299 [-] [WrapperSimpleAppMain]  INFO JMSSender JMS Transport Sender initialized...
2009-08-03 13:21:55,393 [-] [WrapperSimpleAppMain]  WARN JmxAdapter Using unsecured JMX remote access!
2009-08-03 13:21:55,596 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSSLListener Loading Identity Keystore from : lib/ide
ntity.jks
2009-08-03 13:21:55,596 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSSLListener Loading Trust Keystore from : lib/trust.
jks
2009-08-03 13:21:55,627 [-] [WrapperSimpleAppMain]  INFO JMSConnectionFactory JMS ConnectionFactory : default initialize
d
2009-08-03 13:21:55,627 [-] [WrapperSimpleAppMain]  INFO JMSListener JMS Transport Receiver/Listener initialized...
2009-08-03 13:21:55,627 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Loading mediator extensions...
2009-08-03 13:21:55,674 [-] [WrapperSimpleAppMain]  INFO XMLConfigurationBuilder Generating the Synapse configuration mo
del by parsing the XML configuration
2009-08-03 13:21:55,862 [-] [WrapperSimpleAppMain]  INFO SynapseConfigurationBuilder Loaded Synapse configuration from :
 G:\B2BPRO~1\SYNAPS~1.0-S\bin\..\repository\conf\synapse.xml
2009-08-03 13:21:55,862 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Deploying the Synapse service...
2009-08-03 13:21:55,893 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Deploying Proxy services...
2009-08-03 13:21:55,893 [-] [WrapperSimpleAppMain]  INFO ProxyService Building Axis service for Proxy service : Receiver
QCF
2009-08-03 13:21:55,893 [-] [WrapperSimpleAppMain]  INFO ProxyService Adding service ReceiverQCF to the Axis2 configurat
ion
2009-08-03 13:21:55,893 [-] [WrapperSimpleAppMain]  INFO ProxyService Successfully created the Axis2 service for Proxy s
ervice : ReceiverQCF
2009-08-03 13:21:55,893 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Deployed Proxy service : ReceiverQCF
2009-08-03 13:21:55,893 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Deploying EventSources...
2009-08-03 13:21:55,924 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOListener HTTPS Listener started on port : 8243
2009-08-03 13:21:55,924 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOListener HTTP Listener started on port : 8280
2009-08-03 13:21:55,924 [-] [WrapperSimpleAppMain]  INFO VFSTransportListener VFS Listener started
2009-08-03 13:21:55,924 [-] [WrapperSimpleAppMain]  INFO MailTransportListener MAILTO Listener started
2009-08-03 13:21:55,924 [-] [WrapperSimpleAppMain]  INFO JMSListener JMS Listener started
2009-08-03 13:21:55,940 [-] [WrapperSimpleAppMain]  INFO ServiceTaskManager Task manager for service : ReceiverQCF [re-]
initialized
2009-08-03 13:21:55,940 [-] [WrapperSimpleAppMain]  INFO JMSListener Started to listen on destination : MyMDBQueue of ty
pe Queue for service ReceiverQCF
2009-08-03 13:21:55,955 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Management using JMX available via: serv
ice:jmx:rmi:///jndi/rmi://sinpunap072:1099/synapse
2009-08-03 13:21:55,955 [-] [WrapperSimpleAppMain]  INFO ServerManager Server ready for processing...
2009-08-03 13:21:55,955 [-] [WrapperSimpleAppMain]  INFO SynapseServer Apache Synapse started successfully
2009-08-03 13:21:56,330 [-] [jms-Worker-1] ERROR ServiceTaskManager Error creating JMS consumer for service : ReceiverQC
F

        at com.ibm.mq.jms.MQQueueSession.createConsumer(MQQueueSession.java:398)
        at org.apache.axis2.transport.jms.JMSUtils.createConsumer(JMSUtils.java:634)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConsumer(ServiceTaskManager.java:
835)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.getMessageConsumer(ServiceTaskManager.j
ava:706)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.receiveMessage(ServiceTaskManager.java:
474)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:405)
        at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
        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:595)
2009-08-03 13:21:56,330 [-] [jms-Worker-1] ERROR NativeWorkerPool Uncaught exception
org.apache.axis2.transport.jms.AxisJMSException: Error creating JMS consumer for service : ReceiverQCF
        at org.apache.axis2.transport.jms.ServiceTaskManager.handleException(ServiceTaskManager.java:959)
        at org.apache.axis2.transport.jms.ServiceTaskManager.access$700(ServiceTaskManager.java:48)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConsumer(ServiceTaskManager.java:
842)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.getMessageConsumer(ServiceTaskManager.j
ava:706)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.receiveMessage(ServiceTaskManager.java:
474)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:405)
        at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
        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:595)
Caused by: javax.jms.IllegalStateException: MQJMS1112: JMS1.1 Invalid operation for domain specific object
        at com.ibm.mq.jms.MQQueueSession.createConsumer(MQQueueSession.java:398)
        at org.apache.axis2.transport.jms.JMSUtils.createConsumer(JMSUtils.java:634)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConsumer(ServiceTaskManager.java:
835)
        ... 7 more

RE: Synapse ESB and IBM MQ issue

by Sunil.2.Tiwari :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hi,

Attaching log by increasing log level.

Any idea how to over come/handle this MQ related error.

Thanks,

 

Thanks & Regards

Sunil Kumar Tiwari | Tech Mahindra Ltd.

(Office: 009120 6641 7136  Mobile: 0091 9767644210)

Email: sunil.tiwari2@...

 


From: Sunil.2.Tiwari [mailto:st0031200@...]
Sent: Monday, August 03, 2009 10:18 PM
To: user@...
Subject: RE: Synapse ESB and IBM MQ issue

 

Hi,

I am getting exception while deploying MQ-Queue listener proxy service. Using latest synapse built for development. When trying to deploy proxy service getting attached error.

Proxy Service Synapse.xml::

<definitions xmlns="http://ws.apache.org/ns/synapse">

 <proxy name="ReceiverQCFPS" transports="jms" startOnLoad="true" statistics="enable">

    <parameter name="transport.jms.Destination">MyMDBQueue</parameter>

        <target>

            <inSequence>

              <log level="full" separator=", "/>

            <drop/>

            </inSequence>

          </target>

        </proxy>

</definitions>

 

Eception snap shot (PFA for complete log)::

2009-08-03 15:00:32,218 [-] [jms-Worker-1] ERROR ServiceTaskManager Error creating JMS consumer for service : ReceiverQC

FPS

javax.jms.IllegalStateException: MQJMS1112: JMS1.1 Invalid operation for domain specific object

        at com.ibm.mq.jms.MQQueueSession.createConsumer(MQQueueSession.java:398)

        at org.apache.axis2.transport.jms.JMSUtils.createConsumer(JMSUtils.java:634)

        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConsumer(ServiceTaskManager.java:

835)

 

Any idea how overcome this exception.

 

Thanks & Regards

Sunil Kumar Tiwari | Tech Mahindra Ltd.

(Office: 009120 6641 7136  Mobile: 0091 9767644210)

Email: sunil.tiwari2@...

 

-----Original Message-----
From: Asankha Perera [mailto:asankha.apache@...] On Behalf Of Asankha C. Perera
Sent: Saturday, August 01, 2009 8:50 PM
To: user@...
Subject: Re: Synapse ESB and IBM MQ issue

 

Hi Sunil

> 

> Could you please detail how can I use the latest stable build to

> upgrade Synapse version (Steps)?

> 

None in particular.. just extract the last nightly build from the

location I specified, extract the Zip file, and just change the

synapse.xml found at the same place as before in the 1.2 release

> 

> So that I overcome MQ-JMS connection factory name/ destination queue

> name mismatch problem.

> 

If you hit any issues, do keep the user@ list informed, so you do not

need to Cc: emails direct to me

 

cheers

asankha

 

--

Asankha C. Perera

AdroitLogic, http://adroitlogic.org

 

http://esbmagic.blogspot.com

 

 

 

 

============================================================================================================================


Disclaimer:

This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally and http://tim.techmahindra.com/Disclaimer.html internally within Tech Mahindra.

============================================================================================================================
============================================================================================================================


Disclaimer:

This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally and http://tim.techmahindra.com/Disclaimer.html internally within Tech Mahindra.

============================================================================================================================


G:\B2BProgramFiles\synapse-1.4.0-SNAPSHOT\bin>synapse.bat
"Starting Synapse/Java ..."
Using SYNAPSE_HOME:        G:\B2BPRO~1\SYNAPS~1.0-S\bin\..
Using JAVA_HOME:       G:\B2BProgramFiles\jdk160_05
--> Wrapper Started as Console
Launching a JVM...
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
  Copyright 1999-2006 Tanuki Software, Inc.  All Rights Reserved.

2009-08-04 07:16:19,796 [-] [WrapperSimpleAppMain]  INFO SynapseServer Starting Apache Synapse...
2009-08-04 07:16:19,812 [-] [WrapperSimpleAppMain]  INFO SynapseControllerFactory Using Synapse home : G:\B2BPRO~1\SYNAP
S~1.0-S\.
2009-08-04 07:16:19,812 [-] [WrapperSimpleAppMain]  INFO SynapseControllerFactory Using Axis2 repository : G:\B2BPRO~1\S
YNAPS~1.0-S\repository
2009-08-04 07:16:19,812 [-] [WrapperSimpleAppMain]  INFO SynapseControllerFactory Using axis2.xml location : G:\B2BPRO~1
\SYNAPS~1.0-S\repository\conf\axis2.xml
2009-08-04 07:16:19,812 [-] [WrapperSimpleAppMain]  INFO SynapseControllerFactory Using synapse.xml location : G:\B2BPRO
~1\SYNAPS~1.0-S\bin\..\repository\conf\synapse.xml
2009-08-04 07:16:19,812 [-] [WrapperSimpleAppMain]  INFO SynapseControllerFactory Using server name : localhost
2009-08-04 07:16:19,812 [-] [WrapperSimpleAppMain] DEBUG SynapseControllerFactory Using Server Configuration As : [ Serv
er Name : localhost ][ Synapse Home : . ][ Synapse XML : G:\B2BPRO~1\SYNAPS~1.0-S\bin\..\repository\conf\synapse.xml ][
Server Host : localhost][ Axis2 Repository : repository ][ Axis2 XML : repository/conf/
axis2.xml ]
2009-08-04 07:16:19,828 [-] [WrapperSimpleAppMain] DEBUG SynapsePropertiesLoader Loading synapse properties from a prope
rty file
2009-08-04 07:16:19,828 [-] [WrapperSimpleAppMain] DEBUG MiscellaneousUtil Loading a file ' synapse.properties ' from cl
asspath
2009-08-04 07:16:19,843 [-] [WrapperSimpleAppMain] DEBUG MiscellaneousUtil The name with ' synapse.timeout_handler_inter
val ' cannot be found. Using default value 15000
2009-08-04 07:16:19,843 [-] [WrapperSimpleAppMain]  INFO SynapseControllerFactory The timeout handler will run every : 1
5s
2009-08-04 07:16:19,906 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Initializing Synapse at : Tue Aug 04 07:
16:19 BST 2009
2009-08-04 07:16:19,906 [-] [WrapperSimpleAppMain] DEBUG Axis2SynapseController Initializing Synapse in a new axis2 serv
er environment instance
2009-08-04 07:16:21,203 [-] [WrapperSimpleAppMain] ERROR SandeshaModule Could not load module policies. Using default va
lues.
2009-08-04 07:16:21,234 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSSLSender Loading Identity Keystore from : lib/ident
ity.jks
2009-08-04 07:16:21,250 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSSLSender Loading Trust Keystore from : lib/trust.jk
s
2009-08-04 07:16:21,390 [-] [WrapperSimpleAppMain] DEBUG NativeWorkerPool Using native util.concurrent package..
2009-08-04 07:16:21,390 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSSLSender Loading custom SSL profiles for the HTTPS
sender
2009-08-04 07:16:21,390 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSender HTTPS Sender starting
2009-08-04 07:16:21,406 [-] [WrapperSimpleAppMain] DEBUG NativeWorkerPool Using native util.concurrent package..
2009-08-04 07:16:21,406 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSender HTTP Sender starting
2009-08-04 07:16:21,406 [-] [WrapperSimpleAppMain]  INFO VFSTransportSender VFS Sender started
2009-08-04 07:16:21,546 [-] [WrapperSimpleAppMain]  INFO JMSSender JMS Sender started
2009-08-04 07:16:21,687 [-] [WrapperSimpleAppMain]  INFO JMSConnectionFactory JMS ConnectionFactory : default initialize
d
2009-08-04 07:16:21,687 [-] [WrapperSimpleAppMain]  INFO JMSSender JMS Transport Sender initialized...
2009-08-04 07:16:21,687 [-] [WrapperSimpleAppMain] DEBUG SynapsePropertiesLoader Retrieving synapse properties from the
cache
2009-08-04 07:16:21,687 [-] [WrapperSimpleAppMain] DEBUG MiscellaneousUtil The name with ' synapse.jmx.rmiPort ' cannot
be found. Using default value 0
2009-08-04 07:16:21,687 [-] [WrapperSimpleAppMain] DEBUG MiscellaneousUtil The name with ' synapse.jmx.remote.ssl ' cann
ot be found. Using default value false
2009-08-04 07:16:21,703 [-] [WrapperSimpleAppMain]  WARN JmxAdapter Using unsecured JMX remote access!
2009-08-04 07:16:21,750 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSSLListener Loading Identity Keystore from : lib/ide
ntity.jks
2009-08-04 07:16:21,750 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSSLListener Loading Trust Keystore from : lib/trust.
jks
2009-08-04 07:16:21,750 [-] [WrapperSimpleAppMain] DEBUG NativeWorkerPool Using native util.concurrent package..
2009-08-04 07:16:21,781 [-] [WrapperSimpleAppMain] DEBUG NativeWorkerPool Using native util.concurrent package..
2009-08-04 07:16:21,781 [-] [WrapperSimpleAppMain] DEBUG NativeWorkerPool Using native util.concurrent package..
2009-08-04 07:16:21,781 [-] [WrapperSimpleAppMain]  INFO JMSConnectionFactory JMS ConnectionFactory : default initialize
d
2009-08-04 07:16:21,781 [-] [WrapperSimpleAppMain]  INFO JMSListener JMS Transport Receiver/Listener initialized...
2009-08-04 07:16:21,781 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Loading mediator extensions...
2009-08-04 07:16:21,781 [-] [WrapperSimpleAppMain] DEBUG TaskDescriptionRepositoryFactory Creating a TaskDescriptionRepo
sitory with id : task_description_repository
2009-08-04 07:16:21,796 [-] [WrapperSimpleAppMain] DEBUG SynapsePropertiesLoader Reloading synapse properties
2009-08-04 07:16:21,796 [-] [WrapperSimpleAppMain] DEBUG SynapsePropertiesLoader Loading synapse properties from a prope
rty file
2009-08-04 07:16:21,796 [-] [WrapperSimpleAppMain] DEBUG MiscellaneousUtil Loading a file ' synapse.properties ' from cl
asspath
2009-08-04 07:16:21,812 [-] [WrapperSimpleAppMain] DEBUG DataSourceInformationRepositoryFactory Creating a new DataSourc
eInformationRepository
2009-08-04 07:16:21,812 [-] [WrapperSimpleAppMain] DEBUG DataSourceInformationListFactory No DataSources defined for ini
tialization..
2009-08-04 07:16:21,812 [-] [WrapperSimpleAppMain]  INFO XMLConfigurationBuilder Generating the Synapse configuration mo
del by parsing the XML configuration
2009-08-04 07:16:21,828 [-] [WrapperSimpleAppMain] DEBUG ConfigurationFactoryAndSerializerFinder getConfiguration({http:
//ws.apache.org/ns/synapse}definitions)
2009-08-04 07:16:21,828 [-] [WrapperSimpleAppMain] DEBUG TaskDescriptionRepositoryFactory Creating a TaskDescriptionRepo
sitory with id : synapse.startup.taskdescriptions.repository
2009-08-04 07:16:21,828 [-] [WrapperSimpleAppMain] DEBUG SynapsePropertiesLoader Retrieving synapse properties from the
cache
2009-08-04 07:16:21,937 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder Added MediatorFactory class org.apache.sy
napse.experimental.DetachMediatorFactory to handle {http://ws.apache.org/ns/synapse}detach
2009-08-04 07:16:21,937 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder Added MediatorFactory class org.apache.sy
napse.experimental.ReplaceMediatorFactory to handle {http://ws.apache.org/ns/synapse}replace
2009-08-04 07:16:21,953 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder Added MediatorFactory class org.apache.sy
napse.mediators.spring.SpringMediatorFactory to handle {http://ws.apache.org/ns/synapse/spring}spring
2009-08-04 07:16:21,953 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder Added MediatorFactory class org.apache.sy
napse.mediators.bsf.ScriptMediatorFactory to handle {http://ws.apache.org/ns/synapse}script
2009-08-04 07:16:21,953 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder Added MediatorFactory class org.apache.sy
napse.mediators.throttle.ThrottleMediatorFactory to handle {http://ws.apache.org/ns/synapse}throttle
2009-08-04 07:16:21,953 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder Added MediatorFactory class org.apache.sy
napse.mediators.xquery.XQueryMediatorFactory to handle {http://ws.apache.org/ns/synapse}xquery
2009-08-04 07:16:21,953 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder getMediator({http://ws.apache.org/ns/syna
pse}log)
2009-08-04 07:16:21,953 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder getMediator({http://ws.apache.org/ns/syna
pse}drop)
2009-08-04 07:16:22,000 [-] [WrapperSimpleAppMain]  INFO SynapseConfigurationBuilder Loaded Synapse configuration from :
 G:\B2BPRO~1\SYNAPS~1.0-S\bin\..\repository\conf\synapse.xml
2009-08-04 07:16:22,000 [-] [WrapperSimpleAppMain] DEBUG SynapsePropertiesLoader Retrieving synapse properties from the
cache
2009-08-04 07:16:22,000 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Deploying the Synapse service...
2009-08-04 07:16:22,031 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Deploying Proxy services...
2009-08-04 07:16:22,031 [-] [WrapperSimpleAppMain]  INFO ProxyService Building Axis service for Proxy service : Receiver
QCFPS
2009-08-04 07:16:22,031 [-] [WrapperSimpleAppMain]  INFO ProxyService Adding service ReceiverQCFPS to the Axis2 configur
ation
2009-08-04 07:16:22,031 [-] [WrapperSimpleAppMain]  INFO ProxyService Successfully created the Axis2 service for Proxy s
ervice : ReceiverQCFPS
2009-08-04 07:16:22,031 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Deployed Proxy service : ReceiverQCFPS
2009-08-04 07:16:22,031 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Deploying EventSources...
2009-08-04 07:16:22,031 [-] [WrapperSimpleAppMain] DEBUG SynapseConfiguration Initializing the Synapse Configuration usi
ng the SynapseEnvironment
2009-08-04 07:16:22,031 [-] [WrapperSimpleAppMain] DEBUG SequenceMediator Initializing child mediators of mediator : Seq
uenceMediator
2009-08-04 07:16:22,031 [-] [WrapperSimpleAppMain] DEBUG SequenceMediator Initializing child mediators of mediator : Seq
uenceMediator
2009-08-04 07:16:22,031 [-] [WrapperSimpleAppMain] DEBUG SequenceMediator Initializing child mediators of mediator : Seq
uenceMediator
2009-08-04 07:16:22,031 [-] [WrapperSimpleAppMain] DEBUG HttpCoreNIOListener Starting Listener...
2009-08-04 07:16:22,046 [-] [WrapperSimpleAppMain] DEBUG NativeWorkerPool Using native util.concurrent package..
2009-08-04 07:16:22,062 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOListener HTTPS Listener started on port : 8243
2009-08-04 07:16:22,062 [-] [WrapperSimpleAppMain] DEBUG HttpCoreNIOListener Starting Listener...
2009-08-04 07:16:22,062 [-] [WrapperSimpleAppMain] DEBUG NativeWorkerPool Using native util.concurrent package..
2009-08-04 07:16:22,078 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOListener HTTP Listener started on port : 8280
2009-08-04 07:16:22,078 [-] [WrapperSimpleAppMain]  INFO VFSTransportListener VFS Listener started
2009-08-04 07:16:22,078 [-] [WrapperSimpleAppMain]  INFO MailTransportListener MAILTO Listener started
2009-08-04 07:16:22,078 [-] [WrapperSimpleAppMain]  INFO JMSListener JMS Listener started
2009-08-04 07:16:22,078 [-] [WrapperSimpleAppMain] DEBUG JMSEndpoint JMS destination type not given. default queue
2009-08-04 07:16:22,078 [-] [WrapperSimpleAppMain] DEBUG ServiceTaskManager The JMS Connection, Session and MessageConsu
mer will be cached and shared between successive poller task invocations
2009-08-04 07:16:22,093 [-] [WrapperSimpleAppMain]  INFO ServiceTaskManager Task manager for service : ReceiverQCFPS [re
-]initialized
2009-08-04 07:16:22,093 [-] [jms-Worker-1] DEBUG ServiceTaskManager New poll task starting : thread id = 45
2009-08-04 07:16:22,093 [-] [jms-Worker-1] DEBUG ServiceTaskManager Connected to the JMS connection factory : ReceiverQC
F
2009-08-04 07:16:22,093 [-] [jms-Worker-1] DEBUG JMSUtils Creating a QueueConnection using credentials : (null/null)
2009-08-04 07:16:22,359 [-] [jms-Worker-1] DEBUG ServiceTaskManager JMS Connection for service : ReceiverQCFPS created a
nd started
2009-08-04 07:16:22,359 [-] [jms-Worker-1] DEBUG ServiceTaskManager Creating a new JMS Session for service : ReceiverQCF
PS
2009-08-04 07:16:22,375 [-] [jms-Worker-1] DEBUG ServiceTaskManager Creating a new JMS MessageConsumer for service : Rec
eiverQCFPS
2009-08-04 07:16:22,390 [-] [jms-Worker-1] DEBUG ServiceTaskManager JMS Destination with JNDI name : MyMDBQueue found fo
r service ReceiverQCFPS
2009-08-04 07:16:22,390 [-] [jms-Worker-1] ERROR ServiceTaskManager Error creating JMS consumer for service : ReceiverQC
FPS
javax.jms.IllegalStateException: MQJMS1112: JMS1.1 Invalid operation for domain specific object
        at com.ibm.mq.jms.MQQueueSession.createConsumer(MQQueueSession.java:398)
        at org.apache.axis2.transport.jms.JMSUtils.createConsumer(JMSUtils.java:634)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConsumer(ServiceTaskManager.java:
835)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.getMessageConsumer(ServiceTaskManager.j
ava:706)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.receiveMessage(ServiceTaskManager.java:
474)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:405)
        at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
        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:595)
2009-08-04 07:16:22,390 [-] [jms-Worker-1] ERROR NativeWorkerPool Uncaught exception
org.apache.axis2.transport.jms.AxisJMSException: Error creating JMS consumer for service : ReceiverQCFPS
        at org.apache.axis2.transport.jms.ServiceTaskManager.handleException(ServiceTaskManager.java:959)
        at org.apache.axis2.transport.jms.ServiceTaskManager.access$700(ServiceTaskManager.java:48)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConsumer(ServiceTaskManager.java:
842)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.getMessageConsumer(ServiceTaskManager.j
ava:706)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.receiveMessage(ServiceTaskManager.java:
474)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:405)
        at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
        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:595)
Caused by: javax.jms.IllegalStateException: MQJMS1112: JMS1.1 Invalid operation for domain specific object
        at com.ibm.mq.jms.MQQueueSession.createConsumer(MQQueueSession.java:398)
        at org.apache.axis2.transport.jms.JMSUtils.createConsumer(JMSUtils.java:634)
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConsumer(ServiceTaskManager.java:
835)
        ... 7 more
2009-08-04 07:16:25,093 [-] [WrapperSimpleAppMain]  WARN JMSListener Polling tasks on destination : MyMDBQueue of type Q
ueue for service ReceiverQCFPS have not yet started after 3 seconds ..
2009-08-04 07:16:25,093 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Management using JMX available via: serv
ice:jmx:rmi:///jndi/rmi://sinpunap072:1099/synapse
2009-08-04 07:16:25,093 [-] [WrapperSimpleAppMain]  INFO ServerManager Server ready for processing...
2009-08-04 07:16:25,093 [-] [WrapperSimpleAppMain]  INFO SynapseServer Apache Synapse started successfully

Re: Synapse ESB and IBM MQ issue

by Asankha C. Perera :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Sunil
> Attaching log by increasing log level.
>
> Any idea how to over come/handle this MQ related error.
>
Seems like a basic JMS consumer creation error.. thus could you try to
run the simple producer and consumer as per [1] against your MQ provider
with the same configuration you've used for Synapse? Once thats working,
it will be simpler to copy any tweaked parameters/settings to Synapse
more easily

cheers
asankha

[1] http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JMS5.html
Esp
http://java.sun.com/j2ee/1.4/docs/tutorial/examples/jms/simple/src/SimpleSynchConsumer.java
and the SimpleProducer

--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org

http://esbmagic.blogspot.com





RE: Synapse ESB and IBM MQ issue

by Sunil.2.Tiwari :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Thanks Asankha
I got it resolved by adding JMS specification 1.0 in proxy service parameter.
MQ transport is working for me now.

Thanks & Regards
Sunil Kumar Tiwari | Tech Mahindra Ltd.
(Office: 009120 6641 7136  Mobile: 0091 9767644210)
Email: sunil.tiwari2@...

-----Original Message-----
From: Asankha Perera [mailto:asankha.apache@...] On Behalf Of Asankha C. Perera
Sent: Tuesday, August 04, 2009 8:50 PM
To: user@...
Subject: Re: Synapse ESB and IBM MQ issue

Hi Sunil
> Attaching log by increasing log level.
>
> Any idea how to over come/handle this MQ related error.
>
Seems like a basic JMS consumer creation error.. thus could you try to
run the simple producer and consumer as per [1] against your MQ provider
with the same configuration you've used for Synapse? Once thats working,
it will be simpler to copy any tweaked parameters/settings to Synapse
more easily

cheers
asankha

[1] http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JMS5.html
Esp
http://java.sun.com/j2ee/1.4/docs/tutorial/examples/jms/simple/src/SimpleSynchConsumer.java
and the SimpleProducer

--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org

http://esbmagic.blogspot.com





============================================================================================================================

 
Disclaimer:

This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at <a href="http://www.techmahindra.com/Disclaimer.html">http://www.techmahindra.com/Disclaimer.html</a> externally and <a href="http://tim.techmahindra.com/Disclaimer.html">http://tim.techmahindra.com/Disclaimer.html</a> internally within Tech Mahindra.

============================================================================================================================

Re: Synapse ESB and IBM MQ issue

by Asankha C. Perera :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Sunil
> Thanks Asankha
> I got it resolved by adding JMS specification 1.0 in proxy service parameter.
> MQ transport is working for me now.
>  
Good to hear!

cheers
asankha

--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org

http://esbmagic.blogspot.com





Synapse ESB and IBM MQ sender issue

by Sunil.2.Tiwari :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Hello everybody,
I am trying to read (enqueu) message from MQ queue and post(dequeue) it into response MQ queue.
Getting exception (PFA for exception) over Synapse ESB console for proxy service when PS is trying to post (dequeue) message to MQ response queue.
Proxy Service Synapse.xml:
<definitions xmlns="http://ws.apache.org/ns/synapse">
 <proxy name="ReceiverQCFPS" transports="jms" startOnLoad="true" statistics="enable">
   <parameter name="transport.jms.JMSSpecVersion">1.0</parameter>
    <parameter name="transport.jms.Destination">MyMDBQueue</parameter>
        <parameter name="transport.PollInterval">15</parameter>
          <target>
            <inSequence>            
              <log level="full" separator=", "/>
              <property action="set" name="OUT_ONLY" value="true"/>
            </inSequence>
   <endpoint>
   <address  uri="jms:/MyReplyQueue?transport.jms.ConnectionFactoryJNDIName=SenderQCF&java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory&java.naming.provider.url=file:/C:/JNDI-Directory&transport.jms.ConnectionFactoryType=queue"/>
   </endpoint>
        <outSequence>
        <log level="full" separator=", "/>
             <send/>
         <log level="full" separator=", "/>
         </outSequence>
        </target>      
</proxy>
</definitions>

Any idea where is the problem.

Thanks & Regards
Sunil Kumar Tiwari | I&B2B | Tech Mahindra Ltd.
(Office: 009120 6641 7136  Mobile: 0091 9767644210)
Email: sunil.tiwari2@...


============================================================================================================================

 
Disclaimer:

This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at <a href="http://www.techmahindra.com/Disclaimer.html">http://www.techmahindra.com/Disclaimer.html</a> externally and <a href="http://tim.techmahindra.com/Disclaimer.html">http://tim.techmahindra.com/Disclaimer.html</a> internally within Tech Mahindra.

============================================================================================================================

G:\B2BProgramFiles\synapse-1.4.0-SNAPSHOT\bin>synapse.bat
"Starting Synapse/Java ..."
Using SYNAPSE_HOME:        G:\B2BPRO~1\SYNAPS~1.0-S\bin\..
Using JAVA_HOME:       C:\jdk
--> Wrapper Started as Console
Launching a JVM...
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
  Copyright 1999-2006 Tanuki Software, Inc.  All Rights Reserved.

2009-08-05 11:40:13,296 [-] [WrapperSimpleAppMain]  INFO SynapseServer Starting Apache Synapse...
2009-08-05 11:40:13,311 [-] [WrapperSimpleAppMain]  INFO SynapseControllerFactory Using Synapse home : G:\B2BPRO~1\SYNAP
S~1.0-S\.
2009-08-05 11:40:13,311 [-] [WrapperSimpleAppMain]  INFO SynapseControllerFactory Using Axis2 repository : G:\B2BPRO~1\S
YNAPS~1.0-S\repository
2009-08-05 11:40:13,311 [-] [WrapperSimpleAppMain]  INFO SynapseControllerFactory Using axis2.xml location : G:\B2BPRO~1
\SYNAPS~1.0-S\repository\conf\axis2.xml
2009-08-05 11:40:13,311 [-] [WrapperSimpleAppMain]  INFO SynapseControllerFactory Using synapse.xml location : G:\B2BPRO
~1\SYNAPS~1.0-S\bin\..\repository\conf\synapse.xml
2009-08-05 11:40:13,311 [-] [WrapperSimpleAppMain]  INFO SynapseControllerFactory Using server name : localhost
2009-08-05 11:40:13,327 [-] [WrapperSimpleAppMain] DEBUG SynapseControllerFactory Using Server Configuration As : [ Serv
er Name : localhost ][ Synapse Home : . ][ Synapse XML : G:\B2BPRO~1\SYNAPS~1.0-S\bin\..\repository\conf\synapse.xml ][
Server Host : sinpunap072 ][ Server IP : 172.24.182.114 ][ Axis2 Repository : repository ][ Axis2 XML : repository/conf/
axis2.xml ]
2009-08-05 11:40:13,327 [-] [WrapperSimpleAppMain] DEBUG SynapsePropertiesLoader Loading synapse properties from a prope
rty file
2009-08-05 11:40:13,343 [-] [WrapperSimpleAppMain] DEBUG MiscellaneousUtil Loading a file ' synapse.properties ' from cl
asspath
2009-08-05 11:40:13,343 [-] [WrapperSimpleAppMain] DEBUG MiscellaneousUtil The name with ' synapse.timeout_handler_inter
val ' cannot be found. Using default value 15000
2009-08-05 11:40:13,343 [-] [WrapperSimpleAppMain]  INFO SynapseControllerFactory The timeout handler will run every : 1
5s
2009-08-05 11:40:13,390 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Initializing Synapse at : Wed Aug 05 11:
40:13 BST 2009
2009-08-05 11:40:13,390 [-] [WrapperSimpleAppMain] DEBUG Axis2SynapseController Initializing Synapse in a new axis2 serv
er environment instance
2009-08-05 11:40:14,390 [-] [WrapperSimpleAppMain] ERROR SandeshaModule Could not load module policies. Using default va
lues.
2009-08-05 11:40:14,405 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSSLSender Loading Identity Keystore from : lib/ident
ity.jks
2009-08-05 11:40:14,421 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSSLSender Loading Trust Keystore from : lib/trust.jk
s
2009-08-05 11:40:14,530 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSSLSender Loading custom SSL profiles for the HTTPS
sender
2009-08-05 11:40:14,530 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSender HTTPS Sender starting
2009-08-05 11:40:14,546 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSender HTTP Sender starting
2009-08-05 11:40:14,546 [-] [WrapperSimpleAppMain]  INFO VFSTransportSender VFS Sender started
2009-08-05 11:40:14,686 [-] [WrapperSimpleAppMain]  INFO JMSSender JMS Sender started
2009-08-05 11:40:14,811 [-] [WrapperSimpleAppMain]  INFO JMSConnectionFactory JMS ConnectionFactory : default initialize
d
2009-08-05 11:40:14,811 [-] [WrapperSimpleAppMain]  INFO JMSSender JMS Transport Sender initialized...
2009-08-05 11:40:14,811 [-] [WrapperSimpleAppMain] DEBUG SynapsePropertiesLoader Retrieving synapse properties from the
cache
2009-08-05 11:40:14,827 [-] [WrapperSimpleAppMain] DEBUG MiscellaneousUtil The name with ' synapse.jmx.rmiPort ' cannot
be found. Using default value 0
2009-08-05 11:40:14,827 [-] [WrapperSimpleAppMain] DEBUG MiscellaneousUtil The name with ' synapse.jmx.remote.ssl ' cann
ot be found. Using default value false
2009-08-05 11:40:14,827 [-] [WrapperSimpleAppMain]  WARN JmxAdapter Using unsecured JMX remote access!
2009-08-05 11:40:14,874 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSSLListener Loading Identity Keystore from : lib/ide
ntity.jks
2009-08-05 11:40:14,874 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSSLListener Loading Trust Keystore from : lib/trust.
jks
2009-08-05 11:40:14,905 [-] [WrapperSimpleAppMain]  INFO JMSConnectionFactory JMS ConnectionFactory : default initialize
d
2009-08-05 11:40:14,905 [-] [WrapperSimpleAppMain]  INFO JMSListener JMS Transport Receiver/Listener initialized...
2009-08-05 11:40:14,905 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Loading mediator extensions...
2009-08-05 11:40:14,905 [-] [WrapperSimpleAppMain] DEBUG TaskDescriptionRepositoryFactory Creating a TaskDescriptionRepo
sitory with id : task_description_repository
2009-08-05 11:40:14,921 [-] [WrapperSimpleAppMain] DEBUG SynapsePropertiesLoader Reloading synapse properties
2009-08-05 11:40:14,921 [-] [WrapperSimpleAppMain] DEBUG SynapsePropertiesLoader Loading synapse properties from a prope
rty file
2009-08-05 11:40:14,921 [-] [WrapperSimpleAppMain] DEBUG MiscellaneousUtil Loading a file ' synapse.properties ' from cl
asspath
2009-08-05 11:40:14,921 [-] [WrapperSimpleAppMain] DEBUG DataSourceInformationRepositoryFactory Creating a new DataSourc
eInformationRepository
2009-08-05 11:40:14,936 [-] [WrapperSimpleAppMain] DEBUG DataSourceInformationListFactory No DataSources defined for ini
tialization..
2009-08-05 11:40:14,936 [-] [WrapperSimpleAppMain]  INFO XMLConfigurationBuilder Generating the Synapse configuration mo
del by parsing the XML configuration
2009-08-05 11:40:14,936 [-] [WrapperSimpleAppMain] DEBUG ConfigurationFactoryAndSerializerFinder getConfiguration({http:
//ws.apache.org/ns/synapse}definitions)
2009-08-05 11:40:14,952 [-] [WrapperSimpleAppMain] DEBUG TaskDescriptionRepositoryFactory Creating a TaskDescriptionRepo
sitory with id : synapse.startup.taskdescriptions.repository
2009-08-05 11:40:14,952 [-] [WrapperSimpleAppMain] DEBUG SynapsePropertiesLoader Retrieving synapse properties from the
cache
2009-08-05 11:40:15,061 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder Added MediatorFactory class org.apache.sy
napse.experimental.DetachMediatorFactory to handle {http://ws.apache.org/ns/synapse}detach
2009-08-05 11:40:15,061 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder Added MediatorFactory class org.apache.sy
napse.experimental.ReplaceMediatorFactory to handle {http://ws.apache.org/ns/synapse}replace
2009-08-05 11:40:15,061 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder Added MediatorFactory class org.apache.sy
napse.mediators.spring.SpringMediatorFactory to handle {http://ws.apache.org/ns/synapse/spring}spring
2009-08-05 11:40:15,061 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder Added MediatorFactory class org.apache.sy
napse.mediators.bsf.ScriptMediatorFactory to handle {http://ws.apache.org/ns/synapse}script
2009-08-05 11:40:15,061 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder Added MediatorFactory class org.apache.sy
napse.mediators.throttle.ThrottleMediatorFactory to handle {http://ws.apache.org/ns/synapse}throttle
2009-08-05 11:40:15,061 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder Added MediatorFactory class org.apache.sy
napse.mediators.xquery.XQueryMediatorFactory to handle {http://ws.apache.org/ns/synapse}xquery
2009-08-05 11:40:15,061 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder getMediator({http://ws.apache.org/ns/syna
pse}log)
2009-08-05 11:40:15,077 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder getMediator({http://ws.apache.org/ns/syna
pse}property)
2009-08-05 11:40:15,077 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder getMediator({http://ws.apache.org/ns/syna
pse}log)
2009-08-05 11:40:15,077 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder getMediator({http://ws.apache.org/ns/syna
pse}send)
2009-08-05 11:40:15,077 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder getMediator({http://ws.apache.org/ns/syna
pse}log)
2009-08-05 11:40:15,124 [-] [WrapperSimpleAppMain]  INFO SynapseConfigurationBuilder Loaded Synapse configuration from :
 G:\B2BPRO~1\SYNAPS~1.0-S\bin\..\repository\conf\synapse.xml
2009-08-05 11:40:15,124 [-] [WrapperSimpleAppMain] DEBUG SynapsePropertiesLoader Retrieving synapse properties from the
cache
2009-08-05 11:40:15,124 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Deploying the Synapse service...
2009-08-05 11:40:15,155 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Deploying Proxy services...
2009-08-05 11:40:15,155 [-] [WrapperSimpleAppMain]  INFO ProxyService Building Axis service for Proxy service : Receiver
QCFPS
2009-08-05 11:40:15,155 [-] [WrapperSimpleAppMain]  INFO ProxyService Adding service ReceiverQCFPS to the Axis2 configur
ation
2009-08-05 11:40:15,155 [-] [WrapperSimpleAppMain]  INFO ProxyService Successfully created the Axis2 service for Proxy s
ervice : ReceiverQCFPS
2009-08-05 11:40:15,155 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Deployed Proxy service : ReceiverQCFPS
2009-08-05 11:40:15,155 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Deploying EventSources...
2009-08-05 11:40:15,171 [-] [WrapperSimpleAppMain] DEBUG SynapseConfiguration Initializing the Synapse Configuration usi
ng the SynapseEnvironment
2009-08-05 11:40:15,171 [-] [WrapperSimpleAppMain] DEBUG SequenceMediator Initializing child mediators of mediator : Seq
uenceMediator
2009-08-05 11:40:15,171 [-] [WrapperSimpleAppMain] DEBUG SequenceMediator Initializing child mediators of mediator : Seq
uenceMediator
2009-08-05 11:40:15,171 [-] [WrapperSimpleAppMain] DEBUG SequenceMediator Initializing child mediators of mediator : Seq
uenceMediator
2009-08-05 11:40:15,171 [-] [WrapperSimpleAppMain] DEBUG SequenceMediator Initializing child mediators of mediator : Seq
uenceMediator
2009-08-05 11:40:15,171 [-] [WrapperSimpleAppMain] DEBUG HttpCoreNIOListener Starting Listener...
2009-08-05 11:40:15,202 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOListener HTTPS Listener started on port : 8243
2009-08-05 11:40:15,202 [-] [WrapperSimpleAppMain] DEBUG HttpCoreNIOListener Starting Listener...
2009-08-05 11:40:15,202 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOListener HTTP Listener started on port : 8280
2009-08-05 11:40:15,202 [-] [WrapperSimpleAppMain]  INFO VFSTransportListener VFS Listener started
2009-08-05 11:40:15,202 [-] [WrapperSimpleAppMain]  INFO MailTransportListener MAILTO Listener started
2009-08-05 11:40:15,202 [-] [WrapperSimpleAppMain]  INFO JMSListener JMS Listener started
2009-08-05 11:40:15,218 [-] [WrapperSimpleAppMain]  INFO ServiceTaskManager Task manager for service : ReceiverQCFPS [re
-]initialized
2009-08-05 11:40:15,218 [-] [WrapperSimpleAppMain]  INFO JMSListener Started to listen on destination : MyMDBQueue of ty
pe Queue for service ReceiverQCFPS
2009-08-05 11:40:15,218 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Management using JMX available via: serv
ice:jmx:rmi:///jndi/rmi://sinpunap072:1099/synapse
2009-08-05 11:40:15,218 [-] [WrapperSimpleAppMain]  INFO ServerManager Server ready for processing...
2009-08-05 11:40:15,218 [-] [WrapperSimpleAppMain]  INFO SynapseServer Apache Synapse started successfully
2009-08-05 11:40:26,562 [-] [jms-Worker-1] DEBUG ProxyServiceMessageReceiver Proxy Service ReceiverQCFPS received a new
message...
2009-08-05 11:40:26,562 [-] [jms-Worker-1] DEBUG ProxyServiceMessageReceiver Message To: null
2009-08-05 11:40:26,562 [-] [jms-Worker-1] DEBUG ProxyServiceMessageReceiver SOAPAction: urn:mediate
2009-08-05 11:40:26,562 [-] [jms-Worker-1] DEBUG ProxyServiceMessageReceiver WSA-Action: urn:mediate
2009-08-05 11:40:26,562 [-] [jms-Worker-1] DEBUG StatisticsReporter Setting statistics stack on the message context.
2009-08-05 11:40:26,562 [-] [jms-Worker-1] DEBUG StatisticsRecordFactory Created a StatisticsRecord with [Message id : I
D:414d512074657374716d677220202020c2ea764a20156202 ][Remote  IP : null ][Remote host : null ]
2009-08-05 11:40:26,562 [-] [jms-Worker-1] DEBUG StatisticsReporter Setting statistics collector in the synapse environm
ent.
2009-08-05 11:40:26,577 [-] [jms-Worker-1] DEBUG StatisticsRecord Start to reportForComponent statistics for : ReceiverQ
CFPS
2009-08-05 11:40:26,577 [-] [jms-Worker-1] DEBUG ProxyServiceMessageReceiver Using the anonymous in-sequence of the prox
y service for mediation
2009-08-05 11:40:26,577 [-] [jms-Worker-1] DEBUG SequenceMediator Start : Sequence <anonymous>
2009-08-05 11:40:26,577 [-] [jms-Worker-1] DEBUG SequenceMediator Sequence <SequenceMediator> :: mediate()
2009-08-05 11:40:26,577 [-] [jms-Worker-1] DEBUG LogMediator Start : Log mediator
2009-08-05 11:40:26,609 [-] [jms-Worker-1]  INFO LogMediator To: , WSAction: urn:mediate, SOAPAction: urn:mediate, Messa
geID: ID:414d512074657374716d677220202020c2ea764a20156202, Direction: request, Envelope: <?xml version='1.0' encoding='u
tf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><axis2ns1:text xmlns:ax
is2ns1="http://ws.apache.org/commons/ns/payload"><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/env
elope/" xmlns:ser="http://services.samples" xmlns:xsd="http://services.samples/xsd"><soapenv:Header/> <soapenv:Bod
y><ser:placeOrder> <ser:order><xsd:price>100</xsd:price><xsd:quantity>5</xsd:quantity> <xsd:symbol>
5</xsd:symbol></ser:order> </ser:placeOrder> </soapenv:Body></soapenv:Envelope></axis2ns1:text></soapenv:
Body></soapenv:Envelope>
2009-08-05 11:40:26,609 [-] [jms-Worker-1] DEBUG LogMediator End : Log mediator
2009-08-05 11:40:26,609 [-] [jms-Worker-1] DEBUG PropertyMediator Start : Property mediator
2009-08-05 11:40:26,609 [-] [jms-Worker-1] DEBUG PropertyMediator Setting property : OUT_ONLY at scope : default to : tr
ue (i.e. constant : true)
2009-08-05 11:40:26,609 [-] [jms-Worker-1] DEBUG PropertyMediator End : Property mediator
2009-08-05 11:40:26,609 [-] [jms-Worker-1] DEBUG SequenceMediator End : Sequence <anonymous>
2009-08-05 11:40:26,609 [-] [jms-Worker-1] DEBUG ProxyServiceMessageReceiver Forwarding the message to the anonymous end
point of the proxy service
2009-08-05 11:40:26,609 [-] [jms-Worker-1] DEBUG EndpointContext Checking if endpoint : AnonymousEndpoint currently at s
tate ACTIVE can be used now?
2009-08-05 11:40:26,609 [-] [jms-Worker-1] DEBUG AddressEndpoint Sending message through endpoint : null resolving to ad
dress = jms:/MyReplyQueue?transport.jms.ConnectionFactoryJNDIName=SenderQCF&java.naming.factory.initial=com.sun.jndi.fsc
ontext.RefFSContextFactory&java.naming.provider.url=file:/C:/JNDI-Directory&transport.jms.ConnectionFactoryType=queue
2009-08-05 11:40:26,609 [-] [jms-Worker-1] DEBUG AddressEndpoint SOAPAction: urn:mediate
2009-08-05 11:40:26,609 [-] [jms-Worker-1] DEBUG AddressEndpoint WSA-Action: urn:mediate
2009-08-05 11:40:26,609 [-] [jms-Worker-1] DEBUG Axis2FlexibleMEPClient Sending [add = false] [sec = false] [rm = false]
 [mtom = false] [swa = false] [format = null] [force soap11=false] [force soap12=false] [pox=false] [get=false] [encodin
g=null] [to null]
2009-08-05 11:40:26,624 [-] [jms-Worker-1] DEBUG Axis2FlexibleMEPClient Message [Original Request Message ID : ID:414d51
2074657374716d677220202020c2ea764a20156202] [New Cloned Request Message ID : urn:uuid:71A142F05B90DA1DAD161575569136342-
1258760702]
2009-08-05 11:40:26,656 [-] [jms-Worker-1] DEBUG SynapsePropertiesLoader Retrieving synapse properties from the cache
2009-08-05 11:40:26,656 [-] [jms-Worker-1] DEBUG MiscellaneousUtil The name with ' synapse.global_timeout_interval ' can
not be found. Using default value 86400000
2009-08-05 11:40:26,656 [-] [jms-Worker-1]  INFO TimeoutHandler This engine will expire all callbacks after : 86400 seco
nds, irrespective of the timeout action, after the specified or optional timeout
2009-08-05 11:40:26,656 [-] [jms-Worker-1] DEBUG SynapsePropertiesLoader Retrieving synapse properties from the cache
2009-08-05 11:40:26,656 [-] [jms-Worker-1] DEBUG MiscellaneousUtil The name with ' synapse.timeout_handler_interval ' ca
nnot be found. Using default value 15000
2009-08-05 11:40:26,656 [-] [Timer-1] DEBUG SynapsePropertiesLoader Retrieving synapse properties from the cache
2009-08-05 11:40:26,656 [-] [Timer-1] DEBUG MiscellaneousUtil The name with ' statistics.clean.interval ' cannot be foun
d. Using default value 300000
2009-08-05 11:40:26,656 [-] [Timer-1] DEBUG SynapsePropertiesLoader Retrieving synapse properties from the cache
2009-08-05 11:40:26,656 [-] [Timer-1] DEBUG MiscellaneousUtil The name with ' statistics.clean.enable ' cannot be found.
 Using default value true
2009-08-05 11:40:26,656 [-] [Timer-1] DEBUG StatisticsCleaner Statistics cleaning is will be occured with interval : 300
 s.
2009-08-05 11:40:26,656 [-] [Timer-1] DEBUG StatisticsCleaner There are no expired statistics to be cleaned.
2009-08-05 11:40:26,687 [-] [Axis2 Task] ERROR JMSSender Error creating a JMS message from the message context
javax.jms.MessageFormatException: MQJMS1058: Invalid message property name: JMS_REDELIVERED
        at com.ibm.jms.JMSMessage.newMessageFormatException(JMSMessage.java:4674)
        at com.ibm.jms.JMSMessage.setStringProperty(JMSMessage.java:5658)
        at org.apache.axis2.transport.jms.JMSUtils.setTransportHeaders(JMSUtils.java:277)
        at org.apache.axis2.transport.jms.JMSSender.createJMSMessage(JMSSender.java:413)
        at org.apache.axis2.transport.jms.JMSSender.sendOverJMS(JMSSender.java:159)
        at org.apache.axis2.transport.jms.JMSSender.sendMessage(JMSSender.java:141)
        at org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:112)
        at org.apache.axis2.engine.AxisEngine$TransportNonBlockingInvocationWorker.run(AxisEngine.java:619)
        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:595)
2009-08-05 11:40:41,656 [-] [Timer-1] DEBUG StatisticsCleaner There are no expired statistics to be cleaned.

Re: Synapse ESB and IBM MQ sender issue

by Rajika Kumarasiri :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Wed, Aug 5, 2009 at 5:18 PM, Sunil.2.Tiwari
<st0031200@...>wrote:
hi Sunil,
Having the stack trace will be useful to identify the problem.

-Rajika

>
> Hello everybody,
> I am trying to read (enqueu) message from MQ queue and post(dequeue) it
> into response MQ queue.
> Getting exception (PFA for exception) over Synapse ESB console for proxy
> service when PS is trying to post (dequeue) message to MQ response queue.
> Proxy Service Synapse.xml:
> <definitions xmlns="http://ws.apache.org/ns/synapse">
>  <proxy name="ReceiverQCFPS" transports="jms" startOnLoad="true"
> statistics="enable">
>   <parameter name="transport.jms.JMSSpecVersion">1.0</parameter>
>    <parameter name="transport.jms.Destination">MyMDBQueue</parameter>
>        <parameter name="transport.PollInterval">15</parameter>
>          <target>
>            <inSequence>
>              <log level="full" separator=", "/>
>              <property action="set" name="OUT_ONLY" value="true"/>
>            </inSequence>
>   <endpoint>
>   <address
>  uri="jms:/MyReplyQueue?transport.jms.ConnectionFactoryJNDIName=SenderQCF&java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory&java.naming.provider.url=file:/C:/JNDI-Directory&transport.jms.ConnectionFactoryType=queue"/>
>   </endpoint>
>        <outSequence>
>        <log level="full" separator=", "/>
>             <send/>
>         <log level="full" separator=", "/>
>         </outSequence>
>        </target>
> </proxy>
> </definitions>
>
> Any idea where is the problem.
>
> Thanks & Regards
> Sunil Kumar Tiwari | I&B2B | Tech Mahindra Ltd.
> (Office: 009120 6641 7136  Mobile: 0091 9767644210)
> Email: sunil.tiwari2@...
>
>
>
> ============================================================================================================================
>
>
> Disclaimer:
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Tech Mahindra policy statement, you may
> review the policy at <a href="http://www.techmahindra.com/Disclaimer.html
> ">http://www.techmahindra.com/Disclaimer.html</a> externally and <a href="
> http://tim.techmahindra.com/Disclaimer.html">
> http://tim.techmahindra.com/Disclaimer.html</a> internally within Tech
> Mahindra.
>
>
> ============================================================================================================================




--
http://wso2.org
http://llvm.org
http://www.minix3.org/

RE: Synapse ESB and IBM MQ sender issue

by Sunil.2.Tiwari :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Hi Rajika,
Attaching stack trace log and axi2.xml.
I am using synapse-1.4.0-SNAPSHOT
Thanks & Regards
Sunil Kumar Tiwari | Tech Mahindra Ltd.
(Office: 009120 6641 7136  Mobile: 0091 9767644210)
Email: sunil.tiwari2@...


-----Original Message-----
From: Rajika Kumarasiri [mailto:rajika@...]
Sent: Wednesday, August 05, 2009 5:22 PM
To: user@...
Subject: Re: Synapse ESB and IBM MQ sender issue

On Wed, Aug 5, 2009 at 5:18 PM, Sunil.2.Tiwari
<st0031200@...>wrote:
hi Sunil,
Having the stack trace will be useful to identify the problem.

-Rajika

>
> Hello everybody,
> I am trying to read (enqueu) message from MQ queue and post(dequeue) it
> into response MQ queue.
> Getting exception (PFA for exception) over Synapse ESB console for proxy
> service when PS is trying to post (dequeue) message to MQ response queue.
> Proxy Service Synapse.xml:
> <definitions xmlns="http://ws.apache.org/ns/synapse">
>  <proxy name="ReceiverQCFPS" transports="jms" startOnLoad="true"
> statistics="enable">
>   <parameter name="transport.jms.JMSSpecVersion">1.0</parameter>
>    <parameter name="transport.jms.Destination">MyMDBQueue</parameter>
>        <parameter name="transport.PollInterval">15</parameter>
>          <target>
>            <inSequence>
>              <log level="full" separator=", "/>
>              <property action="set" name="OUT_ONLY" value="true"/>
>            </inSequence>
>   <endpoint>
>   <address
>  uri="jms:/MyReplyQueue?transport.jms.ConnectionFactoryJNDIName=SenderQCF&java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory&java.naming.provider.url=file:/C:/JNDI-Directory&transport.jms.ConnectionFactoryType=queue"/>
>   </endpoint>
>        <outSequence>
>        <log level="full" separator=", "/>
>             <send/>
>         <log level="full" separator=", "/>
>         </outSequence>
>        </target>
> </proxy>
> </definitions>
>
> Any idea where is the problem.
>
> Thanks & Regards
> Sunil Kumar Tiwari | I&B2B | Tech Mahindra Ltd.
> (Office: 009120 6641 7136  Mobile: 0091 9767644210)
> Email: sunil.tiwari2@...
>
>
>
> ============================================================================================================================
>
>
> Disclaimer:
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Tech Mahindra policy statement, you may
> review the policy at <a href="http://www.techmahindra.com/Disclaimer.html
> ">http://www.techmahindra.com/Disclaimer.html</a> externally and <a href="
> http://tim.techmahindra.com/Disclaimer.html">
> http://tim.techmahindra.com/Disclaimer.html</a> internally within Tech
> Mahindra.
>
>
> ============================================================================================================================



--
http://wso2.org
http://llvm.org
http://www.minix3.org/


============================================================================================================================

 
Disclaimer:

This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at <a href="http://www.techmahindra.com/Disclaimer.html">http://www.techmahindra.com/Disclaimer.html</a> externally and <a href="http://tim.techmahindra.com/Disclaimer.html">http://tim.techmahindra.com/Disclaimer.html</a> internally within Tech Mahindra.

============================================================================================================================

G:\B2BProgramFiles\synapse-1.4.0-SNAPSHOT\bin>synapse.bat
"Starting Synapse/Java ..."
Using SYNAPSE_HOME:        G:\B2BPRO~1\SYNAPS~1.0-S\bin\..
Using JAVA_HOME:       C:\jdk
--> Wrapper Started as Console
Launching a JVM...
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
  Copyright 1999-2006 Tanuki Software, Inc.  All Rights Reserved.

2009-08-05 12:55:24,706 [-] [WrapperSimpleAppMain]  INFO SynapseServer Starting Apache Synapse...
2009-08-05 12:55:24,721 [-] [WrapperSimpleAppMain]  INFO SynapseControllerFactory Using Synapse home : G:\B2BPRO~1\SYNAP
S~1.0-S\.
2009-08-05 12:55:24,721 [-] [WrapperSimpleAppMain]  INFO SynapseControllerFactory Using Axis2 repository : G:\B2BPRO~1\S
YNAPS~1.0-S\repository
2009-08-05 12:55:24,721 [-] [WrapperSimpleAppMain]  INFO SynapseControllerFactory Using axis2.xml location : G:\B2BPRO~1
\SYNAPS~1.0-S\repository\conf\axis2.xml
2009-08-05 12:55:24,737 [-] [WrapperSimpleAppMain]  INFO SynapseControllerFactory Using synapse.xml location : G:\B2BPRO
~1\SYNAPS~1.0-S\bin\..\repository\conf\synapse.xml
2009-08-05 12:55:24,737 [-] [WrapperSimpleAppMain]  INFO SynapseControllerFactory Using server name : localhost
2009-08-05 12:55:24,737 [-] [WrapperSimpleAppMain] DEBUG SynapseControllerFactory Using Server Configuration As : [ Serv
er Name : localhost ][ Synapse Home : . ][ Synapse XML : G:\B2BPRO~1\SYNAPS~1.0-S\bin\..\repository\conf\synapse.xml ][
Server Host : sinpunap072 ][ Server IP : 172.24.182.114 ][ Axis2 Repository : repository ][ Axis2 XML : repository/conf/
axis2.xml ]
2009-08-05 12:55:24,753 [-] [WrapperSimpleAppMain] DEBUG SynapsePropertiesLoader Loading synapse properties from a prope
rty file
2009-08-05 12:55:24,753 [-] [WrapperSimpleAppMain] DEBUG MiscellaneousUtil Loading a file ' synapse.properties ' from cl
asspath
2009-08-05 12:55:24,753 [-] [WrapperSimpleAppMain] DEBUG MiscellaneousUtil The name with ' synapse.timeout_handler_inter
val ' cannot be found. Using default value 15000
2009-08-05 12:55:24,753 [-] [WrapperSimpleAppMain]  INFO SynapseControllerFactory The timeout handler will run every : 1
5s
2009-08-05 12:55:24,831 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Initializing Synapse at : Wed Aug 05 12:
55:24 BST 2009
2009-08-05 12:55:24,831 [-] [WrapperSimpleAppMain] DEBUG Axis2SynapseController Initializing Synapse in a new axis2 serv
er environment instance
2009-08-05 12:55:26,237 [-] [WrapperSimpleAppMain] ERROR SandeshaModule Could not load module policies. Using default va
lues.
2009-08-05 12:55:26,268 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSSLSender Loading Identity Keystore from : lib/ident
ity.jks
2009-08-05 12:55:26,284 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSSLSender Loading Trust Keystore from : lib/trust.jk
s
2009-08-05 12:55:26,425 [-] [WrapperSimpleAppMain] DEBUG NativeWorkerPool Using native util.concurrent package..
2009-08-05 12:55:26,425 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSSLSender Loading custom SSL profiles for the HTTPS
sender
2009-08-05 12:55:26,425 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSender HTTPS Sender starting
2009-08-05 12:55:26,440 [-] [WrapperSimpleAppMain] DEBUG NativeWorkerPool Using native util.concurrent package..
2009-08-05 12:55:26,440 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSender HTTP Sender starting
2009-08-05 12:55:26,440 [-] [WrapperSimpleAppMain]  INFO VFSTransportSender VFS Sender started
2009-08-05 12:55:26,581 [-] [WrapperSimpleAppMain]  INFO JMSSender JMS Sender started
2009-08-05 12:55:26,706 [-] [WrapperSimpleAppMain]  INFO JMSConnectionFactory JMS ConnectionFactory : default initialize
d
2009-08-05 12:55:26,706 [-] [WrapperSimpleAppMain]  INFO JMSSender JMS Transport Sender initialized...
2009-08-05 12:55:26,721 [-] [WrapperSimpleAppMain] DEBUG SynapsePropertiesLoader Retrieving synapse properties from the
cache
2009-08-05 12:55:26,721 [-] [WrapperSimpleAppMain] DEBUG MiscellaneousUtil The name with ' synapse.jmx.rmiPort ' cannot
be found. Using default value 0
2009-08-05 12:55:26,721 [-] [WrapperSimpleAppMain] DEBUG MiscellaneousUtil The name with ' synapse.jmx.remote.ssl ' cann
ot be found. Using default value false
2009-08-05 12:55:26,737 [-] [WrapperSimpleAppMain]  WARN JmxAdapter Using unsecured JMX remote access!
2009-08-05 12:55:26,784 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSSLListener Loading Identity Keystore from : lib/ide
ntity.jks
2009-08-05 12:55:26,784 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOSSLListener Loading Trust Keystore from : lib/trust.
jks
2009-08-05 12:55:26,784 [-] [WrapperSimpleAppMain] DEBUG NativeWorkerPool Using native util.concurrent package..
2009-08-05 12:55:26,800 [-] [WrapperSimpleAppMain] DEBUG NativeWorkerPool Using native util.concurrent package..
2009-08-05 12:55:26,815 [-] [WrapperSimpleAppMain] DEBUG NativeWorkerPool Using native util.concurrent package..
2009-08-05 12:55:26,815 [-] [WrapperSimpleAppMain]  INFO JMSConnectionFactory JMS ConnectionFactory : default initialize
d
2009-08-05 12:55:26,815 [-] [WrapperSimpleAppMain]  INFO JMSListener JMS Transport Receiver/Listener initialized...
2009-08-05 12:55:26,815 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Loading mediator extensions...
2009-08-05 12:55:26,815 [-] [WrapperSimpleAppMain] DEBUG TaskDescriptionRepositoryFactory Creating a TaskDescriptionRepo
sitory with id : task_description_repository
2009-08-05 12:55:26,831 [-] [WrapperSimpleAppMain] DEBUG SynapsePropertiesLoader Reloading synapse properties
2009-08-05 12:55:26,831 [-] [WrapperSimpleAppMain] DEBUG SynapsePropertiesLoader Loading synapse properties from a prope
rty file
2009-08-05 12:55:26,831 [-] [WrapperSimpleAppMain] DEBUG MiscellaneousUtil Loading a file ' synapse.properties ' from cl
asspath
2009-08-05 12:55:26,831 [-] [WrapperSimpleAppMain] DEBUG DataSourceInformationRepositoryFactory Creating a new DataSourc
eInformationRepository
2009-08-05 12:55:26,846 [-] [WrapperSimpleAppMain] DEBUG DataSourceInformationListFactory No DataSources defined for ini
tialization..
2009-08-05 12:55:26,846 [-] [WrapperSimpleAppMain]  INFO XMLConfigurationBuilder Generating the Synapse configuration mo
del by parsing the XML configuration
2009-08-05 12:55:26,862 [-] [WrapperSimpleAppMain] DEBUG ConfigurationFactoryAndSerializerFinder getConfiguration({http:
//ws.apache.org/ns/synapse}definitions)
2009-08-05 12:55:26,862 [-] [WrapperSimpleAppMain] DEBUG TaskDescriptionRepositoryFactory Creating a TaskDescriptionRepo
sitory with id : synapse.startup.taskdescriptions.repository
2009-08-05 12:55:26,862 [-] [WrapperSimpleAppMain] DEBUG SynapsePropertiesLoader Retrieving synapse properties from the
cache
2009-08-05 12:55:26,971 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder Added MediatorFactory class org.apache.sy
napse.experimental.DetachMediatorFactory to handle {http://ws.apache.org/ns/synapse}detach
2009-08-05 12:55:26,971 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder Added MediatorFactory class org.apache.sy
napse.experimental.ReplaceMediatorFactory to handle {http://ws.apache.org/ns/synapse}replace
2009-08-05 12:55:26,971 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder Added MediatorFactory class org.apache.sy
napse.mediators.spring.SpringMediatorFactory to handle {http://ws.apache.org/ns/synapse/spring}spring
2009-08-05 12:55:26,971 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder Added MediatorFactory class org.apache.sy
napse.mediators.bsf.ScriptMediatorFactory to handle {http://ws.apache.org/ns/synapse}script
2009-08-05 12:55:26,971 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder Added MediatorFactory class org.apache.sy
napse.mediators.throttle.ThrottleMediatorFactory to handle {http://ws.apache.org/ns/synapse}throttle
2009-08-05 12:55:26,987 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder Added MediatorFactory class org.apache.sy
napse.mediators.xquery.XQueryMediatorFactory to handle {http://ws.apache.org/ns/synapse}xquery
2009-08-05 12:55:26,987 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder getMediator({http://ws.apache.org/ns/syna
pse}log)
2009-08-05 12:55:26,987 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder getMediator({http://ws.apache.org/ns/syna
pse}property)
2009-08-05 12:55:26,987 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder getMediator({http://ws.apache.org/ns/syna
pse}log)
2009-08-05 12:55:26,987 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder getMediator({http://ws.apache.org/ns/syna
pse}send)
2009-08-05 12:55:26,987 [-] [WrapperSimpleAppMain] DEBUG MediatorFactoryFinder getMediator({http://ws.apache.org/ns/syna
pse}log)
2009-08-05 12:55:27,034 [-] [WrapperSimpleAppMain]  INFO SynapseConfigurationBuilder Loaded Synapse configuration from :
 G:\B2BPRO~1\SYNAPS~1.0-S\bin\..\repository\conf\synapse.xml
2009-08-05 12:55:27,034 [-] [WrapperSimpleAppMain] DEBUG SynapsePropertiesLoader Retrieving synapse properties from the
cache
2009-08-05 12:55:27,050 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Deploying the Synapse service...
2009-08-05 12:55:27,065 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Deploying Proxy services...
2009-08-05 12:55:27,065 [-] [WrapperSimpleAppMain]  INFO ProxyService Building Axis service for Proxy service : Receiver
QCFPS
2009-08-05 12:55:27,065 [-] [WrapperSimpleAppMain]  INFO ProxyService Adding service ReceiverQCFPS to the Axis2 configur
ation
2009-08-05 12:55:27,065 [-] [WrapperSimpleAppMain]  INFO ProxyService Successfully created the Axis2 service for Proxy s
ervice : ReceiverQCFPS
2009-08-05 12:55:27,065 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Deployed Proxy service : ReceiverQCFPS
2009-08-05 12:55:27,065 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Deploying EventSources...
2009-08-05 12:55:27,081 [-] [WrapperSimpleAppMain] DEBUG SynapseConfiguration Initializing the Synapse Configuration usi
ng the SynapseEnvironment
2009-08-05 12:55:27,081 [-] [WrapperSimpleAppMain] DEBUG SequenceMediator Initializing child mediators of mediator : Seq
uenceMediator
2009-08-05 12:55:27,081 [-] [WrapperSimpleAppMain] DEBUG SequenceMediator Initializing child mediators of mediator : Seq
uenceMediator
2009-08-05 12:55:27,081 [-] [WrapperSimpleAppMain] DEBUG SequenceMediator Initializing child mediators of mediator : Seq
uenceMediator
2009-08-05 12:55:27,081 [-] [WrapperSimpleAppMain] DEBUG SequenceMediator Initializing child mediators of mediator : Seq
uenceMediator
2009-08-05 12:55:27,081 [-] [WrapperSimpleAppMain] DEBUG HttpCoreNIOListener Starting Listener...
2009-08-05 12:55:27,096 [-] [WrapperSimpleAppMain] DEBUG NativeWorkerPool Using native util.concurrent package..
2009-08-05 12:55:27,112 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOListener HTTPS Listener started on port : 8243
2009-08-05 12:55:27,112 [-] [WrapperSimpleAppMain] DEBUG HttpCoreNIOListener Starting Listener...
2009-08-05 12:55:27,112 [-] [WrapperSimpleAppMain] DEBUG NativeWorkerPool Using native util.concurrent package..
2009-08-05 12:55:27,112 [-] [WrapperSimpleAppMain]  INFO HttpCoreNIOListener HTTP Listener started on port : 8280
2009-08-05 12:55:27,112 [-] [WrapperSimpleAppMain]  INFO VFSTransportListener VFS Listener started
2009-08-05 12:55:27,112 [-] [WrapperSimpleAppMain]  INFO MailTransportListener MAILTO Listener started
2009-08-05 12:55:27,112 [-] [WrapperSimpleAppMain]  INFO JMSListener JMS Listener started
2009-08-05 12:55:27,112 [-] [WrapperSimpleAppMain] DEBUG JMSEndpoint JMS destination type not given. default queue
2009-08-05 12:55:27,128 [-] [WrapperSimpleAppMain] DEBUG ServiceTaskManager The JMS Connection, Session and MessageConsu
mer will be cached and shared between successive poller task invocations
2009-08-05 12:55:27,128 [-] [WrapperSimpleAppMain]  INFO ServiceTaskManager Task manager for service : ReceiverQCFPS [re
-]initialized
2009-08-05 12:55:27,128 [-] [jms-Worker-1] DEBUG ServiceTaskManager New poll task starting : thread id = 45
2009-08-05 12:55:27,128 [-] [jms-Worker-1] DEBUG ServiceTaskManager Connected to the JMS connection factory : ReceiverQC
F
2009-08-05 12:55:27,128 [-] [jms-Worker-1] DEBUG JMSUtils Creating a QueueConnection using credentials : (null/null)
2009-08-05 12:55:27,393 [-] [jms-Worker-1] DEBUG ServiceTaskManager JMS Connection for service : ReceiverQCFPS created a
nd started
2009-08-05 12:55:27,393 [-] [jms-Worker-1] DEBUG ServiceTaskManager Creating a new JMS Session for service : ReceiverQCF
PS
2009-08-05 12:55:27,425 [-] [jms-Worker-1] DEBUG ServiceTaskManager Creating a new JMS MessageConsumer for service : Rec
eiverQCFPS
2009-08-05 12:55:27,425 [-] [jms-Worker-1] DEBUG ServiceTaskManager JMS Destination with JNDI name : MyMDBQueue found fo
r service ReceiverQCFPS
2009-08-05 12:55:27,456 [-] [jms-Worker-1] DEBUG ServiceTaskManager Preparing a Connection, Session and Consumer to read
 messages
2009-08-05 12:55:27,456 [-] [jms-Worker-1] DEBUG ServiceTaskManager Waiting for a message for service : ReceiverQCFPS -
duration : 1000ms
2009-08-05 12:55:28,128 [-] [WrapperSimpleAppMain]  INFO JMSListener Started to listen on destination : MyMDBQueue of ty
pe Queue for service ReceiverQCFPS
2009-08-05 12:55:28,128 [-] [WrapperSimpleAppMain]  INFO Axis2SynapseController Management using JMX available via: serv
ice:jmx:rmi:///jndi/rmi://sinpunap072:1099/synapse
2009-08-05 12:55:28,143 [-] [WrapperSimpleAppMain]  INFO ServerManager Server ready for processing...
2009-08-05 12:55:28,143 [-] [WrapperSimpleAppMain]  INFO SynapseServer Apache Synapse started successfully
2009-08-05 12:55:28,456 [-] [jms-Worker-1] TRACE ServiceTaskManager No message received by Thread ID : 45 for destinatio
n : queue://testqmgr/MyMDBQueue
2009-08-05 12:55:28,456 [-] [jms-Worker-1] DEBUG ServiceTaskManager Waiting for a message for service : ReceiverQCFPS -
duration : 1000ms
2009-08-05 12:55:29,456 [-] [jms-Worker-1] TRACE ServiceTaskManager No message received by Thread ID : 45 for destinatio
n : queue://testqmgr/MyMDBQueue
2009-08-05 12:55:29,456 [-] [jms-Worker-1] DEBUG ServiceTaskManager Waiting for a message for service : ReceiverQCFPS -
duration : 1000ms
2009-08-05 12:55:30,456 [-] [jms-Worker-1] TRACE ServiceTaskManager No message received by Thread ID : 45 for destinatio
n : queue://testqmgr/MyMDBQueue
2009-08-05 12:55:30,456 [-] [jms-Worker-1] DEBUG ServiceTaskManager Waiting for a message for service : ReceiverQCFPS -
duration : 1000ms
2009-08-05 12:55:31,456 [-] [jms-Worker-1] TRACE ServiceTaskManager No message received by Thread ID : 45 for destinatio
n : queue://testqmgr/MyMDBQueue
2009-08-05 12:55:31,456 [-] [jms-Worker-1] DEBUG ServiceTaskManager Waiting for a message for service : ReceiverQCFPS -
duration : 1000ms
2009-08-05 12:55:32,269 [-] [jms-Worker-1] TRACE ServiceTaskManager <<<<<<< READ message with Message ID : ID:414d512074
657374716d677220202020c2ea764a2015ff02 from : queue://testqmgr/MyMDBQueue by Thread ID : 45
2009-08-05 12:55:32,269 [-] [jms-Worker-1] DEBUG JMSMessageReceiver Received new JMS message for service :ReceiverQCFPS
Destination    : null
Message ID     : ID:414d512074657374716d677220202020c2ea764a2015ff02
Correlation ID : null
ReplyTo        : null
Redelivery ?   : false
Priority       : 0
Expiration     : 0
Timestamp      : 1249473332260
Message Type   : null
Persistent ?   : false
2009-08-05 12:55:32,269 [-] [jms-Worker-1] TRACE JMSMessageReceiver
Message : <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://services.samples
" xmlns:xsd="http://services.samples/xsd"><soapenv:Header/> <soapenv:Body><ser:placeOrder> <ser:order><xsd:price>100</xs
d:price><xsd:quantity>5</xsd:quantity> <xsd:symbol>5</xsd:symbol></ser:order> </ser:placeOrder> </soapenv:Body></soapenv
:Envelope>
2009-08-05 12:55:32,315 [-] [jms-Worker-1] DEBUG ProxyServiceMessageReceiver Proxy Service ReceiverQCFPS received a new
message...
2009-08-05 12:55:32,315 [-] [jms-Worker-1] DEBUG ProxyServiceMessageReceiver Message To: null
2009-08-05 12:55:32,315 [-] [jms-Worker-1] DEBUG ProxyServiceMessageReceiver SOAPAction: urn:mediate
2009-08-05 12:55:32,315 [-] [jms-Worker-1] DEBUG ProxyServiceMessageReceiver WSA-Action: urn:mediate
2009-08-05 12:55:32,331 [-] [jms-Worker-1] DEBUG StatisticsReporter Setting statistics stack on the message context.
2009-08-05 12:55:32,331 [-] [jms-Worker-1] DEBUG StatisticsRecordFactory Created a StatisticsRecord with [Message id : I
D:414d512074657374716d677220202020c2ea764a2015ff02 ][Remote  IP : null ][Remote host : null ]
2009-08-05 12:55:32,331 [-] [jms-Worker-1] DEBUG StatisticsReporter Setting statistics collector in the synapse environm
ent.
2009-08-05 12:55:32,331 [-] [jms-Worker-1] DEBUG StatisticsRecord Start to reportForComponent statistics for : ReceiverQ
CFPS
2009-08-05 12:55:32,331 [-] [jms-Worker-1] DEBUG ProxyServiceMessageReceiver Using the anonymous in-sequence of the prox
y service for mediation
2009-08-05 12:55:32,331 [-] [jms-Worker-1] DEBUG SequenceMediator Start : Sequence <anonymous>
2009-08-05 12:55:32,331 [-] [jms-Worker-1] DEBUG SequenceMediator Sequence <SequenceMediator> :: mediate()
2009-08-05 12:55:32,331 [-] [jms-Worker-1] DEBUG LogMediator Start : Log mediator
2009-08-05 12:55:32,362 [-] [jms-Worker-1]  INFO LogMediator To: , WSAction: urn:mediate, SOAPAction: urn:mediate, Messa
geID: ID:414d512074657374716d677220202020c2ea764a2015ff02, Direction: request, Envelope: <?xml version='1.0' encoding='u
tf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><axis2ns1:text xmlns:ax
is2ns1="http://ws.apache.org/commons/ns/payload"><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/env
elope/" xmlns:ser="http://services.samples" xmlns:xsd="http://services.samples/xsd"><soapenv:Header/> <soapenv:Bod
y><ser:placeOrder> <ser:order><xsd:price>100</xsd:price><xsd:quantity>5</xsd:quantity> <xsd:symbol>
5</xsd:symbol></ser:order> </ser:placeOrder> </soapenv:Body></soapenv:Envelope></axis2ns1:text></soapenv:
Body></soapenv:Envelope>
2009-08-05 12:55:32,362 [-] [jms-Worker-1] DEBUG LogMediator End : Log mediator
2009-08-05 12:55:32,362 [-] [jms-Worker-1] DEBUG PropertyMediator Start : Property mediator
2009-08-05 12:55:32,362 [-] [jms-Worker-1] DEBUG PropertyMediator Setting property : OUT_ONLY at scope : default to : tr
ue (i.e. constant : true)
2009-08-05 12:55:32,362 [-] [jms-Worker-1] DEBUG PropertyMediator End : Property mediator
2009-08-05 12:55:32,362 [-] [jms-Worker-1] DEBUG SequenceMediator End : Sequence <anonymous>
2009-08-05 12:55:32,362 [-] [jms-Worker-1] DEBUG ProxyServiceMessageReceiver Forwarding the message to the anonymous end
point of the proxy service
2009-08-05 12:55:32,362 [-] [jms-Worker-1] DEBUG EndpointContext Checking if endpoint : AnonymousEndpoint currently at s
tate ACTIVE can be used now?
2009-08-05 12:55:32,362 [-] [jms-Worker-1] DEBUG AddressEndpoint Sending message through endpoint : null resolving to ad
dress = jms:/MyReplyQueue?transport.jms.ConnectionFactoryJNDIName=SenderQCF&java.naming.factory.initial=com.sun.jndi.fsc
ontext.RefFSContextFactory&java.naming.provider.url=file:/C:/JNDI-Directory&transport.jms.ConnectionFactoryType=queue
2009-08-05 12:55:32,362 [-] [jms-Worker-1] DEBUG AddressEndpoint SOAPAction: urn:mediate
2009-08-05 12:55:32,362 [-] [jms-Worker-1] DEBUG AddressEndpoint WSA-Action: urn:mediate
2009-08-05 12:55:32,378 [-] [jms-Worker-1] DEBUG Axis2FlexibleMEPClient Sending [add = false] [sec = false] [rm = false]
 [mtom = false] [swa = false] [format = null] [force soap11=false] [force soap12=false] [pox=false] [get=false] [encodin
g=null] [to null]
2009-08-05 12:55:32,378 [-] [jms-Worker-1] DEBUG Axis2FlexibleMEPClient Message [Original Request Message ID : ID:414d51
2074657374716d677220202020c2ea764a2015ff02] [New Cloned Request Message ID : urn:uuid:0F93DB624202941A7B1660814523051891
908775174]
2009-08-05 12:55:32,378 [-] [jms-Worker-1] DEBUG SynapsePropertiesLoader Retrieving synapse properties from the cache
2009-08-05 12:55:32,378 [-] [jms-Worker-1] DEBUG MiscellaneousUtil The name with ' synapse.global_timeout_interval ' can
not be found. Using default value 86400000
2009-08-05 12:55:32,378 [-] [jms-Worker-1]  INFO TimeoutHandler This engine will expire all callbacks after : 86400 seco
nds, irrespective of the timeout action, after the specified or optional timeout
2009-08-05 12:55:32,378 [-] [jms-Worker-1] DEBUG SynapsePropertiesLoader Retrieving synapse properties from the cache
2009-08-05 12:55:32,378 [-] [jms-Worker-1] DEBUG MiscellaneousUtil The name with ' synapse.timeout_handler_interval ' ca
nnot be found. Using default value 15000
2009-08-05 12:55:32,378 [-] [Timer-1] DEBUG SynapsePropertiesLoader Retrieving synapse properties from the cache
2009-08-05 12:55:32,378 [-] [Timer-1] DEBUG MiscellaneousUtil The name with ' statistics.clean.interval ' cannot be foun
d. Using default value 300000
2009-08-05 12:55:32,378 [-] [Timer-1] DEBUG SynapsePropertiesLoader Retrieving synapse properties from the cache
2009-08-05 12:55:32,378 [-] [Timer-1] DEBUG MiscellaneousUtil The name with ' statistics.clean.enable ' cannot be found.
 Using default value true
2009-08-05 12:55:32,378 [-] [Timer-1] DEBUG StatisticsCleaner Statistics cleaning is will be occured with interval : 300
 s.
2009-08-05 12:55:32,394 [-] [jms-Worker-1] DEBUG ServiceTaskManager Waiting for a message for service : ReceiverQCFPS -
duration : 1000ms
2009-08-05 12:55:32,394 [-] [Axis2 Task] DEBUG JMSUtils Creating a QueueConnection using credentials : (null/null)
2009-08-05 12:55:32,440 [-] [Timer-1] DEBUG StatisticsCleaner There are no expired statistics to be cleaned.
2009-08-05 12:55:32,440 [-] [Axis2 Task] DEBUG JMSConnectionFactory New JMS Connection from JMS CF : default created
2009-08-05 12:55:32,440 [-] [Axis2 Task] DEBUG JMSConnectionFactory Created shared JMS Connection for JMS CF : default
2009-08-05 12:55:32,440 [-] [Axis2 Task] DEBUG JMSConnectionFactory Creating a new JMS Session from JMS CF : default
2009-08-05 12:55:32,440 [-] [Axis2 Task] DEBUG JMSConnectionFactory Creating a new JMS MessageProducer from JMS CF : def
ault
2009-08-05 12:55:32,456 [-] [Axis2 Task] ERROR JMSSender Error creating a JMS message from the message context
javax.jms.MessageFormatException: MQJMS1058: Invalid message property name: JMS_REDELIVERED
        at com.ibm.jms.JMSMessage.newMessageFormatException(JMSMessage.java:4674)
        at com.ibm.jms.JMSMessage.setStringProperty(JMSMessage.java:5658)
        at org.apache.axis2.transport.jms.JMSUtils.setTransportHeaders(JMSUtils.java:277)
        at org.apache.axis2.transport.jms.JMSSender.createJMSMessage(JMSSender.java:413)
        at org.apache.axis2.transport.jms.JMSSender.sendOverJMS(JMSSender.java:159)
        at org.apache.axis2.transport.jms.JMSSender.sendMessage(JMSSender.java:141)
        at org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:112)
        at org.apache.axis2.engine.AxisEngine$TransportNonBlockingInvocationWorker.run(AxisEngine.java:619)
        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:595)
2009-08-05 12:55:33,440 [-] [jms-Worker-1] TRACE ServiceTaskManager No message received by Thread ID : 45 for destinatio
n : queue://testqmgr/MyMDBQueue
2009-08-05 12:55:33,440 [-] [jms-Worker-1] DEBUG ServiceTaskManager Waiting for a message for service : ReceiverQCFPS -
duration : 1000ms
2009-08-05 12:55:34,440 [-] [jms-Worker-1] TRACE ServiceTaskManager No message received by Thread ID : 45 for destinatio
n : queue://testqmgr/MyMDBQueue
2009-08-05 12:55:34,440 [-] [jms-Worker-1] DEBUG ServiceTaskManager Waiting for a message for service : ReceiverQCFPS -
duration : 1000ms
2009-08-05 12:55:35,441 [-] [jms-Worker-1] TRACE ServiceTaskManager No message received by Thread ID : 45 for destinatio
n : queue://testqmgr/MyMDBQueue
2009-08-05 12:55:35,441 [-] [jms-Worker-1] DEBUG ServiceTaskManager Waiting for a message for service : ReceiverQCFPS -
duration : 1000ms
2009-08-05 12:55:36,441 [-] [jms-Worker-1] TRACE ServiceTaskManager No message received by Thread ID : 45 for destinatio
n : queue://testqmgr/MyMDBQueue
2009-08-05 12:55:36,441 [-] [jms-Worker-1] DEBUG ServiceTaskManager Waiting for a message for service : ReceiverQCFPS -
duration : 1000ms
2009-08-05 12:55:37,441 [-] [jms-Worker-1] TRACE ServiceTaskManager No message received by Thread ID : 45 for destinatio
n : queue://testqmgr/MyMDBQueue
2009-08-05 12:55:37,441 [-] [jms-Worker-1] DEBUG ServiceTaskManager Waiting for a message for service : ReceiverQCFPS -
duration : 1000ms

<!--
  ~  Licensed to the Apache Software Foundation (ASF) under one
  ~  or more contributor license agreements.  See the NOTICE file
  ~  distributed with this work for additional information
  ~  regarding copyright ownership.  The ASF licenses this file
  ~  to you under the Apache License, Version 2.0 (the
  ~  "License"); you may not use this file except in compliance
  ~  with the License.  You may obtain a copy of the License at
  ~
  ~   http://www.apache.org/licenses/LICENSE-2.0
  ~
  ~  Unless required by applicable law or agreed to in writing,
  ~  software distributed under the License is distributed on an
  ~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
  ~  KIND, either express or implied.  See the License for the
  ~  specific language governing permissions and limitations
  ~  under the License.
  -->

<axisconfig name="AxisJava2.0">
    <!-- ================================================= -->
    <!-- Parameters -->
    <!-- ================================================= -->
    <parameter name="hotdeployment">false</parameter>
    <parameter name="hotupdate">false</parameter>
    <parameter name="enableMTOM">false</parameter>
    <parameter name="enableSwA">false</parameter>

    <!--Uncomment if you want to enable file caching for attachments -->
    <!--parameter name="cacheAttachments">true</parameter>
    <parameter name="attachmentDIR"></parameter>
    <parameter name="sizeThreshold">4000</parameter-->

    <!--This will give out the timout of the configuration contexts, in milliseconds-->
    <parameter name="ConfigContextTimeoutInterval">30000</parameter>

    <!--During a fault, stacktrace can be sent with the fault message. The following flag will control -->
    <!--that behavior.-->
    <parameter name="sendStacktraceDetailsWithFaults">false</parameter>

    <!--If there aren't any information available to find out the fault reason, we set the message of the exception-->
    <!--as the faultreason/Reason. But when a fault is thrown from a service or some where, it will be -->
    <!--wrapped by different levels. Due to this the initial exception message can be lost. If this flag-->
    <!--is set, then Axis2 tries to get the first exception and set its message as the faultreason/Reason.-->
    <parameter name="DrillDownToRootCauseForFaultReason">false</parameter>

    <parameter name="userName">admin</parameter>
    <parameter name="password">axis2</parameter>

    <!--To override repository/services you need to uncomment following parameter and value SHOULD be absolute file path.-->
    <!--ServicesDirectory only works on the following cases-->
    <!---File based configurator and in that case the value should be a file URL (http:// not allowed)-->
    <!---When creating URL Based configurator with URL "file://"  -->
    <!--- War based configurator with expanded case , -->

    <!--All the other scenarios it will be ignored.-->
    <!--<parameter name="ServicesDirectory">service</parameter>-->
    <!--To override repository/modules you need to uncomment following parameter and value SHOULD be absolute file path-->
    <!--<parameter name="ModulesDirectory">modules</parameter>-->



    <!--Following params will set the proper context paths for invocations. All the endpoints will have a commons context-->
    <!--root which can configured using the following contextRoot parameter-->
    <parameter name="contextRoot">/</parameter>

    <!--Our HTTP endpoints can handle both REST and SOAP. Following parameters can be used to distinguiush those endpoints-->
    <!--In case of a servlet, if you change this you have to manually change the settings of your servlet container to map this -->
    <!--context path to proper Axis2 servlets-->
    <parameter name="servicePath">services</parameter>
    <parameter name="restPath">rest</parameter>

    <!-- Following parameter will completely disable REST handling in Axis2-->
    <parameter name="disableREST" locked="true">false</parameter>

    <!-- Extension deployer
         ***** Uncomment the following line to enable (hot) deployment of Synapse extensions (mediators and startups) ***** -->
    <!--<deployer extension="xar" directory="extensions" class="org.apache.synapse.core.axis2.ExtensionDeployer"/>-->

    <!-- Following parameter will set the host name for the epr-->
    <!--<parameter name="hostname" locked="true">myhost.com</parameter>-->

    <!-- If you have a frontend host which exposes this webservice using a different public URL  -->
    <!-- use this parameter to override autodetected url -->
    <!--<parameter name="httpFrontendHostUrl">https://someotherhost/context</parameter>-->


    <!--    The way of adding listener to the system-->
    <!--    <listener class="org.apache.axis2.ObserverIMPL">-->
    <!--        <parameter name="RSS_URL">http://127.0.0.1/rss</parameter>-->
    <!--    </listener>-->

    <!-- ================================================= -->
    <!-- Message Receivers -->
    <!-- ================================================= -->
    <!--This is the deafult MessageReceiver for the system , if you want to have MessageReceivers for -->
    <!--all the other MEP implement it and add the correct entry to here , so that you can refer from-->
    <!--any operation -->
    <!--Note : You can ovrride this for a particular service by adding the same element with your requirement-->
    <messageReceivers>
        <messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-only"
                         class="org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver"/>
        <messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-out"
                         class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>
        <messageReceiver mep="http://www.w3.org/2006/01/wsdl/in-only"
                         class="org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver"/>
        <messageReceiver mep="http://www.w3.org/2006/01/wsdl/in-out"
                         class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>
    </messageReceivers>

    <!-- ================================================= -->
    <!-- Message Formatter -->
    <!-- ================================================= -->
    <!--Following content type to message formatter mapping can be used to implement support for different message -->
    <!--format  serialization in Axis2. These message formats are expected to be resolved based on the content type. -->
    <messageFormatters>
        <messageFormatter contentType="application/x-www-form-urlencoded"
                         class="org.apache.axis2.transport.http.XFormURLEncodedFormatter"/>
        <messageFormatter contentType="multipart/form-data"
                         class="org.apache.axis2.transport.http.MultipartFormDataFormatter"/>
        <messageFormatter contentType="application/xml"
                         class="org.apache.axis2.transport.http.ApplicationXMLFormatter"/>
        <!--<messageFormatter contentType="x-application/hessian"
                         class="org.apache.synapse.format.hessian.HessianMessageFormatter"/>-->
        <!--<messageFormatter contentType=""
                         class="org.apache.synapse.format.hessian.HessianMessageFormatter"/>-->
    </messageFormatters>

    <!-- ================================================= -->
    <!-- Message Builders -->
    <!-- ================================================= -->
    <!--Following content type to builder mapping can be used to implement support for different message -->
    <!--formats in Axis2. These message formats are expected to be resolved based on the content type. -->
    <messageBuilders>
        <messageBuilder contentType="application/xml"
                         class="org.apache.axis2.builder.ApplicationXMLBuilder"/>
        <messageBuilder contentType="application/x-www-form-urlencoded"
                         class="org.apache.axis2.builder.XFormURLEncodedBuilder"/>
        <messageBuilder contentType="multipart/form-data"
                         class="org.apache.axis2.builder.MultipartFormDataBuilder"/>
        <!--<messageBuilder contentType="x-application/hessian"
                         class="org.apache.synapse.format.hessian.HessianMessageBuilder"/>-->
        <!--<messageBuilder contentType=""
                         class="org.apache.synapse.format.hessian.HessianMessageBuilder"/>-->
    </messageBuilders>

    <!-- ================================================= -->
    <!-- Transport Ins -->
    <!-- ================================================= -->
    <!-- the non blocking http transport based on HttpCore + NIO extensions -->
    <transportReceiver name="http" class="org.apache.synapse.transport.nhttp.HttpCoreNIOListener">
    <parameter name="port">8280</parameter>
    <parameter name="non-blocking">true</parameter>
        <!--parameter name="bind-address" locked="false">hostname or IP address</parameter-->
        <!--parameter name="WSDLEPRPrefix" locked="false">https://apachehost:port/somepath</parameter-->
    </transportReceiver>

    <!-- the non blocking https transport based on HttpCore + SSL-NIO extensions -->
    <transportReceiver name="https" class="org.apache.synapse.transport.nhttp.HttpCoreNIOSSLListener">
    <parameter name="port" locked="false">8243</parameter>
        <!--parameter name="bind-address" locked="false">hostname or IP address</parameter-->
        <!--parameter name="WSDLEPRPrefix" locked="false">http://apachehost:port/somepath</parameter-->
        <parameter name="non-blocking" locked="false">true</parameter>
        <parameter name="keystore" locked="false">
            <KeyStore>
                <Location>lib/identity.jks</Location>
                <Type>JKS</Type>
                <Password>password</Password>
                <KeyPassword>password</KeyPassword>
            </KeyStore>
        </parameter>
        <parameter name="truststore" locked="false">
            <TrustStore>
                <Location>lib/trust.jks</Location>
                <Type>JKS</Type>
                <Password>password</Password>
            </TrustStore>
        </parameter>
        <!--<parameter name="SSLVerifyClient">require</parameter>
            supports optional|require or defaults to none -->
    </transportReceiver>

   
    <transportReceiver name="jms" class="org.apache.axis2.transport.jms.JMSListener">
        <!--Uncomment this and configure as appropriate for JMS transport support, after setting up your JMS environment (e.g. ActiveMQ)
        <parameter name="myTopicConnectionFactory">
        <parameter name="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
        <parameter name="java.naming.provider.url">tcp://localhost:61616</parameter>
        <parameter name="transport.jms.ConnectionFactoryJNDIName">TopicConnectionFactory</parameter>
                <parameter name="transport.jms.ConnectionFactoryType" locked="false">topic</parameter>
        </parameter>

        <parameter name="myQueueConnectionFactory">
        <parameter name="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
        <parameter name="java.naming.provider.url">tcp://localhost:61616</parameter>
        <parameter name="transport.jms.ConnectionFactoryJNDIName">QueueConnectionFactory</parameter>
                <parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter>
                                <parameter name="transport.jms.ContentTypeProperty" locked="false">Content-Type</parameter>
        </parameter> -->
 
    <parameter name="default">
        <parameter name="java.naming.factory.initial">com.sun.jndi.fscontext.RefFSContextFactory</parameter>
        <parameter name="java.naming.provider.url">file:/C:/JNDI-Directory</parameter>
        <parameter name="transport.jms.ConnectionFactoryJNDIName">ReceiverQCF</parameter>
                <parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter>

        </parameter>
    </transportReceiver>

    <transportReceiver name="vfs" class="org.apache.synapse.transport.vfs.VFSTransportListener"/>

    <transportReceiver name="mailto" class="org.apache.axis2.transport.mail.MailTransportListener">
        <!-- configure any optional POP3/IMAP properties
        check com.sun.mail.pop3 and com.sun.mail.imap package documentation for more details-->
    </transportReceiver>

     <!--Uncomment this for FIX transport support
    <transportReceiver name="fix" class="org.apache.synapse.transport.fix.FIXTransportListener">
        <parameter name="non-blocking">true</parameter>
    </transportReceiver>-->

    <!-- ================================================= -->
    <!-- Transport Outs -->
    <!-- ================================================= -->

    <transportSender name="http"  class="org.apache.synapse.transport.nhttp.HttpCoreNIOSender">
        <parameter name="non-blocking" locked="false">true</parameter>
        <parameter name="warnOnHTTP500" locked="false">*</parameter>
        <!--parameter name="http.proxyHost" locked="false">localhost</parameter>
        <parameter name="http.proxyPort" locked="false">3128</parameter>
        <parameter name="http.nonProxyHosts" locked="false">localhost|moon|sun</parameter-->
    </transportSender>
    <transportSender name="https" class="org.apache.synapse.transport.nhttp.HttpCoreNIOSSLSender">
        <parameter name="non-blocking" locked="false">true</parameter>
        <parameter name="warnOnHTTP500" locked="false">*</parameter>
        <parameter name="keystore" locked="false">
            <KeyStore>
                <Location>lib/identity.jks</Location>
                <Type>JKS</Type>
                <Password>password</Password>
                <KeyPassword>password</KeyPassword>
            </KeyStore>
        </parameter>
        <parameter name="truststore" locked="false">
            <TrustStore>
                <Location>lib/trust.jks</Location>
                <Type>JKS</Type>
                <Password>password</Password>
            </TrustStore>
        </parameter>
        <!--<parameter name="HostnameVerifier">DefaultAndLocalhost</parameter>
            supports Strict|AllowAll|DefaultAndLocalhost or the default if none specified -->
    </transportSender>
   
    <transportSender name="jms" class="org.apache.axis2.transport.jms.JMSSender">
        <!-- uncomment this and configure to use connection pools for sending messages
        <parameter name="myTopicConnectionFactory">
            <parameter name="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
            <parameter name="java.naming.provider.url">tcp://localhost:61616</parameter>
            <parameter name="transport.jms.ConnectionFactoryJNDIName">TopicConnectionFactory</parameter>
        </parameter>
   
        <parameter name="myQueueConnectionFactory">
            <parameter name="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
            <parameter name="java.naming.provider.url">tcp://localhost:61616</parameter>
            <parameter name="transport.jms.ConnectionFactoryJNDIName">QueueConnectionFactory</parameter>
                        <parameter name="transport.jms.ContentTypeProperty" locked="false">Content-Type</parameter>
        </parameter>
    -->
            <parameter name="default">
            <parameter name="java.naming.factory.initial">com.sun.jndi.fscontext.RefFSContextFactory</parameter>
            <parameter name="java.naming.provider.url">file:/C:/JNDI-Directory</parameter>
            <parameter name="transport.jms.ConnectionFactoryJNDIName">SenderQCF</parameter>
                <parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter>
               
                </parameter>
    </transportSender>
   
    <transportSender name="vfs" class="org.apache.synapse.transport.vfs.VFSTransportSender"/>

    <!-- Uncomment and configure the SMTP server information
    check com.sun.mail.smtp package documentation for descriptions of properties
    <transportSender name="mailto" class="org.apache.axis2.transport.mail.MailTransportSender">
        <parameter name="mail.smtp.host">smtp.gmail.com</parameter>
        <parameter name="mail.smtp.port">587</parameter>
        <parameter name="mail.smtp.starttls.enable">true</parameter>
        <parameter name="mail.smtp.auth">true</parameter>
        <parameter name="mail.smtp.user">synapse.demo.0</parameter>
        <parameter name="mail.smtp.password">mailpassword</parameter>
        <parameter name="mail.smtp.from">synapse.demo.0@...</parameter>
    </transportSender>-->

    <!--Uncomment this for FIX transport support
    <transportSender name="fix" class="org.apache.synapse.transport.fix.FIXTransportSender">
            <parameter name="non-blocking">true</parameter>
    </transportSender>-->

    <!-- ================================================= -->
    <!-- Global Modules  -->
    <!-- ================================================= -->
    <!-- Comment this to disable Addressing -->
    <module ref="addressing"/>

    <!--Configuring module , providing parameters for modules whether they refer or not-->
    <!--<moduleConfig name="addressing">-->
    <!--<parameter name="addressingPara">N/A</parameter>-->
    <!--</moduleConfig>-->

    <!-- ================================================= -->
    <!--                  Clustering                       -->
    <!-- ================================================= -->
    <!-- Configure the following for preparing Synapse to a clustered environment -->
    <cluster class="org.apache.axis2.clustering.tribes.TribesClusterManager" enable="false">

        <!--
           This parameter indicates whther the cluster has to be automatically initalized
           when the AxisConfiguration is built. If set to "true" the initialization will not be
           done at that stage, and some other party will have to explictly initialize the cluster.
        -->
        <parameter name="AvoidInitiation">false</parameter>

        <!--
           The membership scheme used in this setup. The only values supported at the moment are
           "multicast" and "wka"

           1. multicast - membership is automatically discovered using multicasting
           2. wka - Well-Known Address based multicasting. Membership is discovered with the help
                    of one or more nodes running at a Well-Known Address. New members joining a
                    cluster will first connect to a well-known node, register with the well-known node
                    and get the membership list from it. When new members join, one of the well-known
                    nodes will notify the others in the group. When a member leaves the cluster or
                    is deemed to have left the cluster, it will be detected by the Group Membership
                    Service (GMS) using a TCP ping mechanism.
        -->
        <parameter name="membershipScheme">multicast</parameter>

        <!--
         The clustering domain/group. Nodes in the same group will belong to the same multicast
         domain. There will not be interference between nodes in different groups.
        -->
        <parameter name="domain">apache.synapse.domain</parameter>

        <!--
           When a Web service request is received, and processed, before the response is sent to the
           client, should we update the states of all members in the cluster? If the value of
           this parameter is set to "true", the response to the client will be sent only after
           all the members have been updated. Obviously, this can be time consuming. In some cases,
           such this overhead may not be acceptable, in which case the value of this parameter
           should be set to "false"
        -->
        <parameter name="synchronizeAll">true</parameter>

        <!--
          The maximum number of times we need to retry to send a message to a particular node
          before giving up and considering that node to be faulty
        -->
        <parameter name="maxRetries">10</parameter>

        <!-- The multicast address to be used -->
        <parameter name="mcastAddress">228.0.0.4</parameter>

        <!-- The multicast port to be used -->
        <parameter name="mcastPort">45564</parameter>

        <!-- The frequency of sending membership multicast messages (in ms) -->
        <parameter name="mcastFrequency">500</parameter>

        <!-- The time interval within which if a member does not respond, the member will be
         deemed to have left the group (in ms)
         -->
        <parameter name="memberDropTime">3000</parameter>

        <!--
           The IP address of the network interface to which the multicasting has to be bound to.
           Multicasting would be done using this interface.
        -->
        <parameter name="mcastBindAddress">127.0.0.1</parameter>

        <!-- The host name or IP address of this member -->
        <parameter name="localMemberHost">127.0.0.1</parameter>

        <!--
        The TCP port used by this member. This is the port through which other nodes will
        contact this member
         -->
        <parameter name="localMemberPort">4000</parameter>

        <!--
           The list of static or well-known members. These entries will only be valid if the
           "membershipScheme" above is set to "wka"
        -->
        <members>
            <member>
                <hostName>127.0.0.1</hostName>
                <port>4000</port>
            </member>
            <member>
                <hostName>127.0.0.1</hostName>
                <port>4001</port>
            </member>
        </members>

        <!--
        Enable the load balancer entry if you need to run this node as a load balancer.
        Multiple application domains with different LoadBalanceEventHandler implementations
        can be defined in this section.
        -->
        <loadBalancer enable="false">
            <applicationDomain name="apache.axis2.app.domain"
                               handler="org.apache.axis2.clustering.DefaultLoadBalanceEventHandler"/>
        </loadBalancer>
           
        <!--
           This interface is responsible for handling context replication. The property changes in
           the Axis2 context hierarchy in this node, are propagated to all other nodes in the cluster.

           The "excludes" patterns can be used to specify the prefixes (e.g. local_*) or
           suffixes (e.g. *_local) of the properties to be excluded from replication. The pattern
           "*" indicates that all properties in a particular context should not be replicated.

            The "enable" attribute indicates whether context replication has been enabled
        -->
        <contextManager class="org.apache.axis2.clustering.context.DefaultContextManager"
                         enable="false">
            <listener class="org.apache.axis2.clustering.context.DefaultContextManagerListener"/>
            <replication>
                <defaults>
                    <exclude name="local_*"/>
                    <exclude name="LOCAL_*"/>
                </defaults>
                <context class="org.apache.axis2.context.ConfigurationContext">
                    <exclude name="UseAsyncOperations"/>
                    <exclude name="SequencePropertyBeanMap"/>
                </context>
                <context class="org.apache.axis2.context.ServiceGroupContext">
                    <exclude name="my.sandesha.*"/>
                </context>
                <context class="org.apache.axis2.context.ServiceContext">
                    <exclude name="my.sandesha.*"/>
                </context>
            </replication>
        </contextManager>
    </cluster>

    <!-- ================================================= -->
    <!-- Phases  -->
    <!-- ================================================= -->
    <phaseOrder type="InFlow">
        <!--  System pre defined phases       -->
        <phase name="Transport">
            <handler name="RequestURIBasedDispatcher"
                     class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher">
                <order phase="Transport"/>
            </handler>
            <handler name="SOAPActionBasedDispatcher"
                     class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher">
                <order phase="Transport"/>
            </handler>
        </phase>
        <phase name="Addressing">
             <handler name="AddressingBasedDispatcher"
                     class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">
                 <order phase="Addressing"/>
            </handler>
        </phase>
        <phase name="Security"/>
        <phase name="PreDispatch"/>
        <phase name="Dispatch" class="org.apache.axis2.engine.DispatchPhase">
            <handler name="CustomURIBasedDispatcher"
                     class="org.apache.synapse.core.axis2.CustomURIBasedDispatcher"/>
            <handler name="RequestURIBasedDispatcher"
                     class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>
            <handler name="SOAPActionBasedDispatcher"
                     class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
            <handler name="RequestURIOperationDispatcher"
                     class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
            <handler name="SOAPMessageBodyBasedDispatcher"
                     class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/>

            <handler name="HTTPLocationBasedDispatcher"
                     class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/>
        </phase>
        <phase name="RMPhase"/>
        <!--  System predefined phases       -->
        <!--   After Postdispatch phase module author or service author can add any phase he want      -->
        <phase name="OperationInPhase"/>
        <phase name="soapmonitorPhase"/>
    </phaseOrder>
    <phaseOrder type="OutFlow">
        <!--      user can add his own phases to this area  -->
        <phase name="soapmonitorPhase"/>
        <phase name="OperationOutPhase"/>
        <!--system predefined phase-->
        <!--these phase will run irrespective of the service-->
        <phase name="RMPhase"/>
        <phase name="PolicyDetermination"/>
        <phase name="MessageOut"/>
        <phase name="Security"/>
    </phaseOrder>
    <phaseOrder type="InFaultFlow">
        <phase name="Addressing">
             <handler name="AddressingBasedDispatcher"
                     class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">
                 <order phase="Addressing"/>
            </handler>
        </phase>
        <phase name="Security"/>
        <phase name="PreDispatch"/>
        <phase name="Dispatch" class="org.apache.axis2.engine.DispatchPhase">
            <handler name="RequestURIBasedDispatcher"
                     class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>
            <handler name="SOAPActionBasedDispatcher"
                     class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
            <handler name="RequestURIOperationDispatcher"
                     class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
            <handler name="SOAPMessageBodyBasedDispatcher"
                     class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/>

            <handler name="HTTPLocationBasedDispatcher"
                     class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/>
        </phase>
        <phase name="RMPhase"/>
        <!--      user can add his own phases to this area  -->
        <phase name="OperationInFaultPhase"/>
        <phase name="soapmonitorPhase"/>
    </phaseOrder>
    <phaseOrder type="OutFaultFlow">
        <!--      user can add his own phases to this area  -->
        <phase name="soapmonitorPhase"/>
        <phase name="OperationOutFaultPhase"/>
        <phase name="RMPhase"/>
        <phase name="PolicyDetermination"/>
        <phase name="MessageOut"/>
        <phase name="Security"/>
    </phaseOrder>
</axisconfig>

Re: Synapse ESB and IBM MQ sender issue

by Asankha C. Perera :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Sunil
> I am trying to read (enqueu) message from MQ queue and post(dequeue) it into response MQ queue.
> Getting exception (PFA for exception) over Synapse ESB console for proxy service when PS is trying to post (dequeue) message to MQ response queue.
>  
By default your configuration would read a message (along with all of
its transport level headers - i.e. JMS headers) and write them back as
read. However, some of the headers read (e.g. JMS_REDELIVERED) does not
seem writable with your JMS provider. With SYNAPSE-478 we fixed this to
work according to the JMS specs, but the header in question passes
through our filter.

Hence you could remove this header from the transport headers read
before the write like follows:

<inSequence>
  ...
  <property name="JMS_REDELIVERED" action="remove" scope="transport"/>
</inSequence>

cheers
asankha

[1] http://issues.apache.org/jira/browse/SYNAPSE-478 (See the last two
comments of this)

--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org

http://esbmagic.blogspot.com





RE: Synapse ESB and IBM MQ sender issue

by Sunil.2.Tiwari :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Cheers mate!!
Thanks Asankha.
Its working now :)

Thanks & Regards
Sunil Kumar Tiwari | I&B2B | Tech Mahindra Ltd.
(Office: 009120 6641 7136  Mobile: 0091 9767644210)
Email: sunil.tiwari2@...


-----Original Message-----
From: Asankha Perera [mailto:asankha.apache@...] On Behalf Of Asankha C. Perera
Sent: Wednesday, August 05, 2009 6:06 PM
To: user@...
Subject: Re: Synapse ESB and IBM MQ sender issue

Hi Sunil
> I am trying to read (enqueu) message from MQ queue and post(dequeue) it into response MQ queue.
> Getting exception (PFA for exception) over Synapse ESB console for proxy service when PS is trying to post (dequeue) message to MQ response queue.
>  
By default your configuration would read a message (along with all of
its transport level headers - i.e. JMS headers) and write them back as
read. However, some of the headers read (e.g. JMS_REDELIVERED) does not
seem writable with your JMS provider. With SYNAPSE-478 we fixed this to
work according to the JMS specs, but the header in question passes
through our filter.

Hence you could remove this header from the transport headers read
before the write like follows:

<inSequence>
  ...
  <property name="JMS_REDELIVERED" action="remove" scope="transport"/>
</inSequence>

cheers
asankha

[1] http://issues.apache.org/jira/browse/SYNAPSE-478 (See the last two
comments of this)

--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org

http://esbmagic.blogspot.com





============================================================================================================================

 
Disclaimer:

This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at <a href="http://www.techmahindra.com/Disclaimer.html">http://www.techmahindra.com/Disclaimer.html</a> externally and <a href="http://tim.techmahindra.com/Disclaimer.html">http://tim.techmahindra.com/Disclaimer.html</a> internally within Tech Mahindra.

============================================================================================================================

Apache Synapse and Oracle AQ

by Sunil.2.Tiwari :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Hello everybody,

Looking for linking Apache Synapse ESB & Oracle AQ (Advanced Queue).
Goal is to Enqueue/Dequeue messages from Oracle AQ using Synapse ESB

Any idea how to do this?
May Apache Synapse ESB communicate with Oracle AQ directly? similar to IBM MQ or Active MQ.

Link, documents will be helpful.

Thanks & Regards
Sunil Kumar Tiwari |  Tech Mahindra Ltd.
(Office: 009120 6641 7136  Mobile: 0091 9767644210)
Email: sunil.tiwari2@...

============================================================================================================================

 
Disclaimer:

This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at <a href="http://www.techmahindra.com/Disclaimer.html">http://www.techmahindra.com/Disclaimer.html</a> externally and <a href="http://tim.techmahindra.com/Disclaimer.html">http://tim.techmahindra.com/Disclaimer.html</a> internally within Tech Mahindra.

============================================================================================================================

Re: Apache Synapse and Oracle AQ

by Hiranya Jayathilaka-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Sunil,

On Tue, Aug 11, 2009 at 11:22 AM, Sunil.2.Tiwari <st0031200@...
> wrote:

>
> Hello everybody,
>
> Looking for linking Apache Synapse ESB & Oracle AQ (Advanced Queue).
> Goal is to Enqueue/Dequeue messages from Oracle AQ using Synapse ESB
>
> Any idea how to do this?
> May Apache Synapse ESB communicate with Oracle AQ directly? similar to IBM
> MQ or Active MQ.


I'm not very familiar with Oracle AQ. Does it provide any JNDI support like
Active MQ does? In that case we'll be able to get it working with Synapse
out of the box. See if that provides an
javax.naming.spi.InitialContextFactory implementation.

Thanks,
Hiranya


>
>
> Link, documents will be helpful.
>
> Thanks & Regards
> Sunil Kumar Tiwari |  Tech Mahindra Ltd.
> (Office: 009120 6641 7136  Mobile: 0091 9767644210)
> Email: sunil.tiwari2@...
>
>
> ============================================================================================================================
>
>
> Disclaimer:
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Tech Mahindra policy statement, you may
> review the policy at <a href="http://www.techmahindra.com/Disclaimer.html
> ">http://www.techmahindra.com/Disclaimer.html</a> externally and <a href="
> http://tim.techmahindra.com/Disclaimer.html">
> http://tim.techmahindra.com/Disclaimer.html</a> internally within Tech
> Mahindra.
>
>
> ============================================================================================================================
>



--
Hiranya Jayathilaka
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: hiranya@...;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com

Re: Apache Synapse and Oracle AQ

by Hiranya Jayathilaka-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Tue, Aug 11, 2009 at 1:44 PM, Hiranya Jayathilaka
<hiranya911@...>wrote:

> Hi Sunil,
>
> On Tue, Aug 11, 2009 at 11:22 AM, Sunil.2.Tiwari <
> st0031200@...> wrote:
>
>>
>> Hello everybody,
>>
>> Looking for linking Apache Synapse ESB & Oracle AQ (Advanced Queue).
>> Goal is to Enqueue/Dequeue messages from Oracle AQ using Synapse ESB
>>
>> Any idea how to do this?
>> May Apache Synapse ESB communicate with Oracle AQ directly? similar to IBM
>> MQ or Active MQ.
>
>
> I'm not very familiar with Oracle AQ. Does it provide any JNDI support like
> Active MQ does? In that case we'll be able to get it working with Synapse
> out of the box. See if that provides an
> javax.naming.spi.InitialContextFactory implementation.
>

A little bit of Googling around revealed a class called "
oracle.jms.AQjmsInitialContextFactory" which might be what you are looking
for.

Thanks,
Hiranya


>
> Thanks,
> Hiranya
>
>
>>
>>
>> Link, documents will be helpful.
>>
>> Thanks & Regards
>> Sunil Kumar Tiwari |  Tech Mahindra Ltd.
>> (Office: 009120 6641 7136  Mobile: 0091 9767644210)
>> Email: sunil.tiwari2@...
>>
>>
>> ============================================================================================================================
>>
>>
>> Disclaimer:
>>
>> This message and the information contained herein is proprietary and
>> confidential and subject to the Tech Mahindra policy statement, you may
>> review the policy at <a href="http://www.techmahindra.com/Disclaimer.html
>> ">http://www.techmahindra.com/Disclaimer.html</a> externally and <a
>> href="http://tim.techmahindra.com/Disclaimer.html">
>> http://tim.techmahindra.com/Disclaimer.html</a> internally within Tech
>> Mahindra.
>>
>>
>> ============================================================================================================================
>>
>
>
>
> --
> Hiranya Jayathilaka
> Software Engineer;
> WSO2 Inc.;  http://wso2.org
> E-mail: hiranya@...;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>



--
Hiranya Jayathilaka
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: hiranya@...;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com

RE: Apache Synapse and Oracle AQ

by Sunil.2.Tiwari :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message



Thanks a lot Hiranya for your inputs.
I am trying on this side.

Incase anybody did R&D on Synapse ESB & AQ linking, his inputs will be helpful.

Thanks & Regards
Sunil Kumar Tiwari | Tech Mahindra Ltd.
(Office: 009120 6641 7136  Mobile: 0091 9767644210)
Email: sunil.tiwari2@...


-----Original Message-----
From: Hiranya Jayathilaka [mailto:hiranya911@...]
Sent: Tuesday, August 11, 2009 1:53 PM
To: user@...
Subject: Re: Apache Synapse and Oracle AQ

On Tue, Aug 11, 2009 at 1:44 PM, Hiranya Jayathilaka
<hiranya911@...>wrote:

> Hi Sunil,
>
> On Tue, Aug 11, 2009 at 11:22 AM, Sunil.2.Tiwari <
> st0031200@...> wrote:
>
>>
>> Hello everybody,
>>
>> Looking for linking Apache Synapse ESB & Oracle AQ (Advanced Queue).
>> Goal is to Enqueue/Dequeue messages from Oracle AQ using Synapse ESB
>>
>> Any idea how to do this?
>> May Apache Synapse ESB communicate with Oracle AQ directly? similar to IBM
>> MQ or Active MQ.
>
>
> I'm not very familiar with Oracle AQ. Does it provide any JNDI support like
> Active MQ does? In that case we'll be able to get it working with Synapse
> out of the box. See if that provides an
> javax.naming.spi.InitialContextFactory implementation.
>

A little bit of Googling around revealed a class called "
oracle.jms.AQjmsInitialContextFactory" which might be what you are looking
for.

Thanks,
Hiranya


>
> Thanks,
> Hiranya
>
>
>>
>>
>> Link, documents will be helpful.
>>
>> Thanks & Regards
>> Sunil Kumar Tiwari |  Tech Mahindra Ltd.
>> (Office: 009120 6641 7136  Mobile: 0091 9767644210)
>> Email: sunil.tiwari2@...
>>
>>
>> ============================================================================================================================
>>
>>
>> Disclaimer:
>>
>> This message and the information contained herein is proprietary and
>> confidential and subject to the Tech Mahindra policy statement, you may
>> review the policy at <a href="http://www.techmahindra.com/Disclaimer.html
>> ">http://www.techmahindra.com/Disclaimer.html</a> externally and <a
>> href="http://tim.techmahindra.com/Disclaimer.html">
>> http://tim.techmahindra.com/Disclaimer.html</a> internally within Tech
>> Mahindra.
>>
>>
>> ============================================================================================================================
>>
>
>
>
> --
> Hiranya Jayathilaka
> Software Engineer;
> WSO2 Inc.;  http://wso2.org
> E-mail: hiranya@...;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>



--
Hiranya Jayathilaka
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: hiranya@...;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com

============================================================================================================================

 
Disclaimer:

This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at <a href="http://www.techmahindra.com/Disclaimer.html">http://www.techmahindra.com/Disclaimer.html</a> externally and <a href="http://tim.techmahindra.com/Disclaimer.html">http://tim.techmahindra.com/Disclaimer.html</a> internally within Tech Mahindra.

============================================================================================================================