Problem with tracker module

Let’s hope for that … but at the same time it not about removing a column - it is more than that and a bit complex.

···

On Wed, Mar 18, 2015 at 4:06 PM, Wilson, Randy rwilson@msh.org wrote:

Thanks for the troubleshooting. We’ll try removing the extra static columns on an offline instance and let you know.

I’m sure it will do the trick.

Randy

This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.


Thank you,

Abyot.

On Wed, Mar 18, 2015 at 4:53 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

The table does look exactly like it has many static atteruibutes which should have moved to dynamic, so probably some upgrade script was not applied.

The rwanda implementation does have a fairly long vintage. I’ll check that old upgrade script and see if it fixes the problem. Thanks Abyot.


Randy Wilson
*Team Leader: *Knowledge Management, Data Use and Research

Rwanda Health System Strengthening Activity

Management Sciences for Health

Rwanda-Kigali

Direct: +250 788308835

E-mail: rwilson@msh.org

Skype: wilsonrandy_us

Stronger health systems. Greater health impact.

www.msh.org

On 18 March 2015 at 14:45, Abyot Gizaw abyota@gmail.com wrote:

we used to have that attribute. see the commit from Tran (Rev: 13239)

That was supposed to be removed when migrating static to dynamic attributes … this then leads to another bigger issue - have you made a proper upgrade?


Thank you,

Abyot.

On Wed, Mar 18, 2015 at 3:36 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

Hi Abyot

Thanks for the explanation. That makes sense. So the second post is never happening because the registration is not completed.

Alex raises an interesting possibility. There is a column called registrationdate on trackedentityinstance. Is this meant to be there or could it be a hangover from an earlier version of the table?

I guess randy can try with 2.18 but I have been testing on one of the production servers so I can’t really upgrade just to test this.

On 18 March 2015 at 14:32, Abyot Gizaw abyota@gmail.com wrote:

It is a two step process… first registration is done meaning server returning uid, then using this uid another json is posted (this time the enrollment details are sent). What I think has happened is server failed to complete registration. Looking the log - do you have an attribute called registrationdate which is set mandatory?

Also, can you make sure you are trying this in 2.18? of course you can continue with 2.17 but just saying that 2.18 is more stable. I just did a test on the demo server (which is 2.18) and it is working fine.

One more thing… if you have made changes to your metadata once the tracker app has run - you need to clear cache to that the new meta-data is cached locally. We don’t have a feature to auto-update local-cache.


Thank you,

Abyot.

On Wed, Mar 18, 2015 at 2:53 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

Hi Abyot

The log shows what Randy initially reported:

  • ERROR 2015-03-18 14:19:55,836 ERROR: null value in column “registrationdate” v

iolates not-null constraint

Detail: Failing row contains (29412, null, null, null, null, null, null, null,

null, 872, null, null, Ktl3NTLuGlK, null, 2015-03-18 14:19:55.805, 2015-03-18 1

4:19:55.805, null, 17032). (SqlExceptionHelper.java [tomcat-http-10])

I am not sure about which instance randy has tested 2.18 on, but this is definitely 2.17. (I think he thought that this instance was also 2.18, but its not)

According to the form the Enrollment date and Reporting date are required fields (see screenshot). Do you mean that they are simply ignored on initial registration?

So where does the registration date come from? From the server date?

Bob

On 18 March 2015 at 13:01, Abyot Gizaw abyota@gmail.com wrote:

Hi Bob,

That is just for registration … then enrollment follows with enrollment and incident dates. Most probably something has failed in between - is there any log?


Thank you,

Abyot.

On Wed, Mar 18, 2015 at 1:48 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

Hi Abyot

I just had a quick look at the tracker app on one of the Rwanda dhis2 instances (it is running 2.17 built on 2015-01-21 02:05 - strange I don’t see the build revision)

The form has some attributes and the Enrollment date and Reporting date at the bottom. When I try to save I see that the following is POSTed.

{“trackedEntity”:“BQu4uXKyrRE”,“orgUnit”:“BPZcHDS6OO0”,“attributes”:[{“attribute”:“xyp3l9obelI”,“value”:55654},{“attribute”:“ul7UIuUoP1Z”,“value”:“5654”},{“attribute”:“rOwntnIQh2P”,“value”:“56546”},{“attribute”:“QnwIsiKw2NF”,“value”:“5654”},{“attribute”:“SZ05eUTBMEN”,“value”:“6546”},{“attribute”:“tNGC3SeoHbb”,“value”:“5656”},{“attribute”:“FQGMFSwKUkB”,“value”:56546},{“attribute”:“VsUAhCcttyf”,“value”:“56546”}]}

Note there are no dates in this even though they were entered on the form. This seems wrong, I guess this is what causes the sql to fail.

Regards

Bob

On 17 March 2015 at 14:26, Abyot Gizaw abyota@gmail.com wrote:

Hello Randy,

Are you using the individual records module?

Can you try tracker capture app?


Thank you,

Abyot.

(sent from mobile)

On Mar 17, 2015 3:15 PM, “Wilson, Randy” rwilson@msh.org wrote:

We’re setting up a tracker module to capture data from individual community health workers using Multiple events with registration.

