[31 May 1:11pm] Mark Matthews
This is a known issue which was solved in 3.0.14 which was posted the same day
as the release of 3.0.13
BTW, in review of dozens of responses in THIS forum, I'd say I'm not the one with the
attitude problem...Look at your responses to users who are just asking
You missed the adjectives repeated and incomplete.
Read READ THIS FIRST or the FAQ in the JBossMQ forum if you are
in any doubt about my attitude towards lazy users.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3837009#3837009
Reply to the post :
Uhh, well, what I want to know is whether there is a bug in Connector/J 3.0.13 or is
there another NEW feature in jboss 3.2.4FC2 that causes the connections to
fail??
With Connector/J 3.0.13 I get a connection errors...If I stop the server, and replace
it with 3.0.11 everything works
I think from the error message (it is hard to tell since you don't post the full
stacktrace)
that the mysql driver is trying to parse localhost as a number.
So either:
1) you have the url wrong
2) it is a bug in their driver
View the original post :
1). I doubt it.
2). Possibly. I have submitted a bug to Mark Mathews at mysql.org
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3836833#3836833
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3836833
I had the same problem. Mark released 3.0.14 yesterday and the problem
was solved. (See the change log).
Jack
tbauer wrote:
Uhh, well, what I want to know is whether there is a bug in Connector/J 3.0.13 or is there
another NEW feature in jboss 3.2.4FC2 that causes the connections to
Here's some more detailed informationHopefully someone can actually look into the
code rather than just post terse(snippy) comments:
Here's my datasource configuration: works with Connector/J 3.0.11
local-tx-datasource
jndi-nameICSRegDS/jndi-name
If you post terse/snippy/incomplete questions you get terse/snippy/incomplete
answers.
http://www.jboss.org/wiki/Wiki.jsp?page=JBossForums
Yes, the problem is in the mysql driver:
Caused by: java.sql.SQLException: Cannot load connection class because of underlying
exception:
