Sorry for the top post. I'm having email formatting problems.
Lavitesh,
15-Jun-2020 07:34:45.122 SEVERE [http-nio-7080-exec-10]
org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for
servlet [MainControllerServlet] in context with path [/porequest] threw
exception [Servlet execution threw an exception] with root cause
javax.xml.stream.FactoryConfigurationError: Provider
com.ctc.wstx.stax.WstxInputFactory not found
at javax.xml.stream.XMLInputFactory.newInstance(Unknown Source)
This is saying it can't find WstxInputFactory, which appears to be the Woodstox
implementation of the XMLInputFactory abstract class.
If you want to continue using Woodstox, you need to add it to your classpath
again.
If you don't want to use it, there are a few things to check to find out why
it's being used. Look for:
- System property
javax.xml.stream.XMLInputFactory=com.ctc.wstx.stax.WstxInputFactory
- $JAVA_HOME/lib/stax.properties
- $JAVA_HOME/lib/jaxp.properties
- META-INF/services/javax.xml.stream.XMLInputFactory
That last one is actually a file of the same name as the class. There is no
traditional file extension. This file might also be in a 3rd-party lib, too.
The file contains the name of the implementation to use.
One of those things is probably telling the finder to use that Woodstox class.
If you don't want to use Woodstox anymore, you have to remove or change one of
those sources. Removing it just means you'll get the default.
John
From: Lavitesh Verma <lavitesh.ve...@amdocs.com>
Sent: Monday, June 15, 2020 8:49 AM
To: Tomcat Users List <users@tomcat.apache.org>
Subject: RE: Issue found during migration of Tomcat version 6.0.35 to 8.5.5
Hi,
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]
-----Original Message-----
From: Jason Wee <peich...@gmail.com<mailto:peich...@gmail.com>>
Sent: Monday, June 15, 2020 6:49 PM
To: Tomcat Users List <users@tomcat.apache.org<mailto:users@tomcat.apache.org>>
Subject: Re: Issue found during migration of Tomcat version 6.0.35 to 8.5.5
guess looks like jar not found, full stacktrace would be helpful.
On Mon, Jun 15, 2020 at 8:17 PM Lavitesh Verma
<lavitesh.ve...@amdocs.com<mailto:lavitesh.ve...@amdocs.com>>
wrote:
> 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
>
> [image: download12]+91.9810157771
>
> *OOO - 06/16 - 06/19*
>
> [image: 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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww
> .amdocs.com%2Fabout%2Femail-terms-of-service*&data=02%7C01%7CLavit
> esh.Verma%40amdocs.com%7Cf5593255a1244392bb8a08d8113145f6%7Cc8eca3ca12
> 7646d59d9da0f2a028920f%7C0%7C0%7C637278250614631760&sdata=%2B6rV%2
> Bbnayil4ZJr7yAuCsl2YyE86CZV19JWANZPz%2BIo%3D&reserved=0
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww
> .amdocs.com%2Fabout%2Femail-terms-of-service&data=02%7C01%7CLavite
> sh.Verma%40amdocs.com%7Cf5593255a1244392bb8a08d8113145f6%7Cc8eca3ca127
> 646d59d9da0f2a028920f%7C0%7C0%7C637278250614631760&sdata=Wtzp%2BGE
> %2BjEvBwZwExHs1jlNLsN5wxGZvYhHK7SAwfxM%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
