| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Message Exit |
« View previous topic :: View next topic » |
| Author |
Message
|
| Neo_47 |
 Posted: Thu Jun 02, 2011 7:17 am Post subject: |
 |
|
Newbie
Joined: 02 Jun 2011
Posts: 7
|
| Quote: |
Run-time errors? If so, copy/paste results here so we can see what failed. What ReasonCode(s)? |
No Compile Time errors. But the channel goes in Retrying State with a FDC as below :
| |
| Date/Time :- Thu June 02 2011 15:09:10 GMT |
| UTC Time :- 1307027350.029838 |
| UTC Time Offset :- 60 (GMT) |
| Host Name :- linux-brot |
| Operating System :- Linux 2.6.34.7-0.7-desktop |
| PIDS :- 5724H7224 |
| LVLS :- 7.0.1.2 |
| Product Long Name :- WebSphere MQ for Linux (x86 platform) |
| Vendor :- IBM |
| Probe Id :- XC130003 |
| Application Name :- MQM |
| Component :- xehExceptionHandler |
| SCCS Info :- lib/cs/unix/amqxerrx.c, 1.242.1.2 |
| Line Number :- 1386 |
| Build Date :- May 6 2010 |
| CMVC level :- p701-102-100504 |
| Build Type :- IKAP - (Production) |
| Effective UserID :- 1000 (mqm) |
| Real UserID :- 1000 (mqm) |
| Program Name :- amqrmppa |
| Addressing mode :- 32-bit |
| Process :- 13492 |
| Process(Thread) :- 13496 |
| Thread :- 5 |
| ThreadingModel :- PosixThreads |
| QueueManager :- QM2 |
| UserApp :- FALSE |
| ConnId(1) IPCC :- 226 |
| Last HQC :- 1.0.0-251796 |
| Last HSHMEMB :- 0.0.0-0 |
| Major Errorcode :- STOP |
| Minor Errorcode :- OK |
| Probe Type :- HALT6109 |
| Probe Severity :- 1 |
| Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 11 (0xb) |
| Comment1 :- SIGSEGV: address not mapped(0x98) |
O/S Call Stack for current thread
/opt/mqm/lib/libmqmcs_r.so(xcsPrintStackForCurrentThread+0xa1)[0xb7200f21]
/opt/mqm/lib/libmqmcs_r.so(signalHandlerInternal+0x55)[0xb7216335]
/opt/mqm/lib/libmqmcs_r.so(PrepareDumpAreas+0x81c)[0xb7214fbc]
/opt/mqm/lib/libmqmcs_r.so(xcsFFSTFn+0x21d3)[0xb7218d03]
/opt/mqm/lib/libmqmcs_r.so(xehExceptionHandler+0x45c)[0xb721300c]
[0xffffe40c]
/opt/mqm/lib/libmqmr_r.so(+0xf2ed3)[0xb76c1ed3]
/opt/mqm/lib/libmqmr_r.so(rriInitExits+0x411)[0xb76c6891]
/opt/mqm/lib/libmqmr_r.so(rriAcceptSessReceive+0x2163)[0xb7717e73]
/opt/mqm/lib/libmqmr_r.so(rriAcceptSess+0x4ac)[0xb77194cc]
/opt/mqm/lib/libmqmr_r.so(rrxResponder+0x141)[0xb7714cf1]
/opt/mqm/lib/libmqmr_r.so(ccxResponder+0x1eb)[0xb75f476b]
/opt/mqm/lib/libmqmr_r.so(cciResponderThread+0xaf)[0xb75f493f]
/opt/mqm/lib/libmqmcs_r.so(+0xa8c0d)[0xb726bc0d]
/lib/libpthread.so.0(+0x59a0)[0xb71919a0]
/lib/libc.so.6(clone+0x5e)[0xb70efc4e] |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Thu Jun 02, 2011 7:30 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Lots of hits on google for Probe Type :- HALT6109
_________________
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 |
|
|
| gbaddeley |
| Posted: Thu Jun 02, 2011 3:54 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| Neo_47 wrote: |
| | Comment1 :- SIGSEGV: address not mapped(0x98) |
This is the classic symptom for invalid use of a pointer in an MQ exit on UNIX. MQ does not produce any diagnostics on where in the exit code the invalid use occurs.
I suggest that you add a debug file capability to your exit and dump out various things to confirm that pointers and data are as you expect.
Always test the validity of pointers and the structure id's before trying to use them.
MQ exit programming is an advanced topic. Be prepared to crash and burn many times as you learn how they work.
_________________
Glenn |
|
| Back to top |
|
|
| Neo_47 |
| Posted: Thu Jun 02, 2011 10:42 pm Post subject: |
|
|
Newbie
Joined: 02 Jun 2011
Posts: 7
|
| Quote: |
I suggest that you add a debug file capability to your exit and dump out various things to confirm that pointers and data are as you expect.
|
Thanks !!!. It took sometime for me to figure that out by going through google and found that I am victim of null pointer. Now there are certain fields in the Exit Parameters which are coming as NULL from the sender and when trying accessing them, Things are'nt going well !! 
Have to log the exits flow now. 
| Quote: |
| MQ exit programming is an advanced topic. Be prepared to crash and burn many times as you learn how they work. |
Yes !!!! I agree. Will post here if something comes out for success. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Jun 03, 2011 6:47 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Neo_47 wrote: |
| Quote: |
I suggest that you add a debug file capability to your exit and dump out various things to confirm that pointers and data are as you expect.
|
Thanks !!!. It took sometime for me to figure that out by going through google and found that I am victim of null pointer. Now there are certain fields in the Exit Parameters which are coming as NULL from the sender and when trying accessing them, Things are'nt going well !!
Have to log the exits flow now.
| Quote: |
| MQ exit programming is an advanced topic. Be prepared to crash and burn many times as you learn how they work. |
Yes !!!! I agree. Will post here if something comes out for success. |
You are simultaneously the victim and the perpetrator of the null pointer. Good programming dictates that your code should be testing values to ensure that they are valid for the function your code is about to undertake.
_________________
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 |
|
|
|
|
|
|
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
|
|
|
|
