June 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1799) Create JBM sessions from a daemon thread

by Kevin Conner (JIRA)

Create JBM sessions from a daemon thread ---------------------------------------- Key: JBESB-1799 URL: http://jira.jboss.com/jira/browse/JBESB-1799 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 CP3 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 CP3 JBM can create non-daemon background threads for handling sessions if the caller is not a daemon thread. These threads prevent the VM from exiting as our pooling code will not execute the session.close method until the shutdown hook is fired. We must workaround this by creating all JBM sessions on a daemon background thread. -- 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

17 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1800) Add Complex Splitting and Routing Quickstart

by Tom Fennelly (JIRA)

Add Complex Splitting and Routing Quickstart -------------------------------------------- Key: JBESB-1800 URL: http://jira.jboss.com/jira/browse/JBESB-1800 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, Examples Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.4 I have this partly done already. It: 1. Reads in an EDI Order message. User can specify the number of order items, so it can be huge if desired. 2. Reads in the EDI message and filters through it reading out the customer and order details. 3. The customer and order item details from the message are enriched with data from a database. 4. The order items are split out and merged with the order and additional order item data from the DB. 5. Split order item messages below a certain value are routed as XML to the "02_Low_Price" service. 6. Split order item messages above a certain value are routed as Java Objects to the "03_High_Price" service. 7. Split order item messages with a category == "REPTILES" are routed as a SOAP message to the "04_Reptiles_notify_webservice" service, which uses the HttpRouter to route the SOAP message to a webservice. Might also add routing of some of the order items to a DB. Would be good to add some flash demos 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

17 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1811) Add public/private key support to SFTP

by Kevin Conner (JIRA)

Add public/private key support to SFTP -------------------------------------- Key: JBESB-1811 URL: http://jira.jboss.com/jira/browse/JBESB-1811 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.3, 4.2.1 TP-FP1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 TP-FP2, 4.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

17 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1812) Support local configuration of SoapUI

by Kevin Conner (JIRA)

Support local configuration of SoapUI ------------------------------------- Key: JBESB-1812 URL: http://jira.jboss.com/jira/browse/JBESB-1812 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.3, 4.2.1 TP-FP1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 TP-FP2, 4.4 Allow configuration of SoapUI via an embedded config file an allow the specification of a directory for including additional schema. -- 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

17 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1791) SoapUIClientService not setting the OGNL expression attribute when the clone point is the element itself and there's only a single collection entrry

by Tom Fennelly (JIRA)

SoapUIClientService not setting the OGNL expression attribute when the clone point is the element itself and there's only a single collection entrry ---------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBESB-1791 URL: http://jira.jboss.com/jira/browse/JBESB-1791 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.3, 4.2.1 CP2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2.1 CP3, 4.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

17 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1798) Error message for Notifier is misleading if exception is thrown in Notifier class constructor

by Jiri Pechanec (JIRA)

