Re: Tomcat 8.0.15 - error using Web Services

[jgebhardt]

Hi Marina,

did you manage to solve your problem?
I'm running into the same issue that relative URLs are note resolved while
loading the XSD Definitions in Tomcat 8.0.30.

Below you'll find my stacktrace.

Thanks in advance
Joern



java.lang.IllegalArgumentException: The resource path
[/./../../metadaten/fachlich/fachliche-metadaten.xsd] has been normalized to
[null] which is not valid
at
org.apache.catalina.webresources.StandardRoot.validate(StandardRoot.java:265)
~[tomcat-embed-core-8.0.30.jar:8.0.30]
at
org.apache.catalina.webresources.StandardRoot.getResource(StandardRoot.java:212)
~[tomcat-embed-core-8.0.30.jar:8.0.30]
at
org.apache.catalina.webresources.StandardRoot.getResource(StandardRoot.java:206)
~[tomcat-embed-core-8.0.30.jar:8.0.30]
at
org.apache.catalina.core.ApplicationContext.getResource(ApplicationContext.java:554)
~[tomcat-embed-core-8.0.30.jar:8.0.30]
at
org.apache.catalina.core.ApplicationContextFacade.getResource(ApplicationContextFacade.java:199)
~[tomcat-embed-core-8.0.30.jar:8.0.30]
at
org.apache.cxf.transport.servlet.ServletContextResourceResolver.resolve(ServletContextResourceResolver.java:82)
~[cxf-rt-transports-http-3.1.4.jar:3.1.4]
at
org.apache.cxf.resource.DefaultResourceManager.findResource(DefaultResourceManager.java:113)
~[cxf-core-3.1.4.jar:3.1.4]
at
org.apache.cxf.resource.DefaultResourceManager.resolveResource(DefaultResourceManager.java:58)
~[cxf-core-3.1.4.jar:3.1.4]
at
org.apache.cxf.ws.addressing.EndpointReferenceUtils$SchemaLSResourceResolver.resolveResource(EndpointReferenceUtils.java:150)
~[cxf-core-3.1.4.jar:3.1.4]
at
com.sun.org.apache.xerces.internal.util.DOMEntityResolverWrapper.resolveEntity(DOMEntityResolverWrapper.java:117)
~[na:1.8.0_66]
at
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.resolveEntity(XMLEntityManager.java:1082)
~[na:1.8.0_66]
at
com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.resolveDocument(XMLSchemaLoader.java:657)
~[na:1.8.0_66]
at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.resolveSchema(XSDHandler.java:2048)
~[na:1.8.0_66]
at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.constructTrees(XSDHandler.java:1004)
~[na:1.8.0_66]
at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.constructTrees(XSDHandler.java:1116)
~[na:1.8.0_66]
at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.constructTrees(XSDHandler.java:1116)
~[na:1.8.0_66]
at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.constructTrees(XSDHandler.java:1116)
~[na:1.8.0_66]
at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.parseSchema(XSDHandler.java:616)
~[na:1.8.0_66]
at
com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadSchema(XMLSchemaLoader.java:613)
~[na:1.8.0_66]
at
com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:572)
~[na:1.8.0_66]
at
com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:538)
~[na:1.8.0_66]
at
com.sun.org.apache.xerces.internal.jaxp.validation.XMLSchemaFactory.newSchema(XMLSchemaFactory.java:255)
~[na:1.8.0_66]
at
org.apache.cxf.ws.addressing.EndpointReferenceUtils.createSchema(EndpointReferenceUtils.java:626)
[cxf-core-3.1.4.jar:3.1.4]
at
org.apache.cxf.ws.addressing.EndpointReferenceUtils.getSchema(EndpointReferenceUtils.java:672)
[cxf-core-3.1.4.jar:3.1.4]
at
org.apache.cxf.interceptor.AbstractInDatabindingInterceptor.setDataReaderValidation(AbstractInDatabindingInterceptor.java:116)
[cxf-core-3.1.4.jar:3.1.4]
at
org.apache.cxf.wsdl.interceptors.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:162)
[cxf-rt-wsdl-3.1.4.jar:3.1.4]
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
[cxf-core-3.1.4.jar:3.1.4]
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
[cxf-core-3.1.4.jar:3.1.4]
at
org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:251)
[cxf-rt-transports-http-3.1.4.jar:3.1.4]
at
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234)
[cxf-rt-transports-http-3.1.4.jar:3.1.4]
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208)
[cxf-rt-transports-http-3.1.4.jar:3.1.4]
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160)
[cxf-rt-transports-http-3.1.4.jar:3.1.4]
at
org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:180)
[cxf-rt-transports-http-3.1.4.jar:3.1.4]
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:293)

