August 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-794) The getting started guide has spelling and minor grammar errors, technical inaccuracies and is not self consistent.

by Ryan Ovrevik (JIRA)

The getting started guide has spelling and minor grammar errors, technical inaccuracies and is not self consistent. -------------------------------------------------------------------------------------------------------------------- Key: JBESB-794 URL: http://jira.jboss.com/jira/browse/JBESB-794 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Environment: Windows XP, java version "1.5.0_12" Reporter: Ryan Ovrevik Assigned To: Mark Little Priority: Minor Inconsistent use of JBossESB ((the) ESB/JbossESB/Jboss ESB). Use of Fonts is inconsistent. Directory hierarchy trees are inconsistent with distribution. Broken hyperlinks. -- 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

18 years, 7 months

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-886) Configurable ack pattern from JMS

by Mark Little (JIRA)

Configurable ack pattern from JMS --------------------------------- Key: JBESB-886 URL: http://jira.jboss.com/jira/browse/JBESB-886 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.1 >From Burr: "Why is that when we pull a message from a JMS queue via the JMS gateway that we use "auto-ack" instead of "client-ack"? Therefore, if our action chain that is processing the message dies (the JVM in which it is running dies) then the message is lost." -- 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

18 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-950) SmooksTransformerUnitTest generates errors indicating it should be an integration test

by Mark Little (JIRA)

SmooksTransformerUnitTest generates errors indicating it should be an integration test -------------------------------------------------------------------------------------- Key: JBESB-950 URL: http://jira.jboss.com/jira/browse/JBESB-950 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples, Transformation Service Reporter: Mark Little Assigned To: Tom Fennelly Fix For: 4.2.1 For example: 13:11:12,339 DEBUG [main][NamingContext] Failed to connect to localhost:1099 [java] [junit] javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]] [java] [junit] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:269) [java] [junit] at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1385) [java] [junit] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:594) [java] [junit] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587) [java] [junit] at javax.naming.InitialContext.lookup(InitialContext.java:351) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.getJmsConnectionFactory(SmooksInstanceManager.java:142) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.connect(SmooksInstanceManager.java:186) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.<init>(SmooksInstanceManager.java:105) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.<init>(SmooksInstanceManager.java:92) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager.<init>(SmooksInstanceManager.java:67) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformer.initialiseLocalSmooksInstanceManager(SmooksTransformer.java:240) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformer.initialise(SmooksTransformer.java:222) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformerUnitTest.transform(SmooksTransformerUnitTest.java:82) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformerUnitTest.test_trans(SmooksTransformerUnitTest.java:69) [java] [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) and: [java] [junit] 12:31:51,155 ERROR [main][SmooksInstanceManager] Lookup of the JMS ConnectionFactory failed for the Transformation configuration Update Listener. Update listener not enabled! [java] [junit] org.jboss.soa.esb.ConfigurationException: JNDI lookup of JMS Connection Factory [ConnectionFactory] failed. [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.getJmsConnectionFactory(SmooksInstanceManager.java:144) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.connect(SmooksInstanceManager.java:186) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.<init>(SmooksInstanceManager.java:105) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.<init>(SmooksInstanceManager.java:92) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager.<init>(SmooksInstanceManager.java:67) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformer.initialiseLocalSmooksInstanceManager(SmooksTransformer.java:240) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformer.initialise(SmooksTransformer.java:222) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformerUnitTest.transform(SmooksTransformerUnitTest.java:82) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformerUnitTest.test_trans(SmooksTransformerUnitTest.java:73) [java] [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [java] [junit] at java.lang.reflect.Method.invoke(Method.java:585) -- 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

18 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-920) MessageFilter QuickStart fails deploying to ESB Server

by Tom Cunningham (JIRA)

MessageFilter QuickStart fails deploying to ESB Server ------------------------------------------------------ Key: JBESB-920 URL: http://jira.jboss.com/jira/browse/JBESB-920 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Reporter: Tom Cunningham Assigned To: Mark Little Fix For: 4.2 MessageFilter Quickstart fails deploying to the ESB Server. I'm unsure about what the requirements are for this QS, but there's nothing in the readme.txt saying that it has to deploy to JBoss AS. 09:01:06,494 WARN [ServiceController] Problem starting service jboss.esb:deployment=Quickstart_messagefilter.esb org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Error configuring action processing pipeline at org.jboss.soa.esb.listeners.message.MessageAwareListener.doInitialise(MessageAwareListener.java:176) at org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.initialise(AbstractManagedLifecycle.java:133) at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.initialiseInstances(ManagedLifecycleController.java:163) at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.start(ManagedLifecycleController.java:82) at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startService(JBoss4ESBDeployment.java:79) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) 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.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.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor20.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 org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) Caused by: org.jboss.soa.esb.ConfigurationException: Unexpected exception while instantiating action instance at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.getActionClassInstance(ActionProcessorMethodInfo.java:348) at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.getActionClassInstance(ActionProcessorMethodInfo.java:329) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.<init>(ActionProcessingPipeline.java:140) at org.jboss.soa.esb.listeners.message.MessageAwareListener.doInitialise(MessageAwareListener.java:171) ... 52 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.getActionClassInstance(ActionProcessorMethodInfo.java:344) ... 55 more Caused by: org.jboss.soa.esb.ConfigurationException: Problems with object path list at org.jboss.soa.esb.actions.ContentBasedWiretap.checkMyParms(ContentBasedWiretap.java:222) at org.jboss.soa.esb.actions.ContentBasedWiretap.<init>(ContentBasedWiretap.java:70) at org.jboss.soa.esb.actions.ContentBasedRouter.<init>(ContentBasedRouter.java:39) at org.jboss.soa.esb.actions.MessageFilter.<init>(MessageFilter.java:48) ... 60 more Caused by: org.jboss.soa.esb.ConfigurationException: Required configuration property 'esb' not defined on configuration 'object-path'. at org.jboss.soa.esb.helpers.ConfigTree.getRequiredAttribute(ConfigTree.java:242) at org.jboss.soa.esb.actions.ContentBasedWiretap.checkMyParms(ContentBasedWiretap.java:218) ... 63 more 09:01:06,547 ERROR [URLDeploymentScanner] Incomplete Deployment listing: --- MBeans waiting for other MBeans --- ObjectName: jboss.esb:deployment=Quickstart_messagefilter.esb State: FAILED Reason: org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Error configuring action processing pipeline I Depend On: jboss.esb:deployment=jbrules.esb jboss.esb.quickstart.destination:service=Queue,name=quickstart_messagefilter_Request_esb jboss.esb.quickstart.destination:service=Queue,name=quickstart_messagefilter_Request_gw jboss.esb.quickstart.destination:service=Queue,name=quickstart_messagefilter_next_Request_esb --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.esb:deployment=Quickstart_messagefilter.esb State: FAILED Reason: org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Error configuring action processing pipeline I Depend On: jboss.esb:deployment=jbrules.esb jboss.esb.quickstart.destination:service=Queue,name=quickstart_messagefilter_Request_esb jboss.esb.quickstart.destination:service=Queue,name=quickstart_messagefilter_Request_gw jboss.esb.quickstart.destination:service=Queue,name=quickstart_messagefilter_next_Request_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

