March 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2459) Concurrent access in ESB Quartz Scheduler initialization

by Jiri Pechanec (JIRA)

Concurrent access in ESB Quartz Scheduler initialization -------------------------------------------------------- Key: JBESB-2459 URL: https://jira.jboss.org/jira/browse/JBESB-2459 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 CP2 Reporter: Jiri Pechanec Assignee: Kevin Conner Attachments: exs.log.gz I placed all Seam examples to deploy dir and started the server, I got the following exception during the startup 2009-03-09 11:34:20,945 INFO [org.quartz.core.QuartzScheduler] Quartz Scheduler v.1.5.2 created. 2009-03-09 11:34:20,945 INFO [org.quartz.simpl.RAMJobStore] RAMJobStore initialized. 2009-03-09 11:34:20,945 INFO [org.quartz.impl.StdSchedulerFactory] Quartz scheduler 'ESBScheduler:jbossesb.esb' initialized from an externally provided properties instance. 2009-03-09 11:34:20,945 INFO [org.quartz.impl.StdSchedulerFactory] Quartz scheduler version: 1.5.2 2009-03-09 11:34:20,945 INFO [org.quartz.core.QuartzScheduler] Scheduler ESBScheduler:jbossesb.esb_$_NON_CLUSTERED started. 2009-03-09 11:34:21,087 INFO [org.quartz.core.JobRunShell] Job ESBScheduler.ESBJob1 threw a JobExecutionException: org.quartz.JobExecutionException: Unexpected exception on ESBJob1 at org.jboss.soa.esb.schedule.SchedulerJob$ESBScheduledJob.execute(SchedulerJob.java:299) at org.quartz.core.JobRunShell.run(JobRunShell.java:203) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520) Caused by: java.util.ConcurrentModificationException at java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1031) at java.util.TreeMap$KeyIterator.next(TreeMap.java:1058) at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:235) at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:514) at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:408) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at org.jboss.internal.soa.esb.message.format.xml.MessageImpl.<init>(MessageImpl.java:78) at org.jboss.internal.soa.esb.message.format.xml.XMLMessagePlugin.getMessage(XMLMessagePlugin.java:46) at org.jboss.internal.soa.esb.message.format.MessageFactoryImpl.getMessage(MessageFactoryImpl.java:109) at org.jboss.soa.esb.schedule.RedeliverEventMessageComposer.composeMessage(RedeliverEventMessageComposer.java:25) at org.jboss.soa.esb.listeners.ScheduleListener.onSchedule(ScheduleListener.java:118) at org.jboss.soa.esb.listeners.lifecycle.AbstractScheduledManagedLifecycle$1.onSchedule(AbstractScheduledManagedLifecycle.java:68) at org.jboss.soa.esb.schedule.SchedulerJob$ESBScheduledJob.execute(SchedulerJob.java:289) ... 2 more Unfortunately it is very very very rare to generate it twice. Full log is attached -- 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, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2401) FileGatewayListener: Does not support overwriting of processed files.

by Daniel Bevenius (JIRA)

FileGatewayListener: Does not support overwriting of processed files. --------------------------------------------------------------------- Key: JBESB-2401 URL: https://jira.jboss.org/jira/browse/JBESB-2401 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.5 Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 4.6 In version 4.3 it was possible to have the processed file overwritten when a new file with the same name is later processed. This was possible as FileUtil previously first tried to rename the file but if it was unsuccessful it would copy the contents of the new file to the old replacing its content. Add a test that verifies that the file contents is overwritten and not only that the file was renamed so we can maintain this -- 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, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2453) soapUI SOAP client: Remove "empty" elements

by Tom Fennelly (JIRA)

soapUI SOAP client: Remove "empty" elements ------------------------------------------- Key: JBESB-2453 URL: https://jira.jboss.org/jira/browse/JBESB-2453 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.5 Reporter: Tom Fennelly Fix For: 4.x This is a contribution from Kurt Stam. This is a mod to SoapUIClientService that automatically removes elements for which there are no values in the supplied data model. As Kurt pointed out... we may need to make it more configurable e.g. turn it off by default... add some control of which message elements are removed when empty etc. The change was to the injectParameters() method: private void injectParameters(Element element, Map params, String soapNs) { NodeList children = element.getChildNodes(); int childCount = children.getLength(); for (int i = 0; i < childCount; i++) { Node node = children.item(i); if (childCount == 1 && node.getNodeType() == Node.TEXT_NODE) { if (node.getTextContent().equals("?")) { String ognl = OGNLUtils.getOGNLExpression(element, soapNs); Object param; param = OGNLUtils.getParameter(ognl, params); element.removeChild(node); if (! "".equals(param)) { element.appendChild(element.getOwnerDocument().createTextNode(param.toString())); } else { element.getParentNode().removeChild(element); } } } else if (node!=null && node.getNodeType() == Node.ELEMENT_NODE) { injectParameters((Element) node, params, soapNs); } } element.removeAttributeNS(OGNLUtils.JBOSSESB_SOAP_NS, IS_CLONE_ATTRIB); element.removeAttributeNS(OGNLUtils.JBOSSESB_SOAP_NS, OGNLUtils.OGNL_ATTRIB); } -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-1646) Add support for making schedule-provider Jobs clusterable

by Tom Fennelly (JIRA)

Add support for making schedule-provider Jobs clusterable --------------------------------------------------------- Key: JBESB-1646 URL: http://jira.jboss.com/jira/browse/JBESB-1646 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Reporter: Tom Fennelly This should support "singleton" execution of a job in a clustered env, with fail-over etc. See http://java-x.blogspot.com/2006/12/using-quartz-scheduler-in-cluster.html -- 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

15 years, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (JBESB-2203) Duplicate service names during cluster startup

by Joakim Sandström (JIRA)

Duplicate service names during cluster startup ---------------------------------------------- Key: JBESB-2203 URL: https://jira.jboss.org/jira/browse/JBESB-2203 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.4 Environment: jboss esb cluster, replicated mysql 5.1. Reporter: Joakim Sandström If I startup more than one cluster node at the same time when uddi is empty it will be populated as follows: -Service A -- node1 EPR -Service A -- node2 EPR Expected uddi content; -Service A --node1 EPR --node2 EPR The esb cluster nodes access the same mysq node (transaction READ_COMMITTED). -- 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, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-2451) SoapUIClientService: not handling nested collections properly

by Tom Fennelly (JIRA)

SoapUIClientService: not handling nested collections properly ------------------------------------------------------------- Key: JBESB-2451 URL: https://jira.jboss.org/jira/browse/JBESB-2451 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.5 Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.6 -- 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, 2 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues March 2009