Re: Tomcat 8.0.15

[Mark Thomas]

On 29/01/2016 18:18, juliesur wrote:
> My webapp does show poor performance and stops responding after a while ,
> with these errors in the log.
> I have been unable to replicate the issue in my testing environment during
> load testing. 
> The error appears only in production .
> 
> I haven't tried another connector or diff tomcat version. I want to confirm
> this as a bug before suggesting the team to upgrade or make changes.

The evidence points to an application bug. You are getting an NPE from
the Context. That suggests the Request has been recycled and something
in the application is retaining a reference to the Request and trying to
use it.

Mark


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Tomcat 8.0.15

[juliesur]

My webapp does show poor performance and stops responding after a while ,
with these errors in the log.
I have been unable to replicate the issue in my testing environment during
load testing. 
The error appears only in production .

I haven't tried another connector or diff tomcat version. I want to confirm
this as a bug before suggesting the team to upgrade or make changes.




--
View this message in context: 
http://tomcat.10.x6.nabble.com/Re-Tomcat-8-0-15-tp5044779p5045814.html
Sent from the Tomcat - User mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Tomcat 8.0.15

[Caldarale, Charles R]

> From: Julie Sur [mailto:julie...@gmail.com] 
> Subject: Re: Tomcat 8.0.15

> I am using tomcat 8.0.15, jdk1.8.0_45 with my application and I am seeing
> below errors in my log. Is this a bug with the tomcat version that I am
> using ?

Could be, but it's more likely an application bug.  Try running with the 
current level (8.0.30).

> TomcatLog Error processing request java.lang.NullPointerException
>  at
> org.apache.catalina.connector.Request.notifyAttributeAssigned(Request.java:1492)

Is your webapp hanging onto a request or response object after the request has 
completed?  Typical errors include storing the reference in a ThreadLocal, 
servlet instance field, or static field.

> TomcatLog Error finishing response java.lang.NullPointerException
>  at
> org.apache.coyote.http11.InternalNioOutputBuffer.flushBuffer(InternalNioOutputBuffer.java:234)

Have you tried one of the other  types?

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 8.0.15

[Julie Sur]

Resending the email as I got failure notification earlier

Thanks
Julie

On Thu, Jan 7, 2016 at 12:44 PM, Julie Sur  wrote:

> Hi,
> I am using tomcat 8.0.15, jdk1.8.0_45 with my application and I am seeing
> below errors in my log. Is this a bug with the tomcat version that I am
> using ?
>
> TomcatLog Error processing request java.lang.NullPointerException
>  at
> org.apache.catalina.connector.Request.notifyAttributeAssigned(Request.java:1492)
>
>  at
> org.apache.catalina.connector.Request.setAttribute(Request.java:1482)
>  at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154)
>
>  at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
>
>  at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
>
>  at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:537)
>  at
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1085)
>
>  at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:658)
>
>  at
> org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:222)
>
>  at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1556)
>
>  at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1513)
>
>  at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>
>  at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>
>  at
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>
>  at java.lang.Thread.run(Thread.java:745)
>
> and
> TomcatLog Error finishing response java.lang.NullPointerException
>  at
> org.apache.coyote.http11.InternalNioOutputBuffer.flushBuffer(InternalNioOutputBuffer.java:234)
>
>  at
> org.apache.coyote.http11.InternalNioOutputBuffer.addToBB(InternalNioOutputBuffer.java:189)
>
>  at
> org.apache.coyote.http11.InternalNioOutputBuffer.commit(InternalNioOutputBuffer.java:177)
>
>  at
> org.apache.coyote.http11.AbstractHttp11Processor.action(AbstractHttp11Processor.java:739)
>
>  at org.apache.coyote.Response.action(Response.java:179)
>  at
> org.apache.coyote.http11.AbstractOutputBuffer.endRequest(AbstractOutputBuffer.java:369)
>
>  at
> org.apache.coyote.http11.AbstractHttp11Processor.endRequest(AbstractHttp11Processor.java:1773)
>
>  at
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1142)
>
>  at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:658)
>
>  at
> org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:222)
>
>  at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1556)
>
>  at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1513)
>
>  at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>
>  at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>
>  at
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>
>  at java.lang.Thread.run(Thread.java:745)
>
> Thank you for looking into this
> Julie Sur
>

Re: Tomcat 8.0.15 - error using Web Services

[Marina F]

And the XML file that contains that reference is located where in the
web application?

This is the package structure that shows the location of the
Types.xsd. Types.xsd
is included in Account.xsd.

---com
test
-example
--api
---common
schemas
  Types.xsd
---account
schemas
  Account.xsd (xsd:include
schemaLocation=../../common/schemas/Types.xsd /)
---consumer
schemas
  Consumer.xsd (xsd:include
schemaLocation=../../common/schemas/Types.xsd
/)

Please let me know if this doesn't answer the question or there is other
question/response in this thread that I am missing.

Thank you,

Marina

On Wed, Dec 10, 2014 at 8:42 AM, Mark Thomas ma...@apache.org wrote:

 On 10/12/2014 14:21, Marina F wrote:
  Hello,
 
  Tomcat 8.0.15
 
  I am getting an error when using web services. (no errors if using Tomcat
  7.0.50)
 
  Schema:
  xsd:include schemaLocation=../../common/schemas/Types.xsd /
 
  Error:
  Dec 10, 2014 7:59:48 AM org.apache.catalina.core.StandardWrapperValve
 invoke
  SEVERE: Allocate exception for servlet api-ws-soap
  java.lang.IllegalArgumentException: The resource path
  [/../../common/schemas/Types.xsd] has been normalized to [null] which is
  not valid

 And the XML file that contains that reference is located where in the
 web application?

 Mark


 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 8.0.15 - error using Web Services

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256



On 2/2/15 6:10 PM, Marina F wrote:
 Hi Mark,
 
 I installed Tomcat 8.0.18 and I am still seeing the same error.
 
 I am wondering if you have any suggestions?

Mark had a suggestion back on 10 January when you posted this question
initially. Care to read his response?

- -chris

 On Wed, Dec 10, 2014 at 9:10 AM, Marina F m86...@gmail.com
 wrote:
 
 ---com test -example --api ---common 
 schemas Types.xsd ---account schemas 
 Account.xsd (xsd:include 
 schemaLocation=../../common/schemas/Types.xsd /) 
 ---consumer schemas Consumer.xsd (xsd:include 
 schemaLocation=../../common/schemas/Types.xsd /)
 
 On Wed, Dec 10, 2014 at 8:42 AM, Mark Thomas ma...@apache.org
 wrote:
 
 On 10/12/2014 14:21, Marina F wrote:
 Hello,
 
 Tomcat 8.0.15
 
 I am getting an error when using web services. (no errors if
 using
 Tomcat
 7.0.50)
 
 Schema: xsd:include
 schemaLocation=../../common/schemas/Types.xsd /
 
 Error: Dec 10, 2014 7:59:48 AM
 org.apache.catalina.core.StandardWrapperValve
 invoke
 SEVERE: Allocate exception for servlet api-ws-soap 
 java.lang.IllegalArgumentException: The resource path 
 [/../../common/schemas/Types.xsd] has been normalized to
 [null] which is not valid
 
 And the XML file that contains that reference is located where
 in the web application?
 
 Mark
 
 
 -

 
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org
 
 
 
 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJU0S+JAAoJEBzwKT+lPKRYNGoQAKIUuiqislkBLvKlppX+cPFK
