[Mifos-issues] [JIRA Studio] Created: (MIFOS-4963) Upgrade script fails to get datasource object
Kojo Gambrah-Sampaney (JIRA)
----------------------------------------------
Key: MIFOS-4963
URL: http://mifosforge.jira.com/browse/MIFOS-4963
Project: mifos
Issue Type: Bug
Affects Versions: Release 2.0.3
Reporter: Kojo Gambrah-Sampaney
Priority: Critical
Changes in spring configuration have made the datasource object unavailable during Java upgrade execution. This causes a null pointer exception to occur in Upgrade1283765911.
This can be reproduced by upgrading a dataset at Mifos 1.6.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Mifos-issues mailing list
Mifos-...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mifos-issues
Adam Monsen (JIRA)
[ http://mifosforge.jira.com/browse/MIFOS-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Monsen updated MIFOS-4963:
-------------------------------
Attachment: 203_db_repro.sql.gz
> 2.0.3 database upgrade breaks when upgrading Mifos 1.6 (or prior) datasets
> --------------------------------------------------------------------------
>
> Key: MIFOS-4963
> URL: http://mifosforge.jira.com/browse/MIFOS-4963
> Project: mifos
> Issue Type: Bug
> Affects Versions: Release 2.0.3
> Reporter: Kojo Gambrah-Sampaney
> Assignee: Adam Monsen
> Priority: Critical
> Fix For: Release 2.0.3
>
> Attachments: 203_db_repro.sql.gz
>
>
> Changes in spring configuration have made the datasource object unavailable during Java upgrade execution. This causes a null pointer exception to occur in Upgrade1283765911.
> This can be reproduced by upgrading a Mifos 1.6 database to the latest code on the e-release branch (Mifos 2.0.3 release candidate).
> Log snippet showing error:
> {noformat}
> applying upgrade with timestamp: 1282814250: Finished in 31 msec
> applying upgrade with timestamp: 1283237728: Finished in 18 msec
> applying upgrade with timestamp: 1283320210: Finished in 4 msec
> applying upgrade with timestamp: 1283416834: Finished in 15 msec
> applying upgrade with timestamp: 12837659112011-05-03/11:47:38.993/PDT ERROR, org.mifos.framework.ApplicationInitializer, ?, ?, ?,
> Failed to upgrade database.
> java.io.IOException: java.lang.IllegalArgumentException: The [dataSource] argument cannot be null.
> at org.mifos.application.master.persistence.Upgrade1283765911.upgrade(Upgrade1283765911.java:79)
> at org.mifos.framework.persistence.DatabaseMigrator.applyUpgrade(DatabaseMigrator.java:324)
> at org.mifos.framework.persistence.DatabaseMigrator.upgrade(DatabaseMigrator.java:163)
> at org.mifos.framework.persistence.DatabaseMigrator.upgrade(DatabaseMigrator.java:175)
> at org.mifos.framework.ApplicationInitializer.dbUpgrade(ApplicationInitializer.java:174)
> at org.mifos.framework.ApplicationInitializer.init(ApplicationInitializer.java:132)
> at org.mifos.framework.ApplicationInitializer.contextInitialized(ApplicationInitializer.java:119)
> at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3972)
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4467)
> 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:546)
> at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:637)
> at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:563)
> at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:498)
> at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277)
> at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321)
> at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
> at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
> at org.apache.catalina.core.StandardHost.start(StandardHost.java:785)
> 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:519)
> at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:581)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
> Caused by: java.lang.IllegalArgumentException: The [dataSource] argument cannot be null.
> at org.springframework.util.Assert.notNull(Assert.java:112)
> at org.springframework.jdbc.core.namedparam.NamedParameterJdbcTemplate.<init>(NamedParameterJdbcTemplate.java:76)
> at org.springframework.jdbc.core.simple.SimpleJdbcTemplate.<init>(SimpleJdbcTemplate.java:66)
> at org.mifos.application.master.persistence.Upgrade1283765911.upgrade(Upgrade1283765911.java:66)
> ... 30 more
> {noformat}
Adam Monsen (JIRA)
[ http://mifosforge.jira.com/browse/MIFOS-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Monsen updated MIFOS-4963:
-------------------------------
Description:
Changes in spring configuration have made the datasource object unavailable during Java upgrade execution. This causes a null pointer exception to occur in Upgrade1283765911.
This can be reproduced by upgrading a Mifos 1.6 database to the latest code on the e-release branch (Mifos 2.0.3 release candidate).
was:
Changes in spring configuration have made the datasource object unavailable during Java upgrade execution. This causes a null pointer exception to occur in Upgrade1283765911.
This can be reproduced by upgrading a dataset at Mifos 1.6.
Fix Version/s: Release 2.0.3
Assignee: Adam Monsen
Summary: 2.0.3 database upgrade breaks when upgrading Mifos 1.6 (or prior) datasets (was: Upgrade script fails to get datasource object )
> 2.0.3 database upgrade breaks when upgrading Mifos 1.6 (or prior) datasets
> --------------------------------------------------------------------------
>
> Key: MIFOS-4963
> URL: http://mifosforge.jira.com/browse/MIFOS-4963
> Project: mifos
> Issue Type: Bug
> Affects Versions: Release 2.0.3
> Reporter: Kojo Gambrah-Sampaney
> Assignee: Adam Monsen
> Priority: Critical
> Fix For: Release 2.0.3
>
> Attachments: 203_db_repro.sql.gz
>
>
> Changes in spring configuration have made the datasource object unavailable during Java upgrade execution. This causes a null pointer exception to occur in Upgrade1283765911.
--
Adam Monsen (JIRA)
[ http://mifosforge.jira.com/browse/MIFOS-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=67054#comment-67054 ]
Adam Monsen commented on MIFOS-4963:
------------------------------------
Van is working on a fix for 2.0.3: remove database upgrade support from Mifos 1.6.
Upgrading from 1.6 to all later releases is still possible, users would just need to run 2.0.2 first (to do the db upgrade) then immediately start using 2.0.3 (to get the fix for MIFOS-4950).
> 2.0.3 database upgrade breaks when upgrading Mifos 1.6 (or prior) datasets
> --------------------------------------------------------------------------
>
> Key: MIFOS-4963
> URL: http://mifosforge.jira.com/browse/MIFOS-4963
> Project: mifos
> Issue Type: Bug
> Affects Versions: Release 2.0.3
> Reporter: Kojo Gambrah-Sampaney
> Assignee: Adam Monsen
> Priority: Critical
> Labels: documentinfs
> Fix For: Release 2.0.3
>
> Attachments: 203_db_repro.sql.gz
>
>
> Changes in spring configuration have made the datasource object unavailable during Java upgrade execution. This causes a null pointer exception to occur in Upgrade1283765911.
--
Adam Monsen (JIRA)
[ http://mifosforge.jira.com/browse/MIFOS-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Monsen reassigned MIFOS-4963:
----------------------------------
Assignee: Van Mittal-Henkle (was: Adam Monsen)
I was able to upgrade the attached dataset (203_db_repro.sql.gz) using 2.0.2. I then stopped Tomcat, and re-started using a war built from e-release commit 789c3ac560d4700a735c3d45d6d7c5d29a252931.
Van, will you resolve if the e-release build passes?
> 2.0.3 database upgrade breaks when upgrading Mifos 1.6 (or prior) datasets
> --------------------------------------------------------------------------
>
> Key: MIFOS-4963
> URL: http://mifosforge.jira.com/browse/MIFOS-4963
> Project: mifos
> Issue Type: Bug
> Affects Versions: Release 2.0.3
> Reporter: Kojo Gambrah-Sampaney
> Assignee: Van Mittal-Henkle
> Priority: Critical
> Labels: documentinfs
> Fix For: Release 2.0.3
>
> Attachments: 203_db_repro.sql.gz
>
>
> Changes in spring configuration have made the datasource object unavailable during Java upgrade execution. This causes a null pointer exception to occur in Upgrade1283765911.
--
Van Mittal-Henkle (JIRA)
[ http://mifosforge.jira.com/browse/MIFOS-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Van Mittal-Henkle resolved MIFOS-4963.
--------------------------------------
Resolution: Fixed
Resolved by removing the reference to the datasource (which was needed to migrate historic batch job entries). To preserve batch job entries an MFI needs to migrate to Mifos 2.0.2 first and then to 2.0.3. Migrating directly to 2.0.3 is safe, but will start with an empty batch job history.
> 2.0.3 database upgrade breaks when upgrading Mifos 1.6 (or prior) datasets
> --------------------------------------------------------------------------
>
> Key: MIFOS-4963
> URL: http://mifosforge.jira.com/browse/MIFOS-4963
> Project: mifos
> Issue Type: Bug
> Affects Versions: Release 2.0.3
> Reporter: Kojo Gambrah-Sampaney
> Assignee: Van Mittal-Henkle
> Priority: Critical
> Labels: documentinfs
> Fix For: Release 2.0.3
>
> Attachments: 203_db_repro.sql.gz
>
>
> Changes in spring configuration have made the datasource object unavailable during Java upgrade execution. This causes a null pointer exception to occur in Upgrade1283765911.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
Lukasz Chudy (Updated) (JIRA)
[ http://mifosforge.jira.com/browse/MIFOS-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lukasz Chudy updated MIFOS-4963:
--------------------------------
Status: Ready for Showcase (was: Ready for Testing / Resolved)
Verified 14.12.2011
Bug has been fixed properly.
> 2.0.3 database upgrade breaks when upgrading Mifos 1.6 (or prior) datasets
> --------------------------------------------------------------------------
>
> Key: MIFOS-4963
> URL: http://mifosforge.jira.com/browse/MIFOS-4963
> Project: mifos
> Issue Type: Bug
> Affects Versions: Release 2.0.3
> Reporter: Kojo Gambrah-Sampaney
> Assignee: Van Mittal-Henkle
> Priority: Critical
> Fix For: Release 2.0.3
>
> Attachments: 203_db_repro.sql.gz
>
>
> Changes in spring configuration have made the datasource object unavailable during Java upgrade execution. This causes a null pointer exception to occur in Upgrade1283765911.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: http://mifosforge.jira.com/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Cloud Computing - Latest Buzzword or a Glimpse of the Future?
This paper surveys cloud computing today: What are the benefits?
Why are businesses embracing it? What are its payoffs and pitfalls?
http://www.accelacomm.com/jaw/sdnl/114/51425149/