Greetings,
I have a problem about inconsistency of 2 environment. The system consist of :
QA Environment:
Oracle RDBMS 8.1.7.4 (in #1 HP-UX box)
Oracle 9IAS running J2EE 1.2 (in #2 HP-UX box)
Production Environment:
Oracle RDBMS 8.1.7.1b (in #3 HP-UX box)
Oracle 9IAS running J2EE 1.3 (in #4 HP-UX box)
I have the vendor develop web-application in EAR file. The deployment of EAR file is exactly the same for both QA and Prod. However, there are 2 screens (out of about 40 screens) that have problem in only Production server. Below is the error message.
500 Internal Server Error
OracleJSP: oracle.jsp.parse.JspParseException: Line # 12, <%@ page language="java" import="com.pg.aaipos.util.UserSession,com.pg.aaipos.util.Trace"%>
Error: Error, attribute defined twice: language
I tried the internal support team, but they said nothing wrong with the 9IAS. They have tried pointed production 9IAS into QA RDBMS - and it works fine. So they expected problem is might be something within either the Database itself or in the incompatibility between 8.1.7.4 and 8.1.7.1b.
Any ideas or suggestions would be greatly appreciated.
Best Regards,
Comgrit Sirisangchaikul
I have a problem about inconsistency of 2 environment. The system consist of :
QA Environment:
Oracle RDBMS 8.1.7.4 (in #1 HP-UX box)
Oracle 9IAS running J2EE 1.2 (in #2 HP-UX box)
Production Environment:
Oracle RDBMS 8.1.7.1b (in #3 HP-UX box)
Oracle 9IAS running J2EE 1.3 (in #4 HP-UX box)
I have the vendor develop web-application in EAR file. The deployment of EAR file is exactly the same for both QA and Prod. However, there are 2 screens (out of about 40 screens) that have problem in only Production server. Below is the error message.
500 Internal Server Error
OracleJSP: oracle.jsp.parse.JspParseException: Line # 12, <%@ page language="java" import="com.pg.aaipos.util.UserSession,com.pg.aaipos.util.Trace"%>
Error: Error, attribute defined twice: language
I tried the internal support team, but they said nothing wrong with the 9IAS. They have tried pointed production 9IAS into QA RDBMS - and it works fine. So they expected problem is might be something within either the Database itself or in the incompatibility between 8.1.7.4 and 8.1.7.1b.
Any ideas or suggestions would be greatly appreciated.
Best Regards,
Comgrit Sirisangchaikul