Log files
When you run an application, the Genero Application Server (GAS) creates log files which may be viewed for troubleshooting.
- Dispatcher
- A log file is generated for each dispatcher. Incoming requests, starting of proxies, responses sent, and system error messages are captured.
- Proxy
- A separate log file is generated for each proxy started.
- DVM
- A log file is generated for each DVM started. DVM standard error and standard output are sent to the dedicated DVM log files.
Accessing log files in appdata
You can access log files in your appdata/log/dispatcher_name/date directory.
In a Windows® platform, for example, log files are found in the C:\ProgramData\vendor\gas\gas_version\log\dispatcher_name\current_date directory.
Accessing log files from monitor URL
While the dispatcher is running, access the logs from the GAS monitor URL http://appserver:port/monitor. Use the links found in the monitor page to view current dispatcher and proxy logs.
Log file names
- Dispatcher log
- The name specifies the type of dispatcher. Examples:
- httpdispatch.log
- isapidispatch.log
- fastcgidispatch.log
- Proxy log
- The name indicates the type of proxy. Examples:
- uaproxy-<session-id>.log
- gwsproxy-<group>-<app>.log
- DVM logs
-
- Web applications
The name includes the session-id. For example vm-<session-id>.log
- Web ServicesWhen working with Web services, a GWS proxy can spawn multiple DVMs. Each DVM gets its own log file. The log file is suffixed with a number from 0 to
MAX_AVAILABLE
-1. For example, vm-<group>-<app>-<number>.log- vm-demo-Calculator-0.log
- vm-demo-Calculator-1.log
Note: A log file is reused for new DVM logs if the previous DVM has finished, to avoid the accumulation of log files on disk.
- Web applications
Manage the Genero Application Server log files
The GAS creates a log for each application session. As a result, you can end up with a lot of log files. You should have some plan for archiving and removing log files. For UNIX-based platforms, you can use utilities such as logrotate to compress and move log files. For Windows, any program that can compress and archive log files can be used.
fastcgidispatch
process (see
Apache: mod_fastcgi) while it may not stop the existing process. If you
observe this behavior, you can set logrotate's prerotate
script to get the pid of
the running fastcgidispatch
process; it should then be possible to stop the old
fastcgidispatch
process in the postrotate
script. For more information, see logrotate.