Thanks for the additional information Florin,
We will proceed with the investigation and try to fix the problem ASAP if
any.
Best regards,
Eugene Zhuravlev
IntelliJ Software, http://www.intellij.com/
"Develop with pleasure!"
----- Original Message -----
From: "Florin Manolache" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 23, 2002 21:01
Subject: [Eap-list] Debugging problem [bug]
>
> Hi Eugene,
>
>
> No exceptions or any message in the console window;
> I can stop the debug session and start another, in fact, I can continue
the
> debug session (but i am in a wrong class as i said, usually Class.java or
> another boot class like ClassLoader or Sting and i am at a wrong level in
> the execution stack). When i first press F7, the debugger hangs for a long
> period of time until it stops in a wrong class;
> My project is an j2ee application server (in my case is the j2ee-ri, but a
> friend of mine is having the same kind of problems trying to debug jboss)
so
> it uses a lot of RMI and custom class-loaders (in my case the problem
seems
> to be related with a Class.forName("ClassName") see below).
>
>
> More details about my particular case:
> I have a method run in the main class of the project, something like (see
> comments inline after the '// >>>'):
>
>
> private void run(String[] args, boolean verbose, boolean singleVM,
boolean
> startJMS) {
> EJBServer svr = null; // >>> here I set the breakpoint and I start
> pressing F8
> try {
> (new java.security.SecureRandom()).nextLong(); // >>> F7 bug here
>
> // Load default properties
> defaultProperties =
> Utility.getPropertiesFromFile(Utility.J2EE_DEFAULT_CONFIGURATION_FILE); //
> >>> F7 bug here
>
> // Initialize System properties
> Properties props = System.getProperties(); // >>> F7 bug here
>
> // Set EJBServer.EJB_ACTIVATIONDB_DIR property
> String repname = "repository"; // >>> F7 bug here !!!
> try {
> // Dont use ServerConfiguration here because ORB not set up yet
> Configuration config = new ConfigurationImpl(); // >>> F7 bug here
> repname = config.getProperty(REPOSITORY_DIRECTORY); // >>> F7 bug here
> } catch(Exception ex) {
> }
> String activationDir = repname + File.separator +
Utility.getLocalHost();
> props.put(EJBServer.EJB_ACTIVATIONDB_DIR,
> FileUtil.getAbsolutePath(activationDir));
>
> if(singleVM) {
> // set server-id and server-port so that persistent objects
> // in J2EEServer will be reachable after crashes.
> System.out.println("single JVM"); // me
> String serverId = (new Integer(J2EE_SERVERID)).toString();
> props.setProperty(EJBServer.EJB_SERVER_ID, serverId);
> props.setProperty(EJBServer.EJB_APPNAME, "j2ee");
> }
>
>
>
> In my case it seems that the debugger always cannot pass through the
> execution of a Class.forName("SomeClass") and it always stops on the
> following line (regardless of the line where I press F7):
> Class.java
> public static Class forName(String className)
> throws ClassNotFoundException {
> return forName0(className, true,
> ClassLoader.getCallerClassLoader()); // >>> here i find the cursor after
F7
> anyway in the run method
> }
>
>
> I can continue the debug session (with a Step out Shift+F8) and now the
> cursor is in my project somewhere in:
> ResourceInstaller.java
> public static void registerJDBCDrivers(Set jdbcDrivers) {
>
> for(Iterator iter = jdbcDrivers.iterator(); iter.hasNext();) {
> JdbcDriver next = (JdbcDriver) iter.next();
> String classname = next.getName();
>
> try {
> Class.forName(classname).newInstance(); // >>> here is the cursor now
> } catch(Exception cnf) {
> try {
> // This is a JDK1.2 API
> Class c = ClassLoader.getSystemClassLoader().loadClass(classname);
> try {
> Object d = c.newInstance();
> } catch(Exception ex) {
> }
> } catch(java.lang.ClassNotFoundException ex) {
> Log.err.println(localStrings.getLocalString("poolmgr.loaderror",
> "Cannot load class " + classname, new Object[]{classname}));
> }
> }
> }
> }
>
> I hope this can help.
>
> Best regards,
> Florin
>
>
>
>
> >Hi Florin,
> >
> >Are there any exceptions in the console? Are you able to terminate this
and
> >start another debug session, or debugger stops responding and you have to
> >restart IDEA? We had similar reports from JBoss users but unfortunately
> this
> >behaviour is hardly reproducible (we did not manage to recreate it).
Could
> >the problem have something to do with the specifics of your application?
> >
> >Best regards,
> >Eugene Zhuravlev
> >IntelliJ Software, http://www.intellij.com/
> >"Develop with pleasure!"
> >
> >----- Original Message -----
> >From: "Florin Manolache" <[EMAIL PROTECTED]>
> >To: <[EMAIL PROTECTED]>
> >Sent: 23 January, 2002 10:27 AM
> >Subject: [Eap-list] Debugging problem [bug]
> >
> >
> >>
> >> Hi all,
> >>
> >> When debugging big projects, after a few F8 (step over), if you press
F7
> >> (step into) after a while the debugger stops somewhere in the Class or
> >> ClassLoader (in the project properties the checkbox for not stepping
into
> >> the boot classes is checked so it should not reach Class or
ClassLoader;
> >> also this behavior does not depend on the transport used for debugging:
> >> socket or shared memory).
> >> The bug appeared on 2 different machines (both win2k boxes, one with
sun
> jdk
> >> 1.3.1_02 and the other with 1.3.1_01, all recent idea builds) one
> debugging
> >> jboss project and the other with j2ee-ri.
> >> Anyone saw something similar ?
> >>
> >> Regards,
> >> Florin
> >>
> >>
> >>
> >> _______________________________________________
> >> Eap-list mailing list
> >> [EMAIL PROTECTED]
> >> http://www.intellij.com/mailman/listinfo/eap-list
>
>
>
>
> _______________________________________________
> Eap-list mailing list
> [EMAIL PROTECTED]
> http://www.intellij.com/mailman/listinfo/eap-list
_______________________________________________
Eap-list mailing list
[EMAIL PROTECTED]
http://www.intellij.com/mailman/listinfo/eap-list
