[esb-issues] [JBoss JIRA] Commented: (JBESB-2127) Text supplied to the TEXTVALUE field of JMXDATA table too long

[Darrin Mison (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBESB-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12453034#action_12453034 ] 

Darrin Mison commented on JBESB-2127:
-------------------------------------

I notice that the corresponding column in the HSQLDB create_database.sql has the datatype of varchar(255)

> Text supplied to the TEXTVALUE field of JMXDATA table too long
> --------------------------------------------------------------
>
>                 Key: JBESB-2127
>                 URL: https://jira.jboss.org/jira/browse/JBESB-2127
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Management
>    Affects Versions: 4.4
>            Reporter: Lukas Petrovicky
>            Assignee: Tom Cunningham
>             Fix For: 4.4 CP2
>
>
> When running the SOA-P 4.3 testsuite on Oracle, one of the tests (Notifiers QS) found the following problem:
> 2008-10-17 04:20:07,500 WARN  [org.hibernate.util.JDBCExceptionReporter] SQL Error: 12899, SQLState: 72000
> 2008-10-17 04:20:07,500 ERROR [org.hibernate.util.JDBCExceptionReporter] ORA-12899: value too large for column "SOAQRHEL4"."JMXDATA"."TEXTVALUE" (actual: 2041, maximum: 2000)
> 2008-10-17 04:20:07,500 WARN  [org.hibernate.util.JDBCExceptionReporter] SQL Error: 12899, SQLState: 72000
> 2008-10-17 04:20:07,500 ERROR [org.hibernate.util.JDBCExceptionReporter] ORA-12899: value too large for column "SOAQRHEL4"."JMXDATA"."TEXTVALUE" (actual: 2041, maximum: 2000)
> 2008-10-17 04:20:07,501 ERROR [org.hibernate.event.def.AbstractFlushingEventListener] Could not synchronize database state with session
> org.hibernate.exception.GenericJDBCException: Could not execute JDBC batch update
> 	at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103)
> 	at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91)
> 	at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
> 	at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:254)
> 	at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:237)
> 	at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:141)
> 	at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298)
> 	at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27)
> 	at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000)
> 	at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338)
> 	at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106)
> 	at org.jboss.soa.esb.monitoring.server.DataFiler.insertStatistics(DataFiler.java:194)
> 	at org.jboss.soa.esb.monitoring.server.DataFiler.persistData(DataFiler.java:230)
> 	at org.jboss.soa.esb.monitoring.server.FilerAction.fileMessage(FilerAction.java:70)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102)
> 	at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74)
> 	at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:520)
> 	at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:392)
> 	at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:538)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> 	at java.lang.Thread.run(Thread.java:595)
> Caused by: java.sql.BatchUpdateException: ORA-12899: value too large for column "SOAQRHEL4"."JMXDATA"."TEXTVALUE" (actual: 2041, maximum: 2000)
> 	at oracle.jdbc.driver.DatabaseError.throwBatchUpdateException(DatabaseError.java:343)
> 	at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:10698)
> 	at org.jboss.resource.adapter.jdbc.WrappedStatement.executeBatch(WrappedStatement.java:620)
> 	at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:48)
> 	at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:247)
> 	... 22 more
> Further information can be found in the server log of that build:
> http://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-it-db-jdk15/35/DATABASE=oracle10g,jdk=java15,label=RHEL4_x86/artifact/jbosssoa/jboss-as/server/oracle/log/server.log
> This issue seems to be related to JBESB-1348, if not the same. It doesn't happen anywhere else but Oracle.

-- 
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