HI Jason,

Below are the details for the Tomcat 6 version, that we used before,
Server version: Apache Tomcat/6.0.35
Server number:  6.0.35.0
OS Name:        SunOS
OS Version:     5.10
Architecture:   sparcv9
JVM Version:    1.8.0_101-b13
JVM Vendor:     Oracle Corporation

We don't face any issue on the other test environment that we are facing on 
updating to 8.5.5.

Thanks & Regards
Lavitesh Verma
Software Engineering Associate
Amdocs Global SmartOps
[download12]+91.9810157771
OOO - 06/16 - 06/19
[cid:image001.jpg@01D2912B.17505E90]

From: Jason Pyeron <jpye...@pdinc.us>
Sent: Monday, June 15, 2020 7:33 PM
To: 'Tomcat Users List' <users@tomcat.apache.org>
Cc: 'RUBIN, JACOB' <jr2...@att.com>; lsrv...@list.att.com; Vasudev Wadhawan 
<vasudev.wadha...@amdocs.com>
Subject: RE: [tomcat-users] Issue found during migration of Tomcat version 
6.0.35 to 8.5.5

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 
<lavitesh.ve...@amdocs.com<mailto:lavitesh.ve...@amdocs.com>>
Sent: Monday, June 15, 2020 9:29 AM
To: Jason Pyeron <jpye...@pdinc.us<mailto:jpye...@pdinc.us>>; 'Tomcat Users 
List' <users@tomcat.apache.org<mailto:users@tomcat.apache.org>>
Cc: 'RUBIN, JACOB' <jr2...@att.com<mailto:jr2...@att.com>>; 
lsrv...@list.att.com<mailto:lsrv...@list.att.com>; Vasudev Wadhawan 
<vasudev.wadha...@amdocs.com<mailto:vasudev.wadha...@amdocs.com>>
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
[download12]+91.9810157771
OOO - 06/16 - 06/19
[cid:image001.jpg@01D2912B.17505E90]

From: Jason Pyeron <jpye...@pdinc.us<mailto:jpye...@pdinc.us>>
Sent: Monday, June 15, 2020 6:15 PM
To: 'Tomcat Users List' 
<users@tomcat.apache.org<mailto:users@tomcat.apache.org>>
Cc: 'RUBIN, JACOB' <jr2...@att.com<mailto:jr2...@att.com>>; 
lsrv...@list.att.com<mailto:lsrv...@list.att.com>; Vasudev Wadhawan 
<vasudev.wadha...@amdocs.com<mailto:vasudev.wadha...@amdocs.com>>
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:lavitesh.ve...@amdocs.com]
Sent: Monday, June 15, 2020 8:16 AM
To: users@tomcat.apache.org<mailto:users@tomcat.apache.org>
Cc: RUBIN, JACOB <jr2...@att.com<mailto:jr2...@att.com>>; 
lsrv...@list.att.com<mailto:lsrv...@list.att.com>; Vasudev Wadhawan 
<vasudev.wadha...@amdocs.com<mailto:vasudev.wadha...@amdocs.com>>
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.

[cid:image004.jpg@01D6433C.E23C4DF0]

Could you please assist on how we could resolve the issue.

Thanks & Regards
Lavitesh Verma
Software Engineering Associate
Amdocs Global SmartOps
[download12]+91.9810157771
OOO - 06/16 - 06/19
[cid:image001.jpg@01D2912B.17505E90]

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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__www.amdocs.com_about_email-2Dterms-2Dof-2Dservice%26d%3DDwMFaQ%26c%3DLFYZ-o9_HUMeMTSQicvjIg%26r%3Dq4z4Z_LzvA-puKNZt92-wVsDWO_kmKRO8UvFw6kIv8E%26m%3Dya8xEu8AbtIK6o7mc8CpVi11Dn71LH_Ui1J-uJxXzNg%26s%3DEjDUw37y3DHXzYwFqeqanPK4qeTYOyqb8sJ7gq8J174%26e%3D&data=02%7C01%7CLavitesh.Verma%40amdocs.com%7C4093a9c9936d4d091a4608d8113721b2%7Cc8eca3ca127646d59d9da0f2a028920f%7C0%7C0%7C637278275776422500&sdata=h5CqXnDipyCgqclpTggTxMq5ciug0nWdI1XaDZLt4e0%3D&reserved=0>
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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.amdocs.com%2Fabout%2Femail-terms-of-service&data=02%7C01%7CLavitesh.Verma%40amdocs.com%7C4093a9c9936d4d091a4608d8113721b2%7Cc8eca3ca127646d59d9da0f2a028920f%7C0%7C0%7C637278275776432494&sdata=OFRFiGSpD0WnDEqukXplygxGpkoyB%2Bcq1J2aV9ZCQBk%3D&reserved=0>
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>

Reply via email to