> Could it be that our Artemis instance is still using older JDK which
exist only in memory, and console "inherits" that by trying to start
itself, and then fails?
I don't have any experience with such a use-case so it's hard to say. The
"console" isn't fundamentally different from any other part
No, I don't see any of these messages in the log. I have posted full log what I
see.
This is production system so getting threadump is not so easy, but I have
decided to test this on our testing environment which runs newest 2.27.1.
Running restartEmbeddedWebServer() via Hawtio console on that
We're using a build.gradle file actually. Personally, I'd like to move the
dependencies to a pom.xml file, but that'll come later
On Wed, Jan 11, 2023, 12:31 PM Justin Bertram wrote:
> I was under the impression that Gradle understood Maven pom files so that
> if your project depended on org.apa
I was under the impression that Gradle understood Maven pom files so that
if your project depended on org.apache.activemq:artemis-server it would get
all the transitive dependencies like commons-beanutils:commons-beanutils.
Is that not the case?
Justin
On Wed, Jan 11, 2023 at 2:14 PM Michael Bre
Ah, that explains why it's missing. We're using Gradle on this project to
import dependencies. I'll add that dependency as well
On Wed, Jan 11, 2023, 12:06 PM Justin Bertram wrote:
> Looks like you need commons-beanutils:commons-beanutils:1.9.4 [1]. This
> dependency is declared in the artemis-s
Looks like you need commons-beanutils:commons-beanutils:1.9.4 [1]. This
dependency is declared in the artemis-server [2] module so you should get
it automatically if you're using Maven to manage your dependencies.
Justin
[1]
https://search.maven.org/artifact/commons-beanutils/commons-beanutils/1
John, I appreciate your suggestions! I will try to put them to work today.
Perhaps they can help me resolve a runtime error I'm getting from
embeddedActiveMQ.start()? the stacktrace looks something like this:
[23-Jan-10 14:16:50:330] [INFO] [BrokerInitializer:197] - Embedded Artemis
Broker being
Thanks for following up, Fredrik.
I believe the changes from ARTEMIS-4065 [1] will resolve your issue in
2.28.0. You can test your reproducer with a snapshot [2] in the mean-time
if you like.
Justin
[1] https://issues.apache.org/jira/browse/ARTEMIS-4065
[2]
https://repository.apache.org/content
> In particular, AMQ 5 let's you create several objects off the same
Session and use them concurrently...
For what it's worth, the JMS specification states that Session objects are
*not* thread-safe so any concurrent use is a spec violation. You may find
implementations where concurrent use happen
Those exceptions look internal to Jetty. I wouldn't expect them to
necessarily be a problem for the restart process. Perhaps it was handling a
request at the moment you tried to restart it.
Do you ever see any of these messages in the log:
Stopped embedded web server
or
Embedded web server
Michael,
I am also not familiar with "activemq-broker-initializer", and do not see any
documentation for it online.
I suspect that this is a custom Spring factory bean that those who came before
you created. Because Spring is limited to creating objects and setting
properties, such a thing is
Well, I have found " restartEmbeddedWebServer()" and tried to use that from the
console, however now the console went down and doesn't come up. The logs say:
https://p.defau.lt/?C6ssFYW0JSJiZX1yszP0yQ
Jolokia API is also down now. Is there a way to start embedded web server
without restarting t
Hi,
since because of https://issues.apache.org/jira/browse/ARTEMIS-3117 ActiveMQ
Artemis doesn‘t reload TLS certificates automatically anymore I‘m wondering,
what is the correct way to reload certificates for embedded Jolokia Console?
I have reloaded keystore for acceptors via console using rel
13 matches
Mail list logo
