| Author |
Message
|
| hal |
 Posted: Tue Feb 14, 2006 11:49 am Post subject: Message Broker V6 $SYS_mqsi execution group |
 |
|
Acolyte
Joined: 07 Dec 2005
Posts: 67
Location: New York City, New York
|
Hello,
After opening a domain connection from my Message Broker Toolkit to my UNIX Solaris V6 message broker via File->New->Broker, an execution group called $SYS_mqsi appeared as a UNIX process. The $SYS_mqsi execution group does not show up anywhere in the toolkit Domains.
Additional deployments succeed but take a very long time and contain the event log message,
BIP1536S: The Configuration Manager was unable to register for internal subscriptions with broker WBRK_BROKER.
ps -ef|grep Data
shows
mqm 10045 10009 0 10:18:20 ? 0:06 DataFlowEngine WBRK_BROKER 82a6e590-12b3-11d3-81a2-00203506a68e $SYS_mqsi 1
The toolkit event log error is
BIP2066E: Broker WBRK_BROKER (UUID 82f82369-0901-0000-0080-885e2877f895) was unable to retrieve an internal configuration response message for execution group '$SYS_mqsi' within the 360 second Configuration Timeout.
The message broker log also complains about a failed attempt to insert a BUSERMEMBERSHIP record into my message broker UNIX Sybase ASE 12.5.3 database:
Feb 14 10:18:30 appnyu171 WebSphere Broker v6000[10045]:
[ID 702911 user.error] (WBRK_BROKER.$SYS_mqsi)
[28]BIP2371E: Database statement 'INSERT INTO dbo.BUSERMEMBERSHIP VALUES (? , ? , ?)' could not be executed. :
WBRK_BROKER.82a6e590-12b3-11d3-81a200203506a68e:
/build/S000_P/src/DataFlowEngine/ImbOdbc.cpp:
1679: ImbOdbcStatement::execDirect: :
Feb 14 10:18:30 appnyu171 WebSphere Broker v6000[10045]:
[ID 702911 user.error] (WBRK_BROKER.$SYS_mqsi)[28]BIP2321E: Database error: ODBC return code '-1'. :
WBRK_BROKER.82a6e590-12b3-11d3-81a2-00203506a68e:
/build/S000_P/src/DataFlowEngine/ImbOdbc.cpp: 232: ImbOdbcHandle::checkRcInner: :
Feb 14 10:18:30 appnyu171 WebSphere Broker v6000[10045]:
[ID 702911 user.error] (WBRK_BROKER.$SYS_mqsi)[28]BIP2322E:
Database error: SQL State '23000'; Native Error Code '233'; Error Text '[DataDirect][ODBC Sybase Wire Protocol driver][SQL Server]
The column Memberof in table dbo.BUSERMEMBERSHIP does not allow null values.'. :
WBRK_BROKER.82a6e590-12b3-11d3-81a200203506a68e:
/build/S000_P/src/DataFlowEngine/ImbOdbc.cpp: 360: ImbOdbcHandle::checkRcInner: :
There is a /var/mqsi/components/WBRK_BROKER/82a6e590-12b3-11d3-81a2-00203506a68e directory.
I am unable to delete the $SYS_mqsi execution group.
mqsideleteexecutiongroup -i appnyu171 -p 1414 -q MQSPROD -b WBRK_BROKER -e '$SYS_mqsi'
BIP1044I: Connecting to the Configuration Manager's queue manager...
BIP1045I: Connecting to the Configuration Manager...
BIP1038S: Execution group not found.
Either the execution group '$SYS_mqsi' was not found in the Configuration Manager repository for broker 'WBRK_BROKER', or you do not have the required permissions to view it.
Reissue the command specifying a valid execution group to which you have access.
mqsideleteexecutiongroup -i appnyu171 -p 1414 -q MQSPROD -b WBRK_BROKER -e 82a6e590-12b3-11d3-81a2-00203506a68e
also didn't work.
The same $SYS_mqsi issue occurred after I recreated all my broker components from scratch (I used mqsideleteconfigmgr CMGR01 -n to delete the configuration manager. After that I had to rerun mqsicreateaclentry.) |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Wed Feb 15, 2006 1:53 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Hello,
Search the forum for information on $SYS_MQSI.
Each broker always requires at least one execution group in order to run, and The $SYS_MQSI execution group is automatically created by the broker if no other execution group exists.
Create and deploy a 'proper' execution group and the $SYS_MQSI one will disappear the next time the broker is restarted.
There is still potentally a problem with you not receiving configuration responses (BIP2066E), but try creating an execution group first, restarting the broker and deploying a BAR file to it. That will at least remove the $SYS_MQSI from the equation.
Regards
-Matt |
|
| Back to top |
|
|
| hal |
| Posted: Wed Feb 15, 2006 6:40 am Post subject: |
|
|
Acolyte
Joined: 07 Dec 2005
Posts: 67
Location: New York City, New York
|
I have already created other execution groups and am able to deploy bar files containing message flows and message sets to them. The problem is that the deploys take a very long time (usually at least 10 minutes) and are always accompanied by BIP2066E errors. The $SYS_mqsi execution group did not go away after the other execution groups were deployed. I have recyled the broker multiple times. The configuration manager and the message broker use the same queue manager.
ps -ef|grep Data
mqm 26885 10009 0 17:09:17 ? 0:05 DataFlowEngine WBRK_BROKER 7b16636a-0901-0000-0080-885e2877f895 EXECOFAC 0
mqm 27767 10009 0 17:33:51 ? 0:06 DataFlowEngine WBRK_BROKER 3f5f636a-0901-0000-0080-885e2877f895 EXECPARIS 0
mqm 23032 10009 0 16:07:58 ? 0:06 DataFlowEngine WBRK_BROKER 700f626a-0901-0000-0080-885e2877f895 EXECCLIENTS 0
mqm 23260 10009 0 16:14:08 ? 0:05 DataFlowEngine WBRK_BROKER 146a626a-0901-0000-0080-885e2877f895 EXECDDA 0
mqm 26010 10009 0 16:46:41 ? 0:06 DataFlowEngine WBRK_BROKER e8d8626a-0901-0000-0080-885e2877f895 EXECMTR 0
mqm 22141 10009 0 15:47:23 ? 0:05 DataFlowEngine WBRK_BROKER 83f82369-0901-0000-0080-885e2877f895 default 0
mqm 10045 10009 0 10:18:20 ? 0:06 DataFlowEngine WBRK_BROKER 82a6e590-12b3-11d3-81a2-00203506a68e $SYS_mqsi 1
The message broker log is with now updated every several minutes with repeated $SYS_mqsi BIP2080E errors:
Feb 15 09:20:32 appnyu171 WebSphere Broker v6000[10009]: [ID 702911 user.error] (WBRK_BROKER)[1]BIP2080E: Execution Group $SYS_mqsi failed to return an internal configuration Start message response within a 60 second time period. : WBRK_BROKER.agent: /build/
S000_P/src/AdminAgent/ImbAdminAgent.cpp: 6319: ImbAdminAgent::getXMLResponse: :
Feb 15 09:24:52 appnyu171 last message repeated 2 times |
|
| Back to top |
|
|
| hal |
| Posted: Thu Feb 16, 2006 2:32 pm Post subject: Concurrent $SYS_mqsi and default execution groups |
|
|
Acolyte
Joined: 07 Dec 2005
Posts: 67
Location: New York City, New York
|
According to IBM support the $SYS_mqsi execution group and the default execution group are not supposed to be running at the same time.
Has anyone seen this before?
mqm 1683 1653 0 17:13:40 ? 0:02 DataFlowEngine WBRK_BROKER
83f82369-0901-0000-0080-885e2877f895 default 0
mqm 1661 1653 0 17:12:40 ? 0:06 DataFlowEngine WBRK_BROKER
82a6e590-12b3-11d3-81a2-00203506a68e $SYS_mqsi 1
mqm 1688 1653 0 17:13:40 ? 0:02 DataFlowEngine WBRK_BROKER
700f626a-0901-0000-0080-885e2877f895 EXECONE 0
mqm 1682 1653 0 17:13:40 ? 0:02 DataFlowEngine WBRK_BROKER
7b16636a-0901-0000-0080-885e2877f895 EXECTWO 0
Last edited by hal on Fri Feb 17, 2006 3:39 pm; edited 1 time in total |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Feb 16, 2006 5:14 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Hi Hal,
is this a clean install of V6, or on a machine that previously had v2 or v5? and is this a new broker or a migration?
Have you tried deleteing the broker and the database and recreating both from scratch? If it were me, I would try to fix the db error first.
_________________
-wayne |
|
| Back to top |
|
|
| hal |
| Posted: Fri Feb 17, 2006 3:16 pm Post subject: mqsicreatebroker -s causes errors on Solaris |
|
|
Acolyte
Joined: 07 Dec 2005
Posts: 67
Location: New York City, New York
|
Hi Wayne,
This is a clean install with a new broker. mqsimigratemsgflows and mqsimigratemsgsets were used to replicate my old environment.
I was able to fix my issues by repeatedly deleting and recreating the message broker using different options. All of my errors went away after I created my Solaris V6 message broker without the mqsicreatebroker -s UserNameServerQueueManagerName switch (and without the -s switch in combination with the -j pub/sub access control enablement switch.)
The $SYS_mqsi execution group did not disappear after the first successful message flow deployment. It only vanished after the first mqsistop/mqsistart component recycles.
The Information Center is confusing. The mqiscreatebroker command section states that supported platforms are Windows, Linux, UNIX and Z/OS. One of the examples uses the -s switch. However the Information Center's "Creating a broker on Solaris" section does not contain any information about the optional mqsicreatebroker switches.
My user name server is still running. I don't use it now but may need pub/sub message flows in the future. |
|
| Back to top |
|
|
| wschutz |
| Posted: Fri Feb 17, 2006 4:52 pm Post subject: Re: mqsicreatebroker -s causes errors on Solaris |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| hal wrote: |
The $SYS_mqsi execution group did not disappear after the first successful message flow deployment. It only vanished after the first mqsistop/mqsistart component recycles.
|
That behaviour is to be expected (as Matt indicates),and as described here for the "default" execution group: http://www.mqseries.net/phpBB2/viewtopic.php?t=25494&highlight=default+broker
| hal wrote: |
The Information Center is confusing. The mqiscreatebroker command section states that supported platforms are Windows, Linux, UNIX and Z/OS. One of the examples uses the -s switch. However the Information Center's "Creating a broker on Solaris" section does not contain any information about the optional mqsicreatebroker switches.
|
Sorry, I'm not exactly sure what the point is here. None of the "creating a broker on xxx" platforms sections shows the -s (or -j) switches.....
_________________
-wayne |
|
| Back to top |
|
|
| hal |
| Posted: Sat Apr 08, 2006 3:13 pm Post subject: mqsicreatebroker -s -j flags require Message Broker 6.0.0.1 |
|
|
Acolyte
Joined: 07 Dec 2005
Posts: 67
Location: New York City, New York
|
I sent my user name server trace file to IBM support. They identified "a defect that matched this problem and it has gone into fix pack 01." The trace shows UNIX accounts that do not belong to any operating system group. (My system administrator told me that these represent ex-employees.) Apparently groupless accounts disallow database connectivity between a message broker and a user name server in the base V6 Message Broker. The dangling $SYS_mqsi execution group is a side effect.
I cannot find fix details at
http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27007481
But after applying Message Broker Fix Pack 6.0.0.1 I am able to successfully create a message broker with user name server authentication services and publish/subscribe access control enablement via,
mqsicreatebroker $MESSAGEBROKER
-i mqm -a mqmPassword
-q $QUEUEMANAGER -n WBRKBKDB
-u mqm -p databasePassword
-s $QUEUEMANAGER -j
In order to validate my deployments and execution groups I decided to start with a clean slate. First I removed message broker components by deleting the broker from the Toolkit topology, exiting from the Toolkit, stopping the SYSTEM.BKR.CONFIG server connection channel, mqsistopping the UNIX broker components, sending a kill signal to the RAServer, issuing mqsibackupconfigmgr/mqsideleteusernameserver/
mqsideleteconfigmgr -n/mqsideletebroker commands and dropping the message broker Sybase database tables.
Next I recreated the broker runtime components with
mqsicreatebroker/mqsicreateconfigmgr/mqsicreateaclentry/mqsicreateusernameserver commands. After mqsistarting the broker/configmgr/usernameserver and invoking the RAServer, I opened the Toolkit and created my Broker under Domain Broker Topology.
I deployed a bar file containing a message-flow and a message-set to the default execution group. At this point there were two DataFlowEngines running on the UNIX side: $SYS_mqsi and default. After recycling the run-time message broker, the $SYS_mqsi execution group disappeared. Finally I recreated the rest of my execution groups and deployed message-flow/message-set bar files to them. |
|
| Back to top |
|
|
| rmah |
| Posted: Wed Mar 18, 2009 4:46 pm Post subject: |
|
|
Centurion
Joined: 04 May 2007
Posts: 142
|
| mqmatt wrote: |
Hello,
Search the forum for information on $SYS_MQSI.
Each broker always requires at least one execution group in order to run, and The $SYS_MQSI execution group is automatically created by the broker if no other execution group exists.
Create and deploy a 'proper' execution group and the $SYS_MQSI one will disappear the next time the broker is restarted.
There is still potentally a problem with you not receiving configuration responses (BIP2066E), but try creating an execution group first, restarting the broker and deploying a BAR file to it. That will at least remove the $SYS_MQSI from the equation.
Regards
-Matt |
I've just deployed several flows to my broker, and have restarted the broker several times, but the $SYS_mqsi group is still there with a 1 beside it. This will affect my ability to clone broker.
Any thoughts on how to get rid of this and have the default exec group be assigned to a deployed flow?
Thanks
_________________
MQ 6.0.2.3
Broker 6.0.0.7
for Linux |
|
| Back to top |
|
|
|
|
