Exception thrown after json schema validation failed

54 views
Skip to first unread message

victo...@gmail.com

unread,
Feb 13, 2015, 4:13:57 PM2/13/15
to membrane...@googlegroups.com
Hi,

We have been testing json schema validation and found membrane throws the following exception if JSON schema failed to validate. It seems the JsonFactory used in membrane doesn't support the createJsonGenerator methods any more. Is this a bug and how do we fix it? Thanks in advance...

Uncaught service() exception thrown by servlet membrane: java.lang.NoSuchMethodError: org/codehaus/jackson/JsonFactory.createJsonGenerator(Ljava/io/OutputStream;)Lorg/codehaus/jackson/JsonGenerator;
at com.predic8.membrane.core.interceptor.schemavalidation.JSONValidator.validateMessage(JSONValidator.java:101)
at com.predic8.membrane.core.interceptor.schemavalidation.JSONValidator.validateMessage(JSONValidator.java:63)
at com.predic8.membrane.core.interceptor.schemavalidation.ValidatorInterceptor.handleRequest(ValidatorInterceptor.java:108)
at com.predic8.membrane.core.interceptor.flow.RequestInterceptor.handleRequest(RequestInterceptor.java:48)
at com.predic8.membrane.core.interceptor.InterceptorFlowController.invokeRequestHandlers(InterceptorFlowController.java:106)
at com.predic8.membrane.core.interceptor.UserFeatureInterceptor.handleRequest(UserFeatureInterceptor.java:43)
at com.predic8.membrane.core.interceptor.InterceptorFlowController.invokeRequestHandlers(InterceptorFlowController.java:106)
at com.predic8.membrane.core.interceptor.InterceptorFlowController.invokeHandlers(InterceptorFlowController.java:71)
at com.predic8.membrane.core.transport.http.AbstractHttpHandler.invokeHandlers(AbstractHttpHandler.java:68)
at com.predic8.membrane.servlet.embedded.HttpServletHandler.run(HttpServletHandler.java:75)
at com.predic8.membrane.servlet.embedded.MembraneServlet.service(MembraneServlet.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1214)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:774)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:456)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1027)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:87)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:895)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:195)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:522)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:311)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:87)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1783)

Tobias Polley

unread,
Feb 14, 2015, 4:10:02 PM2/14/15
to membrane...@googlegroups.com
Hi Victor.

Which version of Membrane Service Proxy are you using?

Thanks, Tobias

Thomas Bayer

unread,
Feb 25, 2015, 3:39:56 AM2/25/15
to membrane...@googlegroups.com
Hi,
thanks for reporting. We will have a look. What version of Membrane did you use?

Cheers,
Thomas

Am 13.02.15 um 22:13 schrieb victo...@gmail.com:
--
You received this message because you are subscribed to the Google Groups "membrane-monitor" group.
To unsubscribe from this group and stop receiving emails from it, send an email to membrane-monit...@googlegroups.com.
To post to this group, send email to membrane...@googlegroups.com.
Visit this group at http://groups.google.com/group/membrane-monitor.
For more options, visit https://groups.google.com/d/optout.

victo...@gmail.com

unread,
Mar 11, 2015, 9:30:22 AM3/11/15
to membrane...@googlegroups.com
I'm using the latest 4.0.18.

thanks again...

Thomas Bayer

unread,
Mar 11, 2015, 11:34:08 AM3/11/15
to membrane...@googlegroups.com
Hi Victor,
are you using IBM WebSphere as a Container for Membrane? Maybe the application server is putting an own version of the JSON lib into the classpath. You can try your config with a standalone Membrane installation to verify that. Maybe you can setup your application server to use the right lig.

Cheers,
Thomas

Am 11.03.15 um 14:30 schrieb victo...@gmail.com:

Victor Weng

unread,
Mar 11, 2015, 3:21:10 PM3/11/15
to membrane...@googlegroups.com
You are right! Thanks for the tip!! 
You received this message because you are subscribed to a topic in the Google Groups "membrane-monitor" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/membrane-monitor/L5oDZZH96C4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to membrane-monit...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages