You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Jason Pyeron <jp...@pdinc.us> on 2020/06/15 12:44:30 UTC
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.Verma@amdocs.com]
Sent: Monday, June 15, 2020 8:16 AM
To: users@tomcat.apache.org
Cc: RUBIN, JACOB <jr...@att.com>; lsrv_ms@list.att.com; Vasudev Wadhawan <Va...@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.
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> https://www.amdocs.com/about/email-terms-of-service
Re: [OT] [tomcat-users] Issue found during migration of Tomcat
version 6.0.35 to 8.5.5
Posted by Lavitesh Verma <La...@amdocs.com>.
All,
________________________________
From: Christopher Schultz <ch...@christopherschultz.net>
Sent: Tuesday, June 16, 2020, 23:29
To: users@tomcat.apache.org
Subject: Re: [OT] [tomcat-users] Issue found during migration of Tomcat version 6.0.35 to 8.5.5
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
All,
On 6/15/20 10:02, Jason Pyeron wrote:
> A quick brief on etiquette.
>
> 1. Please do not harvest emails and send linked in requests
OMG +1 many many times to this.
If I haven't met you in person, don't send me a LinkedIn request.
For that, I have already apologised to Jason (You can certainly connect on that with him) but for instance if it had been intentional, we are all technical people here and know the value of digital networking. LinkedIn is such a platform for that. Even if i never intended it to be sent to Jason Pyeron but to Jason Pryce. It was a bit of a misunderstanding.
> 2. Do not mark questions as urgent and do provide sufficient
> details to reproduce the problem
I didn't see anything "urgent" about the initial post.
As for the marking urgent post, i had some really pressing need to complete the work as i am on leave for the whole week and wanted it to be completed as soon as possible. I did not know that marking urgent here on tomcat mailing list will create such blunders. I sincerely apologize for this as it was my first time on tom cat mailing list and it wont be repeated again. It was just me being proactive and completing my work on time and as fast as possible without considering the consequences(which i now got and again apologize for)
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl7pCFgACgkQHPApP6U8
pFhLGA/+OCBFDtwXqg25GkHzJIVCCDz0PUmo+WwshsHXmg+6njQ6oyk0xfbqUQNh
2x4IQEsqi0wvTHXRBhWtK1RQfu1emcPdLADb7Fx58AAGzyc1aNSn/LPT3+XkVRJ1
D82SQVMFeoOtOxLTSRfWlHEvjthuV7g5nobKW5yDOiv0TR+CBqarAzSewvRis5DZ
9HtAzS3jZnZVC6cCdyScRYjc4vMYWhfVHzCaAvsSoMwR/+644xeN/6rUpl6eY8L/
gxBW+w1Vn7X91gLyXML1sHQhwaupCvw3jnaV5B/CkPGTUKufKV6x3Xpycg/OmNeI
7w9m5ukzFDqtwIfbep7ngHZyiWXCngkCH50bFc7q/O/7nlbrKNx6cBS6ifh9b7dX
go1juA3dLqekY98eZxKh8nz4U7hI6Snw0KQJruLiVin3E8F8LqUegvq5QJelsQql
IoZZaj44BaPvCHIzdUxLhMKj0YJEOH5TxG7/NyyCI98RLrz0hk+JbF1+7YREIN0s
NQk2701kfmrPy2XeywvNS8psXQEsh0QtL7WpFBBnw2LZefKlqX4OcMC3hAl1o2dS
RkakYu0/J7UCvvUg0wTG3kK/NDseOBi6sMLSXatgSXIa8nfhjxygxH/fBrrAJt/D
CSlHgXDLfJIsfz8sd+/htW2ACCmd6VpdYfcFc5p0fHpkz+tIE6c=
=jJNV
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Sent from Outlook Mobile<https://aka.ms/blhgte>
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>
Re: [OT] [tomcat-users] Issue found during migration of Tomcat
version 6.0.35 to 8.5.5
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
All,
On 6/15/20 10:02, Jason Pyeron wrote:
> A quick brief on etiquette.
>
> 1. Please do not harvest emails and send linked in requests
OMG +1 many many times to this.
If I haven't met you in person, don't send me a LinkedIn request.
> 2. Do not mark questions as urgent and do provide sufficient
> details to reproduce the problem
I didn't see anything "urgent" about the initial post.
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl7pCFgACgkQHPApP6U8
pFhLGA/+OCBFDtwXqg25GkHzJIVCCDz0PUmo+WwshsHXmg+6njQ6oyk0xfbqUQNh
2x4IQEsqi0wvTHXRBhWtK1RQfu1emcPdLADb7Fx58AAGzyc1aNSn/LPT3+XkVRJ1
D82SQVMFeoOtOxLTSRfWlHEvjthuV7g5nobKW5yDOiv0TR+CBqarAzSewvRis5DZ
9HtAzS3jZnZVC6cCdyScRYjc4vMYWhfVHzCaAvsSoMwR/+644xeN/6rUpl6eY8L/
gxBW+w1Vn7X91gLyXML1sHQhwaupCvw3jnaV5B/CkPGTUKufKV6x3Xpycg/OmNeI
7w9m5ukzFDqtwIfbep7ngHZyiWXCngkCH50bFc7q/O/7nlbrKNx6cBS6ifh9b7dX
go1juA3dLqekY98eZxKh8nz4U7hI6Snw0KQJruLiVin3E8F8LqUegvq5QJelsQql
IoZZaj44BaPvCHIzdUxLhMKj0YJEOH5TxG7/NyyCI98RLrz0hk+JbF1+7YREIN0s
NQk2701kfmrPy2XeywvNS8psXQEsh0QtL7WpFBBnw2LZefKlqX4OcMC3hAl1o2dS
RkakYu0/J7UCvvUg0wTG3kK/NDseOBi6sMLSXatgSXIa8nfhjxygxH/fBrrAJt/D
CSlHgXDLfJIsfz8sd+/htW2ACCmd6VpdYfcFc5p0fHpkz+tIE6c=
=jJNV
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: [tomcat-users] Issue found during migration of Tomcat version 6.0.35 to 8.5.5
Posted by Jason Pyeron <jp...@pdinc.us>.
If you deploy your application against a fresh extract of https://archive.apache.org/dist/tomcat/tomcat-6/v6.0.35/bin/apache-tomcat-6.0.35.tar.gz, without ANY customizations you do not get the problem?
If you have to make customizations to get it to run, what are they? (e.g. context.xml changes, lib/ JARs, startup parameters, etc)
Based on the limited information you have provided (e.g. no test case I can run) I do not see any relevant issues in the following guides.
https://tomcat.apache.org/migration-7.html
http://tomcat.apache.org/migration-8.html
http://tomcat.apache.org/migration-85.html
Since the JVM (indicated) and WAR (implied) is the same version in your two installs, then it is a configuration issue.
CLASSPATH ?
System properties?
Please provide details to reproduce here.
-Jason
From: Lavitesh Verma <La...@amdocs.com>
Sent: Monday, June 15, 2020 11:14 AM
To: Tomcat Users List <us...@tomcat.apache.org>
Cc: 'RUBIN, JACOB' <jr...@att.com>; lsrv_ms@list.att.com; Vasudev Wadhawan <Va...@amdocs.com>
Subject: RE: [tomcat-users] Issue found during migration of Tomcat version 6.0.35 to 8.5.5
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
+91.9810157771
OOO – 06/16 – 06/19
From: Jason Pyeron <jpyeron@pdinc.us <ma...@pdinc.us> >
Sent: Monday, June 15, 2020 7:33 PM
To: 'Tomcat Users List' <users@tomcat.apache.org <ma...@tomcat.apache.org> >
Cc: 'RUBIN, JACOB' <jr2373@att.com <ma...@att.com> >; lsrv_ms@list.att.com <ma...@list.att.com> ; Vasudev Wadhawan <Vasudev.Wadhawan@amdocs.com <ma...@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 <La...@amdocs.com>
Sent: Monday, June 15, 2020 9:29 AM
To: Jason Pyeron <jpyeron@pdinc.us <ma...@pdinc.us> >; 'Tomcat Users List' <users@tomcat.apache.org <ma...@tomcat.apache.org> >
Cc: 'RUBIN, JACOB' <jr2373@att.com <ma...@att.com> >; lsrv_ms@list.att.com <ma...@list.att.com> ; Vasudev Wadhawan <Vasudev.Wadhawan@amdocs.com <ma...@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
+91.9810157771
OOO – 06/16 – 06/19
From: Jason Pyeron <jpyeron@pdinc.us <ma...@pdinc.us> >
Sent: Monday, June 15, 2020 6:15 PM
To: 'Tomcat Users List' <users@tomcat.apache.org <ma...@tomcat.apache.org> >
Cc: 'RUBIN, JACOB' <jr2373@att.com <ma...@att.com> >; lsrv_ms@list.att.com <ma...@list.att.com> ; Vasudev Wadhawan <Vasudev.Wadhawan@amdocs.com <ma...@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.Verma@amdocs.com]
Sent: Monday, June 15, 2020 8:16 AM
To: users@tomcat.apache.org <ma...@tomcat.apache.org>
Cc: RUBIN, JACOB <jr2373@att.com <ma...@att.com> >; lsrv_ms@list.att.com <ma...@list.att.com> ; Vasudev Wadhawan <Vasudev.Wadhawan@amdocs.com <ma...@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.
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://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> 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
RE: [tomcat-users] Issue found during migration of Tomcat version
6.0.35 to 8.5.5
Posted by Lavitesh Verma <La...@amdocs.com>.
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 <jp...@pdinc.us>
Sent: Monday, June 15, 2020 7:33 PM
To: 'Tomcat Users List' <us...@tomcat.apache.org>
Cc: 'RUBIN, JACOB' <jr...@att.com>; lsrv_ms@list.att.com; Vasudev Wadhawan <Va...@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 <La...@amdocs.com>>
Sent: Monday, June 15, 2020 9:29 AM
To: Jason Pyeron <jp...@pdinc.us>>; 'Tomcat Users List' <us...@tomcat.apache.org>>
Cc: 'RUBIN, JACOB' <jr...@att.com>>; lsrv_ms@list.att.com<ma...@list.att.com>; Vasudev Wadhawan <Va...@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 <jp...@pdinc.us>>
Sent: Monday, June 15, 2020 6:15 PM
To: 'Tomcat Users List' <us...@tomcat.apache.org>>
Cc: 'RUBIN, JACOB' <jr...@att.com>>; lsrv_ms@list.att.com<ma...@list.att.com>; Vasudev Wadhawan <Va...@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.Verma@amdocs.com]
Sent: Monday, June 15, 2020 8:16 AM
To: users@tomcat.apache.org<ma...@tomcat.apache.org>
Cc: RUBIN, JACOB <jr...@att.com>>; lsrv_ms@list.att.com<ma...@list.att.com>; Vasudev Wadhawan <Va...@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>
RE: [tomcat-users] Issue found during migration of Tomcat version 6.0.35 to 8.5.5
Posted by Jason Pyeron <jp...@pdinc.us>.
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 <La...@amdocs.com>
Sent: Monday, June 15, 2020 9:29 AM
To: Jason Pyeron <jp...@pdinc.us>; 'Tomcat Users List' <us...@tomcat.apache.org>
Cc: 'RUBIN, JACOB' <jr...@att.com>; lsrv_ms@list.att.com; Vasudev Wadhawan <Va...@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
+91.9810157771
OOO – 06/16 – 06/19
From: Jason Pyeron <jpyeron@pdinc.us <ma...@pdinc.us> >
Sent: Monday, June 15, 2020 6:15 PM
To: 'Tomcat Users List' <users@tomcat.apache.org <ma...@tomcat.apache.org> >
Cc: 'RUBIN, JACOB' <jr2373@att.com <ma...@att.com> >; lsrv_ms@list.att.com <ma...@list.att.com> ; Vasudev Wadhawan <Vasudev.Wadhawan@amdocs.com <ma...@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.Verma@amdocs.com]
Sent: Monday, June 15, 2020 8:16 AM
To: users@tomcat.apache.org <ma...@tomcat.apache.org>
Cc: RUBIN, JACOB <jr2373@att.com <ma...@att.com> >; lsrv_ms@list.att.com <ma...@list.att.com> ; Vasudev Wadhawan <Vasudev.Wadhawan@amdocs.com <ma...@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.
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
RE: [tomcat-users] Issue found during migration of Tomcat version
6.0.35 to 8.5.5
Posted by Lavitesh Verma <La...@amdocs.com>.
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 <jp...@pdinc.us>
Sent: Monday, June 15, 2020 6:15 PM
To: 'Tomcat Users List' <us...@tomcat.apache.org>
Cc: 'RUBIN, JACOB' <jr...@att.com>; lsrv_ms@list.att.com; Vasudev Wadhawan <Va...@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.Verma@amdocs.com]
Sent: Monday, June 15, 2020 8:16 AM
To: users@tomcat.apache.org<ma...@tomcat.apache.org>
Cc: RUBIN, JACOB <jr...@att.com>>; lsrv_ms@list.att.com<ma...@list.att.com>; Vasudev Wadhawan <Va...@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%7C0018b1a5efe1486313dd08d81129f16c%7Cc8eca3ca127646d59d9da0f2a028920f%7C0%7C0%7C637278219127900245&sdata=1gEPDIY%2BI%2BFfKW3gB8kiuNPkiMDG8mHSg45Cod4%2BLaI%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>