This content has been marked as final. Show 2 replies
Perhaps you need to check the security configuration for the queue (Q) to ensure it matches the MDB (M) security parameters.
Weblogic Security Realms: User/Group
JMSModule Security: Role/Group , Policy: Role
MDB: MDBRole/Principal (User) in weblogic-ejb-jar.xml
2. Double check that the queue created in weblogic
3. Test your queue (manually create a new message using weblogic console) or observe unconsumed messages (if producer has run and placed messages)
1) Check the queueJNDI lookup name & test the queue using weblogic provided sample test
2) Message Bridge configuration
3)See that in both the machines the Guest Disabled is Unchecked in Domain Wide Security settings of both machines, also see that credential checking tab is unchecked and the contents of credential principals in both the machines are the SAME.
4)check connection factory and it should be XA enabled.
5) Security roles/policy