Stacktrace不能在Glassfish 4.1集群日志中打印

问题描述

在Glassfish上做我们的第一个集群设置（4.1）。 （GF-dir）/domains//logs/server.log或（GF-dir）/ nodes /（节点名称）中的server.log似乎无法到达应用程序（EAR）级别日志）/（instance-name）/server.log

（文档中没有cluster.log）

我们没有更改logging.properties中的任何默认日志记录选项。

当前日志仅显示群集和实例相关信息。

解决方案

当JMS代理配置为嵌入式（缺省）时，节点停止输出到日志文件。我尝试将其更改为LOCAL（在JMS配置中，并且默认情况下打开了JMS可用性服务），并且现在按预期输出了日志文件。

这是这本身并不是一个解决方案，因为由于JMS配置的变化，我开始出现其他错误。但是我能够看到我的应用程序中的错误消息，这是我之前无法看到的。

Doing our first cluster setup on Glassfish (4.1). Application(EAR) level logs (ex printing a stacktrace) don't seem to reach the server.log in (GF-dir)/domains//logs/server.log or (GF-dir)/nodes/(node-name)/(instance-name)/server.log

(There is no cluster.log as stated in documentation)

We didn't change any of the default logging options in logging.properties.

The current logs only show cluster and instance related information.

解决方案

It seems that the node stops to output to the log file when JMS broker is configured as embedded (the default). I tried to change it to LOCAL (in the JMS configuration, plus turned on JMS availability service with defaults), and the log file is now output as expected.

This is not a solution per se, as I started to get other errors due to the change in JMS configuration. But I'm able to see error messages from my application which I was not able to see before.

这篇关于Stacktrace不能在Glassfish 4.1集群日志中打印的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！