Error message for Notifier is misleading if exception is thrown in Notifier class constructor --------------------------------------------------------------------------------------------- Key: JBESB-1798 URL: http://jira.jboss.com/jira/browse/JBESB-1798 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Reporter: Jiri Pechanec See log file 14:17:19,281 ERROR [STDERR] java.lang.reflect.InvocationTargetException 14:17:19,281 ERROR [STDERR] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Met hod) 14:17:19,281 ERROR [STDERR] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConst ructorAccessorImpl.java:39) 14:17:19,281 ERROR [STDERR] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Delegat ingConstructorAccessorImpl.java:27) 14:17:19,281 ERROR [STDERR] at java.lang.reflect.Constructor.newInstance(Constructor.java:494) 14:17:19,281 ERROR [STDERR] at org.jboss.soa.esb.notification.NotificationTarget.fromParams(Noti ficationTarget.java:144) 14:17:19,281 ERROR [STDERR] at org.jboss.soa.esb.notification.NotificationList.notifyAll(Notific ationList.java:162) 14:17:19,281 ERROR [STDERR] at org.jboss.soa.esb.actions.Notifier.notifyOK(Notifier.java:93) 14:17:19,282 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 14:17:19,282 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorI mpl.java:39) 14:17:19,282 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodA ccessorImpl.java:25) 14:17:19,282 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585) 14:17:19,282 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.pro cessSuccess(ActionProcessorMethodInfo.java:165) 14:17:19,282 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProc essor.processSuccess(OverriddenActionLifecycleProcessor.java:108) 14:17:19,282 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.noti fySuccess(ActionProcessingPipeline.java:610) 14:17:19,282 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.proc ess(ActionProcessingPipeline.java:384) 14:17:19,282 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.MessageAwareListener$Transact ionalRunner.run(MessageAwareListener.java:530) 14:17:19,282 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPool Executor.java:650) 14:17:19,282 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExec utor.java:675) 14:17:19,282 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595) 14:17:19,282 ERROR [STDERR] Caused by: org.jboss.internal.soa.esb.rosetta.pooling.ConnectionExceptio n: Unexpected exception accessing Naming Context 14:17:19,282 ERROR [STDERR] at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getS ession(JmsConnectionPool.java:165) 14:17:19,282 ERROR [STDERR] at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getS ession(JmsConnectionPool.java:229) 14:17:19,282 ERROR [STDERR] at org.jboss.soa.esb.notification.NotifyJMS.setUpProducers(NotifyJMS .java:403) 14:17:19,282 ERROR [STDERR] at org.jboss.soa.esb.notification.NotifyQueues.<init>(NotifyQueues.java:71) 14:17:19,282 ERROR [STDERR] ... 19 more 14:17:19,283 ERROR [STDERR] Caused by: org.jboss.soa.esb.helpers.NamingContextException: Failed to c reate Naming Context 14:17:19,283 ERROR [STDERR] at org.jboss.soa.esb.helpers.NamingContextPool.createContext(NamingC ontextPool.java:358) 14:17:19,283 ERROR [STDERR] at org.jboss.soa.esb.helpers.NamingContextPool.getContext(NamingCont extPool.java:296) 14:17:19,283 ERROR [STDERR] at org.jboss.soa.esb.helpers.NamingContextPool.getContext(NamingCont extPool.java:151) 14:17:19,283 ERROR [STDERR] at org.jboss.soa.esb.helpers.NamingContextPool.getNamingContext(Nami ngContextPool.java:402) 14:17:19,283 ERROR [STDERR] at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.init Connection(JmsConnectionPool.java:408) 14:17:19,283 ERROR [STDERR] at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getS ession(JmsConnectionPool.java:163) 14:17:19,283 ERROR [STDERR] ... 22 more 14:17:19,283 ERROR [STDERR] Caused by: javax.naming.CommunicationException: Could not obtain connect ion to any of these urls: localhost:7222 and discovery failed with error: javax.naming.Communication Exception: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to retrieve stub from server localhos t:7222 [Root exception is java.io.StreamCorruptedException: invalid stream header]] 14:17:19,289 ERROR [STDERR] at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1562 ) 14:17:19,289 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:634) 14:17:19,289 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627) 14:17:19,289 ERROR [STDERR] at javax.naming.InitialContext.lookup(InitialContext.java:351) 14:17:19,289 ERROR [STDERR] at org.jboss.soa.esb.helpers.NamingContextPool.createContext(NamingC ontextPool.java:342) 14:17:19,289 ERROR [STDERR] ... 27 more 14:17:19,289 ERROR [STDERR] Caused by: javax.naming.CommunicationException: Failed to retrieve stub from server localhost:7222 [Root exception is java.io.StreamCorruptedException: invalid stream heade r] 14:17:19,289 ERROR [STDERR] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:268 ) 14:17:19,289 ERROR [STDERR] at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1533 ) 14:17:19,289 ERROR [STDERR] ... 31 more 14:17:19,289 ERROR [STDERR] Caused by: java.io.StreamCorruptedException: invalid stream header 14:17:19,290 ERROR [STDERR] at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java :764) 14:17:19,290 ERROR [STDERR] at java.io.ObjectInputStream.<init>(ObjectInputStream.java:277) 14:17:19,290 ERROR [STDERR] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:255 ) 14:17:19,290 ERROR [STDERR] ... 32 more 14:17:19,298 ERROR [NotificationList] Can't instantiate target <target class="NotifyQueues"> <messageProp name="quetest" value="some test property"/> <queue jndi-URL="localhost:7222" jndiName="QUICKSTART_NOTIFIER_QUETEST_GW"> </queue> </target> org.jboss.soa.esb.ConfigurationException: NotifyQueues does not extend NotificationTarget at org.jboss.soa.esb.notification.NotificationTarget.fromParams(NotificationTarget.java:151) at org.jboss.soa.esb.notification.NotificationList.notifyAll(NotificationList.java:162) at org.jboss.soa.esb.actions.Notifier.notifyOK(Notifier.java:93) 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.processSuccess(ActionProces sorMethodInfo.java:165) at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.processSuccess(Ove rriddenActionLifecycleProcessor.java:108) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.notifySuccess(ActionProcessi ngPipeline.java:610) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipe line.java:384) at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageA wareListener.java:530) 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) The issue is caused by the code from NotificationTarget.java Object oRet = null; try { oRet = oCons.newInstance(new Object[] { p_oP }); } catch (Exception e) { e.printStackTrace(); } if (null == oRet || (!(oRet instanceof NotificationTarget))) throw new ConfigurationException(sClass + " does not extend NotificationTarget"); return (NotificationTarget) oRet; The problem is that for some Notifiers it is allowed to throw exception in constructor (e.g. NotifyQueue) and in such case the variable oRet has still value set to null but it is due to completely different reason then that class is not subclass of NotificationTarget. -- 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

17 years, 9 months

4
7
0 / 0

[JBoss JIRA] Created: (JBESB-1788) JTATransactionStrategy logs too much information when debug is enabled

by Kevin Conner (JIRA)

JTATransactionStrategy logs too much information when debug is enabled ---------------------------------------------------------------------- Key: JBESB-1788 URL: http://jira.jboss.com/jira/browse/JBESB-1788 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 CP2 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 CP3 -- 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

17 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1786) Disable run target in bpm_orchestration2

by Kevin Conner (JIRA)

Disable run target in bpm_orchestration2 ---------------------------------------- Key: JBESB-1786 URL: http://jira.jboss.com/jira/browse/JBESB-1786 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP2 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 CP3 -- 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

17 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1785) SOAPClient: Process method should assert that parameter payload is a Map

by Tom Fennelly (JIRA)

SOAPClient: Process method should assert that parameter payload is a Map ------------------------------------------------------------------------ Key: JBESB-1785 URL: http://jira.jboss.com/jira/browse/JBESB-1785 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.3, 4.2.1 TP-FP1, 4.2.1 CP2 Reporter: Tom Fennelly Fix For: 4.2.1 CP3 At the moment, the user is just getting a cast exception. -- 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

17 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1776) Tidy up quickstart DB dependencies and make sure they can run together

by Kevin Conner (JIRA)

Tidy up quickstart DB dependencies and make sure they can run together ---------------------------------------------------------------------- Key: JBESB-1776 URL: http://jira.jboss.com/jira/browse/JBESB-1776 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP2 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 CP3 This is the CP task associated with JBESB-1762 -- 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

17 years, 9 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues June 2008