[Mifos-users] V 1.5.1

[Polly]

Hello,

The collection sheet in v 1.5.1 is not working properly. On the server we were still using v 1.3. 
We did not upgrade to v1.4. because it was not supporting loans with 0% interest. v1.5 on the test server was working well except that in the collection sheet it was only displaying cells for loans that had amounts that were due whereas in our MFI we have clients paying constantly even where there are no amounts due.
So on Thursday we went ahead and did the upgrade on the server from v 1.3 to v 1.5.1. Now the collection sheet is not working at all, not only does it not display cells for posting loan transactions but even when submitting data for savings transactions we get an error "HTTP 500".
We had taken the risk because there's one feature we liked about v 1.5.1. in that it supported grace period on all installment whereas that feature in v1.3 still charges interest.
We allowed batch jobs to run for 3 days uninterrupted hoping it would correct the collection sheet issue but this is causing a delay in posting data. So we are planning to do a roll back to v1.3.

Has anyone else faced the same problem with the collection sheet with v1.5?
--
Best Regards
Polly Najori

[Polly]

Hi,

When the you click on submit on the collection sheet you get the following error

javax.servlet.ServletException: org.mifos.core.MifosRuntimeException: Input Errors Found:
ACCOUNT_DOESNT_BELONG_TO_CUSTOMER: Customer Id: 3641 Account Id: 7845

ACCOUNT_DOESNT_BELONG_TO_CUSTOMER: Customer Id: 7087 Account Id: 19128
ACCOUNT_DOESNT_BELONG_TO_CUSTOMER: Customer Id: 8687 Account Id: 26880
ACCOUNT_DOESNT_BELONG_TO_CUSTOMER: Customer Id: 9453 Account Id: 29786


	org.apache.struts.action.RequestProcessor.processException(RequestProcessor.java:523)
	org.mifos.framework.struts.action.MifosRequestProcessor.processActionPerform(MifosRequestProcessor.java:233)
	org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224)

	org.apache.struts.action.ActionServlet.process(ActionServlet.java:1194)
	org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

	org.mifos.security.util.LoginFilter.doFilter(LoginFilter.java:85)
	org.mifos.framework.persistence.DatabaseInitFilter.doFilter(DatabaseInitFilter.java:51)

root cause

org.mifos.core.MifosRuntimeException: Input Errors Found:

ACCOUNT_DOESNT_BELONG_TO_CUSTOMER: Customer Id: 3641 Account Id: 7845
ACCOUNT_DOESNT_BELONG_TO_CUSTOMER: Customer Id: 7087 Account Id: 19128
ACCOUNT_DOESNT_BELONG_TO_CUSTOMER: Customer Id: 8687 Account Id: 26880

ACCOUNT_DOESNT_BELONG_TO_CUSTOMER: Customer Id: 9453 Account Id: 29786

	org.mifos.application.servicefacade.CollectionSheetServiceFacadeWebTier.saveCollectionSheet(CollectionSheetServiceFacadeWebTier.java:237)
	org.mifos.application.collectionsheet.struts.action.CollectionSheetEntryAction.create(CollectionSheetEntryAction.java:271)

	sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

	java.lang.reflect.Method.invoke(Method.java:597)
	org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:274)
	org.apache.struts.actions.DispatchAction.execute(DispatchAction.java:194)
	org.mifos.framework.struts.action.BaseAction.execute(BaseAction.java:105)

	org.mifos.framework.struts.action.MifosRequestProcessor.processActionPerform(MifosRequestProcessor.java:204)
	org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224)
	org.apache.struts.action.ActionServlet.process(ActionServlet.java:1194)

	org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
	org.mifos.security.util.LoginFilter.doFilter(LoginFilter.java:85)

	org.mifos.framework.persistence.DatabaseInitFilter.doFilter(DatabaseInitFilter.java:51)

The accounts numbers in question are ok and yet this error is generated.
I have attached 2 pages from Mifos demo server showing a client with active loans but on the collection sheet page there are no cells to post transactions.

Polly

[Polly]

How would someone go about downgrading Mifos? Is there anyone who has done it before? What is the standard procedure to downgrade the database?

