Looks like the maxReconnectAttempts=0 helped me. Thanks, Tim!
When switching to 5.13, I'll check again if there are some problems
remaining - currently it seems to work fine.
Best Regards,
Jochen
--
View this message in context:
We have a serviceMix 4.3 which use the same ActiveMQ (embedded) and we also
have the issue.
In another deployment, we use ActiveMQ 5.10.x and apparently the activemqweb
is working better (still few bugs when you browse queue from the slave
instance) but quite more stable anyway.
We plan to
Note that what you're asking for is not a fix, but rather an enhancement.
Nothing's broken: the failover transport is successfully connecting to the
first responsive URI in the list, it's just that that's not the behavior
you actually want. Which simply means that the failover transport isn't
the
I made a few modifications to the AMQP example to enable security on the broker
and to pass the appropriate username and password from the client and
everything worked as expected. Can you provide me with a way to reproduce the
failure you're seeing?
Justin
- Original Message -
Turns out that Spring is creating two instances of bean "jmsServer"
(EmbeddedJMS) and invoking method "start" on both. On the first invocation
of "start", the server starts normally and quietly. On the second, it
throws the exception. Now I just need to determine why Spring creates two
The element was supported in previous versions of Artemis, but
support was removed when matured enough to make
unnecessary.
Justin
- Original Message -
From: "spruitt"
To: users@activemq.apache.org
Sent: Thursday, January 14, 2016 10:45:55 AM
Subject: basic
Any idea what might be the cause of the IllegalArgumentException that the
Tomcat log file sample below shows? Here, an embedded ActiveMQ Artemis
server runs inside a Tomcat 8 Web application context and Spring
4.1.7.RELEASE creates an instance of EmbeddedJMS similar to what example
"embedded"
Can someone post an example of for the tab in the
bootstrap.xml file.
I left the tag in the file and added
this:
file:${activemq.home}/etc/artemis-users.properties
file:${activemq.home}/etc/artemis-roles.properties
guest
Now Artemis broker throws a SAX parse exception
Invalid
On Thu, Jan 14, 2016 at 9:27 AM, spruitt wrote:
> That is the code I started with. But I get:
>
> Exception in thread "main" javax.jms.JMSSecurityException: AMQ119031: Unable
> to validate user
>
> So next I started trying:
>
> connection =
Can you set these two properties at your JDK?
-Djava.util.logging.manager="$ARTEMIS_LOG_MANAGER" \
-Dlogging.configuration="$ARTEMIS_LOGGING_CONF"
On Thu, Jan 14, 2016 at 2:29 PM, Derek Mahar wrote:
> How may I suppress the debug continuous stream of log messages that
that's probably tracing meant for debugging.
On Thu, Jan 14, 2016 at 4:35 PM, Derek Mahar wrote:
> Yes, but it was only the server that was generating large numbers of
> repetitive "doing deliver" log messages. Not entirely sure what those mean.
>
> On 14 January 2016 at
there are a set of examples with the artemis download.
the one under examples/features/standard/security doesn't suit what
you're looking for?
On Thu, Jan 14, 2016 at 11:45 AM, spruitt wrote:
> Can someone post an example of for the tab in the
> bootstrap.xml file.
>
> I
I managed to suppress the Artemis debug log messages by adding the line
to file "logback.xml" in our project.
Derek
On 14 January 2016 at 15:00, Derek Mahar wrote:
> After reading http://activemq.apache.org/artemis/docs/1.2.0/logging.html
> and
>
How may I suppress the debug continuous stream of log messages that the
ActiveMQ Artemis embedded server generates? Some sample messages:
2016-01-14 09:51:09.066 [DEBUG] [Thread-6
(ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@230a9578-1801390477)]
After reading http://activemq.apache.org/artemis/docs/1.2.0/logging.html
and
https://docs.jboss.org/hibernate/orm/4.3/topical/html/logging/Logging.html,
I think I can figure it out. In our project, JBossLogging delegates to
Slf4j which in turn delegates to Logback, so in order to suppress the
shouldn't you be at org.apache.activemq.artemis ?
as journal, client and others could still be logging debug and trace?
On Thu, Jan 14, 2016 at 3:16 PM, Derek Mahar wrote:
> I managed to suppress the Artemis debug log messages by adding the line
>
>
>
> to file
Hi Dejan,
the last days I messed around with the config of OCSP. I've set the
following configuration into activemq.bat:
set ACTIVEMQ_SSL_OPTS="-Dcom.sun.security.enableCRLDP=true
-Docsp.enable=true -Docsp.responderURL=http://my.ocspurl.example;
echo %ACTIVEMQ_SSL_OPTS%
When executing the
That is the code I started with. But I get:
Exception in thread "main" javax.jms.JMSSecurityException: AMQ119031: Unable
to validate user
So next I started trying:
connection = connectionFactory.createConnection(user, pw);
But I still get:
Exception in thread "main"
Yes, but it was only the server that was generating large numbers of
repetitive "doing deliver" log messages. Not entirely sure what those mean.
On 14 January 2016 at 15:19, Clebert Suconic
wrote:
> shouldn't you be at org.apache.activemq.artemis ?
>
> as journal,
19 matches
Mail list logo