ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ API Support » Why does MQSeries VB DLL fails intermittently?

Post new topic  Reply to topic
 Why does MQSeries VB DLL fails intermittently? « View previous topic :: View next topic » 
Author Message
farteau
PostPosted: Thu Nov 29, 2001 8:29 am    Post subject: Reply with quote

Newbie

Joined: 27 Nov 2001
Posts: 2
Location: Quebec (Canada)

I am using a VB DLL that I register into MTS to call MQ Client 5.1 on Win NT4 ( SP6a ) server. The DLL is invoked from an ASP page.

Approximately 0.1% to 0.5% of calls to this DLL result in "out of memory" error returned by the MQSeries component.

The problem is very difficult to reproduce, but I have to fix it.

When it happens, this mesage appears in NT Event viewer :

Event ID : 4101
Source : Transaction Server
Type : Error
Category : Context Wrapper
Details :
An object call caused an exception. (Package: DEBUG-MQSERIES) (ProgId: DebugMQSeriesAPART.Client) (CLSID: {AF8F2C5D-B9F9-46CA-998C-D6673C877DC0}) (Interface: Client) (IID: {97A6CF13-4204-4351-9EE3-8455589A3EEC}) (Method: 7) (Microsoft Transaction Server Internals Information: File: i:vipersrcruntimecwcwlib.cpp, Line: 935) (Exception: C0000005) (Address: 0x015411be)
AMQRMQIA!zstMQCONNX + 0x18E


Anyone any ideas ? Is this a known issue with problems regarding threading with MQ Series client?
Back to top
View user's profile Send private message Send e-mail Visit poster's website
sanvaranasi
PostPosted: Thu Mar 18, 2004 9:03 pm    Post subject: Any Solution. I am facing a similar problem Reply with quote

Novice

Joined: 24 Feb 2004
Posts: 10
Location: india

Hi Farteau,

I am facing a similar problem. HAve you found a solution yet.

I am having a ATL COM componenet that is deployed under IIS. I have WebphsereMQ5.3 server version installed on the same machine. Sometimes i get this exception stated below and all reads from queue stop (the component is actually used only for reading from queue. It does not happen always. The log generated in event viewer is as follows:

The system has called a custom component and that component has failed and generated an exception. This indicates a problem with the custom component. Notify the developer of this component that a failure has occurred and provide them with the information below.
Component Prog ID:
Server Application ID: {910F8FCF-B61C-4A21-A73E-C269EA5D2035}
Server Application Name: QLMMqComp
The serious nature of this error has caused the process to terminate.
Exception: C0000005
Address: 0x7800FA97
Call Stack:
MSVCRT!setvbuf + 0x7CC
...
....
Back to top
View user's profile Send private message
JasonE
PostPosted: Fri Mar 19, 2004 2:20 am    Post subject: Reply with quote

Grand Master

Joined: 03 Nov 2003
Posts: 1220
Location: Hursley

farteau - Yours is almost definitely caused by a coding issue.

An MQCONN(X) takes as a parameter an MQCHAR42, and may try to read all 42 bytes. I would bet you are doing something like MQCONN("QM",... or MQCONNX("",... or MQCONN(fred,... where fred is a String. VB has a habit of putting these variables very intermittently near a page boundary, and the subsequent page is not readable. It results in a trap in amqrmqia at around offset 1b7 (depending on the version, release and fixpack level, so 0x18? is almost certainly the match)

The solutions...
1. Ensure the parameter is as defined to the C layer, ie
Dim qmname as String * 48
qmname = "fred"
MQCONN(qmname,...

2. Apply a recent fix level - I changed it to tollerate null terminated strings via an APAR which should work most of the time

contact admin - Yours sounds different, you didnt put enough call stack in to see what MQ function the trap is occurring in. MSVCRT is just the C runtime!
Back to top
View user's profile Send private message
sanvaranasi
PostPosted: Fri Mar 19, 2004 2:32 am    Post subject: Reply with quote

Novice

Joined: 24 Feb 2004
Posts: 10
Location: india

ok i figured out the problem. i was trying to format a MQLong to CString using %s rather than %d

So the point where it was bombing was written as under

CString szReasonCode;
szReasonCode.format("Mq returned Reason Code %s", MQ_REASON_CODE);
where MQ_REASON_CODE is a variable holding MQLong value.

I corrected it to %d.

For reference here is the complete error that i was getting.
-------------------------------------------------------------------
Component Prog ID:
Server Application ID: {910F8FCF-B61C-4A21-A73E-C269EA5D2035}
Server Application Name: QLMMqComp
The serious nature of this error has caused the process to terminate.
Exception: C0000005
Address: 0x7800FA97
Call Stack:
MSVCRT!setvbuf + 0x7CC
MSVCRT!vsprintf + 0x2D
MFC42!Ordinal2827 + 0x348
MFC42!Ordinal2818 + 0x12
RPCRT4!NdrServerMarshall + 0x12F6
RPCRT4 + 0x65AD7
RPCRT4!CStdStubBuffer_Invoke + 0x6B
OLEAUT32!UserEXCEPINFO_free_local + 0x20F4
ole32!WdtpInterfacePointer_UserSize + 0x980
ole32!UpdateDCOMSettings + 0xB136
ole32!CoGetPSClsid + 0x1007
ole32!CoGetPSClsid + 0xE71
ole32!WdtpInterfacePointer_UserSize + 0x55D
ole32!WdtpInterfacePointer_UserSize + 0xCB5
ole32!WdtpInterfacePointer_UserSize + 0x9F8
ole32!UpdateDCOMSettings + 0x75FC
USER32!SetWindowPlacement + 0x50
USER32!TranslateMessageEx + 0x605
USER32!DispatchMessageW + 0xB
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
+ 0xA8FB8
COMSVCS + 0x128960
+ 0x7F2A8
+ 0x9F8A8
+ 0xA5FF8
+ 0x9AB00
+ 0xA01B8
+ 0xA6880
+ 0xA66B0
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ API Support » Why does MQSeries VB DLL fails intermittently?
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.