My Oracle Support Banner

Getting Cannot Resolve URL for Protocol JMS When Non SSL Port is Disabled (Doc ID 2338471.1)

Last updated on DECEMBER 13, 2023

Applies to:

Oracle WebLogic Server - Version and later
Information in this document applies to any platform.


A client cannot connect to JMS queue in the following conditions:

The issue can be reproduced with the following test case, including a Java client, attached to this document. 

To setup environment

Create a new WLS domain and define the following resources:

see: Create a Basic WebLogic Server Domain

Ch 3 Configuring Basic JMS System Resources

Then deploy the Custom.ear application (attached to this note), which contains a HelloWorld web service, MDB listening on JMS Queue (InventoryCustomWSQueue).

On the client end, the JMSQueueClient.jar file sends a WS request on the InventoryCustomWSQueue queue.

To run the testcase

To run this client, copy the attached JMSQueueClient.jar and hello.txt in a testcase directory, for example.
Setup the environment using the {new domain}/bin/ file

The issue persists for both t3s and t3 protocols.

When the non-SSL listen ports are enabled and cluster address is configured to use only them in these conditions the issue cannot be seen.




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
 To setup environment
 To run the testcase
 To verify the issue from WLS console

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