You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Jacek Laskowski (JIRA)" <ji...@apache.org> on 2006/12/02 11:45:20 UTC
[jira] Created: (OPENEJB-393) Create a web page "Hunting down
issues in OpenEJB" with information on how to hunt down "Cannot stop the
test server: java.lang.NullPointerException null" or alike
Create a web page "Hunting down issues in OpenEJB" with information on how to hunt down "Cannot stop the test server: java.lang.NullPointerException null" or alike
-------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: OPENEJB-393
URL: http://issues.apache.org/jira/browse/OPENEJB-393
Project: OpenEJB
Issue Type: Task
Components: website
Affects Versions: 3.0
Reporter: Jacek Laskowski
We need a page that would outline how to crack down issues with a possibly dangling OpenEJB instance. See Dave's response in the dev mailing list. The page would be called like "Hunting down issues in OpenEJB"
On Dec 1, 2006, at 4:23 PM, Jacek Laskowski wrote:
> On 12/1/06, David Blevins <da...@visi.com> wrote:
>
>> How are things looking for you on this?
>
> Just to add to it - I'm getting the following bizarre error message:
>
> Cannot stop the test server: java.lang.NullPointerException null
>
> Does it ring a bell? Tips and tricks how to hunt it down greatly
> appreciated.
>
Ahh. Maybe you have an openejb process running in the background?
Definitely check the surefire contents relating to the failed test.
So for example:
container/openejb-core/target/surefire-reports/
org.apache.openejb.SpringAssemblerTest.txt
Also, are you doing a brand new check out/build? Definitely want to
make sure you don't have any modifications in your current checkout.
Another thing to try is just delete your ~/.m2/repository/org/apache/
openejb directory as maybe there's some cruft in there. Either that
or do an 'svn status' and look for modified or '?' files that
shouldn't be there -- I've done that more than once.
One last thing if all else fails, if you add a 'logs' directory in i
think 'target/test-classes' then the openejb logs should get output
into there. If that doesn't work you can edit the Log4jConfigUtils
you wrote and tweak the doFallbackConfiguration method and set all
the log levels to debug.
Maybe one of those ideas might lead somewhere -- if you haven't
already tried them that is.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira