Owners Manual
Troubleshooting Your Application | Troubleshooting
712 OMNM 6.5.2 User Guide
To see what categories are available, look in
\oware\jboss-x.x.x\server\
oware\conf\log4j.xml.
This file concatenates all logging categories, but is generated, and
should
not
be changed.
When application server starts, it detects logging levels in these categories and concatenates them
into the server's
log4j.xml
from
*log4j.xml
files in the
server\conf
directories of
installed components under
owareapps
.
When it starts, application server processes logging for components in order of their dependency,
and overrides any detected settings from a file whose name ends in
log4j.xml
in the
installprops
directory.
This application applies detected changes once a minute. The log4j file scanner can then detect
any subsequent changes up to a minute after making them. The
server.log
is not truncated
when this occurs.
The following are additional categories that allow logging level changes:
For Mediation Server registration with App Server, add the following category:
<category name="com.dorado.mbeans.OWMedServerTrackerMBean">
<priority value=“WARN"/>
</category>
For SNMP and Syslog, change INFO to DEBUG in
<category name="com.dorado.core.mediation">
<priority value="INFO"/>
</category>
To view debug output:
Server
Debug does not appear in real-time in the application server shell (if you have one). View real-time
and historical logs in the
oware\jboss-x.x.x\server\oware\log
directory.
NOTE:
Typing
oware
in a Windows shell lets you use Linux commands like
tail -f server.log
. Tailing
it lets you watch the log file as it is generated.
Resolving Port Conflicts
Installation scans for port conflicts, but these may arise after you install too. If your application
runs with others, conflicts related to those other applications’ ports are possible. For example: the
application can have trouble communicating with the built-in TFTP server for backups. Port
contention of TFTP on UDP port 69 with other applications can cause this. Try rebooting the
system to clear any unused ports and verify that UDP port 69 is not in use before starting the
application.
Finding Port Conflicts
You can find ports in use with the following command line:
netstat -a -b -o | findstr [port number]
Use this command to track down port conflicts if installation reports one. Best practice is to run
this software on its own machine to avoid such conflicts. Freeware port conflict finding programs
like Active Ports are also available.