[jbossts-issues] [JBoss JIRA] (JBTM-3134) Init store failure could provide more information in the exception than just NullPointer

[Ondrej Chaloupka (Jira)]

     [ https://issues.jboss.org/browse/JBTM-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Issue was automatically transitioned when Ondrej Chaloupka created pull request #1439 in GitHub
-----------------------------------------------------------------------------------------------
    Status: Pull Request Sent  (was: Open)


> Init store failure could provide more information in the exception than just NullPointer
> ----------------------------------------------------------------------------------------
>
>                 Key: JBTM-3134
>                 URL: https://issues.jboss.org/browse/JBTM-3134
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>    Affects Versions: 5.9.5.Final
>            Reporter: Ondrej Chaloupka
>            Assignee: Ondrej Chaloupka
>            Priority: Minor
>
> When `StorageManager` fails with to initialize store instance the error comes as `NullPointerException`. That's not much informative. The exception should says what happens. The example of the exception thrown now is[1]. The more information then is available in the log but still exception should give some basic idea what happens not just `NullPointerException`.
> [1]
> {code}
> java.lang.NullPointerException
>  at com.arjuna.ats.arjuna.objectstore.StoreManager.initStore(StoreManager.java:159)
>  at com.arjuna.ats.arjuna.objectstore.StoreManager.setupStore(StoreManager.java:136)
>  at com.hp.mwtests.ts.arjuna.abstractrecords.CadaverRecordUnitTest.test(CadaverRecordUnitTest.java:49)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  at java.lang.reflect.Method.invoke(Method.java:498)
>  at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
>  at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>  at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
>  at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>  at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
>  at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
>  at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
>  at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>  at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
>  at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
>  at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
>  at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
>  at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
>  at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
>  at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
>  at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236)
>  at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
>  at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:386)
>  at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:323)
>  at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:143)
> {code}



--
This message was sent by Atlassian Jira
(v7.12.1#712002)