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:[EMAIL PROTECTED] 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.
