Grupos de Google ya no admite publicaciones ni suscripciones nuevas de Usenet. El contenido anterior sigue visible.

Attempt to sendMsg using a closed connection

0 vistas
Ir al primer mensaje no leído

Alexandre Vauthey

no leída,
6 nov 2001, 5:37:49 p.m.6/11/01
para
I get the following exception from time to time. Once I get it, any
following ejb access attempt triggers the same error. I'm using weblogic
6.0SP2 on windows. This happens between a client java application and the
server. Any idea what is going wrong ?

Thanks, AlexV.

TestEjbEvent - begin
*** TEST UPDATE***
Attempting to create book DATA_INTEG_BOOK1
** ERROR ** Unable to create book : DATA_INTEG_BOOK1
Exception :
javax.naming.CommunicationException. Root exception is
java.rmi.ConnectException: Attempt to sendMsg using a closed connection
at weblogic.rjvm.ConnectionManager.sendMsg(ConnectionManager.java:429)
at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:419)
at
weblogic.rjvm.MsgAbbrevOutputStream.flushAndSendRaw(MsgAbbrevOutputStream.ja
va:114)
at
weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:
122)
at
weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:162)
at
weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java
:56)
at weblogic.security.acl.internal.Security.authenticate(Security.java:108)
at
weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFacto
ryDelegate.java:455)
at
weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFac
toryDelegate.java:289)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
textFactoryDelegate.java:261)
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
net.appl.jrisk.ejb.weblogic.WebLogicContext.getInitialContext(WebLogicContex
t.java:263)
at net.appl.jrisk.ejb.ServerContext.getContext(ServerContext.java:479)
at net.appl.jrisk.ejb.ServerContext.lookup(ServerContext.java:527)
at net.appl.jrisk.ejb.ejbAccessor.addHome(ejbAccessor.java:277)
at net.appl.jrisk.ejb.ejbAccessor.getHome(ejbAccessor.java:250)
at
net.appl.jrisk.ejb.archive.ejbArchiveableSourceHelper.createBean(ejbArchivea
bleSourceHelper.java:50)
at
net.appl.jrisk.ejb.ejbDataSourceHelper.create(ejbDataSourceHelper.java:190)
at
test.net.appl.jrisk.ejb.event.testEjbEvent.createBook(testEjbEvent.java:163)
at
test.net.appl.jrisk.ejb.event.testEjbEvent.testUpdate(testEjbEvent.java:99)
at test.net.appl.jrisk.ejb.event.testEjbEvent.test(testEjbEvent.java:83)
at test.util.JRiskTestCase.doTest(JRiskTestCase.java:125)
at test.util.TestRun.executeTests(TestRun.java:621)
at test.util.TestRun.testDirectories(TestRun.java:749)
at test.util.TestRun.testPath(TestRun.java:776)
at test.util.TestRun.testDirectories(TestRun.java:746)
at test.util.TestRun.testPath(TestRun.java:776)
at test.util.TestRun.testDirectories(TestRun.java:746)
at test.util.TestRun.testPath(TestRun.java:776)
at test.util.TestRun.testDirectories(TestRun.java:746)
at test.util.TestRun.testPath(TestRun.java:776)
at test.util.TestRun.testDirectories(TestRun.java:746)
at test.util.TestRun.testPath(TestRun.java:776)
at test.util.TestRun.testDirectories(TestRun.java:746)
at test.util.TestRun.test(TestRun.java:386)
at test.util.TestRun.run(TestRun.java:149)
at test.util.TestRun.main(TestRun.java:109)

--
Alexandre Vauthey
Software Engineer
Application Networks
444 Ramona street
Palo Alto, CA 94301


Ed Hager

no leída,
20 nov 2001, 6:44:19 p.m.20/11/01
para
I sent an e-mail message to Alex asking if he found a solution and
here is his response. It helped solve my problem:

Hi Ed,

The problem went away when we disabled native IOs in our config.xml
(NativeIOEnabled="false" in server tag).

BEA does not seem to know what's going on yet.

Hope this helps. Rgrds, Alex.

"Alexandre Vauthey" <alexandr...@appl.net> wrote in message news:<3be8...@newsgroups.bea.com>...

0 mensajes nuevos