| Author |
Message
|
| santeciafardoni |
 Posted: Sun Mar 04, 2012 8:24 am Post subject: XMS - NullReferenceException at IBM.WMQ.Nmqi.UnmanagedNmqiMQ |
 |
|
Novice
Joined: 04 Mar 2012
Posts: 13
|
Dear All, thanks in advance for your time.
We experienced the issue in subject building an Enterprise Async Pool that sends and gets messages to a WMB.
We are using amqmdnet.dll 7.0.1.7 and several machine shows the same behaviour.
During stability test, randomly, clients stops working and shows this message, while MQ errors dump is:
As a result of a Severe Abend Error, a MiniDump has been written to: AMQ6048.5392.0.dmp
An Unhandled Exception detected in process 6048, on thread 0x1510.
Type: EXCEPTION_ACCESS_VIOLATION (C0000005).
Address: 0023:05B4164D.
The thread could not read from memory address 0x00000000.
Does anyone experienced the same issue ?
Sante. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Sun Mar 04, 2012 8:49 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Was an FDC created for this?
Did you search google? There a number of hits for AMQ6048.
_________________
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 |
|
|
| santeciafardoni |
| Posted: Sun Mar 04, 2012 9:10 am Post subject: |
|
|
Novice
Joined: 04 Mar 2012
Posts: 13
|
Hi Bruce,
yes, it was an FDC what I have reported in italic,
Yep I have searched a lot, but found nothing.
Seems to me that AMQ6046 is a conversion error, I dont think is related to this scenario. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Mar 04, 2012 9:15 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Please post the first 30+ lines of the FDC.
Look for probe point. Search google for the probe point id.
_________________
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 |
|
|
| santeciafardoni |
| Posted: Sun Mar 04, 2012 9:22 am Post subject: |
|
|
Novice
Joined: 04 Mar 2012
Posts: 13
|
Got it.
Operating System :- Windows Ver 6.1 (5) Enterprise x64 Edition, Build 7600
PIDS :- 5724H7220
LVLS :- 7.0.1.7
Product Long Name :- WebSphere MQ for Windows
Vendor :- IBM
Probe Id :- XC130031
Application Name :- MQM
Component :- xehExceptionHandler
SCCS Info :- lib/cs/pc/winnt/amqxerrn.c, 1.44.1.1
Line Number :- 761
Build Date :- Nov 17 2011
CMVC level :- p701-107-111117
Build Type :- IKAP - (Production)
UserID :- c012382
Process Name :- xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Addressing mode :- 32-bit
Process :- 00011980
Thread :- 00000175
UserApp :- TRUE
Last HQC :- 0.0.0-0
Last HSHMEMB :- 0.0.0-0
Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC
Minor Errorcode :- OK
Probe Type :- MSGAMQ6119
Probe Severity :- 2
Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred.
FDCSequenceNumber :- 0
Comment1 :- Access Violation at address 00000018 when reading
|
|
| Back to top |
|
|
| Vitor |
| Posted: Sun Mar 04, 2012 9:59 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
I'd verify you (and all of your clients) really are using 7.0.1.7 and do have this available.
I'd then check that none of the .NET is misbehaving is the ways described in other links for that probe id.
Then I'd consider a PMR.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Mar 04, 2012 10:06 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Open a PMR!
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| santeciafardoni |
| Posted: Sun Mar 04, 2012 10:47 am Post subject: |
|
|
Novice
Joined: 04 Mar 2012
Posts: 13
|
Thanks all.
Trying to escalate, actually now I'm using only 2 Client Machine with MQ 7.0.1.7 with always same results.
PS: I have never opened a PMR. Need to know something in particular ? |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Mar 04, 2012 10:48 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| fjb_saper wrote: |
| Open a PMR! |
Is this an expression of surprise? Or affirmation
_________________
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 |
|
|
| santeciafardoni |
| Posted: Sun Mar 04, 2012 10:50 am Post subject: |
|
|
Novice
Joined: 04 Mar 2012
Posts: 13
|
I guess it's a hint  |
|
| Back to top |
|
|
| Vitor |
| Posted: Sun Mar 04, 2012 10:56 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| santeciafardoni wrote: |
| PS: I have never opened a PMR. Need to know something in particular ? |
You'll need the details associated with your site's license to verify you're a licensed user. Whoever manages the IBM account at your site will know this.
You'll also need to be able to describe the problem, how to reproduce the problem and all the MustGather documents listed on the IBM support page.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| santeciafardoni |
| Posted: Sun Mar 04, 2012 11:00 am Post subject: |
|
|
Novice
Joined: 04 Mar 2012
Posts: 13
|
Fine, surely will let you know how things are going.
Please, meanwhile I open a PMR, feel free to share any other hints (if any). |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Mar 04, 2012 12:00 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| santeciafardoni wrote: |
| ... feel free to share any other hints (if any). |
This is basic problem-determination, and not specifically for WMQ problems.
With any application, o/s, or middle-ware, you first identify that there is a problem - by its symptoms.
You begin by documenting the symptoms (program name, o/s-level, WMQ version/release, related software (.NET, etc.).
You determine if the problem can be repeated.
In this instance, you received an error code belonging to WMQ - by the AMQ... error code. You next do some research - by looking for other/related errors logged in the ERRORS directories. You next search google looking to see if there's already a fix for this problem.
Then, you might consider posting here - because we will ask you for the exact same things IBM will ask you for.
_________________
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 |
|
|
| santeciafardoni |
| Posted: Sun Mar 04, 2012 12:26 pm Post subject: |
|
|
Novice
Joined: 04 Mar 2012
Posts: 13
|
Thanks Bruce,
actually is the same pattern we are applying since 1990.
And the repetition (LOL) is the real issue.
The huge skill that I find in this forum drive me to post here and Im sure that now I'm ready to talk with IBM. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Mar 04, 2012 1:08 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| santeciafardoni wrote: |
| actually is the same pattern we are applying since 1990. |
One of the other basic problem-determination questions is: what has changed? IBM will ask you this.
Are you saying that you have had this exact symptom since 1990? If not, what changed?
Is 7.0.1.7 new, and all other hardware/software is unchanged? When, during all the change(s), did the symptom show up? Did the symptom show up during testing?
_________________
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 |
|
|
|
|
