-
1. Re: RESTEasy HttpProtocol Exception JBOSS AS 7.
nickarls Nov 26, 2012 1:56 AM (in response to johnwasmat)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?
-
2. Re: RESTEasy HttpProtocol Exception JBOSS AS 7.
johnwasmat Nov 26, 2012 12:30 PM (in response to nickarls)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.
-
3. Re: RESTEasy HttpProtocol Exception JBOSS AS 7.
nickarls Nov 26, 2012 2:47 PM (in response to johnwasmat)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.
-
4. Re: RESTEasy HttpProtocol Exception JBOSS AS 7.
johnwasmat Nov 27, 2012 10:03 AM (in response to nickarls)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
-
5. Re: RESTEasy HttpProtocol Exception JBOSS AS 7.
nickarls Nov 28, 2012 1:57 AM (in response to johnwasmat)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
-
6. Re: RESTEasy HttpProtocol Exception JBOSS AS 7.
johnwasmat Nov 30, 2012 11:52 AM (in response to nickarls)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?
-
7. Re: RESTEasy HttpProtocol Exception JBOSS AS 7.
nickarls Dec 1, 2012 3:15 AM (in response to johnwasmat)check the interface definitions in the end of standalone.xml
-
8. Re: RESTEasy HttpProtocol Exception JBOSS AS 7.
nickarls Dec 2, 2012 4:54 PM (in response to nickarls)Although if you get a 404 it shows that there is a http listener on that port...
-
9. Re: RESTEasy HttpProtocol Exception JBOSS AS 7.
johnwasmat Dec 5, 2012 10:26 AM (in response to nickarls)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 ?
-
10. Re: RESTEasy HttpProtocol Exception JBOSS AS 7.
nickarls Dec 5, 2012 11:38 AM (in response to johnwasmat)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)
-
11. Re: RESTEasy HttpProtocol Exception JBOSS AS 7.
johnwasmat Dec 5, 2012 5:14 PM (in response to nickarls)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?
-
12. Re: RESTEasy HttpProtocol Exception JBOSS AS 7.
nickarls Dec 6, 2012 1:29 AM (in response to johnwasmat)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?
-
13. Re: RESTEasy HttpProtocol Exception JBOSS AS 7.
johnwasmat Dec 6, 2012 11:48 AM (in response to nickarls) -
14. Re: RESTEasy HttpProtocol Exception JBOSS AS 7.
johnwasmat Dec 7, 2012 10:17 AM (in response to johnwasmat)Any suggestions guys?