February 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1559) DefaultESBPropertiesSetter should not set the ESBMessageID

by Daniel Bevenius (JIRA)

DefaultESBPropertiesSetter should not set the ESBMessageID ----------------------------------------------------------- Key: JBESB-1559 URL: http://jira.jboss.com/jira/browse/JBESB-1559 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 CP1 Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Fix For: 4.3 Since it is setting the ESB MessageID the message id will change every time the JMSCourier picks up a message. The orginal idea was the a message coming in at a JMS gateway should set the id, and the an JMSRouter or JMSNotifier could use it as a correlation id. But as the courier also uses it i might be better to take that out. User can always override the defaults anywhay -- 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 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1565) GroovyActionProcessor doesn't allow script mods without a redeploy

by Tom Fennelly (JIRA)

GroovyActionProcessor doesn't allow script mods without a redeploy ------------------------------------------------------------------ Key: JBESB-1565 URL: http://jira.jboss.com/jira/browse/JBESB-1565 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 CP1 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2.1 CP2 -- 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 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1560) GroovyActionProcessor implementation is grossly inefficient

by Jiri Pechanec (JIRA)

GroovyActionProcessor implementation is grossly inefficient ----------------------------------------------------------- Key: JBESB-1560 URL: http://jira.jboss.com/jira/browse/JBESB-1560 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Adapters, Rosetta Affects Versions: 4.2.1 CP1 Reporter: Jiri Pechanec Assigned To: Kevin Conner Fix For: 4.2.1 CP2 Attachments: GroovyScriptTest.java The GroovyActionProcess parses action script each time the message is processed the script is recompiled which means serous performance hit. The attached standalone testcase compare current and optimal implementation. Actual results from the test Preparsed 160 ms Non-preparsed 120832 ms -- 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 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-1561) Groovy security compromised

by Martin Vecera (JIRA)

Groovy security compromised --------------------------- Key: JBESB-1561 URL: http://jira.jboss.com/jira/browse/JBESB-1561 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Adapters, Rosetta Affects Versions: 4.2.1 CP1 Reporter: Martin Vecera GroovyActionProcess allows execution of malicious code. This code can be sent via esb message. See attached example (modified 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

16 years, 4 months

4
8
0 / 0

[JBoss JIRA] Created: (JBESB-1551) error in helloworld_hibernate_action QS

by Jehudi Castro (JIRA)

error in helloworld_hibernate_action QS --------------------------------------- Key: JBESB-1551 URL: http://jira.jboss.com/jira/browse/JBESB-1551 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 Reporter: Jehudi Castro please see SOA-420 for full description -- 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 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-1548) revision 18484 - helloworld_hibernate_action - Hibernate Interceptor events onSave, OnLoad return different subset of message - onDelete seems OK

by Len DiMaggio (JIRA)

revision 18484 - helloworld_hibernate_action - Hibernate Interceptor events onSave, OnLoad return different subset of message - onDelete seems OK ------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBESB-1548 URL: http://jira.jboss.com/jira/browse/JBESB-1548 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 Environment: revision 18484 Reporter: Len DiMaggio Assigned To: Tom Cunningham Priority: Minor Fix For: 4.2.1 CP1 Found this problem with looking at SOA-420. The onLoad Hibernate Interceptor event returns this for the message: id [1]product [null] quantity [null] price [null] (the id value increments correctly) While onSave returns: id [0]product [Widgets] quantity [20] price [2.4] (the id value is always 0) While onDelete seems to get it right: id [1]product [Widgets] quantity [20] price [2.4] -- 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 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-1550) NullPointerException in NamingContextPool

by Pavel Kadlec (JIRA)

NullPointerException in NamingContextPool ----------------------------------------- Key: JBESB-1550 URL: http://jira.jboss.com/jira/browse/JBESB-1550 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Reporter: Pavel Kadlec I got this exception while there were a lot of messages in ESB. 22:05:52,765 WARN [ServiceInvoker] Unexpected exception during attempted message delivery over Courier for EPR [JMSEpr [ PortReference < <wsa:Address jms://10.0.0.2:1099/queue/quickstart_Aggregator/> <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 10.0.0.2/>, <wsa:ReferenceProp erties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceP roperties jbossesb:persistent : false/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jboss esb:type : urn:jboss/esb/epr/type/jms/> > ]] for Service [Example:Aggregator] and Message [header: [ To: JMSEpr [ PortReference < <wsa:Address jms://10.0.0.2:1099/queue/quickstart_Aggregator/>, <wsa:R eferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 10.0.0.2/>, <wsa:ReferenceProperties j bossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferencePropertie s jbossesb:persistent : false/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: ID:11-1203195911358401 RelatesTo: jms:correlationID#81925235-a61b-4c87-b158-54232c623dee ]]. java.lang.NullPointerException at org.jboss.soa.esb.helpers.NamingContextPool.getContext(NamingContextPool.java:286) at org.jboss.soa.esb.helpers.NamingContextPool.getContext(NamingContextPool.java:150) at org.jboss.soa.esb.helpers.NamingContextPool.getNamingContext(NamingContextPool.java:400) at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageProducer(JmsCourier.java:340) at org.jboss.internal.soa.esb.couriers.JmsCourier.deliver(JmsCourier.java:199) at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.deliver(TwoWayCourierImpl.java:188) at org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.attemptDelivery(ServiceInvoker.java:508) at org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.access$200(ServiceInvoker.java:430) at org.jboss.soa.esb.client.ServiceInvoker.post(ServiceInvoker.java:307) at org.jboss.soa.esb.client.ServiceInvoker.deliverAsync(ServiceInvoker.java:216) at org.jboss.soa.esb.client.MessageMulticaster.sendToSubset(MessageMulticaster.java:144) at org.jboss.soa.esb.client.MessageMulticaster.sendToAll(MessageMulticaster.java:106) at org.jboss.soa.esb.actions.StaticWiretap.process(StaticWiretap.java:58) at org.jboss.soa.esb.actions.StaticRouter.process(StaticRouter.java:48) at cz.flynet.esb.actions.StaticRouter.process(StaticRouter.java:68) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316) at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:566) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) When I looked at the class org.jboss.soa.esb.helpers.NamingContextPool I could see that there is something wrong in method private Context getContext(final Properties env, final String key). If I studied code well, I thing that there is bad key put as a parameter, below is fixed method getContext. Please check if the fix is ok. private Context getContext(final Properties env, final String key) throws NamingContextException { final Context context = getFreeContext(key) ; if (context != null) { return context ; } if (numContexts == POOL_SIZE) { if (freeContextOrder.size() == 0) { return null ; } final Iterator<Entry<Context, String>> freeContextIter = freeContextOrder.entrySet().iterator() ; final Entry<Context, String> freeContextEntry = freeContextIter.next() ; final Context freeContext = freeContextEntry.getKey() ; final String freeContextKey = freeContextEntry.getValue() ; if (LOGGER.isDebugEnabled()) { LOGGER.debug("Ejecting Naming Context from pool, key: " + freeContextKey) ; } freeContextOrder.remove(freeContext) ; final List<Context> contexts = freeContexts.get(freeContextKey) ; // FIXED KEY contexts.remove(freeContext) ; if (contexts.size() == 0) { freeContexts.remove(freeContextKey) ; // FIXED KEY } numContexts-- ; closeContext(freeContext) ; } return createContext(env, key) ; } -- 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 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1417) bpm_orchestration1 needs to be updated

by Jiri Pechanec (JIRA)

bpm_orchestration1 needs to be updated -------------------------------------- Key: JBESB-1417 URL: http://jira.jboss.com/jira/browse/JBESB-1417 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples, Process flow Affects Versions: 4.2.1 CP1 Reporter: Jiri Pechanec See warnings in log 2007-12-20 14:31:20,131 INFO [STDOUT] 1********** Begin Service 1 *********** 2007-12-20 14:31:20,196 INFO [STDOUT] In: Start It Up 2007-12-20 14:31:20,196 INFO [STDOUT] Out: Service 1 Start It Up 2007-12-20 14:31:20,196 INFO [STDOUT] ************ End Service 1 ************ 2007-12-20 14:31:20,406 INFO [org.jboss.soa.esb.services.jbpm.actionhandlers.EsbActionHandler] millisToWaitForResponse is no longer a valid element, please use a jBPM timer for this node instead. 2007-12-20 14:31:20,644 INFO [STDOUT] 2********** Begin Service 2 *********** 2007-12-20 14:31:20,644 INFO [STDOUT] In: Service 1 Start It Up 2007-12-20 14:31:20,645 INFO [STDOUT] Out: Service 2 Service 1 Start It Up 2007-12-20 14:31:20,645 INFO [STDOUT] ************ End Service 2 ************ 2007-12-20 14:31:20,789 INFO [org.jboss.soa.esb.services.jbpm.actionhandlers.EsbActionHandler] millisToWaitForResponse is no longer a valid element, please use a jBPM timer for this node instead. 2007-12-20 14:31:21,020 INFO [STDOUT] 3********** Begin Service 3 *********** 2007-12-20 14:31:21,028 INFO [STDOUT] In: Service 2 Service 1 Start It Up 2007-12-20 14:31:21,028 INFO [STDOUT] Out: Service 3 Service 2 Service 1 Start It Up 2007-12-20 14:31:21,029 INFO [STDOUT] ************ End Service 3 ************ 2007-12-20 14:31:21,184 INFO [STDOUT] Executed by the process, not by the ESB -- 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 months

5
8
0 / 0

[JBoss JIRA] Created: (JBESB-768) Quickstart that demos JMS custom_correlation

by Daniel Bevenius (JIRA)

Quickstart that demos JMS custom_correlation -------------------------------------------- Key: JBESB-768 URL: http://jira.jboss.com/jira/browse/JBESB-768 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Priority: Optional Burr suggested that we add a quickstart that demos a custom correlation using jms. An example could be an application that creates a custom correlation id which it sets on the JMSMessage before posting to the ESB. It then needs to wait for a response and use a selector for that that specific correlation id. This would call for them to create a custom JMSRouter/JMSNotifier. -- 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 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-1545) Need for client JAR for the ServiceInvoker class

by Antonio Souza (JIRA)

Need for client JAR for the ServiceInvoker class ------------------------------------------------ Key: JBESB-1545 URL: http://jira.jboss.com/jira/browse/JBESB-1545 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Environment: Jboss ESB Server 4.2.1 JDK 1.5.0_14 Windows Server 2003 Reporter: Antonio Souza Priority: Minor At the time, one must add server jar jbossesb-rosetta.jar locate under soapui-client.sar to client project in order to use ServiceInvoker class. A client version of this jar must be provided under client directory. -- 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 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues February 2008