Forum Stats

  • 3,750,550 Users
  • 2,250,192 Discussions
  • 7,867,004 Comments

Discussions

Java QueueConnectionFactory lookup failing, possibly because weblogic server having multiple jms ser

Hi Team,

I am successfully able to put one message on JMS Queue which is hosted on my local weblogic environment.

However when I am trying to do the same on another environment, it is failing at the first step where I am trying lookup for QueueConnectionFactory.

Here is my code that is failing.

Properties props = new Properties();

  props.setProperty(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");

  props.setProperty(Context.PROVIDER_URL, "t3://IP_Address:9001");

  props.setProperty(Context.SECURITY_PRINCIPAL, "username");

  props.setProperty(Context.SECURITY_CREDENTIALS, "password");

  InitialContext ctx = new InitialContext(props);

  qconFactory = (QueueConnectionFactory) ctx.lookup("[email protected]@omx_jms_connectionFactory");

Weblogic server where my java code is failing has following setup:

There are 2 JMS Servers: with one JMS server showing Health as OK.

1. JMS QConnectionFactory details

JMS Queue factory: omx_jms_connectionFactory

JNDI for JMS Queue factory: omx.jms.connectionFactory

Targets: NewtonServicesCluster

2. JMS Server details

JMS ServerName: newtonServicesJmsServer1

PersistentStoreName: NewtonServicesServerFileStore1

Target: NewtonServicesServer1

CurrentServer: NewtonServicesServer1

3. JMS Queue details

QueueName: sagtAvosRequestQueue

Type: Uniform Distributed Queue

JNDI Name: omx.jms.local.cthadapter.sagtAvosRequestQueue

Subdeployment: DistributedServicesJMSServer

Target: newtonServicesJmsServer1

André Ribeiro
This discussion has been closed.