| Author |
Message
|
| messg_wb |
 Posted: Thu Sep 29, 2005 10:22 am Post subject: Unable to start JDBC connector |
 |
|
Acolyte
Joined: 29 Sep 2005
Posts: 51
|
I am trying to start JDBC connector and I keep getting below error (appended at end) in the connector log. Broker type is WMQI but not ICS and start command is "C:\IBM\WebSphereAdapters\connectors\JDBC>start_JDBC JDBC BROKERWBI -cC:\mqsiconnectors\JDBCConnector.cfg".
(db2jdbc.dll is in correct path)
I tested the connector using "visual test connector" and it works perfectly, i mean it starts with no errors. Did anyone of you encountered such problem.
Thanks,
- Mohan
--------
[Version:4.3.0.0][TZ:America/New_York]
[Time: 2005/09/29 14:11:02.247] [System: ConnectorAgent] [SS: JDBCConnector] [Thread: wbia_main (#11618991)] [Type: Info] [MsgID: 17000] [Mesg: Initialization started. Name: JDBCConnector. ConfigFileName: C:\mqsiconnectors\JDBCConnector.cfg. Implementation DLL/Class Name: com.crossworlds.connectors.JDBC.JDBCConnectorAgent.class.]
[Time: 2005/09/29 14:11:02.257] [System: Server] [Thread: wbia_main (#11618991)] [Mesg: Privacy is NOT initialized. Reason: The privacy is NOT turned on.]
[Version:4.3.0.0][TZ:America/New_York]
[Time: 2005/09/29 14:11:04.390] [System: ConnectorAgent] [SS: JDBCConnector] [Thread: wbia_main (#11618991)] [Type: Trace] [MsgID: 17016] [Mesg: Initializing connector JDBCConnector, Version = 2.6.0, Connector Framework version = 4.3.0, CDK version = 4.3.0.]
[Time: 2005/09/29 14:11:04.400] [System: ConnectorAgent] [SS: JDBCConnector] [Thread: wbia_main (#11618991)] [Type: Error] [MsgID: 33018] [Mesg: Setting TimingStats to default.]
[Time: 2005/09/29 14:11:04.410] [System: ConnectorAgent] [SS: JDBCConnector] [Thread: wbia_main (#11618991)] [Type: Internal Warning] [MsgID: 33027] [Mesg: Setting PreparedStatementCacheSize to default.]
[Time: 2005/09/29 14:11:04.430] [System: ConnectorAgent] [SS: JDBCConnector] [Thread: wbia_main (#11618991)] [Type: Error] [MsgID: 17109] [Mesg: Exception caught in the method BusObjJavaInterface::init. Reason: java.util.NoSuchElementException]
[Time: 2005/09/29 14:11:04.430] [System: ConnectorAgent] [SS: JDBCConnector] [Thread: wbia_main (#11618991)] [Type: Fatal Error] [MsgID: 17050] [Mesg: The call to method init() in the application connector failed.]
[Time: 2005/09/29 14:11:04.430] [System: ConnectorAgent] [SS: JDBCConnector] [Thread: wbia_main (#11618991)] [Type: Info] [MsgID: 17514] [Mesg: About to begin restart retry # 1 for serial connector agent JDBCConnector.]
[Time: 2005/09/29 14:11:04.440] [System: ConnectorAgent] [SS: JDBCConnector] [Thread: wbia_main (#11618991)] [Type: Info] [MsgID: 17516] [Mesg: Waiting for configured restart retry interval: 1 minute(s) before restarting connector agent JDBCConnector.]
------------ |
|
| Back to top |
|
 |
| djeripo |
| Posted: Thu Sep 29, 2005 12:31 pm Post subject: |
|
|
Master
Joined: 25 Jan 2004
Posts: 225
|
Did you specify the businessobjects path in the property RepositoryDirectory?
Did you have the same BusinessObjects under SupportedBusinessObjects tab with the corresponding values of MessageSetId's? |
|
| Back to top |
|
|
| messg_wb |
| Posted: Thu Sep 29, 2005 1:45 pm Post subject: |
|
|
Acolyte
Joined: 29 Sep 2005
Posts: 51
|
| Yeah.. I have mentioned the repository directory correctly, also bussiness object and message ID's correlate.. |
|
| Back to top |
|
|
| hopsala |
| Posted: Thu Sep 29, 2005 5:57 pm Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
| did you raise connector and agent trace level to 5? |
|
| Back to top |
|
|
| messg_wb |
| Posted: Fri Sep 30, 2005 7:28 am Post subject: |
|
|
Acolyte
Joined: 29 Sep 2005
Posts: 51
|
| Yes, I have set trace level at 5 |
|
| Back to top |
|
|
| hopsala |
| Posted: Fri Sep 30, 2005 12:16 pm Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
from "BusObjJavaInterface" and "NoSuchElementException" I deduce some problem with the specific buisness object you subscribed, I would advise that you try working with a much simpler buisness object (just some sample with one or two fields) and see what happens. But I admit, this is guesswork, i've never encountered such an error.
This may sound odd, but since the JDBC adapter has a tendency towards highly obscure error messages, I found it quite helpful to open the adapter code to see what happened; simply use JAD to retrieve the source code from the class files. This is a last resort, but with the Adapter framework, last resort measures are reached pretty fast... |
|
| Back to top |
|
|
| djeripo |
| Posted: Fri Sep 30, 2005 7:55 pm Post subject: |
|
|
Master
Joined: 25 Jan 2004
Posts: 225
|
| Post your JDBCAdapter config file here. |
|
| Back to top |
|
|
| messg_wb |
| Posted: Sat Oct 01, 2005 11:36 am Post subject: |
|
|
Acolyte
Joined: 29 Sep 2005
Posts: 51
|
| Thanks guys, Its been reolved. I replaced odbc driver with db2 driver and it worked.. |
|
| Back to top |
|
|
|
|
