StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POApplication using Pooled JDBC Connections
primarykey
Id
774018
data
AcceptedAnswerId
778175
AnswerCount
7
ClosedDate
CommentCount
6
CommunityOwnedDate
CreationDate
2009-04-21T18:44:20.100
FavoriteCount
0
LastActivityDate
2014-11-12T20:50:07.813
LastEditDate
2009-04-22T14:57:03.430
LastEditorUserId
11760
OwnerUserId
11760
ParentId
0
PostTypeId
1
Score
0
ViewCount
10068
LastEditorDisplayName
text
Body
I'm working with a legacy WebLogic application that contains a web-service application and a standalone, command-line application. Both need access to a common database and I would like to try and get the command-line application use a pooled connection to the web-server's JDBC connection. (The standalone application can only be run when the server is active and both will be run on the same physical machine.) I've been trying to use a JNDI lookup to the JDBC driver as follows: <pre><code>try { Context ctx = null; Hashtable ht = new Hashtable(); ht.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory"); ht.put(Context.PROVIDER_URL, "t3://localhost:7001"); ctx = new InitialContext(ht); DataSource ds = (DataSource) ctx.lookup ("dbOracle"); Connection conn = null; conn = ds.getConnection(); // <-- Exception raised here // conn = ds.getConnection(username, password); // (Also fails) // ... } catch (Exception e) { // Handle exception... } </code></pre> I've confirmed the JNDI name is correct. I am able to connect to the database with other web-applications but my standalone application continues to have difficulties. - I got the idea for this from a <a href="http://download.oracle.com/docs/cd/E12840_01/wls/docs103/jdbc/programming.html" rel="nofollow noreferrer">WebLogic app note</a>. Any ideas on what I have overlooked? EDIT 1.1: I'm seeing a "java.lang.ClassCastException: java.lang.Object" exception. EDIT 2: When I perform the following: <pre><code>Object dsObj = ctx.lookup("dbOracle"); System.out.println("Obj was: " + dsObj.getClass().getName()); </code></pre> In the standalone-application, it reports: <pre><code>"Obj was: weblogic.jdbc.common.internal._RemoteDataSource_Stub" </code></pre> I attempted to test the same chunk of code (described in original question) in the web-application and was able to connect to the datasource (i.e. it seems to "work"). This working test reports: <pre><code>"Obj was: weblogic.jdbc.common.internal.RmiDataSource" </code></pre> Also, here's a stack-trace for when it's failing: <pre><code>####<Apr 22, 2009 10:38:21 AM EDT> <Warning> <RMI> <mlbdev16> <cgServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1240411101452> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.jdbc.common.internal.RmiDataSource.getConnection() java.lang.ClassCastException: java.lang.Object. java.lang.ClassCastException: java.lang.Object at weblogic.iiop.IIOPOutputStream.writeAny(IIOPOutputStream.java:1584) at weblogic.iiop.IIOPOutputStream.writeObject(IIOPOutputStream.java:2222) at weblogic.utils.io.ObjectStreamClass.writeFields(ObjectStreamClass.java:413) 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:1957) at weblogic.iiop.IIOPOutputStream.write_value(IIOPOutputStream.java:1992) at weblogic.iiop.IIOPOutputStream.writeObject(IIOPOutputStream.java:2253) at weblogic.jdbc.common.internal.RmiDataSource_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589) at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:479) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:475) at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:59) at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:1016) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200) at weblogic.work.ExecuteThread.run(ExecuteThread.java:172) </code></pre>
Tags
<java><jdbc><weblogic><jndi>
Title
Application using Pooled JDBC Connections
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USNate
UserOwnerUserId
1. USNate
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POApplication using Pooled JDBC Connections
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTDownMod
2. VO
 singulars
 PostPostId
 POApplication using Pooled JDBC Connections
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.