[jboss-jira] [JBoss JIRA] (JGRP-1758) UnknownFormatConversionException in UNICAST3 logging

[Bela Ban (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932818#comment-12932818 ] 

Bela Ban commented on JGRP-1758:
--------------------------------

Note that while the stack trace is meaningless (doesn't show the root cause of an exception), this does not impact the correctness of message delivery, ie. messages are delivered reliably and in the correct order.
                
> UnknownFormatConversionException in UNICAST3 logging
> ----------------------------------------------------
>
>                 Key: JGRP-1758
>                 URL: https://issues.jboss.org/browse/JGRP-1758
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 3.4.1
>            Reporter: Paul Ferraro
>            Assignee: Bela Ban
>            Priority: Critical
>             Fix For: 3.4.2, 3.5
>
>
> When UNICAST3 tries to log a "FailedToDeliverMsg", it translates to the following pattern from jg-messages.properties:
> "JGRP000039: %s: failed to deliver %s %s: %t"
> This causes the following exception (because %t is not a valid conversion token):
> {noformat}
> java.util.UnknownFormatConversionException: Conversion = 't'
>     at java.util.Formatter$FormatSpecifier.<init>(Formatter.java:2690)
>     at java.util.Formatter.parse(Formatter.java:2528)
>     at java.util.Formatter.format(Formatter.java:2469)
>     at java.util.Formatter.format(Formatter.java:2423)
>     at java.lang.String.format(String.java:2797)
>     at org.jboss.logmanager.ExtLogRecord.formatRecord(ExtLogRecord.java:434)
>     at org.jboss.logmanager.ExtLogRecord.getFormattedMessage(ExtLogRecord.java:397)
>     at org.jboss.logmanager.formatters.Formatters$10.renderRaw(Formatters.java:568)
>     at org.jboss.logmanager.formatters.Formatters$JustifyingFormatStep.render(Formatters.java:225)
>     at org.jboss.logmanager.formatters.MultistepFormatter.format(MultistepFormatter.java:86)
>     at org.jboss.logmanager.ExtFormatter.format(ExtFormatter.java:35)
>     at org.jboss.logmanager.handlers.WriterHandler.doPublish(WriterHandler.java:49)
>     at org.jboss.logmanager.ExtHandler.publish(ExtHandler.java:79)
>     at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:296)
>     at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:304)
>     at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:304)
>     at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:304)
>     at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:304)
>     at org.jboss.logmanager.Logger.logRaw(Logger.java:721)
>     at org.jboss.logmanager.Logger.log(Logger.java:672)
>     at org.jboss.logging.JBossLogManagerLogger.doLogf(JBossLogManagerLogger.java:50)
>     at org.jboss.logging.Logger.errorf(Logger.java:1369)
>     at org.jboss.as.clustering.jgroups.LogFactory$LogAdapter.error(LogFactory.java:104)
>     at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:697)
>     at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:381)
>     at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:600)
>     at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:147)
>     at org.jgroups.protocols.FD.up(FD.java:255)
>     at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:301)
>     at org.jgroups.protocols.MERGE2.up(MERGE2.java:209)
>     at org.jgroups.protocols.Discovery.up(Discovery.java:379)
>     at org.jgroups.protocols.MPING.up(MPING.java:181)
>     at org.jgroups.protocols.TP$ProtocolAdapter.up(TP.java:2609)
>     at org.jgroups.protocols.TP.passMessageUp(TP.java:1399)
>     at org.jgroups.protocols.TP$MyHandler.run(TP.java:1585)
>     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>     at java.lang.Thread.run(Thread.java:724)
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira