Weblogic Jndi tests need to be aware of problems

The use of WebLogic Jndi mainly refers to the WebLogic of Bo's proud and aloof Wolf. Use Summary (iii)--weblogic Configure the Jndi data source. Written in great detail, thank you for sharing. There are some problems in the process of the gourd painting, which is recorded here.

The WebLogic version is WebLogic Server version: 10.3.6.0,ide is MyEclipse 8.5.

Two problems were encountered during use.

1. Can I access the WebLogic deployed Jndi service using a web app deployed by Tomcat?

2. The problems that Web apps deployed with WebLogic have encountered while using Jndi to connect to the database.

The first problem, because there is no clear understanding of the past, so, in the course of testing, try to encounter a variety of problems.

1) JAVA.LANG.CLASSCASTEXCEPTION:WEBLOGIC.JDBC.COMMON.INTERNAL.CONNECTIONENV cannot is cast to java.io.Serializable

JAVA.LANG.CLASSCASTEXCEPTION:WEBLOGIC.JDBC.COMMON.INTERNAL.CONNECTIONENV cannot is cast to java.io.Serializable
At Weblogic.iiop.IIOPOutputStream.writeObject (iiopoutputstream.java:2266)
At Weblogic.utils.io.ObjectStreamClass.writeFields (objectstreamclass.java:414)
At Weblogic.corba.utils.ValueHandlerImpl.writeValueData (valuehandlerimpl.java:235)
At Weblogic.corba.utils.ValueHandlerImpl.writeValueData (valuehandlerimpl.java:225)
At Weblogic.corba.utils.ValueHandlerImpl.writeValue (valuehandlerimpl.java:182)
At Weblogic.iiop.IIOPOutputStream.write_value (iiopoutputstream.java:1963)
At Weblogic.iiop.IIOPOutputStream.write_value (iiopoutputstream.java:2001)
At Weblogic.iiop.IIOPOutputStream.writeObject (iiopoutputstream.java:2266)
At Weblogic.jdbc.common.internal.RmiDataSource_WLSkel.invoke (Unknown Source)
At Weblogic.rmi.internal.BasicServerRef.invoke (basicserverref.java:667)
At Weblogic.rmi.cluster.ClusterableServerRef.invoke (clusterableserverref.java:230)
At Weblogic.rmi.internal.basicserverref$1.run (basicserverref.java:522)
At Weblogic.security.acl.internal.AuthenticatedSubject.doAs (authenticatedsubject.java:363)
At Weblogic.security.service.SecurityManager.runAs (securitymanager.java:146)
At Weblogic.rmi.internal.BasicServerRef.handleRequest (basicserverref.java:518)
At Weblogic.rmi.internal.wls.WLSExecuteRequest.run (wlsexecuterequest.java:118)
At Weblogic.work.ExecuteThread.execute (executethread.java:256)
At Weblogic.work.ExecuteThread.run (executethread.java:221)

In this case, there are statements on the Internet, and other questions will be reported after the attempt.

It is not possible to solve the problem by introducing the path to the location of Weblogic.jar in Classpath.

Back and forth, in a variety of ways, the saying " Security-based, Tomcat-deployed services cannot get to serialized objects from Jndi in WebLogic deployment " has some reason.

So, we turned to a web app deployed with WebLogic to test the Jndi data source for the WebLogic deployment.

The following is a second scenario: the problems that WebLogic deployed Web apps encounter while using Jndi to connect to the database.

It is not possible to determine which jars need to be referenced in previous attempts. So there are all sorts of problems.

The main problems are:

Error creating Bean with Name ' Weblogic.wsee.jaxws.client.async.AsyncTransportProvider '

Start trying to get all the jars from the WebLogic server Lib to the Web Lib deployment, or add or subtract some jars for testing, and there will still be a variety of problems.

As you can see from https://community.oracle.com/thread/2451478?tstart=0, this may be a flaw in WebLogic, or a "feature", because it's normal for you to put a bug in your jar and make a mistake.

• 2. re: Weblogic.wsee.jaxws.client.async.AsyncTransportProvider 967067  2012-10-9 2:34   (reply 967067) What is means?
  It is WebLogic bug?
  Where has the Solve method?
  • < Span class= "j-social-action" > favorite   show 0 Likes (0)
  • operation  
• 3. re: Weblogic.wsee.jaxws.client.async.AsyncTransportProvider Kalyan pasupuleti-oracle  2012-10-10 pm 4:32  (reply 967067) Yes plz check this BUG from MOS.
  • < Span class= "j-social-action" > favorite   show 1 likes (1)
  • operation  
• 4. Re:weblogic.wsee.jaxws.client.async.AsyncTransportProviderRaghu honawad-oracle 2012-11-27 Morning 7:10 (reply 967067)Hi,
  
  See if you have all of the following jars Weblogic.jar and Wlfullclint.jar in your Build Path i.e. deployment Pro File. Remove them, it should fix the issue.
  
  Regards,
  Raghu Honawad

Therefore, I will classpath all the weblogic of the jar cleared, Web-inf lib only reserved Wlclient.jar.

In this way, the WebLogic deployed Web app starts normally, and access Jndi is successful.

Can I access the Jndi service for WebLogic deployment using a web app deployed by Tomcat?

This question, if any warrior knows, kindly advise.

Weblogic Jndi tests need to be aware of problems