Thanks for the help. That appeared to fix it. So for future reference if
anyone else is experiencing the same problem. It appears it's not good
enough to have commons-logging.jar in the server/lib or in the
jbossweb-tomcat50.sar. For some reason it needs to be appended onto the
classpath of the
lookup against. The binding that has been
in place since 3.2.1 is "jmx/invoker/RMIAdaptor".
Also, one appears to be supporting this task.
--
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxx
Mike Youngstrom wrote:
> Hello,
>
(Sorry for the possible duplicate post I originally sent
this 24 hours ago and never saw in on the List)
Hello,
I just upgraded to 3.2.2 from 3.2.2RC3 and now my ant target
that deploys my app using the JMX/Invoke task in jbossjmx-ant.jar fails.
The exact same target worked perfect
Hello,
I just upgraded to 3.2.2 from 3.2.2RC3 and now my ant target
that deploys my app using the JMX/Invoke task in jbossjmx-ant.jar fails. The
exact same target worked perfectly in 3.2.2RC3. Any ideas?
See the exception I’m getting below. My target is a
very vanilla deploy base
--
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Friday, October 10, 2003 3:03 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Quick JDBC question.
You haven't closed your resultset...
Harm.
"Mike Youngstrom" <[EMAIL PROTECTED]>
S
addup?");
}
}
-Original
Message-----
From: Mike Youngstrom
[mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2003
5:35 PM
To:
[EMAIL PROTECTED]
Subject: RE: [JBoss-user] Quick
JDBC question.
Let me add a little more
information.
Version: JBoss 3.2.2 RC3
DBServer Mysql 4.0.
Let me add a little more information.
Version: JBoss 3.2.2 RC3
DBServer Mysql 4.0.15 Windows
JDBCDriver: Connector/J 3.0.8
Mike
-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mike Youngstrom
Sent: Thursday, October 09, 2003
10:38 AM
I’m
fairly new to JDBC development and JBoss. I have the following code in a
stateless session bean.
try
{
boolean
exists;
prepStmt = conn.prepareStatement(USERNAME_EXISTS);
prepStmt.setString(1, username);