Date of First Response: 2008-10-16 04:38:35 project_key: SOA According to JBESB-799 "JBR/HTTP Gateway does not appear to provide actions with the query string from a GET". This lead to the following exception: 08:35:17,199 INFO [MessagePayloadProxy] Null data found in message location(s): [org.jboss.soa.esb.message.defaultEntry] 08:35:17,213 ERROR [JBossRemotingGatewayListener] JBoss Remoting Gateway failed to synchronously deliver message to target service [SecurityCredentials:HttpsMethodService1]. org.jboss.soa.esb.listeners.message.MessageDeliverException: Null data found in message location(s): [org.jboss.soa.esb.message.defaultEntry] at org.jboss.soa.esb.message.MessagePayloadProxy.getPayload(MessagePayloadProxy.java:161) at org.jboss.soa.esb.listeners.message.AbstractMessageComposer.decompose(AbstractMessageComposer.java:100) at org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListener$JBossRemotingMessageComposer.decompose(JBossRemotingGatewayListener.java:574) at org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListener$JBossRemotingMessageComposer.decompose(JBossRemotingGatewayListener.java:487) at org.jboss.soa.esb.listeners.message.UncomposedMessageDeliveryAdapter.deliverSync(UncomposedMessageDeliveryAdapter.java:89) at org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListener.invoke(JBossRemotingGatewayListener.java:345) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:866) at org.jboss.remoting.transport.coyote.CoyoteInvoker.service(CoyoteInvoker.java:310) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) And the client recieves: Response code from server: 500 Response message from server: JBoss Remoting: Error occurred within target application.
Link: Added: This issue depends JBESB-799
Link: Removed: This issue depends JBESB-799
JBESB-1958 is a better report of the issue.
Link: Added: This issue depends JBESB-1958
It does not support other HTTP verbs as well, such as OPTIONS.
According to PRD following verbs should be supported: (4.3) HTTP/S support includes support for HTTP verbs such as GET, PUT, POST and DELETE. When we asked Burr for more precise definition we got this reply: And GET, PUT, POST & DELETE should also be supported (GET is presently broken) but that isn't exclusive. If HEAD also works then great.
Yes, but not for this release now unfortunately. See Fix field.
The ERROR is thrown even if POST is used without any data in the request body.
So - for the 4.3 release, which HTTP verbs are supported, with which parameters? We'll want to have/build tests to cover what we're supporting.
Link: Added: This issue is related to JBESB-799
Link: Added: This issue related SOA-989
The new feature in SOA-989 should eliminate the need to correct the JBR-based HTTP support
Yes, we won't fix the JBR HTTP support to address this issue.