| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Access violation at address FFFFFFFF when reading |
« View previous topic :: View next topic » |
| Author |
Message
|
| Inforz |
 Posted: Thu May 17, 2018 5:37 am Post subject: Access violation at address FFFFFFFF when reading |
 |
|
Centurion
Joined: 15 Apr 2011
Posts: 139
Location: Chennai, India
|
Hi,
We are running MQ 6.0.2.12 in Windows 2003 server. We are getting Access violation error as seen in the below FDC generated.
===============
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Thu May 17 14:12:12 GMT Daylight Time 2018 |
| Host Name :- SGB87516VST (Windows Server 2003, Build 3790: Service |
| Pack 2) |
| PIDS :- 5724H7200 |
| LVLS :- 6.0.2.12 |
| 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.36.1.3 |
| Line Number :- 916 |
| Build Date :- Dec 5 2012 |
| CMVC level :- p600-212-121205 |
| Build Type :- IKAP - (Production) |
| UserID :- mqservice2 |
| Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\amqrmppa.exe |
| Addressing mode :- 32-bit |
| Process :- 00009308 |
| Thread :- 00000002 |
| QueueManager :- SGB87516VST |
| ConnId(1) IPCC :- 107 |
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred |
| (Access Violation at address FFFFFFFF when reading) |
| FDCSequenceNumber :- 0 |
| Comment1 :- Access Violation at address FFFFFFFF when reading |
===============
The version is out of support and we have informed the same to our customer. They are ok for the risk.
The messages are not received by MQ after this error and the cluster sender channel is in inactive state always.
Please suggest. |
|
| Back to top |
|
 |
| exerk |
| Posted: Thu May 17, 2018 6:04 am Post subject: Re: Access violation at address FFFFFFFF when reading |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| Inforz wrote: |
| ...The version is out of support and we have informed the same to our customer. They are ok for the risk... |
Go back to your customer and inform them that the risk they took is a bad one...
...and there are plenty of hits on Google for that Probe Id.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu May 17, 2018 4:19 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
Did this only happen once, or is it reproducable? What does the MQ function call stack show it is doing just before the memory access violation? Looks like a bad pointer or offset.
_________________
Glenn |
|
| 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
|
|
|
|
