Jaas.jar conflict in Weblogic 6.1 cluster

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.

Hi jerry
i already got that problem solved by removing jaas.jar file
from class path.
i don'nt how it is working with out in classpath...?
Jerry <[email protected]> wrote:
Hi Nivas,
I think that the problem you are seeing has something to do with the
placement of jaas.jar in your classpath
On WebLogic server, put jaas.jar in the classpath after weblogic.jar.
I would bet that you have it placed before weblogic.jar right now.
I don't think the exception that you're seeing right now has anything
to do with your weblogic.policy file right now, so I think it is
safe to not worry about it right now.
Hope this helps,
Joe Jerry

Similar Messages

Conflict of weblogic with jaas.jar

Hi there,
I am using weblogic6.0+sp1 for JAAS simple and SSL authentication. Sun's
implementation class com.sun.security.auth.login.ConfigFile in jaas.jar
is conflict with the Config class I implemented that extends
Configuration to parse the login policy file and return the array of
AppConfigurationEntry. If this jaas.jar gets picked up before
weblogic.jar (For some jdk version, this jar is put under the jdk's
lib/ext directory) the sun's implementation will be picked up instead of
mine and this will results in failure. I am wandering if this is a bug
or not?
Thanks,
Cathy

This has nothing to do with the class name, since both my implementation and
sun's are subclass of Configuration class. Runtime, it will pick up sun's if
jaas.jar is put in front of weblogic.jar.
Hellen Andersen wrote:
An aside related question: isn't jaas.jar always installed in lib/ext?
Otherwise, couldn't you rename your ConfigFile class so it doesn't match
Sun's?
"Cathy Wei" <[email protected]> wrote in message
news:[email protected]..
Hi there,
I am using weblogic6.0+sp1 for JAAS simple and SSL authentication. Sun's
implementation class com.sun.security.auth.login.ConfigFile in jaas.jar
is conflict with the Config class I implemented that extends
Configuration to parse the login policy file and return the array of
AppConfigurationEntry. If this jaas.jar gets picked up before
weblogic.jar (For some jdk version, this jar is put under the jdk's
lib/ext directory) the sun's implementation will be picked up instead of
mine and this will results in failure. I am wandering if this is a bug
or not?
Thanks,
Cathy

ORA-01017: invalid username/password; logon denied on Weblogic 9.0 cluster

I am experiencing the following exception in Weblogic 9.0 server cluster environment. The same code works fine in non-cluster environment. The problem happens every now and then and would go away temporarily after recycling the domains. The Oracle database that the backend system connects to is 9.0.2.6. I am using the ocjdbc14.jar jdbc driver that comes with the Weblogic 9.0 on the client side to connect. I really appreciate any help or clue.
Ashkan
Error on dequeuing requests
org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLException: ORA-01017: invalid username/password; logon denied
java.sql.SQLException: ORA-01017: invalid username/password; logon denied
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
     at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289)
     at oracle.jdbc.ttc7.O3log.receive2nd(O3log.java:496)
     at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:278)
     at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:346)
     at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:468)
     at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:314)
     at java.sql.DriverManager.getConnection(Ljava.lang.String;Ljava.util.Properties;Ljava.lang.ClassLoader;)Ljava.sql.Connection;(Unknown Source)
     at java.sql.DriverManager.getConnection(Ljava.lang.String;Ljava.util.Properties;)Ljava.sql.Connection;(Unknown Source)
     at org.springframework.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriverManager(DriverManagerDataSource.java:291)
     at org.springframework.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriverManager(DriverManagerDataSource.java:277)
     at org.springframework.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriverManager(DriverManagerDataSource.java:259)
     at org.springframework.jdbc.datasource.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:241)
     at org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:111)
     at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:77)
     at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:810)
     at org.springframework.jdbc.core.JdbcTemplate.call(JdbcTemplate.java:857)
     at org.springframework.jdbc.object.StoredProcedure.execute(StoredProcedure.java:102)
     at com.rwi.wam.dao.serviceprovider.ServiceProviderDequeue.dequeue(ServiceProviderDequeue.java:32)
     at com.rwi.wam.dao.serviceprovider.ServiceProviderDAO.dequeueRequest(ServiceProviderDAO.java:48)
     at com.rwi.wam.ejb.WAMRequestMessageBean.onMessage(WAMRequestMessageBean.java:168)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:425)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:332)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:288)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3069)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2989)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:3448)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)

Hi, I can tell you that you're not using any WebLogic
JDBC code. You're getting a connection directly from
the Oracle drive, and you can change the vesion of the
drive if you want by changing the ojdbc14.jar in the
weblogic server\lib directory.
However, I believe the problem is an inherent weakness
at the DBMS. The DBMS listener process can sometimes
be temporarily swamped if it gets too many connection
requests at one time, and will fail some of them even if
they are all identical and correct.
This is one of the major reasons you should use WebLogic
connection pools so you always get already-made and
tested connections.
Another huge danger is that you are using DriverManager
calls. These are very bad in multithreaded applications
like WebLogic, because all DriverManager calls (including
some internal ones that all JDBC drivers call all the time,
are class-synchronized! This means that one call to
getConnection() will probably bolock all other running
JDBC in the whole JVM. If you can change the springframework
code to use WebLogic DataSources to pools, you'll be much
better off.
Joe
Ashkan Gholam-Zadeh wrote:
I am experiencing the following exception in Weblogic 9.0 server cluster environment. The same code works fine in non-cluster environment. The problem happens every now and then and would go away temporarily after recycling the domains. The Oracle database that the backend system connects to is 9.0.2.6. I am using the ocjdbc14.jar jdbc driver that comes with the Weblogic 9.0 on the client side to connect. I really appreciate any help or clue.
Ashkan
Error on dequeuing requests
org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLException: ORA-01017: invalid username/password; logon denied
java.sql.SQLException: ORA-01017: invalid username/password; logon denied
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
     at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289)
     at oracle.jdbc.ttc7.O3log.receive2nd(O3log.java:496)
     at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:278)
     at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:346)
     at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:468)
     at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:314)
     at java.sql.DriverManager.getConnection(Ljava.lang.String;Ljava.util.Properties;Ljava.lang.ClassLoader;)Ljava.sql.Connection;(Unknown Source)
     at java.sql.DriverManager.getConnection(Ljava.lang.String;Ljava.util.Properties;)Ljava.sql.Connection;(Unknown Source)
     at org.springframework.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriverManager(DriverManagerDataSource.java:291)
     at org.springframework.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriverManager(DriverManagerDataSource.java:277)
     at org.springframework.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriverManager(DriverManagerDataSource.java:259)
     at org.springframework.jdbc.datasource.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:241)
     at org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:111)
     at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:77)
     at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:810)
     at org.springframework.jdbc.core.JdbcTemplate.call(JdbcTemplate.java:857)
     at org.springframework.jdbc.object.StoredProcedure.execute(StoredProcedure.java:102)
     at com.rwi.wam.dao.serviceprovider.ServiceProviderDequeue.dequeue(ServiceProviderDequeue.java:32)
     at com.rwi.wam.dao.serviceprovider.ServiceProviderDAO.dequeueRequest(ServiceProviderDAO.java:48)
     at com.rwi.wam.ejb.WAMRequestMessageBean.onMessage(WAMRequestMessageBean.java:168)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:425)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:332)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:288)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3069)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2989)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:3448)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)

Conflict Error Handler Exception in Cluster

          Hi
          We bind some objects using rebind method to the JNDI in our weblogic servers.
          If we run one instance of weblogic server no problem but if we start another one
          server in the cluster it throughs conflict error handler exception. More over
          if we refresh one object instance in one server (by rebind) the new changes in
          the object doesn't reflect in other servers.


If you bind non clusterable objects in the jndi from two servers then you
          will run into conflicts.
          Basically in a cluster, two servers cannot provide the same service unless
          it is clusterable.
          WLS assumes that everything you bind into jndi is a service.
          -- Prasad
          "BSIL" <[email protected]> wrote in message
          news:3b94f93a$[email protected]..
          >
          > Hi
          > We bind some objects using rebind method to the JNDI in our weblogic
          servers.
          > If we run one instance of weblogic server no problem but if we start
          another one
          > server in the cluster it throughs conflict error handler exception. More
          over
          > if we refresh one object instance in one server (by rebind) the new
          changes in
          > the object doesn't reflect in other servers.

Jaas sample progrma in weblogic 6.1 giving the following error java.lang.SecurityException: attempting to add an object which is not an instance of java.security.Principal to a Subjec

jaas sample progrma in weblogic 6.1 giving the following error java.lang.SecurityException:
attempting to add an object which is not an instance of java.security.Principal
to a Subjec
on runnig the program during the call of method Authenticate.authenticate(env,
subject); giving following exceptions Error: Login Exception on authenticate,
java.lang.SecurityException: attempting to add an object which is not an instance
of java.security.Principal to a Subjec t's Principal Set Authentication Failed:
Unexpected Exception, javax.security.auth.login.LoginExce ption: java.lang.SecurityException:
attempting to add an object which is not an instance of java.security.Principal
to a Subject's Principal Set javax.security.auth.login.LoginException: javax.security.auth.login.LoginExcepti
on: java.lang.SecurityException: attempting to add an object which is not an ins
tance of java.security.Principal to a Subject's Principal Set at examples.security.jaas.SampleLoginModule.login(SampleLoginModule.java
:192) at java.lang.reflect.Method.invoke(Native Method) at javax.security.auth.login.LoginContext.invoke(LoginContext.java:595)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:1 25) at
javax.security.auth.login.LoginContext$3.run(LoginContext.java:531) at java.security.AccessController.doPrivileged(Native
Method) at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java
:528) at javax.security.auth.login.LoginContext.login(LoginContext.java:449) at
examples.security.jaas.SampleClient.main(SampleClient.java:96)
1)what is the reason for this problem
2)in weblogic document they told to edit server.policy file in webligic\lib folder
a)what the modification is needed in this file..?

Hi jerry
i already got that problem solved by removing jaas.jar file
from class path.
i don'nt how it is working with out in classpath...?
Jerry <[email protected]> wrote:
Hi Nivas,
I think that the problem you are seeing has something to do with the
placement of jaas.jar in your classpath
On WebLogic server, put jaas.jar in the classpath after weblogic.jar.
I would bet that you have it placed before weblogic.jar right now.
I don't think the exception that you're seeing right now has anything
to do with your weblogic.policy file right now, so I think it is
safe to not worry about it right now.
Hope this helps,
Joe Jerry

How to use both ojdbc14.jar and ojdbc6.jar in same weblogic domain(weblogic12C)

Hi all,
I 'm having issue of using both ojdbc14.jar and ojdbc6.jar in same weblogic application and same weblogic domain in weblogic 12C environment.
how can i do that?
i'm currently having application developed using jdk 1.6 and ojdbc6.jar, application developed using jdk 1.4 and ojdbc14.jar.both are currently installed at same domain.
i want to use the both ojdbc14.jar and ojdbc6.jar in same domain.
what i previously did was renaming /usr/weblogic/wls_server10.3.4/lib/ojdbc6.jar to /usr/weblogic/wls_server10.3.4/lib/ojdbc6.jar.bak and put ojdbc14.jar in the same path when i wanna use ojdbc14.jar.
i haven't use both in same environment before, but to go live i wanna match about requirement.pls help.
i know the way use this by having two domains, but in the same domain i could not find a solution yet.
Please help

Hey
I have the similar requirement.. Did you managed to get an option of doing it? If yes, please provide some insights
Thanks in Advance

Deploying, ReDeploying JAR file to WebLogic EM without restarting the serve

Hi
Can any one help me how to re-deploy .jar file on weblogic EM with steps.
Deploying, ReDeploying JAR file to WebLogic EM without restarting the server
Appriciate if you provide information in steps with screenshot.
Note: Not in weblogic 11g console.
Thanks,
Phani

http://download.oracle.com/docs/cd/E14571_01/core.1111/e10105/deploy.htm#BIHIIEIA

How to deploy EJB jar file in Weblogic 8.1

Hi,
I have created the EJB jar file, bearing home,remote,ejb and client class aling with the META-INF folder containing ejb-jar.xml and weblogic-ejb-jar.xml.
After all this I am confused where to put this EJB jar file so that the container could deploy it.
I am putting it in application folder of my own created Domain.
Suggest me...

Put it anywhere you like. You can always deploy it using the administrator console. There usually is an auto-deployment directory for the domain. You could find all that information in the Weblogic documentation.

Javax.xml.ws.soap.SOAPFaultException: ClusterRoutingTubeUtils weblogic.wsee.jaxws.cluster.ClusterRoutingTubeUtils@6ad8e382 not ready, no WseeClusterRoutingRuntimeMBean/WseeRuntimeMBean

Hi,everyone:
I am running into this error when I call a webService :My weblogic version is 10.3.5 and have applied the patch N5G9.
javax.xml.ws.soap.SOAPFaultException: ClusterRoutingTubeUtils weblogic.wsee.jaxws.cluster.ClusterRoutingTubeUtils@6ad8e382 not ready, no WseeClusterRoutingRuntimeMBean/WseeRuntimeMBean
at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:197)
at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:122)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:125)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:95)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:136)
at $Proxy117.getLoginUserInfoByCzryDm(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.wsee.jaxws.spi.ClientInstanceInvocationHandler.invoke(ClientInstanceInvocationHandler.java:84)
at $Proxy118.getLoginUserInfoByCzryDm(Unknown Source)
at com.hkgt.sso.access.ZRWebServiceProxyImpl.getLoginUserInfoByCzryDm(ZRWebServiceProxyImpl.java:106)
at com.hkgt.sso.access.WebServiceAuthenticationHandler.doAuthentication(WebServiceAuthenticationHandler.java:71)
at com.hkgt.sso.access.AMManagerImpl.doAuthentication(AMManagerImpl.java:165)
at com.hkgt.sso.authserver.SSOLoginServlet.doPost(SSOLoginServlet.java:175)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3723)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3689)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2285)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2184)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1459)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
However it works fine under another machine(say machine A) when I call the same webservice. I tried to copy the whole domain to the problematic machine, this error still appears.
Does anyone have any suggestions. Thank you !

Hi,everyone:
I am running into this error when I call a webService :My weblogic version is 10.3.5 and have applied the patch N5G9.
javax.xml.ws.soap.SOAPFaultException: ClusterRoutingTubeUtils weblogic.wsee.jaxws.cluster.ClusterRoutingTubeUtils@6ad8e382 not ready, no WseeClusterRoutingRuntimeMBean/WseeRuntimeMBean
at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:197)
at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:122)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:125)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:95)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:136)
at $Proxy117.getLoginUserInfoByCzryDm(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.wsee.jaxws.spi.ClientInstanceInvocationHandler.invoke(ClientInstanceInvocationHandler.java:84)
at $Proxy118.getLoginUserInfoByCzryDm(Unknown Source)
at com.hkgt.sso.access.ZRWebServiceProxyImpl.getLoginUserInfoByCzryDm(ZRWebServiceProxyImpl.java:106)
at com.hkgt.sso.access.WebServiceAuthenticationHandler.doAuthentication(WebServiceAuthenticationHandler.java:71)
at com.hkgt.sso.access.AMManagerImpl.doAuthentication(AMManagerImpl.java:165)
at com.hkgt.sso.authserver.SSOLoginServlet.doPost(SSOLoginServlet.java:175)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3723)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3689)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2285)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2184)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1459)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
However it works fine under another machine(say machine A) when I call the same webservice. I tried to copy the whole domain to the problematic machine, this error still appears.
Does anyone have any suggestions. Thank you !

JAR conflicts

I have a web application in Tomcat, and in the classpath of Tomcat there are already many jar files (spring, struts, commons-logging, mail, etc). In this web application I want to install a servlet that uses a new version of struts, but the problem is that there is already another servlet that should continue using an old version of struts. How can I handle with this situation?

duffymo wrote:
strict wrote:
paulcw wrote:
Make two different web applications and put the struts jars in the separate lib directories under each?These two servlets should be in the same web apps.
But I notice that Tomcat has a version of commons-collections-3.1.jar in its common/lib directory, and spring also uses a commons-collections. What if spring uses a different version of this jar that conflicts with the one in Tomcat?
>
>Make two different web applications and put the struts jars in the separate lib directories under each?These two servlets should be in the same web apps.
you duplicate two servlets in several web apps? violates " don't repeat yourself"
No. I mistyped. I meant two servlets in the same web app (in the singular, not plural)
But I notice that Tomcat has a version of commons-collections-3.1.jar in its common/lib directory, and spring also uses a commons-collections. What if spring uses a different version of this jar that conflicts with the one in Tomcat?that's what osgi solvesActually, I read the Tomcat documentation, and I see that such a conflict is impossible, although there are another kinds of jar conflicts, described in that documentation. But this specific conflict (spring dependency jars with tomcat jars) is not possible. Thank God!

