RE: remote debug with tomcat 3.3.2
From: Kedzior Wojciech [mailto:wojciech.kedz...@gemalto.com] Subject: remote debug with tomcat 3.3.2 I'm having a problem with setting up a remote debug session to my Tomcat 3.3.2 Final. You're asking for help with a version of Tomcat that's six years old and hasn't been supported for ages? Not to mention buggier and much slower than the current releases. Your time would be better spent moving up to a supported level and then working on the debugging. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: remote debug with tomcat 3.3.2
Hi Chuck, Thanks for your answer. That is exactly how I feel. However I'm not the person responsible for these kinds of decisions within the company. I am merely trying to help the guys here by being more (much much more) efficient by using a debugger instead of log files when developing code. To be honest I have no idea why they use such an old version of Tomcat. And I hope RND or someone is looking at upgrading. I also suspect that there are some proprietary libraries involved here, which may hinder a tomcat upgrade. I hate it, but I have to do with what I have and I'm just trying to get the best out of what I have. So, any other suggestions? Cheers -Original Message- From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] Sent: 2. března 2010 15:16 To: Tomcat Users List Subject: RE: remote debug with tomcat 3.3.2 From: Kedzior Wojciech [mailto:wojciech.kedz...@gemalto.com] Subject: remote debug with tomcat 3.3.2 I'm having a problem with setting up a remote debug session to my Tomcat 3.3.2 Final. You're asking for help with a version of Tomcat that's six years old and hasn't been supported for ages? Not to mention buggier and much slower than the current releases. Your time would be better spent moving up to a supported level and then working on the debugging. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: remote debug with tomcat 3.3.2
On 02/03/2010 15:28, Kedzior Wojciech wrote: Hi Chuck, Thanks for your answer. That is exactly how I feel. However I'm not the person responsible for these kinds of decisions within the company. I am merely trying to help the guys here by being more (much much more) efficient by using a debugger instead of log files when developing code. To be honest I have no idea why they use such an old version of Tomcat. And I hope RND or someone is looking at upgrading. I also suspect that there are some proprietary libraries involved here, which may hinder a tomcat upgrade. I hate it, but I have to do with what I have and I'm just trying to get the best out of what I have. So, any other suggestions? http://www.monster.fr/ ;o) p Cheers -Original Message- From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] Sent: 2. března 2010 15:16 To: Tomcat Users List Subject: RE: remote debug with tomcat 3.3.2 From: Kedzior Wojciech [mailto:wojciech.kedz...@gemalto.com] Subject: remote debug with tomcat 3.3.2 I'm having a problem with setting up a remote debug session to my Tomcat 3.3.2 Final. You're asking for help with a version of Tomcat that's six years old and hasn't been supported for ages? Not to mention buggier and much slower than the current releases. Your time would be better spent moving up to a supported level and then working on the debugging. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: remote debug with tomcat 3.3.2
I'm pretty sure that I compiled the binary for 3.3.2 without debugging support. The only thing I can think of is to download the source release of 3.3.2 and compile it with debugging. At the time 3.3.2 was released, using a debugger in Java was so painful that almost nobody did it. Kedzior Wojciech wojciech.kedz...@gemalto.com wrote in message news:a8dd7b2abeb7b842af607d392ff73c7ee4834af...@croexcfwp03.gemalto.com... Hello, I'm having a problem with setting up a remote debug session to my Tomcat 3.3.2 Final. I am copying some classes I developed into the working directory of an application deployed on tomcat. I can connect to the remote debug port from eclipse but the debugger will not stop on any break points what so ever. Here is my environment: I specify the following system variables: JPDA_ADDRESS=8000 JPDA_TRANSPORT=dt_socket I start my Tomcat with the jpda start parameters. While tailing the logs I can see the following line: Listening for transport dt_socket at address: 8000 At this point I can connect to the remote debug port from Eclipse. I can see all the treads running within Tomcat, but my debug will not stop on any breakpoints. Even though the class I am trying to debug was created by me in Eclipse and I have the correct source. The classes were compiled using Java 1.5.0_09. Tomcat also uses the same version of Java. The tomcat is deployed on Linux RedHat 5. Eclipse version is 3.5.1 The complied classes have a reference to the .java file. To prove that the problem occurs with the entire deployment I obtained the sources for the deployed application, linked them in my eclipse and set some debug points. I know the flow goes through the line with break points because I used some dirty System.err output to prove this. One thing that may be a hint is that the Tomcat startup log shows the following line: EmbededTomcat: Startup time 45 The thing to note here is that I don't have control over the actual war file deployed in tomcat. I simply get the war from a different department in the company, deploy it, and write some classes that the deployed application will pick up and use. I have studied this Embedded Tomcat a little bit and I don't know if this could be a problem. Has someone experienced anything like this before? If so, I would appreciate it very much if you could shed some (even the dimmest) light onto this. Thanks, Wojtek Kedzior - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: remote debug with tomcat 3.3.2
Hahaha! -Original Message- From: Pid [mailto:p...@pidster.com] Sent: 3. března 2010 0:13 To: Tomcat Users List Subject: Re: remote debug with tomcat 3.3.2 On 02/03/2010 15:28, Kedzior Wojciech wrote: Hi Chuck, Thanks for your answer. That is exactly how I feel. However I'm not the person responsible for these kinds of decisions within the company. I am merely trying to help the guys here by being more (much much more) efficient by using a debugger instead of log files when developing code. To be honest I have no idea why they use such an old version of Tomcat. And I hope RND or someone is looking at upgrading. I also suspect that there are some proprietary libraries involved here, which may hinder a tomcat upgrade. I hate it, but I have to do with what I have and I'm just trying to get the best out of what I have. So, any other suggestions? http://www.monster.fr/ ;o) p Cheers -Original Message- From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] Sent: 2. března 2010 15:16 To: Tomcat Users List Subject: RE: remote debug with tomcat 3.3.2 From: Kedzior Wojciech [mailto:wojciech.kedz...@gemalto.com] Subject: remote debug with tomcat 3.3.2 I'm having a problem with setting up a remote debug session to my Tomcat 3.3.2 Final. You're asking for help with a version of Tomcat that's six years old and hasn't been supported for ages? Not to mention buggier and much slower than the current releases. Your time would be better spent moving up to a supported level and then working on the debugging. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: remote debug with tomcat 3.3.2
I see. Thanks for the input. I think I will try to run the app (as a local experiment only) on tomcat 6 to see what happens. If that fails I may try to recompile 3.3.2. Cheers -Original Message- From: Bill Barker [mailto:billwbar...@verizon.net] Sent: 3. března 2010 4:13 To: users@tomcat.apache.org Subject: Re: remote debug with tomcat 3.3.2 I'm pretty sure that I compiled the binary for 3.3.2 without debugging support. The only thing I can think of is to download the source release of 3.3.2 and compile it with debugging. At the time 3.3.2 was released, using a debugger in Java was so painful that almost nobody did it. Kedzior Wojciech wojciech.kedz...@gemalto.com wrote in message news:a8dd7b2abeb7b842af607d392ff73c7ee4834af...@croexcfwp03.gemalto.com... Hello, I'm having a problem with setting up a remote debug session to my Tomcat 3.3.2 Final. I am copying some classes I developed into the working directory of an application deployed on tomcat. I can connect to the remote debug port from eclipse but the debugger will not stop on any break points what so ever. Here is my environment: I specify the following system variables: JPDA_ADDRESS=8000 JPDA_TRANSPORT=dt_socket I start my Tomcat with the jpda start parameters. While tailing the logs I can see the following line: Listening for transport dt_socket at address: 8000 At this point I can connect to the remote debug port from Eclipse. I can see all the treads running within Tomcat, but my debug will not stop on any breakpoints. Even though the class I am trying to debug was created by me in Eclipse and I have the correct source. The classes were compiled using Java 1.5.0_09. Tomcat also uses the same version of Java. The tomcat is deployed on Linux RedHat 5. Eclipse version is 3.5.1 The complied classes have a reference to the .java file. To prove that the problem occurs with the entire deployment I obtained the sources for the deployed application, linked them in my eclipse and set some debug points. I know the flow goes through the line with break points because I used some dirty System.err output to prove this. One thing that may be a hint is that the Tomcat startup log shows the following line: EmbededTomcat: Startup time 45 The thing to note here is that I don't have control over the actual war file deployed in tomcat. I simply get the war from a different department in the company, deploy it, and write some classes that the deployed application will pick up and use. I have studied this Embedded Tomcat a little bit and I don't know if this could be a problem. Has someone experienced anything like this before? If so, I would appreciate it very much if you could shed some (even the dimmest) light onto this. Thanks, Wojtek Kedzior - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
remote debug with tomcat 3.3.2
Hello, I'm having a problem with setting up a remote debug session to my Tomcat 3.3.2 Final. I am copying some classes I developed into the working directory of an application deployed on tomcat. I can connect to the remote debug port from eclipse but the debugger will not stop on any break points what so ever. Here is my environment: I specify the following system variables: JPDA_ADDRESS=8000 JPDA_TRANSPORT=dt_socket I start my Tomcat with the jpda start parameters. While tailing the logs I can see the following line: Listening for transport dt_socket at address: 8000 At this point I can connect to the remote debug port from Eclipse. I can see all the treads running within Tomcat, but my debug will not stop on any breakpoints. Even though the class I am trying to debug was created by me in Eclipse and I have the correct source. The classes were compiled using Java 1.5.0_09. Tomcat also uses the same version of Java. The tomcat is deployed on Linux RedHat 5. Eclipse version is 3.5.1 The complied classes have a reference to the .java file. To prove that the problem occurs with the entire deployment I obtained the sources for the deployed application, linked them in my eclipse and set some debug points. I know the flow goes through the line with break points because I used some dirty System.err output to prove this. One thing that may be a hint is that the Tomcat startup log shows the following line: EmbededTomcat: Startup time 45 The thing to note here is that I don't have control over the actual war file deployed in tomcat. I simply get the war from a different department in the company, deploy it, and write some classes that the deployed application will pick up and use. I have studied this Embedded Tomcat a little bit and I don't know if this could be a problem. Has someone experienced anything like this before? If so, I would appreciate it very much if you could shed some (even the dimmest) light onto this. Thanks, Wojtek Kedzior
