Oracle Weblogic Server (MOSC)

MOSC Banner

Getting the exception: weblogic.jms.common.InvalidClientIDException

edited Jan 18, 2011 10:33PM in Oracle Weblogic Server (MOSC) 4 commentsAnswered
 Hi,

We are the sender end and using 10gR3, and our recever end is consuming data from our jms queue using wls 8.1 using bridhe connectivity.

They are facing weblogic.jms.common.InvalidClientIDException exception and the connectivity was losed due to this.

 Can you please help us to solve the issue?

Exception detail:

JMS Connection Problem: weblogic.jms.common.InvalidClientIDException: Client id, bam2tbsm, is in use.  The reason for rejecti

on is "The JNDI name weblogic.jms.connection.clientid.bam2tbsm was found, and was bound to an object of type weblogic.jms.frontend.FEClientIDSingularAggregat

able : FEClientIDSingularAggregatable(SingularAggregatable(<7725433874603523300.1>:90):bam2tbsm)"

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center