|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 4417 | major | always | 03-01-11 08:29 | 04-07-11 09:50 | |
|
|
|||||
| Reporter: | stoty | Platform: | |||
| Assigned To: | alex | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 4.0.15 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.16 | ||
|
|
|||||
| Summary: | 0004417: Debugging does not work with 4.0.15 version of the Eclipse plugin | ||||
| Description: | After upgrading the caucho resin Eclipse plugin to the current version (4.0.15) from the update site, debugging no longer works from within eclipse. | ||||
| Steps To Reproduce: | |||||
| Additional Information: |
I spent some time chasing the problem down, and it caused by the change where 4.0.15 starts <mainClass>com.caucho.boot.ResinBoot</mainClass> instead of <mainClass>com.caucho.server.resin.Resin</mainClass>. ResinBoot forks, and starts an other JVM, to which eclipse does not seem to have debugging access. I have replaced the <start> ... </start> section of resin40-in-place.serverdef with the <start> ... </start> section from the 4.0.2 version of the plugin I had laying around, and debugging works fine with that change. So It seems either the change needs to be reverted, so that eclipse starts resin directly, without the watchdog, or some way needs to be found that propagates the debugging connection from eclipse to the forked JVM. Personally, I think that there is no point in having a watchdog for a server that is started by eclipse. |
||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||