We have the program and stage as well as attributes and data elements - using 3 different instances of DHIS-2.

When we try to create a new instance we fill in the form, but when we click on Add, the screen freezes. The instance is not saved so we can’t enter any data.

We are using version 2.18 build 18143

Any guidance would be much appreciated… we’re stuck.

Here is the log:

  • INFO 2015-03-17 16:08:42,610 ‘randy’ create org.hisp.dhis.trackedentity.Track

edEntityInstance, uid: S4SGPUtDl0o (AuditLogUtil.java [http-bio-8080-exec-6])

  • INFO 2015-03-17 16:08:42,650 ‘randy’ update org.hisp.dhis.trackedentity.Track

edEntityInstance, uid: S4SGPUtDl0o (AuditLogUtil.java [http-bio-8080-exec-6])

  • WARN 2015-03-17 16:08:42,650 SQL Error: 0, SQLState: 23502 (SqlExceptionHelpe

r.java [http-bio-8080-exec-6])

  • ERROR 2015-03-17 16:08:42,650 ERROR: null value in column “registrationdate” v

iolates not-null constraint

Detail: Failing row contains (19556, null, null, null, null, null, null, null,

null, 872, null, null, S4SGPUtDl0o, null, 2015-03-17 16:08:42.61, 2015-03-17 16

:08:42.61, null, 17032). (SqlExceptionHelper.java [http-bio-8080-exec-6])

  • ERROR 2015-03-17 16:08:42,660 HHH000352: Unable to release batch statement…

(AbstractBatchImpl.java [http-bio-8080-exec-6])

  • ERROR 2015-03-17 16:08:42,670 HHH000246: SQLException escaped proxy (AbstractB

atchImpl.java [http-bio-8080-exec-6])

java.sql.SQLException: You can’t operate on a closed Statement!!!


Randy Wilson
*Team Leader: *Knowledge Management, Data Use and Research

Rwanda Health System Strengthening Activity

Management Sciences for Health

Rwanda-Kigali

Direct: +250 788308835

E-mail: rwilson@msh.org

Skype: wilsonrandy_us

Stronger health systems. Greater health impact.

www.msh.org

This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp

Hi Abyot

Looking at the upgrade script it ends with

ALTER TABLE patient DROP COLUMN gender;

ALTER TABLE patient DROP COLUMN deathDate;

ALTER TABLE patient DROP COLUMN registrationDate;

ALTER TABLE patient DROP COLUMN isDead;

ALTER TABLE patient DROP COLUMN underAge;

ALTER TABLE patient DROP COLUMN dobType;

ALTER TABLE patient DROP COLUMN birthdate;

ALTER TABLE patient DROP COLUMN phoneNumber;

ALTER TABLE patient DROP COLUMN name;

ALTER TABLE patient DROP COLUMN healthworkerid

which removes all the old static attributes (obviously table name has changed). I see that the earlier part of the script is dedicated to creating dynamic attributes for these and copying over the data. If there is no existing data is there still a need to create these formerly fixed attributes?

···

On 18 March 2015 at 15:10, Abyot Gizaw abyota@gmail.com wrote:

Let’s hope for that … but at the same time it not about removing a column - it is more than that and a bit complex.


Thank you,

Abyot.

On Wed, Mar 18, 2015 at 4:06 PM, Wilson, Randy rwilson@msh.org wrote:

Thanks for the troubleshooting. We’ll try removing the extra static columns on an offline instance and let you know.

I’m sure it will do the trick.

Randy

This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.

On Wed, Mar 18, 2015 at 4:53 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

The table does look exactly like it has many static atteruibutes which should have moved to dynamic, so probably some upgrade script was not applied.

The rwanda implementation does have a fairly long vintage. I’ll check that old upgrade script and see if it fixes the problem. Thanks Abyot.


Randy Wilson
*Team Leader: *Knowledge Management, Data Use and Research

Rwanda Health System Strengthening Activity

Management Sciences for Health

Rwanda-Kigali

Direct: +250 788308835

E-mail: rwilson@msh.org

Skype: wilsonrandy_us

Stronger health systems. Greater health impact.

www.msh.org

On 18 March 2015 at 14:45, Abyot Gizaw abyota@gmail.com wrote:

we used to have that attribute. see the commit from Tran (Rev: 13239)

That was supposed to be removed when migrating static to dynamic attributes … this then leads to another bigger issue - have you made a proper upgrade?


Thank you,

Abyot.

On Wed, Mar 18, 2015 at 3:36 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

Hi Abyot

Thanks for the explanation. That makes sense. So the second post is never happening because the registration is not completed.

Alex raises an interesting possibility. There is a column called registrationdate on trackedentityinstance. Is this meant to be there or could it be a hangover from an earlier version of the table?

I guess randy can try with 2.18 but I have been testing on one of the production servers so I can’t really upgrade just to test this.

On 18 March 2015 at 14:32, Abyot Gizaw abyota@gmail.com wrote:

It is a two step process… first registration is done meaning server returning uid, then using this uid another json is posted (this time the enrollment details are sent). What I think has happened is server failed to complete registration. Looking the log - do you have an attribute called registrationdate which is set mandatory?

Also, can you make sure you are trying this in 2.18? of course you can continue with 2.17 but just saying that 2.18 is more stable. I just did a test on the demo server (which is 2.18) and it is working fine.

One more thing… if you have made changes to your metadata once the tracker app has run - you need to clear cache to that the new meta-data is cached locally. We don’t have a feature to auto-update local-cache.


Thank you,

Abyot.

On Wed, Mar 18, 2015 at 2:53 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

Hi Abyot

The log shows what Randy initially reported:

  • ERROR 2015-03-18 14:19:55,836 ERROR: null value in column “registrationdate” v

iolates not-null constraint

Detail: Failing row contains (29412, null, null, null, null, null, null, null,

null, 872, null, null, Ktl3NTLuGlK, null, 2015-03-18 14:19:55.805, 2015-03-18 1

4:19:55.805, null, 17032). (SqlExceptionHelper.java [tomcat-http-10])

I am not sure about which instance randy has tested 2.18 on, but this is definitely 2.17. (I think he thought that this instance was also 2.18, but its not)

According to the form the Enrollment date and Reporting date are required fields (see screenshot). Do you mean that they are simply ignored on initial registration?

So where does the registration date come from? From the server date?

Bob

On 18 March 2015 at 13:01, Abyot Gizaw abyota@gmail.com wrote:

Hi Bob,

That is just for registration … then enrollment follows with enrollment and incident dates. Most probably something has failed in between - is there any log?


Thank you,

Abyot.

On Wed, Mar 18, 2015 at 1:48 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

Hi Abyot

I just had a quick look at the tracker app on one of the Rwanda dhis2 instances (it is running 2.17 built on 2015-01-21 02:05 - strange I don’t see the build revision)

The form has some attributes and the Enrollment date and Reporting date at the bottom. When I try to save I see that the following is POSTed.

{“trackedEntity”:“BQu4uXKyrRE”,“orgUnit”:“BPZcHDS6OO0”,“attributes”:[{“attribute”:“xyp3l9obelI”,“value”:55654},{“attribute”:“ul7UIuUoP1Z”,“value”:“5654”},{“attribute”:“rOwntnIQh2P”,“value”:“56546”},{“attribute”:“QnwIsiKw2NF”,“value”:“5654”},{“attribute”:“SZ05eUTBMEN”,“value”:“6546”},{“attribute”:“tNGC3SeoHbb”,“value”:“5656”},{“attribute”:“FQGMFSwKUkB”,“value”:56546},{“attribute”:“VsUAhCcttyf”,“value”:“56546”}]}

Note there are no dates in this even though they were entered on the form. This seems wrong, I guess this is what causes the sql to fail.

Regards

Bob

On 17 March 2015 at 14:26, Abyot Gizaw abyota@gmail.com wrote:

Hello Randy,

Are you using the individual records module?

Can you try tracker capture app?


Thank you,

Abyot.

(sent from mobile)

On Mar 17, 2015 3:15 PM, “Wilson, Randy” rwilson@msh.org wrote:

We’re setting up a tracker module to capture data from individual community health workers using Multiple events with registration.

We have the program and stage as well as attributes and data elements - using 3 different instances of DHIS-2.

When we try to create a new instance we fill in the form, but when we click on Add, the screen freezes. The instance is not saved so we can’t enter any data.

We are using version 2.18 build 18143

Any guidance would be much appreciated… we’re stuck.

Here is the log:

  • INFO 2015-03-17 16:08:42,610 ‘randy’ create org.hisp.dhis.trackedentity.Track

edEntityInstance, uid: S4SGPUtDl0o (AuditLogUtil.java [http-bio-8080-exec-6])

  • INFO 2015-03-17 16:08:42,650 ‘randy’ update org.hisp.dhis.trackedentity.Track

edEntityInstance, uid: S4SGPUtDl0o (AuditLogUtil.java [http-bio-8080-exec-6])

  • WARN 2015-03-17 16:08:42,650 SQL Error: 0, SQLState: 23502 (SqlExceptionHelpe

r.java [http-bio-8080-exec-6])

  • ERROR 2015-03-17 16:08:42,650 ERROR: null value in column “registrationdate” v

iolates not-null constraint

Detail: Failing row contains (19556, null, null, null, null, null, null, null,

null, 872, null, null, S4SGPUtDl0o, null, 2015-03-17 16:08:42.61, 2015-03-17 16

:08:42.61, null, 17032). (SqlExceptionHelper.java [http-bio-8080-exec-6])

  • ERROR 2015-03-17 16:08:42,660 HHH000352: Unable to release batch statement…

(AbstractBatchImpl.java [http-bio-8080-exec-6])

  • ERROR 2015-03-17 16:08:42,670 HHH000246: SQLException escaped proxy (AbstractB

atchImpl.java [http-bio-8080-exec-6])

java.sql.SQLException: You can’t operate on a closed Statement!!!


Randy Wilson
*Team Leader: *Knowledge Management, Data Use and Research

Rwanda Health System Strengthening Activity

Management Sciences for Health

Rwanda-Kigali

Direct: +250 788308835

E-mail: rwilson@msh.org

Skype: wilsonrandy_us

Stronger health systems. Greater health impact.

www.msh.org

This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp

I just dropped these columns and it is now working. Thanks Abyot and Alex …

···

On 18 March 2015 at 15:15, Bob Jolliffe bobjolliffe@gmail.com wrote:

Hi Abyot

Looking at the upgrade script it ends with

ALTER TABLE patient DROP COLUMN gender;

ALTER TABLE patient DROP COLUMN deathDate;

ALTER TABLE patient DROP COLUMN registrationDate;

ALTER TABLE patient DROP COLUMN isDead;

ALTER TABLE patient DROP COLUMN underAge;

ALTER TABLE patient DROP COLUMN dobType;

ALTER TABLE patient DROP COLUMN birthdate;

ALTER TABLE patient DROP COLUMN phoneNumber;

ALTER TABLE patient DROP COLUMN name;

ALTER TABLE patient DROP COLUMN healthworkerid

which removes all the old static attributes (obviously table name has changed). I see that the earlier part of the script is dedicated to creating dynamic attributes for these and copying over the data. If there is no existing data is there still a need to create these formerly fixed attributes?

On 18 March 2015 at 15:10, Abyot Gizaw abyota@gmail.com wrote:

Let’s hope for that … but at the same time it not about removing a column - it is more than that and a bit complex.


Thank you,

Abyot.

On Wed, Mar 18, 2015 at 4:06 PM, Wilson, Randy rwilson@msh.org wrote:

Thanks for the troubleshooting. We’ll try removing the extra static columns on an offline instance and let you know.

I’m sure it will do the trick.

Randy

This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.

On Wed, Mar 18, 2015 at 4:53 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

The table does look exactly like it has many static atteruibutes which should have moved to dynamic, so probably some upgrade script was not applied.

The rwanda implementation does have a fairly long vintage. I’ll check that old upgrade script and see if it fixes the problem. Thanks Abyot.


Randy Wilson
*Team Leader: *Knowledge Management, Data Use and Research

Rwanda Health System Strengthening Activity

Management Sciences for Health

Rwanda-Kigali

Direct: +250 788308835

E-mail: rwilson@msh.org

Skype: wilsonrandy_us

Stronger health systems. Greater health impact.

www.msh.org

On 18 March 2015 at 14:45, Abyot Gizaw abyota@gmail.com wrote:

we used to have that attribute. see the commit from Tran (Rev: 13239)

That was supposed to be removed when migrating static to dynamic attributes … this then leads to another bigger issue - have you made a proper upgrade?


Thank you,

Abyot.

On Wed, Mar 18, 2015 at 3:36 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

Hi Abyot

Thanks for the explanation. That makes sense. So the second post is never happening because the registration is not completed.

Alex raises an interesting possibility. There is a column called registrationdate on trackedentityinstance. Is this meant to be there or could it be a hangover from an earlier version of the table?

I guess randy can try with 2.18 but I have been testing on one of the production servers so I can’t really upgrade just to test this.

On 18 March 2015 at 14:32, Abyot Gizaw abyota@gmail.com wrote:

It is a two step process… first registration is done meaning server returning uid, then using this uid another json is posted (this time the enrollment details are sent). What I think has happened is server failed to complete registration. Looking the log - do you have an attribute called registrationdate which is set mandatory?

Also, can you make sure you are trying this in 2.18? of course you can continue with 2.17 but just saying that 2.18 is more stable. I just did a test on the demo server (which is 2.18) and it is working fine.

One more thing… if you have made changes to your metadata once the tracker app has run - you need to clear cache to that the new meta-data is cached locally. We don’t have a feature to auto-update local-cache.


Thank you,

Abyot.

On Wed, Mar 18, 2015 at 2:53 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

Hi Abyot

The log shows what Randy initially reported:

  • ERROR 2015-03-18 14:19:55,836 ERROR: null value in column “registrationdate” v

iolates not-null constraint

Detail: Failing row contains (29412, null, null, null, null, null, null, null,

null, 872, null, null, Ktl3NTLuGlK, null, 2015-03-18 14:19:55.805, 2015-03-18 1

4:19:55.805, null, 17032). (SqlExceptionHelper.java [tomcat-http-10])

I am not sure about which instance randy has tested 2.18 on, but this is definitely 2.17. (I think he thought that this instance was also 2.18, but its not)

According to the form the Enrollment date and Reporting date are required fields (see screenshot). Do you mean that they are simply ignored on initial registration?

So where does the registration date come from? From the server date?

Bob

On 18 March 2015 at 13:01, Abyot Gizaw abyota@gmail.com wrote:

Hi Bob,

That is just for registration … then enrollment follows with enrollment and incident dates. Most probably something has failed in between - is there any log?


Thank you,

Abyot.

On Wed, Mar 18, 2015 at 1:48 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

Hi Abyot

I just had a quick look at the tracker app on one of the Rwanda dhis2 instances (it is running 2.17 built on 2015-01-21 02:05 - strange I don’t see the build revision)

The form has some attributes and the Enrollment date and Reporting date at the bottom. When I try to save I see that the following is POSTed.

{“trackedEntity”:“BQu4uXKyrRE”,“orgUnit”:“BPZcHDS6OO0”,“attributes”:[{“attribute”:“xyp3l9obelI”,“value”:55654},{“attribute”:“ul7UIuUoP1Z”,“value”:“5654”},{“attribute”:“rOwntnIQh2P”,“value”:“56546”},{“attribute”:“QnwIsiKw2NF”,“value”:“5654”},{“attribute”:“SZ05eUTBMEN”,“value”:“6546”},{“attribute”:“tNGC3SeoHbb”,“value”:“5656”},{“attribute”:“FQGMFSwKUkB”,“value”:56546},{“attribute”:“VsUAhCcttyf”,“value”:“56546”}]}

Note there are no dates in this even though they were entered on the form. This seems wrong, I guess this is what causes the sql to fail.

Regards

Bob

On 17 March 2015 at 14:26, Abyot Gizaw abyota@gmail.com wrote:

Hello Randy,

Are you using the individual records module?

Can you try tracker capture app?


Thank you,

Abyot.

(sent from mobile)

On Mar 17, 2015 3:15 PM, “Wilson, Randy” rwilson@msh.org wrote:

We’re setting up a tracker module to capture data from individual community health workers using Multiple events with registration.

We have the program and stage as well as attributes and data elements - using 3 different instances of DHIS-2.

When we try to create a new instance we fill in the form, but when we click on Add, the screen freezes. The instance is not saved so we can’t enter any data.

We are using version 2.18 build 18143

Any guidance would be much appreciated… we’re stuck.

Here is the log:

  • INFO 2015-03-17 16:08:42,610 ‘randy’ create org.hisp.dhis.trackedentity.Track

edEntityInstance, uid: S4SGPUtDl0o (AuditLogUtil.java [http-bio-8080-exec-6])

  • INFO 2015-03-17 16:08:42,650 ‘randy’ update org.hisp.dhis.trackedentity.Track

edEntityInstance, uid: S4SGPUtDl0o (AuditLogUtil.java [http-bio-8080-exec-6])

  • WARN 2015-03-17 16:08:42,650 SQL Error: 0, SQLState: 23502 (SqlExceptionHelpe

r.java [http-bio-8080-exec-6])

  • ERROR 2015-03-17 16:08:42,650 ERROR: null value in column “registrationdate” v

iolates not-null constraint

Detail: Failing row contains (19556, null, null, null, null, null, null, null,

null, 872, null, null, S4SGPUtDl0o, null, 2015-03-17 16:08:42.61, 2015-03-17 16

:08:42.61, null, 17032). (SqlExceptionHelper.java [http-bio-8080-exec-6])

  • ERROR 2015-03-17 16:08:42,660 HHH000352: Unable to release batch statement…

(AbstractBatchImpl.java [http-bio-8080-exec-6])

  • ERROR 2015-03-17 16:08:42,670 HHH000246: SQLException escaped proxy (AbstractB

atchImpl.java [http-bio-8080-exec-6])

java.sql.SQLException: You can’t operate on a closed Statement!!!


Randy Wilson
*Team Leader: *Knowledge Management, Data Use and Research

Rwanda Health System Strengthening Activity

Management Sciences for Health

Rwanda-Kigali

Direct: +250 788308835

E-mail: rwilson@msh.org

Skype: wilsonrandy_us

Stronger health systems. Greater health impact.

www.msh.org

This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp

Great !

···

On Wed, Mar 18, 2015 at 4:28 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

I just dropped these columns and it is now working. Thanks Abyot and Alex …


Thank you,

Abyot.

On 18 March 2015 at 15:15, Bob Jolliffe bobjolliffe@gmail.com wrote:

Hi Abyot

Looking at the upgrade script it ends with

ALTER TABLE patient DROP COLUMN gender;

ALTER TABLE patient DROP COLUMN deathDate;

ALTER TABLE patient DROP COLUMN registrationDate;

ALTER TABLE patient DROP COLUMN isDead;

ALTER TABLE patient DROP COLUMN underAge;

ALTER TABLE patient DROP COLUMN dobType;

ALTER TABLE patient DROP COLUMN birthdate;

ALTER TABLE patient DROP COLUMN phoneNumber;

ALTER TABLE patient DROP COLUMN name;

ALTER TABLE patient DROP COLUMN healthworkerid

which removes all the old static attributes (obviously table name has changed). I see that the earlier part of the script is dedicated to creating dynamic attributes for these and copying over the data. If there is no existing data is there still a need to create these formerly fixed attributes?

On 18 March 2015 at 15:10, Abyot Gizaw abyota@gmail.com wrote:

Let’s hope for that … but at the same time it not about removing a column - it is more than that and a bit complex.


Thank you,

Abyot.

On Wed, Mar 18, 2015 at 4:06 PM, Wilson, Randy rwilson@msh.org wrote:

Thanks for the troubleshooting. We’ll try removing the extra static columns on an offline instance and let you know.

I’m sure it will do the trick.

Randy

This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.

On Wed, Mar 18, 2015 at 4:53 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

The table does look exactly like it has many static atteruibutes which should have moved to dynamic, so probably some upgrade script was not applied.

The rwanda implementation does have a fairly long vintage. I’ll check that old upgrade script and see if it fixes the problem. Thanks Abyot.


Randy Wilson
*Team Leader: *Knowledge Management, Data Use and Research

Rwanda Health System Strengthening Activity

Management Sciences for Health

Rwanda-Kigali

Direct: +250 788308835

E-mail: rwilson@msh.org

Skype: wilsonrandy_us

Stronger health systems. Greater health impact.

www.msh.org

On 18 March 2015 at 14:45, Abyot Gizaw abyota@gmail.com wrote:

we used to have that attribute. see the commit from Tran (Rev: 13239)

That was supposed to be removed when migrating static to dynamic attributes … this then leads to another bigger issue - have you made a proper upgrade?


Thank you,

Abyot.

On Wed, Mar 18, 2015 at 3:36 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

Hi Abyot

Thanks for the explanation. That makes sense. So the second post is never happening because the registration is not completed.

Alex raises an interesting possibility. There is a column called registrationdate on trackedentityinstance. Is this meant to be there or could it be a hangover from an earlier version of the table?

I guess randy can try with 2.18 but I have been testing on one of the production servers so I can’t really upgrade just to test this.

On 18 March 2015 at 14:32, Abyot Gizaw abyota@gmail.com wrote:

It is a two step process… first registration is done meaning server returning uid, then using this uid another json is posted (this time the enrollment details are sent). What I think has happened is server failed to complete registration. Looking the log - do you have an attribute called registrationdate which is set mandatory?

Also, can you make sure you are trying this in 2.18? of course you can continue with 2.17 but just saying that 2.18 is more stable. I just did a test on the demo server (which is 2.18) and it is working fine.

One more thing… if you have made changes to your metadata once the tracker app has run - you need to clear cache to that the new meta-data is cached locally. We don’t have a feature to auto-update local-cache.


Thank you,

Abyot.

On Wed, Mar 18, 2015 at 2:53 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

Hi Abyot

The log shows what Randy initially reported:

  • ERROR 2015-03-18 14:19:55,836 ERROR: null value in column “registrationdate” v

iolates not-null constraint

Detail: Failing row contains (29412, null, null, null, null, null, null, null,

null, 872, null, null, Ktl3NTLuGlK, null, 2015-03-18 14:19:55.805, 2015-03-18 1

4:19:55.805, null, 17032). (SqlExceptionHelper.java [tomcat-http-10])

I am not sure about which instance randy has tested 2.18 on, but this is definitely 2.17. (I think he thought that this instance was also 2.18, but its not)

According to the form the Enrollment date and Reporting date are required fields (see screenshot). Do you mean that they are simply ignored on initial registration?

So where does the registration date come from? From the server date?

Bob

On 18 March 2015 at 13:01, Abyot Gizaw abyota@gmail.com wrote:

Hi Bob,

That is just for registration … then enrollment follows with enrollment and incident dates. Most probably something has failed in between - is there any log?


Thank you,

Abyot.

On Wed, Mar 18, 2015 at 1:48 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

Hi Abyot

I just had a quick look at the tracker app on one of the Rwanda dhis2 instances (it is running 2.17 built on 2015-01-21 02:05 - strange I don’t see the build revision)

The form has some attributes and the Enrollment date and Reporting date at the bottom. When I try to save I see that the following is POSTed.

{“trackedEntity”:“BQu4uXKyrRE”,“orgUnit”:“BPZcHDS6OO0”,“attributes”:[{“attribute”:“xyp3l9obelI”,“value”:55654},{“attribute”:“ul7UIuUoP1Z”,“value”:“5654”},{“attribute”:“rOwntnIQh2P”,“value”:“56546”},{“attribute”:“QnwIsiKw2NF”,“value”:“5654”},{“attribute”:“SZ05eUTBMEN”,“value”:“6546”},{“attribute”:“tNGC3SeoHbb”,“value”:“5656”},{“attribute”:“FQGMFSwKUkB”,“value”:56546},{“attribute”:“VsUAhCcttyf”,“value”:“56546”}]}

Note there are no dates in this even though they were entered on the form. This seems wrong, I guess this is what causes the sql to fail.

Regards

Bob

On 17 March 2015 at 14:26, Abyot Gizaw abyota@gmail.com wrote:

Hello Randy,

Are you using the individual records module?

Can you try tracker capture app?


Thank you,

Abyot.

(sent from mobile)

On Mar 17, 2015 3:15 PM, “Wilson, Randy” rwilson@msh.org wrote:

We’re setting up a tracker module to capture data from individual community health workers using Multiple events with registration.

We have the program and stage as well as attributes and data elements - using 3 different instances of DHIS-2.

When we try to create a new instance we fill in the form, but when we click on Add, the screen freezes. The instance is not saved so we can’t enter any data.

We are using version 2.18 build 18143

Any guidance would be much appreciated… we’re stuck.

Here is the log:

  • INFO 2015-03-17 16:08:42,610 ‘randy’ create org.hisp.dhis.trackedentity.Track

edEntityInstance, uid: S4SGPUtDl0o (AuditLogUtil.java [http-bio-8080-exec-6])

  • INFO 2015-03-17 16:08:42,650 ‘randy’ update org.hisp.dhis.trackedentity.Track

edEntityInstance, uid: S4SGPUtDl0o (AuditLogUtil.java [http-bio-8080-exec-6])

  • WARN 2015-03-17 16:08:42,650 SQL Error: 0, SQLState: 23502 (SqlExceptionHelpe

r.java [http-bio-8080-exec-6])

  • ERROR 2015-03-17 16:08:42,650 ERROR: null value in column “registrationdate” v

iolates not-null constraint

Detail: Failing row contains (19556, null, null, null, null, null, null, null,

null, 872, null, null, S4SGPUtDl0o, null, 2015-03-17 16:08:42.61, 2015-03-17 16

:08:42.61, null, 17032). (SqlExceptionHelper.java [http-bio-8080-exec-6])

  • ERROR 2015-03-17 16:08:42,660 HHH000352: Unable to release batch statement…

(AbstractBatchImpl.java [http-bio-8080-exec-6])

  • ERROR 2015-03-17 16:08:42,670 HHH000246: SQLException escaped proxy (AbstractB

atchImpl.java [http-bio-8080-exec-6])

java.sql.SQLException: You can’t operate on a closed Statement!!!


Randy Wilson
*Team Leader: *Knowledge Management, Data Use and Research

Rwanda Health System Strengthening Activity

Management Sciences for Health

Rwanda-Kigali

Direct: +250 788308835

E-mail: rwilson@msh.org

Skype: wilsonrandy_us

Stronger health systems. Greater health impact.

www.msh.org

This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp

Thanks Bob for fixing this.
Abyot, thanks your detailed explanation of the module.

Together we win!

Alex

···

On Wed, Mar 18, 2015 at 6:29 PM, Abyot Gizaw abyota@gmail.com wrote:

Great !


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp


Thank you,

Abyot.

On Wed, Mar 18, 2015 at 4:28 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

I just dropped these columns and it is now working. Thanks Abyot and Alex …

On 18 March 2015 at 15:15, Bob Jolliffe bobjolliffe@gmail.com wrote:

Hi Abyot

Looking at the upgrade script it ends with

ALTER TABLE patient DROP COLUMN gender;

ALTER TABLE patient DROP COLUMN deathDate;

ALTER TABLE patient DROP COLUMN registrationDate;

ALTER TABLE patient DROP COLUMN isDead;

ALTER TABLE patient DROP COLUMN underAge;

ALTER TABLE patient DROP COLUMN dobType;

ALTER TABLE patient DROP COLUMN birthdate;

ALTER TABLE patient DROP COLUMN phoneNumber;

ALTER TABLE patient DROP COLUMN name;

ALTER TABLE patient DROP COLUMN healthworkerid

which removes all the old static attributes (obviously table name has changed). I see that the earlier part of the script is dedicated to creating dynamic attributes for these and copying over the data. If there is no existing data is there still a need to create these formerly fixed attributes?

On 18 March 2015 at 15:10, Abyot Gizaw abyota@gmail.com wrote:

Let’s hope for that … but at the same time it not about removing a column - it is more than that and a bit complex.


Thank you,

Abyot.

On Wed, Mar 18, 2015 at 4:06 PM, Wilson, Randy rwilson@msh.org wrote:

Thanks for the troubleshooting. We’ll try removing the extra static columns on an offline instance and let you know.

I’m sure it will do the trick.

Randy

This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.

On Wed, Mar 18, 2015 at 4:53 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

The table does look exactly like it has many static atteruibutes which should have moved to dynamic, so probably some upgrade script was not applied.

The rwanda implementation does have a fairly long vintage. I’ll check that old upgrade script and see if it fixes the problem. Thanks Abyot.


Randy Wilson
*Team Leader: *Knowledge Management, Data Use and Research

Rwanda Health System Strengthening Activity

Management Sciences for Health

Rwanda-Kigali

Direct: +250 788308835

E-mail: rwilson@msh.org

Skype: wilsonrandy_us

Stronger health systems. Greater health impact.

www.msh.org

On 18 March 2015 at 14:45, Abyot Gizaw abyota@gmail.com wrote:

we used to have that attribute. see the commit from Tran (Rev: 13239)

That was supposed to be removed when migrating static to dynamic attributes … this then leads to another bigger issue - have you made a proper upgrade?


Thank you,

Abyot.

On Wed, Mar 18, 2015 at 3:36 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

Hi Abyot

Thanks for the explanation. That makes sense. So the second post is never happening because the registration is not completed.

Alex raises an interesting possibility. There is a column called registrationdate on trackedentityinstance. Is this meant to be there or could it be a hangover from an earlier version of the table?

I guess randy can try with 2.18 but I have been testing on one of the production servers so I can’t really upgrade just to test this.

On 18 March 2015 at 14:32, Abyot Gizaw abyota@gmail.com wrote:

It is a two step process… first registration is done meaning server returning uid, then using this uid another json is posted (this time the enrollment details are sent). What I think has happened is server failed to complete registration. Looking the log - do you have an attribute called registrationdate which is set mandatory?

Also, can you make sure you are trying this in 2.18? of course you can continue with 2.17 but just saying that 2.18 is more stable. I just did a test on the demo server (which is 2.18) and it is working fine.

One more thing… if you have made changes to your metadata once the tracker app has run - you need to clear cache to that the new meta-data is cached locally. We don’t have a feature to auto-update local-cache.


Thank you,

Abyot.

