August 2011 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3622) DefaultJMSPropertiesSetter needs to filter out JMS properties

by Kevin Conner (JIRA)

DefaultJMSPropertiesSetter needs to filter out JMS properties ------------------------------------------------------------- Key: JBESB-3622 URL: https://issues.jboss.org/browse/JBESB-3622 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.9 CP1 Reporter: Kevin Conner The current property setter checks for properties that start with JMSX and JMS_ but we also need to include any properties that begin with JMS. The spec states that the prefixes JMSX and JMS_ are reserved for the JMS spec and implementations respectively, but it also states in a later section that any identifier name which does not begin with 'JMS' is application specific. Two implementations that will raise exceptions are WSMQ and HornetQ. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-3666) Smooks PropertyChecker can't find generated class

by Tom Cunningham (JIRA)

Smooks PropertyChecker can't find generated class ------------------------------------------------- Key: JBESB-3666 URL: https://issues.jboss.org/browse/JBESB-3666 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.10 CP1 Reporter: Tom Cunningham Assignee: Tom Fennelly Fix For: 4.10 CP1 Seeing a regression from SOA-P 5.1.0.GA (or ESB 4.9) (and the previous version of Smooks used in JBoss ESB) - when trying out the test case from SOA-3205, PropertySetter is unable to find the generated bean class the first time I run the example, but any subsequent time I try to run it, it works. private Class<?> getBeanClass(Element bindingElement) { String beanClassName = getBeanTypeName(bindingElement); Class<?> beanClass; try { ----> beanClass = ClassUtil.forName(beanClassName, getClass()); } catch (ClassNotFoundException e) { throw new SmooksConfigurationException("Bean class '" + beanClassName + "' not avilable on classpath."); } return beanClass; } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-3658) SmooksConfigurationException: ComplexObject not avilable on classpath

by Jaroslaw Kijanowski (JIRA)

SmooksConfigurationException: ComplexObject not avilable on classpath --------------------------------------------------------------------- Key: JBESB-3658 URL: https://issues.jboss.org/browse/JBESB-3658 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.10 Environment: jbossesb-4.10(a)jboss-5.1.0.GA java version "1.6.0_26" Reporter: Jaroslaw Kijanowski I'm running webservice_consumer_wise2: 07:31:16,166 ERROR [STDERR] org.milyn.SmooksException: Failed to apply processing unit [org.milyn.javabean.ext.PropertyChecker] to [org:milyn:smooks:unknowndoc:/smooks-resource-list/jb:bean/jb:value]. 07:31:16,166 ERROR [STDERR] at org.milyn.delivery.dom.SmooksDOMFilter.processVisitorException(SmooksDOMFilter.java:823) 07:31:16,166 ERROR [STDERR] at org.milyn.delivery.dom.SmooksDOMFilter.access$700(SmooksDOMFilter.java:134) 07:31:16,166 ERROR [STDERR] at org.milyn.delivery.dom.SmooksDOMFilter$ElementProcessor.processMapping(SmooksDOMFilter.java:765) 07:31:16,166 ERROR [STDERR] at org.milyn.delivery.dom.SmooksDOMFilter$ElementProcessor.process(SmooksDOMFilter.java:710) 07:31:16,166 ERROR [STDERR] at org.milyn.delivery.dom.SmooksDOMFilter$ElementProcessor.access$000(SmooksDOMFilter.java:666) 07:31:16,166 ERROR [STDERR] at org.milyn.delivery.dom.SmooksDOMFilter.filter(SmooksDOMFilter.java:385) 07:31:16,166 ERROR [STDERR] at org.milyn.delivery.dom.SmooksDOMFilter.doFilter(SmooksDOMFilter.java:238) 07:31:16,166 ERROR [STDERR] at org.milyn.delivery.dom.SmooksDOMFilter.doFilter(SmooksDOMFilter.java:216) 07:31:16,167 ERROR [STDERR] at org.milyn.Smooks._filter(Smooks.java:516) 07:31:16,167 ERROR [STDERR] at org.milyn.Smooks.filterSource(Smooks.java:470) 07:31:16,167 ERROR [STDERR] at org.milyn.cdr.XMLConfigDigester.digestExtendedResourceConfig(XMLConfigDigester.java:555) 07:31:16,167 ERROR [STDERR] at org.milyn.cdr.XMLConfigDigester.digestV11XSDValidatedConfig(XMLConfigDigester.java:340) 07:31:16,167 ERROR [STDERR] at org.milyn.cdr.XMLConfigDigester.digestConfigRecursively(XMLConfigDigester.java:226) 07:31:16,167 ERROR [STDERR] at org.milyn.cdr.XMLConfigDigester.digestConfig(XMLConfigDigester.java:184) 07:31:16,167 ERROR [STDERR] at org.milyn.cdr.SmooksResourceConfigurationStore.registerResources(SmooksResourceConfigurationStore.java:227) 07:31:16,167 ERROR [STDERR] at org.milyn.Smooks.addConfigurations(Smooks.java:338) 07:31:16,167 ERROR [STDERR] at org.jboss.soa.esb.actions.soap.wise.SmooksMapper.applyMapping(SmooksMapper.java:95) 07:31:16,167 ERROR [STDERR] at it.javalinux.wise.core.client.WSMethod.invoke(WSMethod.java:114) 07:31:16,167 ERROR [STDERR] at org.jboss.soa.esb.actions.soap.wise.SOAPClient.process(SOAPClient.java:253) 07:31:16,167 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:649) 07:31:16,167 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:603) 07:31:16,167 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:433) 07:31:16,167 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:550) 07:31:16,167 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 07:31:16,167 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 07:31:16,167 ERROR [STDERR] at java.lang.Thread.run(Thread.java:680) 07:31:16,167 ERROR [STDERR] Caused by: org.milyn.cdr.SmooksConfigurationException: Bean class 'org.jboss.soa.esb.samples.quickstart.webservice_consumer_wise2.generated.ComplexObject' not avilable on classpath. 07:31:16,167 ERROR [STDERR] at org.milyn.javabean.ext.PropertyChecker.getBeanClass(PropertyChecker.java:97) 07:31:16,167 ERROR [STDERR] at org.milyn.javabean.ext.PropertyChecker.getBeanType(PropertyChecker.java:78) 07:31:16,167 ERROR [STDERR] at org.milyn.javabean.ext.PropertyChecker.visitBefore(PropertyChecker.java:47) 07:31:16,167 ERROR [STDERR] at org.milyn.delivery.dom.SmooksDOMFilter$ElementProcessor.processMapping(SmooksDOMFilter.java:759) 07:31:16,168 ERROR [STDERR] ... 23 more I guess a Smooks classloader issue? I have to put the generated ComplexObjcet class (from the wise.tmpDir) into the esb archive to have it working. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-3671) SOAPProxy fails to extract soapAction from request.

