November 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-834) Include Smooks documentation in release

by Mark Little (JIRA)

Include Smooks documentation in release --------------------------------------- Key: JBESB-834 URL: http://jira.jboss.com/jira/browse/JBESB-834 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Tom Fennelly On behalf of intern: "It would be nice if the Smooks docs were included in the distribution. In general, it would be nice if all 3rd party libs that the user may need to play with have some form of self-contained docs." -- 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

14 years, 1 month

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-556) Make the webservice_bpel quickstart into a Trailblazer

by Tom Fennelly (JIRA)

Make the webservice_bpel quickstart into a Trailblazer ------------------------------------------------------ Key: JBESB-556 URL: http://jira.jboss.com/jira/browse/JBESB-556 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2 This is really a Trailblazer - too much in it to be a QS -- 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

14 years, 1 month

3
8
0 / 0

[JBoss JIRA] Created: (JBESB-1691) MRG/RHM support

by Mark Little (JIRA)

MRG/RHM support --------------- Key: JBESB-1691 URL: http://jira.jboss.com/jira/browse/JBESB-1691 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 CP2 Reporter: Mark Little -- 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

14 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-1429) Need an MBean for CronExpressions

by Tom Cunningham (JIRA)

Need an MBean for CronExpressions --------------------------------- Key: JBESB-1429 URL: http://jira.jboss.com/jira/browse/JBESB-1429 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.2.1 Reporter: Tom Cunningham Assigned To: Tom Cunningham Need a way of dynamically updating a cron expression at runtime. MBean probably would be the preferable method for 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

14 years, 1 month

4
4
0 / 0

[JBoss JIRA] Created: (JBESB-1937) Document performance tuning parameters

by Kevin Conner (JIRA)

Document performance tuning parameters -------------------------------------- Key: JBESB-1937 URL: https://jira.jboss.org/jira/browse/JBESB-1937 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.4 Reporter: Kevin Conner Assignee: Jervis Liu Fix For: 4.5 We need to include documentation on tuning parameters that are available within the ESB. Jervis has made a good start to this as part of the recent work he has been doing, his experience should be used as the basis. -- 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

14 years, 2 months

4
14
0 / 0

[JBoss JIRA] Created: (JBESB-1121) JBoss Web Console integration (message alerter)

by Tom Cunningham (JIRA)

JBoss Web Console integration (message alerter) ----------------------------------------------- Key: JBESB-1121 URL: http://jira.jboss.com/jira/browse/JBESB-1121 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Tom Cunningham Assigned To: Tom Cunningham According to their docs, the JBoss Web Console does console-based alerts and email-alerts. It'd be nice if there was also was an ESB option - where based off of a JMX Bean property, a message is sent to whatever ESB service the user specifies in their monitoring XML. -- 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

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1851) JAXRConnectionFactory should not rely on System properties when creating a Connection

by Daniel Bevenius (JIRA)

JAXRConnectionFactory should not rely on System properties when creating a Connection ------------------------------------------------------------------------------------- Key: JBESB-1851 URL: http://jira.jboss.com/jira/browse/JBESB-1851 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples, Registry and Repository Reporter: Daniel Bevenius The quickstarts that use the ServiceInvoker all seem to do this (atleast the ones that I've looked at) : System.setProperty("javax.xml.registry.ConnectionFactoryClass","org.apache.ws.scout.registry.ConnectionFactoryImpl"); Now, we have this property in the jbossesb-properties.xml as: <property name="org.jboss.soa.esb.registry.factoryClass" value="org.apache.ws.scout.registry.ConnectionFactoryImpl"/> This property is read by JAXRConnectionFactory constructor and saved into a Properties object as: props.setProperty("javax.xml.registry.factoryClass", Configuration.getRegistryFactoryClass()); The 'props' are set on the ConnectionFactory object that is created in the getConnection() method: protected Connection getConnection() { Connection connection = null; try { // Create the connection, passing it the configuration properties ConnectionFactory factory = ConnectionFactory.newInstance(); factory.setProperties(props); connection = factory.createConnection(); connection.setCredentials(creds); } catch (JAXRException e) { logger.log(Level.ERROR, "Could not set up a connection to the Registry. " + e.getMessage(), e); } return connection; } Here we can see that ConnectionFactory.newInstance() method will be called prior to the properties getting set on the factory, which is natural. But the problem is that ConnectionFactory.newInstance() method looks like this: private static final String SYS_PROP_NAME = "javax.xml.registry.ConnectionFactoryClass"; public static ConnectionFactory newInstance() throws JAXRException { String factoryName = null; ConnectionFactory factory = null; try { String defaultName = null; factoryName = System.getProperty(SYS_PROP_NAME, defaultName); ClassLoader loader =Thread.currentThread().getContextClassLoader(); Class factoryClass = loader.loadClass(factoryName); factory = (ConnectionFactory) factoryClass.newInstance(); } catch(Throwable e) { throw new JAXRException("Failed to create instance of:"+factoryName, e); } return factory; } We should not be relying on the system properties in order to do this. Our JAXRConnectionFactory should be creating the factory directly and not using ConnectionFactory, this is the real error IMO. If we do this then we will not be affected by anyone else in the AS overriding JAXR. Kev See also this googlegroups thread for more background info: http://groups.google.se/group/jbossesb/browse_frm/thread/3a5ce28b4a0f6bca -- 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

14 years, 2 months

