Re: Junk characters in SOAP request after upgrade to tomcat 9.0.31

2020-06-11 Thread Naveen Kumar
Hi All, Can someone please help on this ? It is in production and affecting many customers. Upgrading tomcat is a big task. Any pointers will be really appreciated. Thanks Naveen On Wed, Jun 10, 2020 at 4:24 PM Naveen Kumar wrote: > Hi Luis, > > Thanks for your suggestion. &

Re: Junk characters in SOAP request after upgrade to tomcat 9.0.31

2020-06-10 Thread Naveen Kumar
oding > > > El mié., 10 jun. 2020 a las 11:08, Naveen Kumar () > escribió: > > > Hi All, > > > > I have a webapp A which has few SOAP services and I consume those > services > > from webapp B. > > I started getting below error since I upgraded the tom

Junk characters in SOAP request after upgrade to tomcat 9.0.31

2020-06-10 Thread Naveen Kumar
Hi All, I have a webapp A which has few SOAP services and I consume those services from webapp B. I started getting below error since I upgraded the tomcat to 9.0.31 (from 9.0.24): com.sun.xml.ws.transport.http.HttpAdapter.invokeAsync Couldn't create SOAP message due to exception: XML reader

Re: Not running on Jetty, JSR-356 support unavailable

2019-11-26 Thread Naveen Kumar
ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Naveen, > > On 11/25/19 04:21, Naveen Kumar wrote: > > I am trying to upgrade ActiveMQ jar to its latest version. It > > requires me to upgrade Jetty to 9.4 version. I have curr

Not running on Jetty, JSR-356 support unavailable

2019-11-25 Thread Naveen Kumar
I am trying to upgrade ActiveMQ jar to its latest version. It requires me to upgrade Jetty to 9.4 version. I have current setup as Tomcat 9 + ActiveMQ 5.12 + jetty-all-8.1. I want to upgrade it as Tomcat 9 + ActiveMQ 5.15 + jetty-all-9.4. After doing the changes when I try to start tomcat, it