On Wed, Mar 18, 2015 at 2:53 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

Hi Abyot

The log shows what Randy initially reported:

  • ERROR 2015-03-18 14:19:55,836 ERROR: null value in column “registrationdate” v

iolates not-null constraint

Detail: Failing row contains (29412, null, null, null, null, null, null, null,

null, 872, null, null, Ktl3NTLuGlK, null, 2015-03-18 14:19:55.805, 2015-03-18 1

4:19:55.805, null, 17032). (SqlExceptionHelper.java [tomcat-http-10])

I am not sure about which instance randy has tested 2.18 on, but this is definitely 2.17. (I think he thought that this instance was also 2.18, but its not)

According to the form the Enrollment date and Reporting date are required fields (see screenshot). Do you mean that they are simply ignored on initial registration?

So where does the registration date come from? From the server date?

Bob

On 18 March 2015 at 13:01, Abyot Gizaw abyota@gmail.com wrote:

Hi Bob,

That is just for registration … then enrollment follows with enrollment and incident dates. Most probably something has failed in between - is there any log?


Thank you,

Abyot.

On Wed, Mar 18, 2015 at 1:48 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

Hi Abyot

I just had a quick look at the tracker app on one of the Rwanda dhis2 instances (it is running 2.17 built on 2015-01-21 02:05 - strange I don’t see the build revision)

The form has some attributes and the Enrollment date and Reporting date at the bottom. When I try to save I see that the following is POSTed.

{“trackedEntity”:“BQu4uXKyrRE”,“orgUnit”:“BPZcHDS6OO0”,“attributes”:[{“attribute”:“xyp3l9obelI”,“value”:55654},{“attribute”:“ul7UIuUoP1Z”,“value”:“5654”},{“attribute”:“rOwntnIQh2P”,“value”:“56546”},{“attribute”:“QnwIsiKw2NF”,“value”:“5654”},{“attribute”:“SZ05eUTBMEN”,“value”:“6546”},{“attribute”:“tNGC3SeoHbb”,“value”:“5656”},{“attribute”:“FQGMFSwKUkB”,“value”:56546},{“attribute”:“VsUAhCcttyf”,“value”:“56546”}]}

Note there are no dates in this even though they were entered on the form. This seems wrong, I guess this is what causes the sql to fail.

Regards

Bob

On 17 March 2015 at 14:26, Abyot Gizaw abyota@gmail.com wrote:

Hello Randy,

Are you using the individual records module?

Can you try tracker capture app?


Thank you,

Abyot.

(sent from mobile)

On Mar 17, 2015 3:15 PM, “Wilson, Randy” rwilson@msh.org wrote:

We’re setting up a tracker module to capture data from individual community health workers using Multiple events with registration.

We have the program and stage as well as attributes and data elements - using 3 different instances of DHIS-2.

When we try to create a new instance we fill in the form, but when we click on Add, the screen freezes. The instance is not saved so we can’t enter any data.

We are using version 2.18 build 18143

Any guidance would be much appreciated… we’re stuck.

Here is the log:

  • INFO 2015-03-17 16:08:42,610 ‘randy’ create org.hisp.dhis.trackedentity.Track

edEntityInstance, uid: S4SGPUtDl0o (AuditLogUtil.java [http-bio-8080-exec-6])

  • INFO 2015-03-17 16:08:42,650 ‘randy’ update org.hisp.dhis.trackedentity.Track

edEntityInstance, uid: S4SGPUtDl0o (AuditLogUtil.java [http-bio-8080-exec-6])

  • WARN 2015-03-17 16:08:42,650 SQL Error: 0, SQLState: 23502 (SqlExceptionHelpe

r.java [http-bio-8080-exec-6])

  • ERROR 2015-03-17 16:08:42,650 ERROR: null value in column “registrationdate” v

iolates not-null constraint

Detail: Failing row contains (19556, null, null, null, null, null, null, null,

null, 872, null, null, S4SGPUtDl0o, null, 2015-03-17 16:08:42.61, 2015-03-17 16

:08:42.61, null, 17032). (SqlExceptionHelper.java [http-bio-8080-exec-6])

  • ERROR 2015-03-17 16:08:42,660 HHH000352: Unable to release batch statement…

(AbstractBatchImpl.java [http-bio-8080-exec-6])

  • ERROR 2015-03-17 16:08:42,670 HHH000246: SQLException escaped proxy (AbstractB

atchImpl.java [http-bio-8080-exec-6])

java.sql.SQLException: You can’t operate on a closed Statement!!!


Randy Wilson
*Team Leader: *Knowledge Management, Data Use and Research

Rwanda Health System Strengthening Activity

Management Sciences for Health

Rwanda-Kigali

Direct: +250 788308835

E-mail: rwilson@msh.org

Skype: wilsonrandy_us

Stronger health systems. Greater health impact.

www.msh.org

This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp

Alex Tumwesigye

Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET

Kampala

Uganda

IT Consultant - BarefootPower Uganda Ltd, SmartSolar, Kenya

IT Specialist (Servers, Networks and Security, Health Information Systems - DHIS2 ) & Solar Consultant

+256 774149 775, + 256 759 800161

"I don’t want to be anything other than what I have been - one tree hill "