October 2009 - esb-issues - Jboss List Archives

[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

16 years

4
4
0 / 0

[JBoss JIRA] Created: (JBESB-2550) "local first" load balancing policy

by toby cabot (JIRA)

"local first" load balancing policy ----------------------------------- Key: JBESB-2550 URL: https://jira.jboss.org/jira/browse/JBESB-2550 Project: JBoss ESB Issue Type: Patch Security Level: Public (Everyone can see) Affects Versions: 4.4 Reporter: toby cabot Here's a patch that adds org.jboss.soa.esb.listeners.ha.LocalFirstRoundRobin which will choose a local EPR if there is one and fall back to RoundRobin if not. We like this because it keeps processing on a single host when that's possible and only goes off-host (which is relatively expensive) if necessary. -- 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, 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

16 years, 1 month

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

16 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2901) Can't deploy custom ScheduledListener configuration

by Thorsten Polster (JIRA)

Can't deploy custom ScheduledListener configuration --------------------------------------------------- Key: JBESB-2901 URL: https://jira.jboss.org/jira/browse/JBESB-2901 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.5 Reporter: Thorsten Polster ConfigurationException while configure custom ScheduledListener Can't use custom ScheduledListener like described in JBoss Wiki (see: http://www.jboss.org/community/wiki/WritingCustomListenersforJBossESB4x#S...) org.jboss.soa.esb.ConfigurationException: Can only use the org.jboss.soa.esb.listeners.config.mappers110.UntypedListenerMapper mapper on the base listener type. Cannot use on org.jboss.soa.esb.listeners.config.xbeanmodel110.impl.ScheduledListenerDocumentImpl$ScheduledListenerImpl at org.jboss.soa.esb.listeners.config.mappers110.UntypedListenerMapper.assertListenerConfigOK(UntypedListenerMapper.java:101) at org.jboss.soa.esb.listeners.config.mappers110.UntypedListenerMapper.map(UntypedListenerMapper.java:62) at org.jboss.soa.esb.listeners.config.mappers110.GatewayGenerator.addGatewayConfig(GatewayGenerator.java:146) at org.jboss.soa.esb.listeners.config.mappers110.GatewayGenerator.generate(GatewayGenerator.java:108) at org.jboss.soa.esb.listeners.config.mappers110.XMLBeansModel.generateGatewayConfig(XMLBeansModel.java:451) at org.jboss.soa.esb.listeners.config.model.Model110SchemaParser$Model110Adapter.generateGatewayConfig(Model110SchemaParser.java:138) at org.jboss.soa.esb.listeners.config.Generator.generate(Generator.java:116) at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration.java:94) ... 46 more There might be a bug in the class org.jboss.soa.esb.listeners.config.mappers110.UntypedListenerMapper in the method assertListenerConfigOK, cause there is a check for that the mapped Listener must be a ListenerImpl, but is a ScheduledListenerImpl which is just a instance of ListenerImpl. -- 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, 1 month

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

16 years, 1 month

4
5
0 / 0

[JBoss JIRA] Created: (JBESB-2457) SoapUIClientService does not populate request attributes

by Kevin Conner (JIRA)

SoapUIClientService does not populate request attributes -------------------------------------------------------- Key: JBESB-2457 URL: https://jira.jboss.org/jira/browse/JBESB-2457 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 CP2, 4.5 Reporter: Joakim Sandström SoapUIClientService only appears to handle population of text elements and not the attributes. expected request: <soapenv:Body> <ns:updateCustomer customerId="124343"> <ns:name> <ns:firstName>FIRSTNAME</ns:firstName> actual request: <soapenv:Body> <ns:updateCustomer customerId="?"> <ns:name> <ns:firstName>FIRSTNAME</ns:firstName> -- 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, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2868) InVMTransport deliver NPE on missing service

by Kevin Conner (JIRA)

InVMTransport deliver NPE on missing service -------------------------------------------- Key: JBESB-2868 URL: https://jira.jboss.org/jira/browse/JBESB-2868 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 CP3 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP4 My bad, the code is referencing the entry before checking it is null. -- 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, 1 month

1
3
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

16 years, 1 month

4
7
0 / 0

[JBoss JIRA] Created: (JBESB-2844) WebService invocation is sometimes handled by CoyoteInvoker belonging to undeployed package

by Kevin Conner (JIRA)

WebService invocation is sometimes handled by CoyoteInvoker belonging to undeployed package ------------------------------------------------------------------------------------------- Key: JBESB-2844 URL: https://jira.jboss.org/jira/browse/JBESB-2844 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1, 4.4 CP3 Reporter: Jiri Pechanec Assignee: Tom Fennelly Priority: Minor Fix For: 4.2.1 CP4 There were multiple packages deployed/undeployed in the test. The deployment of Quickstart_webservice_mtom.esb is started on line 413471. This package starts coyote invoker with hashCode 17a4c54 at the line 413681. The undeploymetn of this package starts on line 414408. The CoyoteInvoker with the given hashCode is stopped at line 414457. The Quickstart_webservice_wsa.esb package deployment starts at line 414599. The CoyotInvoker with hashCode d93db8 is started at line 414806. Then the test message is sent via HTTP/SOAP and this request fails on line 515535 because it was served by the CoyoteInvoker with hashCode 17a4c54 so the one that belongs to previously undeployed package. -- 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, 1 month

2
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues October 2009