My Oracle Support Banner

Alert Destination For Local JMS Queues (Doc ID 2524548.1)

Last updated on JULY 10, 2020

Applies to:

Oracle Service Bus - Version and later
Information in this document applies to any platform.


On : version, OSB Transports

In our 11g environment, we were able to create an OSB alert destination with the following Destination URI:


We've tried various other options:

- jms://localhost:8011/weblogic.jms.ConnectionFactory/cis/jms/OsbErrorQueueV1
- jms://<HOST>:8011,<HOST>:8011,<HOST>:8011,<HOST>:8011/weblogic.jms.ConnectionFactory/cis/jms/OsbErrorQueueV1

None of those options work, because "8011" is an SSL (t3s) port, and the alert destination seems to use only non-SSL (t3) port. Our non-SSL ports have been disabled.

According to Doc ID 1176343.1, the (jms:///) protocol should be working for local JMS connections.

In 11g, alerts using this destination would produce a message on the "cis/jms/OsbErrorQueueV1" on the server OSB was running on.

In 12c, alerts using this destination do not produce a message and give the following warning message:

no host: t3:///weblogic.jms.ConnectionFactory/cis [Root exception is no host: t3:///weblogic.jms.ConnectionFactory/cis]>


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.