Thanks Scott. I think I'll leave it chalked up to the JDK bug for now.
Rgds,
Dan.
--
Danny Yates
-Original Message-
From: Scott M Stark [mailto:[EMAIL PROTECTED]
Sent: 15 July 2003 05:44
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Error debugging 3.2.0
I'm going to have
Hi all,
I'm debugging my code using the following:
JBoss 3.2.0
Eclipse 2.1.1
JBoss IDE 1.1.0
Every 10 seconds, I get the following console output:
14:54:35,603 INFO [DLQHandler] Destroying
14:54:35,603 INFO [DLQHandler] Destroyed
14:54:35,613 INFO [DLQHandler] Creating
14:54:35,613 ERROR
What does the JNDI namespace show in terms of bound jms factories? What does the
jms invocation layer service associated with XAConnectionFactory show in terms
of starting up?
--
Scott Stark
Chief Technology Officer
JBoss Group, LLC
[EMAIL
Yates
-Original Message-
From: Scott M Stark [mailto:[EMAIL PROTECTED]
Sent: 14 July 2003 15:56
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Error debugging 3.2.0
What does the JNDI namespace show in terms of bound jms factories? What does
the
jms invocation layer service associated
a debug.
Rgds,
Dan.
--
Danny Yates
-Original Message-
From: Scott M Stark [mailto:[EMAIL PROTECTED]
Sent: 14 July 2003 15:56
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Error debugging 3.2.0
What does the JNDI namespace show in terms of bound jms factories? What does
the
jms
-Original Message-
From: Scott M Stark [mailto:[EMAIL PROTECTED]
Sent: 14 July 2003 15:56
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Error debugging 3.2.0
What does the JNDI namespace show in terms of bound jms factories? What does
the
jms invocation layer service associated
Then the likely problem is that the ObjectFactory for the java: namespace, which
is implemented as a singleton via a static class variable is not working in your
debug environment because the class is being loaded through another class loader
and thus creating a seperate java: namespace that
I'm going to have to see a trace log of the class loading layer when this occurs
to try to see where this is coming from. It could be this JDK bug showing up
since java.lang.NumberFormatException cannot be causing cicularity problem:
