You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by tcomprak <tc...@gmail.com> on 2018/02/20 23:41:46 UTC
Artemis and RESTeasy jar files
https://activemq.apache.org/artemis/docs/latest/rest.html
The documentation above has this line "If RESTEasy is not installed within
your environment, you must add the RESTEasy jar files within the lib
directory as well"
Which RESTEasy jar files are exactly needed ?
Also, when I tried to generate the .war file, I got this - what does this
error mean ?
[INFO] Packaging webapp
[INFO] Assembling webapp [artemis-rest] in
[/root/artemis-rest/target/artemis-rest-1.0-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/root/artemis-rest/src/main/webapp]
[INFO] Webapp assembled in [35 msecs]
[INFO] Building war: /root/artemis-rest/target/artemis-rest-1.0-SNAPSHOT.war
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 14.064 s
[INFO] Finished at: 2018-02-20T23:37:51+00:00
[INFO] Final Memory: 15M/331M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-war-plugin:2.2:war (default-war) on project
artemis-rest: Error assembling WAR: webxml attribute is required (or
pre-existing WEB-INF/web.xml if executing in update mode) -> [Help 1]
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: Artemis and RESTeasy jar files
Posted by Justin Bertram <jb...@apache.org>.
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 <ar...@gmx.net> wrote:
> What i meant, is if you publish the rest war under "artemis-rest" using
> <app url="artemis-rest" war="activemq-rest.war"/>
>
> 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
Posted by Archibald <ar...@gmx.net>.
What i meant, is if you publish the rest war under "artemis-rest" using
<app url="artemis-rest" war="activemq-rest.war"/>
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
Posted by Archibald <ar...@gmx.net>.
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:
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>org.somebody</groupId>
<artifactId>artemis-rest</artifactId>
<packaging>war</packaging>
<name>My App</name>
<version>1.0-SNAPSHOT</version>
<dependencies>
<dependency>
<groupId>org.apache.activemq.rest</groupId>
<artifactId>artemis-rest</artifactId>
<version>$VERSION</version>
<exclusions>
<exclusion>
<groupId>*</groupId>
<artifactId>*</artifactId>
</exclusion>
</exclusions>
</dependency>
</dependencies>
</project>
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: Artemis and RESTeasy jar files
Posted by Justin Bertram <jb...@apache.org>.
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 <tc...@gmail.com> wrote:
> Here is my entire broker.xml file:
>
> [vncuser@qa-centos7x64-102 broker1]$ cat etc/broker.xml
> <?xml version='1.0'?>
>
>
> <configuration xmlns="urn:activemq"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="urn:activemq
> /schema/artemis-configuration.xsd">
>
> <core xmlns="urn:activemq:core"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="urn:activemq:core ">
>
> <name>0.0.0.0</name>
>
> <persistence-enabled>true</persistence-enabled>
>
>
> <journal-type>ASYNCIO</journal-type>
>
> <paging-directory>./data/paging</paging-directory>
>
> <bindings-directory>./data/bindings</bindings-directory>
>
> <journal-directory>./data/journal</journal-directory>
>
>
> <large-messages-directory>./data/large-messages</large-messages-directory>
>
> <journal-datasync>true</journal-datasync>
>
> <journal-min-files>2</journal-min-files>
>
> <journal-pool-files>-1</journal-pool-files>
>
> <journal-file-size>10M</journal-file-size>
>
>
> <journal-buffer-timeout>36000</journal-buffer-timeout>
>
>
>
> <journal-max-io>4096</journal-max-io>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> <disk-scan-period>5000</disk-scan-period>
>
>
> <max-disk-usage>90</max-disk-usage>
>
>
> <critical-analyzer>true</critical-analyzer>
>
> <critical-analyzer-timeout>120000</critical-analyzer-timeout>
>
> <critical-analyzer-check-period>60000</critical-
> analyzer-check-period>
>
> <critical-analyzer-policy>HALT</critical-analyzer-policy>
>
>
>
> <acceptors>
>
>
>
>
>
>
> <acceptor
> name="artemis">tcp://0.0.0.0:61616?tcpSendBufferSize=
> 1048576;tcpReceiveBufferSize=1048576;protocols=CORE,AMQP,
> STOMP,HORNETQ,MQTT,OPENWIRE;useEpoll=true;amqpCredits=
> 1000;amqpLowCredits=300</acceptor>
>
>
> <acceptor
> name="amqp">tcp://0.0.0.0:5672?tcpSendBufferSize=
> 1048576;tcpReceiveBufferSize=1048576;protocols=AMQP;
> useEpoll=true;amqpCredits=1000;amqpMinCredits=300</acceptor>
>
>
> <acceptor
> name="stomp">tcp://0.0.0.0:61613?tcpSendBufferSize=
> 1048576;tcpReceiveBufferSize=1048576;protocols=STOMP;useEpoll=true
> </acceptor>
>
>
> <acceptor
> name="hornetq">tcp://0.0.0.0:5445?protocols=HORNETQ,STOMP;useEpoll=true
> </acceptor>
>
>
> <acceptor
> name="mqtt">tcp://0.0.0.0:1883?tcpSendBufferSize=
> 1048576;tcpReceiveBufferSize=1048576;protocols=MQTT;useEpoll=true
> </acceptor>
>
> <acceptor name="in-vm">vm://0</acceptor>
>
> </acceptors>
>
>
> <security-settings>
> <security-setting match="#">
> <permission type="createNonDurableQueue" roles="amq"/>
> <permission type="deleteNonDurableQueue" roles="amq"/>
> <permission type="createDurableQueue" roles="amq"/>
> <permission type="deleteDurableQueue" roles="amq"/>
> <permission type="createAddress" roles="amq"/>
> <permission type="deleteAddress" roles="amq"/>
> <permission type="consume" roles="amq"/>
> <permission type="browse" roles="amq"/>
> <permission type="send" roles="amq"/>
>
> <permission type="manage" roles="amq"/>
> </security-setting>
> </security-settings>
>
> <address-settings>
>
> <address-setting match="activemq.management#">
> <dead-letter-address>DLQ</dead-letter-address>
> <expiry-address>ExpiryQueue</expiry-address>
> <redelivery-delay>0</redelivery-delay>
>
> <max-size-bytes>-1</max-size-bytes>
>
> <message-counter-history-day-limit>10</message-counter-history-day-limit>
> <address-full-policy>PAGE</address-full-policy>
> <auto-create-queues>true</auto-create-queues>
> <auto-create-addresses>true</auto-create-addresses>
> <auto-create-jms-queues>true</auto-create-jms-queues>
> <auto-create-jms-topics>true</auto-create-jms-topics>
> </address-setting>
>
> <address-setting match="#">
> <dead-letter-address>DLQ</dead-letter-address>
> <expiry-address>ExpiryQueue</expiry-address>
> <redelivery-delay>0</redelivery-delay>
>
> <max-size-bytes>-1</max-size-bytes>
>
> <message-counter-history-day-limit>10</message-counter-history-day-limit>
> <address-full-policy>PAGE</address-full-policy>
> <auto-create-queues>true</auto-create-queues>
> <auto-create-addresses>true</auto-create-addresses>
> <auto-create-jms-queues>true</auto-create-jms-queues>
> <auto-create-jms-topics>true</auto-create-jms-topics>
> </address-setting>
> </address-settings>
>
> <addresses>
> <address name="DLQ">
> <anycast>
> <queue name="DLQ" />
> </anycast>
> </address>
> <address name="ExpiryQueue">
> <anycast>
> <queue name="ExpiryQueue" />
> </anycast>
> </address>
> <address name="q1">
> <anycast>
> <queue name="q1" />
> </anycast>
> </address>
> </addresses>
>
> <queues>
> <queue name="myQ">
> <address>myQ</address>
> <durable>false</durable>
> </queue>
> </queues>
>
> </core>
> </configuration>
>
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> f2341805.html
>
Re: Artemis and RESTeasy jar files
Posted by tcomprak <tc...@gmail.com>.
Here is my entire broker.xml file:
[vncuser@qa-centos7x64-102 broker1]$ cat etc/broker.xml
<?xml version='1.0'?>
<configuration xmlns="urn:activemq"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:activemq
/schema/artemis-configuration.xsd">
<core xmlns="urn:activemq:core"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:activemq:core ">
<name>0.0.0.0</name>
<persistence-enabled>true</persistence-enabled>
<journal-type>ASYNCIO</journal-type>
<paging-directory>./data/paging</paging-directory>
<bindings-directory>./data/bindings</bindings-directory>
<journal-directory>./data/journal</journal-directory>
<large-messages-directory>./data/large-messages</large-messages-directory>
<journal-datasync>true</journal-datasync>
<journal-min-files>2</journal-min-files>
<journal-pool-files>-1</journal-pool-files>
<journal-file-size>10M</journal-file-size>
<journal-buffer-timeout>36000</journal-buffer-timeout>
<journal-max-io>4096</journal-max-io>
<disk-scan-period>5000</disk-scan-period>
<max-disk-usage>90</max-disk-usage>
<critical-analyzer>true</critical-analyzer>
<critical-analyzer-timeout>120000</critical-analyzer-timeout>
<critical-analyzer-check-period>60000</critical-analyzer-check-period>
<critical-analyzer-policy>HALT</critical-analyzer-policy>
<acceptors>
<acceptor
name="artemis">tcp://0.0.0.0:61616?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=CORE,AMQP,STOMP,HORNETQ,MQTT,OPENWIRE;useEpoll=true;amqpCredits=1000;amqpLowCredits=300</acceptor>
<acceptor
name="amqp">tcp://0.0.0.0:5672?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=AMQP;useEpoll=true;amqpCredits=1000;amqpMinCredits=300</acceptor>
<acceptor
name="stomp">tcp://0.0.0.0:61613?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=STOMP;useEpoll=true</acceptor>
<acceptor
name="hornetq">tcp://0.0.0.0:5445?protocols=HORNETQ,STOMP;useEpoll=true</acceptor>
<acceptor
name="mqtt">tcp://0.0.0.0:1883?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=MQTT;useEpoll=true</acceptor>
<acceptor name="in-vm">vm://0</acceptor>
</acceptors>
<security-settings>
<security-setting match="#">
<permission type="createNonDurableQueue" roles="amq"/>
<permission type="deleteNonDurableQueue" roles="amq"/>
<permission type="createDurableQueue" roles="amq"/>
<permission type="deleteDurableQueue" roles="amq"/>
<permission type="createAddress" roles="amq"/>
<permission type="deleteAddress" roles="amq"/>
<permission type="consume" roles="amq"/>
<permission type="browse" roles="amq"/>
<permission type="send" roles="amq"/>
<permission type="manage" roles="amq"/>
</security-setting>
</security-settings>
<address-settings>
<address-setting match="activemq.management#">
<dead-letter-address>DLQ</dead-letter-address>
<expiry-address>ExpiryQueue</expiry-address>
<redelivery-delay>0</redelivery-delay>
<max-size-bytes>-1</max-size-bytes>
<message-counter-history-day-limit>10</message-counter-history-day-limit>
<address-full-policy>PAGE</address-full-policy>
<auto-create-queues>true</auto-create-queues>
<auto-create-addresses>true</auto-create-addresses>
<auto-create-jms-queues>true</auto-create-jms-queues>
<auto-create-jms-topics>true</auto-create-jms-topics>
</address-setting>
<address-setting match="#">
<dead-letter-address>DLQ</dead-letter-address>
<expiry-address>ExpiryQueue</expiry-address>
<redelivery-delay>0</redelivery-delay>
<max-size-bytes>-1</max-size-bytes>
<message-counter-history-day-limit>10</message-counter-history-day-limit>
<address-full-policy>PAGE</address-full-policy>
<auto-create-queues>true</auto-create-queues>
<auto-create-addresses>true</auto-create-addresses>
<auto-create-jms-queues>true</auto-create-jms-queues>
<auto-create-jms-topics>true</auto-create-jms-topics>
</address-setting>
</address-settings>
<addresses>
<address name="DLQ">
<anycast>
<queue name="DLQ" />
</anycast>
</address>
<address name="ExpiryQueue">
<anycast>
<queue name="ExpiryQueue" />
</anycast>
</address>
<address name="q1">
<anycast>
<queue name="q1" />
</anycast>
</address>
</addresses>
<queues>
<queue name="myQ">
<address>myQ</address>
<durable>false</durable>
</queue>
</queues>
</core>
</configuration>
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: Artemis and RESTeasy jar files
Posted by Justin Bertram <jb...@apache.org>.
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 <tc...@gmail.com> wrote:
> 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
> o.e.j.w.WebAppContext@697446d4{/artemis-rest,file:///home/
> vncuser/artemis-brokers/broker1/tmp/jetty-localhost-
> 8161-artemis-rest.war-_artemis-rest-any-1761735582786623780.dir/
> webapp/,UNAVAILABLE}{/home/vncuser/apache-artemis-2.4.0/
> web/artemis-rest.war}:
> java.lang.RuntimeException:
> ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007:
> Cannot connect to server(s). Tried with all available servers.]
> at
> org.apache.activemq.artemis.rest.integration.
> RestMessagingBootstrapListener.contextInitialized(
> RestMessagingBootstrapListener.java:54)
> [artemis-rest-2.4.0.jar:2.4.0]
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(
> ContextHandler.java:876)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(
> ServletContextHandler.java:532)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.server.handler.ContextHandler.
> startContext(ContextHandler.java:839)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(
> ServletContextHandler.java:344)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(
> WebAppContext.java:1480)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.webapp.WebAppContext.startContext(
> WebAppContext.java:1442)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.server.handler.ContextHandler.
> doStart(ContextHandler.java:799)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.servlet.ServletContextHandler.doStart(
> ServletContextHandler.java:261)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at org.eclipse.jetty.webapp.WebAppContext.doStart(
> WebAppContext.java:540)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.
> start(AbstractLifeCycle.java:68)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.
> start(ContainerLifeCycle.java:131)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.
> doStart(ContainerLifeCycle.java:113)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.server.handler.AbstractHandler.
> doStart(AbstractHandler.java:113)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.
> start(AbstractLifeCycle.java:68)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.
> start(ContainerLifeCycle.java:131)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at org.eclipse.jetty.server.Server.start(Server.java:452)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.
> doStart(ContainerLifeCycle.java:105)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.server.handler.AbstractHandler.
> doStart(AbstractHandler.java:113)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at org.eclipse.jetty.server.Server.doStart(Server.java:419)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.
> start(AbstractLifeCycle.java:68)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.apache.activemq.artemis.component.WebServerComponent.
> start(WebServerComponent.java:134)
> [artemis-web-2.4.0.jar:2.4.0]
> at org.apache.activemq.artemis.cli.commands.Run.execute(Run.
> java:92)
> [artemis-cli-2.4.0.jar:2.4.0]
> at
> org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:149)
> [artemis-cli-2.4.0.jar:2.4.0]
> at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.
> java:96)
> [artemis-cli-2.4.0.jar:2.4.0]
> at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.
> java:123)
> [artemis-cli-2.4.0.jar:2.4.0]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [rt.jar:1.8.0_161]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> 62)
> [rt.jar:1.8.0_161]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> [rt.jar:1.8.0_161]
> at java.lang.reflect.Method.invoke(Method.java:498)
> [rt.jar:1.8.0_161]
> at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.
> java:129)
> [artemis-boot.jar:2.4.0]
> at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:49)
> [artemis-boot.jar:2.4.0]
> Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED
> message=AMQ119007: Cannot connect to server(s). Tried with all available
> servers.]
> at
> org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.
> createSessionFactory(ServerLocatorImpl.java:790)
> [artemis-core-client-2.4.0.jar:2.4.0]
> at
> org.apache.activemq.artemis.rest.MessageServiceManager.
> start(MessageServiceManager.java:150)
> [artemis-rest-2.4.0.jar:2.4.0]
> at
> org.apache.activemq.artemis.rest.integration.
> RestMessagingBootstrapListener.contextInitialized(
> RestMessagingBootstrapListener.java:50)
> [artemis-rest-2.4.0.jar:2.4.0]
> ... 31 more
>
> 12:01:30,149 INFO [org.apache.activemq.artemis] AMQ241001: HTTP Server
> started at http://localhost:8161
> 12:01:30,150 INFO [org.apache.activemq.artemis] AMQ241002: Artemis Jolokia
> REST API available at http://localhost:8161/console/jolokia
> 12:01:30,150 INFO [org.apache.activemq.artemis] AMQ241004: Artemis Console
> available at http://localhost:8161/console
>
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> f2341805.html
>
Re: Artemis and RESTeasy jar files
Posted by tcomprak <tc...@gmail.com>.
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
o.e.j.w.WebAppContext@697446d4{/artemis-rest,file:///home/vncuser/artemis-brokers/broker1/tmp/jetty-localhost-8161-artemis-rest.war-_artemis-rest-any-1761735582786623780.dir/webapp/,UNAVAILABLE}{/home/vncuser/apache-artemis-2.4.0/web/artemis-rest.war}:
java.lang.RuntimeException:
ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007:
Cannot connect to server(s). Tried with all available servers.]
at
org.apache.activemq.artemis.rest.integration.RestMessagingBootstrapListener.contextInitialized(RestMessagingBootstrapListener.java:54)
[artemis-rest-2.4.0.jar:2.4.0]
at
org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:876)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:532)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:839)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:344)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1480)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1442)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:799)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:261)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:540)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:113)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at org.eclipse.jetty.server.Server.start(Server.java:452)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:105)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at org.eclipse.jetty.server.Server.doStart(Server.java:419)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.apache.activemq.artemis.component.WebServerComponent.start(WebServerComponent.java:134)
[artemis-web-2.4.0.jar:2.4.0]
at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:92)
[artemis-cli-2.4.0.jar:2.4.0]
at
org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:149)
[artemis-cli-2.4.0.jar:2.4.0]
at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:96)
[artemis-cli-2.4.0.jar:2.4.0]
at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:123)
[artemis-cli-2.4.0.jar:2.4.0]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[rt.jar:1.8.0_161]
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[rt.jar:1.8.0_161]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[rt.jar:1.8.0_161]
at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_161]
at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:129)
[artemis-boot.jar:2.4.0]
at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:49)
[artemis-boot.jar:2.4.0]
Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED
message=AMQ119007: Cannot connect to server(s). Tried with all available
servers.]
at
org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:790)
[artemis-core-client-2.4.0.jar:2.4.0]
at
org.apache.activemq.artemis.rest.MessageServiceManager.start(MessageServiceManager.java:150)
[artemis-rest-2.4.0.jar:2.4.0]
at
org.apache.activemq.artemis.rest.integration.RestMessagingBootstrapListener.contextInitialized(RestMessagingBootstrapListener.java:50)
[artemis-rest-2.4.0.jar:2.4.0]
... 31 more
12:01:30,149 INFO [org.apache.activemq.artemis] AMQ241001: HTTP Server
started at http://localhost:8161
12:01:30,150 INFO [org.apache.activemq.artemis] AMQ241002: Artemis Jolokia
REST API available at http://localhost:8161/console/jolokia
12:01:30,150 INFO [org.apache.activemq.artemis] AMQ241004: Artemis Console
available at http://localhost:8161/console
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: Artemis and RESTeasy jar files
Posted by Justin Bertram <jb...@apache.org>.
> 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 absence of any other configuration. They wouldn't be defaults
otherwise. :)
The same section of documentation you quoted states that the default url
which the REST interface will use to connect to the broker is "vm://0".
Justin
On Thu, Feb 22, 2018 at 1:48 PM, tcomprak <tc...@gmail.com> wrote:
> Thanks. I added that as well now as follows
>
>
> <acceptor name="in-vm">vm://0</acceptor>
>
> </acceptors>
>
> 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
> options. These are configured via XML configuration file that must be in
> your WEB-INF/classes directory. You must set the web.xml context-param
> rest.messaging.config.file to specify the name of the configuration file.
> Below is the format of the XML configuration file and the default values
> for
> each.
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> f2341805.html
>
Re: Artemis and RESTeasy jar files
Posted by tcomprak <tc...@gmail.com>.
Thanks. I added that as well now as follows
<acceptor name="in-vm">vm://0</acceptor>
</acceptors>
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
options. These are configured via XML configuration file that must be in
your WEB-INF/classes directory. You must set the web.xml context-param
rest.messaging.config.file to specify the name of the configuration file.
Below is the format of the XML configuration file and the default values for
each.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: Artemis and RESTeasy jar files
Posted by Justin Bertram <jb...@apache.org>.
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 acceptor configured with this url? If not, you should.
Justin
On Thu, Feb 22, 2018 at 1:23 PM, tcomprak <tc...@gmail.com> wrote:
> 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
> o.e.j.w.WebAppContext@27494e46{/artemis-rest,file:///home/
> vncuser/artemis-brokers/broker1/tmp/jetty-localhost-
> 8161-artemis-rest.war-_artemis-rest-any-1297401241729321808.dir/
> webapp/,UNAVAILABLE}{/home/vncuser/apache-artemis-2.4.0/
> web/artemis-rest.war}:
> java.lang.RuntimeException:
> ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007:
> Cannot connect to server(s). Tried with all available servers.]
> at
> org.apache.activemq.artemis.rest.integration.
> RestMessagingBootstrapListener.contextInitialized(
> RestMessagingBootstrapListener.java:54)
> [artemis-rest-2.4.0.jar:2.4.0]
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(
> ContextHandler.java:876)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(
> ServletContextHandler.java:532)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.server.handler.ContextHandler.
> startContext(ContextHandler.java:839)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(
> ServletContextHandler.java:344)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(
> WebAppContext.java:1480)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.webapp.WebAppContext.startContext(
> WebAppContext.java:1442)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.server.handler.ContextHandler.
> doStart(ContextHandler.java:799)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.servlet.ServletContextHandler.doStart(
> ServletContextHandler.java:261)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:540)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.
> start(AbstractLifeCycle.java:68)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.
> start(ContainerLifeCycle.java:131)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.
> doStart(ContainerLifeCycle.java:113)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.server.handler.AbstractHandler.
> doStart(AbstractHandler.java:113)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.
> start(AbstractLifeCycle.java:68)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.
> start(ContainerLifeCycle.java:131)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at org.eclipse.jetty.server.Server.start(Server.java:452)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.
> doStart(ContainerLifeCycle.java:105)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.server.handler.AbstractHandler.
> doStart(AbstractHandler.java:113)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at org.eclipse.jetty.server.Server.doStart(Server.java:419)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.
> start(AbstractLifeCycle.java:68)
> [jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
> at
> org.apache.activemq.artemis.component.WebServerComponent.
> start(WebServerComponent.java:134)
> [artemis-web-2.4.0.jar:2.4.0]
> at org.apache.activemq.artemis.cli.commands.Run.execute(Run.
> java:92)
> [artemis-cli-2.4.0.jar:2.4.0]
> at
> org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:149)
> [artemis-cli-2.4.0.jar:2.4.0]
> at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.
> java:96)
> [artemis-cli-2.4.0.jar:2.4.0]
> at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.
> java:123)
> [artemis-cli-2.4.0.jar:2.4.0]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [rt.jar:1.8.0_161]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> 62)
> [rt.jar:1.8.0_161]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> [rt.jar:1.8.0_161]
> at java.lang.reflect.Method.invoke(Method.java:498)
> [rt.jar:1.8.0_161]
> at
> org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:129)
> [artemis-boot.jar:2.4.0]
> at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:49)
> [artemis-boot.jar:2.4.0]
> Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED
> message=AMQ119007: Cannot connect to server(s). Tried with all available
> servers.]
> at
> org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.
> createSessionFactory(ServerLocatorImpl.java:790)
> [artemis-core-client-2.4.0.jar:2.4.0]
> at
> org.apache.activemq.artemis.rest.MessageServiceManager.
> start(MessageServiceManager.java:150)
> [artemis-rest-2.4.0.jar:2.4.0]
> at
> org.apache.activemq.artemis.rest.integration.
> RestMessagingBootstrapListener.contextInitialized(
> RestMessagingBootstrapListener.java:50)
> [artemis-rest-2.4.0.jar:2.4.0]
> ... 31 more
> 11:21:33,782 INFO [org.apache.activemq.artemis] AMQ241001: HTTP Server
> started at http://localhost:8161
> 11:21:33,783 INFO [org.apache.activemq.artemis] AMQ241002: Artemis Jolokia
> REST API available at http://localhost:8161/console/jolokia
> 11:21:33,783 INFO [org.apache.activemq.artemis] AMQ241004: Artemis Console
> available at http://localhost:8161/console
>
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> f2341805.html
>
Re: Artemis and RESTeasy jar files
Posted by tcomprak <tc...@gmail.com>.
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
o.e.j.w.WebAppContext@27494e46{/artemis-rest,file:///home/vncuser/artemis-brokers/broker1/tmp/jetty-localhost-8161-artemis-rest.war-_artemis-rest-any-1297401241729321808.dir/webapp/,UNAVAILABLE}{/home/vncuser/apache-artemis-2.4.0/web/artemis-rest.war}:
java.lang.RuntimeException:
ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007:
Cannot connect to server(s). Tried with all available servers.]
at
org.apache.activemq.artemis.rest.integration.RestMessagingBootstrapListener.contextInitialized(RestMessagingBootstrapListener.java:54)
[artemis-rest-2.4.0.jar:2.4.0]
at
org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:876)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:532)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:839)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:344)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1480)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1442)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:799)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:261)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:540)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:113)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at org.eclipse.jetty.server.Server.start(Server.java:452)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:105)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at org.eclipse.jetty.server.Server.doStart(Server.java:419)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.apache.activemq.artemis.component.WebServerComponent.start(WebServerComponent.java:134)
[artemis-web-2.4.0.jar:2.4.0]
at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:92)
[artemis-cli-2.4.0.jar:2.4.0]
at
org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:149)
[artemis-cli-2.4.0.jar:2.4.0]
at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:96)
[artemis-cli-2.4.0.jar:2.4.0]
at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:123)
[artemis-cli-2.4.0.jar:2.4.0]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[rt.jar:1.8.0_161]
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[rt.jar:1.8.0_161]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[rt.jar:1.8.0_161]
at java.lang.reflect.Method.invoke(Method.java:498)
[rt.jar:1.8.0_161]
at
org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:129)
[artemis-boot.jar:2.4.0]
at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:49)
[artemis-boot.jar:2.4.0]
Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED
message=AMQ119007: Cannot connect to server(s). Tried with all available
servers.]
at
org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:790)
[artemis-core-client-2.4.0.jar:2.4.0]
at
org.apache.activemq.artemis.rest.MessageServiceManager.start(MessageServiceManager.java:150)
[artemis-rest-2.4.0.jar:2.4.0]
at
org.apache.activemq.artemis.rest.integration.RestMessagingBootstrapListener.contextInitialized(RestMessagingBootstrapListener.java:50)
[artemis-rest-2.4.0.jar:2.4.0]
... 31 more
11:21:33,782 INFO [org.apache.activemq.artemis] AMQ241001: HTTP Server
started at http://localhost:8161
11:21:33,783 INFO [org.apache.activemq.artemis] AMQ241002: Artemis Jolokia
REST API available at http://localhost:8161/console/jolokia
11:21:33,783 INFO [org.apache.activemq.artemis] AMQ241004: Artemis Console
available at http://localhost:8161/console
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: Artemis and RESTeasy jar files
Posted by Justin Bertram <jb...@apache.org>.
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 <tc...@gmail.com> wrote:
> 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
> <html>
> <head>
> <meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
> <title>Error 503 Service Unavailable</title>
> </head>
> <body>
> HTTP ERROR 503
>
> <p>Problem accessing /artemis-rest/queues/myQ. Reason:
> <pre> Service Unavailable</pre></p><hr> Powered by Jetty://
> 9.4.z-SNAPSHOT <http://eclipse.org/jetty> <hr/>
>
> </body>
> </html>
> [vncuser@qa-centos7x64-102 broker1]
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> f2341805.html
>
Re: Artemis and RESTeasy jar files
Posted by tcomprak <tc...@gmail.com>.
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
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
<title>Error 503 Service Unavailable</title>
</head>
<body>
HTTP ERROR 503
<p>Problem accessing /artemis-rest/queues/myQ. Reason:
<pre> Service Unavailable</pre></p><hr> Powered by Jetty://
9.4.z-SNAPSHOT <http://eclipse.org/jetty> <hr/>
</body>
</html>
[vncuser@qa-centos7x64-102 broker1]
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: Artemis and RESTeasy jar files
Posted by Justin Bertram <jb...@apache.org>.
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 <jb...@apache.org> wrote:
> > 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 at 1:42 AM, Archibald <ar...@gmx.net> wrote:
>
>> Your configuration reads:
>> <app url="artemis-rest" war="activemq-rest.war"/>
>>
>> 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
Posted by Justin Bertram <jb...@apache.org>.
> 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 at 1:42 AM, Archibald <ar...@gmx.net> wrote:
> Your configuration reads:
> <app url="artemis-rest" war="activemq-rest.war"/>
>
> 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
Posted by Archibald <ar...@gmx.net>.
Your configuration reads:
<app url="artemis-rest" war="activemq-rest.war"/>
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
Posted by Justin Bertram <jb...@apache.org>.
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 proper
port now (i.e. 8161) which is progress. However, you are no longer
specifying the context. You were previously using "activemq-rest" which
was almost certainly wrong (as Archibald pointed out earlier). I think you
should probably be using this url:
http://localhost:8161/artemis-rest/queues/myQ
Try that and let me know how it goes. You're slowly eliminating all the
wrong ways to construct the url!
Justin
On Thu, Feb 22, 2018 at 12:56 PM, tcomprak <tc...@gmail.com> wrote:
> Thanks. I configured a queue in the broker.xml file and re started artemis.
> Added the queue element inside the core element like this
>
> <core>
>
> <queues>
> <queue name="myQ">
> <address>myQ</address>
> <durable>false</durable>
> </queue>
> </queues>
>
> </core>
>
> and I get this
>
> [vncuser@qa-centos7x64-102 broker1]$ curl --head
> http://localhost:8161/queues/myQ
> HTTP/1.1 404 Not Found
> Date: Thu, 22 Feb 2018 18:54:20 GMT
> Cache-Control: must-revalidate,no-cache,no-store
> Content-Type: text/html;charset=iso-8859-1
> Content-Length: 325
> Server: Jetty(9.4.z-SNAPSHOT)
>
>
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> f2341805.html
>
Re: Artemis and RESTeasy jar files
Posted by tcomprak <tc...@gmail.com>.
Thanks. I configured a queue in the broker.xml file and re started artemis.
Added the queue element inside the core element like this
<core>
<queues>
<queue name="myQ">
<address>myQ</address>
<durable>false</durable>
</queue>
</queues>
</core>
and I get this
[vncuser@qa-centos7x64-102 broker1]$ curl --head
http://localhost:8161/queues/myQ
HTTP/1.1 404 Not Found
Date: Thu, 22 Feb 2018 18:54:20 GMT
Cache-Control: must-revalidate,no-cache,no-store
Content-Type: text/html;charset=iso-8859-1
Content-Length: 325
Server: Jetty(9.4.z-SNAPSHOT)
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: Artemis and RESTeasy jar files
Posted by Justin Bertram <jb...@apache.org>.
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 <tc...@gmail.com> wrote:
> 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
> root@sh3:~/apache-artemis-2.4.0/web#
>
> - Created a new broker and added the web element in its etc/bootstrap.xml
> file as follows
>
> <web bind="http://localhost:8161" path="web">
> <app url="activemq-branding" war="activemq-branding.war"/>
> <app url="artemis-plugin" war="artemis-plugin.war"/>
> <app url="console" war="console.war"/>
> <app url="artemis-rest" war="activemq-rest.war"/>
> </web>
>
> - after which I started the broker
> root@sh3:/var/lib/mybroker# ./bin/artemis-service start
> Starting artemis-service
> artemis-service is now running (31401)
> root@sh3:/var/lib/mybroker#
>
> But I'm unable to access it from my browser
> http://10.141.65.248:8080/activemq-rest/queues
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> f2341805.html
>
Re: Artemis and RESTeasy jar files
Posted by Justin Bertram <jb...@apache.org>.
> 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 wouldn't expect http://10.141.65.248:8080/activemq-rest/queues to
actually return anything meaningful. You'd need to configure a queue in
broker.xml and then specify that queue in the URL, e.g.
http://10.141.65.248:8080/activemq-rest/queues/myQueue.
Justin
On Wed, Feb 21, 2018 at 11:50 AM, tcomprak <tc...@gmail.com> wrote:
> 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
> root@sh3:~/apache-artemis-2.4.0/web#
>
> - Created a new broker and added the web element in its etc/bootstrap.xml
> file as follows
>
> <web bind="http://localhost:8161" path="web">
> <app url="activemq-branding" war="activemq-branding.war"/>
> <app url="artemis-plugin" war="artemis-plugin.war"/>
> <app url="console" war="console.war"/>
> <app url="artemis-rest" war="activemq-rest.war"/>
> </web>
>
> - after which I started the broker
> root@sh3:/var/lib/mybroker# ./bin/artemis-service start
> Starting artemis-service
> artemis-service is now running (31401)
> root@sh3:/var/lib/mybroker#
>
> But I'm unable to access it from my browser
> http://10.141.65.248:8080/activemq-rest/queues
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> f2341805.html
>
Re: Artemis and RESTeasy jar files
Posted by tcomprak <tc...@gmail.com>.
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
root@sh3:~/apache-artemis-2.4.0/web#
- Created a new broker and added the web element in its etc/bootstrap.xml
file as follows
<web bind="http://localhost:8161" path="web">
<app url="activemq-branding" war="activemq-branding.war"/>
<app url="artemis-plugin" war="artemis-plugin.war"/>
<app url="console" war="console.war"/>
<app url="artemis-rest" war="activemq-rest.war"/>
</web>
- after which I started the broker
root@sh3:/var/lib/mybroker# ./bin/artemis-service start
Starting artemis-service
artemis-service is now running (31401)
root@sh3:/var/lib/mybroker#
But I'm unable to access it from my browser
http://10.141.65.248:8080/activemq-rest/queues
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: Artemis and RESTeasy jar files
Posted by Justin Bertram <jb...@apache.org>.
> 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 it in the "web" element in
etc/bootstrap.xml.
Justin
[1] https://github.com/apache/activemq-artemis/blob/2.4.0/pom.xml#L92
On Tue, Feb 20, 2018 at 6:08 PM, tcomprak <tc...@gmail.com> wrote:
> 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
>
> <dependency>
> <groupId>org.jboss.resteasy</groupId>
> <artifactId>resteasy-jaxrs</artifactId>
> <version>2.3.2.Final</version>
> </dependency>
>
> Is this good enough ?
>
> My .war file looks like this
>
> root@sh3:~/artemis-rest/target# ls
> artemis-rest-1.0-SNAPSHOT artemis-rest-1.0-SNAPSHOT.war maven-archiver
> root@sh3:~/artemis-rest/target#
>
> Now, the documentation says "For example, if you've constructed a WAR as
> described above named "activemq-rest.war" then clients will access it at,
> e.g. http://localhost:8080/activemq-rest/[queues|topics]"
>
> I'm lost what exactly I would do with this .war file now...
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> f2341805.html
>
Re: Artemis and RESTeasy jar files
Posted by tcomprak <tc...@gmail.com>.
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
<dependency>
<groupId>org.jboss.resteasy</groupId>
<artifactId>resteasy-jaxrs</artifactId>
<version>2.3.2.Final</version>
</dependency>
Is this good enough ?
My .war file looks like this
root@sh3:~/artemis-rest/target# ls
artemis-rest-1.0-SNAPSHOT artemis-rest-1.0-SNAPSHOT.war maven-archiver
root@sh3:~/artemis-rest/target#
Now, the documentation says "For example, if you've constructed a WAR as
described above named "activemq-rest.war" then clients will access it at,
e.g. http://localhost:8080/activemq-rest/[queues|topics]"
I'm lost what exactly I would do with this .war file now...
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html