June 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2639) Extend DatabaseInitializer comment support

by Kevin Conner (JIRA)

Extend DatabaseInitializer comment support ------------------------------------------ Key: JBESB-2639 URL: https://jira.jboss.org/jira/browse/JBESB-2639 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.4 CP2 Reporter: Kevin Conner Fix For: 4.4 CP3 To include lines starting with # and /* */. -- 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

16 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2637) Upgrade jBPM to 3.2.5SP5

by Kevin Conner (JIRA)

Upgrade jBPM to 3.2.5SP5 ------------------------ Key: JBESB-2637 URL: https://jira.jboss.org/jira/browse/JBESB-2637 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.4 CP2 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP3 -- 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

16 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2573) SOAPProcessor Programmer Guide Documentation

by Stelios Koussouris (JIRA)

SOAPProcessor Programmer Guide Documentation -------------------------------------------- Key: JBESB-2573 URL: https://jira.jboss.org/jira/browse/JBESB-2573 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Stelios Koussouris Priority: Minor The example in the following section is meant to refer to SOAPProcessor but it has a different example. Some additional info on the paramters to pass in might also come handy 11.7. Webservices/SOAP Action Configuration The <action ... /> configuration for this action is very straightforward. The action requires only one mandatory property value, which is the "jbossws-endpoint" property. This property names the JBossWS endpoint that the SOAPProcessor is exposing (invoking). <action name="PrintAMessage" class="test.PrintMessage"> <property name="information" value="Hello World!" /> <property name="repeatCount" value="5" /> </action> -- 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

16 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-2644) Suggested Rewording in ESB Programmers' Guide

by David Le Sage (JIRA)

Suggested Rewording in ESB Programmers' Guide --------------------------------------------- Key: JBESB-2644 URL: https://jira.jboss.org/jira/browse/JBESB-2644 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Environment: JBoss ESB Trunk Documentation Reporter: David Le Sage I have rewritten the following section from the ESB Programmers' Guide for inclusion in the SOA Platform Documentation. Can someone please check this for technical accuracy? Request that the ESB docs please be updated with this content as well. http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/docs/Prog... Revision: 26877 Chapter: Building and Using Services. Page 41. The subsection "Transactions" currently reads: ****** Some Couriers support transactional delivery semantics, e.g., InVM and JMS. The current delivery semantics for such Couriers is based on JMS transacted sessions, i.e., the message is placed on a queue within the scope of a transaction but not actually delivered until the enclosing transaction has committed; it is then pulled by the receiver in the scope of a separate transaction. Unfortunately for synchronous request/response interactions this can result in a timeout waiting for the response since the sender blocks waiting for the response before it can terminate the delivery transaction. >From JBossESB 4.5 onwards we attempt to detect these blocking situations and throw the IncompatibleTransactionScopeException. The application should catch this and act accordingly. ****** Suggested rewording: ***** Some Couriers, such as InVM and JMS, support transactional delivery semantics. The current delivery semantics for such a Courier is based on JMS transacted sessions. In other words, the message is placed in a queue within the scope of a transaction. However, it is not actually delivered until the enclosing transaction has been committed. It is then pulled by the receiver in the scope of a separate transaction. In the case of synchronous request/response interactions this can result in a timeout waiting for the response. This is because the sender blocks while waiting for the response and terminates the delivery transaction. JBossESB 4.5 onwards attempts to detect these blocking situations and will throw an IncompatibleTransactionScopeException exception. The application should catch this and act accordingly. ***** -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-2643) Setting required http-provider attributes fails the *.esb deployment

by Sindre Hamlander (JIRA)

Setting required http-provider attributes fails the *.esb deployment -------------------------------------------------------------------- Key: JBESB-2643 URL: https://jira.jboss.org/jira/browse/JBESB-2643 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.4 FP1 Reporter: Sindre Hamlander According to jbossesb-1.1.0.xsd the "host" and "port" attribute must be set on the "http-provider" tag in the jboss-esb.xml. If these values are set, the deployment fails with the following stacktrace: 2009-06-24 16:39:28,006 ERROR [org.jboss.deployment.MainDeployer] Could not initialise deployment: file:/opt/redhat/jboss-soa-p.4.3.0/jboss-as/server/production/deploy/ws_simple.esb org.jboss.deployment.DeploymentException: Failed to parse jboss-esb.xml; - nested throwable: (org.apache.xmlbeans.XmlException: error: The document is not a jbossesb@http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.0.1.xsd: document element namespace mismatch expected "http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..." got "http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml...") at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer.getJbossEsb(JBoss4ESBDeployer.java:411) at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer.init(JBoss4ESBDeployer.java:264) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) Caused by: org.apache.xmlbeans.XmlException: error: The document is not a jbossesb@http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.0.1.xsd: document element namespace mismatch expected "http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..." got "http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..." at org.apache.xmlbeans.impl.store.Locale.verifyDocumentType(Locale.java:452) at org.apache.xmlbeans.impl.store.Locale.autoTypeDocument(Locale.java:357) at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1326) at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1310) at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:360) at org.jboss.soa.esb.listeners.config.xbeanmodel.JbossesbDocument$Factory.parse(JbossesbDocument.java:179) at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer.getJbossEsb(JBoss4ESBDeployer.java:407) ... 22 more -- 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

16 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2548) HttpClientFactory not configuring the "default-max-connections-per-host" on the connection manager

by Tom Fennelly (JIRA)

HttpClientFactory not configuring the "default-max-connections-per-host" on the connection manager -------------------------------------------------------------------------------------------------- Key: JBESB-2548 URL: https://jira.jboss.org/jira/browse/JBESB-2548 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.5 Reporter: Tom Fennelly Fix For: 4.6 HttpClientFactory.createHttpClient creates a HttpConnectionManager instance and configures the "max-total-connections". This is somewhat irrelevant however as the HttpClient still has a default limit of 1 (or 2 - I forget) max connections per connected host, so will never use anything like the configured "max-total-connections". One fix is to also set the "default-max-connections-per-host" on the HostConnectionManager params, with a default value of the value returned from a call to HttpConnectionManager.getParams().getMaxTotalConnections(). I think this would be fine because we only ever have 1 host per httpclient, but you could also provide an override config for situations where we have more. -- 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

16 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-2642) JbpmService assumes existence of JobExecutor

by Kevin Conner (JIRA)

JbpmService assumes existence of JobExecutor -------------------------------------------- Key: JBESB-2642 URL: https://jira.jboss.org/jira/browse/JBESB-2642 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 CP2 Reporter: Kevin Conner Fix For: 4.4 CP3 Check for existence of JobExecutor and force start/stop of services through JbpmConfiguration/JbpmContext. -- 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

16 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2641) AsyncProcessSignal assumes existence of JobExecutor

by Kevin Conner (JIRA)

AsyncProcessSignal assumes existence of JobExecutor --------------------------------------------------- Key: JBESB-2641 URL: https://jira.jboss.org/jira/browse/JBESB-2641 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.4 CP2 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP3 -- 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

16 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2636) Upgrade h2 to latest version

by Kevin Conner (JIRA)

Upgrade h2 to latest version ---------------------------- Key: JBESB-2636 URL: https://jira.jboss.org/jira/browse/JBESB-2636 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.4 CP2 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP3 -- 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

16 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2638) Add support for generic JCA inflow

by Kevin Conner (JIRA)

Add support for generic JCA inflow ---------------------------------- Key: JBESB-2638 URL: https://jira.jboss.org/jira/browse/JBESB-2638 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.4 CP2 Reporter: Kevin Conner Fix For: 4.4 CP3 This is not directly associated with the ESB but will take advantage of some of the ESB support. This is intended to enable JMS inflow for jBPM. -- 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

16 years, 10 months

1
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 June 2009