[jboss-jira] [JBoss JIRA] Closed: (JBAS-6005) Jboss as cmp Dynamic QL

[ https://jira.jboss.org/jira/browse/JBAS-6005?page=com.atlassian.jira.plug... ] Adrian Brock closed JBAS-6005. ------------------------------ Fix Version/s: (was: JBossAS-4.2.3.GA) Resolution: Incomplete Description Assignee: (was: Alexey Loubyansky) When you posted this bug report you were asked to read this: http://wiki.jboss.org/wiki/HelpBugReport Since 4.2.3 has already been released there's little point making the "fix for" that version. Which release it gets fixed in (assuming a fix is required) is not your decision anyway which is why it says "FOR DEVELOPERS USE ONLY". It is mainly because of this corruption of 4.2.3's release's notes that I'm even responding this bug report. This bug report falls into the "Quality" failure of the above link. Ask yourself, is there enough information to answer the question in the forum? e.g. How is businessObjectID defined in the java entity bean class and the deployment descriptors (DONT ANSWER THAT QUESTION HERE, BUG REPORTS ARE NOT FOR HELP) Basically your forum post has been ignored because it is unanswerable. Making it a bug report to try to get attention won't change that failing. What it will get is a LART like this one. Some bonus and very quick analysis to show this is unlikely to be a JBoss problem. 1) If you type the location of the error into google "mysql getInt ResultSetImpl.java blob" your's is the only problem that appears (notice I didn't restrict the search to JBoss) This points to something specific in your usage, most likely a config problem or something broken in your deployment (e.g. something specific about the data like it is corrupted in the database). 2) If I search "mysql bug getInt blob" you'll I see the mysql driver has had problems in this area in the past http://bugs.mysql.com/bug.php?id=1576 including a regression where the bug fix got lost between versions: http://bugs.mysql.com/bug.php?id=2916 Feel free to re-open this bug report if you have a reproducable testcase or at least enough information on how to create one (this includes all relevant information such as backend mysql server version, operating system, etc. that you were asked to provide in the above link) Often the construction of such a simplified test (from scratch) reveals the typo, etc. that is the real cause of the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira