|
Title: GAS down with overlapping message in log Post by: Najmi N. on October 26, 2010, 06:56:38 am Hi
I'm running the application with Genero BDL 2.21.01 , GAS 2.21.05, in RH Linux 5.3 platform with Informix 11.5 database. I have a program which passing the argument parameter during execution. My curious, the GAS will be always down when I execute this program. But I'm able to ran the program using Genero DEsktop client. Following is the message in the GAS log when I execute the program :- 11:43:52 3276 MUTEX=469118992;VM=7;WA=473569600;TEMPLATE "Warning" Data Size=121 Content=Element 'Grid (idRef: 413)' has only partially be rendered, because it contains at least one element overlapping another. Below is how the program been executed :- fglrun-bin prgname IN XYZ DB=dbname Note: IN and OUT is 1st argument while XYZ is company code as 2nd argument. I don't understand why this can make the GAS down. We had tried use other name beside IN and OUT(feel if this is something Genero specific variable which can't be used) , but it still the same. Apprecite some input from other if known or had encounter such problem to share the solution. Regards Title: Re: GAS down with overlapping message in log Post by: Sisavanh S. on October 26, 2010, 11:05:00 am Hi,
You are using GAS 2.21.05. I suggest that you upgrade to 2.22.04. You might need to migrate your snippets. About the warning in the log, the message sound like bug: 11553 - GAS engine may crash when the tablePageHeightThreshold style attribute is used But this bug has already been fixed in 2.20. Please contact your local support center, they will help you track the issue. Best regards, Sisa. Title: Re: GAS down with overlapping message in log Post by: Reuben B. on October 27, 2010, 10:53:21 pm Hi, You are using GAS 2.21.05. I suggest that you upgrade to 2.22.04. You might need to migrate your snippets. About the warning in the log, the message sound like bug: 11553 - GAS engine may crash when the tablePageHeightThreshold style attribute is used But this bug has already been fixed in 2.20. Please contact your local support center, they will help you track the issue. Best regards, Sisa. Hi Sisa, We tracked this down to some code doing some DOM Tree manipulation on a Checkbox and/or its text attribute. If I can get a small example to reproduce I'll send in via support channels. Reuben |