[JIRA] Issue Comment Edited: (MQ-294) improvement in handling "Bad Sysmessage ID" exception during processing messages after takeover

  • From: "amyk (JIRA)" <jira-no-reply@...>
  • To: issues@...
  • Subject: [JIRA] Issue Comment Edited: (MQ-294) improvement in handling "Bad Sysmessage ID" exception during processing messages after takeover
  • Date: Mon, 8 Jul 2013 19:29:14 +0000 (UTC)
  • Auto-submitted: auto-generated


    [ 
https://java.net/jira/browse/MQ-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=366088#action_366088
 ] 

amyk edited comment on MQ-294 at 7/8/13 7:27 PM:
-------------------------------------------------

This has been addressed in 5.0.1, 4.5u2p3 and 4.4u2p9 to workaround this 
particular "Bad Sysmessage ID" exception due to database corruption when it 
occurs on takeover processing, 
- First the broker will try to recover the real SysMessageID from the packet 
data in the MESSAGE column
- If the packet data corrupted as well,  the packet data is read as byte[] 
and placed in a BytesMessage body in DMQ, then the "bad Sysmessage ID" row is 
removed.  The following DMQ message properties will contain details
JMS_SUN_MQ_UNDELIVERED_EXCEPTION
JMS_SUN_MQ_UNDELIVERED_COMMENT

test cases
tonga/jmsserver/ha/badsysid/badsysid_goodpkt
tonga/jmsserver/ha/badsysid/badsysid_badpkt


      was (Author: amyk):
    fixed in 5.0.1, and test cases
tonga/jmsserver/ha/badsysid/badsysid_goodpkt
tonga/jmsserver/ha/badsysid/badsysid_badpkt

  
> improvement in handling "Bad Sysmessage ID" exception during processing 
> messages after takeover
> -----------------------------------------------------------------------------------------------
>
>                 Key: MQ-294
>                 URL: https://java.net/jira/browse/MQ-294
>             Project: mq
>          Issue Type: Improvement
>          Components: broker-core
>    Affects Versions: 4.1, 4.2, 4.3, 4.4, 4.4u1, 4.4u2, 4.5, 4.5.1, 4.5.2
>            Reporter: amyk
>            Assignee: amyk
>             Fix For: 5.0.1 (RI-Bug-Fix)
>
>
> The following "Bad Sysmessage ID", a database corruption, exception caused 
> the processing of the 29 tookover store sessions aborted.
> [11/Apr/2013:15:27:46 PDT] Taking over 29 store sessions from broker OP3A: 
> [1488221239986032896, 5586220265278418432, 8049963995445706496, 
> 9082979074575872256, 7791008938799758592, 7416084340418864640, 
> 6634991214383628288, 4495499917085071104, 2815657317436625152, 
> 7625220200722065664, 6016872143819836928, 624656035789557504, 
> 5096730528590142976, 4170114906992881664, 2581474891339070464, 
> 2264529266832214784, 8856671297772396032, 8660203733056411904, 
> 8390553822889987072, 359788083488415232, 737812642772529664, 
> 4814415888378023168, 768771313556431616, 4737008610143260416, 
> 7977343474343682304, 8373380688469237504, 2941195182957275136, 
> 3392399556327095040, 337833037512803840]
> [11/Apr/2013:15:27:46 PDT] [B1217]: Takeover of broker OP3A was successful, 
> processing data and state information owned by that broker
> [11/Apr/2013:15:27:46 PDT] [B1218]: Processing 3981 transactions from 
> broker OP3A
> [11/Apr/2013:15:27:46 PDT] [B1297]: Processing 0 remote transactions from 
> broker OP3A
> [11/Apr/2013:15:27:47 PDT] ERROR [B3244]: Exception during processing 
> takeover data from OP3A[StoreSession:4814415888378023168], 
> 8229833343271380736, 1365719206983, (4):
> java.lang.RuntimeException: Bad Sysmessage ID
>         at com.sun.messaging.jmq.io.SysMessageID.get(SysMessageID.java:166)
>         at 
> com.sun.messaging.jmq.jmsserver.core.Destination.remoteCheckTakeoverMsgs(Destination.java:3611)
>         at 
> com.sun.messaging.jmq.jmsserver.service.HAMonitorService$TakeoverThread.doTakeover(HAMonitorService.java:979)
>         at 
> com.sun.messaging.jmq.jmsserver.service.HAMonitorService$TakeoverThread.run(HAMonitorService.java:924)
>         at java.lang.Thread.run(Thread.java:662)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://java.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[JIRA] Issue Comment Edited: (MQ-294) improvement in handling "Bad Sysmessage ID" exception during processing messages after takeover

amyk (JIRA) 07/08/2013
Terms of Use; Privacy Policy; Copyright ©2013-2016 (revision 20160708.bf2ac18)
 
 
Close
loading
Please Confirm
Close