Bug 1158827 - LevelDB Test clearTempDir throws NullPointerException on all Enviroments
Summary: LevelDB Test clearTempDir throws NullPointerException on all Enviroments
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan
Version: 6.4.0,6.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 6.4.0
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-30 10:20 UTC by Roman Macor
Modified: 2025-02-10 03:43 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:43:26 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-4909 0 Major Resolved Test clearTempDir throws NullPointerException on all Enviroments 2016-09-23 16:18:35 UTC

Description Roman Macor 2014-10-30 10:20:44 UTC
Description of problem:

Infinispan testsuite test org.infinispan.persistence.leveldb.config.ConfigurationTest.clearTempDir throws NullPointerException on all Enviroments.

Full trace log:

java.lang.NullPointerException
	at java.io.File.<init>(File.java:277)
	at org.infinispan.test.TestingUtil.recursiveFileRemove(TestingUtil.java:566)
	at org.infinispan.persistence.leveldb.config.ConfigurationTest.clearTempDir(ConfigurationTest.java:44)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
	at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564)
	at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213)
	at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:138)
	at org.testng.TestRunner.afterRun(TestRunner.java:1021)
	at org.testng.TestRunner.run(TestRunner.java:621)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
	at org.testng.SuiteRunner.access$000(SuiteRunner.java:37)
	at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368)
	at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	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:745)

Comment 2 Tomas Sykora 2015-05-06 05:15:03 UTC
I can see this one now in JDG 6.5.0.ER3 on RHEL x86_64

This is OK on my Fedora 20, fc20.x86_64

Comment 3 Tomas Sykora 2015-05-06 08:00:00 UTC
Setting BZ issue component version to 6.5.0, to reflect it started to make troubles now, with ER3, again. 
(I am reffering to jdg-functional-tests running in Hudson. I can't spot the problem locally.)

Comment 4 JBoss JIRA Server 2016-09-23 16:18:36 UTC
Dan Berindei <dberinde> updated the status of jira ISPN-4909 to Resolved

Comment 5 Red Hat Bugzilla 2025-02-10 03:43:26 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.


Note You need to log in before you can comment on or make changes to this bug.