Re: Payara connection pool 2.28.0

I fixed the problem by having payara JDK 1.8 and artemis-rar 2.19.1 deployed, while I’m using 2.28.0 as broker > On 20. 4. 2023., at 11:16, Marko Lazić wrote: > > Yes you are right about logging I also have > > [#|2023-04-20T09:08:56.810+|SEVERE|Payara > 5.2022.5||_ThreadID=24;_ThreadName

Re: Payara connection pool 2.28.0

Looking at Release v1.6.0 · fmtn/a (github.com) it could be fixed in payara 6, but it would be really good if i could solve it with payara 5 > On 20. 4. 2023., at 10:42, Robbie Gemmell wrote: > > Actually since the logging is not from artemis its

Re: Payara connection pool 2.28.0

The deployment of artemis-rar switches the SLFJ4 to NOP and I probably have bug in my MDB that is not working. Funny thing when I realised this and searched the mailing list I’ve found this one :) > On 20. 4. 2023., at 10:42, Robbie Gemmell wrote: > > Actually since the logging is not from art

Re: Payara connection pool 2.28.0

Yes you are right about logging I also have [#|2023-04-20T09:08:56.810+|SEVERE|Payara 5.2022.5||_ThreadID=24;_ThreadName=RunLevelControllerThread-1681981732090;_TimeMillis=1681981736810;_LevelValue=1000;| SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".|#] [#|2023-04-20T09:0

Re: Payara connection pool 2.28.0

Actually since the logging is not from artemis itself, the last bit probably doenst really make sense hehe.although we did also remove the JBL usage any related JUL config around log managers etc, so the change probably could still have an effect...albeit perhaps to make it less likely to log s

Re: Payara connection pool 2.28.0

As you said, the setters presumably didnt exist before, and still dont, soperhaps the main difference is just in the logging setup? The old version was 2.19.1 (noted later) which used JBoss Logging, while the newer version is 2.28.0 which now uses SLF4J API and in turn any supporting logging i

Re: Payara connection pool 2.28.0

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

Re: Payara connection pool 2.28.0

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

Re: Payara connection pool 2.28.0

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

Re: Payara connection pool 2.28.0

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

Payara connection pool 2.28.0

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