[JBoss JIRA] Created: (JBPM-2049) hbm2ddl.auto doesn't work within AS
by Heiko Braun (JIRA)
hbm2ddl.auto doesn't work within AS
-----------------------------------
Key: JBPM-2049
URL: https://jira.jboss.org/jira/browse/JBPM-2049
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Core Engine
Reporter: Heiko Braun
Assignee: Heiko Braun
Fix For: jBPM 4.0.0 Alpha2
The enterprise tests fail against hypersonic because the tables cannot generated:
2009-02-18 20:53:38,181 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (http-127.0.0.1-8080-1) Running hbm2ddl schema expo
rt
2009-02-18 20:53:38,213 DEBUG [org.hibernate.tool.hbm2ddl.SchemaExport] (http-127.0.0.1-8080-1) import file not found: /imp
ort.sql
2009-02-18 20:53:38,213 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (http-127.0.0.1-8080-1) exporting generated schema
to database
2009-02-18 20:53:38,215 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (http-127.0.0.1-8080-1) schema export unsuccessful
java.sql.SQLException: You cannot set autocommit during a managed transaction!
at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.setJdbcAutoCommit(BaseWrapperManagedConnection.java
:598)
at org.jboss.resource.adapter.jdbc.WrappedConnection.setAutoCommit(WrappedConnection.java:458)
at org.hibernate.tool.hbm2ddl.SuppliedConnectionProviderConnectionHelper.prepare(SuppliedConnectionProviderConnecti
onHelper.java:60)
at org.hibernate.tool.hbm2ddl.SchemaExport.execute(SchemaExport.java:252)
at org.hibernate.tool.hbm2ddl.SchemaExport.create(SchemaExport.java:211)
at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:343)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1327)
--
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
15 years, 10 months
[JBoss JIRA] Commented: (JBPM-2057) Do not truncate long messages/exceptions
by Thomas Diesler (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-2057?page=com.atlassian.jira.plug... ]
Thomas Diesler commented on JBPM-2057:
--------------------------------------
These are the columns that have string length 4000
[tdiesler@tddell resources]$ find . -name "*.xml" | xargs grep "type=\"string\" length=\"4000\""
./org/jbpm/logging/log/MessageLog.hbm.xml: <property name="message" column="MESSAGE_" type="string" length="4000"/>
./org/jbpm/instantiation/Delegation.hbm.xml: <property name="className" column="CLASSNAME_" type="string" length="4000" />
./org/jbpm/instantiation/Delegation.hbm.xml: <property name="configuration" column="CONFIGURATION_" type="string" length="4000" />
./org/jbpm/graph/action/Script.hbm.xml: <property name="expression" column="EXPRESSION_" type="string" length="4000" />
./org/jbpm/graph/exe/Comment.hbm.xml: <property name="message" column="MESSAGE_" type="string" length="4000"/>
./org/jbpm/graph/def/Node.hbm.xml: <property name="description" column="DESCRIPTION_" type="string" length="4000"/>
./org/jbpm/graph/def/ExceptionHandler.hbm.xml: <property name="exceptionClassName" column="EXCEPTIONCLASSNAME_" type="string" length="4000" />
./org/jbpm/graph/def/ProcessDefinition.hbm.xml: <property name="description" column="DESCRIPTION_" type="string" length="4000"/>
./org/jbpm/graph/def/Transition.hbm.xml: <property name="description" column="DESCRIPTION_" type="string" length="4000"/>
./org/jbpm/graph/log/ActionLog.hbm.xml: <property name="exception" column="EXCEPTION_" type="string" length="4000"/>
./org/jbpm/job/Job.hbm.xml: <property name="exception" column="EXCEPTION_" type="string" length="4000"/>
./org/jbpm/module/def/ModuleDefinition.hbm.xml: <property name="name" column="NAME_" type="string" length="4000"/>
./org/jbpm/taskmgmt/exe/TaskInstance.hbm.xml: <property name="description" column="DESCRIPTION_" type="string" length="4000"/>
./org/jbpm/taskmgmt/def/Task.hbm.xml: <property name="description" column="DESCRIPTION_" type="string" length="4000"/>
./org/jbpm/context/exe/variableinstance/StringInstance.hbm.xml: <property name="value" column="STRINGVALUE_" type="string" length="4000"/>
./org/jbpm/context/log/variableinstance/StringUpdateLog.hbm.xml: <property name="oldValue" column="OLDSTRINGVALUE_" type="string" length="4000"/>
./org/jbpm/context/log/variableinstance/StringUpdateLog.hbm.xml: <property name="newValue" column="NEWSTRINGVALUE_" type="string" length="4000"/>
> Do not truncate long messages/exceptions
> ----------------------------------------
>
> Key: JBPM-2057
> URL: https://jira.jboss.org/jira/browse/JBPM-2057
> Project: JBoss jBPM
> Issue Type: Bug
> Components: Productization
> Environment: Sybase/DB2
> Reporter: Ryan Campbell
> Assignee: Alejandro Guizar
> Fix For: jBPM-3.2.5.SP2
>
>
> For sybase, a "text" column should be used instead of the current varchar(4000)
> This will prevent the truncation of stack traces.
> Do to data migration issues we cannot change the mapping of existing db columns. Instead the issue should be resolved by adding additional "text" columns.
--
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
15 years, 10 months