Oracle Audio Technologies 12.2 manual Setting Up a Foreign JMS Server on WebLogic Server

Setting Up a Foreign JMS Server on WebLogic Server

Local JNDI Name: CommonConnectionFactory

Remote JNDI Name: CommonConnectionFactory

7.Configure a new Foreign JMS Topic and point it to the topic created under the CommonJMSServer deployed on Plan.

For example,

Name: RemoteNotificationTopic

Local JNDI Name: com.profitlogic.notification.topic

Remote JNDI Name: com.profitlogic.notification.topic

Note: The 'com.profitlogic.notification.topic' used above is the JNDI name of NotificationEventTopic under CommonJMSServer.

8.Restart the servers.

Since the Place JMS configuration depends on Plan, and the two servers are started concurrently, the following exception is logged during the start up in the Place logs (see below). The JNDI lookup is retrieved by the Place server after start up and hence the exception can be ignored during the start up.

Note: To avoid the exception, Place servers must be started sequentially after Plan servers during startup.

Registering Application: Store set

com.profitlogic.common.notification.EventException:(1217324969224:0): JNDI lookup failure[javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://dev-app-l07:7090: Destination unreachable; nested exception is:

java.net.ConnectException: Connection refused; No available router to destination]]

<.......... More exceptions>

Installing Place Over Plan 6-7