Message Channel Handler error [oData through SUP]

[Former Member]

when we are trying to access the oData service URL through SUP we are getting the following error any idea what could be wrong

ERROR MMS MessageChannel Thread-252 [com.sybase.sup.server.msgchannel.internal.InboundMoHttpTransport]MessageChannel error [MessageChannel handler failed. , returning ERROR_CODE [500], ERROR_TEXT [MessageChannel handler failed. ], HTTP status [500]
        ... 33 more
        at com.sybase.sup.server.msgchannel.internal.MessageChannelInternal.dispatch(MessageChannelInternal.java:100)
        at com.sybase.sup.server.msgchannel.internal.Response.setContent(Response.java:23)
        at com.sybase.sup.server.msgchannel.internal.Response.writeStreamFromBytes(Response.java:41)
        at java.io.ByteArrayInputStream.<init>(ByteArrayInputStream.java:89)
Caused by: java.lang.NullPointerException
        at java.lang.Thread.run(Thread.java:662)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547)
        at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)
        at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
        at com.sybase.djc.server.jetty.JettyServer.handle(JettyServer.java:168)
        at org.mortbay.jetty.Server.handle(Server.java:322)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
        at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:242)
        at com.sybase.djc.server.jetty.SybWebAppContext.handle(SybWebAppContext.java:157)
        at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
        at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
        at com.sybase.djc.server.jetty.SybSessionHandler.handle(SybSessionHandler.java:147)
        at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
        at org.mortbay.jetty.security.HTAccessHandler.handle(HTAccessHandler.java:234)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
        at web.components.msgchannel.msgchannel$WC.service(msgchannel$WC.java:24)
        at web.components.msgchannel.msgchannel_DJC.service(msgchannel_DJC.java:339)
        at com.sybase.djc.transaction.TransactionManager.invokeBeanManaged(TransactionManager.java:611)
        at com.sybase.djc.transaction.TransactionManager.invokeNotSupported1(TransactionManager.java:670)
        at web.components.msgchannel.msgchannel_DJC$3.invoke(msgchannel_DJC.java:310)
        at web.components.msgchannel.msgchannel_DJC.access$201(msgchannel_DJC.java:4)
        at web.components.msgchannel.msgchannel.service(msgchannel.java:28)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:767)
        at com.sybase.sup.server.msgchannel.internal.InboundMoHttpTransport.doPost(InboundMoHttpTransport.java:50)
        at com.sybase.sup.server.msgchannel.internal.InboundMoHttpTransport.process(InboundMoHttpTransport.java:113)
        at com.sybase.sup.server.msgchannel.internal.MessageChannelInternal.dispatch(MessageChannelInternal.java:120)
com.sybase.sup.server.msgchannel.internal.MessageChannelException: MessageChannel handler failed.

[Former Member · Accepted solution]

Hi!

We upgraded (patched) the SUP to 2.1.2 (2.1 ESD #2, available via sybase.com / Support / EBFs/Maintenance / Sybase Unwired Platform).

The error has gone. Furthermore we received some other errors, that were caused by a missing "DOMAIN" (now we are using at least "default") in the SUP-application-connection.

regards,
Martin

[Former Member · Accepted solution]

Typically, in SCC, while creating the SUP user ensure that you have set the "default" in Domain, that solved the problem for me in SUP 2.1.0 it self. with NWGW SP 2 installed

I hope this might solve the problem for you also.

Regards,

Srinivas Divakarla

[s0007226202]

Hi ,

We are having the same problem while trying to configure SAP Employee Lookup through SUP 2.1 and SAP NW GW 2.0 SP3.

We can call the OData service on NW Gateway system from the SUP server, but when the service is called by the mobile app we apparently get a HTTP 500 error (internal server error).

See the trace listing below.

2012-03-02 17:36:31.958 ERROR MMS MessageChannel Thread-425 [com.sybase.sup.server.msgchannel.internal.InboundMoHttpTransport]MessageChannel error [MessageChannel handler failed. , returning ERROR_CODE [500], ERROR_TEXT [MessageChannel handler failed. ], HTTP status [500]

... 33 more

at com.sybase.sup.server.msgchannel.internal.MessageChannelInternal.dispatch(MessageChannelInternal.java:100)

at com.sybase.sup.server.msgchannel.internal.Response.setContent(Response.java:23)

at com.sybase.sup.server.msgchannel.internal.Response.writeStreamFromBytes(Response.java:41)

at java.io.ByteArrayInputStream.<init>(ByteArrayInputStream.java:89)

Caused by: java.lang.NullPointerException

at java.lang.Thread.run(Thread.java:662)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)

at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)

at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)

at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547)

at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)

at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)

at com.sybase.djc.server.jetty.JettyServer.handle(JettyServer.java:168)

at org.mortbay.jetty.Server.handle(Server.java:322)

at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)

at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:242)

at com.sybase.djc.server.jetty.SybWebAppContext.handle(SybWebAppContext.java:157)

at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)

at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)

at com.sybase.djc.server.jetty.SybSessionHandler.handle(SybSessionHandler.java:147)

at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)

at org.mortbay.jetty.security.HTAccessHandler.handle(HTAccessHandler.java:234)

at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)

at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)

at web.components.msgchannel.msgchannel$WC.service(msgchannel$WC.java:24)

at web.components.msgchannel.msgchannel_DJC.service(msgchannel_DJC.java:339)

at com.sybase.djc.transaction.TransactionManager.invokeBeanManaged(TransactionManager.java:611)

at com.sybase.djc.transaction.TransactionManager.invokeNotSupported1(TransactionManager.java:670)

at web.components.msgchannel.msgchannel_DJC$3.invoke(msgchannel_DJC.java:310)

at web.components.msgchannel.msgchannel_DJC.access$201(msgchannel_DJC.java:4)

at web.components.msgchannel.msgchannel.service(msgchannel.java:28)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:767)

at com.sybase.sup.server.msgchannel.internal.InboundMoHttpTransport.doPost(InboundMoHttpTransport.java:50)

at com.sybase.sup.server.msgchannel.internal.InboundMoHttpTransport.process(InboundMoHttpTransport.java:113)

at com.sybase.sup.server.msgchannel.internal.MessageChannelInternal.dispatch(MessageChannelInternal.java:120)

com.sybase.sup.server.msgchannel.internal.MessageChannelException: MessageChannel handler failed.

2012-03-02 17:36:31.957 DEBUG MMS MessageChannel Thread-425 [com.sybase.sup.server.msgchannel.internal.MessageChannelInternal]Done executing request (requestId=[43577039].

2012-03-02 17:36:31.954 DEBUG MMS MessageChannel Thread-425 [com.sybase.sup.server.msgchannel.internal.MessageChannelInternal]About to execute request (requestId=[43577039], handlerId=[GWCRequest]) in Handler [com.sybase.suplite.gwc.req.handler.GatewayConnectorHandler]...

[Former Member]

Hi there,

having exactly the same problem here!

Tried NW GW 2.0 SP2 and SP3. No difference.

regards,

Martin