Remote JMS provider is not working

[Navin2008]

I have a JMS Queue on a remote Websphere Server where
messages are published.Lets call it as "Server2"

My application has been deployed in "Server1" and in
"Messaging-Config.xml", I have given the following entry



<destination id="testJMSQueue">

<adapter ref="jms"/>

<properties>

<jms>

<destination-type>Queue</destination-type>


<message-type>javax.jms.TextMessage</message-type>

<connection-factory>jms/QCF</connection-factory>


<destination-jndi-name>jms/testQueue</destination-jndi-name>

<delivery-mode>NON_PERSISTENT</delivery-mode>


<message-priority>DEFAULT_PRIORITY</message-priority>


<preserve-jms-headers>"true"</preserve-jms-headers>


<acknowledge-mode>AUTO_ACKNOWLEDGE</acknowledge-mode>

<max-producers>1</max-producers>

<initial-context-environment>

<property>

<name>Context.PROVIDER_URL</name>

<value>iiop://server2:9810</value>

</property>

<property>

<name>Context.INITIAL_CONTEXT_FACTORY</name>


<value>com.ibm.websphere.naming.WsnInitialContextFactory</value>

</property>

</initial-context-environment>

</jms>

</properties>

<channels>

<channel ref="my-rtmp"/>

</channels>

</destination>



I consume the message using mx:consumer , by subscribing to
"testJMSQueue" defined "Messsaging-config"



Even though messages are there in "testQueue" in the remote
JMS server, messages are not getting received..

If i change the configuration to point to "Server1" JMS queue
, then it works.





Pl let me know how to make it work using remote JMS provider

[Karl_Sigiscar_1]

Here is my working JMS config:



<?xml version="1.0" encoding="UTF-8"?>



<service id="message-service"

class="flex.messaging.services.MessageService">



<adapters>

<adapter-definition id="actionscript"
class="flex.messaging.services.messaging.adapters.ActionScriptAdapter"
/>

<adapter-definition id="jms"
class="flex.messaging.services.messaging.adapters.JMSAdapter"
default="true"/>

</adapters>



<destination id="alertsfeed">



<properties>



<jms>

<destination-type>Topic</destination-type>


<message-type>javax.jms.ObjectMessage</message-type>


<connection-factory>ConnectionFactory</connection-factory>


<destination-jndi-name>/topic/gis-alert-topic</destination-jndi-name>

<delivery-mode>NON_PERSISTENT</delivery-mode>


<message-priority>DEFAULT_PRIORITY</message-priority>


<acknowledge-mode>AUTO_ACKNOWLEDGE</acknowledge-mode>

<transacted-sessions>false</transacted-sessions>



<initial-context-environment>



<property>

<name>Context.SECURITY_PRINCIPAL</name>

<value>anonymous</value>

</property>



<property>

<name>Context.SECURITY_CREDENTIALS</name>

<value>anonymous</value>

</property>



<property>

<name>Context.PROVIDER_URL</name>

<value>jnp://www.myserver.com:1099</value>

</property>



<property>

<name>Context.INITIAL_CONTEXT_FACTORY</name>


<value>org.jnp.interfaces.NamingContextFactory</value>

</property>



</initial-context-environment>



</jms>



</properties>



<channels>

<channel ref="my-polling-amf"/>

</channels>



<adapter ref="jms"/>



</destination>



</service>

[Karl_Sigiscar_1]

We use JNDI to access the remote JMS topic, hence the use of
the jnp:// protocol.

[Navin2008]

Does anyone tried using the Websphere JMS Provider? I need to
use "IIOP protocal" only ..

[ashwinbks83]

hi Navin

Are you using tomcat to run your blazeds environment. If you are can you send us the log from your application server?

Regards

Ashwin