jaas.jar conflict in Weblogic 6.1 cluster

[Jagan]

We are using a Custom realm for Weblogic which communicates with Tivoli Policy
director for user authentication and authorization.
For communicating with PolicyDirector, We need to have IBM's jaas.jar as a JDK
extension(in jre/lib/ext directory)along with some more jar files.We never had
problems when running Weblogic in stand alone mode.But when we are trying to run
Weblogic as a cluster, Managed Server is not able to communicate with Admin Server
giving following exception:
-----------------------------------
Starting WebLogic Server ....
Connecting to http://166.57.31.66:8101...
<Feb 7, 2002 1:52:26 PM EST> <Info> <Logging> <FileLogger Opened.>
<Feb 7, 2002 1:52:27 PM EST> <Info> <Posix Performance Pack> <System has file
descriptor limits of - soft: '1024', hard: '1024'>
<Feb 7, 2002 1:52:27 PM EST> <Info> <Posix Performance Pack> <Using effective
file descriptor limit of: '1024' open sockets/files.>
<Feb 7, 2002 1:52:27 PM EST> <Info> <Posix Performance Pack> <Allocating: '3'
POSIX reader threads>
<Feb 7, 2002 1:52:28 PM EST> <Emergency> <Configuration Management> <Errors detected
attempting to connect to admin server at 166.57.31.66:8101 during initialization
of managed server ( 166.57.31.69:8001 ). The reported error was: < null > This
condition generally results when the managed and admin servers are using the same
listen address and port.>
<Feb 7, 2002 1:52:28 PM EST> <Emergency> <Server> <Unable to initialize the server:
'Fatal initialization exception
Throwable: weblogic.management.configuration.ConfigurationException - with nested
exception:
[javax.naming.AuthenticationException [Root exception is java.lang.SecurityException:
attempting to add an object which is not an instance of java.security.Principal
to a Subject's Principal Set]]
javax.naming.AuthenticationException. Root exception is java.lang.SecurityException:
attempting to add an object which is not an instance of java.security.Principal
to a Subject's Principal Set
at javax.security.auth.Subject$SecureSet.add(d:/jn130-userlvl/src/classes/sov/javax/security/auth/Subject.java:1098)
at weblogic.common.internal.BootServicesStub.writeUserInfoToSubject(BootServicesStub.java:72)
at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:80)
at weblogic.security.acl.internal.Security.authenticate(Security.java:108)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:509)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:364)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:336)
at weblogic.jndi.Environment.getContext(Environment.java:156)
at weblogic.jndi.Environment.getInitialContext(Environment.java:139)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:950)
at weblogic.management.Admin.start(Admin.java:351)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:372)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException - with nested exception:
[javax.naming.AuthenticationException [Root exception is java.lang.SecurityException:
attempting to add an object which is not an instance of java.security.Principal
to a Subject's Principal Set]]
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:959)
at weblogic.management.Admin.start(Admin.java:351)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:372)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
----------------------------------------------------------
When we removed IBM's jaas.jar from jdk/jre/lib/ext to check the clustering.It
works fine.But We need to have jaas.jar for our custom realm.

Thanks.

Jagan.