Ordermgr errors on demo-trunk.ofbiz.apache.org

[Pawan Verma]

Hello Devs,

Just saw some unusual errors on demo-trunk.ofbiz.apache.org for ordermgr
component. Most of the Order screens are broken.

At first glance, it seems some deployment issues because most of the
screens are broken. At my local, after the latest update these screens seem
to be working fine.

Does anyone know about it? TIA
--
Thanks & Regards
Pawan Verma
Technical Consultant
*HotWax Systems*
*Enterprise open source experts*
http://www.hotwaxsystems.com

[Jacques Le Roux]

Hi Pawan,

It seems related to this error:

Caused by: org.apache.ofbiz.service.GenericServiceException: Error running Groovy method [getPartyNameForDate] in Groovy file
[component://party/groovyScripts/party/PartyServices.groovy]: (The field name (or key) [gender] is not valid for entity [PartyNameHistory].)

But I updated locally to HEAD and can't reproduce either

It could be related to OFBIZ-11506 but that's 5 weeks ago, so I doubt. Maybe someone screwed the data on trunk demo. How I have no ideas.

Also when I get to ordermgr on trunk demo, the 1st error I get in log is:

- Failed at: #assign billToPartyNameResult = dispa...  [in template "component://order/template/order/OrderListByDate.ftl" at line 51, column 13]

HTH

Jacques

Le 23/05/2020 à 16:27, Pawan Verma a écrit :

> Hello Devs,
>
> Just saw some unusual errors on demo-trunk.ofbiz.apache.org for ordermgr
> component. Most of the Order screens are broken.
>
> At first glance, it seems some deployment issues because most of the
> screens are broken. At my local, after the latest update these screens seem
> to be working fine.
>
> Does anyone know about it? TIA

[Jacques Le Roux]

Hi Pawan,

It seems related to this error:

Caused by: org.apache.ofbiz.service.GenericServiceException: Error running Groovy method [getPartyNameForDate] in Groovy file
[component://party/groovyScripts/party/PartyServices.groovy]: (The field name (or key) [gender] is not valid for entity [PartyNameHistory].)

But I updated locally to HEAD and can't reproduce either

It could be related to OFBIZ-11506 but that's 5 weeks ago, so I doubt. Maybe someone screwed the data on trunk demo. How I have no ideas.

Also when I get to ordermgr on trunk demo, the 1st error I get in log is:

- Failed at: #assign billToPartyNameResult = dispa...  [in template "component://order/template/order/OrderListByDate.ftl" at line 51, column 13]

At this stage I think it's better to wait tomorrow morning to see if it reproduces. But yes something seems wrong with data and that's not normal.

HTH

Jacques

Le 23/05/2020 à 16:27, Pawan Verma a écrit :

> Hello Devs,
>
> Just saw some unusual errors on demo-trunk.ofbiz.apache.org for ordermgr
> component. Most of the Order screens are broken.
>
> At first glance, it seems some deployment issues because most of the
> screens are broken. At my local, after the latest update these screens seem
> to be working fine.
>
> Does anyone know about it? TIA

[Pawan Verma]

Hello Everyone,

I dig around the issue and found that getPartyNameForDate is the main
culprit for this issue. It can be easily generated on the local instance by
updating the admin's name.

Updating name will create a new record in PartyNameHistory entity and
service getPartyNameForDate has an issue while trying to fetch the name.

The reason for this issue is code is trying to get the gender of a person
from partyNameHistory record and gender is not a field in the
partyNameHistory entity. During conversion we minimized duplicate code
which caused that issue. Conversion is done under OFBIZ-11361.

I've added a check to avoid checking gender in the partyNameHistory record
at 3f9e377 under OFBIZ-11736.

A special thanks to Unknown person who tried to update the admin's name and
due to which we got this error :)

--
Thanks & Regards
Pawan Verma
Technical Consultant
*HotWax Systems*
*Enterprise open source experts*
http://www.hotwaxsystems.com


On Sat, May 23, 2020 at 8:28 PM Jacques Le Roux <
[hidden email]> wrote:

> Hi Pawan,
>
> It seems related to this error:
>
> Caused by: org.apache.ofbiz.service.GenericServiceException: Error running
> Groovy method [getPartyNameForDate] in Groovy file
> [component://party/groovyScripts/party/PartyServices.groovy]: (The field
> name (or key) [gender] is not valid for entity [PartyNameHistory].)
>
> But I updated locally to HEAD and can't reproduce either
>
> It could be related to OFBIZ-11506 but that's 5 weeks ago, so I doubt.
> Maybe someone screwed the data on trunk demo. How I have no ideas.
>
> Also when I get to ordermgr on trunk demo, the 1st error I get in log is:
>
> - Failed at: #assign billToPartyNameResult = dispa...  [in template
> "component://order/template/order/OrderListByDate.ftl" at line 51, column
> 13]
>
> At this stage I think it's better to wait tomorrow morning to see if it
> reproduces. But yes something seems wrong with data and that's not normal.
>
> HTH
>
> Jacques
>
> Le 23/05/2020 à 16:27, Pawan Verma a écrit :
> > Hello Devs,
> >
> > Just saw some unusual errors on demo-trunk.ofbiz.apache.org for ordermgr
> > component. Most of the Order screens are broken.
> >
> > At first glance, it seems some deployment issues because most of the
> > screens are broken. At my local, after the latest update these screens
> seem
> > to be working fine.
> >
> > Does anyone know about it? TIA
>
>

[Pierre Smits-3]

Thanks Pawan, for the quick action.

Op za 23 mei 2020 20:16 schreef Pawan Verma <[hidden email]>:

> Hello Everyone,
>
> I dig around the issue and found that getPartyNameForDate is the main
> culprit for this issue. It can be easily generated on the local instance by
> updating the admin's name.
>
> Updating name will create a new record in PartyNameHistory entity and
> service getPartyNameForDate has an issue while trying to fetch the name.
>
> The reason for this issue is code is trying to get the gender of a person
> from partyNameHistory record and gender is not a field in the
> partyNameHistory entity. During conversion we minimized duplicate code
> which caused that issue. Conversion is done under OFBIZ-11361.
>
> I've added a check to avoid checking gender in the partyNameHistory record
> at 3f9e377 under OFBIZ-11736.
>
> A special thanks to Unknown person who tried to update the admin's name and
> due to which we got this error :)
>
> --
> Thanks & Regards
> Pawan Verma
> Technical Consultant
> *HotWax Systems*
> *Enterprise open source experts*
> http://www.hotwaxsystems.com
>
>
> On Sat, May 23, 2020 at 8:28 PM Jacques Le Roux <
> [hidden email]> wrote:
>
> > Hi Pawan,
> >
> > It seems related to this error:
> >
> > Caused by: org.apache.ofbiz.service.GenericServiceException: Error
> running
> > Groovy method [getPartyNameForDate] in Groovy file
> > [component://party/groovyScripts/party/PartyServices.groovy]: (The field
> > name (or key) [gender] is not valid for entity [PartyNameHistory].)
> >
> > But I updated locally to HEAD and can't reproduce either
> >
> > It could be related to OFBIZ-11506 but that's 5 weeks ago, so I doubt.
> > Maybe someone screwed the data on trunk demo. How I have no ideas.
> >
> > Also when I get to ordermgr on trunk demo, the 1st error I get in log is:
> >
> > - Failed at: #assign billToPartyNameResult = dispa...  [in template
> > "component://order/template/order/OrderListByDate.ftl" at line 51, column
> > 13]
> >
> > At this stage I think it's better to wait tomorrow morning to see if it
> > reproduces. But yes something seems wrong with data and that's not
> normal.
> >
> > HTH
> >
> > Jacques
> >
> > Le 23/05/2020 à 16:27, Pawan Verma a écrit :
> > > Hello Devs,
> > >
> > > Just saw some unusual errors on demo-trunk.ofbiz.apache.org for
> ordermgr
> > > component. Most of the Order screens are broken.
> > >
> > > At first glance, it seems some deployment issues because most of the
> > > screens are broken. At my local, after the latest update these screens
> > seem
> > > to be working fine.
> > >
> > > Does anyone know about it? TIA
> >
> >
>

[Jacques Le Roux]

Thanks Pawan!

Le 23/05/2020 à 20:58, Pierre Smits a écrit :

> Thanks Pawan, for the quick action.
>
> Op za 23 mei 2020 20:16 schreef Pawan Verma <[hidden email]>:
>
>> Hello Everyone,
>>
>> I dig around the issue and found that getPartyNameForDate is the main
>> culprit for this issue. It can be easily generated on the local instance by
>> updating the admin's name.
>>
>> Updating name will create a new record in PartyNameHistory entity and
>> service getPartyNameForDate has an issue while trying to fetch the name.
>>
>> The reason for this issue is code is trying to get the gender of a person
>> from partyNameHistory record and gender is not a field in the
>> partyNameHistory entity. During conversion we minimized duplicate code
>> which caused that issue. Conversion is done under OFBIZ-11361.
>>
>> I've added a check to avoid checking gender in the partyNameHistory record
>> at 3f9e377 under OFBIZ-11736.
>>
>> A special thanks to Unknown person who tried to update the admin's name and
>> due to which we got this error :)
>>
>> --
>> Thanks & Regards
>> Pawan Verma
>> Technical Consultant
>> *HotWax Systems*
>> *Enterprise open source experts*
>> http://www.hotwaxsystems.com
>>
>>
>> On Sat, May 23, 2020 at 8:28 PM Jacques Le Roux <
>> [hidden email]> wrote:
>>
>>> Hi Pawan,
>>>
>>> It seems related to this error:
>>>
>>> Caused by: org.apache.ofbiz.service.GenericServiceException: Error
>> running
>>> Groovy method [getPartyNameForDate] in Groovy file
>>> [component://party/groovyScripts/party/PartyServices.groovy]: (The field
>>> name (or key) [gender] is not valid for entity [PartyNameHistory].)
>>>
>>> But I updated locally to HEAD and can't reproduce either
>>>
>>> It could be related to OFBIZ-11506 but that's 5 weeks ago, so I doubt.
>>> Maybe someone screwed the data on trunk demo. How I have no ideas.
>>>
>>> Also when I get to ordermgr on trunk demo, the 1st error I get in log is:
>>>
>>> - Failed at: #assign billToPartyNameResult = dispa...  [in template
>>> "component://order/template/order/OrderListByDate.ftl" at line 51, column
>>> 13]
>>>
>>> At this stage I think it's better to wait tomorrow morning to see if it
>>> reproduces. But yes something seems wrong with data and that's not
>> normal.
>>> HTH
>>>
>>> Jacques
>>>
>>> Le 23/05/2020 à 16:27, Pawan Verma a écrit :
>>>> Hello Devs,
>>>>
>>>> Just saw some unusual errors on demo-trunk.ofbiz.apache.org for
>> ordermgr
>>>> component. Most of the Order screens are broken.
>>>>
>>>> At first glance, it seems some deployment issues because most of the
>>>> screens are broken. At my local, after the latest update these screens
>>> seem
>>>> to be working fine.
>>>>
>>>> Does anyone know about it? TIA
>>>