Adam,
We have tried logging on and off. Today this worked. I am sure I
remembered restarting the mifos service/daemon and my college agrees. I
meant to say service below not server.
To recreate:
- Logon with mifos userid
- Wait for at least 30 minutes. We have seen the problem happen as soon as
15 minutes or as long as around 30 minutes.
- Select link: Admin
- Select Link: Define new user
- Select Link: Mifos HO
- We then get an HTTP 500 Error
We can recreate this every time. There some links that work, but many cause
this error. All the pages I tried are JSP pages. We get this problem on all
our Linux and our XP systems. Our systems are with 10 days of current, my
system was updated today.
A log snip-it when the Http 500 error happens:
2007-11-13 21:03:28,260 INFO [STDOUT] 21:03:28,260 ERROR [[jsp]]
Servlet.service() for servlet jsp threw exception
java.lang.NullPointerException
at
org.mifos.application.rolesandpermission.struts.tag.ActivityTag.doEndTag(Act
ivityTag.java:37)
Each error generated a NullPointerException. It looks to be JSP/strut/user
context related. I have never worked with JSP or struts, so I am not sure.
All the lines that generated the null pointer exceptions all have in common
a reference to the users context. For example:
userContext.getLocaleId()
getOffice(userContext.getBranchId()
getUserContext(request).getLocaleId()
Does this generate any thoughts?
In preparation for this email I wanted to be sure of what I was saying here
was correct. This time the http 500 errors came immediately after Mifos
start and just after logging on.
Thanks, Gary
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Adam
Monsen
Sent: Tuesday, November 13, 2007 5:56 PM
To: [email protected]
Subject: Re: [Mifos-developer] Time outs
On Nov 12, 3:01 pm, "Gary Weberg" <[EMAIL PROTECTED]> wrote:
[...]
> One that is causing the http 500 error (issue 1475). This could be
> connected to the normal client logon session time-out. Again this error
> displayed to the client requires a restart of the server to clear.
[...]
Are you sure a server restart is required after this particular time
out (or whatever it is) is encountered? I am able to simply close and
restart my browser to work around issue 1475. If you have a repro that
requres a server restart, it would potentially indicate the problem is
more serious.
--
Adam Monsen
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
