A quick brief on etiquette.
1. Please do not harvest emails and send linked in requests
2. Do not mark questions as urgent and do provide sufficient details to
reproduce the problem
What I see here is that there is a bit of custom code that is “causing” the
issue.
at
com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:104)
at javax.xml.ws.Service.<init>(Service.java:77)
Above here are JARs / runtime in the classpath
at com.att.lsrv.preorder.PreOrderService.<init>(Unknown Source)
at porequest.control.LviCsClient.getLviCsClientProxy(Unknown Source)
at porequest.control.LviCsClient.getCSRResponse(Unknown Source)
at porequest.control.MainControllerServlet.CsrqResponse(Unknown Source)
at porequest.control.MainControllerServlet.doPost(Unknown Source)
Below here is tomcat..
at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)
You indicate that this was on Tomcat 6.0.35, but you did not confirm the JVM it
was running on. I am skeptical since the Tomcat version you indicated was
released before Java 8 (2012 vs 2014) – but I am more skeptical that 6.0.35 was
not customized. Have you deployed the application to an “out of the box” 6.0.35
on the same JVM as 8.5.5?
Have you reached out to your developer of the com.att.lsrv and
porequest.control code? You should have a test case to prove the issue out.
-Jason
From: Lavitesh Verma <[email protected]>
Sent: Monday, June 15, 2020 9:29 AM
To: Jason Pyeron <[email protected]>; 'Tomcat Users List'
<[email protected]>
Cc: 'RUBIN, JACOB' <[email protected]>; [email protected]; Vasudev Wadhawan
<[email protected]>
Subject: RE: [tomcat-users] Issue found during migration of Tomcat version
6.0.35 to 8.5.5
Hi Jason,
We have updated the xercesImpl from version 2.6.2 to 2.12.0 for the migration
and no new jars were added for the new environment.
We didn’t use Woodstox StAX jar with tomcat 6.0.35 and did not face any such
issue.
PFA the complete Stack Trace for the Issue.
Thanks & Regards
Lavitesh Verma
Software Engineering Associate
Amdocs Global SmartOps
+91.9810157771
OOO – 06/16 – 06/19
From: Jason Pyeron <[email protected] <mailto:[email protected]> >
Sent: Monday, June 15, 2020 6:15 PM
To: 'Tomcat Users List' <[email protected]
<mailto:[email protected]> >
Cc: 'RUBIN, JACOB' <[email protected] <mailto:[email protected]> >;
[email protected] <mailto:[email protected]> ; Vasudev Wadhawan
<[email protected] <mailto:[email protected]> >
Subject: RE: [tomcat-users] Issue found during migration of Tomcat version
6.0.35 to 8.5.5
Sounds like you have added Jars to the old environment that are not in the new
environment.
What is the offending code that causes the error?
What were your customizations against the 6.0.35 environment?
Is the Woodstox StAX jar in the web application or Tomcat lib directory? Where
was it previously?
Did you test this before you migrated causing this “urgent” issue? What is
different between your test and this urgent outage’s configuration.
-Jason
From: Lavitesh Verma [mailto:[email protected]]
Sent: Monday, June 15, 2020 8:16 AM
To: [email protected] <mailto:[email protected]>
Cc: RUBIN, JACOB <[email protected] <mailto:[email protected]> >;
[email protected] <mailto:[email protected]> ; Vasudev Wadhawan
<[email protected] <mailto:[email protected]> >
Subject: [tomcat-users] Issue found during migration of Tomcat version 6.0.35
to 8.5.5
Importance: High
Hi Team,
Below are the details of the system and tomcat version
Old tomcat version: Apache Tomcat/6.0.35
New tomcat version: Apache Tomcat/8.5.5
Operating System: SunOS
OS Version: 5.10
Architecture: sparcv9
JVM Version: 1.8.0_101-b13
Vendor: Oracle Corporation
We are trying to migrate Apache Tomcat version 6.0.35 to 8.5.5.
We found the issue javax.xml.stream.FactoryConfigurationError: Provider
com.ctc.wstx.stax.WstxInputFactory not found in localhost logs.
Could you please assist on how we could resolve the issue.
Thanks & Regards
Lavitesh Verma
Software Engineering Associate
Amdocs Global SmartOps
+91.9810157771
OOO – 06/16 – 06/19
This email and the information contained herein is proprietary and confidential
and subject to the Amdocs Email Terms of Service, which you may review at
https://www.amdocs.com/about/email-terms-of-service
This email and the information contained herein is proprietary and confidential
and subject to the Amdocs Email Terms of Service, which you may review at
<https://www.amdocs.com/about/email-terms-of-service>
https://www.amdocs.com/about/email-terms-of-service
