OK well for what it's worth I have:
PII 350 256MB
NT 4 Workstation Service Pack 5
JBuilder 3.0 Professional (all patches I know of applied)
Standard Jonas 1.6.1
Sybase ASE 11.9.2 running remotely on Solaris box
Sybase jConnect 5.2 JDBC driver
When I debug my EJBs/Jonas I use the built-in JBuilder VM (1.2), rather
than a 3rd party one. When I run Jonas not under the debugger I use
Hotspot.
Maybe I do just lead a charmed life! (a reassuring thought!) It's kind of
frustrating to hear people agonizing over something I regard as easy and
not a problem.
Joe
-----Original Message-----
From: Halas, Miroslav [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, June 29, 2000 5:45 PM
To: 'Joe Gittings'; '[EMAIL PROTECTED]'
Subject: RE: Question on debugging
Well 8-).
We are running on 10-12 PII 300 with anything from 128 to 256MB of memory
under Windows NT 4.0 Service Pack 5 both Workstation and Server. We are
using both JBuilder 3.0 Professional and Enterprise with all the latest
patches available from Borland and lately JBuilder 3.5 Foundation for
development.
I am not sure what is non standard (how do you define standard 8-) on
combination of Jetty and Jonas. We have made the decision to merge them and
run in one JVM (exactly what Enhydra and Jonas) are doing for speed and
footprint purposes. Source codes for both are available, we went through
them to make sure there are no conflicts and troubles. And we are running
it
successfuly for last 6 months in development and 3-4 months in production
environment without any problems handling day to day work of 10-12 people
on
PII 300 with 256MB of memory on WinNT 4.0 Server together with Interbase
5.6
Server.
Oh, except we cannot debug under JBuilder 8-). But we would appreciate any
help if you know how to resolve it.
Miro Halas
P.S. We haven't tried JBuilder 3.5 for debugging so cannot tell.
-----Original Message-----
From: Joe Gittings [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 29, 2000 11:33 AM
To: '[EMAIL PROTECTED]'
Cc: 'Halas, Miroslav'
Subject: RE: Question on debugging
I am having trouble recognizing the planet from which these posts
originate.
I am using JBuilder 3.0 to debug my EJBs with Jonas 1.6.1, it hardly ever
GPFs (maybe 1 in 30 times), and I only have a lowly PII 350 with 256mb of
RAM. Oh yeah, *and* I'm running all the Jini *and* JavaSpaces services at
the same time!
The bottom line is, as far as I'm concerned there is absolutely NO PROBLEM
with debugging EJBs running in Jonas under JBuilder, or for that matter any
other IDE as the technique I described should work for all of them.
Is it possible that the GPFing Halas is experiencing is due to the
non-standard combination of Jonas and Jetty?
I repeat, for me this is a *total* non-problem, and I simply can't
understand how it's vexing others so much! Maybe I just live a charmed
life? (I don't think so somehow lol).
Joe
-----Original Message-----
From: Halas, Miroslav [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, June 29, 2000 5:15 PM
To: 'Mark Williams'; [EMAIL PROTECTED]
Subject: RE: Question on debugging
We were doing debugging using JBuilder 3.0. We have our own launcher which
launces Jonas 2.0, and Jetty 2.3.4 which represents our J2EE-like platform
(advantage is small footprint). We setup our launcher as the starting
execution point and set breakpoints in the beans. Once the beans get
invoked, JBuilder pops up at the correct place. Where is the catch?
JBuilder
is not stable, and GPFs 9 from 10 times. The other problems is that the
memory and speed requirements are horrible (machine with 256 MB is not
enough, 100 for JBuilder, 128 for our server and the machine is swapping
all
the time). So what are we doing. Like everybody else using
System.out.println(), our own assert and our own loging.
Miro Halas
-----Original Message-----
From: Mark Williams [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 29, 2000 11:06 AM
To: [EMAIL PROTECTED]
Subject: RE: Question on debugging
Having just come from JavaOne, I can tell you that just about everyone is
doing the same. At our shop, we have looked at MANY debugging tools, and
have found very few that actually work for EJB debugging (remote
debugging).
The one combination we found that did work was Visual Cafe on the WebLogic
application server. The only reason we made this work is that we had
engineers from BEA show us how to do it and help us set it up (it was quite
a trick).
We had been using println() exclusively before that, and had written our
own
sort of println-based debugging tool. We took println statements and wrote
them to a GUI window on the server. We had some methods that prompted (via
a
dialog) for input and our code could respond accordinlgy. We also had some
assert methods, etc. It was just a slightly fancier println().
The bottom line is that if you do find a way to remotely debug an EJB in
Jonas, let us all know!!!
-----Original Message-----
maybe this is off topic, but I would like to know how experienced
EJB-developers handle debugging of EJBs.
All I see in my debugger are the remote stubs, which are of no help.
Currently I am debugging as my father did in the 70s,
by using System.out.println().
Any suggestions ?
Nikolaus
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
