Thanks,
Girish.

I figured out that I have to use “FTQueueConnectionFactory” because I am using queues. I could able to fix all the issues and above method is working great.

Thanks,

Could you please help me doing the above configuration in my project, I am also using Tibco JMS with Tomcat and Spring app, my current serverUrl is hardcoded like below in my spring context file:

I am trying to move the serverUrl out of the code and want to config it in tomcat somewhere like you did above.

I am not able to figure out what should my tomcat serverl.xml should have for the following :

FTTopicConnectionFactory

And also could you please post your configuration from tomcat end, like the jms.properties what it has and the above FTTopicConnectionFactory details.

Thanks for your help.
golamari

Thanks for your reply.

I haven’t started the other application which is listening on port 2099 and have queue’s runing.

Actually I wanted to see if my application deploys/starts successfully, if the other application is not runing, but it failed.
I’m not passing any user/password and not sure where its required.

Thanks & Regards,
Irfan

QueueConnectionFactory

queue/PricingQueue

Regards,
Irfan

I have used these settings for my application as below

QueueConnectionFactory

and

queue/DataQueue

But when deploying this application it throws error for listener

and errors are as below

2009-04-02 16:04:12,500 DEBUG [org.jnp.interfaces.NamingContext] Failed to connect to localhost:2099
javax.naming.CommunicationException: Failed to connect to server localhost:2099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:2099 [Root exception is java.net.ConnectException: Connection refused: connect]]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:274)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1533)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:634)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at org.springframework.jndi.JndiTemplate$1.doInContext(JndiTemplate.java:123)
at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:85)
at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:121)
at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:146)
at org.springframework.jndi.JndiLocatorSupport.lookup(JndiLocatorSupport.java:93)
at org.springframework.jndi.JndiObjectLocator.lookup(JndiObjectLocator.java:105)
at org.springframework.jndi.JndiObjectTargetSource.getTarget(JndiObjectTargetSource.java:126)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:184)
at $Proxy56.createQueueConnection(Unknown Source)
at org.springframework.jms.listener.DefaultMessageListenerContainer102.createConnection(DefaultMessageListenerContainer102.java:71)
.
.
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost:2099 [Root exception is java.net.ConnectException: Connection refused: connect]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:248)
… 173 more
Caused by: java.net.ConnectException: Connection refused: connect

Any ideas?
Best Regards,
Irfan

I’ve been meaning to do a follow-up post about this very issue. What you want to do is configure to use a proxy interface at startup. You need to add two properties to you connection factory, proxyInterface and lookupOnStartup. We also find that setting the cache property to false also helps, as this allows the application to recover if it fails for any particular attempt to use the topic connection. We have low enough volume that it’s not a performance issue for us.

<bean id=”topicConnectionFactory” class=”org.springframework.jndi.JndiObjectFactoryBean”/>
<property name=”jndiTemplate” ref=”jndiTemplate”/>
<property name=”jndiName” value=”FTTopicConnectionFactory”/>
<property name=”proxyInterface” value=”javax.jms.TopicConnectionFactory” />
<property name=”lookupOnStartup” value=”false” />
<property name=”cache” value=”false” /><br />
</bean>

I have everything working fine and the only issue is my application reads the queue on some remote location and when starting the application if the remote application is not runing my application doesn’t start.

com.tibco.tibjms.naming.TibjmsInitialContextFactory

${jms.jndicontexturl}

In above configuration if the java.naming.provider.url is not accessible, application simply doesn’t start.

Any ideas?

Thanks & Regards,
Irfan