[ http://jira.jboss.com/jira/browse/JBESB-1435?page=all ] Martin Vecera updated JBESB-1435: --------------------------------- Attachment: server.oracle10g.log.gz How about Oracle10g? Search for ORA-01461 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1435?page=comments#action_12394337 ] Len DiMaggio commented on JBESB-1435: ------------------------------------- Is this a hibernate restriction? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1435?page=comments#action_12394475 ] Kevin Conner commented on JBESB-1435: ------------------------------------- This is obviously an issue within jBPM, whether this is hibernate or scripts. We need to get someone from that team to look into this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1435?page=comments#action_12394481 ] Tom Baeyens commented on JBESB-1435: ------------------------------------ to get the best possible db portability, we have to take into account all the restrictions of all the databases. we sometimes end up with these kinds of low values in the default configuration because we want to have the default schema generation to work on as many db's as possible out of the box. therefor it is usually desirable to optimize the default db schema that comes out of the generation for perticular dbs. we currently expect the users to do this themselves, since we don't have the manpower to maintain individual schema tweaks for all the dbs. i have used 2 lengths for strings in the schema generation. the default (255) and i have explicitely set it to 4000 for columns where longer texts can be expected. i think it might be opportune to update the length of the string variable column to 4000 as well. the motivation to limit the number of columns with length 4000 is that for some dbs (db2?) the default schema generation results fixed length disc space that is reserved for columns, resulting in huge row sizes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1435?page=comments#action_12394486 ] Jiri Pechanec commented on JBESB-1435: -------------------------------------- 1) The problem is that 255 chars length is set on ESB sql create scripts 2) The second problem is that for us/customer it means that we cannot pass message with arbitary length to jBPM So as I see it we should 1) Modify the SQL scripts so it will allow maximum string length for each database 2) Document the limitation about message length 3) Educate customer that if he requires to process long messages then he should - either use message store and pass only UUID to it between services - use ByteArray approach and pass message as byte array -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1435?page=comments#action_12394492 ] Tom Baeyens commented on JBESB-1435: ------------------------------------ i can't currently test the buld cause our build is broken by a name change in the eap file. it takes me too long to fix that now. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1435?page=all ] Kurt Stam closed JBESB-1435. ---------------------------- Resolution: Done Documented the issue as a Known jBPM issue in the jBPMIntegrationGuide. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1435?page=all ] Kevin Conner reopened JBESB-1435: --------------------------------- The jBPM issue has now been fixed. I'll pull the configs and update them but the changes to the docs will need to be reverted. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1435?page=all ] Kurt Stam closed JBESB-1435. ---------------------------- Resolution: Done OK I have removed it from the docs. I hope jBPM did also update their DDL files, since we simply pull from them with every jBPM release, and this would undo changes on our side. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira