Ara-Server | - The server for Ara | REST library

Changed glassfish-resources.xml to payara-resources.xml and changed the contents of the file to:

The timeout you're referring to is not related to how long it takes the consumer who receives message to "respond." The timeout is simply about how long the sending client will wait for the broker to acknowledge that it has indeed received the message. This happens before the consumer ever receives the message.

If you're implementing request/response functionality with JMS then you should follow the proper pattern either using correlation ID or temporary reply queues.

Given that you're using the ActiveMQ JCA resource adapter it's very likely the connection implementation your client actually gets from the JNDI lookup will be wrapped by the JCA implementation of your container. It's unlikely you will be able to simply cast it to the ActiveMQ implementation. Furthermore, all the ActiveMQ client classes are packaged in the JCA resource adapter archive and isolated from your application. You're likely to get weird classloading behavior (e.g. unexpected ClassCastException) if you put those same classes somewhere else in your runtime environment. Java EE application servers are designed to give access to the Java EE APIs (e.g. JMS, JDBC, JNDI, etc.). Getting access to the underlying implementations to do non-portable stuff is generally difficult and discouraged.

You could check this using jmap -heap on the PID of the Payara process. jmap is contained in the JDK bin directory.

On JDK9+ you need to use jhsdb jmap --heap --pid to get the needed information.

The output should contain the needed information, e.g: