Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Client-side DataSource cannot connect to server

17 views
Skip to first unread message

Sree Bodapati

unread,
Aug 2, 2002, 12:10:50 PM8/2/02
to
Huum... Try using the ip address of the server instead of localhost.

"Niels" <bebo...@yahoo.com> wrote in message
news:3d49...@newsgroups.bea.com...
>
> Hi,
>
> I'm having a problem connecting to the weblogic server from a client
running on
> the same machine. The test client is attached and basically follows the
code
> that weblogic provides in their tutorial on jdbc/jndi/DataSource. It's
complaining
> about "empty server reply" and "No available router to destination". The
full
> stack trace is below. The connection pools don't seem to be the issue
because
> I also ran against the exampleServer and had the same issue. Is it
possible there
> is a machine configuration issue?
>
> Thanks,
>
> Niels
>
> <Aug 1, 2002 7:15:48 PM EDT> <Info> <ConnectionManager> <Bootstrap unable
to get
> a direct: 'Protocol: 't3''connection to:
'0S:127.0.0.1:[7011,-1,-1,-1,-1,-1,-1]'
> on port: '7011'
>
> java.rmi.ConnectException: Destination unreachable; nested exception is:
> java.io.IOException: Empty server reply
>
> java.io.IOException: Empty server reply
>
> at weblogic.rjvm.t3.T3JVMConnection.connect(T3JVMConnection.java:102)
>
> at
weblogic.rjvm.t3.T3JVMConnection.createConnection(T3JVMConnection.java:148)
>
> at weblogic.rjvm.Protocol.createConnection(Protocol.java:201)
>
> at
weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.jav
a:1077)
>
> at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:365)
>
> at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
>
> at
weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
>
> at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
>
> at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
>
> at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
>
> at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
>
> at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
textFactoryDelegate.java:235)
>
> at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
textFactoryDelegate.java:176)
>
> at
weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
ory.java:123)
>
> at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
>
> at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
>
> at javax.naming.InitialContext.init(InitialContext.java:222)
>
> at javax.naming.InitialContext.<init>(InitialContext.java:198)
>
> at
com.picot.persistent.TestWeblogicDriver.getDataSource(TestWeblogicDriver.jav
a:75)
>
> at
com.picot.persistent.TestWeblogicDriver.main(TestWeblogicDriver.java:23)
>
> >
>
> <Aug 1, 2002 7:15:48 PM EDT> <Info> <ConnectionManager> <Bootstrap unable
to get
> a routed: 'Protocol: 't3'' connection to:
'0S:127.0.0.1:[7011,-1,-1,-1,-1,-1,-1]'
> on port: '7011'
>
> java.rmi.ConnectException: No available router to destination
>
> at
weblogic.rjvm.ConnectionManager.findOrCreateRouter(ConnectionManager.java:11
67)
>
> at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:378)
>
> at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
>
> at
weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
>
> at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
>
> at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
>
> at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
>
> at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
>
> at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
textFactoryDelegate.java:235)
>
> at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
textFactoryDelegate.java:176)
>
> at
weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
ory.java:123)
>
> at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
>
> at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
>
> at javax.naming.InitialContext.init(InitialContext.java:222)
>
> at javax.naming.InitialContext.<init>(InitialContext.java:198)
>
> at
com.picot.persistent.TestWeblogicDriver.getDataSource(TestWeblogicDriver.jav
a:75)
>
> at
com.picot.persistent.TestWeblogicDriver.main(TestWeblogicDriver.java:23)
>
> >
>


Niels

unread,
Aug 2, 2002, 5:30:55 PM8/2/02
to

Turns out the javax jars were mixed up. Perhaps a problem with the JBuilder package.
Switching to weblogic's jdk fixed it.
0 new messages