![[Topic]](/images/icons/record_topic.png) Unable to start new 0.7d server
I just upgraded my AT installation from 0.7c to 0.7d. Since I upgraded the server, I am unable to start the server in either console or daemon mode. Is anyone else having this problem?
Here's a snippet from the logs concerning the error:
INFO | jvm 1 | 2006/10/11 15:43:45 | WrapperSimpleApp: Encountered an error running main: java.lang.NullPointerException
INFO | jvm 1 | 2006/10/11 15:43:45 | java.lang.NullPointerException
INFO | jvm 1 | 2006/10/11 15:43:45 | at agiletrack.server.http.TrackerHttpServer.<init>(TrackerHttpServer.java:38)
INFO | jvm 1 | 2006/10/11 15:43:45 | at agiletrack.server.ServerApplication.main(ServerApplication.java:271)
INFO | jvm 1 | 2006/10/11 15:43:45 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
INFO | jvm 1 | 2006/10/11 15:43:45 | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
INFO | jvm 1 | 2006/10/11 15:43:45 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
INFO | jvm 1 | 2006/10/11 15:43:45 | at java.lang.reflect.Method.invoke(Method.java:585)
INFO | jvm 1 | 2006/10/11 15:43:45 | at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:136)
INFO | jvm 1 | 2006/10/11 15:43:45 | at java.lang.Thread.run(Thread.java:595)
STATUS | wrapper | 2006/10/11 15:43:47 | <—Wrapper Stopped
—Posted by Aaron Molenaur on Oct 11, 2006
|
|
I experience the same problem on one installation and discovered it's due to a fix which was supposed to get HTTP access logs working again. There are two solutions.
1. Put an access_log option in the agiletrack.conf. That can be done by editing the config file directly, or running the server GUI configuration utility. The access_log path should look something like this—"logs/agiletrack".
2. Because of the severity of the problem, I've rebuilt the agiletrack-server.jar and it's now available to download from http://agiletrack.org/download/agiletrack-server.jar . Just Replace the existing agiletrack-server.jar in the lib directory and the problem should go away.
—Posted by Adam Lane on Oct 11, 2006 at 7:51:03 PM
I tried option 1 and that did not resolve the problem, however replacing the jar file with the updated version allowed the server to start as expected.
Things appear to be working normally again.
—Posted by Aaron Molenaur on Oct 12, 2006 at 11:39:02 AM