Weblogic.jar conflict with my js-1.0.jar(org.mozilla.javascript )

I am using js-1.0.jar in my application. It gets conflict with package inside the weblogic.jar. For this issue i set the js-1.0.jar in server start-up and it works. But is there any way to resolve the (js-1.0.jar) package conflict without setting it in the classpath.

I am using js-1.0.jar in my application. It gets conflict with package inside the weblogic.jar. For this issue i set the js-1.0.jar in server start-up and it works. But is there any way to resolve the (js-1.0.jar) package conflict without setting it in the classpath.

Storing ejb-jar.xml and weblogic-ejb-jar.xml

We are using Weblogic Integration 9.2 on a 2 cluster system sharing the same domain directory.
1) I am wondering if I can store these files somewhere in the domains directory instead of the EJB's archive - call it MyEjb.jar?
2) Are there any benefits to storing these files outside of the MyEjb.jar file? I am thinking to make it easier to update the configurations such as number of MDB consumers and such to avoid having to recreate the MyEjb.jar with the new config and redeploy the application. A simple text edit and bounce could be fine if the files can be stored outside.
2b) Can another application in the same domain read these files to find out the connection factory and queue information?
3) Are there any disadvantages to storing those files outside of the jar file? One issue I can think of here is how to deal with them on a cluster environment.
4) Any other feedback apprecaited.

If you look at the contents of a deployment plan (Plan.xml) when you have it generated
<deployment-plan ...>
<module-override>
    <module-name>ejb.jar</module-name>
    <module-type>ejb</module-type>
    <module-descriptor external="true">
      <root-element>weblogic-ejb-jar</root-element>
      <uri>META-INF/weblogic-ejb-jar.xml</uri>
    </module-descriptor>
    <module-descriptor external="false">
      <root-element>ejb-jar</root-element>
      <uri>META-INF/ejb-jar.xml</uri>
    </module-descriptor>
    <module-descriptor external="true">
      <root-element>persistence-configuration</root-element>
      <uri>META-INF/persistence-configuration.xml</uri>
    </module-descriptor>
    <module-descriptor external="false">
      <root-element>persistence</root-element>
      <uri>META-INF/persistence.xml</uri>
    </module-descriptor>
</module-override>
</deployment-plan>You can see which files can be external and which can be not. The weblogic-ejb-jar.xml can be external
but in this case you need a deployment plan to point weblogic to the file. The ejb-jar.xml cannot be
external (see external=false)
The benefit of storing the weblogic-ejb-jar.xml is that your administrator can fine tune certain
configurations by using a deployment plan, instead of having to extract the contents from the jar file
and then repackage it again.
No need to worry about a clustered environment, you can place the jar and the deployment plan
on the server where the admin server is located, when you deploy an application you deploy it to
the cluster and everything is taken care off.
More information on deployment plans can be found here: http://download.oracle.com/docs/cd/E11035_01/wls100/deployment/config.html

Error in Deploying jar file in weblogic

I got this error while deploying in weblogic. Give me the solution to solve this.
Exception:weblogic.management.ApplicationException: prepare failed for Count1 Module: Count1 Error: Exception preparing module: EJBModule(Count1,status=NEW) Unable to deploy EJB: F:\Arul\EJB\Statefull\deploy\Count1.jar from Count1.jar: weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: count.CountBean at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:548) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:232) at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1262) at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:477) at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2847) at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1534) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031) at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2634) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2584) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2506) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:833) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:542) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
[Deployer:149033]preparing application Count1 on myserver
[Deployer:149033]failed application Count1 on myserver
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application Count1 on myserver.: Exception:weblogic.management.ApplicationException: prepare failed for Count1 Module: Count1 Error: Exception preparing module: EJBModule(Count1,status=NEW) Unable to deploy EJB: F:\Arul\EJB\Statefull\deploy\Count1.jar from Count1.jar: weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: count.CountBean at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:548) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:232) at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1262) at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:477) at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2847) at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1534) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031) at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2634) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2584) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2506) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:833) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:542) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170) .

Give me the solution to solve this.Manners cost so little and usually encourage helpfulness in others.

Error while deployingejb jar file in weblogic 8.1

Exception:weblogic.management.ApplicationException: prepare failed for testsix Module: testsix Error: Exception preparing module: EJBModule(testsix,status=NEW) Unable to deploy EJB: C:\bea\user_projects\domains\mydomain\applications\testsix.jar from testsix.jar: weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: examples.CalculatorSessionBean at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:550) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:232) at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1262) at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:477) at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2962) at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1534) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031) at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2602) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2552) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2474) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

A possibly related issue:
http://forums.bea.com/thread.jspa?threadID=600016825
...I have faced same problem most of time and resolved ot by recompileing my all the classes and new deployment descriptors. First you should make new java files for all clases(copy contents fron old java files ) and make anew package same as old and then do all the required process and re deploy it. I think because of some problem in class generation...
Hope it helps.

Problems processing a large batch of data within a Weblogic 5.1 cluster

I have about exhausted my sources of information on this, so I ask the
          experts:
          The project I am involved with is attempting to build a scheduled
          process on a 5.1 cluster which will retrieve hundreds to thousands of
          database rows from a small group of Oracle tables and then submit them
          into a legacy system for processing. The problems we face are:
          1. We cannot have duplicate data submitted from startup classes on
          different servers in the cluster
          2. We need the process to run if even only one machine in the cluster is
          available and therefore do not want to tie the process to a single
          machine
          3. We would prefer to distribute the workload across all servers
          currently available in the cluster, but this is not mandatory.
          One solution is to retrieve each record as an Entity bean, attempting to
          update it to "in process" and rejecting any failures thus utilizing
          database locking, but due to the large number of records being processed
          this is much too resource intensive as well as time consuming.
          We have looked into JMS based solutions, but it appears that JMS under
          5.1 is tied to a specific server (failing case 2).
          One acceptable approach that we have yet to find a way of implementing
          is to have a "singleton" session bean, only one of which exists on the
          cluster (though it may exist anywhere on the cluster). I have run
          across a number of other applications for just this sort of EJB, but is
          it possible to implement?
          Sadly, Weblogic 6.0 cannot be part of the solution as our company will
          not be adopting it until well after this project's delivery date.
          Are we missing something obvious?
          Many thanks!
          -Steve


You have to have all the servers in the cluster polling for work out of the
          database. Use the database as a scheduling / routing mechanism. Use timers
          on each server in the cluster to kick off a "find me one thing to do"
          process every n minutes or seconds.
          Peace,
          Cameron Purdy
          Tangosol, Inc.
          http://www.tangosol.com
          +1.617.623.5782
          WebLogic Consulting Available
          "Steven Wicklund" <[email protected]> wrote in message
          news:[email protected]...
          > I have about exhausted my sources of information on this, so I ask the
          > experts:
          > The project I am involved with is attempting to build a scheduled
          > process on a 5.1 cluster which will retrieve hundreds to thousands of
          > database rows from a small group of Oracle tables and then submit them
          > into a legacy system for processing. The problems we face are:
          > 1. We cannot have duplicate data submitted from startup classes on
          > different servers in the cluster
          > 2. We need the process to run if even only one machine in the cluster is
          > available and therefore do not want to tie the process to a single
          > machine
          > 3. We would prefer to distribute the workload across all servers
          > currently available in the cluster, but this is not mandatory.
          >
          > One solution is to retrieve each record as an Entity bean, attempting to
          > update it to "in process" and rejecting any failures thus utilizing
          > database locking, but due to the large number of records being processed
          > this is much too resource intensive as well as time consuming.
          >
          > We have looked into JMS based solutions, but it appears that JMS under
          > 5.1 is tied to a specific server (failing case 2).
          >
          > One acceptable approach that we have yet to find a way of implementing
          > is to have a "singleton" session bean, only one of which exists on the
          > cluster (though it may exist anywhere on the cluster). I have run
          > across a number of other applications for just this sort of EJB, but is
          > it possible to implement?
          >
          > Sadly, Weblogic 6.0 cannot be part of the solution as our company will
          > not be adopting it until well after this project's delivery date.
          >
          > Are we missing something obvious?
          > Many thanks!
          > -Steve
          >

Jaas.jar conflict in Weblogic 6.1 cluster

Similar Messages

Maybe you are looking for