[jboss-jira] [JBoss JIRA] Resolved: (JGRP-363) GossipRouter classpath error message is misleading

[Bela Ban (JIRA)]

     [ http://jira.jboss.com/jira/browse/JGRP-363?page=all ]

Bela Ban resolved JGRP-363.
---------------------------

    Resolution: Won't Fix

In 2.5, concurrent.jar is not needed anymore.

I will not fix this in 2.4, unless this is absolutely necessary. The workaround - as you said - is know, so no high priority in either case

> GossipRouter classpath error message is misleading
> --------------------------------------------------
>
>                 Key: JGRP-363
>                 URL: http://jira.jboss.com/jira/browse/JGRP-363
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.4
>            Reporter: Jerry Gauthier
>         Assigned To: Bela Ban
>            Priority: Minor
>             Fix For: 2.5
>
>
> If you start the GossipRouter without concurrent.jar on the classpath, a NoClassDefFoundError exception will occur.  However this information is hidden by GossipRouter error handing and the user is presented with the cryptic message:  "failed reading the magic number mapping file."
> I think there are severl ways to improve this situation.
> 1)  Update the GossipRouter example in the JGroups documentation to show what jars need to be on the classpath.
> 2)  Modify the GossipRouter or ClassConfigurator to reveal the underlying problem.
> Note that this error occurs when you start the GossipRouter per the doc without adding concurrent.jar to the classpath.

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