November 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2536) jUDDI local transport creates a new thread to handle every individual request

by Kevin Conner (JIRA)

jUDDI local transport creates a new thread to handle every individual request ----------------------------------------------------------------------------- Key: JBESB-2536 URL: https://jira.jboss.org/jira/browse/JBESB-2536 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.5 Reporter: Kevin Conner Fix For: 4.6 There are two classes used in jUDDI for local communication, org.apache.juddi.registry.local.InquiryService and org.apache.juddi.registry.local.PublishService. Every request passing through these classes, and there are many, results in the creation of a thread as follows Thread thread = new Thread(requestHandler, "WorkThread"); thread.start(); thread.join(); This has a big impact on performance. -- 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

16 years, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-2970) AS5 esb deployments should have implicit dependency on jbossesb.esb

by Kevin Conner (JIRA)

AS5 esb deployments should have implicit dependency on jbossesb.esb ------------------------------------------------------------------- Key: JBESB-2970 URL: https://jira.jboss.org/jira/browse/JBESB-2970 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.6 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 I have done this as part of the juddi work, will check in separately. -- 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

16 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2929) Verify operation of quickstarts in as4 and as5 deployments

by Tom Fennelly (JIRA)

Verify operation of quickstarts in as4 and as5 deployments ---------------------------------------------------------- Key: JBESB-2929 URL: https://jira.jboss.org/jira/browse/JBESB-2929 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.5 Reporter: Tom Fennelly Assignee: Kevin Conner 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

16 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-2934) Verify quickstarts helloworld_ftp_action -> helloworld_tx_sql_action

by Tom Fennelly (JIRA)

Verify quickstarts helloworld_ftp_action -> helloworld_tx_sql_action -------------------------------------------------------------------- Key: JBESB-2934 URL: https://jira.jboss.org/jira/browse/JBESB-2934 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.5 Reporter: Tom Fennelly Assignee: David Ward Fix For: 4.6 helloworld_ftp_action helloworld_hibernate_action helloworld_sql_action helloworld_topic_notifier helloworld_tx_sql_action -- 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

16 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-2867) Clean up issues identified in the findbugs report.

by Kevin Conner (JIRA)

Clean up issues identified in the findbugs report. -------------------------------------------------- Key: JBESB-2867 URL: https://jira.jboss.org/jira/browse/JBESB-2867 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.6 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 -- 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

16 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2897) Eliminate /esb-console, make the path /admin-console, change docs

by Tom Cunningham (JIRA)

Eliminate /esb-console, make the path /admin-console, change docs ----------------------------------------------------------------- Key: JBESB-2897 URL: https://jira.jboss.org/jira/browse/JBESB-2897 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.6 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.7 AS 5 ships with a JOPR console that is labeled as jboss5-admin-console.war and that deploys at /admin-console. For consistency, we should do something similar with ESB & AS4, and review the docs to make sure that the docs specify the correct path and war file name. -- 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

16 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-2968) Document jUDDI v3 changes

by Tom Cunningham (JIRA)

Document jUDDI v3 changes ------------------------- Key: JBESB-2968 URL: https://jira.jboss.org/jira/browse/JBESB-2968 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.7 The documentation contains a lot of references to jUDDI v2 configuration. Change these to match jUDDI v3. -- 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

16 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2956) helloworld_tx_sql_action quickstart deploy error on AS 5

by Daniel Bevenius (JIRA)

helloworld_tx_sql_action quickstart deploy error on AS 5 -------------------------------------------------------- Key: JBESB-2956 URL: https://jira.jboss.org/jira/browse/JBESB-2956 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 4.7 When deploying the quickstart the following error is displayed in the console: 15:04:33,294 WARN [HDScanner] Failed to process changes org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): DEPLOYMENTS MISSING DEPENDENCIES: Deployment "jboss.esb.vfszip:/opt/jboss/as/bundles/jboss-5.1.0.GA/server/default/deploy/Quickstart_helloworld_TX_SQL_action.esb/" is missing the following dependencies: Dependency "<UNKNOWN jboss.esb.vfszip:/opt/jboss/as/bundles/jboss-5.1.0.GA/server/default/deploy/Quickstart_helloworld_TX_SQL_action.esb/>" (should be in state "PreInstall", but is actually in state "** UNRESOLVED Demands 'jboss.esb:service=HelloworldTxSqlDatabaseInitializer' **") Deployment "jboss.esb:service=HelloworldTxSqlDatabaseInitializer" is missing the following dependencies: Dependency "jboss.jca:name=HelloworldTxSqlDB,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=HelloworldTxSqlDB,service=DataSourceBinding' **") DEPLOYMENTS IN ERROR: Deployment "<UNKNOWN jboss.esb.vfszip:/opt/jboss/as/bundles/jboss-5.1.0.GA/server/default/deploy/Quickstart_helloworld_TX_SQL_action.esb/>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.esb:service=HelloworldTxSqlDatabaseInitializer' ** Deployment "jboss.jca:name=HelloworldTxSqlDB,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=HelloworldTxSqlDB,service=DataSourceBinding' ** at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993) at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939) at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:369) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:65) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:142) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:166) 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 problem seems to be timing related. What I mean is that this quickstart is similar other quickstart that deploy a database as a part of the .esb deployment. This works well in the others but I think this is just by chance. If you add a JMS queue definition to this quickstart then it will work just fine. I think that the extra time that it take to deploy the queue gives the db enough time to start and be bound. There might be way to add dependencies to this but I've not been succesful doing so. -- 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

16 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-2963) Change JON plugin version

by Kevin Conner (JIRA)

Change JON plugin version ------------------------- Key: JBESB-2963 URL: https://jira.jboss.org/jira/browse/JBESB-2963 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.6 Reporter: Kevin Conner Assignee: Tom Cunningham Fix For: 4.7 Currently configured as 2.3.0-SNAPSHOT. -- 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

16 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2965) HttpRouter action does not propagate exceptions

by Aaron Pestel (JIRA)

HttpRouter action does not propagate exceptions ----------------------------------------------- Key: JBESB-2965 URL: https://jira.jboss.org/jira/browse/JBESB-2965 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.6 Reporter: Aaron Pestel In the process() method of org/jboss/soa/esb/actions/routing/http/HttpRouter.java, lines 140 and 148, it eats exceptions and logs them to stderr. This causes the action chain to continue as if no error occurred. It seems these exceptions should get propagated up. Here's the use case. Create ESB WS Proxy scenario. Client invokes ESB, ESB action invokes HttpRouter action, HttpRouter action is pointing to an endpointUrl that is invalid, instead of propagating the exception up to the ESB service, it eats the exception and continues processing. -- 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

16 years, 5 months

3
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues November 2009