Mark, [See my comments below in brackets]
-----Original Message----- From: Mark Phelps [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 16, 2002 2:09 PM To: JRun-Talk Subject: RE: debugging Jrun 3.0 with JBuilder 4.0EE I was the one who wrote the article you mention. I see exactly the same problem when I debug. I'm not sure why it happens and I have never spent enough time to see if there is a better way of doing things. Even when the debugging works, I usually find it so slow to load that I can't stand to use it. [ I noted this issue too, I have about 32 ejb and when JBuilder try to start up server in debugging mode. It's take a long time for this task ] There may very well be a better configuration that will give you what you want but I have not found it yet. [ I'm concerned to hear this. ] Our solution at my current assignment has been to create a flexible logging API that allows us to monitor everything that happens inside the application. It is not as nice as a propper debugger for finding bugs but it is great for monitoring the application and providing automated responses to problems that occur. For example, we can specify that certain types of errors or exceptions will trigger emails to the system administrator. [ It's a god work around to perform debbugging if you have enough time to build and API. I think other way to show any exception or message is to start up jrun from a command prompt and not like a service. But I try to start from a command line, but jrun.exe is a windows app and It performs like an windows app and not like a java console. If you or someone else know how to start the server like a java console it would be nice to hear about that. I think this is the way that a server have to operate. Remember that if you don't provide what a customer need someonelse will. ] [ Thanks for your time and help, Paul S. ] -----Original Message----- From: Paul Sanchez [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 16, 2002 11:27 AM To: JRun-Talk Subject: debugging Jrun 3.0 with JBuilder 4.0EE All, I'm trying to debug my code in Jrun 3.0 sp2 using JBuilder EE 4.0. Doing this, I follow the instructions in http://www.macromedia.com/v1/handlers/index.cfm?ID=20830 <http://www.macromedia.com/v1/handlers/index.cfm?ID=20830&Method=Full> &Method=Full and it works but... I noted that after I performed a "step into" or "step over" operation in my code the connection between IDE and the server is loosed. Even after use a "-debug" option for the server in this way: -start c:/Allaire/JRun/servers/default jrun.rootDir=c:/Allaire/JRun -debug connection is loosed. So I have to restart the server again and again :(. So, I need to know if there is some tricky in order to mainting the debugging session. I found a work around to debugg but is too tedious: I have to set many break points and perform the trace jumping between each break point using "resume program (F9)" operation and in this way CONNECTION IS NOT LOOSED. Is really hard to debug in this way. Any help will be really appreciate it Regards, Paul Sanchez Software Engineer Objeq [EMAIL PROTECTED] Tel: (593)-2-2268349 x 518 Objeq: "We help you deliver high quality, on time, cost effective software" Visit http://www.objeq.com <http://www.objeq.com/> to find free resources, information and tips on how to deliver successful software projects ______________________________________________________________________ Macromedia ColdFusion 5 Training from the Source Step by Step ColdFusion http://www.amazon.com/exec/obidos/ASIN/0201758474/houseoffusion Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