by Marek Baluch (JIRA)

SOAPProxy fails to extract soapAction from request. --------------------------------------------------- Key: JBESB-3671 URL: https://issues.jboss.org/browse/JBESB-3671 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.10 Reporter: Marek Baluch A SOAPProxy action defined like the following one: {code} <action name="proxy" class="org.jboss.soa.esb.actions.soap.proxy.SOAPProxy"> <property name="wsdl" value="internal://jboss.ws:context=Quickstart_bpm_webservice_proxy_ws,endpoint=TestWS"/> <property name="soapAction" value=""/> </action> {code} will/may need to call the SOAPProxy.findElement(Message) method. This method will produce a NullPointerException {noformat} 2011-08-29 15:33:11,278 WARN [org.jboss.soa.esb.actions.soap.proxy.SOAPProxy] (WorkManager(2)-14) null binding for soapaction [null]; parsing envelope to find element or operation... 2011-08-29 15:33:11,322 DEBUG [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] (WorkManager(2)-14) Unexpected exception caught while processing the action pipeline org.jboss.soa.esb.actions.ActionProcessingException: java.lang.NullPointerException at org.jboss.soa.esb.actions.soap.proxy.SOAPProxy.findElement(SOAPProxy.java:505) at org.jboss.soa.esb.actions.soap.proxy.SOAPProxy.process(SOAPProxy.java:387) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:649) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:603) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:433) at org.jboss.soa.esb.listeners.jca.JcaMessageAwareListener.process(JcaMessageAwareListener.java:163) at org.jboss.soa.esb.listeners.jca.JcaJMSInflowMessageProcessorAdapter.onMessage(JcaJMSInflowMessageProcessorAdapter.java:44) 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:597) at org.jboss.soa.esb.listeners.jca.BaseJcaInflow$1.invoke(BaseJcaInflow.java:205) at org.jboss.soa.esb.listeners.jca.EndpointProxy.delivery(EndpointProxy.java:258) at org.jboss.soa.esb.listeners.jca.EndpointProxy.invoke(EndpointProxy.java:150) at $Proxy413.onMessage(Unknown Source) at org.jboss.resource.adapter.jms.inflow.JmsServerSession.onMessage(JmsServerSession.java:179) at org.jboss.jms.client.container.ClientConsumer.callOnMessageStatic(ClientConsumer.java:167) at org.jboss.jms.client.container.SessionAspect.handleRun(SessionAspect.java:895) at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect_z_handleRun_16427044.invoke(SessionAspect_z_handleRun_16427044.java) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:172) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.jms.client.delegate.ClientSessionDelegate.run(ClientSessionDelegate.java) at org.jboss.jms.client.JBossSession.run(JBossSession.java:199) at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:236) at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205) at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.NullPointerException at org.jboss.soa.esb.actions.soap.proxy.SOAPProxy.findElement(SOAPProxy.java:495) ... 30 more {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-3672) Implement workaround for drools performance issue

by Kevin Conner (JIRA)

Implement workaround for drools performance issue ------------------------------------------------- Key: JBESB-3672 URL: https://issues.jboss.org/browse/JBESB-3672 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.10 Reporter: Kevin Conner Fix For: 4.10 CP1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3668) Incorporate SOA-3077

by Kevin Conner (JIRA)

Incorporate SOA-3077 -------------------- Key: JBESB-3668 URL: https://issues.jboss.org/browse/JBESB-3668 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.10 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.10 CP1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBESB-2813) Lazy lookup of EJBs in EJBProcessor

by Magesh Bojan (JIRA)

[ https://issues.jboss.org/browse/JBESB-2813?page=com.atlassian.jira.plugin... ] Magesh Bojan closed JBESB-2813. ------------------------------- > Lazy lookup of EJBs in EJBProcessor > ----------------------------------- > > Key: JBESB-2813 > URL: https://issues.jboss.org/browse/JBESB-2813 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Adapters > Affects Versions: 4.4, 4.5, 4.6 > Reporter: Martin Weiler > Assignee: Magesh Bojan > Fix For: 4.10 CP1 > > Attachments: EJBProcessor.java > > > EJBProcessor performs lookup of remote EJBs at application startup. If the lookup fails, EJBProcessor throws an exception, so that the whole application cannot start. > This should be changed to a lazy lookup. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBESB-2813) Lazy lookup of EJBs in EJBProcessor

by Magesh Bojan (JIRA)

[ https://issues.jboss.org/browse/JBESB-2813?page=com.atlassian.jira.plugin... ] Magesh Bojan resolved JBESB-2813. --------------------------------- Resolution: Done At branch JBESB_4_10_CP revision 37428 > Lazy lookup of EJBs in EJBProcessor > ----------------------------------- > > Key: JBESB-2813 > URL: https://issues.jboss.org/browse/JBESB-2813 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Adapters > Affects Versions: 4.4, 4.5, 4.6 > Reporter: Martin Weiler > Assignee: Magesh Bojan > Fix For: 4.10 CP1 > > Attachments: EJBProcessor.java > > > EJBProcessor performs lookup of remote EJBs at application startup. If the lookup fails, EJBProcessor throws an exception, so that the whole application cannot start. > This should be changed to a lazy lookup. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-3643) WISE SOAPClient exception loss

by Tom Cunningham (JIRA)

WISE SOAPClient exception loss ------------------------------ Key: JBESB-3643 URL: https://issues.jboss.org/browse/JBESB-3643 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.10 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 WISE currently captures the exception raised by the WS invocation, and then goes through a list of exceptions to see if the exception matches those. What we'd like to do is catch the exception, look inside the InvocationTargetException, and if it is a javax.xml.ws.soap.SOAPFaultException, wrap it in the same as other exceptions. REPRODUCE : 1. Deploy the WAR attached to SOA-3205 file on SOA-P 5.1 2. Unzip the webservice_consumer_wise_smooks.zip into the quickstarts directory 3. ant deploy 4. ant runtest -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3475) Revisit remote strategies in ESB. They use an obsolete version of JBoss Cache.

by Marek Baluch (JIRA)

Revisit remote strategies in ESB. They use an obsolete version of JBoss Cache. ------------------------------------------------------------------------------ Key: JBESB-3475 URL: https://jira.jboss.org/browse/JBESB-3475 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.9 Environment: SOA 5.1 Reporter: Marek Baluch Package org.jboss.soa.esb.listeners.gateway.remotestrategies.cache uses TreeCache and TreeCacheListener classes which where present in an older JBoss Cache release. This release is not shipped with SOA-P 5.1. It was last seen in SOA-P 5.0.2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues August 2011