7J64UyDf7GnKyHiWYv/hGV0tHi/UVSj6L7LgG0CSaZtLpREoc8SnzXWN7e8EQokR
YX1VDd2SibSU0vsspdZUet+PjwRQ8zsipiFj7PEDQiZUc84Dl7xsw+tq4SlZcNIv
PkwEqnMuRNtZ6nfopJyzIyGNd3kQRDvA5uB75lWUimfe7fsLPL4fpOzuVLAbk7DQ
EyAwABr5DesA4joiHyI/1R+YFGJm+7ZEXtYdxclfGL04tUmVh0XcsQhjLNcSUbhJ
sVEp3YZrJFPs1db8/VFrmMvTroNB/W/5FsH1uNYFWsCHjo+ZJHNdlsYfJXl/RHi1
xudswCuEUvF9Flpq7vglESYdjxXfBGLhP9marESHyEbzr0cXMtRhO4iCc8nR8cRl
L4ntMaS3CzJf7g7MATKcvWvJZv8TX5u4x5mYIhOez4hmaUdHNtx5b6Ga4QxIqmMm
WdYIP1Xe50NkjsLJxQMPEjp56rfaYHM20YD7SYuVWPS9/rgxM1G1Hm9XcdnB4pLG
2Easx1Mo09ykgXAkXYC40dAQl1cdOwYPQXR8kmxtQQff7cCTEAglPnyWjjuPcOlR
mo1D3Ne6dXbQOvehYi/ontBgs/pWSpAab8zxHe/v1lfveR1gbHIBb8oCVYvKpvAn
BlNdNcE/s+02930dEk6H
=qNQg
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 8.0.15 - error using Web Services

[Marina F]

Hi Mark,

I installed Tomcat 8.0.18 and I am still seeing the same error.

I am wondering if you have any suggestions?

Thanks,

Marina

On Wed, Dec 10, 2014 at 9:10 AM, Marina F m86...@gmail.com wrote:

 ---com
 test
 -example
 --api
 ---common
 schemas
   Types.xsd
 ---account
 schemas
   Account.xsd (xsd:include
 schemaLocation=../../common/schemas/Types.xsd /)
 ---consumer
 schemas
   Consumer.xsd (xsd:include
 schemaLocation=../../common/schemas/Types.xsd /)

 On Wed, Dec 10, 2014 at 8:42 AM, Mark Thomas ma...@apache.org wrote:

 On 10/12/2014 14:21, Marina F wrote:
  Hello,
 
  Tomcat 8.0.15
 
  I am getting an error when using web services. (no errors if using
 Tomcat
  7.0.50)
 
  Schema:
  xsd:include schemaLocation=../../common/schemas/Types.xsd /
 
  Error:
  Dec 10, 2014 7:59:48 AM org.apache.catalina.core.StandardWrapperValve
 invoke
  SEVERE: Allocate exception for servlet api-ws-soap
  java.lang.IllegalArgumentException: The resource path
  [/../../common/schemas/Types.xsd] has been normalized to [null] which is
  not valid

 And the XML file that contains that reference is located where in the
 web application?

 Mark


 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 8.0.15, EL Performance

[Dirk Högemann]

