Hi,
We got problem with the JDBC adapter while inserting a huge String into a CLOB.
Error: (17002) Io exception: End of TNS data channel.
For Strings which are not that huge in size are inserted fine.
Environment used:
webMethods Integration Server
Version: 6.5
Updates: IS_6-5_SP2_SrvPrtcl_Fix1, IS_6-5_SP2_WebSvcsXML_Fix2, IS_6-5_SP2’, TNS_6- 5_Fix10, TNS_6-5_Fix11, TNS_6-5_Fix15 and WmPRT_6-5-1_Fix1
Java Version: 1.4.2_11 (48.0)
Java Vendor: Sun Microsystems Inc.

WmJDBCAdapter
Version: 6.0.3.1
Patches Included: None

ORACLE
Version: 8.1.7.4.1
Please let me know if anyone has faced this issue earlier.

Thanks,
VJ.

This is just a guess but maybe it will be helpful…

There are size limits imposed by the JDBC driver and possibly the DB, though I’m not certain what they are (depends on version, I think). You’ll want to find out what the upper limit is to see if the string is exceeding that.

Thanks for the reply.

As we are using ORACLE JDBC Thin Driver, the adapter should be able to support up to 4MB.

But the system was failing when we were trying to insert data less than 4KB.

We have the following jars available in the classpath:

D:\j2sdk1.4.2_11\lib\rt.jar
D:\j2sdk1.4.2_11\lib\i18n.jar
D:\webMethods65\IntegrationServer\lib\proxy.jar
D:\webMethods65\IntegrationServer\updates\IS_6-5_SP2_SrvPrtcl_Fix1.jar
D:\webMethods65\IntegrationServer\updates\IS_6-5_SP2_WebSvcsXML_Fix2.jar
D:\webMethods65\IntegrationServer\updates\IS_6-5_SP2.jar
D:\webMethods65\IntegrationServer\updates\TNS_6-5_Fix10.jar
D:\webMethods65\IntegrationServer\updates\TNS_6-5_Fix11.jar
D:\webMethods65\IntegrationServer\updates\TNS_6-5_Fix15.jar
D:\webMethods65\IntegrationServer\updates\WmPRT_6-5-1_Fix1.jar
[FONT=Verdana]D:\webMethods65\IntegrationServer\lib\classes[/font]
D:\webMethods65\IntegrationServer\lib\server.jar
D:\webMethods65\IntegrationServer\lib\client.jar
D:\webMethods65\IntegrationServer\lib\mail.jar
D:\webMethods65\common\lib\wmbrokerclient.jar
D:\webMethods65\common\lib\wmjmsclient.jar
D:\webMethods65\common\lib\jms.jar
D:\webMethods65\IntegrationServer\lib\entrust\enttoolkit.jar
D:\webMethods65\IntegrationServer\lib\jars\converters.jar
D:\webMethods65\IntegrationServer\lib\jars\msbase.jar
D:\webMethods65\IntegrationServer\lib\jars\mssqlserver.jar
D:\webMethods65\IntegrationServer\lib\jars\msutil.jar
D:\webMethods65\IntegrationServer\lib\jars\ojdbc14.zip
D:\webMethods65\IntegrationServer\lib\jars\resolver.jar
D:\webMethods65\IntegrationServer\lib\jars\sl53_cj36.jar
D:\webMethods65\IntegrationServer\lib\jars\srp.jar
D:\webMethods65\IntegrationServer\lib\jars\TNS_6-5_Fix6.jar
D:\webMethods65\IntegrationServer\lib\jars\Una2000.jar
D:\webMethods65\IntegrationServer\lib\jars\xercesImpl.jar
D:\webMethods65\IntegrationServer\lib\jars\xml-apis.jar
D:\webMethods65\IntegrationServer\lib\jars\xmlParserAPIs.jar
D:\webMethods65\IntegrationServer\packages\SAP\code\jars\static\jARM.jar
D:\webMethods65\IntegrationServer\packages\SAP\code\jars\static\jCO.jar
D:\webMethods65\IntegrationServer\packages\SAP\code\jars\static\sapjco.jar
D:\webMethods65\IntegrationServer\packages\WmART\code\jars\static\wmartbundle.jar
D:\webMethods65\IntegrationServer\packages\WmDeployer\code\jars\static\axis.jar
D:\webMethods65\IntegrationServer\packages\WmDeployer\code\jars\static\commons-discovery.jar
D:\webMethods65\IntegrationServer\packages\WmDeployer\code\jars\static\commons-logging.jar
D:\webMethods65\IntegrationServer\packages\WmDeployer\code\jars\static\jaxrpc.jar
D:\webMethods65\IntegrationServer\packages\WmDeployer\code\jars\static\saaj.jar
D:\webMethods65\IntegrationServer\packages\WmFlatFile\code\jars\static\ffcore.jar
D:\webMethods65\IntegrationServer\packages\WmIPRoot\code\jars\static\WmIPRoot.jar
D:\webMethods65\IntegrationServer\packages\WmMonitor\code\jars\static\mIcons.zip
D:\webMethods65\IntegrationServer\packages\WmPRT\code\jars\static\1jxpathpatch.jar
D:\webMethods65\IntegrationServer\packages\WmPRT\code\jars\static\castor-0.9.5.2.jar
D:\webMethods65\IntegrationServer\packages\WmPRT\code\jars\static\commons-jxpath-1.1.jar
D:\webMethods65\IntegrationServer\packages\WmPRT\code\jars\static\jwsdl-1.0.jar
D:\webMethods65\IntegrationServer\packages\WmPRT\code\jars\static\wmprt.jar
D:\webMethods65\IntegrationServer\packages\WmRNIF11TRP\code\jars\static\WmRNIF11TRP.jar
D:\webMethods65\IntegrationServer\packages\WmTN\code\jars\static\tncore.jar



From the above jars/zip I think the adapter uses the java classes from ojdbc14.zip

As per the ORACLE JDBC Thin drivers documentation it is mentioned that ojdbc14.jar can be used with JDK 1.4 & 1.5 and classes12.jar can be used with JDK 1.2 and JDK 1.3

Since we are using Java version 1.4.2_11, I think we are using the right jar.

I was able to get a temporary fix to this insert problem by adding classes12.jar to classpath.

After adding classes12.jar to the classpath I able to insert all the huge Strings into CLOB that failed earlier.

Can anyone brief me the reason behind this\correct me if I am wrong and provide me the permanent solution?

Thanks,
VJ.

The ojdbc14.zip file would be the right one to use for the 1.4 JVM.

By changing to use the classes12.jar, you effectively changed JDBC drivers.

I would suggest opening a service request with wM tech support to figure out what might be amiss.

There is limitation of 4KB for CLOB when using JDBC thin drivers, to avoid that you should go for oci drivers. Actually this is documented in the jdbc user guide as well page 14.

Didn’t they say the data that was failing was less than 4k?

VJ,

what is the exact size of the CLOB?

reamon,

Just trying to correct the typo above that the limit is 4 MB.