Hi,
One of the futures of my project works on both DEV and Live servers but not on UAT.
When option 'All Process' is selected from dropdown list, partial page brings the table with SLA values for all Admin process, then after changing one of the values, 'Pass to' dropdown appears with list of Authorisers. After choosing the checker and pressing Complete, form resets instead of completing. It's only happening for that one selection and only in UAT.
I have stopped the UAT server, delete process and moved it across from DEV, but that didn't solve the problem. Process is identical across all servers on BPS too.
We found some errors in tomcat7wm-stderr logs in both Dev and UAT too:
Nov 20, 2017 10:42:01 AM org.apache.tomcat.util.http.Parameters processParameters
INFO: Invalid chunk starting at byte [14,648] and ending at byte [14,666] with a value of [=a%0Ab%0Ac%0Ad%0Ae] ignored
Note: further occurrences of Parameter errors will be logged at DEBUG level.
Nov 21, 2017 2:20:39 PM org.apache.tomcat.util.http.Parameters processParameters
INFO: Invalid chunk starting at byte [32,913] and ending at byte [32,931] with a value of [=a%0Ab%0Ac%0Ad%0Ae] ignored
Note: further occurrences of Parameter errors will be logged at DEBUG level.
Nov 22, 2017 3:04:24 PM org.apache.tomcat.util.http.Parameters processParameters
INFO: Invalid chunk starting at byte [32,908] and ending at byte [32,926] with a value of [=a%0Ab%0Ac%0Ad%0Ae] ignored
Note: further occurrences of Parameter errors will be logged at DEBUG level.
Nov 24, 2017 10:54:24 AM org.apache.tomcat.util.http.Parameters processParameters
INFO: Invalid chunk starting at byte [14,639] and ending at byte [14,657] with a value of [=a%0Ab%0Ac%0Ad%0Ae] ignored
Note: further occurrences of Parameter errors will be logged at DEBUG level.
Nov 27, 2017 10:39:35 AM org.apache.tomcat.util.http.Parameters processParameters
INFO: Invalid chunk starting at byte [14,639] and ending at byte [14,657] with a value of [=a%0Ab%0Ac%0Ad%0Ae] ignored
Note: further occurrences of Parameter errors will be logged at DEBUG level.
gram%20Files/Apache%20Software%20Foundation/Tomcat%207.0_Tomcat7WM/webapps/bizflowwebmaker/SLA_Maintenance/doc/JLT_MNT/mvc/SLA_Maintenance/views/view/Page_Painter/; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
file:/D:/Program%20Files/Apache%20Software%20Foundation/Tomcat%207.0_Tomcat7WM/webapps/bizflowwebmaker/SLA_Maintenance/doc/JLT_MNT/mvc/SLA_Maintenance/views/view/Page_Painter/; Line #1; Column #1; org.xml.sax.SAXParseException; systemId: file:/D:/Program%20Files/Apache%20Software%20Foundation/Tomcat%207.0_Tomcat7WM/webapps/bizflowwebmaker/SLA_Maintenance/doc/JLT_MNT/mvc/SLA_Maintenance/views/view/Page_Painter/; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
Do you have any ideas what can cause that issue?
Regards,
Kat
One of the futures of my project works on both DEV and Live servers but not on UAT.
When option 'All Process' is selected from dropdown list, partial page brings the table with SLA values for all Admin process, then after changing one of the values, 'Pass to' dropdown appears with list of Authorisers. After choosing the checker and pressing Complete, form resets instead of completing. It's only happening for that one selection and only in UAT.
I have stopped the UAT server, delete process and moved it across from DEV, but that didn't solve the problem. Process is identical across all servers on BPS too.
We found some errors in tomcat7wm-stderr logs in both Dev and UAT too:
Nov 20, 2017 10:42:01 AM org.apache.tomcat.util.http.Parameters processParameters
INFO: Invalid chunk starting at byte [14,648] and ending at byte [14,666] with a value of [=a%0Ab%0Ac%0Ad%0Ae] ignored
Note: further occurrences of Parameter errors will be logged at DEBUG level.
Nov 21, 2017 2:20:39 PM org.apache.tomcat.util.http.Parameters processParameters
INFO: Invalid chunk starting at byte [32,913] and ending at byte [32,931] with a value of [=a%0Ab%0Ac%0Ad%0Ae] ignored
Note: further occurrences of Parameter errors will be logged at DEBUG level.
Nov 22, 2017 3:04:24 PM org.apache.tomcat.util.http.Parameters processParameters
INFO: Invalid chunk starting at byte [32,908] and ending at byte [32,926] with a value of [=a%0Ab%0Ac%0Ad%0Ae] ignored
Note: further occurrences of Parameter errors will be logged at DEBUG level.
Nov 24, 2017 10:54:24 AM org.apache.tomcat.util.http.Parameters processParameters
INFO: Invalid chunk starting at byte [14,639] and ending at byte [14,657] with a value of [=a%0Ab%0Ac%0Ad%0Ae] ignored
Note: further occurrences of Parameter errors will be logged at DEBUG level.
Nov 27, 2017 10:39:35 AM org.apache.tomcat.util.http.Parameters processParameters
INFO: Invalid chunk starting at byte [14,639] and ending at byte [14,657] with a value of [=a%0Ab%0Ac%0Ad%0Ae] ignored
Note: further occurrences of Parameter errors will be logged at DEBUG level.
gram%20Files/Apache%20Software%20Foundation/Tomcat%207.0_Tomcat7WM/webapps/bizflowwebmaker/SLA_Maintenance/doc/JLT_MNT/mvc/SLA_Maintenance/views/view/Page_Painter/; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
file:/D:/Program%20Files/Apache%20Software%20Foundation/Tomcat%207.0_Tomcat7WM/webapps/bizflowwebmaker/SLA_Maintenance/doc/JLT_MNT/mvc/SLA_Maintenance/views/view/Page_Painter/; Line #1; Column #1; org.xml.sax.SAXParseException; systemId: file:/D:/Program%20Files/Apache%20Software%20Foundation/Tomcat%207.0_Tomcat7WM/webapps/bizflowwebmaker/SLA_Maintenance/doc/JLT_MNT/mvc/SLA_Maintenance/views/view/Page_Painter/; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
Do you have any ideas what can cause that issue?
Regards,
Kat
RE: Process works on DEV and Live servers, but not in UAT
That does sound strange behaviour.
The first thing I would suggest would be to clear out your browser cache, just to make sure there isn+?+?+?t an older file being cached for that particular server. It would also be worth checking to see if you are getting any script errors being reported by the browser.
Otherwise, if the WebMaker application is the same on all environments, then I would think the different behaviour would be being caused by differences in the data returned from the web service or database calls.
Are you able to capture full development log traces from the working DEV environment, and the broken UAT one? If so, it would be worth comparing these to look for any differences in the data being retrieved.
With regards to the log entries you have posted, do you know if these line up with the problem you are getting, or are these logged at other points? The fact you are getting these in the Dev environment as well, which is otherwise working, makes me think these might not be related to the problem you mention.
Regards,
Gerard