RESTEasy HttpProtocol Exception JBOSS AS 7.

[johnwasmat]

Hello,

I`m trying to develop a Java ReastEasy client to send messages to a hornetq queue. I followed the steps listed in the jboss documentation but I couldnt find any help to this issue Following is my client code

HttpClient client = new DefaultHttpClient();

       HttpPost post = new HttpPost("http://127.0.0.1:4447/queue/jms.queue.test");

       JSONObject json = new JSONObject();

       json.append("test", "test");

       StringEntity input = new StringEntity(json.toString());

       input.setContentEncoding("UTF-8");

       input.setContentType("application/json");

       post.setEntity(input);

       post.addHeader("accept", "application/json");

       HttpResponse response = client.execute(post);

I`m receving the following errors.

a) On the cleint side

Exception in thread "main" org.apache.http.ProtocolException: The server failed to respond with a valid HTTP response

b) On the server side

22:51:05,530 ERROR [org.jboss.remoting.remote.connection]  JBREM000200: Remote connection failed: java.io.IOException: Receiv

ed an invalid message length of 1347375956

I have a web.xml file that I have created based on the rest documentation and placed it in the deployments folder of the JBOSS AS 7 directory. I also have the hornetq-rest.xml file in the same folder. Both get deployed correctly. I`m not sure if this is a code issue or I`m missing any configuration on the server side. Any help would be appreciated.

Thanks.

[nickarls]

Some questions ;-)

What documentation are you following? What are you trying to do? What does it have to do with RestEasy?

I thought 4447 was the remoting port, can you really post json to it like that?

[johnwasmat]

Hey Nicklas,

I followed the hornetq Rest configuration for Jboss AS 7. I have a blog that explained how hornetq was now a part of JBoss AS 7. Here are the  links

http://hornetq.blogspot.com/2011/06/hornetq-on-jboss-as7.html

http://hornetq.blogspot.com/2009/10/understanding-connectors-acceptors.html

I also read the documentation on the JBoss website and understood that all I had to do was copy the web.xml listed in the documentation and hornetq-rest.xml in deployments folder.

The Jboss documentation that I referred was

http://docs.jboss.org/resteasy/docs/3.0-beta-1/userguide/html/index.html

Also I`m trying to populate a message to teh hornetq queue listed in the standalone.xml file. RestEasy is a jar that contains the Rest API needed to populate messages to hornetq queue. I looked at the server output and that was the port all messages were redirected to. If there is any other port I should be looking at please let me know. I dont think JSON Object is a problem here because you can specify the content-type as application-xml and have an xml string passed to the server.

I hope I answered all your questions. Thank you for helping me out here.

[nickarls]

Oh, never knew there was a hornetq-rest bridge.

Anyways, from the http://docs.jboss.org/resteasy/hornetq-rest/1.0-beta-3/userguide/html_single/#d0e49 example I get the picture that we're talking about a WAR with a web.xml which would indicate the REST calls would also have to target the http port (8080 by default) and the URL should hit the web context of the web application.

It appears to be bundled with HQ nowadays so you might want to try the rest examples included there.

[johnwasmat]

I tried with the 8080 port and I`m getting the "HTTP 404 Resource /queue/jmsFirstFour not found" error code in the response. Am I missing anything in the jboss configuration in hornetq-rest.xml or web.xml or standlone-full.xml? I have the queues mentioned in the standalone-full.xml <subsystem><hornetw-server> section.

Thanks

[nickarls]

Have you read the entire http://docs.jboss.org/hornetq/2.3.0.beta2/docs/user-manual/html_single/index.html#d0e11684 ?

I get the picture the URL should be /queues/jms.queue.jmsFirstFour

[johnwasmat]

I read the docs again. I think the problem might be that I`m trying to send request to http://127.0.0.1:8080/..... and the server is not listening on that port or not accepting http request on that port. Where do I verify all of this?

[nickarls]

check the interface definitions in the end of standalone.xml

[nickarls]

Although if you get a 404 it shows that there is a http listener on that port...

[johnwasmat]

Following are my interface definitions

    <interfaces>

        <interface name="management">

            <inet-address value="${jboss.bind.address.management:127.0.0.1}"/>

        </interface>

        <interface name="public">

            <inet-address value="${jboss.bind.address:127.0.0.1}"/>

        </interface>

        <interface name="unsecure">

            <inet-address value="${jboss.bind.address.unsecure:127.0.0.1}"/>

        </interface>

    </interfaces>

What I dont understand is what is the value of jboss.bind.address.unsecure or jboss.bind.address or jboss.bind.address.management ?

[nickarls]

Check the socket-binding-group

the jboss.bind.* is just stuff that are used if they are passed in with -D parameters (otherwise it pulls it from default)

[johnwasmat]

Following is my socket-binding-group

    <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">

        <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/>

        <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>

        <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9443}"/>

        <socket-binding name="ajp" port="8009"/>

        <socket-binding name="http" port="8080"/>

        <socket-binding name="https" port="8443"/>

        <socket-binding name="jacorb" interface="unsecure" port="3528"/>

        <socket-binding name="jacorb-ssl" interface="unsecure" port="3529"/>

        <socket-binding name="messaging" port="5445"/>

        <socket-binding name="messaging-throughput" port="5455"/>

        <socket-binding name="osgi-http" interface="management" port="8090"/>

        <socket-binding name="remoting" port="4447"/>

        <socket-binding name="txn-recovery-environment" port="4712"/>

        <socket-binding name="txn-status-manager" port="4713"/>

        <outbound-socket-binding name="mail-smtp">

            <remote-destination host="localhost" port="25"/>

        </outbound-socket-binding>

    </socket-binding-group>

Are there any modifications that need to be done in here?

[nickarls]

no, 8080 is fine. And as I said, I think that error messge you see is from REST. Did you try the

/queues/jms.queue.jmsFirstFour

format?

[johnwasmat]

Yes I tried the following link

http://127.0.0.1:8080/queues/jms.queue.jmsFirstFour

No luck.

[johnwasmat]

Any suggestions guys?