[Mifos-developer] Mifos - session timeout

[soham]

Hi,

I am trying to run mifos. I checked out the recent code, built it and am deploying it with JBoss. I can login with "mifos/testmifos" but once i get to the main page, if i click on any of the navigation menu's (e.g reports) i get logged out and the following message is displayed

"The user session has expired. Please login again to access the application."

 

I also tried using jetty instead of Jboss but still get the same message.

 

any help would be apprecitated.

 

Operating system: Win XP

JDK 6u2

AS: Jboss 4.2

 

 

Thanks

Soham

 

 

[Tom Bostelmann]

Do we have documentation that talks about supported platforms? What
is the test server running on?

> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
>

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

[Jim Kingdon]

> "The user session has expired. Please login again to access the
> application."

The most obvious explanation is that your browser is not set
to allow cookies.

I'm not sure what else would do this, or how to most easily
track it down. Unfortunately, it is a bit of a catch-all
error message, which MIFOS puts up in different situations.

[Van Mittal-Henkle]

Tom Bostelmann wrote:
> Do we have documentation that talks about supported platforms? What
> is the test server running on?

The Mifos README file
(https://mifos.dev.java.net/source/browse/mifos/trunk/mifos/README?rev=11643&v
iew=log) contains information about supported tools. There are instructions
at http://wiki.java.net/bin/view/Javatools/InstallMifos relating to installing
Mifos on Windows and Linux. If by "platforms" you mean OS versions, then I'm
not aware that such a list has been compiled (and we would need to define what
we mean by "supported platforms" :-)

As for the test server, it is currently running on:

Windows Server 2003
512 MB RAM, 2.66GHz P4 Processor
Current Mifos War - Rev 11943 (updated Friday, July 20th)
JBoss - 4.1 or Jetty - 6.1.3
MySQL - 4.1
Java JDK - 1.5.0_06

The configuration for the test server is likely to change in the near future,
but this is what we're running on now.

--Van

-------------------------------------------------------------------------
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/

[Tom Bostelmann]

By "supported platform" I meant everything - hardware, OS, JVM, Java
containers, MySQL versions, etc.

I was asking mainly because we were getting into requiring large heap
sizes for some of the reports (in excess of 512MB for max heap).

>From asking around a little it sounds like we're trying to be somewhat
platform agnostic. This is fine, however, it might be a good idea to
at least 'suggest' a platform based on what our test server is running
on (since our tests generally run on this). But this may become
problematic when testing some of the reports since the test server
only has 512mb RAM.

[Van Mittal-Henkle]

Tom Bostelmann wrote:
> By "supported platform" I meant everything - hardware, OS, JVM, Java
> containers, MySQL versions, etc.
>
> I was asking mainly because we were getting into requiring large heap
> sizes for some of the reports (in excess of 512MB for max heap).
>
>> From asking around a little it sounds like we're trying to be
>> somewhat
> platform agnostic. This is fine, however, it might be a good idea to
> at least 'suggest' a platform based on what our test server is
> running on (since our tests generally run on this). But this may
> become problematic when testing some of the reports since the test
> server only has 512mb RAM.

One note is that when we mention our "test server" it refers to a server which
is running a live instance of Mifos that can be used to test out Mifos
functionality. Our "build server" is the machine that actually runs the builds
(which includes running the test suite). The "build server" is currently in
the process of being migrated to a new host (but currently also has the 512Mb
RAM limit)

[Tom Bostelmann]

Here's a possible section addition to the README. I'm not suggesting
that this will stick for long - it's just good to have this out there
to communicate some basic design constraints.

--------------------
Recommended Platform
--------------------

2 GHz Processor (or better)
1 GB RAM (or more)
10 GB Hard Drive Space (or more)

JBoss - 4.1 or Jetty - 6.1.3
MySQL - 4.1
Java JDK - 1.5.0_06

I'd also recommend that we update it when the test servers have been
upgraded. The 'recommended platform' should match the platform that
we're using to test/build on.

[Aliya Walji]

Tom,

When you are mentioning recommended platform, you talking about
recommended for 'development' purposes or for deployment purposes? The
recommendations may be different for each scenario.

If you add the section below to the Wiki, you should be specific that
the hardware recommendations you are making are not necessarily for
deployment purposes. We already have some suggestions on hardware for
deployments at MFIs
(http://wiki.java.net/bin/view/Javatools/MifosInfrastructureRequirements
)

Aliya

[Tom Bostelmann]

Good point - how about this then?

--------------------
Recommended Platform
--------------------

2 GHz Processor (or better)
1 GB RAM (or more)
10 GB Hard Drive Space (or more)
JBoss - 4.1 or Jetty - 6.1.3
MySQL - 4.1
Java JDK - 1.5.0_06

NOTE: The hardware recommended is for development and testing. See
the following wiki for production installation recommendations:

http://wiki.java.net/bin/view/Javatools/MifosInfrastructureRequirements

[Van Mittal-Henkle]

I would echo Aliya's distinction between development and deployment platforms.

Also, before making a recommendation, I would argue that some investigation is
required. For example, I'm not sure why we are running Jboss 4.1 rather than
4.2-- a quick look at the jboss site and it appears that 4.1 is no longer
available for download.

For MySQL, I'm not sure why we are still running 4.1 rather than using 5.0.

For the JDK, 1.6 is now available.

The most likely reason that more recent versions are not being run is a matter
of resource availability. They probably should be upgraded.

So if we were to make a recommendation, these versions could be given as "xyz
version or later".

--Van

-------------------------------------------------------------------------

[Aliya Walji]

Agreed that we should investigate the versions we recommend and make
recommendations based on consideration rather than just based on what is
on the test server. We will be upgrading the test server soon in any
case, so the versions will all change to more recent versions of all of
the software.

> For MySQL, I'm not sure why we are still running 4.1 rather than using
> 5.0.

This is because the prior version of reporting (in Jasper) only seemed
to work with 4.1. This makes me realize that when we have regular
releases of Mifos tagged, we will probably have to indicate compatible
versions of supporting software for each release/version.

[Aliya Walji]

> For the JDK, 1.6 is now available.

One other note I forgot to mention on the JDK version. We have a JBoss
profiling tool that Amit suggested for being able to dig deeper to
investigate issues and this tool only supports JDK 1.5, if I'm not
mistaken. It's something to consider when we are recommending versions
of the JDK to use for dev purposes and deployment purposes.

[Van Mittal-Henkle]

> This makes me realize that when we have
> regular releases of Mifos tagged, we will probably have to indicate
> compatible versions of supporting software for each release/version.

Yes. We will want to get to a point where we can say that a given set of
component versions are all compatible and verified to work together (which I
think is what Tom is getting at).

We still have a few more steps to take before we are at the point of being
able to do this in a well defined way, but it is good thing to start taking
those steps.

[Tom Bostelmann]

I agree with this, however, at this point we cannot technically say
that we support any of these recommendations because we aren't
consistently running our full suite of automated tests on this
specification.

When you 'recommend' or 'support' a specific platform, technically
you're saying that you've tested the specification. Inversely you
want to let the development community know what you are testing on so
that they have some boundaries for design (i.e automated tests don't
fail because they ran out of memory).

Recommending the platform that we test on may be limiting at this
point, but it communicates, at a minimum, what we know. And, most of
all, it doesn't require any resources right now ;)

On 7/25/07, Aliya Walji <awa...@grameenfoundation.org> wrote:

[Tom Bostelmann]

agreed. this is mainly why i'm suggesting we just use our test/build
server spec for now. at least we're communicating something.

On 7/25/07, Van Mittal-Henkle <van...@comcast.net> wrote: