| Author |
Message
|
| fdouek |
 Posted: Tue Aug 27, 2002 12:05 pm Post subject: MQSeries on Solaris as a transaction coordinator |
 |
|
Newbie
Joined: 17 Jul 2002
Posts: 4
Location: Brazil
|
I´m trying to make this scenario work but can´t stop getting erros in
Oracle and MQSeries:
* Solaris 2.7
* MQSeries V5R2 as a transaction coordinator
* API IBM MQBase for Java
* CSD05 applied
* 2 processes consuming from DIFFERENT MQ queues
* Oracle as a XA resource
Here are the errors:
AMQ6109, AMQ6119 and AMQ7605
We´re thinking about changing the solution to another product that can
work on
Solaris. Please, help us if there´s some workaround or solution.
Maybe a full description can help:
+-----------------------------------------------------------------------------+
| Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
    |
| MQSeries First Failure Symptom Report               Â
    |
| ===================================== Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
    |
| Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
    |
| Date/Time     :- Friday August 23 16:54:14 EST 2002      Â
    |
| Host Name     :- srvtux02rj1sol (SunOS 5.7)          Â
    |
| PIDS Â Â Â Â Â Â Â :- 5765B75 Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
    |
| LVLS Â Â Â Â Â Â Â :- 520 Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
    |
| Product Long Name :- MQSeries for Sun Solaris 2 (Sparc) Â Â Â Â Â Â
    |
| Vendor       :- IBM                      Â
    |
| Probe Id      :- XC130002                   Â
    |
| Application Name  :- MQM                      Â
    |
| Component     :- xehExceptionHandler              Â
    |
| Build Date     :- Aug  1 2002                  Â
    |
| CMVC level     :- p520-CSD05G                  Â
    |
| Build Type     :- IKAP - (Production)              Â
    |
| UserID Â Â Â Â Â Â :- 00001012 (qsms) Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
    |
| Program Name    :- java                     Â
    |
| Process      :- 00002542                   Â
    |
| Thread       :- 00000001                   Â
    |
| QueueManager    :- QM_SMS                    Â
    |
| Major Errorcode  :- STOP                     Â
    |
| Minor Errorcode  :- OK                      Â
    |
| Probe Type     :- HALT6109                   Â
    |
| Probe Severity   :- 1                       Â
    |
| Probe Description :- AMQ6109: An internal MQSeries error has
occurred. Â Â Â |
| Arith1 Â Â Â Â Â Â :- 4 4 Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
    |
| Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
    |
+-----------------------------------------------------------------------------+
+-----------------------------------------------------------------------------+
| Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
    |
| MQSeries First Failure Symptom Report               Â
    |
| ===================================== Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
    |
| Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
    |
| Date/Time     :- Friday August 23 16:54:14 EST 2002      Â
    |
| Host Name     :- srvtux02rj1sol (SunOS 5.7)          Â
    |
| PIDS Â Â Â Â Â Â Â :- 5765B75 Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
    |
| LVLS Â Â Â Â Â Â Â :- 520 Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
    |
| Product Long Name :- MQSeries for Sun Solaris 2 (Sparc) Â Â Â Â Â Â
    |
| Vendor       :- IBM                      Â
    |
| Probe Id      :- XC022001                   Â
    |
| Application Name  :- MQM                      Â
    |
| Component     :- xcsDisplayMessageForSubpool          Â
    |
| Build Date     :- Aug  1 2002                  Â
    |
| CMVC level     :- p520-CSD05G                  Â
    |
| Build Type     :- IKAP - (Production)              Â
    |
| UserID Â Â Â Â Â Â :- 00001012 (qsms) Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
    |
| Program Name    :- java                     Â
    |
| Process      :- 00002542                   Â
    |
| Thread       :- 00000001                   Â
    |
| QueueManager    :- QM_SMS                    Â
    |
| Major Errorcode  :- xecF_E_UNEXPECTED_SYSTEM_RC          Â
    |
| Minor Errorcode  :- OK                      Â
    |
| Probe Type     :- MSGAMQ6119                  Â
    |
| Probe Severity   :- 2                       Â
    |
| Probe Description :- AMQ6119: An internal MQSeries error has
occurred ('13 Â |
| Â - Permission denied' from open.) Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
    |
| Arith1       :- 13 d                     Â
    |
| Comment1 Â Â Â Â Â :- '13 - Permission denied' from open. Â Â Â Â Â Â
    |
| Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
    |
| Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
_________________
Fabio Douek |
|
| Back to top |
|
 |
| TonyD |
| Posted: Tue Aug 27, 2002 3:50 pm Post subject: |
|
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
I suspect the clue is here:
'13 - Permission denied' from open.'
I have experienced similar, athough not in the same context as you, but cannot recall exact details. Would suggest that you check permissions under /var/mqm/qmgrs/QM_SMS and also authorisation for userid qsms...or even Oracle authorisation(?).
Last edited by TonyD on Tue Aug 27, 2002 10:10 pm; edited 1 time in total |
|
| Back to top |
|
|
| jc_squire |
| Posted: Tue Aug 27, 2002 4:24 pm Post subject: |
|
|
Centurion
Joined: 14 Apr 2002
Posts: 105
Location: New Zealand
|
Following from the information centre:
AMQ7605 The XA resource manager &3 has returned an unexpected return code &1, when called for &4.
Explanation: MQSeries received an unexpected return code when calling XA resource manager &3 at its &4 entry point. This indicates an internal error, either within MQSeries or the resource manager.
User Response: Try to determine the source of the error. A trace of the failure could be used to look at the XA flows between MQSeries and the resource manager. MQSeries has allocated an RMId of &2 to this resource manager. This will be useful when isolating the flows associated with the resource manager concerned. If the error occurs on an xa_commit or xa_rollback request, the queue manager will not attempt to redeliver the commit or rollback instruction for this transaction, until after the queue manager has been restarted. The transaction indoubt is identified by the following XID of X'&5'. If you think that the error lies within the queue manager, contact your IBM support center. Do not discard any information describing the problem until after the problem has been resolved.
Looks like you are going to have fun with this one ..... 
Regards
_________________
J C Squire
IBM Certified Specialist - MQSeries |
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed Aug 28, 2002 10:19 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
You didn't give the levels of all of your products. I'd suggest that you go out to:
http://www-3.ibm.com/software/ts/mqseries/platforms/supported/mqseries_for_solaris_5_2.html
and make sure that everything is at a supported level.
I'd also suggest that you check the AMQERR01.LOG for your qmgr right after you start it up to make sure that it isn't throwing an XA error at start up. You can also post your qm.ini file here so that another pair of eyes can confirm the contents of the XAResourceManager stanza. |
|
| Back to top |
|
|
| fdouek |
| Posted: Wed Aug 28, 2002 10:52 am Post subject: Reply to Bower |
|
|
Newbie
Joined: 17 Jul 2002
Posts: 4
Location: Brazil
|
Bower,
On MQseries start, no errors occur.
#*******************************************************************#
#* Module Name: qm.ini *#
#* Type : MQSeries queue manager configuration file *#
# Function : Define the configuration of a single queue manager *#
#* *#
#*******************************************************************#
#* Notes : *#
#* 1) This file defines the configuration of the queue manager *#
#* *#
#*******************************************************************#
ExitPath:
ExitsDefaultPath=/var/mqm/exits/
#* *#
#* *#
Log:
LogPrimaryFiles=3
LogSecondaryFiles=2
LogFilePages=1024
LogType=CIRCULAR
LogBufferPages=17
LogPath=/var/mqm/log/QM_SMS/
LogWriteIntegrity=TripleWrite
Service:
Name=AuthorizationService
EntryPoints=9
ServiceComponent:
Service=AuthorizationService
Name=MQSeries.UNIX.auth.service
Module=/opt/mqm/lib/amqzfu
ComponentDataSize=0
XAResourceManager:
Name=smstar
ThreadOfControl=THREAD
SwitchFile=/opt/mqm/bin/jdbcora
XAOpenString=Oracle_XA+Acc=P/myuser/mypassword+SesTM=15+DB=smstar+LogDir=.+Threads=true+SqlNet=mydatabase
_________________
Fabio Douek |
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed Aug 28, 2002 12:34 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
I did some searching on an internal database, and the only thing that I found:
- check the bottom of the FDC that has the XC022001 probe. There should be a file listed that the open is failing on. You then need to verify the permissions on this file. One of the reasons for problems was the recreation of the mqm userid and its getting assigned a different number. |
|
| Back to top |
|
|
|
|
