February 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2409) ftp-message-filter: add support for the 'post-rename' attribute

by Daniel Bevenius (JIRA)

ftp-message-filter: add support for the 'post-rename' attribute --------------------------------------------------------------- Key: JBESB-2409 URL: https://jira.jboss.org/jira/browse/JBESB-2409 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 4.4 FP1 The ftp-message-filter should support the 'post-rename' attribute like the fs-message-filter does. -- 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

17 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2426) Merge JBESB-2177 : Create a proper mechanism for handling schema evolutions

by Tom Fennelly (JIRA)

Merge JBESB-2177 : Create a proper mechanism for handling schema evolutions --------------------------------------------------------------------------- Key: JBESB-2426 URL: https://jira.jboss.org/jira/browse/JBESB-2426 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.4 Reporter: Tom Fennelly Assignee: Kevin Conner Priority: Blocker Fix For: 4.5 We need to create a proper mechanism for handling different schema mechanisms. The current schema has evolved through a number of revisions without updating the version, this is generally a bad practice. We should base the 1.0.1 version of the schema on the SOA 4.3 GA version with any subsequent changes requiring an update to the version/namespace. -- 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

17 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-1936) Create a contract publisher to handle remote WS endpoints

by Kevin Conner (JIRA)

Create a contract publisher to handle remote WS endpoints --------------------------------------------------------- Key: JBESB-1936 URL: https://jira.jboss.org/jira/browse/JBESB-1936 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 Reporter: Kevin Conner Fix For: 4.5 We have a contract publisher that exposes wsdl for a co-located JBoss WS endpoint, WebserviceContractPublisher. We should have an equivalent that can be used to expose the wsdl of remote services through the ESB. -- 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

17 years, 2 months

3
9
0 / 0

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

by Lukas Petrovicky (JIRA)

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) Affects Versions: 4.4 Reporter: Lukas Petrovicky 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... 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

17 years, 2 months

5
9
0 / 0

[JBoss JIRA] Created: (JBESB-2358) Change the default value of ExistsSql

by Taro Yasuma (JIRA)

Change the default value of ExistsSql ------------------------------------- Key: JBESB-2358 URL: https://jira.jboss.org/jira/browse/JBESB-2358 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.4 Reporter: Taro Yasuma Please change the default value of ExistsSql to gain performance to initialize DatabaseInitializer. The current jbossesb.esb/jbossesb-service.xml is like: <server> <mbean code="org.jboss.internal.soa.esb.dependencies.DatabaseInitializer" name="jboss.esb:service=MessageStoreDatabaseInitializer"> ... <attribute name="ExistsSql">select * from message</attribute> ... </mbean> </server> But it should be "select count(*) from message". -- 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

17 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-2418) Support querying of process instance variables

by Daniel Bevenius (JIRA)

Support querying of process instance variables ---------------------------------------------- Key: JBESB-2418 URL: https://jira.jboss.org/jira/browse/JBESB-2418 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Process flow Reporter: Daniel Bevenius Fix For: 4.4 FP1 -- 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

17 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2419) XStreamToObject. Add support for implicit collections and field alias

by Daniel Bevenius (JIRA)

XStreamToObject. Add support for implicit collections and field alias --------------------------------------------------------------------- Key: JBESB-2419 URL: https://jira.jboss.org/jira/browse/JBESB-2419 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 4.4 FP1 -- 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

17 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2424) Database maintenance scripts

by Len DiMaggio (JIRA)

Database maintenance scripts ---------------------------- Key: JBESB-2424 URL: https://jira.jboss.org/jira/browse/JBESB-2424 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.5 Reporter: Len DiMaggio Project JIRA for SOA-P platform JIRA: https://jira.jboss.org/jira/browse/SOA-310 -- 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

17 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-2417) Allow jBPM process instance creation commands to return the created process instance id

by Daniel Bevenius (JIRA)

Allow jBPM process instance creation commands to return the created process instance id --------------------------------------------------------------------------------------- Key: JBESB-2417 URL: https://jira.jboss.org/jira/browse/JBESB-2417 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Process flow Reporter: Daniel Bevenius Fix For: 4.4 FP1 -- 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

17 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2421) Upgrade groovy from 1.0 to 1.5.0

by Daniel Bevenius (JIRA)

Upgrade groovy from 1.0 to 1.5.0 -------------------------------- Key: JBESB-2421 URL: https://jira.jboss.org/jira/browse/JBESB-2421 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Scripting Reporter: Daniel Bevenius Fix For: 4.4 FP1 -- 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

17 years, 2 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues February 2009