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
different brokers :)
@MessageDriven(
activationConfig = { @ActivationConfigProperty(propertyName =
"destination", propertyValue = "custodian.imported"),
@ActivationConfigProperty(propertyName =
"destinationType", propertyValue = "javax.jms.Queue"),
@ActivationConfigProperty(
propertyName = "acknowledgeMode",
propertyValue = "Auto-acknowledge"),
@ActivationConfigProperty(propertyName =
"resourceAdapter", propertyValue = "artemis-rar") })
I have Quarkus app which uses smallrye-amqp connector and Payara app. Run order
is broker, payara, quarkus. This makes payara first autocreate addresses. So
the thing is I have multiple identical MDBs on Payara app and they are working,
I must say off-course maybe I made the bug, but I feel like I’m missing
something. Heres what happen.
I had some problem with 2.19.1, it didn’t want to autocreate or send message
via Topic if i remember, and the queues were working fine. So i migrated to
artemis-rar 2.28.0 and built docker image from activemq-artemis repo. And
everything worked fine. The MDB I am referring to worked fine and ANYCAST, and
MULTICAST were auto-created and messages were sent. Everything was super. I am
pretty sure almost 99% that I was using payara
luminositylabs/payara-server-full:5.2022.2_openjdk-8u345_zulu-alpine-8.64.0.19
I use this unofficial image in development because I am on arm64 processor and
the official Payara server is not supported so it is constantly sitting in my
git untagged. Then after I merged my Artemis upgrade and run on the mocked
environment server I noticed that artemis-rar is failing to deploy because
official Payara (which uses amd64) server is using was 1.8. Okay, so I changed
it to payara/server-full:5.2022.5-jdk11 and artemis-rar could be deployed once
again. From then this MDB that I am referring is not receiving messages anymore
and only those WARNING-s were suspicious at in the log file. And the worst
thing that melted my brain is that the luminositylabs payara also started to
fail to deploy artemis-rar so I bumped that too to a JDK11 version one
luminositylabs/payara-server-full:5.2022.5_openjdk-11.0.17_zulu-alpine-11.60.19
Later I’ve tried lower versions of luminositylabs payara w JDK11 and the
problem was the same.
So now I have same problem on mocked and local development environment. I
believe all MDBs are receiving messages, but one does not. I will test them all
tomorrow. And they all do the same thing, they receive the message from Artemis
broker and pass it to OpenMQ (imq) builtin Payara broker.
I tried looking back on my commits and didn’t find anything suspicious. Anyways
I hope this is a bug on my end.
Marko
> On 19. 4. 2023., at 20:41, Justin Bertram <jbert...@apache.org> wrote:
>
> 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 <jbert...@apache.org> wrote:
>
>> 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://issues.apache.org/jira/browse/ARTEMIS-4188
>>
>> On Wed, Apr 19, 2023 at 11:02 AM Marko Lazić <zila...@gmail.com> wrote:
>>
>>> 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-rar-2.28.0.rar
>>> create-resource-adapter-config --property
>>> ConnectorClassName='org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnectorFactory':ConnectionParameters='host=broker;port=61616':UserName='artemis':Password='artemis'
>>> artemis-rar
>>> create-connector-connection-pool --raname artemis-rar
>>> --connectiondefinition
>>> org.apache.activemq.artemis.ra.ActiveMQRAConnectionFactory --property
>>> UserName=artemis:Password=artemis --ping true jms/ConnectionFactoryPool
>>> create-connector-resource --poolname jms/ConnectionFactoryPool
>>> jms/msgConnectionFactory
>>>
>>>
>>>
>>>
>>> Payara log
>>>
>>> [#|2023-04-19T15:52:44.487+0000|INFO|Payara
>>> 5.2022.5|fish.payara.boot.runtime.BootCommand|_ThreadID=25;_ThreadName=RunLevelControllerThread-1681919558585;_TimeMillis=1681919564487;_LevelValue=800;|
>>> Boot Command create-resource-adapter-config returned with result
>>> SUCCESS : PlainTextActionReporterSUCCESSNo monitoring data to report.
>>> |#]
>>> [#|2023-04-19T15:52:44.502+0000|WARNING|Payara 5.2022.5|javax.enterprise.
>>> resource.resourceadapter.com
>>> .sun.enterprise.connectors.util|_ThreadID=25;_ThreadName=RunLevelControllerThread-1681919558585;_TimeMillis=1681919564502;_LevelValue=900;|
>>> RAR8000 : The method setPassword is not present in the class :
>>> org.apache.activemq.artemis.ra.ActiveMQRAManagedConnectionFactory|#]
>>> [#|2023-04-19T15:52:44.503+0000|WARNING|Payara 5.2022.5|javax.enterprise.
>>> resource.resourceadapter.com
>>> .sun.enterprise.connectors.util|_ThreadID=25;_ThreadName=RunLevelControllerThread-1681919558585;_TimeMillis=1681919564503;_LevelValue=900;|
>>> RAR7097: No setter method present for the property password in the
>>> class org.apache.activemq.artemis.ra.ActiveMQRAManagedConnectionFactory|#]
>>> [#|2023-04-19T15:52:44.503+0000|WARNING|Payara 5.2022.5|javax.enterprise.
>>> resource.resourceadapter.com
>>> .sun.enterprise.connectors.util|_ThreadID=25;_ThreadName=RunLevelControllerThread-1681919558585;_TimeMillis=1681919564503;_LevelValue=900;|
>>> RAR8000 : The method setUsername is not present in the class :
>>> org.apache.activemq.artemis.ra.ActiveMQRAManagedConnectionFactory|#]
>>> [#|2023-04-19T15:52:44.503+0000|WARNING|Payara 5.2022.5|javax.enterprise.
>>> resource.resourceadapter.com
>>> .sun.enterprise.connectors.util|_ThreadID=25;_ThreadName=RunLevelControllerThread-1681919558585;_TimeMillis=1681919564503;_LevelValue=900;|
>>> RAR7097: No setter method present for the property username in the
>>> class org.apache.activemq.artemis.ra.ActiveMQRAManagedConnectionFactory|#]
>>> [#|2023-04-19T15:52:44.920+0000|INFO|Payara
>>> 5.2022.5|fish.payara.boot.runtime.BootCommand|_ThreadID=25;_ThreadName=RunLevelControllerThread-1681919558585;_TimeMillis=1681919564920;_LevelValue=800;|
>>> Boot Command create-connector-connection-pool returned with result
>>> SUCCESS : PlainTextActionReporterSUCCESSConnector connection pool
>>> jms/ConnectionFactoryPool created.
>>> Attempting to ping during Connector Connection Pool Creation :
>>> jms/ConnectionFactoryPool - Succeeded.|#]
>>> [#|2023-04-19T15:52:44.939+0000|INFO|Payara
>>> 5.2022.5|fish.payara.boot.runtime.BootCommand|_ThreadID=25;_ThreadName=RunLevelControllerThread-1681919558585;_TimeMillis=1681919564939;_LevelValue=800;|
>>> Boot Command create-connector-resource returned with result SUCCESS :
>>> PlainTextActionReporterSUCCESSConnector resource jms/msgConnectionFactory
>>> created.|#]
>>>
>>>
>>> I noticed also some MDBs that are listening on auto-created queues do not
>>> receive messages anymore
>>>
>>>
>>> Kind regards,
>>> Marko
>>
>>
