|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 2750 | minor | always | 06-23-08 12:20 | 06-23-08 16:16 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 3.1.6 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.2.0 | ||
|
|
|||||
| Summary: | 0002750: admin display of classpath | ||||
| Description: |
(rep by Martin Morawetz) We have some classpath issues when using resin on a linux system. Some jars which get loaded under windows apparently don?t get loaded in the linux environment. The only difference I know is that we use resin-pro3.1.2 on Windows and resin-pro3.1.6 on linux. To see what resin actually loads I added the -verbose flag to the httpd start script, but that doesn?t seem to have any effect. Where should I see the logged classpath? Stdout? Just out of curiosity: why does the resin-admin webapp doesn?t show the classpath? |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |