We have not yet resolved the problem. We have opened support requests with both Bea and Software AG (reference #547178).
We also experience two other problems that may be related to this issue:
1. ViolatedPrecondition. Occasionally we see the following stack trace, typically after a garbage collect:
<AF[729]: Allocation Failure. need 760 bytes, 183322 ms since last AF>
<AF[729]: managing allocation failure, action=1 (0/1070594560) (3145728/3145728)>
<GC(729): GC cycle started Sun Jul 4 11:05:11 2004
<GC(729): freed 1011229320 bytes, 94% free (1014375048/1073740288), in 110 ms>
<GC(729): mark: 92 ms, sweep: 18 ms, compact: 0 ms>
<GC(729): refs: soft 0 (age >= 32), weak 5, final 3661, phantom 0>
<AF[729]: completed in 112 ms>
WARNING: ViolatedPrecondition detected. Treating is like a document lock exception to allow retry.
com.softwareag.common.instrumentation.contract.ViolatedPrecondition: Violated Precondition: Connection handle is invalid!
at com.softwareag.common.instrumentation.contract.Precondition.check(Unknown Source)(Inlined Compiled Code)
at com.softwareag.tamino.db.API.connector.spi.TConnectionWrapper.newStreamAccessor(Unknown Source)(Compiled Code)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java(Compiled Code))
at $Proxy112.newStreamAccessor(Unknown Source)(Compiled Code)
at nl.schiphol.ciss.database.access.AbstractTaminoAccessor.getStreamAccessor(Unknown Source)(Compiled Code)
at nl.schiphol.ciss.database.access.AbstractTaminoAccessor.readLockedDocument(Unknown Source)(Compiled Code)
at nl.schiphol.ciss.logic.flight.flt.FltAccessor.getLockedFltByCompletelyReasoneableArguments(Unknown Source)(Inlined Compiled Code)
at nl.schiphol.ciss.logic.flight.flt.FltAccessor.updateFlight(Unknown Source)(Compiled Code)
at nl.schiphol.ciss.logic.flight.session.FlightBean.updateFlight(Unknown Source)(Compiled Code)
at nl.schiphol.ciss.logic.flight.session.FlightBean_yugk9c_EOImpl.updateFlight(FlightBean_yugk9c_EOImpl.java(Compiled Code))
at nl.schiphol.ciss.jms.consumer.invokers.FlightInvoker.invoke(Unknown Source)(Compiled Code)
at nl.schiphol.ciss.jms.consumer.invokers.Invoker.process(Unknown Source)(Compiled Code)
at nl.schiphol.ciss.jms.consumer.beans.MessageProcessorBean.processMessage(Unknown Source)(Compiled Code)
at nl.schiphol.ciss.jms.consumer.beans.MessageProcessorBean_mlbwx7_EOImpl.processMessage(MessageProcessorBean_mlbwx7_EOImpl.java(Compiled Code))
at nl.schiphol.ciss.jms.consumer.beans.MessageConsumerBean.onMessage(Unknown Source)(Compiled Code)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java(Compiled Code))
at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java(Compiled Code))
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java(Compiled Code))
at com.seebeyond.jms.client.STCMessageConsumer.onMessage(STCMessageConsumer.java(Compiled Code))
at com.seebeyond.jms.client.STCSession.onMessage(STCSession.java(Compiled Code))
at com.seebeyond.jms.sockets.ReceiverSocket.deliverMessage(ReceiverSocket.java(Compiled Code))
at com.seebeyond.jms.sockets.ThreadPerConnectionMgr$ConnThread.run(ThreadPerConnectionMgr.java(Compiled Code))
2. After the application has run for a while Weblogic is detecting a lot of connection leaks.
Are you also having these problems with your application?
Regards,
Sebastiaan
#API-Management#webMethods#webMethods-Tamino-XML-Server-APIs