June 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1848) bpm_orchestration1 quickstart is broken

by Lukas Petrovicky (JIRA)

bpm_orchestration1 quickstart is broken --------------------------------------- Key: JBESB-1848 URL: http://jira.jboss.com/jira/browse/JBESB-1848 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 CP4 Reporter: Lukas Petrovicky Deploying a process ends with the following message: deployProcess: [echo] Deploy the process definition [deployToServer] java.io.FileNotFoundException: http://localhost:8080/jbpm-console/upload/ [deployToServer] at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1168) [deployToServer] at org.jbpm.ant.DeployProcessToServerTask.pingServerOK(DeployProcessToServerTask.java:315) [deployToServer] at org.jbpm.ant.DeployProcessToServerTask.execute(DeployProcessToServerTask.java:127) [deployToServer] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) [deployToServer] at org.apache.tools.ant.Task.perform(Task.java:364) [deployToServer] at org.apache.tools.ant.Target.execute(Target.java:341) [deployToServer] at org.apache.tools.ant.Target.performTasks(Target.java:369) [deployToServer] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) [deployToServer] at org.apache.tools.ant.Project.executeTarget(Project.java:1185) [deployToServer] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40) [deployToServer] at org.apache.tools.ant.Project.executeTargets(Project.java:1068) [deployToServer] at org.apache.tools.ant.Main.runBuild(Main.java:668) [deployToServer] at org.apache.tools.ant.Main.startAnt(Main.java:187) [deployToServer] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246) [deployToServer] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67) [deployToServer] An unexpected exception happened while testing the server (http://localhost:8080/jbpm-console/upload/) connection. -- 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

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1846) Add 'DO NOT reformat code' text to Developer.txt

by Mark Little (JIRA)

Add 'DO NOT reformat code' text to Developer.txt ------------------------------------------------ Key: JBESB-1846 URL: http://jira.jboss.com/jira/browse/JBESB-1846 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.3 Reporter: Mark Little Assigned To: Mark Little Priority: Trivial Fix For: 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

16 years

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1845) Reduce default logging for jbossesb-server

by Daniel Bevenius (JIRA)

Reduce default logging for jbossesb-server ------------------------------------------ Key: JBESB-1845 URL: http://jira.jboss.com/jira/browse/JBESB-1845 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.4 Reporter: Daniel Bevenius Fix For: 4.x By default the logging level for many components is set to the default log level. This can cause a lot of noice in the servers log. I think we can be restrictive and perhaps set the following to error log level: org.jbpm org.hibernate -- 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

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-1153) File Gateway: Consume only a single file at a time

by Burr Sutter (JIRA)

File Gateway: Consume only a single file at a time -------------------------------------------------- Key: JBESB-1153 URL: http://jira.jboss.com/jira/browse/JBESB-1153 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2 Reporter: Burr Sutter Assigned To: Mark Little Fix For: 4.3 The current File gateway consumes files at a rate faster than the internal/native listener (typically JMS-based) and its associated action chain. This request is for a configuration property that causes the rate of consumption of the file gateway to match the underlying internal/native listener. Basically a file would not be pulled from disk until it has completely passed through the action chain. Here are some notes related to this use case: I have 1000+ files which are very huge in size and when all the files are kept in the folder they are read at same time and placed in configured JMS Queue. - When all the files are placed in Queue there is a chance that the size of messages in Queue may exceed and it may not accept new messages? Or - Sometimes the case may be like the input folder is monitored by one person and the message processing is monitored by other person. In this case when all the files are read at once it gives a wrong assumption that all files are processed but where as due to some application failure the messages may still be in queue. Or - Its always a good option to be able to see how many messages are still in process in the folder rather than browsing the JMS queue and looking for Queue depth. In this case if you look at Queue depth sometimes it may be give you wrong count of messages as there is a chance that some other application also put message some messages into the same queue, when Queue is configured for application sharing. Or - If you want to replace a single file out of 1000+ files in the input folder while in middle of processing the files, it will be easy if the files are read one at a time rather going and deleting the messages from JMS queue after they are read at once and placed in Queue. -- 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

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-726) JCR Message repository does not support classification and delivery earmark

by Jiri Pechanec (JIRA)

JCR Message repository does not support classification and delivery earmark --------------------------------------------------------------------------- Key: JBESB-726 URL: http://jira.jboss.com/jira/browse/JBESB-726 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 3 Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Minor JCR Message repository currently does not support classification and delivery flag. Proposed solution 1) Add special property under which the classification will be stored 2) Add special property under which delivery earmark will be stored 3) Implement all get<Collection> actions as JCR query and return the results -- 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

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-1714) helloworld_sql_action QS has a missing dependency on the database initialiser MBean

by Kevin Conner (JIRA)

helloworld_sql_action QS has a missing dependency on the database initialiser MBean ----------------------------------------------------------------------------------- Key: JBESB-1714 URL: http://jira.jboss.com/jira/browse/JBESB-1714 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 Reporter: Kevin Conner Fix For: 4.4 The helloworld_sal_action has a race on deployment, leasing to the following output 15:30:12,330 ERROR [SimpleDataSource] Could not create connection for jdbc:hsqldb:hsql://localhost:1703 - datasource may be unavailable. See server log for details. There are a couple of issues - the datasource is explicitly copied into the deploy directory, whereas it should be included within the ear file - there is no dependency on the database initialiser MBean -- 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

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1682) Fix helloworld_file_notifier QS

by Tom Cunningham (JIRA)

Fix helloworld_file_notifier QS ------------------------------- Key: JBESB-1682 URL: http://jira.jboss.com/jira/browse/JBESB-1682 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP2 Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.3 Fix the helloworld_notify_files QS so that it uses the new property substitution that was added in JBESB-1589. There's no longer any need to do the ant based token replacement in this 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

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1644) Create a task that illustrates the use of FaultTo

by Mark Little (JIRA)

Create a task that illustrates the use of FaultTo ------------------------------------------------- Key: JBESB-1644 URL: http://jira.jboss.com/jira/browse/JBESB-1644 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP2 Reporter: Mark Little Fix For: 4.3 -- 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

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1796) Memory Leak in Content Based Router

by Maurice Zeijen (JIRA)

Memory Leak in Content Based Router ----------------------------------- Key: JBESB-1796 URL: http://jira.jboss.com/jira/browse/JBESB-1796 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.2.1 CP3, 4.3 Environment: Java 1.5 or 6.0 JBoss 4.2.2 GA JBoss ESB 4.2.1 or 4.3 Memory settings: -Xms256m -Xmx256m -XX:MaxPermSize=128m Reporter: Maurice Zeijen Attachments: memory_leak_cbr.zip may have found a memory leak in the Content Based Router in both JBoss ESB 4.2.1 and 4.3. I noticed the problem at my Job with a production JBoss ESB 4.2.1 CP2 because it regularly crashed because the memory run out. After doing some memory analysis I found that the problem was with the content based router. To reliably reproduce the problem I created a sample project using the simple_cbr sample. I attached the sample project to this issueu. I also included an export from a memory analysis of a memory dump. In that dump you can clearly see that the org.drools.base.FireAllRulesRuleBaseUpdateListener objects are piling up. Because the problem is within Drools I am not sure if the problem is really in the ESB. Simply unpack the project within the sample/quickstarts directoy to make it work. -- 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

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-549) Automate war deployment for quickstarts

by Kevin Conner (JIRA)

Automate war deployment for quickstarts --------------------------------------- Key: JBESB-549 URL: http://jira.jboss.com/jira/browse/JBESB-549 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 We need to be able to automatically deploy the QSes into a war deployment. The main blocker for this issue is the new requirement to merge jboss-esb.xml configuration files. This is required because of the ESB internal services. -- 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

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues June 2008