| Author |
Message
|
| keenlearner |
 Posted: Wed Jan 25, 2012 8:38 am Post subject: JDBC Connection in JCN |
 |
|
Acolyte
Joined: 24 Aug 2006
Posts: 62
|
Hi All
Env
MB7 with fix pack level 2. Windows XP with SP3
I am trying to connect to a DB but getting an error as below. Any pointers what can be the issue. I am not using the XA
| Code: |
Text:CHARACTER:Node throwing exception
RecoverableException
File:CHARACTER:F:\build\S700_P\src\DataFlowEngine\PluginInterface\ImbJniNode.cpp
Line:INTEGER:1179
Function:CHARACTER:ImbJniNode::evaluate
Type:CHARACTER:ComIbmJavaComputeNode
Name:CHARACTER:com/deere/jdc/jdrpintegration/continuousroll/StoreLog#FCMComposite_1_5
Label:CHARACTER:com.deere.jdc.jdrpintegration.continuousroll.StoreLog.Java Compute
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Caught exception and rethrowing
RecoverableException
File:CHARACTER:JDBCType4SinglePhaseTrxnHandlerErrors.java
Line:INTEGER:209
Function:CHARACTER:JDBCType4SinglePhaseTrxnHandler::getConnection
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:6233
Text:CHARACTER:Problem obtaining Transaction Resource
Insert
Type:INTEGER:5
Text:CHARACTER:Java Compute
Insert
Type:INTEGER:5
Text:CHARACTER:jdbc:db2://server name:port/dbname:user=myuser;password=xxxxxxxx;
|
|
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Jan 25, 2012 8:53 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Have you edited the URL connection format to include the proper values for your site?
If so, that's why it's not working.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Jan 25, 2012 8:55 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Also, try mqsicvp to verify that the conx is at least good from ODBC point of view. If ODBC has same issue, you've identified the fact that its outside of the WMB runtime.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| keenlearner |
| Posted: Wed Jan 25, 2012 9:12 am Post subject: |
|
|
Acolyte
Joined: 24 Aug 2006
Posts: 62
|
@lance : I have verified the connections from ODBC point of view. We have an existing flow which uses ODBC conenction to the same DB and its connecting the DB successfully.
@Vitor : I am using the deafult URL pattern for Universal DB2 driver. The URL pattern for my Db 2 driver is
| Code: |
| jdbc:db2://[serverName]:[portNumber]/[databaseName]:user=[user];password=[password]; |
Thanks |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jan 25, 2012 9:18 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Did you read the support statements in the InfoCenter about type4JDBCConnections and XA? |
|
| Back to top |
|
|
| keenlearner |
| Posted: Wed Jan 25, 2012 10:48 am Post subject: |
|
|
Acolyte
Joined: 24 Aug 2006
Posts: 62
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jan 25, 2012 12:48 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It is optional, unless you want to use global transactions, in which case it's required. So if you're *positive* that you have not turned on global transactions on your flow, then you can ignore this.
You didn't post the full exception text, though, so it's hard to tell what the reason for the failure is. |
|
| Back to top |
|
|
| keenlearner |
| Posted: Thu Jan 26, 2012 2:04 pm Post subject: |
|
|
Acolyte
Joined: 24 Aug 2006
Posts: 62
|
Here goes the full exception Tree
| Code: |
ExceptionList
RecoverableException
File:CHARACTER:F:\build\S700_P\src\DataFlowEngine\ImbDataFlowNode.cpp
Line:INTEGER:1073
Function:CHARACTER:ImbDataFlowNode::createExceptionList
Type:CHARACTER:ComIbmMQInputNode
Name:CHARACTER:com/deere/jdc/jdrpintegration/continuousroll/StoreLog#FCMComposite_1_1
Label:CHARACTER:com.deere.jdc.jdrpintegration.continuousroll.StoreLog.JDC.CONTINUOUSROLL.LOG.REQUEST
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Node throwing exception
RecoverableException
File:CHARACTER:F:\build\S700_P\src\DataFlowEngine\PluginInterface\ImbJniNode.cpp
Line:INTEGER:1179
Function:CHARACTER:ImbJniNode::evaluate
Type:CHARACTER:ComIbmJavaComputeNode
Name:CHARACTER:com/deere/jdc/jdrpintegration/continuousroll/StoreLog#FCMComposite_1_5
Label:CHARACTER:com.deere.jdc.jdrpintegration.continuousroll.StoreLog.Java Compute
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Caught exception and rethrowing
RecoverableException
File:CHARACTER:JDBCType4SinglePhaseTrxnHandlerErrors.java
Line:INTEGER:209
Function:CHARACTER:JDBCType4SinglePhaseTrxnHandler::getConnection
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:6233
Text:CHARACTER:Problem obtaining Transaction Resource
Insert
Type:INTEGER:5
Text:CHARACTER:Java Compute
Insert
Type:INTEGER:5
Text:CHARACTER:jdbc:db2://serverName:port/DBName:user=user;password=xxxxxxxx; |
Here goes the user Trace
| Code: |
2012-01-25 16:29:13.735830 9444 UserTrace BIP4040I: The Execution Group ''Default'' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2012-01-25 16:29:13.736263 9444 UserTrace BIP2638I: The MQ output node '.outputNode' attempted to write a message to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' connected to queue manager ''BRKRQM7''. The MQCC was '0' and the MQRC was '0'.
2012-01-25 16:29:13.736413 9444 UserTrace BIP2622I: Message successfully output by output node '.outputNode' to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' on queue manager ''BRKRQM7''.
2012-01-25 16:29:13.736731 9444 Information BIP2154I: Execution group finished with Configuration message.
A command response will be sent to the broker.
No user action required.
2012-01-25 16:29:21.756395 6896 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'com.deere.jdc.jdrpintegration.continuousroll.StoreLog.JDC.CONTINUOUSROLL.LOG.REQUEST'.
2012-01-25 16:29:21.756507 6896 UserTrace BIP3904I: Invoking the evaluate() method of node (class='ComIbmJavaComputeNode', name='com/deere/jdc/jdrpintegration/continuousroll/StoreLog#FCMComposite_1_5').
About to pass a message to the evaluate() method of the specified node.
No user action required.
2012-01-25 16:29:21.756595 6896 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'com.deere.jdc.jdrpintegration.continuousroll.StoreLog.JDC.CONTINUOUSROLL.LOG.REQUEST' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2012-01-25 16:29:21.756631 6896 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'com.deere.jdc.jdrpintegration.continuousroll.StoreLog.JDC.CONTINUOUSROLL.LOG.REQUEST' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2012-01-25 16:29:21.756719 6896 UserTrace BIP6061I: Parser type ''XMLNSC'' created on behalf of node 'com.deere.jdc.jdrpintegration.continuousroll.StoreLog.JDC.CONTINUOUSROLL.LOG.REQUEST' to handle portion of incoming message of length '679' bytes beginning at offset '364'. Parser type selected based on value ''XMLNSC'' from previous parser.
2012-01-25 16:29:21.757640 6896 UserTrace BIP2231E: Error detected whilst processing a message in node 'com.deere.jdc.jdrpintegration.continuousroll.StoreLog.JDC.CONTINUOUSROLL.LOG.REQUEST'.
The message broker detected an error whilst processing a message in node 'com.deere.jdc.jdrpintegration.continuousroll.StoreLog.JDC.CONTINUOUSROLL.LOG.REQUEST'. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing.
See the following messages for details of the error.
2012-01-25 16:29:21.757659 6896 RecoverableException BIP2230E: Error detected whilst processing a message in node 'com.deere.jdc.jdrpintegration.continuousroll.StoreLog.Java Compute'.
The message broker detected an error whilst processing a message in node 'com.deere.jdc.jdrpintegration.continuousroll.StoreLog.Java Compute'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2012-01-25 16:29:21.757669 6896 RecoverableException BIP6233E: An error occurred in node: 'Java Compute' There was a problem establishing a connection to the given database URL: jdbc:db2://serverName:port/DBName:user=user;password=xxxxxxxx;' Exception details: {2}
The node was unable to establish a connection to the given database URL.
Contact your WebSphere Message Broker administrator. |
I tried the same DB URL with a sample JDBC java class and was able to connect to DB successfully.
Thanks |
|
| Back to top |
|
|
|
|
