|  | 
 
  
    | RSS Feed - WebSphere MQ Support | RSS Feed - Message Broker Support |  
 
  
	|    |  |  
  
	| No Reconnect to Database after session has been killed | « View previous topic :: View next topic » |  
  	| 
		
		
		  | Author | Message |  
		  | ronq | 
			  
				|  Posted: Thu Apr 01, 2004 5:26 am    Post subject: No Reconnect to Database after session has been killed |   |  |  
		  | Newbie
 
 
 Joined: 03 Apr 2003Posts: 8
 
 
 | 
			  
				| Hi, 
 we are testing our message flow in failure scenarios (e.g. kill the ODBC-Session). After we killed the OBDC-Session the broker didn't reconnect to the database.
 
 Here [url]http://www .mqseries.net/phpBB2/viewtopic.php?t=9823[/url] is a solution discussed (use the BackoutTreshhold-Value of the InputQueue).
 
 We set the BackoutTreshhold-value of our InputQueue to 6.
 Now we would expect that the broker would fail the first incoming message, increment the BackoutCounter of the message, put the message back to the InputQueue and try it again. At the sesond time the broker reconnect to the db.
 But the reconnection doesn't work.
 
 The syslog of WMQI has 6 times the same error-message (see below). So we think that the BackoutTreshhold works.
 
 Only after stop and restart the Broker will establish a new connection.
 
 Have someone any idea?
 
 Thanks a lot.
 RonQ
 
 Error-Message:
 
 
   
	| Quote: |  
	| BIP2230E: Error detected whilst processing a message in node 'F_ALL_SIDB.CP_ALL_SIDB_AblageOrg'. : SITA_BROKER.a7f5283b-f800-0000-0080-e73c96192db0: /build/S210_P/src/DataFlowEngine/ImbComputeNode.cpp: 453: ImbComputeNode::evaluate: ComIbmComputeNode: 4496030f-f300-0000-0080-e73c96192db0 BIP2519E:(8, 3) : Error executing SQL statement 'SELECT SITA.S_SITA_ORG.nextval from DUAL' against datasource 'WSSITA' with parameters ''. : SITA_BROKER.a7f5283b-f800-0000-0080-e73c96192db0: /build/S210_P/src/DataFlowEngine/ImbRdl/ImbRdlExternalDb.cpp: 267: SqlExternalDbStmt::executeStmt: ComIbmComputeNode: 4496030f-f300-0000-0080-e73c96192db0
 BIP2321E: Database error: ODBC return code '-1'. : SITA_BROKER.a7f5283b-f800-0000-0080-e73c96192db0: /build/S210_P/src/DataFlowEngine/ImbOdbc.cpp: 152: ImbOdbcHandle::checkRcInner: :
 BIP2322E: Database error: SQL State 'HY000'; Native Error Code '1012'; Error Text '[MERANT][ODBC Oracle 8 driver][Oracle 8]ORA-01012: not logged on: SITA_BROKER.a7f5283b-f800-0000-0080-e73c96192db0: /build/S210_P/src/DataFlowEngine/ImbOdbc.cpp: 252: ImbOdbcHandle::checkRcInner: :
 BIP2628E: Exception condition detected on input node 'F_ALL_SIDB.LQ.SITAGW.SIBROK'. : SITA_BROKER.a7f5283b-f800-0000-0080-e73c96192db0: /build/S210_P/src/DataFlowEngine/ImbMqInputNode.cpp: 1512: ImbMqInputNode::readQueue: ComIbmMQInputNode: 390af04f-f100-0000-0080-e73c96192db0
 BIP2321E: Database error: ODBC return code '-1'. : SITA_BROKER.a7f5283b-f800-0000-0080-e73c96192db0: /build/S210_P/src/DataFlowEngine/ImbOdbc.cpp: 152: ImbOdbcHandle::checkRcInner: :
 BIP2322E: Database error: SQL State 'HY000'; Native Error Code '1012'; Error Text '[MERANT][ODBC Oracle 8 driver][Oracle 8]ORA-01012: not logged on: SITA_BROKER.a7f5283b-f800-0000-0080-e73c96192db0: /build/S210_P/src/DataFlowEngine/ImbOdbc.cpp: 252: ImbOdbcHandle::checkRcInner: :
 |  _________________
 RonQ
 |  |  
		  | Back to top |  |  
		  |  |  
		  | kirani | 
			  
				|  Posted: Sat Apr 03, 2004 11:29 am    Post subject: |   |  |  
		  | Jedi Knight
 
 
 Joined: 05 Sep 2001Posts: 3779
 Location: Torrance, CA, USA
 
 | 
			  
				| Could you provide your platform details? It's working for us, we are using WMQI 2.1 CSD4 on Windows platform.
 _________________
 Kiran
 
 
 IBM Cert. Solution Designer & System Administrator - WBIMB V5
 IBM Cert. Solutions Expert - WMQI
 IBM Cert. Specialist - WMQI, MQSeries
 IBM Cert. Developer - MQSeries
 
 
 |  |  
		  | Back to top |  |  
		  |  |  
		  | Heinz57 | 
			  
				|  Posted: Sun Apr 04, 2004 5:21 am    Post subject: |   |  |  
		  |  Apprentice
 
 
 Joined: 21 Jan 2004Posts: 26
 Location: Syracuse, NY
 
 | 
			  
				| we have had similar problems, especially when we IPL the mainframe or reboot SQL server. We have an automated task the runs MQSIRELOAD. This reloads the broker and resets the ODBC connections. You should be at CSD4 to use it though, we first tried with CSD2 and ran into problems |  |  
		  | Back to top |  |  
		  |  |  
		  | ronq | 
			  
				|  Posted: Tue Apr 13, 2004 2:37 am    Post subject: |   |  |  
		  | Newbie
 
 
 Joined: 03 Apr 2003Posts: 8
 
 
 | 
			  
				| sorry for being late, but i was in vacation. 
 Our platform details: AIX 4.3.3 and MQSI 2.1 CSD4
 
 I think we've got the solution. In the reading from the CSD-Level 5 is described following problem:
 
 IY37803 - BROKER FAILS TO CONNECT TO ITS DATABASE, AFTER  A DATABASE RECYLE  ...
 
 I didn't try the CSD 5 or 6 yet, so I can't say if it works or doesn't.
 
 Greetings
 RonQ
 _________________
 RonQ
 |  |  
		  | Back to top |  |  
		  |  |  
		  |  |  |  
  
	|    |  | Page 1 of 1 |  
 
 
  
  	| 
		
		  | 
 
 | You cannot post new topics in this forum You cannot reply to topics in this forum
 You cannot edit your posts in this forum
 You cannot delete your posts in this forum
 You cannot vote in polls in this forum
 
 |  |  |  |