Exception while creating the initial context for the lookup to an external weblogic server
Herwig
I have the following problem - hopefully there is anyone who can help
me.
We develop an application, using weblogic 5.1, sp11, j2se 1.3. One
(little) feature of this application is the possibility to "print" the
data you actually working with. Therefore we have to use a special
Print-Server, witch is also a weblogic-server. This server generates a
pdf-File witch the user can print from word. Not nice - but we have to
do it like this.
To connect to this server, we just have to make a lookup to the
print-server and call than a special method, but unfortunately at
creating the initial context I got already an exception. At the same
time, also the print-server logs an exception.
Important note: All works fine, when I try to connect from an
testprogramm, which don't run within a weblogic server. So maybe, the
both weblogic servers don't like each other - environment problem or
something else(?).
The sourcecode, where the exceptin occurs looks like this:
----
Properties props = new Properties();
props.put(Context.PROVIDER_URL, sServer);
// sServer is like t3://172.72.72.72:7001
props.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
Context context = null;
try{
context = new InitialContext(props); //--> the exception occurs
here!
}
catch( NamingException ne ){
ne.printStackTrace();
}
ICOModTA ComodTA = null;
try {
ComodTA = (ICOModTA)context.lookup("weblogic.rmi." + sLookupName);
} catch ( Exception ne) { ne.printStackTrace();
}
-----
And this javax.naming.CommunicationException occurs at my server:
----
Fr Apr 26 15:59:15 CEST 2002:<I> <RJVM> Signaling peer
2823042936492895001S172.17.71.194:[7001,7001,7002,7002,7001,-1]
gone: weblogic.rjvm.PeerGoneException:
- with nested exception:
[java.io.EOFException]
javax.naming.CommunicationException. Root exception is
java.io.EOFException
at weblogic.socket.JVMSocketT3.endOfStream(JVMSocketT3.java:549)
at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:237)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
--------------- nested within: ------------------
weblogic.rjvm.PeerGoneException:
- with nested exception:
[java.io.EOFException]
at weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.java:76)
at weblogic.jndi.internal.RemoteContextFactoryImpl_WLStub.getContext(RemoteContextFactoryImpl_WLStub.java:95)
at weblogic.jndi.WLInitialContextFactoryDelegate.newRemoteContext(WLInitialContextFactoryDelegate.java:316)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:242)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:205)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:148)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.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 de.hvb.wk.ba.common.print.WkBaPdfGeneratorBean.generateDocument(WkBaPdfGeneratorBean.java:720)
at de.hvb.wk.ba.common.print.WkBaPdfGeneratorBean.generateFormWithList(WkBaPdfGeneratorBean.java:662)
at de.hvb.wk.ba.common.print.WkBaPdfGeneratorBeanEOImpl.generateFormWithList(WkBaPdfGeneratorBeanEOImpl.java:219
)
...
----
And the Exception that occurs at the print-server is the following:
----
Mi Okt 02 13:48:09 GMT+02:00 2002:<E> <NT Performance Pack> failure in
processSockets() loop: GetData: fd=820 numBytes=528
java.io.InvalidClassException:
weblogic.security.acl.internal.AuthenticatedUser; Local class not
compatible
at java/io/ObjectStreamClass.setClass
at java/io/ObjectInputStream.readClassDescriptor
at java/io/ObjectInputStream.readNewObject
at java/io/ObjectInputStream.readObject
at weblogic/socket/JVMAbbrevSocket.readMsgAbbrevs
at weblogic/rjvm/MsgAbbrevInputStream.prime
at weblogic/rjvm/RJVMImpl.dispatch
at weblogic/rjvm/ConnectionManagerServer.handleRJVM
at weblogic/rjvm/ConnectionManager.dispatch
at weblogic/socket/JVMAbbrevSocket.dispatch
at weblogic/socket/JVMSocketT3.dispatch
at weblogic/socket/NTSocketMuxer.processSockets
at weblogic/socket/SocketReaderRequest.execute
at weblogic/kernel/ExecuteThread.run
--------------- nested within: ------------------
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
creating response stream ] - with nested exception:
[java.io.InvalidClassException:
weblogic.security.acl.internal.AuthenticatedUser; Local class not
compatible]
at weblogic/socket/JVMAbbrevSocket.readMsgAbbrevs
at weblogic/rjvm/MsgAbbrevInputStream.prime
at weblogic/rjvm/RJVMImpl.dispatch
at weblogic/rjvm/ConnectionManagerServer.handleRJVM
at weblogic/rjvm/ConnectionManager.dispatch
at weblogic/socket/JVMAbbrevSocket.dispatch
at weblogic/socket/JVMSocketT3.dispatch
at weblogic/socket/NTSocketMuxer.processSockets
at weblogic/socket/SocketReaderRequest.execute
at weblogic/kernel/ExecuteThread.run
----
I would appreciate any help!
Thanx!
Herwig
Rob Woollen
-- Rob
Herwig
well - finally I got some more information about this strange
print-server. My server uses SP11, this print-server runs also
weblogic 5.1 but no SP I think. However - the problem is, that they
use some M$-com classes, and therefore they have to start the server
with jview and not java. So there are conflicts between the used
classes. Further - they use not EJB's. Our lookup refers to a startup
class.
I got this information yesterday and so the problem is not my problem
anymore. ;-) The developer team around this print server have to solve
it. :)
Despite - thnx.
--Herwig
Rob Woollen <rwoo...@nomail.org> wrote in message news:<3da3...@newsgroups.bea.com>...