Mifos Database Error

A database error occurred. Correct the error and restart the application. Details:

Failed to upgrade database. Database Version = 240 Application Version = 212.

More details:

Using Mifos database connection settings from file(s): [C:\Program Files\Apache\Tomcat 6.0\webapps\mifos\WEB-INF\classes\org\mifos\config\resources\mainDatabase.properties] Connection URL=jdbc:mysql://localhost:3306/mifos?useUnicode=true&characterEncoding=UTF-8. Username=root. Password=********

Stack trace:

java.lang.UnsupportedOperationException: your database needs to be downgraded from 240 to 212
	at org.mifos.framework.persistence.DatabaseVersionPersistence.scripts(DatabaseVersionPersistence.java:376)
	at org.mifos.framework.persistence.DatabaseVersionPersistence.upgradeDatabase(DatabaseVersionPersistence.java:463)

	at org.mifos.framework.persistence.DatabaseVersionPersistence.upgradeDatabase(DatabaseVersionPersistence.java:445)
	at org.mifos.framework.ApplicationInitializer.init(ApplicationInitializer.java:156)
	at org.mifos.framework.ApplicationInitializer.contextInitialized(ApplicationInitializer.java:122)

	at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843)
	at org.apache.catalina.core.StandardContext.start(StandardContext.java:4350)
	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)

	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
	at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:829)

	at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:718)
	at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
	at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1147)

	at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
	at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
	at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)

	at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
	at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
	at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)

	at org.apache.catalina.core.StandardService.start(StandardService.java:516)
	at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
	at org.apache.catalina.startup.Catalina.start(Catalina.java:578)

	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)

	at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)


Polly

 

[Jeff Brewster]

Polly,

Did you delete the tomcat work directory as part of the upgrade?  You can still give that  a try if you didn’t.  Stop tomcat, then delete the mifos folder under Tomcat/work/Catalina/localhost, and restart tomcat. 

 

Jeff

[Polly]

Jeff,

Thank you. The downgrade went well. Why is the batch job scheduler for collection sheet disabled in the task.xml?

    <!--<scheduler>
        <task-class-name>CollectionSheetTask</task-class-name>
        <initial-time>24:00:00</initial-time>
        <delay-time>86400</delay-time>
    </scheduler>-->

I am suspecting that this might be the cause for the missing cells in the collection sheet. My understanding is that the batch jobs affect the functionality in the collection sheet. We are planning to upgrade the test server to v.1.6 to see if the collection sheet is working well.

Polly.

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Mifos-users mailing list
Mifos...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mifos-users

[Kay Chau]

Hi Polly

 

This task is actually unneeded hence why it’s commented out.  We have removed the batch job altogether in 1.6.

 

What missing cells are you seeing in collection sheet?  Is it the report or collection sheet entry?

 

Kay

[Jeff Brewster]

Polly,

As Kay said, that batch job is no longer needed.  You can read more details in this issue:  http://mifosforge.jira.com/browse/MIFOS-2881

 

Jeff

[Polly]

Hi Kay,

The collection sheet is a vital functionality in our MFI since it cuts down the time needed to post transactions by 70%.
This is the situation, we have one fully dedicated data entry clerk and one part time who helps out 3 hours a day and we the data is only 2 days behind on a bad day for 6,500 clients.
If the collection sheet does not work well, we will be forced to have 3 fully dedicated data entry clerks and 2 part time working 3 hours a day for the same number of clients. We came to this conclusion when we upgraded to v1.5.1 and the collection sheet was not working which created a backlog of 5 days work.
In my experience for the time I have worked with Mifos, when the batch jobs are not running well, the collection sheet does not display cells for active loans where payments to loan accounts are posted which means that every loan repayment has to be posted one by one in the client's loan dashboard (seriously tedious and time consuming).

One of the reasons we were upgrading to v1.5.1 was because the grace period is not working well in v1.3, "grace on all repayments" still charges interest during the grace period. But in 1.5.1 this funcionality works well. So what we have been doing is, if a loan is disbursed on 3/8/2010, in the system we disburse it on 17/8/2010 (3 weeks grace period). The disbursement date in the system is calculated mentaly by the person who is booking the loans. This is a loophole for something serious in the future. Now all this is done assuming that no client makes payment during the grace period (which happens ALOT!).

