| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| SQLSERVER issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| bdrummond |
 Posted: Fri Sep 27, 2013 1:31 am Post subject: SQLSERVER issue |
 |
|
Disciple
Joined: 06 May 2004
Posts: 164
|
Hi All,
I am having a strange issue when trying to insert data into a SQLSERVER 2012 DB.
When running an INSERT statement from a Windows (Win7) Broker, it is successful.
However, when running the same code in a Solaris Broker, I get a strange response and the flow fails.
The version of MB on both boxes is v7.0.0.2
When running through debug in Solaris, at the time of the INSERT, the debug terminates and the message is backed out.
When runnig user trace, I see a lot of the following entries:
| Code: |
2013-09-26 14:45:59.537568 1 UserTrace BIP3484E: ''Please edit axis2.xml and replace with the same class in org.apache.axis2.dispatchers package''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2013-09-26 14:45:59.803080 1 UserTrace BIP3484E: ''Dispatcher org.apache.axis2.engine.SOAPMessageBodyBasedDispatcher is now deprecated.''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2013-09-26 14:45:59.804128 1 UserTrace BIP3484E: ''Please edit axis2.xml and replace with the same class in org.apache.axis2.dispatchers package''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2013-09-26 14:45:59.817560 1 UserTrace BIP3484E: ''Dispatcher org.apache.axis2.engine.SOAPActionBasedDispatcher is now deprecated.''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2013-09-26 14:45:59.818172 1 UserTrace BIP3484E: ''Please edit axis2.xml and replace with the same class in org.apache.axis2.dispatchers package''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2013-09-26 14:45:59.819576 1 UserTrace BIP3484E: ''Dispatcher org.apache.axis2.engine.SOAPMessageBodyBasedDispatcher is now deprecated.''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2013-09-26 14:45:59.819840 1 UserTrace BIP3484E: ''Please edit axis2.xml and replace with the same class in org.apache.axis2.dispatchers package''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2013-09-26 14:46:01.688162 1 UserTrace BIP3484E: ''Deploying module: addressing-SNAPSHOT - file:/opt/mqsi7/webservices/prereqs/axis2-SNAPSHOT.jar''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2013-09-26 14:46:01.755697 1 UserTrace BIP3484E: ''Deploying module: metadataExchange-SNAPSHOT - file:/opt/mqsi7/webservices/prereqs/mex-SNAPSHOT.jar''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2013-09-26 14:46:01.848026 1 UserTrace BIP3484E: ''Deploying module: wss-SNAPSHOT - file:/opt/mqsi7/webservices/prereqs/wssecurity-platform-impl-1.0-SNAPSHOT.jar''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
|
The ODBC entry for this DB is as follows:
| Code: |
[UKDEV1940]
Driver=/opt/mqsi7/ODBC/V6.0/lib/UKmsss24.so
Description=DataDirect 6.0 SQL Server Wire Protocol
Address=UK1SXWNSQL0008,1433
AnsiNPW=Yes
Database=UKDEV1940
QuotedId=No
ColumnSizeAsCharacter=1
LoginTimeout=0
|
The version of SQLSERVER is: Microsoft SQL Server 2012 (SP1) - 11.0.3128.0 (X64)
The mqsicvp command can also be run successfully from the Solaris Broker.
Does anyone have any knowledge on what the above issue could be..? I am assuming it is some sort of DB Driver issue but according to the InfoCenter and other docs, this driver should work.
Any help would be greatly appreciated.
Thanks. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Fri Sep 27, 2013 2:41 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Brendan,
That output from the usertrace looks a lot like some HTTPS Webservice traffic.
That may well have nothing to do with the DB problem.
What is the funny error you are seeing?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| dogorsy |
| Posted: Fri Sep 27, 2013 2:44 am Post subject: |
|
|
Knight
Joined: 13 Mar 2013
Posts: 553
Location: Home Office
|
| Agree with smdavies99, there is no indication that DB server is failing... unless there are other messages |
|
| Back to top |
|
|
| bdrummond |
| Posted: Fri Sep 27, 2013 4:22 am Post subject: |
|
|
Disciple
Joined: 06 May 2004
Posts: 164
|
Hi Stephen - Hope you are well..?
The funny error is not so much of an error message, just processing completely stops with no error reported but the message is backed out. The trace entries immediately before/after the strange entries in my original post (HTTPS Webservice traffic..?? - No Webservice calls at this stage of the flow) are as follows:
| Code: |
2013-09-27 12:09:50.374136 34 UserTrace BIP2544I: Node 'Logger.CSIIF_UGC_IALS_AuditLogger.Compute': Executing database SQL statement ''INSERT INTO dbo.IALS_TXN_AUDIT_TBL(REFERENCE_ID, VERSION, LOG_COMPONENT_NAME, LOG_CHAMELEON_ID, BUSINESS_TRANSACTION_ID, TRANSACTION_ID, SERVICE_NAME, TRANSACTION_NAME, PARENT_BUS_TID, CORRELATION_ID, ENVIRONMENT, SRC_COMPONENT_NAME, DEST_COMPONENT_NAME, MSG_DIRECTION, MSG_PERSISTENCE, MSG_PRIORITY, MSG_SERVICEOBJECT, MSG_SERVICEOBJECT_HOST, MSG_REPLYTO_SERVICEOBJECT, MSG_REPLYTO_SERVICEOBJECT_HOST, MSG_USERIDENTIFIER, MSG_RECEIVED_TS, MSG_PROCESSED_TS, MSG_STATUS, TRANSACTION_STATUS, ADDITIONAL_INFORMATION) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)'' derived from ('Logger.CSIIF_UGC_IALS_AuditLogger_Compute.Main', '37.5'); expressions ''ReferenceIDChr, VersionChr, ComponentNameChr, ChameleonIDChr, BusinessTransactionIDChr, TransactionIDChr, ServiceNameChr, TransactionNameChr, ParentBusTIDChr, CorrelationIDChr, EnvironmentChr, SrcComponentNameChr, DestComponentNameChr, MsgDirectionChr, MsgPersistenceChr, MsgPriorityInt, MsgServiceObjectChr, MsgServiceObjectHostChr, MsgReplyToServiceObjectChr, MsgReplyToServiceObjectHostChr, MsgUserIdentifierChr, MsgReceivedTSChr, MsgProcessedTSChr, MsgStatusChr, TransactionStatusChr, AdditionalInfoChr''; resulting parameter values '''b5a2ace0-276d-11e3-99ce-000000000000', '1.0', 'CSIIF_ESB', 'Chameleon_Id', 'ea36fc1e-276c-11e3-99ce-000000000000', '414d512047534f415f4448315f5753325242fc2a202d9f05', 'XPRESS', 'XPRESS', '', '', '', 'CSIIF_ESB', 'CCIS', 'O', 'NP', 0, 'GQH1_RD_XPRESS_REQUEST_001.FLOWQ', 'GSOA_DH1_WS2', '', 'GSOA_DH1_WS2', 'mqm', '2013-09-27 12:04:08.690', '2013-09-27 12:04:09.065819', 'E', '', ':: FaultCode - 2951 :: FaultType - UserException'''.
2013-09-27 12:10:50.251204 1 UserTrace BIP3484E: ''Dispatcher org.apache.axis2.engine.SOAPActionBasedDispatcher is now deprecated.''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
.
.
.
.
2013-09-27 12:11:06.628724 1 UserTrace BIP3484E: ''Deploying module: wss-SNAPSHOT - file:/opt/mqsi7/webservices/prereqs/wssecurity-platform-impl-1.0-SNAPSHOT.jar''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2013-09-27 12:11:12.929502 31 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node '.InputNode'.
2013-09-27 12:11:12.931301 31 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node '.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2013-09-27 12:11:12.931477 31 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node '.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2013-09-27 12:11:12.932234 31 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node '.InputNode' to handle portion of incoming message of length '305' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
2013-09-27 12:11:13.190737 31 Information BIP2155I: About to ''start ' ' the Message flow - ''Logger.CSIIF_UGC_IALS_AuditLogger''.
An execution group is about to perform an action.
No user action required.
2013-09-27 12:11:13.227971 31 UserTrace BIP2269I: Message flow ''Logger.CSIIF_UGC_IALS_AuditLogger'' (uuid=''59f82507-4101-0000-0080-e20fa54dd753'') started successfully.
The message broker received an operational control message containing an instruction to start the message flow ''Logger.CSIIF_UGC_IALS_AuditLogger'' (uuid=''59f82507-4101-0000-0080-e20fa54dd753'') and successfully performed this action.
No user action required.
2013-09-27 12:11:13.390271 33 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'Logger.CSIIF_UGC_IALS_AuditLogger.AuditLogger Queue' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2013-09-27 12:11:13.390549 33 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'Logger.CSIIF_UGC_IALS_AuditLogger.AuditLogger Queue' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2013-09-27 12:11:13.399539 33 UserTrace BIP6061I: Parser type ''XMLNSC'' created on behalf of node 'Logger.CSIIF_UGC_IALS_AuditLogger.AuditLogger Queue' to handle portion of incoming message of length '18502' bytes beginning at offset '364'. Parser type selected based on value ''XMLNSC'' from previous parser.
2013-09-27 12:11:13.399904 33 UserTrace BIP2631I: Backed out message being propagated to failure terminal; node 'Logger.CSIIF_UGC_IALS_AuditLogger.AuditLogger Queue'.
Node 'Logger.CSIIF_UGC_IALS_AuditLogger.AuditLogger Queue' has received a message which has previously been backed out because of a processing error in the message flow. The MQMD 'backoutCount' of the message exceeds (or equals) the 'backoutThreshold' defined for the WebSphere MQ input queue. The message broker is propagating the message to the failure terminal of the node.
Examine the other messages and the message flow to determine why the message is being backed out. Correct this situation if possible. Perform any local error recovery processing required.
|
The flow that is doing the INSERT is CSIIF_UGC_IALS_AuditLogger and looking at the trace file, this appears to restart halfway through processing. Maybe there is some kind of connection issue between the Broker server and the DB Server but I would expect more in the way of errros in the trace.
Or am I just asking for too much..? 
Suffice to say, the INSERT is not working and nothing is added to the DB. |
|
| Back to top |
|
|
| bdrummond |
| Posted: Fri Sep 27, 2013 7:15 am Post subject: |
|
|
Disciple
Joined: 06 May 2004
Posts: 164
|
A SELECT from the same DB also doesn't work and on further investigation, the Execution Group restarts itself. A new EG PID is created at the same time the flow is waiting for a response from the DB.
Very bizarre and still has me scratching my head.  |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Sep 27, 2013 7:39 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Did you confirm that broker v7 supports talking to SQLServer 2012? |
|
| Back to top |
|
|
| bdrummond |
| Posted: Fri Sep 27, 2013 7:51 am Post subject: |
|
|
Disciple
Joined: 06 May 2004
Posts: 164
|
| mqjeff wrote: |
| Did you confirm that broker v7 supports talking to SQLServer 2012? |
It certanly does on my v7 Windows Broker, which is why I think it may have something to do with the Data Direct driver that is being used on Solaris. (but that's just a guess at this stage )
Last edited by bdrummond on Fri Sep 27, 2013 7:55 am; edited 1 time in total |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Sep 27, 2013 7:53 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| bdrummond wrote: |
| mqjeff wrote: |
| Did you confirm that broker v7 supports talking to SQLServer 2012? |
It certanly does on my v7 Windows Broker, which is why I think it may have something to do with the Data Direct driver that is being used on Solaris. |
I didn't ask if it WORKED, I asked if it was SUPPORTED. |
|
| Back to top |
|
|
| bdrummond |
| Posted: Fri Sep 27, 2013 8:14 am Post subject: |
|
|
Disciple
Joined: 06 May 2004
Posts: 164
|
| mqjeff wrote: |
| I didn't ask if it WORKED, I asked if it was SUPPORTED. |
Ah..in that case, the answer is 'yes or no'
There is no distinction between different versions of SQL Server, however the InfoCentre has the following:
Solaris on SPARC is supported (6.On Linux and UNIX systems, you can remotely access an SQL Server database on Windows by using a supplied wire protocol driver.)
Solaris on x86-64 is Not Suppoorted.
We've got SPARC so I guess that it is supported. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Sep 27, 2013 8:27 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| bdrummond |
| Posted: Fri Sep 27, 2013 9:03 am Post subject: |
|
|
Disciple
Joined: 06 May 2004
Posts: 164
|
Many thanks for that Jeff. I'll double check the DB columns and also the odbc.ini file.
Failing that, and if SQLServer 2012 isn't supported, we may have to try and point to another flavoured DB.
Cheers. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Sep 27, 2013 10:24 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
And now we have a customer asking for SQLServer 2014!
Yes I know it is not even released yet....
It does have some nifty bits though including some ability to make bits of the DB memory resident.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Sep 27, 2013 10:37 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
To be clear, I expect (although I've not checked) that IIB v9 supports SQLServer 2012.
Just not v7.
First rule of database support in broker - if it hadn't shipped when your release of broker shipped, it's probably not supported and it CERTAINLY wasn't tested. |
|
| Back to top |
|
|
| bdrummond |
| Posted: Mon Sep 30, 2013 3:25 am Post subject: |
|
|
Disciple
Joined: 06 May 2004
Posts: 164
|
Looking again at the link Jeff provided earlier, it looks like the earliest version of Broker that can connect to SQL Server 2012 is 8.0.0.2:
| Quote: |
ODBC connection to database only supported using the DataDirect V7.0 ODBC drivers shipped with WebSphere Message Broker V8.0.0.2, except on Windows where the native driver should be used.
|
So looks like an upgrade to 8 will be required before we can connect to SQL Server 2012. |
|
| 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
|
|
|
|
