Dear All, Thanks for participating. Here here the last findings we have:
1.The class removal under javax/jms in the wlfullclient.jar are necessary because other classloader errors could occur. It is mandatory to remove everything under javax/jms.
2.From the XPI Inspector traces in starting and stopping the channel, it connects to the Weblogic Server and to the queue successfully.
According to Weblogic Documentation when you create a JNDI Initial Context with a username and password, you associate a user with a thread. Before starting a new Context on the thread, you must close the first Context so that the first user is no longer associated with the thread. Otherwise, users are pushed down in the stack each time a new context is created.
This is not an efficient use of resources and may result in the incorrect user being returned by ctx.lookup() calls.
This is the reason why we close the Initial Context after a successful connection. But according to this documentation the security scope ends with a context.close() method.
There is a flag weblogic.jndi.enableDefaultUser. If this flag is enabled even after a ontext.close() the current user is not removed from the thread context.
The solution is to add this flag in the JMS Receiver channel configuration.
JNDI.InitialContext.property.5 =
java.lang.String weblogic.jndi.enableDefaultUser, java.lang.String true
Thanks for your attention.