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:[EMAIL PROTECTED]
Sent: Tuesday, February 12, 2008 10:52 AM
To: [email protected]
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 <[EMAIL PROTECTED]> 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.
