Anonymous | Login | Signup for a new account | 12-17-2024 10:50 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0002750 | [Resin] | minor | always | 06-23-08 12:20 | 06-23-08 16:16 | ||||
Reporter | ferg | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | Platform | |||||
Status | closed | OS | |||||||
Projection | none | OS Version | |||||||
ETA | none | Fixed in Version | 3.2.0 | Product Version | 3.1.6 | ||||
Product Build | |||||||||
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 | |||||||||
Attached Files | |||||||||
|
There are no notes attached to this issue. |
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
26 total queries executed. 24 unique queries executed. |