Polly

[Ryan Whitney]

Polly,

The batch job was removed because we changed the underlying functionality so the collection sheet does not need it anymore, ie, everything is done ‘live’/changes are immediate.  So if you are seeing issues with the collection sheet, its not due to problems with the batch jobs, its a problem with the collection sheet and would need to be addressed.

So if you can detail for us what are the exact issues you are having with the collection sheet, we can better advise you, but without that information, there is not much we can do.  

Ryan

--
Ryan Whitney
Mifos Technical Program Manager
rwhi...@grameenfoundation.org  
Mifos - Technology that Empowers Microfinance (www.mifos.org)
Our mission is to enable the poor, especially the poorest, to create a world without poverty.  
<http://grameenfoundation.org/take-action/ingenuity-fund-challenge/>
P please consider the environment before printing this e-mail.

[Jeff Brewster]

Polly,
I’ve logged issue http://mifosforge.jira.com/browse/MIFOS-3511 in regards to the change in collection sheet behavior for disallowing input when no repayment is due between version 1.3 and 1.5.1.  Please add any additional comments to that issue.

 

Regarding the submit errors you are seeing, can you please post that issue on mifosforge?  Do troubleshoot the issue, we’d likely need a copy of your data.

 

Jeff

[Polly]

Ryan,

If you read all the threads to this email I have been stating the problem, see attached an example the client has active loans but in the collection sheet it is only displaying cells for savings which means you can only post transactions on the savings account. Any repayments on the loan have to be posted in the client's loan dash board. These dumps (collectionsheetaction.do.htm and clientcustaction.do.htm) I got from the test server (the one in the web before it was upgraded to 1.6).

The collection sheet should display cells for all active accounts for the client to allow bulk entry.  Please see attachment cells.doc. (dumps from our server).

Polly

Polly,

The batch job was removed because we changed the underlying functionality so the collection sheet does not need it anymore, ie, everything is done ‘live’/changes are immediate.  So if you are seeing issues with the collection sheet, its not due to problems with the batch jobs, its a problem with the collection sheet and would need to be addressed.

So if you can detail for us what are the exact issues you are having with the collection sheet, we can better advise you, but without that information, there is not much we can do.  

Ryan

- Show quoted text -

On 8/3/10 14:35, "Polly" <polly....@gmail.com> wrote:

- Show quoted text -

--

Ryan Whitney
Mifos Technical Program Manager
rwhi...@grameenfoundation.org  
Mifos - Technology that Empowers Microfinance (www.mifos.org)
Our mission is to enable the poor, especially the poorest, to create a world without poverty.  
<http://grameenfoundation.org/take-action/ingenuity-fund-challenge/>

P please consider the environment before printing this e-mail.

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

------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm

[Ryan Whitney]

Polly,

Apologies, I have not been keeping up on the thread, I was replying to what I last read.

Based on that, I would suspect this may be due to an issue where the payment boxes do not appear if the client is ahead on payments – I filed this issue for release 1.5 (http://mifosforge.jira.com/browse/MIFOS-3354) and it appears its scheduled for the next release of Mifos.
 
Not sure about the HTTP-500 error you are seeing, that seems like something else or a potential bug.  At this point, I’m not sure what the correct solution is for you for the pre-posting issue on the CSE.  Maybe its best to wait on Mifos 1.3 until the next release is out?

Ryan

On 8/3/10 16:32, "Polly" <polly....@gmail.com> wrote:

Ryan,

If you read all the threads to this email I have been stating the problem, see attached an example the client has active loans but in the collection sheet it is only displaying cells for savings which means you can only post transactions on the savings account. Any repayments on the loan have to be posted in the client's loan dash board. These dumps (collectionsheetaction.do.htm and clientcustaction.do.htm) I got from the test server (the one in the web before it was upgraded to 1.6).


The collection sheet should display cells for all active accounts for the client to allow bulk entry.  Please see attachment cells.doc. (dumps from our server).

Polly

Polly,

The batch job was removed because we changed the underlying functionality so the collection sheet does not need it anymore, ie, everything is done ‘live’/changes are immediate.  So if you are seeing issues with the collection sheet, its not due to problems with the batch jobs, its a problem with the collection sheet and would need to be addressed.

So if you can detail for us what are the exact issues you are having with the collection sheet, we can better advise you, but without that information, there is not much we can do.  

Ryan
- Show quoted text -

On 8/3/10 14:35, "Polly" <polly....@gmail.com <http://polly%2Egi...@gmail.com/> > wrote:

- Show quoted text -

Hi Kay,

The collection sheet is a vital functionality in our MFI since it cuts down the time needed to post transactions by 70%.
This is the situation, we have one fully dedicated data entry clerk and one part time who helps out 3 hours a day and we the data is only 2 days behind on a bad day for 6,500 clients.
If the collection sheet does not work well, we will be forced to have 3 fully dedicated data entry clerks and 2 part time working 3 hours a day for the same number of clients. We came to this conclusion when we upgraded to v1.5.1 and the collection sheet was not working which created a backlog of 5 days work.
In my experience for the time I have worked with Mifos, when the batch jobs are not running well, the collection sheet does not display cells for active loans where payments to loan accounts are posted which means that every loan repayment has to be posted one by one in the client's loan dashboard (seriously tedious and time consuming).

One of the reasons we were upgrading to v1.5.1 was because the grace period is not working well in v1.3, "grace on all repayments" still charges interest during the grace period. But in 1.5.1 this funcionality works well. So what we have been doing is, if a loan is disbursed on 3/8/2010, in the system we disburse it on 17/8/2010 (3 weeks grace period). The disbursement date in the system is calculated mentaly by the person who is booking the loans. This is a loophole for something serious in the future. Now all this is done assuming that no client makes payment during the grace period (which happens ALOT!).

Polly

On 23 July 2010 16:23, Kay Chau <kc...@grameenfoundation.org <http://kc...@grameenfoundation.org/> > wrote:

Hi Polly
 
This task is actually unneeded hence why it’s commented out.  We have removed the batch job altogether in 1.6.
 
What missing cells are you seeing in collection sheet?  Is it the report or collection sheet entry?
 
Kay
 

From: Polly [mailto:polly....@gmail.com]
Sent: Tuesday, July 20, 2010 2:04 PM

To: A good place to start for users or folks new to Mifos.
Subject: Re: [Mifos-users] V 1.5.1

 
Jeff,

Thank you. The downgrade went well. Why is the batch job scheduler for collection sheet disabled in the task.xml?

    <!--<scheduler>
        <task-class-name>CollectionSheetTask</task-class-name>
        <initial-time>24:00:00</initial-time>
        <delay-time>86400</delay-time>
    </scheduler>-->

I am suspecting that this might be the cause for the missing cells in the collection sheet. My understanding is that the batch jobs affect the functionality in the collection sheet. We are planning to upgrade the test server to v.1.6 to see if the collection sheet is working well.

Polly.

On 18 July 2010 15:06, Polly <polly....@gmail.com <http://polly%2Egi...@gmail.com/> > wrote:
Hello,

The collection sheet in v 1.5.1 is not working properly. On the server we were still using v 1.3. 
We did not upgrade to v1.4. because it was not supporting loans with 0% interest. v1.5 on the test server was working well except that in the collection sheet it was only displaying cells for loans that had amounts that were due whereas in our MFI we have clients paying constantly even where there are no amounts due.
So on Thursday we went ahead and did the upgrade on the server from v 1.3 to v 1.5.1. Now the collection sheet is not working at all, not only does it not display cells for posting loan transactions but even when submitting data for savings transactions we get an error "HTTP 500".
We had taken the risk because there's one feature we liked about v 1.5.1. in that it supported grace period on all installment whereas that feature in v1.3 still charges interest.
We allowed batch jobs to run for 3 days uninterrupted hoping it would correct the collection sheet issue but this is causing a delay in posting data. So we are planning to do a roll back to v1.3.

Has anyone else faced the same problem with the collection sheet with v1.5?