| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQJMS5053 error, help |
« View previous topic :: View next topic » |
| Author |
Message
|
| kun.leeing |
 Posted: Fri Oct 30, 2009 1:54 am Post subject: MQJMS5053 error, help |
 |
|
Disciple
Joined: 27 Sep 2008
Posts: 171
|
Hi, every expert.
My client sometimes got error MQJMS 5053 and Linked Exception MQJE007 2033.
When the error happens, the broker is running.
I found this situation occur when system is busy. If that client reconnect, it will get connection as well.
The system run normally at first, but this error will happen more frequently as actions increasing.
How can I resolve it? Does only one broker run with one qmgr? If one broker can not response all of my transactions, can I create more broker on qmgr?
Thanks. |
|
| Back to top |
|
 |
| WMBDEV1 |
| Posted: Fri Oct 30, 2009 2:02 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| I havent really got a clue what your setup is as its not clear to me from your post. But the 2033 after the MQJE007 should give you a clue as to whats happened. |
|
| Back to top |
|
|
| jeevan |
| Posted: Fri Oct 30, 2009 7:51 am Post subject: Re: MQJMS5053 error, help |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| kun.leeing wrote: |
Hi, every expert.
My client sometimes got error MQJMS 5053 and Linked Exception MQJE007 2033.
When the error happens, the broker is running.
I found this situation occur when system is busy. If that client reconnect, it will get connection as well.
The system run normally at first, but this error will happen more frequently as actions increasing.
How can I resolve it? Does only one broker run with one qmgr? If one broker can not response all of my transactions, can I create more broker on qmgr?
Thanks. |
Is it request/reply scenario? where does the broker come into picture? Until and unless we know your setup and the context, how can we help you? describe your setup and what context this happens. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Oct 30, 2009 9:08 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| My client sometimes got error MQJMS 5053 and Linked Exception MQJE007 2033 |
This is not an error; rather, 2033 means no message available - something like end-of-file.
Is there any other symptom, other than the 2033? Does the app have code to catch and process this - like it would/should for end-of-file?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Oct 30, 2009 9:19 am Post subject: Re: MQJMS5053 error, help |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| kun.leeing wrote: |
| How can I resolve it? |
Fix your design. It sounds like (and only sounds as you've given no details on your system) when the system is busy it spins up more instances of the application to handle a backlog. Once the backlog is cleared, there are not enough messages for all the instances and some of them "abend" with this no available message code. A code, which as others have correctly pointed out, should be handled differently by the application - an abend is a very odd response to this.
As to why you're asking about broker who know? There's nothing in your post to indicate what you're using it for.
| kun.leeing wrote: |
| Does only one broker run with one qmgr? |
Yes.
| kun.leeing wrote: |
| If one broker can not response all of my transactions, can I create more broker on qmgr? |
No, but you can increase the number of threads the broker uses.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kun.leeing |
| Posted: Fri Oct 30, 2009 6:23 pm Post subject: |
|
|
Disciple
Joined: 27 Sep 2008
Posts: 171
|
Thanks for all of replies above.
My context : MQ 6.0.2.7 Redhat 4.5 .
And our system contained about some dozens of clients used pub/sub for operating message transportation. But the amout of messages intercommunicated in system is very large. All of clients connected to one qmgr with the broker. So this is why I suspect that broker's handling capacity is the bottleneck.
| Quote: |
when the system is busy it spins up more instances of the application to handle a backlog. |
I'm sorry I don't understand clearly.
Is the backlog at the broker? Does it mean apps (clients) wait until all of backlog processed?
| Quote: |
| Once the backlog is cleared, there are not enough messages for all the instances and some of them "abend" with this no available message code. |
Why this happens, the error looks like occurs as clients publishing msg at peak time. Then it receive this error, but it can reconnect and repub the message right away. Do you mean this error is thrown by subscribers in application?
I searh website of ibm, and find the some words about this error.
| Quote: |
| It is important to understand that there could be more than one reason for the MQJMS5053 exception to occur. For example, the broker may be busy and only temporarily unavailable or there could be some communication problem between the queue manager and the broker. |
This temporarily unavailable is normal? Can it be avoided?
| Quote: |
| but you can increase the number of threads the broker uses. |
Where can I set this number? At broker page of qmgr's properties？
Thanks. |
|
| Back to top |
|
|
| kun.leeing |
| Posted: Tue Nov 03, 2009 6:01 am Post subject: |
|
|
Disciple
Joined: 27 Sep 2008
Posts: 171
|
Anybody give me some clues?
Thanks.  |
|
| Back to top |
|
|
| kun.leeing |
| Posted: Thu Nov 05, 2009 7:49 pm Post subject: |
|
|
Disciple
Joined: 27 Sep 2008
Posts: 171
|
Hi,everybody.
I found I can always get this broker error when I publish big message about 1 Mb continuously to broker. But I did not get any errors in server log.
And I get fdc file below at client.
| Quote: |
-------------------------------------------------------------------------------
First Failure Data Capture Symptom Report
Product Name :- Message Service Client for .NET
Vendor :- IBM
Date/Time :- 2009年11月6日 11:18:15
Machine Name :- USER-1F32373F0F
OS Version :- Microsoft Windows NT 5.1.2600 Service Pack 2
Working Set :- 48640 KB
.NET Version :- 2.0.50727.42
XMS Version :- 1.2.6.0
CMVC Level :- Build: nn126-L080611
User Name :- user
User Domain :- USER-1F32373F0F
Process Id :- 2292
Thread Id :- 3064
Command Line :- "E:\Debug\New_Service\System\CTI.exe"
Current Dir :- E:\Debug\New_Service\System
Culture :- zh-CN
ProbeId :- XMS_WMQ_106
Exception :- IBM.WMQ.MQException
Source :- IBM.XMS.Util.ExceptionHelper.Create
Thread State :- Background
Thread Priority :- Normal
ApartmentState :- MTA
IsThreadPoolThr :- False
IsBackgroundThr :- True
-------------------------------------------------------------------------------
Stack trace:
CompCode: 2, Reason: 2033
Assemblies loaded from Global Assembly Cache:
mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
IBM.XMS, Version=1.1.1.2, Culture=neutral, PublicKeyToken=d2666ab12fca862b
IBM.XMS.Impl, Version=1.1.1.2, Culture=neutral, PublicKeyToken=d2666ab12fca862b
IBM.XMS.Core, Version=1.1.1.2, Culture=neutral, PublicKeyToken=d2666ab12fca862b
IBM.XMS.Util, Version=1.1.1.2, Culture=neutral, PublicKeyToken=d2666ab12fca862b
mscorlib.resources, Version=2.0.0.0, Culture=zh-CHS, PublicKeyToken=b77a5c561934e089
IBM.XMS.NLS, Version=1.1.1.2, Culture=neutral, PublicKeyToken=d2666ab12fca862b
System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
IBM.XMS.WMQ, Version=1.1.1.2, Culture=neutral, PublicKeyToken=d2666ab12fca862b
amqmdxcs, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7a58d55a51981a15
amqmdnsp, Version=6.0.1.1, Culture=neutral, PublicKeyToken=4ec3909022c7abcc
amqmdnet, Version=1.0.0.3, Culture=neutral, PublicKeyToken=dd3cb1c9aae9ec97
System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
System.EnterpriseServices.resources, Version=2.0.0.0, Culture=zh-CHS, PublicKeyToken=b03f5f7f11d50a3a
IBM.XMS.Match, Version=1.1.1.2, Culture=neutral, PublicKeyToken=d2666ab12fca862b
IBM.XMS.NLS.resources, Version=1.1.1.2, Culture=zh-CHS, PublicKeyToken=d2666ab12fca862b
Assemblies loaded from File System:
CTI, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
TRPU.XML, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
CTI_DLL, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
ZHMQPro, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
FileWriter, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
Thread dump:
Thread id: 252 State = Wait Priority = 11 Total Processor Time = 00:00:01.5625000 User = 00:00:00.8125000 System = 00:00:00.7500000. Wait reason = LpcReply
Thread id: 3664 State = Wait Priority = 8 Total Processor Time = 00:00:00 User = 00:00:00 System = 00:00:00. Wait reason = UserRequest
Thread id: 3272 State = Wait Priority = 13 Total Processor Time = 00:00:00.0156250 User = 00:00:00.0156250 System = 00:00:00. Wait reason = UserRequest
Thread id: 384 State = Wait Priority = 10 Total Processor Time = 00:00:00.0156250 User = 00:00:00 System = 00:00:00.0156250. Wait reason = ExecutionDelay
Thread id: 2980 State = Wait Priority = 10 Total Processor Time = 00:00:02.8281250 User = 00:00:01.9687500 System = 00:00:00.8593750. Wait reason = UserRequest
Thread id: 1864 State = Wait Priority = 11 Total Processor Time = 00:00:22.1718750 User = 00:00:21.3437500 System = 00:00:00.8281250. Wait reason = UserRequest
Thread id: 2860 State = Wait Priority = 10 Total Processor Time = 00:00:00 User = 00:00:00 System = 00:00:00. Wait reason = ExecutionDelay
Thread id: 2260 State = Wait Priority = 10 Total Processor Time = 00:00:00.1250000 User = 00:00:00.0625000 System = 00:00:00.0625000. Wait reason = ExecutionDelay
Thread id: 3600 State = Wait Priority = 11 Total Processor Time = 00:00:00 User = 00:00:00 System = 00:00:00. Wait reason = EventPairLow
Thread id: 2164 State = Wait Priority = 12 Total Processor Time = 00:00:16.1718750 User = 00:00:12.8906250 System = 00:00:03.2812500. Wait reason = UserRequest
Thread id: 3628 State = Wait Priority = 10 Total Processor Time = 00:00:09.6093750 User = 00:00:07.2031250 System = 00:00:02.4062500. Wait reason = UserRequest
Thread id: 700 State = Wait Priority = 10 Total Processor Time = 00:00:09.2500000 User = 00:00:06.9687500 System = 00:00:02.2812500. Wait reason = UserRequest
Thread id: 1668 State = Wait Priority = 10 Total Processor Time = 00:00:10.1406250 User = 00:00:07.8750000 System = 00:00:02.2656250. Wait reason = UserRequest
Thread id: 3440 State = Wait Priority = 12 Total Processor Time = 00:00:21.4218750 User = 00:00:17.4843750 System = 00:00:03.9375000. Wait reason = UserRequest
Thread id: 1472 State = Wait Priority = 11 Total Processor Time = 00:00:51.9218750 User = 00:00:33.3437500 System = 00:00:18.5781250. Wait reason = UserRequest
Thread id: 1172 State = Wait Priority = 10 Total Processor Time = 00:00:00 User = 00:00:00 System = 00:00:00. Wait reason = UserRequest
Thread id: 236 State = Wait Priority = 15 Total Processor Time = 00:00:00 User = 00:00:00 System = 00:00:00. Wait reason = UserRequest
Thread id: 3320 State = Wait Priority = 15 Total Processor Time = 00:00:00.0468750 User = 00:00:00.0468750 System = 00:00:00. Wait reason = UserRequest
Thread id: 2424 State = Wait Priority = 11 Total Processor Time = 00:00:20.5937500 User = 00:00:19.7656250 System = 00:00:00.8281250. Wait reason = UserRequest
Thread id: 3064 State = Running Priority = 10 Total Processor Time = 00:00:02.3750000 User = 00:00:01.8281250 System = 00:00:00.5468750
Thread id: 3644 State = Wait Priority = 10 Total Processor Time = 00:00:00 User = 00:00:00 System = 00:00:00. Wait reason = ExecutionDelay
Thread id: 3948 State = Wait Priority = 10 Total Processor Time = 00:00:00 User = 00:00:00 System = 00:00:00. Wait reason = LpcReceive
Thread id: 2672 State = Ready Priority = 8 Total Processor Time = 00:00:00 User = 00:00:00 System = 00:00:00
Process Environment Variables:
Path = C:\Program Files\IBM\WebSphere MQ\Java\lib;C:\MQ7K\MQTrigger;C:\Sun\SDK\jdk\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\80\Tools\BINN;C:\Program Files\Microsoft SQL Server\90\Tools\bin\;C:\Program Files\IBM\WebSphere MQ\bin;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\IBM\WebSphere MQ\tools\c\samples\bin
TEMP = C:\DOCUME~1\user\LOCALS~1\Temp
SESSIONNAME = Console
PATHEXT = .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
Rav = C:\Program Files\Rising\Rav
PROCESSOR_ARCHITECTURE = x86
SystemDrive = C:
RavData = C:\Documents and Settings\All Users\Application Data\Rising\Rav\
APPDATA = C:\Documents and Settings\user\Application Data
windir = C:\WINDOWS
USERPROFILE = C:\Documents and Settings\user
MQ_JAVA_LIB_PATH = C:\Program Files\IBM\WebSphere MQ\Java\lib
include = C:\Program Files\IBM\WebSphere MQ\tools\c\include;C:\Program Files\IBM\WebSphere MQ\tools\cplus\include
TMP = C:\DOCUME~1\user\LOCALS~1\Temp
MQ_JAVA_DATA_PATH = C:\Program Files\IBM\WebSphere MQ
ProgramFiles = C:\Program Files
FP_NO_HOST_CHECK = NO
HOMEPATH = \Documents and Settings\user
COMPUTERNAME = USER-1F32373F0F
CLASSPATH = C:\Program Files\IBM\WebSphere MQ\Java\lib\providerutil.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\com.ibm.mqjms.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\ldap.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\jta.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\jndi.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\jms.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\connector.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\fscontext.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\com.ibm.mq.jar;C:\MQ7K\MQTrigger.jar;C:\Program Files\IBM\WebSphere MQ\bin
MQSERVER = SERVERCONN.CHANNEL/Tcp/192.168.0.107(1414)
USERNAME = user
NUMBER_OF_PROCESSORS = 1
PROCESSOR_IDENTIFIER = x86 Family 15 Model 2 Stepping 9, GenuineIntel
SystemRoot = C:\WINDOWS
ComSpec = C:\WINDOWS\system32\cmd.exe
LOGONSERVER = \\USER-1F32373F0F
VS80COMNTOOLS = C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\
CommonProgramFiles = C:\Program Files\Common Files
MQ_JAVA_INSTALL_PATH = C:\Program Files\IBM\WebSphere MQ\Java
PROCESSOR_LEVEL = 15
PROCESSOR_REVISION = 0209
CLIENTNAME = Console
lib = C:\Program Files\IBM\WebSphere MQ\bin;C:\Program Files\IBM\WebSphere MQ\tools\lib
ALLUSERSPROFILE = C:\Documents and Settings\All Users
USERDOMAIN = USER-1F32373F0F
OS = Windows_NT
HOMEDRIVE = C:
First Failure Data Capture Symptom Report Completed at 2009年11月6日 11:18:15
|
Could any expert help me?
Thanks. |
|
| 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
|
|
|
|
