I was able to take the archive you attached and reproduce the issue in just
a few minutes. Thanks for the great reproducer!
During reproduction I noticed something odd in the log. In a two-node
cluster you would expect each node to have 1 bridge each (i.e. going to the
*other* node of the cluster)
Have you looked into message Groups? It seems messages connected to a
different consumer during failover and redelivery happened.
On Wed, Apr 19, 2023 at 5:32 PM Justin Bertram wrote:
> Hey, Oliver. I apologize for the delay on this. It fell off my radar as
> I've been concentrating on other tas
I forgot to mention that previous Artemis version was 2.19.1 where there were
no warnings.
About other problem with MDB not working
This is how MDB on Payara looks like, it only passes the data to another
connection factory that sends message to builtin imq broker. So yeah i have two
differen
Hey, Oliver. I apologize for the delay on this. It fell off my radar as
I've been concentrating on other tasks.
For what it's worth, the community support [1] provided on the mailing list
is, as the website says, provided for free on a volunteer basis. I would
imagine that everybody on this list h
Does the fact that the setters for username and password don't exist
actually prevent you from using the RA as expected?
Justin
On Wed, Apr 19, 2023 at 11:02 AM Marko Lazić wrote:
> Hello,
>
>
> The following code worked before with Payara 5.2022.2 1.8 jdk but now when
> i upgraded to 2.28.0 a
Actually I went ahead and opened a Jira for the setter issue [1].
Justin
[1] https://issues.apache.org/jira/browse/ARTEMIS-4246
On Wed, Apr 19, 2023 at 1:40 PM Justin Bertram wrote:
> I wonder if the newer version of Payara is now logging warnings about the
> missing setters. The fact that th
I wonder if the newer version of Payara is now logging warnings about the
missing setters. The fact that they aren't there isn't new, but we can
certainly add them. Feel free to open a Jira.
As for the MDBs not receiving messages, you are probably hitting
ARTEMIS-4188 [1].
Justin
[1] https://is
Hello,
The following code worked before with Payara 5.2022.2 1.8 jdk but now when i
upgraded to 2.28.0 artemis and Payara 5.2022.5-jdk11 it has some problems
payara pre-boot.commands.asadmin file
# Apache ActiveMQ Artemis
deploy --type rar --name artemis-rar
/opt/payara/deployments/artemis-ra
Hi Justin,
this question is created about 4 weeks ago.
I can imagine that reproducing the unexpected behavior might take some time.
But does it really takes that long?
Do you still think that the dev team will give a feedback?
Regards,
Oliver
On 4/12/23 10:10, Oliver Lins wrote:
Hi,
askin
Hello.
I see no answer, but I've a first working solution.
I've slightly modified the activemq script (in my docker file with
sed) to add 'exec' to the java command :
The lines :
$EXEC_OPTION $DOIT_PREFIX "\"$JAVACMD\" $ACTIVEMQ_OPTS $ACTIVEMQ_DEBUG_OPTS
are replaced with :
$EXEC_OPTION
10 matches
Mail list logo