18 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-953) quickstart base-build.xml contains relative path references.

by Kevin Conner (JIRA)

quickstart base-build.xml contains relative path references. ------------------------------------------------------------ Key: JBESB-953 URL: http://jira.jboss.com/jira/browse/JBESB-953 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Milestone Release 3 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 The quickstart base-build.xml file contains relative file references. These prevent the base-build.xml being used in QSes external to the distributed hierarchy (such as through the eclipse plugin). -- 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

18 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-944) ObjectMapper does not handle qualified property names.

by Kevin Conner (JIRA)

ObjectMapper does not handle qualified property names. ------------------------------------------------------ Key: JBESB-944 URL: http://jira.jboss.com/jira/browse/JBESB-944 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2 Milestone Release 3 Reporter: Kevin Conner Assigned To: Kevin Conner Priority: Critical Fix For: 4.2 The ObjectMapper class maps between parts of the message and the contents but it assumes that the name is not qualified. Unfortunately many properties/body objects use qualified names (e.g. org.jboss.soa.esb.message.time.dod). -- 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

18 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-946) Security implications of changing ReplyTo, FaultTo etc.

by Mark Little (JIRA)

Security implications of changing ReplyTo, FaultTo etc. ------------------------------------------------------- Key: JBESB-946 URL: http://jira.jboss.com/jira/browse/JBESB-946 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little Fix For: 5.0 We need to consider the security implications of allowing senders of responses to change the incoming header data structure. -- 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

18 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-721) Failure on redeployment of helloworld_hibernate_action

by Kevin Conner (JIRA)

Failure on redeployment of helloworld_hibernate_action ------------------------------------------------------ Key: JBESB-721 URL: http://jira.jboss.com/jira/browse/JBESB-721 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Milestone Release 3 Reporter: Kevin Conner Assigned To: Mark Little Fix For: 4.2 Redeployment of the helloworld_hibernate_action QS causes a null pointer exception in the repository classloader. The reason for this is that a reference to the detached classloader is still being used after undeploy. To reproduce, deploy, undeploy, deploy then view http://localhost:8080/hibernateaction/list.jsp -- 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

18 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-930) Remember to change version in root build.xml

by Mark Little (JIRA)

Remember to change version in root build.xml -------------------------------------------- Key: JBESB-930 URL: http://jira.jboss.com/jira/browse/JBESB-930 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Release Process Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Kevin Conner Priority: Blocker Fix For: 4.2 Currently set at MR3. -- 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

18 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-774) helloworld_hibernate_action - ClassCastException

by Jaroslaw Kijanowski (JIRA)

helloworld_hibernate_action - ClassCastException ------------------------------------------------ Key: JBESB-774 URL: http://jira.jboss.com/jira/browse/JBESB-774 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Milestone Release 3 Reporter: Jaroslaw Kijanowski Assigned To: Mark Little Changed in jboss-esb.xml the "event" property in hibernate-message-filter to "onSave", added one item through insert.jsp: 14:05:47,431 INFO [STDOUT] onSave 14:05:47,443 INFO [STDOUT] Hibernate: insert into orders (product, quantity, price) values (?, ?, ?) 14:05:47,460 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 14:05:47,460 WARN [ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline org.jboss.soa.esb.actions.ActionProcessingException: Unexpected invocation target exception from processor at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:127) at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:262) at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:297) 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) Caused by: java.lang.ClassCastException: org.jboss.soa.esb.samples.quickstart.hibernateaction.Order at org.jboss.soa.esb.samples.quickstart.hibernateaction.MyAction.displayMessage(MyAction.java:52) 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.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102) ... 6 more 14:05:47,461 WARN [ActionProcessingPipeline] No fault address defined for fault message! 14:05:47,526 INFO [STDOUT] Hibernate: select order0_.unique_id as unique1_20_, order0_.product as product20_, order0_.quantity as quantity20_, order0_.price as price20_ from orders order0_ 14:05:47,528 INFO [STDOUT] onLoad -- 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

18 years, 8 months

3
7
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues August 2007