I’ve deployed a tamino connection factory (v 4.1.1.1) in weblogic (6.1) and I can obtain and use a connection fine under most circumstances. However, under a heavy load, I get the following stack trace:

Nested Exception (com.softwareag.tamino.db.API.invocation.TCommunicationExceptio
n, tag: $Name: JavaTaminoAPI_2_1_0_39 $) stacktrace:

Nested Exception (java.lang.NullPointerException, tag: $Name: JavaTaminoAPI_2_1_
0_39 $) stacktrace:

java.lang.NullPointerException
at java.io.FilterInputStream.close(FilterInputStream.java:157)
at weblogic.xml.sax.XMLInputSource.setByteStream(XMLInputSource.java:583
)
at weblogic.xml.sax.XMLInputSource.(XMLInputSource.java:130)
at weblogic.xml.jaxp.RegistryDocumentBuilder.parse(RegistryDocumentBuild
er.java:130)
at com.softwareag.tamino.db.API.invocation.TAbstractInvocation.getDocume
nt(Unknown Source)
at com.softwareag.tamino.db.API.invocation.TAbstractInvocation.checkServ
erAvailabilityAndVersion(Unknown Source)
at com.softwareag.tamino.db.API.invocation.TInvocationFactory.initialize
(Unknown Source)
at com.softwareag.tamino.db.API.invocation.TInvocationFactory.newInvocat
ion(Unknown Source)
at com.softwareag.tamino.db.API.connection.TConnectionFactory.newConnect
ion(Unknown Source)
at com.softwareag.tamino.db.API.connector.spi.TaminoManagedConnection.<i
nit>(Unknown Source)
at com.softwareag.tamino.db.API.connector.spi.AbstractConnectionFactory.
createManagedConnection(Unknown Source)
at weblogic.connector.common.internal.ConnectionPool.makeResources(Conne
ctionPool.java:844)
at weblogic.connector.common.internal.ConnectionPool.getConnection(Conne
ctionPool.java:1505)
at weblogic.connector.common.internal.ConnectionPoolManager.getConnectio
n(ConnectionPoolManager.java:155)
at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConn
ection(ConnectionManagerImpl.java:20)
at com.softwareag.tamino.db.API.connector.TaminoDataSourceImpl.getConnec
tionHandle(Unknown Source)
at com.softwareag.tamino.db.API.connector.TaminoDataSourceImpl.getConnec
tion(Unknown Source)
at tem.fargo.ejb.tamino.TaminoStoreSB.saveRevision(TaminoStoreSB.java:14
9)

Actually the Tamino JCA released with Tamino 4.1.1.1 supports Weblogic 7.0
and there is also a weblogic class on the top of the stacktrace. So it seems to be difficult to handle this problem very fast.

1.
Could you try all this on Weblogic 7.0?

2.
If Weblogic 6.1 is required could you switch the trace on and send me the trace output.
You also have to open a new problem at Tamino Support Center.

We?ll have to find out if this problem is caused by Tamino or by WegLogic 6.1.
If Tamino causes the problem then com.softwareag.tamino.db.API.invocation.TAbstractInvocation.getDocument(Unknown Source)
fails because the Tamino DB answer is corrupt, otherwise the WebLogic XML parser implementation causes the problem.
Switching the trace on will show all activities including the Tamino responses.

To switch the tracing on edit the startWebLogic.cmd file. Look for the line where java is started and add ?-Dcom.softwareag.LoggingOn=true? like this:

“%JAVA_HOME%\bin\java” -hotspot -ms64m -mx64m -classpath %CLASSPATH% -Dcom.softwareag.LoggingOn=true ??

to filter the output use log4j.properties file in the front of the servers classpath.
Here is my log4j.properties file (trace all):
# -----------------------------------------------------------------------------
log4j.rootCategory=INFO, A1

log4j.appender.A1=org.apache.log4j.ConsoleAppender
log4j.appender.A1.File=System.out

# A1 uses PatternLayout.
log4j.appender.A1.layout=org.apache.log4j.PatternLayout

# The conversion pattern uses format specifiers. You might want to
# change the pattern an watch the output layout change.
# log4j.appender.A1.layout.ConversionPattern=%-4r %-5p [%t] %37c %3x - %m%n
log4j.appender.A1.layout.ConversionPattern=%p %t %c - %m%n
# -----------------------------------------------------------------------------