Re: Artemis and RESTeasy jar files

2018-02-26 Thread Archibald
One issue might be an incorrect build of artemis-rest.war. The war does not contain any server libs as described in https://activemq.apache.org/artemis/docs/latest/rest.html Quote: http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;

Re: Artemis and RESTeasy jar files

2018-02-23 Thread Justin Bertram
Based on previous emails on this thread I believe he's already gotten past the url issue. Justin On Fri, Feb 23, 2018 at 3:13 AM, Archibald wrote: > What i meant, is if you publish the rest war under "artemis-rest" using > > > you should therefor call >

Re: Artemis and RESTeasy jar files

2018-02-23 Thread Archibald
What i meant, is if you publish the rest war under "artemis-rest" using you should therefor call http://10.141.65.248:8080/artemis-rest/queues instead of http://10.141.65.248:8080/activemq-rest/queues Br, A. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Artemis and RESTeasy jar files

2018-02-22 Thread Justin Bertram
I'm not sure what the problem could be. When I use your configuration it works. Did you restart the broker after you added the acceptor? Justin On Thu, Feb 22, 2018 at 2:15 PM, tcomprak wrote: > Here is my entire broker.xml file: > > [vncuser@qa-centos7x64-102 broker1]$

Re: Artemis and RESTeasy jar files

2018-02-22 Thread tcomprak
Here is my entire broker.xml file: [vncuser@qa-centos7x64-102 broker1]$ cat etc/broker.xml http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="urn:activemq /schema/artemis-configuration.xsd"> http://www.w3.org/2001/XMLSchema-instance;

Re: Artemis and RESTeasy jar files

2018-02-22 Thread Justin Bertram
Can you supply your config? I'm not sure why it would be complaining about that at this point. To be clear, I have everything working on my local box using Artemis 2.4 and your queue configuration. Justin On Thu, Feb 22, 2018 at 2:04 PM, tcomprak wrote: > This is the

Re: Artemis and RESTeasy jar files

2018-02-22 Thread tcomprak
This is the exception after adding the in-vm acceptor. Thanks for the response about defaults, thatz what i thought, but just wanted to be really sure. 12:01:30,129 WARN [org.eclipse.jetty.webapp.WebAppContext] Failed startup of context

Re: Artemis and RESTeasy jar files

2018-02-22 Thread Justin Bertram
> Still get the same exception... Are you 100% certain it's the same exception? Can you paste it? > Is it necessary to do this REST configuration as described or would the defaults automatically get picked up? The defaults are the defaults so they are always automatically picked up in the

Re: Artemis and RESTeasy jar files

2018-02-22 Thread tcomprak
Thanks. I added that as well now as follows vm://0 Still get the same exception... Is it necessary to do this REST configuration as described or would the defaults automatically get picked up? The Apache ActiveMQ Artemis REST implementation does have some configuration

Re: Artemis and RESTeasy jar files

2018-02-22 Thread Justin Bertram
That's definitely a problem. You can't really expect the REST interface to work when it can't actually connect with the broker. :) As noted in the documentation the REST interface will attempt to connect to the broker via an im-vm connection using the url "vm://0". Do you have an in-vm

Re: Artemis and RESTeasy jar files

2018-02-22 Thread tcomprak
When I start the artemis service, I see this 11:21:32,464 INFO [io.hawt.system.ProxyWhitelist] Initial proxy whitelist: [localhost, 127.0.0.1, 10.140.129.24, qa-centos7x64-102.sv.splunk.com] 11:21:33,763 WARN [org.eclipse.jetty.webapp.WebAppContext] Failed startup of context

Re: Artemis and RESTeasy jar files

2018-02-22 Thread Justin Bertram
Does the broker log have any useful information (e.g. stack-traces, error messages, etc.)? Justin On Thu, Feb 22, 2018 at 1:12 PM, tcomprak wrote: > I had missed artemis-rest earlier in the request. Now I get a service > unavailable though. > > [vncuser@qa-centos7x64-102

Re: Artemis and RESTeasy jar files

2018-02-22 Thread tcomprak
I had missed artemis-rest earlier in the request. Now I get a service unavailable though. [vncuser@qa-centos7x64-102 broker1]$ curl --get http://localhost:8161/artemis-rest/queues/myQ Error 503 Service Unavailable HTTP ERROR 503 Problem accessing /artemis-rest/queues/myQ. Reason:

Re: Artemis and RESTeasy jar files

2018-02-22 Thread Justin Bertram
Previously you were using this url: http://10.141.65.248:8080/activemq-rest/queues Now you're using this url: http://localhost:8161/queues/myQ I don't think switching to "localhost" is a problem assuming you're running curl on the same machine as the broker. You look to be using the

Re: Artemis and RESTeasy jar files

2018-02-22 Thread Justin Bertram
I see it now - "activemq" vs. "artemis". Nice catch. Sorry about the confusion. Justin On Thu, Feb 22, 2018 at 8:55 AM, Justin Bertram wrote: > > You should try > > http://10.141.65.248:8080/artemis-rest/queues > > accordingly. > > I don't see how that's any different

Re: Artemis and RESTeasy jar files

2018-02-22 Thread tcomprak
Thanks. I configured a queue in the broker.xml file and re started artemis. Added the queue element inside the core element like this myQ false and I get this [vncuser@qa-centos7x64-102 broker1]$ curl --head http://localhost:8161/queues/myQ HTTP/1.1 404 Not Found

Re: Artemis and RESTeasy jar files

2018-02-22 Thread Justin Bertram
One thing which I just noticed which is definitely a problem... You've defined the web server with bind="http://localhost:8161;, but your using port 8080 in your URL. The two ports should match. Justin On Wed, Feb 21, 2018 at 11:50 AM, tcomprak wrote: > Thanks Justin. I

Re: Artemis and RESTeasy jar files

2018-02-22 Thread Justin Bertram
> You should try > http://10.141.65.248:8080/artemis-rest/queues > accordingly. I don't see how that's any different from the URL he said he tried, "But I'm unable to access it from my browser http://10.141.65.248:8080/activemq-rest/queues.; Am I missing something? Justin On Thu, Feb 22, 2018

Re: Artemis and RESTeasy jar files

2018-02-22 Thread Justin Bertram
> But I'm unable to access it from my browser... You should use a REST client or a tool like curl so you can specify the kind of HTTP request (e.g. HEAD, GET, etc.) and also see the full response. Using a browser isn't going to work properly with the Artemis REST messaging interface. Also, I

Re: Artemis and RESTeasy jar files

2018-02-21 Thread Archibald
Your configuration reads: You should try http://10.141.65.248:8080/artemis-rest/queues accordingly. Br, Archibald -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Artemis and RESTeasy jar files

2018-02-21 Thread tcomprak
Thanks Justin. I did what you mentioned below - Copied the .war file to the web directory root@sh3:~/apache-artemis-2.4.0/web# ls activemq-branding.war activemq-rest.war api artemis-plugin.war console.war examples hacking-guide images index.html META-INF styles user-manual

Re: Artemis and RESTeasy jar files

2018-02-20 Thread Justin Bertram
> Is this good enough ? Artemis 2.4.0 uses RestEasy 3.0.19.Final [1] so I'd recommend you use that version as well. > I'm lost what exactly I would do with this .war file now... You deploy it just like all the other deployed war files. Drop it into ARTEMIS_HOME/web and then add a reference to

Re: Artemis and RESTeasy jar files

2018-02-20 Thread tcomprak
I figured out the error part, I had by mistaked named WEB-INF as WEB_INF. Renamed it and that fixed it. Still would like to know which RESTEasy jar files have to be picked. For now, I added this and the mvn install completed org.jboss.resteasy resteasy-jaxrs