[infinispan-issues] [JBoss JIRA] (ISPN-2145) No descriptions for invalid jgroups configuration files

[Sanne Grinovero (JIRA)]

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

Sanne Grinovero commented on ISPN-2145:
---------------------------------------

This isn't fixed yet, when starting with an invalid JGroups configuration I get:

{noformat}
Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.transaction.TransactionTable.start() on object of type TransactionTable
	at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:185)
	at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:869)
	at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:638)
	at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:627)
	at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:530)
	at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:216)
	at org.infinispan.CacheImpl.start(CacheImpl.java:686)
	at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:567)
	at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:522)
	at org.infinispan.manager.DefaultCacheManager.access$100(DefaultCacheManager.java:106)
	at org.infinispan.manager.DefaultCacheManager$1.run(DefaultCacheManager.java:431)
Caused by: java.lang.NullPointerException
	at org.infinispan.transaction.TransactionTable$1.newThread(TransactionTable.java:132)
	at java.util.concurrent.ThreadPoolExecutor.addThread(ThreadPoolExecutor.java:670)
	at java.util.concurrent.ThreadPoolExecutor.addIfUnderCorePoolSize(ThreadPoolExecutor.java:706)
	at java.util.concurrent.ThreadPoolExecutor.prestartCoreThread(ThreadPoolExecutor.java:1387)
	at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:222)
	at java.util.concurrent.ScheduledThreadPoolExecutor.scheduleAtFixedRate(ScheduledThreadPoolExecutor.java:426)
	at java.util.concurrent.Executors$DelegatedScheduledExecutorService.scheduleAtFixedRate(Executors.java:656)
	at org.infinispan.transaction.TransactionTable.start(TransactionTable.java:142)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:183)
	... 10 more
{noformat}

which is misleading and not too helpful
                
> No descriptions for invalid jgroups configuration files
> -------------------------------------------------------
>
>                 Key: ISPN-2145
>                 URL: https://issues.jboss.org/browse/ISPN-2145
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Configuration
>    Affects Versions: 5.1.2.FINAL
>         Environment: Windows 7
>            Reporter: Dmitry Udalov
>            Assignee: Manik Surtani
>
> Can't find error's description for invalid jgroups configuration files. Shuffling elements of the file (why not!) makes it invalid, but log-files only report the existence of the error and you have to debug it to figure out the problem. It would be easier if the class JGroupsTransport also reports the exception, not just a generic message in blocks like
>     } catch (Exception e) {
>       log.errorCreatingChannelFromConfigFile(cfg);
>       throw new CacheException(e);
>     }
> As a result log-file contains a lot of generic messages without explaining the problem, which in my case was quite helpful:
> java.lang.Exception: events [GET_DIGEST SET_DIGEST FIND_INITIAL_MBRS FIND_ALL_VIEWS ] are required by GMS, but not provided by any of the protocols below it

--
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