You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@synapse.apache.org by gr...@accenture.com on 2008/02/08 04:24:39 UTC
Switching transports - JMS to http using AQ
I am trying to switch from a JMS transport to an HTTP using Sample 250
as a guide. I am using Oracle AQ as the JMS provider. When I drop a
message on the queue, Synapse doesn't pick up the message. However, if
I shutdown Synapse and restart it, it will pick up one message and call
the HTTP Web service succesfully. It will only pick up one message,
even if there are more on the queue. The same configuration (changed to
point to ActiveMQ) works as expected. Any ideas on what might be
causing this? Has Synapse been successfully used with Oracle AQ?
Here's the synapse.xml that I'm using:
<definitions xmlns="http://ws.apache.org/ns/synapse">
<proxy name="java:comp/env/jms/OutQueue" transports="jms">
<target>
<inSequence>
<property action="set" name="OUT_ONLY" value="true"/>
</inSequence>
<endpoint>
<address
uri="http://localhost:9000/soap/SimpleStockQuoteService" />
</endpoint>
<outSequence>
<send/>
</outSequence>
</target>
<property name="transport.jms.Destination"
value="java:comp/env/jms/OutQueue"/>
<publishWSDL
uri="file:repository/conf/sample/resources/proxy/sample_proxy_1.wsdl"/>
</proxy>
</definitions>
Here's the JMS portion of the axis2.xml:
<transportReceiver name="jms"
class="org.apache.synapse.transport.jms.JMSListener">
<parameter name="default">
<parameter
name="java.naming.factory.initial">oracle.j2ee.naming.ApplicationClientI
nitialContextFactory</parameter>
<parameter
name="java.naming.provider.url">ormi://localhost:23791/how-to-connect-to
-oemsjmsd</parameter>
<parameter
name="transport.jms.ConnectionFactoryJNDIName">java:comp/env/jms/PlayerC
onnectionFactory</parameter>
<parameter name="transport.jms.ConnectionFactoryType"
locked="false">queue</parameter>
<parameter name="java.naming.security.principal"
locked="false">test</parameter>
<parameter name="java.naming.security.credentials"
locked="false">test</parameter>
</parameter>
</transportReceiver>
Thanks,
Gregg
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
Re: Switching transports - JMS to http using AQ
Posted by Mustafa Cayci <mu...@gmail.com>.
Hello,
I tried that and did not work either. Besides if I use my standalone Java
client, it is working with either or them.
Mustafa
On Feb 12, 2008 10:01 AM, <gr...@accenture.com> wrote:
> I think you'll need to choose a connection factory that is an
> implementation of QueueConnectionFactory not just ConnectionFactory. It
> seems that Synapse cannot handle just implementations of
> ConnectionFactory because the code needs to determine if it's a Queue or
> a Topic.
>
> -Gregg
>
> -----Original Message-----
> From: Mustafa Cayci [mailto:mustafa.cayci@gmail.com]
> Sent: Tuesday, February 12, 2008 9:19 AM
> To: user@synapse.apache.org
> Subject: Re: Switching transports - JMS to http using AQ
>
> Hello Asankha,
>
> I am working with Gregg on this issue. I have modified the axis2.xml
> file
> as follows
>
> ...
> <parameter
> name="transport.jms.ConnectionFactoryJNDIName">java:comp/resource/OEMSJM
> SDReference/ConnectionFactories/CF</parameter>
> ...
>
> This should directly lookup and connect to physical source by means of
> resource provider (OEMSJMSDReference). The resource provider is defined
> as
> follows in orion-application.xml file
>
> <resource-provider class="oracle.jms.OjmsContext"
> name="OEMSJMSDReference">
> <property name="datasource"
> value="jdbc/xa/MyChannelDemoDataSource"></property>
> </resource-provider>
>
> and the datasource is the actual JDBC data base connection. Ok so far?
>
> Now, when I tried to start the Synapse, I am getting the below error
>
> ConnectionFactory Connected to the JMS connection factory :
> java:comp/resource/O
> EMSJMSDReference/ConnectionFactories/CF
> java.lang.ClassCastException: oracle.jms.AQjmsConnectionFactory
> at
> org.apache.synapse.transport.jms.JMSConnectionFactory.connectAndListe
> n(JMSConnectionFactory.java:226)
> at org.apache.synapse.transport.jms.JMSListener.start(
> JMSListener.java:9
> 9)
> at org.apache.axis2.engine.ListenerManager.addListener(
> ListenerManager.j
> ava:205)
> at
> org.apache.synapse.ServerManager.start(ServerManager.java:103)
> at org.apache.synapse.SynapseServer.main(SynapseServer.java:49)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.
> java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.tanukisoftware.wrapper.WrapperSimpleApp.run(
> WrapperSimpleApp.java
> :240)
> at java.lang.Thread.run(Thread.java:595)
>
> Mustafa
>
>
>
>
> On Feb 11, 2008 11:12 PM, Asankha C. Perera <as...@wso2.com> wrote:
>
> > Can you post the body of a sample messages put on the OUT_QUEUE by
> your
> > MDB.. is it a JMS TextMessage?.. any specific headers you use etc?
> Also,
> > do you think Synapse encounters a fault processing it? If so, the log
> > should show more information.. and to re-check, you are stating that
> > this works fine with ActiveMQ? One option is to put a <log
> > level="full"/> mediator as the first mediator on the inSequence of the
> > JMS Proxy and get a log...
> >
> > asankha
> >
> > gregg.j.blais@accenture.com wrote:
> > > Yes, it still only picks up a single message off the OUT_QUEUE at
> > > startup.
> > >
> > > -Gregg
> > >
> > > -----Original Message-----
> > > From: Asankha C. Perera [mailto:asankha@wso2.com]
> > > Sent: Monday, February 11, 2008 2:22 PM
> > > To: user@synapse.apache.org
> > > Subject: Re: Switching transports - JMS to http using AQ
> > >
> > > Greg
> > >
> > > So.. I am not sure.. do you still have a problem with the attached
> > > config ?
> > >
> > > asankha
> > >
> > > gregg.j.blais@accenture.com wrote:
> > >
> > >> Ahh, I forgot that I only showed the JMS->HTTP side in my original
> > >> email. Here's the synapse.xml I'm using:
> > >>
> > >> <!--
> > >> ~ 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.
> > >> -->
> > >>
> > >> <!-- Introduction to switching transports - JMS to http/s -->
> > >> <definitions xmlns="http://ws.apache.org/ns/synapse">
> > >> <proxy name="StockQuoteProxy" transports="http">
> > >> <target>
> > >> <endpoint>
> > >> <address
> > >>
> > >>
> > >
> uri="jms:/java:comp/env/jms/PlayerCommandDestination?transport.jms.Conne
> > >
> > >
> ctionFactoryJNDIName=java:comp/env/jms/PlayerConnectionFactory&java.
> > >
> > >
> naming.factory.initial=oracle.j2ee.naming.ApplicationClientInitialContex
> > >
> > >
> tFactory&java.naming.provider.url=ormi://localhost:23791/how-to-conn
> > >
> > >
> ect-to-oemsjmsd&java.naming.security.principal=MyChannelDemoUser&
> > >
> > >
> ;java.naming.security.credentials=MyChannelDemoPassword&transport.jm
> > >
> > >> s.DestinationType=queue">
> > >> <enableAddressing/>
> > >> </address>
> > >> </endpoint>
> > >> <inSequence>
> > >> <property action="set" name="OUT_ONLY"
> value="true"/>
> > >> </inSequence>
> > >> <outSequence>
> > >> <send/>
> > >> </outSequence>
> > >> </target>
> > >> <publishWSDL
> > >>
> > >>
> > >
> uri="file:repository/conf/sample/resources/proxy/sample_proxy_1.wsdl"/>
> > >
> > >> </proxy>
> > >> <proxy name="JMSProxy" transports="jms">
> > >> <target>
> > >> <inSequence>
> > >> <property action="set" name="OUT_ONLY"
> value="true"/>
> > >> </inSequence>
> > >> <endpoint>
> > >> <address
> > >> uri="http://localhost:9000/soap/SimpleStockQuoteService">
> > >> <enableAddressing/>
> > >> </address>
> > >> </endpoint>
> > >> <outSequence>
> > >> <property action="set" name="Action"
> > >> value="urn:placeOrder"/>
> > >> <send/>
> > >> </outSequence>
> > >> </target>
> > >> <parameter
> > >>
> > >>
> > >
> name="transport.jms.Destination">java:comp/env/jms/OutQueue</parameter>
> > >
> > >> <publishWSDL
> > >>
> > >>
> > >
> uri="file:repository/conf/sample/resources/proxy/sample_proxy_1.wsdl"/>
> > >
> > >> </proxy>
> > >> </definitions>
> > >>
> > >> -----Original Message-----
> > >> From: Asankha C. Perera [mailto:asankha@wso2.com]
> > >> Sent: Monday, February 11, 2008 1:57 PM
> > >> To: user@synapse.apache.org
> > >> Subject: Re: Switching transports - JMS to http using AQ
> > >>
> > >> Greg
> > >>
> > >>
> > >>> Thanks for all your help so far Ashanka. Sorry for my confusion.
> > >>>
> > >>>
> > >> Np! .. thats what this user list is for :-)
> > >>
> > >>
> > >>> Is the scenario you describe below possible using just
> configuration
> > >>>
> > >>>
> > >> via
> > >>
> > >>
> > >>> the synapse.xml file, or is this something that I'm going to need
> to
> > >>> write custom services for?
> > >>>
> > >>>
> > >>>
> > >> This is possible via just configuring the synapse.xml.. its
> actually
> > >> trivial, instead of just one proxy service, you just define two
> proxy
> > >> services.. one to convert from http->jms and the other for
> jms->http..
> > >>
> > >> If you still have any issues on this, do let us know and one of us
> > >>
> > > will
> > >
> > >> help you more
> > >>
> > >> asankha
> > >>
> > >>
> > >>
> > >> This message is for the designated recipient only and may contain
> > >>
> > > privileged, proprietary, or otherwise private information. If you
> have
> > > received it in error, please notify the sender immediately and
> delete
> > > the original. Any other use of the email by you is prohibited.
> > >
> > >>
> > >>
> > >
> > >
> > > This message is for the designated recipient only and may contain
> > privileged, proprietary, or otherwise private information. If you
> have
> > received it in error, please notify the sender immediately and delete
> the
> > original. Any other use of the email by you is prohibited.
> > >
> > >
> >
>
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise private information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the email by you is prohibited.
>
RE: Switching transports - JMS to http using AQ
Posted by gr...@accenture.com.
I think you'll need to choose a connection factory that is an
implementation of QueueConnectionFactory not just ConnectionFactory. It
seems that Synapse cannot handle just implementations of
ConnectionFactory because the code needs to determine if it's a Queue or
a Topic.
-Gregg
-----Original Message-----
From: Mustafa Cayci [mailto:mustafa.cayci@gmail.com]
Sent: Tuesday, February 12, 2008 9:19 AM
To: user@synapse.apache.org
Subject: Re: Switching transports - JMS to http using AQ
Hello Asankha,
I am working with Gregg on this issue. I have modified the axis2.xml
file
as follows
...
<parameter
name="transport.jms.ConnectionFactoryJNDIName">java:comp/resource/OEMSJM
SDReference/ConnectionFactories/CF</parameter>
...
This should directly lookup and connect to physical source by means of
resource provider (OEMSJMSDReference). The resource provider is defined
as
follows in orion-application.xml file
<resource-provider class="oracle.jms.OjmsContext"
name="OEMSJMSDReference">
<property name="datasource"
value="jdbc/xa/MyChannelDemoDataSource"></property>
</resource-provider>
and the datasource is the actual JDBC data base connection. Ok so far?
Now, when I tried to start the Synapse, I am getting the below error
ConnectionFactory Connected to the JMS connection factory :
java:comp/resource/O
EMSJMSDReference/ConnectionFactories/CF
java.lang.ClassCastException: oracle.jms.AQjmsConnectionFactory
at
org.apache.synapse.transport.jms.JMSConnectionFactory.connectAndListe
n(JMSConnectionFactory.java:226)
at org.apache.synapse.transport.jms.JMSListener.start(
JMSListener.java:9
9)
at org.apache.axis2.engine.ListenerManager.addListener(
ListenerManager.j
ava:205)
at
org.apache.synapse.ServerManager.start(ServerManager.java:103)
at org.apache.synapse.SynapseServer.main(SynapseServer.java:49)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.tanukisoftware.wrapper.WrapperSimpleApp.run(
WrapperSimpleApp.java
:240)
at java.lang.Thread.run(Thread.java:595)
Mustafa
On Feb 11, 2008 11:12 PM, Asankha C. Perera <as...@wso2.com> wrote:
> Can you post the body of a sample messages put on the OUT_QUEUE by
your
> MDB.. is it a JMS TextMessage?.. any specific headers you use etc?
Also,
> do you think Synapse encounters a fault processing it? If so, the log
> should show more information.. and to re-check, you are stating that
> this works fine with ActiveMQ? One option is to put a <log
> level="full"/> mediator as the first mediator on the inSequence of the
> JMS Proxy and get a log...
>
> asankha
>
> gregg.j.blais@accenture.com wrote:
> > Yes, it still only picks up a single message off the OUT_QUEUE at
> > startup.
> >
> > -Gregg
> >
> > -----Original Message-----
> > From: Asankha C. Perera [mailto:asankha@wso2.com]
> > Sent: Monday, February 11, 2008 2:22 PM
> > To: user@synapse.apache.org
> > Subject: Re: Switching transports - JMS to http using AQ
> >
> > Greg
> >
> > So.. I am not sure.. do you still have a problem with the attached
> > config ?
> >
> > asankha
> >
> > gregg.j.blais@accenture.com wrote:
> >
> >> Ahh, I forgot that I only showed the JMS->HTTP side in my original
> >> email. Here's the synapse.xml I'm using:
> >>
> >> <!--
> >> ~ 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.
> >> -->
> >>
> >> <!-- Introduction to switching transports - JMS to http/s -->
> >> <definitions xmlns="http://ws.apache.org/ns/synapse">
> >> <proxy name="StockQuoteProxy" transports="http">
> >> <target>
> >> <endpoint>
> >> <address
> >>
> >>
> >
uri="jms:/java:comp/env/jms/PlayerCommandDestination?transport.jms.Conne
> >
> >
ctionFactoryJNDIName=java:comp/env/jms/PlayerConnectionFactory&java.
> >
> >
naming.factory.initial=oracle.j2ee.naming.ApplicationClientInitialContex
> >
> >
tFactory&java.naming.provider.url=ormi://localhost:23791/how-to-conn
> >
> >
ect-to-oemsjmsd&java.naming.security.principal=MyChannelDemoUser&
> >
> >
;java.naming.security.credentials=MyChannelDemoPassword&transport.jm
> >
> >> s.DestinationType=queue">
> >> <enableAddressing/>
> >> </address>
> >> </endpoint>
> >> <inSequence>
> >> <property action="set" name="OUT_ONLY"
value="true"/>
> >> </inSequence>
> >> <outSequence>
> >> <send/>
> >> </outSequence>
> >> </target>
> >> <publishWSDL
> >>
> >>
> >
uri="file:repository/conf/sample/resources/proxy/sample_proxy_1.wsdl"/>
> >
> >> </proxy>
> >> <proxy name="JMSProxy" transports="jms">
> >> <target>
> >> <inSequence>
> >> <property action="set" name="OUT_ONLY"
value="true"/>
> >> </inSequence>
> >> <endpoint>
> >> <address
> >> uri="http://localhost:9000/soap/SimpleStockQuoteService">
> >> <enableAddressing/>
> >> </address>
> >> </endpoint>
> >> <outSequence>
> >> <property action="set" name="Action"
> >> value="urn:placeOrder"/>
> >> <send/>
> >> </outSequence>
> >> </target>
> >> <parameter
> >>
> >>
> >
name="transport.jms.Destination">java:comp/env/jms/OutQueue</parameter>
> >
> >> <publishWSDL
> >>
> >>
> >
uri="file:repository/conf/sample/resources/proxy/sample_proxy_1.wsdl"/>
> >
> >> </proxy>
> >> </definitions>
> >>
> >> -----Original Message-----
> >> From: Asankha C. Perera [mailto:asankha@wso2.com]
> >> Sent: Monday, February 11, 2008 1:57 PM
> >> To: user@synapse.apache.org
> >> Subject: Re: Switching transports - JMS to http using AQ
> >>
> >> Greg
> >>
> >>
> >>> Thanks for all your help so far Ashanka. Sorry for my confusion.
> >>>
> >>>
> >> Np! .. thats what this user list is for :-)
> >>
> >>
> >>> Is the scenario you describe below possible using just
configuration
> >>>
> >>>
> >> via
> >>
> >>
> >>> the synapse.xml file, or is this something that I'm going to need
to
> >>> write custom services for?
> >>>
> >>>
> >>>
> >> This is possible via just configuring the synapse.xml.. its
actually
> >> trivial, instead of just one proxy service, you just define two
proxy
> >> services.. one to convert from http->jms and the other for
jms->http..
> >>
> >> If you still have any issues on this, do let us know and one of us
> >>
> > will
> >
> >> help you more
> >>
> >> asankha
> >>
> >>
> >>
> >> This message is for the designated recipient only and may contain
> >>
> > privileged, proprietary, or otherwise private information. If you
have
> > received it in error, please notify the sender immediately and
delete
> > the original. Any other use of the email by you is prohibited.
> >
> >>
> >>
> >
> >
> > This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise private information. If you
have
> received it in error, please notify the sender immediately and delete
the
> original. Any other use of the email by you is prohibited.
> >
> >
>
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
Re: Switching transports - JMS to http using AQ
Posted by "Asankha C. Perera" <as...@wso2.com>.
Gregg
> These two threads seem to point at the exact issue that we are seeing:
>
> http://forums.oracle.com/forums/thread.jspa?messageID=2156176
>
> and
>
> http://forums.oracle.com/forums/thread.jspa?messageID=2209776
>
The last comment on this points to Oracle 10.2.0.3 to overcome this? Is
there any possibility for you to use this driver on the Synapse/Client side?
> Ashanka,
>
> The Synapse code uses the setMessageListener method to create a listener
> for the Queue, right?
>
Yes, Check
http://svn.apache.org/viewvc/synapse/trunk/java/modules/transports/src/main/java/org/apache/synapse/transport/jms/JMSConnectionFactory.java?view=markup
and method startListeningOnDestination()
Note that in general, we are keeping compatibility with JMS 1.0.x (i.e.
the previously discussed cast to a QueueConnectionFactory etc) as there
are users who has this in production with old JMS systems
asankha
RE: Switching transports - JMS to http using AQ
Posted by gr...@accenture.com.
These two threads seem to point at the exact issue that we are seeing:
http://forums.oracle.com/forums/thread.jspa?messageID=2156176
and
http://forums.oracle.com/forums/thread.jspa?messageID=2209776
Ashanka,
The Synapse code uses the setMessageListener method to create a listener
for the Queue, right?
-Gregg
-----Original Message-----
From: Mustafa Cayci [mailto:mustafa.cayci@gmail.com]
Sent: Tuesday, February 12, 2008 11:15 AM
To: user@synapse.apache.org
Subject: Re: Switching transports - JMS to http using AQ
Hi Asankha,
There are two types of credentials. As you know, Gregg developed a
standalone JCA adapter. He generated a "rar" file and deployed to
Oracle
Application Server using the application server account. Now, he also
created actual AQ queue objects in Oracle database by using a different
set
of user information. Please note that the Oracle database user is not
the
same user as the Oracle Application server user. Perhaps Gregg created
them
to be the same but it should not have to be.
Mustafa
On Feb 12, 2008 11:06 AM, Asankha C. Perera <as...@wso2.com> wrote:
> Mustafa
> > No those parameters are for the application server credentials. I
am
> > interested in how I can define credentials for the database schema
> username
> > and password.
> >
> I do not understand what you mean by "the database schema username and
> password"...
> >> Add these two parameters in the axis2.xml file under your
connection
> >> factory:
> >>
> >> <parameter name="java.naming.security.principal"
> >> locked="false">MyChannelDemoUser</parameter>
> >> <parameter name="java.naming.security.credentials"
> >> locked="false">MyChannelDemoPassword</parameter>
> >>
> I think the above should solve your connection problem
>
> asankha
>
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
Re: Switching transports - JMS to http using AQ
Posted by Mustafa Cayci <mu...@gmail.com>.
Hi Asankha,
There are two types of credentials. As you know, Gregg developed a
standalone JCA adapter. He generated a "rar" file and deployed to Oracle
Application Server using the application server account. Now, he also
created actual AQ queue objects in Oracle database by using a different set
of user information. Please note that the Oracle database user is not the
same user as the Oracle Application server user. Perhaps Gregg created them
to be the same but it should not have to be.
Mustafa
On Feb 12, 2008 11:06 AM, Asankha C. Perera <as...@wso2.com> wrote:
> Mustafa
> > No those parameters are for the application server credentials. I am
> > interested in how I can define credentials for the database schema
> username
> > and password.
> >
> I do not understand what you mean by "the database schema username and
> password"...
> >> Add these two parameters in the axis2.xml file under your connection
> >> factory:
> >>
> >> <parameter name="java.naming.security.principal"
> >> locked="false">MyChannelDemoUser</parameter>
> >> <parameter name="java.naming.security.credentials"
> >> locked="false">MyChannelDemoPassword</parameter>
> >>
> I think the above should solve your connection problem
>
> asankha
>
Re: Switching transports - JMS to http using AQ
Posted by "Asankha C. Perera" <as...@wso2.com>.
Mustafa
> No those parameters are for the application server credentials. I am
> interested in how I can define credentials for the database schema username
> and password.
>
I do not understand what you mean by "the database schema username and
password"...
>> Add these two parameters in the axis2.xml file under your connection
>> factory:
>>
>> <parameter name="java.naming.security.principal"
>> locked="false">MyChannelDemoUser</parameter>
>> <parameter name="java.naming.security.credentials"
>> locked="false">MyChannelDemoPassword</parameter>
>>
I think the above should solve your connection problem
asankha
Re: Switching transports - JMS to http using AQ
Posted by Mustafa Cayci <mu...@gmail.com>.
Gregg,
No those parameters are for the application server credentials. I am
interested in how I can define credentials for the database schema username
and password.
Mustafa
On Feb 12, 2008 10:56 AM, <gr...@accenture.com> wrote:
> Add these two parameters in the axis2.xml file under your connection
> factory:
>
> <parameter name="java.naming.security.principal"
> locked="false">MyChannelDemoUser</parameter>
> <parameter name="java.naming.security.credentials"
> locked="false">MyChannelDemoPassword</parameter>
>
> -----Original Message-----
> From: Mustafa Cayci [mailto:mustafa.cayci@gmail.com]
> Sent: Tuesday, February 12, 2008 10:52 AM
> To: user@synapse.apache.org
> Subject: Re: Switching transports - JMS to http using AQ
>
> Hello Asankha,
>
> Ok, I used "QueueConnectionFactories/QCF" instead of
> "ConnectionFactories/CF" and went beyond that issue and run into this
> one
> below
>
> ===============
> ConnectionFactory Error connecting to Connection Factory :
> java:comp/resource/OE
> MSJMSDReference/QueueConnectionFactories/QCF
> javax.jms.JMSSecurityException: JMS-232: An invalid user/password was
> specified
> for the JMS connection
> at oracle.jms.AQjmsDBConnMgr.checkForSecurityException(
> AQjmsDBConnMgr.ja
> va:916)
> at
> oracle.jms.AQjmsDBConnMgr.getConnection(AQjmsDBConnMgr.java:601)
> at oracle.jms.AQjmsDBConnMgr.<init>(AQjmsDBConnMgr.java:383)
> at oracle.jms.AQjmsConnection.<init>(AQjmsConnection.java:247)
> at oracle.jms.AQjmsQueueConnectionFactory.createQueueConnection
> (AQjmsQue
> ueConnectionFactory.java:299)
> at
> org.apache.synapse.transport.jms.JMSConnectionFactory.connectAndListe
> n(JMSConnectionFactory.java:238)
> ============
>
> As you see, it is now trying to create an actual connection with a user
> name
> and password. How do I tell what username and password, the Synapse is
> trying to use? Is it the one I defined in axis2.xml?
>
> Thanks,
>
> Mustafa
>
>
> On Feb 12, 2008 10:19 AM, Asankha C. Perera <as...@wso2.com> wrote:
>
> > Mustafa
> >
> > For some reason my mails keep getting rejected as the mail server
> thinks
> > its spam..
> > anyway.. here is what I wanted to let you know
> >
> > This is what we do at that line:
> > context = new InitialContext(jndiProperties);
> > conFactory = (ConnectionFactory) context.lookup
> > (connFactoryJNDIName);
> > log.info("Connected to the JMS connection factory : " +
> > connFactoryJNDIName);
> >
> > try {
> > ConnectionFactory conFac = null;
> > QueueConnectionFactory qConFac = null;
> > TopicConnectionFactory tConFac = null;
> > if
> >
> (JMSConstants.DESTINATION_TYPE_QUEUE.equals(getConnectionFactoryType()))
> {
> > * qConFac = (QueueConnectionFactory) conFactory;*
> > ....
> >
> > So, it seems like what is bound to JNDI as the JMS connection factory
> > does not implement the javax.jms.QueueConnectionFactory interface..
> > maybe this is a known issue with AQ?
> >
> > However, what I do not quite understand is how the sample JMS client
> > that Greg tried worked with AQ.. his code contains the following
> lines:
> >
> > queueConnectionFactory = (QueueConnectionFactory)
> jndiContext.lookup("java:comp/env/jms/PlayerConnectionFactory");Re:
> > Switching transports - JMS to http using AQ
> > queue = (Queue) jndiContext.lookup(queueName);
> >
> >
> > asankha
> >
>
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise private information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the email by you is prohibited.
>
RE: Switching transports - JMS to http using AQ
Posted by gr...@accenture.com.
Add these two parameters in the axis2.xml file under your connection
factory:
<parameter name="java.naming.security.principal"
locked="false">MyChannelDemoUser</parameter>
<parameter name="java.naming.security.credentials"
locked="false">MyChannelDemoPassword</parameter>
-----Original Message-----
From: Mustafa Cayci [mailto:mustafa.cayci@gmail.com]
Sent: Tuesday, February 12, 2008 10:52 AM
To: user@synapse.apache.org
Subject: Re: Switching transports - JMS to http using AQ
Hello Asankha,
Ok, I used "QueueConnectionFactories/QCF" instead of
"ConnectionFactories/CF" and went beyond that issue and run into this
one
below
===============
ConnectionFactory Error connecting to Connection Factory :
java:comp/resource/OE
MSJMSDReference/QueueConnectionFactories/QCF
javax.jms.JMSSecurityException: JMS-232: An invalid user/password was
specified
for the JMS connection
at oracle.jms.AQjmsDBConnMgr.checkForSecurityException(
AQjmsDBConnMgr.ja
va:916)
at
oracle.jms.AQjmsDBConnMgr.getConnection(AQjmsDBConnMgr.java:601)
at oracle.jms.AQjmsDBConnMgr.<init>(AQjmsDBConnMgr.java:383)
at oracle.jms.AQjmsConnection.<init>(AQjmsConnection.java:247)
at oracle.jms.AQjmsQueueConnectionFactory.createQueueConnection
(AQjmsQue
ueConnectionFactory.java:299)
at
org.apache.synapse.transport.jms.JMSConnectionFactory.connectAndListe
n(JMSConnectionFactory.java:238)
============
As you see, it is now trying to create an actual connection with a user
name
and password. How do I tell what username and password, the Synapse is
trying to use? Is it the one I defined in axis2.xml?
Thanks,
Mustafa
On Feb 12, 2008 10:19 AM, Asankha C. Perera <as...@wso2.com> wrote:
> Mustafa
>
> For some reason my mails keep getting rejected as the mail server
thinks
> its spam..
> anyway.. here is what I wanted to let you know
>
> This is what we do at that line:
> context = new InitialContext(jndiProperties);
> conFactory = (ConnectionFactory) context.lookup
> (connFactoryJNDIName);
> log.info("Connected to the JMS connection factory : " +
> connFactoryJNDIName);
>
> try {
> ConnectionFactory conFac = null;
> QueueConnectionFactory qConFac = null;
> TopicConnectionFactory tConFac = null;
> if
>
(JMSConstants.DESTINATION_TYPE_QUEUE.equals(getConnectionFactoryType()))
{
> * qConFac = (QueueConnectionFactory) conFactory;*
> ....
>
> So, it seems like what is bound to JNDI as the JMS connection factory
> does not implement the javax.jms.QueueConnectionFactory interface..
> maybe this is a known issue with AQ?
>
> However, what I do not quite understand is how the sample JMS client
> that Greg tried worked with AQ.. his code contains the following
lines:
>
> queueConnectionFactory = (QueueConnectionFactory)
jndiContext.lookup("java:comp/env/jms/PlayerConnectionFactory");Re:
> Switching transports - JMS to http using AQ
> queue = (Queue) jndiContext.lookup(queueName);
>
>
> asankha
>
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
Re: Switching transports - JMS to http using AQ
Posted by Mustafa Cayci <mu...@gmail.com>.
Hello Asankha,
Ok, I used "QueueConnectionFactories/QCF" instead of
"ConnectionFactories/CF" and went beyond that issue and run into this one
below
===============
ConnectionFactory Error connecting to Connection Factory :
java:comp/resource/OE
MSJMSDReference/QueueConnectionFactories/QCF
javax.jms.JMSSecurityException: JMS-232: An invalid user/password was
specified
for the JMS connection
at oracle.jms.AQjmsDBConnMgr.checkForSecurityException(
AQjmsDBConnMgr.ja
va:916)
at oracle.jms.AQjmsDBConnMgr.getConnection(AQjmsDBConnMgr.java:601)
at oracle.jms.AQjmsDBConnMgr.<init>(AQjmsDBConnMgr.java:383)
at oracle.jms.AQjmsConnection.<init>(AQjmsConnection.java:247)
at oracle.jms.AQjmsQueueConnectionFactory.createQueueConnection
(AQjmsQue
ueConnectionFactory.java:299)
at
org.apache.synapse.transport.jms.JMSConnectionFactory.connectAndListe
n(JMSConnectionFactory.java:238)
============
As you see, it is now trying to create an actual connection with a user name
and password. How do I tell what username and password, the Synapse is
trying to use? Is it the one I defined in axis2.xml?
Thanks,
Mustafa
On Feb 12, 2008 10:19 AM, Asankha C. Perera <as...@wso2.com> wrote:
> Mustafa
>
> For some reason my mails keep getting rejected as the mail server thinks
> its spam..
> anyway.. here is what I wanted to let you know
>
> This is what we do at that line:
> context = new InitialContext(jndiProperties);
> conFactory = (ConnectionFactory) context.lookup
> (connFactoryJNDIName);
> log.info("Connected to the JMS connection factory : " +
> connFactoryJNDIName);
>
> try {
> ConnectionFactory conFac = null;
> QueueConnectionFactory qConFac = null;
> TopicConnectionFactory tConFac = null;
> if
> (JMSConstants.DESTINATION_TYPE_QUEUE.equals(getConnectionFactoryType())) {
> * qConFac = (QueueConnectionFactory) conFactory;*
> ....
>
> So, it seems like what is bound to JNDI as the JMS connection factory
> does not implement the javax.jms.QueueConnectionFactory interface..
> maybe this is a known issue with AQ?
>
> However, what I do not quite understand is how the sample JMS client
> that Greg tried worked with AQ.. his code contains the following lines:
>
> queueConnectionFactory = (QueueConnectionFactory) jndiContext.lookup("java:comp/env/jms/PlayerConnectionFactory");Re:
> Switching transports - JMS to http using AQ
> queue = (Queue) jndiContext.lookup(queueName);
>
>
> asankha
>
Re: Switching transports - JMS to http using AQ
Posted by "Asankha C. Perera" <as...@wso2.com>.
Mustafa
For some reason my mails keep getting rejected as the mail server thinks
its spam..
anyway.. here is what I wanted to let you know
This is what we do at that line:
context = new InitialContext(jndiProperties);
conFactory = (ConnectionFactory) context.lookup(connFactoryJNDIName);
log.info("Connected to the JMS connection factory : " + connFactoryJNDIName);
try {
ConnectionFactory conFac = null;
QueueConnectionFactory qConFac = null;
TopicConnectionFactory tConFac = null;
if
(JMSConstants.DESTINATION_TYPE_QUEUE.equals(getConnectionFactoryType())) {
* qConFac = (QueueConnectionFactory) conFactory;*
....
So, it seems like what is bound to JNDI as the JMS connection factory
does not implement the javax.jms.QueueConnectionFactory interface..
maybe this is a known issue with AQ?
However, what I do not quite understand is how the sample JMS client
that Greg tried worked with AQ.. his code contains the following lines:
queueConnectionFactory = (QueueConnectionFactory) jndiContext.lookup("java:comp/env/jms/PlayerConnectionFactory");Re: Switching transports - JMS to http using AQ
queue = (Queue) jndiContext.lookup(queueName);
asankha
Re: Switching transports - JMS to http using AQ
Posted by Mustafa Cayci <mu...@gmail.com>.
Hello Asankha,
I am working with Gregg on this issue. I have modified the axis2.xml file
as follows
...
<parameter
name="transport.jms.ConnectionFactoryJNDIName">java:comp/resource/OEMSJMSDReference/ConnectionFactories/CF</parameter>
...
This should directly lookup and connect to physical source by means of
resource provider (OEMSJMSDReference). The resource provider is defined as
follows in orion-application.xml file
<resource-provider class="oracle.jms.OjmsContext"
name="OEMSJMSDReference">
<property name="datasource"
value="jdbc/xa/MyChannelDemoDataSource"></property>
</resource-provider>
and the datasource is the actual JDBC data base connection. Ok so far?
Now, when I tried to start the Synapse, I am getting the below error
ConnectionFactory Connected to the JMS connection factory :
java:comp/resource/O
EMSJMSDReference/ConnectionFactories/CF
java.lang.ClassCastException: oracle.jms.AQjmsConnectionFactory
at
org.apache.synapse.transport.jms.JMSConnectionFactory.connectAndListe
n(JMSConnectionFactory.java:226)
at org.apache.synapse.transport.jms.JMSListener.start(
JMSListener.java:9
9)
at org.apache.axis2.engine.ListenerManager.addListener(
ListenerManager.j
ava:205)
at org.apache.synapse.ServerManager.start(ServerManager.java:103)
at org.apache.synapse.SynapseServer.main(SynapseServer.java:49)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.tanukisoftware.wrapper.WrapperSimpleApp.run(
WrapperSimpleApp.java
:240)
at java.lang.Thread.run(Thread.java:595)
Mustafa
On Feb 11, 2008 11:12 PM, Asankha C. Perera <as...@wso2.com> wrote:
> Can you post the body of a sample messages put on the OUT_QUEUE by your
> MDB.. is it a JMS TextMessage?.. any specific headers you use etc? Also,
> do you think Synapse encounters a fault processing it? If so, the log
> should show more information.. and to re-check, you are stating that
> this works fine with ActiveMQ? One option is to put a <log
> level="full"/> mediator as the first mediator on the inSequence of the
> JMS Proxy and get a log...
>
> asankha
>
> gregg.j.blais@accenture.com wrote:
> > Yes, it still only picks up a single message off the OUT_QUEUE at
> > startup.
> >
> > -Gregg
> >
> > -----Original Message-----
> > From: Asankha C. Perera [mailto:asankha@wso2.com]
> > Sent: Monday, February 11, 2008 2:22 PM
> > To: user@synapse.apache.org
> > Subject: Re: Switching transports - JMS to http using AQ
> >
> > Greg
> >
> > So.. I am not sure.. do you still have a problem with the attached
> > config ?
> >
> > asankha
> >
> > gregg.j.blais@accenture.com wrote:
> >
> >> Ahh, I forgot that I only showed the JMS->HTTP side in my original
> >> email. Here's the synapse.xml I'm using:
> >>
> >> <!--
> >> ~ 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.
> >> -->
> >>
> >> <!-- Introduction to switching transports - JMS to http/s -->
> >> <definitions xmlns="http://ws.apache.org/ns/synapse">
> >> <proxy name="StockQuoteProxy" transports="http">
> >> <target>
> >> <endpoint>
> >> <address
> >>
> >>
> > uri="jms:/java:comp/env/jms/PlayerCommandDestination?transport.jms.Conne
> >
> > ctionFactoryJNDIName=java:comp/env/jms/PlayerConnectionFactory&java.
> >
> > naming.factory.initial=oracle.j2ee.naming.ApplicationClientInitialContex
> >
> > tFactory&java.naming.provider.url=ormi://localhost:23791/how-to-conn
> >
> > ect-to-oemsjmsd&java.naming.security.principal=MyChannelDemoUser&
> >
> > ;java.naming.security.credentials=MyChannelDemoPassword&transport.jm
> >
> >> s.DestinationType=queue">
> >> <enableAddressing/>
> >> </address>
> >> </endpoint>
> >> <inSequence>
> >> <property action="set" name="OUT_ONLY" value="true"/>
> >> </inSequence>
> >> <outSequence>
> >> <send/>
> >> </outSequence>
> >> </target>
> >> <publishWSDL
> >>
> >>
> > uri="file:repository/conf/sample/resources/proxy/sample_proxy_1.wsdl"/>
> >
> >> </proxy>
> >> <proxy name="JMSProxy" transports="jms">
> >> <target>
> >> <inSequence>
> >> <property action="set" name="OUT_ONLY" value="true"/>
> >> </inSequence>
> >> <endpoint>
> >> <address
> >> uri="http://localhost:9000/soap/SimpleStockQuoteService">
> >> <enableAddressing/>
> >> </address>
> >> </endpoint>
> >> <outSequence>
> >> <property action="set" name="Action"
> >> value="urn:placeOrder"/>
> >> <send/>
> >> </outSequence>
> >> </target>
> >> <parameter
> >>
> >>
> > name="transport.jms.Destination">java:comp/env/jms/OutQueue</parameter>
> >
> >> <publishWSDL
> >>
> >>
> > uri="file:repository/conf/sample/resources/proxy/sample_proxy_1.wsdl"/>
> >
> >> </proxy>
> >> </definitions>
> >>
> >> -----Original Message-----
> >> From: Asankha C. Perera [mailto:asankha@wso2.com]
> >> Sent: Monday, February 11, 2008 1:57 PM
> >> To: user@synapse.apache.org
> >> Subject: Re: Switching transports - JMS to http using AQ
> >>
> >> Greg
> >>
> >>
> >>> Thanks for all your help so far Ashanka. Sorry for my confusion.
> >>>
> >>>
> >> Np! .. thats what this user list is for :-)
> >>
> >>
> >>> Is the scenario you describe below possible using just configuration
> >>>
> >>>
> >> via
> >>
> >>
> >>> the synapse.xml file, or is this something that I'm going to need to
> >>> write custom services for?
> >>>
> >>>
> >>>
> >> This is possible via just configuring the synapse.xml.. its actually
> >> trivial, instead of just one proxy service, you just define two proxy
> >> services.. one to convert from http->jms and the other for jms->http..
> >>
> >> If you still have any issues on this, do let us know and one of us
> >>
> > will
> >
> >> help you more
> >>
> >> asankha
> >>
> >>
> >>
> >> This message is for the designated recipient only and may contain
> >>
> > privileged, proprietary, or otherwise private information. If you have
> > received it in error, please notify the sender immediately and delete
> > the original. Any other use of the email by you is prohibited.
> >
> >>
> >>
> >
> >
> > This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise private information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the email by you is prohibited.
> >
> >
>
Re: Switching transports - JMS to http using AQ
Posted by "Asankha C. Perera" <as...@wso2.com>.
Can you post the body of a sample messages put on the OUT_QUEUE by your
MDB.. is it a JMS TextMessage?.. any specific headers you use etc? Also,
do you think Synapse encounters a fault processing it? If so, the log
should show more information.. and to re-check, you are stating that
this works fine with ActiveMQ? One option is to put a <log
level="full"/> mediator as the first mediator on the inSequence of the
JMS Proxy and get a log...
asankha
gregg.j.blais@accenture.com wrote:
> Yes, it still only picks up a single message off the OUT_QUEUE at
> startup.
>
> -Gregg
>
> -----Original Message-----
> From: Asankha C. Perera [mailto:asankha@wso2.com]
> Sent: Monday, February 11, 2008 2:22 PM
> To: user@synapse.apache.org
> Subject: Re: Switching transports - JMS to http using AQ
>
> Greg
>
> So.. I am not sure.. do you still have a problem with the attached
> config ?
>
> asankha
>
> gregg.j.blais@accenture.com wrote:
>
>> Ahh, I forgot that I only showed the JMS->HTTP side in my original
>> email. Here's the synapse.xml I'm using:
>>
>> <!--
>> ~ 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.
>> -->
>>
>> <!-- Introduction to switching transports - JMS to http/s -->
>> <definitions xmlns="http://ws.apache.org/ns/synapse">
>> <proxy name="StockQuoteProxy" transports="http">
>> <target>
>> <endpoint>
>> <address
>>
>>
> uri="jms:/java:comp/env/jms/PlayerCommandDestination?transport.jms.Conne
>
> ctionFactoryJNDIName=java:comp/env/jms/PlayerConnectionFactory&java.
>
> naming.factory.initial=oracle.j2ee.naming.ApplicationClientInitialContex
>
> tFactory&java.naming.provider.url=ormi://localhost:23791/how-to-conn
>
> ect-to-oemsjmsd&java.naming.security.principal=MyChannelDemoUser&
>
> ;java.naming.security.credentials=MyChannelDemoPassword&transport.jm
>
>> s.DestinationType=queue">
>> <enableAddressing/>
>> </address>
>> </endpoint>
>> <inSequence>
>> <property action="set" name="OUT_ONLY" value="true"/>
>> </inSequence>
>> <outSequence>
>> <send/>
>> </outSequence>
>> </target>
>> <publishWSDL
>>
>>
> uri="file:repository/conf/sample/resources/proxy/sample_proxy_1.wsdl"/>
>
>> </proxy>
>> <proxy name="JMSProxy" transports="jms">
>> <target>
>> <inSequence>
>> <property action="set" name="OUT_ONLY" value="true"/>
>> </inSequence>
>> <endpoint>
>> <address
>> uri="http://localhost:9000/soap/SimpleStockQuoteService">
>> <enableAddressing/>
>> </address>
>> </endpoint>
>> <outSequence>
>> <property action="set" name="Action"
>> value="urn:placeOrder"/>
>> <send/>
>> </outSequence>
>> </target>
>> <parameter
>>
>>
> name="transport.jms.Destination">java:comp/env/jms/OutQueue</parameter>
>
>> <publishWSDL
>>
>>
> uri="file:repository/conf/sample/resources/proxy/sample_proxy_1.wsdl"/>
>
>> </proxy>
>> </definitions>
>>
>> -----Original Message-----
>> From: Asankha C. Perera [mailto:asankha@wso2.com]
>> Sent: Monday, February 11, 2008 1:57 PM
>> To: user@synapse.apache.org
>> Subject: Re: Switching transports - JMS to http using AQ
>>
>> Greg
>>
>>
>>> Thanks for all your help so far Ashanka. Sorry for my confusion.
>>>
>>>
>> Np! .. thats what this user list is for :-)
>>
>>
>>> Is the scenario you describe below possible using just configuration
>>>
>>>
>> via
>>
>>
>>> the synapse.xml file, or is this something that I'm going to need to
>>> write custom services for?
>>>
>>>
>>>
>> This is possible via just configuring the synapse.xml.. its actually
>> trivial, instead of just one proxy service, you just define two proxy
>> services.. one to convert from http->jms and the other for jms->http..
>>
>> If you still have any issues on this, do let us know and one of us
>>
> will
>
>> help you more
>>
>> asankha
>>
>>
>>
>> This message is for the designated recipient only and may contain
>>
> privileged, proprietary, or otherwise private information. If you have
> received it in error, please notify the sender immediately and delete
> the original. Any other use of the email by you is prohibited.
>
>>
>>
>
>
> This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
>
>
RE: Switching transports - JMS to http using AQ
Posted by gr...@accenture.com.
Yes, it still only picks up a single message off the OUT_QUEUE at
startup.
-Gregg
-----Original Message-----
From: Asankha C. Perera [mailto:asankha@wso2.com]
Sent: Monday, February 11, 2008 2:22 PM
To: user@synapse.apache.org
Subject: Re: Switching transports - JMS to http using AQ
Greg
So.. I am not sure.. do you still have a problem with the attached
config ?
asankha
gregg.j.blais@accenture.com wrote:
> Ahh, I forgot that I only showed the JMS->HTTP side in my original
> email. Here's the synapse.xml I'm using:
>
> <!--
> ~ 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.
> -->
>
> <!-- Introduction to switching transports - JMS to http/s -->
> <definitions xmlns="http://ws.apache.org/ns/synapse">
> <proxy name="StockQuoteProxy" transports="http">
> <target>
> <endpoint>
> <address
>
uri="jms:/java:comp/env/jms/PlayerCommandDestination?transport.jms.Conne
>
ctionFactoryJNDIName=java:comp/env/jms/PlayerConnectionFactory&java.
>
naming.factory.initial=oracle.j2ee.naming.ApplicationClientInitialContex
>
tFactory&java.naming.provider.url=ormi://localhost:23791/how-to-conn
>
ect-to-oemsjmsd&java.naming.security.principal=MyChannelDemoUser&
>
;java.naming.security.credentials=MyChannelDemoPassword&transport.jm
> s.DestinationType=queue">
> <enableAddressing/>
> </address>
> </endpoint>
> <inSequence>
> <property action="set" name="OUT_ONLY" value="true"/>
> </inSequence>
> <outSequence>
> <send/>
> </outSequence>
> </target>
> <publishWSDL
>
uri="file:repository/conf/sample/resources/proxy/sample_proxy_1.wsdl"/>
> </proxy>
> <proxy name="JMSProxy" transports="jms">
> <target>
> <inSequence>
> <property action="set" name="OUT_ONLY" value="true"/>
> </inSequence>
> <endpoint>
> <address
> uri="http://localhost:9000/soap/SimpleStockQuoteService">
> <enableAddressing/>
> </address>
> </endpoint>
> <outSequence>
> <property action="set" name="Action"
> value="urn:placeOrder"/>
> <send/>
> </outSequence>
> </target>
> <parameter
>
name="transport.jms.Destination">java:comp/env/jms/OutQueue</parameter>
> <publishWSDL
>
uri="file:repository/conf/sample/resources/proxy/sample_proxy_1.wsdl"/>
> </proxy>
> </definitions>
>
> -----Original Message-----
> From: Asankha C. Perera [mailto:asankha@wso2.com]
> Sent: Monday, February 11, 2008 1:57 PM
> To: user@synapse.apache.org
> Subject: Re: Switching transports - JMS to http using AQ
>
> Greg
>
>> Thanks for all your help so far Ashanka. Sorry for my confusion.
>>
> Np! .. thats what this user list is for :-)
>
>> Is the scenario you describe below possible using just configuration
>>
> via
>
>> the synapse.xml file, or is this something that I'm going to need to
>> write custom services for?
>>
>>
> This is possible via just configuring the synapse.xml.. its actually
> trivial, instead of just one proxy service, you just define two proxy
> services.. one to convert from http->jms and the other for jms->http..
>
> If you still have any issues on this, do let us know and one of us
will
> help you more
>
> asankha
>
>
>
> This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the sender immediately and delete
the original. Any other use of the email by you is prohibited.
>
>
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
Re: Switching transports - JMS to http using AQ
Posted by "Asankha C. Perera" <as...@wso2.com>.
Greg
So.. I am not sure.. do you still have a problem with the attached config ?
asankha
gregg.j.blais@accenture.com wrote:
> Ahh, I forgot that I only showed the JMS->HTTP side in my original
> email. Here's the synapse.xml I'm using:
>
> <!--
> ~ 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.
> -->
>
> <!-- Introduction to switching transports - JMS to http/s -->
> <definitions xmlns="http://ws.apache.org/ns/synapse">
> <proxy name="StockQuoteProxy" transports="http">
> <target>
> <endpoint>
> <address
> uri="jms:/java:comp/env/jms/PlayerCommandDestination?transport.jms.Conne
> ctionFactoryJNDIName=java:comp/env/jms/PlayerConnectionFactory&java.
> naming.factory.initial=oracle.j2ee.naming.ApplicationClientInitialContex
> tFactory&java.naming.provider.url=ormi://localhost:23791/how-to-conn
> ect-to-oemsjmsd&java.naming.security.principal=MyChannelDemoUser&
> ;java.naming.security.credentials=MyChannelDemoPassword&transport.jm
> s.DestinationType=queue">
> <enableAddressing/>
> </address>
> </endpoint>
> <inSequence>
> <property action="set" name="OUT_ONLY" value="true"/>
> </inSequence>
> <outSequence>
> <send/>
> </outSequence>
> </target>
> <publishWSDL
> uri="file:repository/conf/sample/resources/proxy/sample_proxy_1.wsdl"/>
> </proxy>
> <proxy name="JMSProxy" transports="jms">
> <target>
> <inSequence>
> <property action="set" name="OUT_ONLY" value="true"/>
> </inSequence>
> <endpoint>
> <address
> uri="http://localhost:9000/soap/SimpleStockQuoteService">
> <enableAddressing/>
> </address>
> </endpoint>
> <outSequence>
> <property action="set" name="Action"
> value="urn:placeOrder"/>
> <send/>
> </outSequence>
> </target>
> <parameter
> name="transport.jms.Destination">java:comp/env/jms/OutQueue</parameter>
> <publishWSDL
> uri="file:repository/conf/sample/resources/proxy/sample_proxy_1.wsdl"/>
> </proxy>
> </definitions>
>
> -----Original Message-----
> From: Asankha C. Perera [mailto:asankha@wso2.com]
> Sent: Monday, February 11, 2008 1:57 PM
> To: user@synapse.apache.org
> Subject: Re: Switching transports - JMS to http using AQ
>
> Greg
>
>> Thanks for all your help so far Ashanka. Sorry for my confusion.
>>
> Np! .. thats what this user list is for :-)
>
>> Is the scenario you describe below possible using just configuration
>>
> via
>
>> the synapse.xml file, or is this something that I'm going to need to
>> write custom services for?
>>
>>
> This is possible via just configuring the synapse.xml.. its actually
> trivial, instead of just one proxy service, you just define two proxy
> services.. one to convert from http->jms and the other for jms->http..
>
> If you still have any issues on this, do let us know and one of us will
> help you more
>
> asankha
>
>
>
> This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
>
>
RE: Switching transports - JMS to http using AQ
Posted by gr...@accenture.com.
Ahh, I forgot that I only showed the JMS->HTTP side in my original
email. Here's the synapse.xml I'm using:
<!--
~ 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.
-->
<!-- Introduction to switching transports - JMS to http/s -->
<definitions xmlns="http://ws.apache.org/ns/synapse">
<proxy name="StockQuoteProxy" transports="http">
<target>
<endpoint>
<address
uri="jms:/java:comp/env/jms/PlayerCommandDestination?transport.jms.Conne
ctionFactoryJNDIName=java:comp/env/jms/PlayerConnectionFactory&java.
naming.factory.initial=oracle.j2ee.naming.ApplicationClientInitialContex
tFactory&java.naming.provider.url=ormi://localhost:23791/how-to-conn
ect-to-oemsjmsd&java.naming.security.principal=MyChannelDemoUser&
;java.naming.security.credentials=MyChannelDemoPassword&transport.jm
s.DestinationType=queue">
<enableAddressing/>
</address>
</endpoint>
<inSequence>
<property action="set" name="OUT_ONLY" value="true"/>
</inSequence>
<outSequence>
<send/>
</outSequence>
</target>
<publishWSDL
uri="file:repository/conf/sample/resources/proxy/sample_proxy_1.wsdl"/>
</proxy>
<proxy name="JMSProxy" transports="jms">
<target>
<inSequence>
<property action="set" name="OUT_ONLY" value="true"/>
</inSequence>
<endpoint>
<address
uri="http://localhost:9000/soap/SimpleStockQuoteService">
<enableAddressing/>
</address>
</endpoint>
<outSequence>
<property action="set" name="Action"
value="urn:placeOrder"/>
<send/>
</outSequence>
</target>
<parameter
name="transport.jms.Destination">java:comp/env/jms/OutQueue</parameter>
<publishWSDL
uri="file:repository/conf/sample/resources/proxy/sample_proxy_1.wsdl"/>
</proxy>
</definitions>
-----Original Message-----
From: Asankha C. Perera [mailto:asankha@wso2.com]
Sent: Monday, February 11, 2008 1:57 PM
To: user@synapse.apache.org
Subject: Re: Switching transports - JMS to http using AQ
Greg
> Thanks for all your help so far Ashanka. Sorry for my confusion.
Np! .. thats what this user list is for :-)
> Is the scenario you describe below possible using just configuration
via
> the synapse.xml file, or is this something that I'm going to need to
> write custom services for?
>
This is possible via just configuring the synapse.xml.. its actually
trivial, instead of just one proxy service, you just define two proxy
services.. one to convert from http->jms and the other for jms->http..
If you still have any issues on this, do let us know and one of us will
help you more
asankha
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
Re: Switching transports - JMS to http using AQ
Posted by "Asankha C. Perera" <as...@wso2.com>.
Greg
> Thanks for all your help so far Ashanka. Sorry for my confusion.
Np! .. thats what this user list is for :-)
> Is the scenario you describe below possible using just configuration via
> the synapse.xml file, or is this something that I'm going to need to
> write custom services for?
>
This is possible via just configuring the synapse.xml.. its actually
trivial, instead of just one proxy service, you just define two proxy
services.. one to convert from http->jms and the other for jms->http..
If you still have any issues on this, do let us know and one of us will
help you more
asankha
RE: Switching transports - JMS to http using AQ
Posted by gr...@accenture.com.
Thanks for all your help so far Ashanka. Sorry for my confusion. Is
the scenario you describe below possible using just configuration via
the synapse.xml file, or is this something that I'm going to need to
write custom services for?
-----Original Message-----
From: Asankha C. Perera [mailto:asankha@wso2.com]
Sent: Monday, February 11, 2008 1:37 PM
To: user@synapse.apache.org
Subject: Re: Switching transports - JMS to http using AQ
Greg
> The MDB is not handling the CORRELATION_ID. I was under the
impression
> that they would be treated as two separate operations. For example:
>
> Operation One: HTTP request gets put on a queue by Synapse, and HTTP
202
> returned to the client
>
> Outside of Synapse: MDB puts message on OUT_QUEUE (this simulates our
> normal backend processing)
>
> Operation Two: Synapse listens to OUT_QUEUE and makes HTTP request to
> specified endpoint, returning 202 to Synapse.
>
Ok.. then your config is not correct for the scenario you describe.. If
these are two un-related messages, you could define two proxy services,
one that listens on HTTP and puts it on JMS and returns 202, and the
other service to listen on JMS on the reply Queue and post the message
to an http endpoint
asankha
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
Re: Switching transports - JMS to http using AQ
Posted by "Asankha C. Perera" <as...@wso2.com>.
Greg
> The MDB is not handling the CORRELATION_ID. I was under the impression
> that they would be treated as two separate operations. For example:
>
> Operation One: HTTP request gets put on a queue by Synapse, and HTTP 202
> returned to the client
>
> Outside of Synapse: MDB puts message on OUT_QUEUE (this simulates our
> normal backend processing)
>
> Operation Two: Synapse listens to OUT_QUEUE and makes HTTP request to
> specified endpoint, returning 202 to Synapse.
>
Ok.. then your config is not correct for the scenario you describe.. If
these are two un-related messages, you could define two proxy services,
one that listens on HTTP and puts it on JMS and returns 202, and the
other service to listen on JMS on the reply Queue and post the message
to an http endpoint
asankha
RE: Switching transports - JMS to http using AQ
Posted by gr...@accenture.com.
The MDB is not handling the CORRELATION_ID. I was under the impression
that they would be treated as two separate operations. For example:
Operation One: HTTP request gets put on a queue by Synapse, and HTTP 202
returned to the client
Outside of Synapse: MDB puts message on OUT_QUEUE (this simulates our
normal backend processing)
Operation Two: Synapse listens to OUT_QUEUE and makes HTTP request to
specified endpoint, returning 202 to Synapse.
-----Original Message-----
From: Asankha C. Perera [mailto:asankha@wso2.com]
Sent: Monday, February 11, 2008 1:25 PM
To: user@synapse.apache.org
Subject: Re: Switching transports - JMS to http using AQ
Greg
gregg.j.blais@accenture.com wrote:
> OK, that issue is fixed, but it's still not picking up the message
from
> the JMS queue. Just to let you know, here's my setup:
>
> I have two queues: MY_QUEUE and OUT_QUEUE. I enqueue a message on
> MY_QUEUE by making an HTTP which synapse proxies to the JMS queue.
> There's an MDB listening on MY_QUEUE, which picks up the messages and
> enqueues it on OUT_QUEUE. The message still doesn't get picked up off
> of OUT_QUEUE unless I restart Synapse.
>
>
Does your custom MDB correctly handle the CORRELATION_ID? i.e. Synapse
expects the response you place on the OUT_QUEUE to match the MESSAGE_ID
of the request it placed on MY_QUEUE
asankha
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
Re: Switching transports - JMS to http using AQ
Posted by "Asankha C. Perera" <as...@wso2.com>.
Greg
gregg.j.blais@accenture.com wrote:
> OK, that issue is fixed, but it's still not picking up the message from
> the JMS queue. Just to let you know, here's my setup:
>
> I have two queues: MY_QUEUE and OUT_QUEUE. I enqueue a message on
> MY_QUEUE by making an HTTP which synapse proxies to the JMS queue.
> There's an MDB listening on MY_QUEUE, which picks up the messages and
> enqueues it on OUT_QUEUE. The message still doesn't get picked up off
> of OUT_QUEUE unless I restart Synapse.
>
>
Does your custom MDB correctly handle the CORRELATION_ID? i.e. Synapse
expects the response you place on the OUT_QUEUE to match the MESSAGE_ID
of the request it placed on MY_QUEUE
asankha
RE: Switching transports - JMS to http using AQ
Posted by gr...@accenture.com.
OK, that issue is fixed, but it's still not picking up the message from
the JMS queue. Just to let you know, here's my setup:
I have two queues: MY_QUEUE and OUT_QUEUE. I enqueue a message on
MY_QUEUE by making an HTTP which synapse proxies to the JMS queue.
There's an MDB listening on MY_QUEUE, which picks up the messages and
enqueues it on OUT_QUEUE. The message still doesn't get picked up off
of OUT_QUEUE unless I restart Synapse.
Here's the log:
--> 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.
2008-02-11 13:10:18,441 [-] [WrapperSimpleAppMain] INFO ServerManager
Using the Axis2 Repository C:\SYNAPS~1.1\repository
2008-02-11 13:10:19,993 [-] [WrapperSimpleAppMain] INFO
SynapseInitializationModule Initializing Synapse at : Mon Feb 11
13:10:19 EST 2008
2008-02-11 13:10:19,993 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Loading mediator extensions...
2008-02-11 13:10:19,993 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Initializing the Synapse configuration
...
2008-02-11 13:10:20,003 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO XMLConfigurationBuilder Generating the Synapse configuration model
by parsing the XML configuration
2008-02-11 13:10:20,263 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseConfigurationBuilder Loaded Synapse configuration from :
C:\SYNAPS~1.1\bin\..\repository\conf\sample\synapse_sample_250.xml
2008-02-11 13:10:20,273 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Deploying the Synapse service..
2008-02-11 13:10:20,303 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Initializing Sandesha 2...
2008-02-11 13:10:20,303 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Synapse server name : ACN3T27851
2008-02-11 13:10:20,303 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Deploying Proxy services...
2008-02-11 13:10:20,303 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ProxyService Building Axis service for Proxy service :
StockQuoteProxy
2008-02-11 13:10:20,734 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ProxyService Adding service StockQuoteProxy to the Axis2
configuration
2008-02-11 13:10:20,734 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ProxyService Successfully created the Axis2 service for Proxy
service : StockQuoteProxy
2008-02-11 13:10:20,734 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Deployed Proxy service :
StockQuoteProxy
2008-02-11 13:10:20,734 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ProxyService Building Axis service for Proxy service : JMSProxy
2008-02-11 13:10:20,794 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ProxyService Adding service JMSProxy to the Axis2 configuration
2008-02-11 13:10:20,794 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ProxyService Successfully created the Axis2 service for Proxy
service : JMSProxy
2008-02-11 13:10:20,794 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Deployed Proxy service : JMSProxy
2008-02-11 13:10:20,794 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Synapse initialized successfully...!
2008-02-11 13:10:20,794 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
DEBUG HttpCoreNIOSSLSender Loading Key Store from URL :
file:/C:/synapse-1.1.1/lib/identity.jks
2008-02-11 13:10:20,824 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
DEBUG HttpCoreNIOSSLSender Loading Trust Key Store from URL :
file:/C:/synapse-1.1.1/lib/trust.jks
2008-02-11 13:10:20,884 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO HttpCoreNIOSender HTTPS Sender starting
2008-02-11 13:10:20,884 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO HttpCoreNIOSender HTTP Sender starting
2008-02-11 13:10:21,044 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
WARN ServerManager Port 8080 already in use. Trying alternate
2008-02-11 13:10:21,054 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
DEBUG HttpCoreNIOSSLListener Loading Key Store from URL :
file:/C:/synapse-1.1.1/lib/identity.jks
2008-02-11 13:10:21,054 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
DEBUG HttpCoreNIOSSLListener Loading Trust Key Store from URL :
file:/C:/synapse-1.1.1/lib/trust.jks
2008-02-11 13:10:21,115 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
DEBUG HttpCoreNIOListener Starting Listener...
2008-02-11 13:10:21,115 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO HttpCoreNIOListener HTTPS Listener starting on port : 8443
2008-02-11 13:10:21,115 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ServerManager Starting transport https on port 8443
2008-02-11 13:10:21,185 [172.17.5.187-ACN3T27851] [HttpCoreNIOSender]
DEBUG NativeWorkerPool Using native util.concurrent package..
2008-02-11 13:10:21,195 [172.17.5.187-ACN3T27851] [HttpCoreNIOSender]
DEBUG NativeWorkerPool Using native util.concurrent package..
2008-02-11 13:10:21,225 [172.17.5.187-ACN3T27851] [HttpCoreNIOListener]
DEBUG NativeWorkerPool Using native util.concurrent package..
2008-02-11 13:10:21,275 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
DEBUG HttpCoreNIOListener Starting Listener...
2008-02-11 13:10:21,275 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO HttpCoreNIOListener HTTP Listener starting on port : 8008
2008-02-11 13:10:21,275 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ServerManager Starting transport http on port 8008
2008-02-11 13:10:21,275 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
DEBUG NativeWorkerPool Using native util.concurrent package..
2008-02-11 13:10:21,305 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ServerManager Starting transport vfs
2008-02-11 13:10:21,305 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
DEBUG NativeWorkerPool Using native util.concurrent package..
2008-02-11 13:10:21,305 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ServerManager Starting transport mailto
2008-02-11 13:10:21,305 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
DEBUG NativeWorkerPool Using native util.concurrent package..
2008-02-11 13:10:21,325 [172.17.5.187-ACN3T27851] [HttpCoreNIOListener]
DEBUG NativeWorkerPool Using native util.concurrent package..
2008-02-11 13:10:21,355 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO JMSListener JMS Transport Receiver/Listener initialized...
2008-02-11 13:10:21,355 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
DEBUG JMSConnectionFactory Initializing the JMS connection factory :
default
2008-02-11 13:10:23,328 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO JMSConnectionFactory Connected to the JMS connection factory :
java:comp/env/jms/PlayerConnectionFactory
2008-02-11 13:10:25,931 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO JMSConnectionFactory Connection factory : default initialized...
2008-02-11 13:10:25,931 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
DEBUG JMSUtils JMS destination type not given. default queue
2008-02-11 13:10:25,931 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO JMSListener Starting to listen on destination :
java:comp/env/jms/OutQueue of type queue for service JMSProxy
2008-02-11 13:10:26,312 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO JMSConnectionFactory Mapped JNDI name : java:comp/env/jms/OutQueue
and JMS Destination name : OUT_QUEUE against service : JMSProxy
2008-02-11 13:10:26,763 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ServerManager Starting transport jms
2008-02-11 13:10:26,763 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ServerManager Ready for processing
2008-02-11 13:10:43,847 [172.17.5.187-ACN3T27851] [I/O dispatcher 7]
DEBUG ServerHandler HTTP connection [/127.0.0.1:1851]: Connected
2008-02-11 13:10:43,907 [172.17.5.187-ACN3T27851] [I/O dispatcher 7]
DEBUG ServerHandler HTTP connection [/127.0.0.1:1851]: POST
/soap/StockQuoteProxy HTTP/1.1
2008-02-11 13:10:43,907 [172.17.5.187-ACN3T27851] [I/O dispatcher 7]
INFO PipeImpl Using simulated buffered Pipes for event-driven to stream
IO bridging
2008-02-11 13:10:43,967 [172.17.5.187-ACN3T27851] [I/O dispatcher 7]
DEBUG ServerHandler HTTP connection [localhost/127.0.0.1:1851]: Input
ready
2008-02-11 13:10:43,967 [172.17.5.187-ACN3T27851] [I/O dispatcher 7]
DEBUG ServerHandler HTTP connection [localhost/127.0.0.1:1851]: Content
decoder [chunk-coded; completed: true]
2008-02-11 13:10:44,098 [172.17.5.187-ACN3T27851] [HttpServerWorker-1]
INFO TimeoutHandler This engine will expire all callbacks after : 86400
seconds, irrespective of the timeout action, after the specified or
optional timeout
2008-02-11 13:10:44,618 [172.17.5.187-ACN3T27851] [HttpServerWorker-1]
DEBUG JMSUtils Sending message to destination :
oracle.j2ee.ra.jms.generic.AdminObjectQueueImpl[MY_QUEUE]
2008-02-11 13:10:45,099 [172.17.5.187-ACN3T27851] [HttpServerWorker-1]
DEBUG JMSUtils Sent message to destination :
oracle.j2ee.ra.jms.generic.AdminObjectQueueImpl[MY_QUEUE]
Message ID : ID:EE60BD5207DD4418BE8AFB4F8885ABC2
Correlation ID :
ReplyTo ID : null
2008-02-11 13:10:49,405 [172.17.5.187-ACN3T27851] [I/O dispatcher 7]
DEBUG ServerHandler HTTP connection [localhost/127.0.0.1:1851]: An
existing connection was forcibly closed by the remote host (Probably the
keepalive connection was closed)
2008-02-11 13:10:49,405 [172.17.5.187-ACN3T27851] [I/O dispatcher 7]
DEBUG ServerHandler I/O error (Probably the keepalive connection was
closed):An existing connection was forcibly closed by the remote host
2008-02-11 13:10:49,405 [172.17.5.187-ACN3T27851] [I/O dispatcher 7]
DEBUG ServerHandler HTTP connection [closed]: Closed
-----Original Message-----
From: Asankha C. Perera [mailto:asankha@wso2.com]
Sent: Monday, February 11, 2008 1:07 PM
To: user@synapse.apache.org
Subject: Re: Switching transports - JMS to http using AQ
Greg
> When I change the name to JMSProxy, it tries to look up a queue table
> called JMSProxy. Is there a reason why it's not using the
> transport.jms.Destination parameter that is set?
>
Yep :-) .. it should be a "parameter" and not a property
ref: http://synapse.apache.org/Synapse_Configuration_Language.html#proxy
sample: http://synapse.apache.org/Synapse_Samples.html#Sample254
asankha
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
Re: Switching transports - JMS to http using AQ
Posted by "Asankha C. Perera" <as...@wso2.com>.
Greg
> When I change the name to JMSProxy, it tries to look up a queue table
> called JMSProxy. Is there a reason why it's not using the
> transport.jms.Destination parameter that is set?
>
Yep :-) .. it should be a "parameter" and not a property
ref: http://synapse.apache.org/Synapse_Configuration_Language.html#proxy
sample: http://synapse.apache.org/Synapse_Samples.html#Sample254
asankha
RE: Switching transports - JMS to http using AQ
Posted by gr...@accenture.com.
When I change the name to JMSProxy, it tries to look up a queue table
called JMSProxy. Is there a reason why it's not using the
transport.jms.Destination parameter that is set? The log file is below:
2008-02-11 12:47:54,979 [-] [WrapperSimpleAppMain] INFO ServerManager
Using the Axis2 Repository C:\SYNAPS~1.1\repository
2008-02-11 12:47:56,471 [-] [WrapperSimpleAppMain] INFO
SynapseInitializationModule Initializing Synapse at : Mon Feb 11
12:47:56 EST 2008
2008-02-11 12:47:56,471 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Loading mediator extensions...
2008-02-11 12:47:56,471 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Initializing the Synapse configuration
...
2008-02-11 12:47:56,481 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO XMLConfigurationBuilder Generating the Synapse configuration model
by parsing the XML configuration
2008-02-11 12:47:56,691 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseConfigurationBuilder Loaded Synapse configuration from :
C:\SYNAPS~1.1\bin\..\repository\conf\sample\synapse_sample_250.xml
2008-02-11 12:47:56,721 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Deploying the Synapse service..
2008-02-11 12:47:56,741 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Initializing Sandesha 2...
2008-02-11 12:47:56,741 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Synapse server name : ACN3T27851
2008-02-11 12:47:56,741 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Deploying Proxy services...
2008-02-11 12:47:56,741 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ProxyService Building Axis service for Proxy service :
StockQuoteProxy
2008-02-11 12:47:57,142 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ProxyService Adding service StockQuoteProxy to the Axis2
configuration
2008-02-11 12:47:57,142 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ProxyService Successfully created the Axis2 service for Proxy
service : StockQuoteProxy
2008-02-11 12:47:57,142 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Deployed Proxy service :
StockQuoteProxy
2008-02-11 12:47:57,142 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ProxyService Building Axis service for Proxy service : JMSProxy
2008-02-11 12:47:57,202 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ProxyService Adding service JMSProxy to the Axis2 configuration
2008-02-11 12:47:57,202 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ProxyService Successfully created the Axis2 service for Proxy
service : JMSProxy
2008-02-11 12:47:57,202 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Deployed Proxy service : JMSProxy
2008-02-11 12:47:57,202 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Synapse initialized successfully...!
2008-02-11 12:47:57,202 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
DEBUG HttpCoreNIOSSLSender Loading Key Store from URL :
file:/C:/synapse-1.1.1/lib/identity.jks
2008-02-11 12:47:57,232 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
DEBUG HttpCoreNIOSSLSender Loading Trust Key Store from URL :
file:/C:/synapse-1.1.1/lib/trust.jks
2008-02-11 12:47:57,282 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO HttpCoreNIOSender HTTPS Sender starting
2008-02-11 12:47:57,282 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO HttpCoreNIOSender HTTP Sender starting
2008-02-11 12:47:57,432 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
WARN ServerManager Port 8080 already in use. Trying alternate
2008-02-11 12:47:57,442 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
DEBUG HttpCoreNIOSSLListener Loading Key Store from URL :
file:/C:/synapse-1.1.1/lib/identity.jks
2008-02-11 12:47:57,442 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
DEBUG HttpCoreNIOSSLListener Loading Trust Key Store from URL :
file:/C:/synapse-1.1.1/lib/trust.jks
2008-02-11 12:47:57,492 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
DEBUG HttpCoreNIOListener Starting Listener...
2008-02-11 12:47:57,502 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO HttpCoreNIOListener HTTPS Listener starting on port : 8443
2008-02-11 12:47:57,502 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ServerManager Starting transport https on port 8443
2008-02-11 12:47:57,573 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
DEBUG HttpCoreNIOListener Starting Listener...
2008-02-11 12:47:57,573 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO HttpCoreNIOListener HTTP Listener starting on port : 8008
2008-02-11 12:47:57,573 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ServerManager Starting transport http on port 8008
2008-02-11 12:47:57,583 [172.17.5.187-ACN3T27851] [HttpCoreNIOSender]
DEBUG NativeWorkerPool Using native util.concurrent package..
2008-02-11 12:47:57,613 [172.17.5.187-ACN3T27851] [HttpCoreNIOSender]
DEBUG NativeWorkerPool Using native util.concurrent package..
2008-02-11 12:47:57,623 [172.17.5.187-ACN3T27851] [HttpCoreNIOListener]
DEBUG NativeWorkerPool Using native util.concurrent package..
2008-02-11 12:47:57,623 [172.17.5.187-ACN3T27851] [HttpCoreNIOListener]
DEBUG NativeWorkerPool Using native util.concurrent package..
2008-02-11 12:47:57,643 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
DEBUG NativeWorkerPool Using native util.concurrent package..
2008-02-11 12:47:57,703 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ServerManager Starting transport vfs
2008-02-11 12:47:57,703 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
DEBUG NativeWorkerPool Using native util.concurrent package..
2008-02-11 12:47:57,703 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ServerManager Starting transport mailto
2008-02-11 12:47:57,703 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
DEBUG NativeWorkerPool Using native util.concurrent package..
2008-02-11 12:47:57,713 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO JMSListener JMS Transport Receiver/Listener initialized...
2008-02-11 12:47:57,713 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
DEBUG JMSConnectionFactory Initializing the JMS connection factory :
default
2008-02-11 12:47:59,606 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO JMSConnectionFactory Connected to the JMS connection factory :
java:comp/env/jms/PlayerConnectionFactory
2008-02-11 12:48:02,099 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO JMSConnectionFactory Connection factory : default initialized...
2008-02-11 12:48:02,109 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
DEBUG JMSUtils JMS destination type not given. default queue
2008-02-11 12:48:02,109 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO JMSListener Starting to listen on destination : JMSProxy of type
queue for service JMSProxy
2008-02-11 12:48:02,109 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
WARN JMSConnectionFactory JMS Destination with JNDI name : JMSProxy does
not exist
2008-02-11 12:48:02,109 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO JMSConnectionFactory Creating a JMS Queue with the JNDI name :
JMSProxy using the connection factory definition named : default
2008-02-11 12:48:02,860 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
ERROR JMSConnectionFactory Unable to create Destination with JNDI name :
JMSProxy
oracle.jms.AQjmsException: JMS-190: Queue JMSProxy not found
at oracle.jms.AQjmsError.throwEx(AQjmsError.java:346)
at oracle.jms.AQjmsSession.createQueue(AQjmsSession.java:1296)
at
oracle.j2ee.ra.jms.generic.SessionWrapper.createQueue(SessionWrapper.jav
a:331)
at
org.apache.synapse.transport.jms.JMSUtils.createJMSQueue(JMSUtils.java:8
0)
at
org.apache.synapse.transport.jms.JMSUtils.createDestination(JMSUtils.jav
a:746)
at
org.apache.synapse.transport.jms.JMSConnectionFactory.addDestination(JMS
ConnectionFactory.java:143)
at
org.apache.synapse.transport.jms.JMSListener.startListeningForService(JM
SListener.java:167)
at
org.apache.synapse.transport.base.AbstractTransportListener.start(Abstra
ctTransportListener.java:140)
at
org.apache.synapse.transport.jms.JMSListener.start(JMSListener.java:107)
at
org.apache.axis2.engine.ListenerManager.addListener(ListenerManager.java
:205)
at
org.apache.synapse.ServerManager.start(ServerManager.java:103)
at org.apache.synapse.SynapseServer.main(SynapseServer.java:49)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:24
0)
at java.lang.Thread.run(Thread.java:595)
[Linked-exception]
oracle.jms.AQjmsException: JMS-190: Queue MYCHANNELDEMOUSER.JMSProxy not
found
at oracle.jms.AQjmsSession.getQueue(AQjmsSession.java:4652)
at oracle.jms.AQjmsSession.createQueue(AQjmsSession.java:1289)
at
oracle.j2ee.ra.jms.generic.SessionWrapper.createQueue(SessionWrapper.jav
a:331)
at
org.apache.synapse.transport.jms.JMSUtils.createJMSQueue(JMSUtils.java:8
0)
at
org.apache.synapse.transport.jms.JMSUtils.createDestination(JMSUtils.jav
a:746)
at
org.apache.synapse.transport.jms.JMSConnectionFactory.addDestination(JMS
ConnectionFactory.java:143)
at
org.apache.synapse.transport.jms.JMSListener.startListeningForService(JM
SListener.java:167)
at
org.apache.synapse.transport.base.AbstractTransportListener.start(Abstra
ctTransportListener.java:140)
at
org.apache.synapse.transport.jms.JMSListener.start(JMSListener.java:107)
at
org.apache.axis2.engine.ListenerManager.addListener(ListenerManager.java
:205)
at
org.apache.synapse.ServerManager.start(ServerManager.java:103)
at org.apache.synapse.SynapseServer.main(SynapseServer.java:49)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:24
0)
at java.lang.Thread.run(Thread.java:595)
2008-02-11 12:48:02,930 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
WARN JMSConnectionFactory Cannot find destination : JMSProxy. Creating a
Queue
2008-02-11 12:48:02,940 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ServerManager Starting transport jms
2008-02-11 12:48:02,940 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ServerManager Ready for processing
-----Original Message-----
From: Asankha C. Perera [mailto:asankha@wso2.com]
Sent: Monday, February 11, 2008 12:22 PM
To: user@synapse.apache.org
Subject: Re: Switching transports - JMS to http using AQ
I suspect the java:comp/.. stuff creates issues .. Do not name your
proxy service as "java:comp/env/jms/OutQueue" etc.. but something like
"JMSProxy".. I will have to ask you to paste the full sample JMS
standalone client code that you tried (which shows the connection
factory name etc)..
also in your log4j.properties file, set
"log4j.category.org.apache.synapse.transport=INFO" to
"log4j.category.org.apache.synapse.transport=DEBUG" and see if there is
any additional information..
asankha
gregg.j.blais@accenture.com wrote:
> Here's the contents:
>
> --> 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.
>
> 2008-02-11 11:31:23,937 [-] [WrapperSimpleAppMain] INFO ServerManager
> Using the Axis2 Repository C:\SYNAPS~1.1\repository
> 2008-02-11 11:31:25,359 [-] [WrapperSimpleAppMain] INFO
> SynapseInitializationModule Initializing Synapse at : Mon Feb 11
> 11:31:25 EST 2008
> 2008-02-11 11:31:25,359 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO SynapseInitializationModule Loading mediator extensions...
> 2008-02-11 11:31:25,359 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO SynapseInitializationModule Initializing the Synapse
configuration
> ...
> 2008-02-11 11:31:25,379 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO XMLConfigurationBuilder Generating the Synapse configuration
model
> by parsing the XML configuration
> 2008-02-11 11:31:25,580 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO SynapseConfigurationBuilder Loaded Synapse configuration from :
> C:\SYNAPS~1.1\bin\..\repository\conf\sample\synapse_sample_250.xml
> 2008-02-11 11:31:25,590 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO SynapseInitializationModule Deploying the Synapse service..
> 2008-02-11 11:31:25,610 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO SynapseInitializationModule Initializing Sandesha 2...
> 2008-02-11 11:31:25,620 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO SynapseInitializationModule Synapse server name : ACN3T27851
> 2008-02-11 11:31:25,620 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO SynapseInitializationModule Deploying Proxy services...
> 2008-02-11 11:31:25,620 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO ProxyService Building Axis service for Proxy service :
> java:comp/env/jms/OutQueue
> 2008-02-11 11:31:26,000 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO ProxyService Adding service java:comp/env/jms/OutQueue to the
Axis2
> configuration
> 2008-02-11 11:31:26,000 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO ProxyService Successfully created the Axis2 service for Proxy
> service : java:comp/env/jms/OutQueue
> 2008-02-11 11:31:26,000 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO SynapseInitializationModule Deployed Proxy service :
> java:comp/env/jms/OutQueue
> 2008-02-11 11:31:26,000 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO ProxyService Building Axis service for Proxy service :
> StockQuoteProxy
> 2008-02-11 11:31:26,070 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO ProxyService Adding service StockQuoteProxy to the Axis2
> configuration
> 2008-02-11 11:31:26,070 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO ProxyService Successfully created the Axis2 service for Proxy
> service : StockQuoteProxy
> 2008-02-11 11:31:26,070 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO SynapseInitializationModule Deployed Proxy service :
> StockQuoteProxy
> 2008-02-11 11:31:26,070 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO SynapseInitializationModule Synapse initialized successfully...!
> 2008-02-11 11:31:26,150 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO HttpCoreNIOSender HTTPS Sender starting
> 2008-02-11 11:31:26,150 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO HttpCoreNIOSender HTTP Sender starting
> 2008-02-11 11:31:26,301 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> WARN ServerManager Port 8080 already in use. Trying alternate
> 2008-02-11 11:31:26,361 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO HttpCoreNIOListener HTTPS Listener starting on port : 8443
> 2008-02-11 11:31:26,361 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO ServerManager Starting transport https on port 8443
> 2008-02-11 11:31:26,531 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO HttpCoreNIOListener HTTP Listener starting on port : 8008
> 2008-02-11 11:31:26,531 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO ServerManager Starting transport http on port 8008
> 2008-02-11 11:31:26,571 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO ServerManager Starting transport vfs
> 2008-02-11 11:31:26,571 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO ServerManager Starting transport mailto
> 2008-02-11 11:31:26,591 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO JMSListener JMS Transport Receiver/Listener initialized...
> 2008-02-11 11:31:28,424 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO JMSConnectionFactory Connected to the JMS connection factory :
> java:comp/env/jms/PlayerConnectionFactory
> 2008-02-11 11:31:30,647 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO JMSConnectionFactory Connection factory : default initialized...
> 2008-02-11 11:31:30,647 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO JMSListener Starting to listen on destination :
> java:comp/env/jms/OutQueue of type queue for service
> java:comp/env/jms/OutQueue
> 2008-02-11 11:31:30,777 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO JMSConnectionFactory Mapped JNDI name :
java:comp/env/jms/OutQueue
> and JMS Destination name : OUT_QUEUE against service :
> java:comp/env/jms/OutQueue
> 2008-02-11 11:31:31,068 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO ServerManager Starting transport jms
> 2008-02-11 11:31:31,068 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO ServerManager Ready for processing
> 2008-02-11 11:32:19,107 [172.17.5.187-ACN3T27851] [I/O dispatcher 7]
> INFO PipeImpl Using simulated buffered Pipes for event-driven to
stream
> IO bridging
> 2008-02-11 11:32:19,347 [172.17.5.187-ACN3T27851] [HttpServerWorker-1]
> INFO TimeoutHandler This engine will expire all callbacks after :
86400
> seconds, irrespective of the timeout action, after the specified or
> optional timeout
>
> -----Original Message-----
> From: Asankha C. Perera [mailto:asankha@wso2.com]
> Sent: Monday, February 11, 2008 11:49 AM
> To: user@synapse.apache.org
> Subject: Re: Switching transports - JMS to http using AQ
>
> Greg
>
>> I have attached the log as well.
>>
>>
> I don't see the log :(
>
> asankha
>
>> -----Original Message-----
>> From: Asankha C. Perera [mailto:asankha@wso2.com]
>> Sent: Saturday, February 09, 2008 5:58 AM
>> To: Blais, Gregg J.
>> Subject: Re: Switching transports - JMS to http using AQ
>>
>> Gregg
>>
>>
>>> I tried using a standard JMS client with AQ and it drops messages
>>> successfully and pulls messages off the queue fine using standard
JMS
>>> code. Do you have any other suggestions on how to debug the issue
>>>
>>>
>> with
>>
>>
>>> Synapse?
>>>
>>>
>>>
>> Ok.. well this is good news and I think we should be able to get
>>
> Synapse
>
>> working with AQ then..
>>
>> Can you post the JNDI properties you used to access AQ with the
sample
>>
>
>
>> client on the dev or user list and any logs from your side? You can
>>
> hide
>
>> any server names etc from the logs if its private
>>
>> Another option would be for one of the developers to test against AQ,
>> but lets put it off for now as it seems like you could get this to
>>
> work
>
>> with a bit of work.
>>
>> asankha
>>
>>
>>
>> This message is for the designated recipient only and may contain
>>
> privileged, proprietary, or otherwise private information. If you
have
> received it in error, please notify the sender immediately and delete
> the original. Any other use of the email by you is prohibited.
>
>>
>>
>
>
> This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the sender immediately and delete
the original. Any other use of the email by you is prohibited.
>
>
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
RE: Switching transports - JMS to http using AQ
Posted by gr...@accenture.com.
The code is below. I'll change the logs to debug and see if it reveals
anything.
import javax.jms.*;
import javax.naming.*;
public class SimpleQueueReceiver
{
/**
* Main method.
*
* @param args
* the queue used by the example
*/
public static void main(String[] args)
{
String queueName = null;
Context jndiContext = null;
QueueConnectionFactory queueConnectionFactory = null;
QueueConnection queueConnection = null;
QueueSession queueSession = null;
Queue queue = null;
QueueReceiver queueReceiver = null;
TextMessage message = null;
/*
* Read queue name from command line and display it.
*/
if (args.length != 1)
{
System.out.println("Usage: java "
+ "SimpleQueueReceiver
<queue-name>");
System.exit(1);
}
queueName = new String(args[0]);
System.out.println("Queue name is " + queueName);
try
{
jndiContext = new InitialContext();
}
catch (NamingException e)
{
System.out.println("Could not create JNDI API "
+ "context: "
+ e.toString());
System.exit(1);
}
try
{
queueConnectionFactory =
(QueueConnectionFactory) jndiContext
.lookup("java:comp/env/jms/PlayerConnectionFactory");
queue = (Queue) jndiContext.lookup(queueName);
}
catch (NamingException e)
{
System.out.println("JNDI API lookup failed: " +
e.toString());
System.exit(1);
}
try
{
queueConnection =
queueConnectionFactory.createQueueConnection();
queueSession =
queueConnection.createQueueSession(false,
Session.AUTO_ACKNOWLEDGE);
queueReceiver =
queueSession.createReceiver(queue);
queueConnection.start();
while (true)
{
Message m = queueReceiver.receive(1);
if (m != null)
{
if (m instanceof TextMessage)
{
message = (TextMessage)
m;
System.out.println("Reading message: "
+
message.getText());
}
else
{
break;
}
}
}
}
catch (JMSException e)
{
System.out.println("Exception occurred: " +
e.toString());
}
finally
{
if (queueConnection != null)
{
try
{
queueConnection.close();
}
catch (JMSException e)
{
}
}
}
}
}
-----Original Message-----
From: Asankha C. Perera [mailto:asankha@wso2.com]
Sent: Monday, February 11, 2008 12:22 PM
To: user@synapse.apache.org
Subject: Re: Switching transports - JMS to http using AQ
I suspect the java:comp/.. stuff creates issues .. Do not name your
proxy service as "java:comp/env/jms/OutQueue" etc.. but something like
"JMSProxy".. I will have to ask you to paste the full sample JMS
standalone client code that you tried (which shows the connection
factory name etc)..
also in your log4j.properties file, set
"log4j.category.org.apache.synapse.transport=INFO" to
"log4j.category.org.apache.synapse.transport=DEBUG" and see if there is
any additional information..
asankha
gregg.j.blais@accenture.com wrote:
> Here's the contents:
>
> --> 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.
>
> 2008-02-11 11:31:23,937 [-] [WrapperSimpleAppMain] INFO ServerManager
> Using the Axis2 Repository C:\SYNAPS~1.1\repository
> 2008-02-11 11:31:25,359 [-] [WrapperSimpleAppMain] INFO
> SynapseInitializationModule Initializing Synapse at : Mon Feb 11
> 11:31:25 EST 2008
> 2008-02-11 11:31:25,359 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO SynapseInitializationModule Loading mediator extensions...
> 2008-02-11 11:31:25,359 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO SynapseInitializationModule Initializing the Synapse
configuration
> ...
> 2008-02-11 11:31:25,379 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO XMLConfigurationBuilder Generating the Synapse configuration
model
> by parsing the XML configuration
> 2008-02-11 11:31:25,580 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO SynapseConfigurationBuilder Loaded Synapse configuration from :
> C:\SYNAPS~1.1\bin\..\repository\conf\sample\synapse_sample_250.xml
> 2008-02-11 11:31:25,590 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO SynapseInitializationModule Deploying the Synapse service..
> 2008-02-11 11:31:25,610 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO SynapseInitializationModule Initializing Sandesha 2...
> 2008-02-11 11:31:25,620 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO SynapseInitializationModule Synapse server name : ACN3T27851
> 2008-02-11 11:31:25,620 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO SynapseInitializationModule Deploying Proxy services...
> 2008-02-11 11:31:25,620 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO ProxyService Building Axis service for Proxy service :
> java:comp/env/jms/OutQueue
> 2008-02-11 11:31:26,000 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO ProxyService Adding service java:comp/env/jms/OutQueue to the
Axis2
> configuration
> 2008-02-11 11:31:26,000 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO ProxyService Successfully created the Axis2 service for Proxy
> service : java:comp/env/jms/OutQueue
> 2008-02-11 11:31:26,000 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO SynapseInitializationModule Deployed Proxy service :
> java:comp/env/jms/OutQueue
> 2008-02-11 11:31:26,000 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO ProxyService Building Axis service for Proxy service :
> StockQuoteProxy
> 2008-02-11 11:31:26,070 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO ProxyService Adding service StockQuoteProxy to the Axis2
> configuration
> 2008-02-11 11:31:26,070 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO ProxyService Successfully created the Axis2 service for Proxy
> service : StockQuoteProxy
> 2008-02-11 11:31:26,070 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO SynapseInitializationModule Deployed Proxy service :
> StockQuoteProxy
> 2008-02-11 11:31:26,070 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO SynapseInitializationModule Synapse initialized successfully...!
> 2008-02-11 11:31:26,150 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO HttpCoreNIOSender HTTPS Sender starting
> 2008-02-11 11:31:26,150 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO HttpCoreNIOSender HTTP Sender starting
> 2008-02-11 11:31:26,301 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> WARN ServerManager Port 8080 already in use. Trying alternate
> 2008-02-11 11:31:26,361 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO HttpCoreNIOListener HTTPS Listener starting on port : 8443
> 2008-02-11 11:31:26,361 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO ServerManager Starting transport https on port 8443
> 2008-02-11 11:31:26,531 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO HttpCoreNIOListener HTTP Listener starting on port : 8008
> 2008-02-11 11:31:26,531 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO ServerManager Starting transport http on port 8008
> 2008-02-11 11:31:26,571 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO ServerManager Starting transport vfs
> 2008-02-11 11:31:26,571 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO ServerManager Starting transport mailto
> 2008-02-11 11:31:26,591 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO JMSListener JMS Transport Receiver/Listener initialized...
> 2008-02-11 11:31:28,424 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO JMSConnectionFactory Connected to the JMS connection factory :
> java:comp/env/jms/PlayerConnectionFactory
> 2008-02-11 11:31:30,647 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO JMSConnectionFactory Connection factory : default initialized...
> 2008-02-11 11:31:30,647 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO JMSListener Starting to listen on destination :
> java:comp/env/jms/OutQueue of type queue for service
> java:comp/env/jms/OutQueue
> 2008-02-11 11:31:30,777 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO JMSConnectionFactory Mapped JNDI name :
java:comp/env/jms/OutQueue
> and JMS Destination name : OUT_QUEUE against service :
> java:comp/env/jms/OutQueue
> 2008-02-11 11:31:31,068 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO ServerManager Starting transport jms
> 2008-02-11 11:31:31,068 [172.17.5.187-ACN3T27851]
[WrapperSimpleAppMain]
> INFO ServerManager Ready for processing
> 2008-02-11 11:32:19,107 [172.17.5.187-ACN3T27851] [I/O dispatcher 7]
> INFO PipeImpl Using simulated buffered Pipes for event-driven to
stream
> IO bridging
> 2008-02-11 11:32:19,347 [172.17.5.187-ACN3T27851] [HttpServerWorker-1]
> INFO TimeoutHandler This engine will expire all callbacks after :
86400
> seconds, irrespective of the timeout action, after the specified or
> optional timeout
>
> -----Original Message-----
> From: Asankha C. Perera [mailto:asankha@wso2.com]
> Sent: Monday, February 11, 2008 11:49 AM
> To: user@synapse.apache.org
> Subject: Re: Switching transports - JMS to http using AQ
>
> Greg
>
>> I have attached the log as well.
>>
>>
> I don't see the log :(
>
> asankha
>
>> -----Original Message-----
>> From: Asankha C. Perera [mailto:asankha@wso2.com]
>> Sent: Saturday, February 09, 2008 5:58 AM
>> To: Blais, Gregg J.
>> Subject: Re: Switching transports - JMS to http using AQ
>>
>> Gregg
>>
>>
>>> I tried using a standard JMS client with AQ and it drops messages
>>> successfully and pulls messages off the queue fine using standard
JMS
>>> code. Do you have any other suggestions on how to debug the issue
>>>
>>>
>> with
>>
>>
>>> Synapse?
>>>
>>>
>>>
>> Ok.. well this is good news and I think we should be able to get
>>
> Synapse
>
>> working with AQ then..
>>
>> Can you post the JNDI properties you used to access AQ with the
sample
>>
>
>
>> client on the dev or user list and any logs from your side? You can
>>
> hide
>
>> any server names etc from the logs if its private
>>
>> Another option would be for one of the developers to test against AQ,
>> but lets put it off for now as it seems like you could get this to
>>
> work
>
>> with a bit of work.
>>
>> asankha
>>
>>
>>
>> This message is for the designated recipient only and may contain
>>
> privileged, proprietary, or otherwise private information. If you
have
> received it in error, please notify the sender immediately and delete
> the original. Any other use of the email by you is prohibited.
>
>>
>>
>
>
> This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the sender immediately and delete
the original. Any other use of the email by you is prohibited.
>
>
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
Re: Switching transports - JMS to http using AQ
Posted by "Asankha C. Perera" <as...@wso2.com>.
I suspect the java:comp/.. stuff creates issues .. Do not name your
proxy service as "java:comp/env/jms/OutQueue" etc.. but something like
"JMSProxy".. I will have to ask you to paste the full sample JMS
standalone client code that you tried (which shows the connection
factory name etc)..
also in your log4j.properties file, set
"log4j.category.org.apache.synapse.transport=INFO" to
"log4j.category.org.apache.synapse.transport=DEBUG" and see if there is
any additional information..
asankha
gregg.j.blais@accenture.com wrote:
> Here's the contents:
>
> --> 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.
>
> 2008-02-11 11:31:23,937 [-] [WrapperSimpleAppMain] INFO ServerManager
> Using the Axis2 Repository C:\SYNAPS~1.1\repository
> 2008-02-11 11:31:25,359 [-] [WrapperSimpleAppMain] INFO
> SynapseInitializationModule Initializing Synapse at : Mon Feb 11
> 11:31:25 EST 2008
> 2008-02-11 11:31:25,359 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO SynapseInitializationModule Loading mediator extensions...
> 2008-02-11 11:31:25,359 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO SynapseInitializationModule Initializing the Synapse configuration
> ...
> 2008-02-11 11:31:25,379 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO XMLConfigurationBuilder Generating the Synapse configuration model
> by parsing the XML configuration
> 2008-02-11 11:31:25,580 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO SynapseConfigurationBuilder Loaded Synapse configuration from :
> C:\SYNAPS~1.1\bin\..\repository\conf\sample\synapse_sample_250.xml
> 2008-02-11 11:31:25,590 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO SynapseInitializationModule Deploying the Synapse service..
> 2008-02-11 11:31:25,610 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO SynapseInitializationModule Initializing Sandesha 2...
> 2008-02-11 11:31:25,620 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO SynapseInitializationModule Synapse server name : ACN3T27851
> 2008-02-11 11:31:25,620 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO SynapseInitializationModule Deploying Proxy services...
> 2008-02-11 11:31:25,620 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO ProxyService Building Axis service for Proxy service :
> java:comp/env/jms/OutQueue
> 2008-02-11 11:31:26,000 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO ProxyService Adding service java:comp/env/jms/OutQueue to the Axis2
> configuration
> 2008-02-11 11:31:26,000 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO ProxyService Successfully created the Axis2 service for Proxy
> service : java:comp/env/jms/OutQueue
> 2008-02-11 11:31:26,000 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO SynapseInitializationModule Deployed Proxy service :
> java:comp/env/jms/OutQueue
> 2008-02-11 11:31:26,000 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO ProxyService Building Axis service for Proxy service :
> StockQuoteProxy
> 2008-02-11 11:31:26,070 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO ProxyService Adding service StockQuoteProxy to the Axis2
> configuration
> 2008-02-11 11:31:26,070 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO ProxyService Successfully created the Axis2 service for Proxy
> service : StockQuoteProxy
> 2008-02-11 11:31:26,070 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO SynapseInitializationModule Deployed Proxy service :
> StockQuoteProxy
> 2008-02-11 11:31:26,070 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO SynapseInitializationModule Synapse initialized successfully...!
> 2008-02-11 11:31:26,150 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO HttpCoreNIOSender HTTPS Sender starting
> 2008-02-11 11:31:26,150 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO HttpCoreNIOSender HTTP Sender starting
> 2008-02-11 11:31:26,301 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> WARN ServerManager Port 8080 already in use. Trying alternate
> 2008-02-11 11:31:26,361 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO HttpCoreNIOListener HTTPS Listener starting on port : 8443
> 2008-02-11 11:31:26,361 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO ServerManager Starting transport https on port 8443
> 2008-02-11 11:31:26,531 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO HttpCoreNIOListener HTTP Listener starting on port : 8008
> 2008-02-11 11:31:26,531 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO ServerManager Starting transport http on port 8008
> 2008-02-11 11:31:26,571 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO ServerManager Starting transport vfs
> 2008-02-11 11:31:26,571 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO ServerManager Starting transport mailto
> 2008-02-11 11:31:26,591 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO JMSListener JMS Transport Receiver/Listener initialized...
> 2008-02-11 11:31:28,424 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO JMSConnectionFactory Connected to the JMS connection factory :
> java:comp/env/jms/PlayerConnectionFactory
> 2008-02-11 11:31:30,647 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO JMSConnectionFactory Connection factory : default initialized...
> 2008-02-11 11:31:30,647 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO JMSListener Starting to listen on destination :
> java:comp/env/jms/OutQueue of type queue for service
> java:comp/env/jms/OutQueue
> 2008-02-11 11:31:30,777 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO JMSConnectionFactory Mapped JNDI name : java:comp/env/jms/OutQueue
> and JMS Destination name : OUT_QUEUE against service :
> java:comp/env/jms/OutQueue
> 2008-02-11 11:31:31,068 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO ServerManager Starting transport jms
> 2008-02-11 11:31:31,068 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
> INFO ServerManager Ready for processing
> 2008-02-11 11:32:19,107 [172.17.5.187-ACN3T27851] [I/O dispatcher 7]
> INFO PipeImpl Using simulated buffered Pipes for event-driven to stream
> IO bridging
> 2008-02-11 11:32:19,347 [172.17.5.187-ACN3T27851] [HttpServerWorker-1]
> INFO TimeoutHandler This engine will expire all callbacks after : 86400
> seconds, irrespective of the timeout action, after the specified or
> optional timeout
>
> -----Original Message-----
> From: Asankha C. Perera [mailto:asankha@wso2.com]
> Sent: Monday, February 11, 2008 11:49 AM
> To: user@synapse.apache.org
> Subject: Re: Switching transports - JMS to http using AQ
>
> Greg
>
>> I have attached the log as well.
>>
>>
> I don't see the log :(
>
> asankha
>
>> -----Original Message-----
>> From: Asankha C. Perera [mailto:asankha@wso2.com]
>> Sent: Saturday, February 09, 2008 5:58 AM
>> To: Blais, Gregg J.
>> Subject: Re: Switching transports - JMS to http using AQ
>>
>> Gregg
>>
>>
>>> I tried using a standard JMS client with AQ and it drops messages
>>> successfully and pulls messages off the queue fine using standard JMS
>>> code. Do you have any other suggestions on how to debug the issue
>>>
>>>
>> with
>>
>>
>>> Synapse?
>>>
>>>
>>>
>> Ok.. well this is good news and I think we should be able to get
>>
> Synapse
>
>> working with AQ then..
>>
>> Can you post the JNDI properties you used to access AQ with the sample
>>
>
>
>> client on the dev or user list and any logs from your side? You can
>>
> hide
>
>> any server names etc from the logs if its private
>>
>> Another option would be for one of the developers to test against AQ,
>> but lets put it off for now as it seems like you could get this to
>>
> work
>
>> with a bit of work.
>>
>> asankha
>>
>>
>>
>> This message is for the designated recipient only and may contain
>>
> privileged, proprietary, or otherwise private information. If you have
> received it in error, please notify the sender immediately and delete
> the original. Any other use of the email by you is prohibited.
>
>>
>>
>
>
> This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
>
>
RE: Switching transports - JMS to http using AQ
Posted by gr...@accenture.com.
Here's the contents:
--> 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.
2008-02-11 11:31:23,937 [-] [WrapperSimpleAppMain] INFO ServerManager
Using the Axis2 Repository C:\SYNAPS~1.1\repository
2008-02-11 11:31:25,359 [-] [WrapperSimpleAppMain] INFO
SynapseInitializationModule Initializing Synapse at : Mon Feb 11
11:31:25 EST 2008
2008-02-11 11:31:25,359 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Loading mediator extensions...
2008-02-11 11:31:25,359 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Initializing the Synapse configuration
...
2008-02-11 11:31:25,379 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO XMLConfigurationBuilder Generating the Synapse configuration model
by parsing the XML configuration
2008-02-11 11:31:25,580 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseConfigurationBuilder Loaded Synapse configuration from :
C:\SYNAPS~1.1\bin\..\repository\conf\sample\synapse_sample_250.xml
2008-02-11 11:31:25,590 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Deploying the Synapse service..
2008-02-11 11:31:25,610 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Initializing Sandesha 2...
2008-02-11 11:31:25,620 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Synapse server name : ACN3T27851
2008-02-11 11:31:25,620 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Deploying Proxy services...
2008-02-11 11:31:25,620 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ProxyService Building Axis service for Proxy service :
java:comp/env/jms/OutQueue
2008-02-11 11:31:26,000 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ProxyService Adding service java:comp/env/jms/OutQueue to the Axis2
configuration
2008-02-11 11:31:26,000 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ProxyService Successfully created the Axis2 service for Proxy
service : java:comp/env/jms/OutQueue
2008-02-11 11:31:26,000 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Deployed Proxy service :
java:comp/env/jms/OutQueue
2008-02-11 11:31:26,000 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ProxyService Building Axis service for Proxy service :
StockQuoteProxy
2008-02-11 11:31:26,070 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ProxyService Adding service StockQuoteProxy to the Axis2
configuration
2008-02-11 11:31:26,070 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ProxyService Successfully created the Axis2 service for Proxy
service : StockQuoteProxy
2008-02-11 11:31:26,070 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Deployed Proxy service :
StockQuoteProxy
2008-02-11 11:31:26,070 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO SynapseInitializationModule Synapse initialized successfully...!
2008-02-11 11:31:26,150 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO HttpCoreNIOSender HTTPS Sender starting
2008-02-11 11:31:26,150 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO HttpCoreNIOSender HTTP Sender starting
2008-02-11 11:31:26,301 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
WARN ServerManager Port 8080 already in use. Trying alternate
2008-02-11 11:31:26,361 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO HttpCoreNIOListener HTTPS Listener starting on port : 8443
2008-02-11 11:31:26,361 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ServerManager Starting transport https on port 8443
2008-02-11 11:31:26,531 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO HttpCoreNIOListener HTTP Listener starting on port : 8008
2008-02-11 11:31:26,531 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ServerManager Starting transport http on port 8008
2008-02-11 11:31:26,571 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ServerManager Starting transport vfs
2008-02-11 11:31:26,571 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ServerManager Starting transport mailto
2008-02-11 11:31:26,591 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO JMSListener JMS Transport Receiver/Listener initialized...
2008-02-11 11:31:28,424 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO JMSConnectionFactory Connected to the JMS connection factory :
java:comp/env/jms/PlayerConnectionFactory
2008-02-11 11:31:30,647 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO JMSConnectionFactory Connection factory : default initialized...
2008-02-11 11:31:30,647 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO JMSListener Starting to listen on destination :
java:comp/env/jms/OutQueue of type queue for service
java:comp/env/jms/OutQueue
2008-02-11 11:31:30,777 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO JMSConnectionFactory Mapped JNDI name : java:comp/env/jms/OutQueue
and JMS Destination name : OUT_QUEUE against service :
java:comp/env/jms/OutQueue
2008-02-11 11:31:31,068 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ServerManager Starting transport jms
2008-02-11 11:31:31,068 [172.17.5.187-ACN3T27851] [WrapperSimpleAppMain]
INFO ServerManager Ready for processing
2008-02-11 11:32:19,107 [172.17.5.187-ACN3T27851] [I/O dispatcher 7]
INFO PipeImpl Using simulated buffered Pipes for event-driven to stream
IO bridging
2008-02-11 11:32:19,347 [172.17.5.187-ACN3T27851] [HttpServerWorker-1]
INFO TimeoutHandler This engine will expire all callbacks after : 86400
seconds, irrespective of the timeout action, after the specified or
optional timeout
-----Original Message-----
From: Asankha C. Perera [mailto:asankha@wso2.com]
Sent: Monday, February 11, 2008 11:49 AM
To: user@synapse.apache.org
Subject: Re: Switching transports - JMS to http using AQ
Greg
> I have attached the log as well.
>
I don't see the log :(
asankha
> -----Original Message-----
> From: Asankha C. Perera [mailto:asankha@wso2.com]
> Sent: Saturday, February 09, 2008 5:58 AM
> To: Blais, Gregg J.
> Subject: Re: Switching transports - JMS to http using AQ
>
> Gregg
>
>> I tried using a standard JMS client with AQ and it drops messages
>> successfully and pulls messages off the queue fine using standard JMS
>> code. Do you have any other suggestions on how to debug the issue
>>
> with
>
>> Synapse?
>>
>>
> Ok.. well this is good news and I think we should be able to get
Synapse
>
> working with AQ then..
>
> Can you post the JNDI properties you used to access AQ with the sample
> client on the dev or user list and any logs from your side? You can
hide
>
> any server names etc from the logs if its private
>
> Another option would be for one of the developers to test against AQ,
> but lets put it off for now as it seems like you could get this to
work
> with a bit of work.
>
> asankha
>
>
>
> This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the sender immediately and delete
the original. Any other use of the email by you is prohibited.
>
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
Re: Switching transports - JMS to http using AQ
Posted by "Asankha C. Perera" <as...@wso2.com>.
Greg
> I have attached the log as well.
>
I don't see the log :(
asankha
> -----Original Message-----
> From: Asankha C. Perera [mailto:asankha@wso2.com]
> Sent: Saturday, February 09, 2008 5:58 AM
> To: Blais, Gregg J.
> Subject: Re: Switching transports - JMS to http using AQ
>
> Gregg
>
>> I tried using a standard JMS client with AQ and it drops messages
>> successfully and pulls messages off the queue fine using standard JMS
>> code. Do you have any other suggestions on how to debug the issue
>>
> with
>
>> Synapse?
>>
>>
> Ok.. well this is good news and I think we should be able to get Synapse
>
> working with AQ then..
>
> Can you post the JNDI properties you used to access AQ with the sample
> client on the dev or user list and any logs from your side? You can hide
>
> any server names etc from the logs if its private
>
> Another option would be for one of the developers to test against AQ,
> but lets put it off for now as it seems like you could get this to work
> with a bit of work.
>
> asankha
>
>
>
> This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
>
RE: Switching transports - JMS to http using AQ
Posted by gr...@accenture.com.
Mustafa,
I created a MyChannelDemoUser account. I also tried with oc4jadmin and
got the same results.
-Gregg
-----Original Message-----
From: Mustafa Cayci [mailto:mustafa.cayci@gmail.com]
Sent: Monday, February 11, 2008 11:42 AM
To: user@synapse.apache.org
Subject: Re: Switching transports - JMS to http using AQ
Gregg,
>java.naming.security.principal=MyChannelDemoUser
>java.naming.security.credentials=MyChannelDemoPassword
Shouldn't this be "oc4jadmin/<PASSWORD>"?
Mustafa
On Feb 11, 2008 11:37 AM, <gr...@accenture.com> wrote:
>
> Here are the JNDI properties:
>
>
java.naming.factory.initial=com.evermind.server.ApplicationClientInitial
> ContextFactory
>
java.naming.provider.url=ormi://localhost:23791/how-to-connect-to-oemsjm
> sd
> java.naming.security.principal=MyChannelDemoUser
> java.naming.security.credentials=MyChannelDemoPassword
>
> I have attached the log as well.
>
> -Gregg
> -----Original Message-----
> From: Asankha C. Perera [mailto:asankha@wso2.com]
> Sent: Saturday, February 09, 2008 5:58 AM
> To: Blais, Gregg J.
> Subject: Re: Switching transports - JMS to http using AQ
>
> Gregg
> > I tried using a standard JMS client with AQ and it drops messages
> > successfully and pulls messages off the queue fine using standard
JMS
> > code. Do you have any other suggestions on how to debug the issue
> with
> > Synapse?
> >
> Ok.. well this is good news and I think we should be able to get
Synapse
>
> working with AQ then..
>
> Can you post the JNDI properties you used to access AQ with the sample
> client on the dev or user list and any logs from your side? You can
hide
>
> any server names etc from the logs if its private
>
> Another option would be for one of the developers to test against AQ,
> but lets put it off for now as it seems like you could get this to
work
> with a bit of work.
>
> asankha
>
>
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise private information. If you
have
> received it in error, please notify the sender immediately and delete
the
> original. Any other use of the email by you is prohibited.
>
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
Re: Switching transports - JMS to http using AQ
Posted by Mustafa Cayci <mu...@gmail.com>.
Gregg,
>java.naming.security.principal=MyChannelDemoUser
>java.naming.security.credentials=MyChannelDemoPassword
Shouldn't this be "oc4jadmin/<PASSWORD>"?
Mustafa
On Feb 11, 2008 11:37 AM, <gr...@accenture.com> wrote:
>
> Here are the JNDI properties:
>
> java.naming.factory.initial=com.evermind.server.ApplicationClientInitial
> ContextFactory
> java.naming.provider.url=ormi://localhost:23791/how-to-connect-to-oemsjm
> sd
> java.naming.security.principal=MyChannelDemoUser
> java.naming.security.credentials=MyChannelDemoPassword
>
> I have attached the log as well.
>
> -Gregg
> -----Original Message-----
> From: Asankha C. Perera [mailto:asankha@wso2.com]
> Sent: Saturday, February 09, 2008 5:58 AM
> To: Blais, Gregg J.
> Subject: Re: Switching transports - JMS to http using AQ
>
> Gregg
> > I tried using a standard JMS client with AQ and it drops messages
> > successfully and pulls messages off the queue fine using standard JMS
> > code. Do you have any other suggestions on how to debug the issue
> with
> > Synapse?
> >
> Ok.. well this is good news and I think we should be able to get Synapse
>
> working with AQ then..
>
> Can you post the JNDI properties you used to access AQ with the sample
> client on the dev or user list and any logs from your side? You can hide
>
> any server names etc from the logs if its private
>
> Another option would be for one of the developers to test against AQ,
> but lets put it off for now as it seems like you could get this to work
> with a bit of work.
>
> asankha
>
>
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise private information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the email by you is prohibited.
>
RE: Switching transports - JMS to http using AQ
Posted by gr...@accenture.com.
Here are the JNDI properties:
java.naming.factory.initial=com.evermind.server.ApplicationClientInitial
ContextFactory
java.naming.provider.url=ormi://localhost:23791/how-to-connect-to-oemsjm
sd
java.naming.security.principal=MyChannelDemoUser
java.naming.security.credentials=MyChannelDemoPassword
I have attached the log as well.
-Gregg
-----Original Message-----
From: Asankha C. Perera [mailto:asankha@wso2.com]
Sent: Saturday, February 09, 2008 5:58 AM
To: Blais, Gregg J.
Subject: Re: Switching transports - JMS to http using AQ
Gregg
> I tried using a standard JMS client with AQ and it drops messages
> successfully and pulls messages off the queue fine using standard JMS
> code. Do you have any other suggestions on how to debug the issue
with
> Synapse?
>
Ok.. well this is good news and I think we should be able to get Synapse
working with AQ then..
Can you post the JNDI properties you used to access AQ with the sample
client on the dev or user list and any logs from your side? You can hide
any server names etc from the logs if its private
Another option would be for one of the developers to test against AQ,
but lets put it off for now as it seems like you could get this to work
with a bit of work.
asankha
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
Re: Switching transports - JMS to http using AQ
Posted by "Asankha C. Perera" <as...@wso2.com>.
Greg
Let me CC: this reply for you as I notice that you haven't yet
subscribed to the user list..
> I am trying to switch from a JMS transport to an HTTP using Sample 250
> as a guide. I am using Oracle AQ as the JMS provider. When I drop a
> message on the queue, Synapse doesn't pick up the message. However, if
> I shutdown Synapse and restart it, it will pick up one message and call
> the HTTP Web service succesfully. It will only pick up one message,
> even if there are more on the queue. The same configuration (changed to
> point to ActiveMQ) works as expected. Any ideas on what might be
> causing this?
Seems like Oracle AQ is quite weired and does not support the standard
JMS semantics. Check Oracle documentation (including
http://www.oracle.com/technology/tech/java/oc4j/htdocs/OC4J-JMS-FAQ.html)
and try out some sample standard JMS clients against your Queue (e.g.
http://java.sun.com/products/jms/tutorial/1_3_1-fcs/doc/client.html)
If the above standard JMS clients can access Oracle AQ using JNDI etc,
you should then be able to use Oracle AQ with Synapse using the same
parameters without an issue. i.e. Synapse does support any standard JMS
provider that uses JMS 1.0.x API upwards
> Has Synapse been successfully used with Oracle AQ?
>
Not that I know of.. maybe someone else on the list will answer if they
have.. Since Oracle AQ is a proprietary product the chances that one of
the developers does gets access to this is low.
However, if you do require further support on this matter, send me an
email privately and I will inform you possible options
asankha