November 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2162) Actions with the name name generates exception but does not prevent deployment

by Kevin Conner (JIRA)

Actions with the name name generates exception but does not prevent deployment ------------------------------------------------------------------------------ Key: JBESB-2162 URL: https://jira.jboss.org/jira/browse/JBESB-2162 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration, Rosetta Affects Versions: 4.4 Reporter: Jiri Pechanec Assignee: Kevin Conner Fix For: 4.4 CP1 Two actions with same name generates exception 2008-09-05 13:49:27,546 ERROR [org.jboss.soa.esb.listeners.config.mappers.ActionMapper] org.jboss.soa.esb.ConfigurationException: Tried to register a duplicate action name. Service RequestReplySC already contains an action named action. Action names must be unique per service. at org.jboss.soa.esb.listeners.config.mappers.ActionMapper.map(ActionMapper.java:101) at org.jboss.soa.esb.listeners.config.ESBAwareGenerator.addInVMListener(ESBAwareGenerator.java:126) at org.jboss.soa.esb.listeners.config.ESBAwareGenerator.generate(ESBAwareGenerator.java:91) at org.jboss.soa.esb.listeners.config.Generator.generate(Generator.java:148) at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration.java:104) 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.GeneratedMethodAccessor132.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.GeneratedMethodAccessor12.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.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.redeploy(MainDeployer.java:566) 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.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.GeneratedMethodAccessor114.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.GeneratedMethodAccessor112.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.GeneratedMethodAccessor111.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.GeneratedMethodAccessor110.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) But the archive is still deployed. According to Kevin there is a code [14:52] <kconner> } catch (ConfigurationException ce) { [14:52] <kconner> logger.error("", ce); [14:52] <kconner> } -- 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

15 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2161) HttpClientFactory ignores max-total-connections setting

by Kevin Conner (JIRA)

HttpClientFactory ignores max-total-connections setting ------------------------------------------------------- Key: JBESB-2161 URL: https://jira.jboss.org/jira/browse/JBESB-2161 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP1, 4.5 The createHttpClient method looks for the MAX_TOTAL_CONNECTIONS and, if present, attempts to initialise the MaxTotalConnections attribute. At present this value is applied to an instance of HttpConnectionManagerParams but this is never set on the connectionManager. The codebase should either initialise the params for the connection manager or use the default params when initialising this attribute. -- 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

15 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2156) SoapUIClient inserting cloned nodes in the wrong location

by Kevin Conner (JIRA)

SoapUIClient inserting cloned nodes in the wrong location --------------------------------------------------------- Key: JBESB-2156 URL: https://jira.jboss.org/jira/browse/JBESB-2156 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1 CP2 Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.3 Only shows up when you have a number of unbound collections in a series. This soapUI + DOM manipulation is a bit of a pain in the head! -- 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

15 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2153) WS attachments does not work for non-image binary data

by Kevin Conner (JIRA)

WS attachments does not work for non-image binary data ------------------------------------------------------ Key: JBESB-2153 URL: https://jira.jboss.org/jira/browse/JBESB-2153 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1 Reporter: Jiri Pechanec Assignee: Kevin Conner Fix For: 4.4 In the JBossWS docs there is a list of supported MIME types together with appropriate java data types http://jbws.dyndns.org/mediawiki/index.php?title=User_Guide#Attachments java.awt.Image and javax.xml.transform.Source works but javax.activation.DataHandler that can be used to transfer any binary data does not. Attached is test app and TestNG test that can be convereted into standalone client in two minutes If call is done against WS itself then it works, if it send via ESB facade, the attachment is not added. Can it be related to JBESB-1479 ? -- 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

15 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2154) SOAPClient process method should guard against ClassCastExceptions on the payload

by Kevin Conner (JIRA)

SOAPClient process method should guard against ClassCastExceptions on the payload --------------------------------------------------------------------------------- Key: JBESB-2154 URL: https://jira.jboss.org/jira/browse/JBESB-2154 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1 CP1, 4.2.1 CP2 Reporter: Tom Fennelly Assignee: Mark Little Fix For: 4.4 It's currently just doing a cast to a Map, but not guarding against something else being there. -- 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

15 years, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-2151) Services should be unique by node:esb:category:service

by Kevin Conner (JIRA)

Services should be unique by node:esb:category:service ------------------------------------------------------ Key: JBESB-2151 URL: https://jira.jboss.org/jira/browse/JBESB-2151 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration, Deployment, Rosetta Affects Versions: 4.2.1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.4 Currently, services are unique by : node:esb:service They should be unique by : node:esb:category:service >From Kevin: The gateway generator enforces a unique service name within an esb but it does not take the category into account. It looks like you may have added this requirement into the code at some point, can you remember why the category was never used? -- 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

15 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2152) CBR using rules has poor performance

by Kevin Conner (JIRA)

CBR using rules has poor performance ------------------------------------ Key: JBESB-2152 URL: https://jira.jboss.org/jira/browse/JBESB-2152 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.2.1 Environment: SOA-P 4.2.0.beta1 Reporter: Martin Vecera Assignee: Daniel Bevenius Fix For: 4.4 We have a simple performance that uses ContentBasedRouter to route XML messages: <action class="org.jboss.soa.esb.actions.ContentBasedRouter" name="ContentBasedRouter"> <property name="ruleSet" value="MyESBRules-XPath.drl"/> <property name="ruleLanguage" value="XPathLanguage.dsl"/> <property name="ruleReload" value="true"/> <property name="destinations"> <route-to destination-name="regular1" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular2" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular3" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular4" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular5" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular6" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular7" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular8" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular9" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular0" service-category="wiretapCategory1" service-name="catchService"/> </property> </action> I have created a rule set of 100 rules. Like this: package com.jboss.soa.esb.routing.cbr import org.jboss.soa.esb.message.Message; import org.jboss.soa.esb.message.format.MessageType; expander XPathLanguage.dsl global java.util.List destinations; rule "ProductId1" salience 100 when xpathEquals "/Order/OrderLines/OrderLine/Product/@productId", "1" then Destination : "regular1"; end ... rule "ProductId299" salience 100 when xpathEquals "/Order/OrderLines/OrderLine/Product/@productId", "299" then Destination : "regular0"; end rule "Default rule" salience 1 when then Destination : "regular0"; end See https://svn.corp.jboss.com/repos/soa/trunk/qa/tests/quickstarts/performan... for the whole file. The performance is very poor (see SOA-240 for reports). Only a tens of messages per second. What's the problem here? Is the Rules engine really so slow? Or is it parsing the file every time a message arrives? -- 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

15 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2146) Scheduling: Multiple cron schedules not supported

by Tom Fennelly (JIRA)

Scheduling: Multiple cron schedules not supported ------------------------------------------------- Key: JBESB-2146 URL: https://jira.jboss.org/jira/browse/JBESB-2146 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4, 4.4 CP1 Reporter: Tom Fennelly Assignee: Kevin Conner If you define multiple cron schedules, or just one cron schedule with associated multiple listeners/jobs.... only the first job gets executed. I stepped into the code and the jobs are getting registered, started etc. -- 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

15 years, 6 months

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-2114) inVM information is out of date in Programmers Guide

by Darrin Mison (JIRA)

inVM information is out of date in Programmers Guide ---------------------------------------------------- Key: JBESB-2114 URL: https://jira.jboss.org/jira/browse/JBESB-2114 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.3 Reporter: Darrin Mison The InVM transport information in the programmers guide is out of date regards to configured defaults. -- 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

15 years, 6 months

4
10
0 / 0

[JBoss JIRA] Created: (JBESB-2072) Add TModel through JAXR, rather than manually or through SQL

by Tom Cunningham (JIRA)

Add TModel through JAXR, rather than manually or through SQL ------------------------------------------------------------ Key: JBESB-2072 URL: https://jira.jboss.org/jira/browse/JBESB-2072 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.4 CP1 Currently we add the TModel we need through a SQL script in jUDDI and we ask that the user use the SOA Software GUI to add a TModel in the SOA Software UDDI instructions. It'd be nice if we handled this automatically if the ClassificationScheme query fails, and then we retry that query. -- 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

15 years, 6 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues November 2008