Hmmm. No performance loss with simple single jsp page. I will try to  track
it down some more.  The application has database functionality, many xsl
transformations, Solr search and so on. I will first reduce the
functionality and hopefully find the bottleneck.
Thanks so far.
Dirk
Am 17.01.2015 02:03 schrieb Mark Thomas ma...@apache.org:

 On 16/01/2015 16:01, Dirk Högemann wrote:
  Hello,
 
  I am trying to upgrade a JSP-based application, which is usually hosted
 on
  Tomcat (currently 7.0.57) to Version 8.0.15.
 
  Unfortunately I am facing a massive performance degradation - only 40% of
  the performance of 7.0.56 is reached when running the exact same JMeter
  Test with Tomcat8.
 
  Relevant value here is: 24 page impressions per second on Tomcat 8.0.15.
  On Tomcat 7.0.56 it reaches up to 60 PI/s.
 
  A sampler captured with JVisual VM shows a hotspot on Class:
 
  org.apache.jasper.el.JasperELResolver.getValue - 63,9 % of CPU self time
 
  Tomcat 7.0.57: 0,8 %
 
  Usage of Java8 or Java7 makes no difference.
 
  Any ideas to improve the performance?

 Not yet.

  Or is anybody facing similar issues?

 Not that I recall.

 Can you simplify this to a single JSP (ideally as simple as possible)
 that is significantly slower on 8.0.x compared to 7.0.x? With that, we
 can take a look at what is going on.

 Mark


 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 8.0.15, EL Performance

[Mark Thomas]

On 16/01/2015 16:01, Dirk Högemann wrote:
 Hello,
 
 I am trying to upgrade a JSP-based application, which is usually hosted on
 Tomcat (currently 7.0.57) to Version 8.0.15.
 
 Unfortunately I am facing a massive performance degradation - only 40% of
 the performance of 7.0.56 is reached when running the exact same JMeter
 Test with Tomcat8.
 
 Relevant value here is: 24 page impressions per second on Tomcat 8.0.15.
 On Tomcat 7.0.56 it reaches up to 60 PI/s.
 
 A sampler captured with JVisual VM shows a hotspot on Class:
 
 org.apache.jasper.el.JasperELResolver.getValue - 63,9 % of CPU self time
 
 Tomcat 7.0.57: 0,8 %
 
 Usage of Java8 or Java7 makes no difference.
 
 Any ideas to improve the performance?

Not yet.

 Or is anybody facing similar issues?

Not that I recall.

Can you simplify this to a single JSP (ideally as simple as possible)
that is significantly slower on 8.0.x compared to 7.0.x? With that, we
can take a look at what is going on.

Mark


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 8.0.15 - error using Web Services

[Mark Thomas]

On 10/12/2014 14:21, Marina F wrote:
 Hello,
 
 Tomcat 8.0.15
 
 I am getting an error when using web services. (no errors if using Tomcat
 7.0.50)
 
 Schema:
 xsd:include schemaLocation=../../common/schemas/Types.xsd /

 Error:
 Dec 10, 2014 7:59:48 AM org.apache.catalina.core.StandardWrapperValve invoke
 SEVERE: Allocate exception for servlet api-ws-soap
 java.lang.IllegalArgumentException: The resource path
 [/../../common/schemas/Types.xsd] has been normalized to [null] which is
 not valid

And the XML file that contains that reference is located where in the
web application?

Mark


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 8.0.15 - error using Web Services

[Marina F]

---com
test
-example
--api
---common
schemas
  Types.xsd
---account
schemas
  Account.xsd (xsd:include
schemaLocation=../../common/schemas/Types.xsd /)
---consumer
schemas
  Consumer.xsd (xsd:include
schemaLocation=../../common/schemas/Types.xsd /)

On Wed, Dec 10, 2014 at 8:42 AM, Mark Thomas ma...@apache.org wrote:

 On 10/12/2014 14:21, Marina F wrote:
  Hello,
 
  Tomcat 8.0.15
 
  I am getting an error when using web services. (no errors if using Tomcat
  7.0.50)
 
  Schema:
  xsd:include schemaLocation=../../common/schemas/Types.xsd /
 
  Error:
  Dec 10, 2014 7:59:48 AM org.apache.catalina.core.StandardWrapperValve
 invoke
  SEVERE: Allocate exception for servlet api-ws-soap
  java.lang.IllegalArgumentException: The resource path
  [/../../common/schemas/Types.xsd] has been normalized to [null] which is
  not valid

 And the XML file that contains that reference is located where in the
 web application?

 Mark


 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org