Stacktrace does not print in Glassfish 4.1 Cluster log

Question

Performing our first cluster setup on Glassfish (4.1). Application-level (EAR) logs (e.g. for printing stacktrace) do not seem to reach the .log server at (GF-dir) /domains//logs/server.log or (GF-dir) / nodes / (node ​​-name) /( instance name )/server.log

(The documentation does not include the cluster.log file)

We have not changed any of the default logging options in logging.properties.

Current logs display only cluster and instance information.

Answer 1

I had a similar trial. server.log is not displayed after

MQJMSRA_RA1101: GlassFish MQ JMS Resource Adapter starting: broker is EMBEDDED, connection mode is TCP 

If a similar message is displayed in (GF-dir) / nodes / (node ​​-name) / (instance-name) / imq / instances / (clustername instancename) /log/log.txt

  Invalid broker address for this broker to run in cluster: Loopback IP address is not allowed in broker address mq://127.0.1.1:27676/?instName=c1i1&brokerSessionUID=2263708429127912192&ha=false for cluster 

The node server / etc / hosts file has been fixed so as not to use loopback for the node server.

Answer 2

It appears that node is no longer being output to the log file when the JMS firewall is configured as built-in (default). I tried changing it to LOCAL (in the JMS configuration, and also enabled the JMS availability service with default values), and the log file now displays as expected.

This is not a solution as such since I started getting other errors due to a JMS configuration change. But I can see error messages from my application that I could not see before.