4
5
0 / 0

[JBoss JIRA] Created: (JBESB-2208) JON plugin can not be compiled against JOPR source

by Thorbj?rn Blixen-Finecke (JIRA)

JON plugin can not be compiled against JOPR source -------------------------------------------------- Key: JBESB-2208 URL: https://jira.jboss.org/jira/browse/JBESB-2208 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.4 CP1 Environment: All Reporter: Thorbj?rn Blixen-Finecke Priority: Minor The org.jbosson.plugins.jbossesb.DeploymentComponent imports the class org.rhq.plugins.utils.FileUtils. This class does not exist in the RHQ 1.2.0 or JOPR 2.2.0 source. The JON plugin can therefore not be compiled against the JOPR source. -- 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

14 years, 2 months

4
7
0 / 0

[JBoss JIRA] Created: (JBESB-2204) jBPM Persistence race condition in EsbActionHandler under high load

by Damon Brown (JIRA)

jBPM Persistence race condition in EsbActionHandler under high load ------------------------------------------------------------------- Key: JBESB-2204 URL: https://jira.jboss.org/jira/browse/JBESB-2204 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.4 Environment: AS 4.2.3.GA, jBPM 3.2.3.GA + ehcache, RHEL 5, x86_64, 1.6.0 Sun JVM, Oracle 10g Reporter: Damon Brown Priority: Minor Attachments: CallbackCommand.java.patch Under extremely high load, the org.jboss.soa.esb.services.jbpm.cmd.CallbackCommand:90 cannot always locate the Token to signal for the target process. The exception is not propagated to the CallbackQueue and the message is not retried. The target process is left in a suspended state even though the ESB service has completed its action. The failure rate is machine-load dependent (1 - 5% failure rate). The root cause of the missing token is not able to be attributed to the jBPM hibernate session directly. I extended org.jboss.soa.esb.services.jbpm.actionhandlers.EsbActionHandler directly to forcibly flush the current state of the token to the database. Within the same action, I queried for the state of the object, which was returned successfully. There appears to be a race condition from ESB service invocation (EsbActionHandler), token persistence (hibernate flush), and command callback (CallbackCommand). The particular ESB service I am invoking has a short suspense. Other ESB services, which take longer to execute, do not exhibit this behavior. The behavior for the short-suspense service was random, but repeatable. The patch file attached to this issue attempts to resolve the issue by re-trying the token look-up three times with an intermittent sleep. Within my environment, under high load conditions, the token failed to resolve on the first try 1% - 5% of the time (98% average success on first try), with a 100% success rate on the second try. The target process instance is successfully signaled. -- 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

14 years, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-1972) EBWS endpoints are created even if ESB config file is onvalid

by Jiri Pechanec (JIRA)

EBWS endpoints are created even if ESB config file is onvalid ------------------------------------------------------------- Key: JBESB-1972 URL: https://jira.jboss.org/jira/browse/JBESB-1972 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Web Services Affects Versions: 4.4 CP1 Reporter: Jiri Pechanec Priority: Critical If there is a validation error in ESB config file the EBWS endpoints are created and their WSDL is accessible 2008-09-01 12:59:17,623 WARN [org.jboss.system.ServiceController] Problem starting service jboss.esb:deployment=EBWS.esb java.lang.RuntimeException: java.lang.IllegalStateException: ESB file had validation errors. at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration.java:138) at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startService(JBoss4ESBDeployment.java:99) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor333.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at org.jboss.system.ServiceController.start(ServiceController.java:435) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) 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 $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.redeploy(MainDeployer.java:588) at org.jboss.deployment.MainDeployer.redeploy(MainDeployer.java:562) at sun.reflect.GeneratedMethodAccessor364.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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 sun.reflect.GeneratedMethodAccessor317.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266) at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74) at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:108) 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.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179) at sun.reflect.GeneratedMethodAccessor108.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:818) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:419) at sun.reflect.GeneratedMethodAccessor107.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) at sun.rmi.transport.Transport$1.run(Transport.java:153) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:149) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.IllegalStateException: ESB file had validation errors. at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration.java:132) ... 80 more 2008-09-01 12:59:17,632 INFO [org.jboss.web.tomcat.service.TomcatDeployer] deploy, ctxPath=/EBWS, warUrl=.../tmp/deploy/esbwarfiles/EBWS.esb/EBWS-exp.war/ 2008-09-01 12:59:18,060 INFO [org.jboss.wsf.stack.jbws.WSDLFilePublisher] WSDL published to: file:/home/jpechane/pokus/43IR2AS/jboss-as/server/postgresql/data/wsdl/EBWS.esb/EBWS.war/esbservicesample_helloworldpubservice.wsdl 2008-09-01 12:59:18,068 INFO [org.jboss.wsf.stack.jbws.WSDLFilePublisher] WSDL published to: file:/home/jpechane/pokus/43IR2AS/jboss-as/server/postgresql/data/wsdl/EBWS.esb/EBWS.war/esbservicesample_requestreply.wsdl 2008-09-01 12:59:18,073 INFO [org.jboss.wsf.stack.jbws.WSDLFilePublisher] WSDL published to: file:/home/jpechane/pokus/43IR2AS/jboss-as/server/postgresql/data/wsdl/EBWS.esb/EBWS.war/esbservicesample_oneway.wsdl -- 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

14 years, 2 months

3
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues November 2008