E1: JAVA: JDE Dynamic Java Connector doesn't JITI correctly and failing to insert into F989999
(Doc ID 1576792.1)
Last updated on JANUARY 09, 2023
Applies to:
JD Edwards EnterpriseOne Tools - Version 9.1 and laterInformation in this document applies to any platform.
Symptoms
Unable to run the Java Connector Sample Successfully. JITI splash window comes up but it disappears right away and exits the application.
Error in the e1root.log:
---------
02 Aug 2013 12:29:17,048 [APP ] - [JDBJ] INSERT INTO DV900.F989999(WBJPO,WBUID,WBOID,WBLNGPREF,WBJVER) VALUES (?,?,?,?,?)
02 Aug 2013 12:29:17,048 [APP ] - [JDBJ] SQL statement parameter marker values are :
02 Aug 2013 12:29:17,064 [SEVERE] - [JDBJ] SQLException occured in the SQLPhysicalConnection.insert(): | Vendor code = 17068, SQL state = null | Table or View Name = F989999 | Data Source = Central Objects - DV900 java.sql.SQLException: Invalid argument(s) in call
02 Aug 2013 12:29:17,048 [APP ] - [JDBJ] INSERT INTO DV900.F989999(WBJPO,WBUID,WBOID,WBLNGPREF,WBJVER) VALUES (?,?,?,?,?)
02 Aug 2013 12:29:17,048 [APP ] - [JDBJ] SQL statement parameter marker values are :
02 Aug 2013 12:29:17,064 [SEVERE] - [JDBJ] SQLException occured in the SQLPhysicalConnection.insert(): | Vendor code = 17068, SQL state = null | Table or View Name = F989999 | Data Source = Central Objects - DV900 java.sql.SQLException: Invalid argument(s) in call
02 Aug 2013 12:29:17,064 [DEBUG ] - [JDBJ] Analyzing exception: sql state = null, vendor code = 17068, error message = Invalid argument(s) in call, indicates lost connect = false.
02 Aug 2013 12:29:17,079 [SEVERE] - [BASE] com.jdedwards.database.base.JDBException: [SQL_EXCEPTION_OCCURRED] An SQL exception occurred: Invalid argument(s) in call. java.sql.SQLException: Invalid argument(s) in call
02 Aug 2013 12:29:17,079 [SEVERE] - [BASE] com.jdedwards.database.base.JDBException: [SQL_EXCEPTION_OCCURRED] An SQL exception occurred: Invalid argument(s) in call. com.jdedwards.database.base.JDBException: [SQL_EXCEPTION_OCCURRED] An SQL exception occurred: Invalid argument(s) in call.
02 Aug 2013 12:29:17,079 [DEBUG ] - [JDBJ] Closing Prepared Statement
02 Aug 2013 12:29:17,079 [DEBUG ] - [JDBJ] Connection represented by poolKey e1dev_JDENP checked into pool - com.jdedwards.database.impl.physical.JDBPooledConnection@787c16
02 Aug 2013 12:29:17,079 [DEBUG ] - [JDBJ] Transaction 6 state changing from auto commit to closed.
02 Aug 2013 12:29:17,079 [SEVERE] - [BASE] com.jdedwards.base.spec.SpecException: [SQL_EXCEPTION_OCCURRED] An SQL exception occurred: COMPTBLE-F9862. com.jdedwards.database.base.JDBException: [SQL_EXCEPTION_OCCURRED] An SQL exception occurred: Invalid argument(s) in call.
02 Aug 2013 12:29:17,079 [SEVERE] - [BASE] com.jdedwards.base.spec.SpecException: [SQL_EXCEPTION_OCCURRED] An SQL exception occurred: COMPTBLE-F9862. com.jdedwards.base.spec.SpecException: [SQL_EXCEPTION_OCCURRED] An SQL exception occurred: COMPTBLE-F9862.
02 Aug 2013 12:29:17,079 [SEVERE] - [INTEROP] Fail to fetch ModuleInfo: [SQL_EXCEPTION_OCCURRED] An SQL exception occurred: Invalid argument(s) in call. com.jdedwards.system.connector.dynamic.spec.dbservices.BSFNLookupFailureException: Fail to fetch ModuleInfo: [SQL_EXCEPTION_OCCURRED] An SQL exception occurred: Invalid argument(s) in call.
02 Aug 2013 12:29:17,079 [SEVERE] - [INTEROP] Failed to get HAP (Host and Port) for BSFNMethod:GetEffectiveAddress com.jdedwards.system.connector.dynamic.spec.SpecFailureException: Failed to get HAP (Host and Port) for BSFNMethod:GetEffectiveAddress
Symptoms #2:
Some times it works and some times it doesn't work. For the Failed one, it looks for the key "COMPATBLE-F9862", but it doesn't have the "found key" statement.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |