September 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2041) Unclear documentation in Admin guide

by Mark Little (JIRA)

Unclear documentation in Admin guide ------------------------------------ Key: JBESB-2041 URL: https://jira.jboss.org/jira/browse/JBESB-2041 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.4 Reporter: Mark Little Assignee: Mark Little Fix For: 4.4 CP1 >From Darrin Mison: "Someone just pointed this out to me in my draft of the SOA Admin Guide but it exists also in the original ESB Admin Guide Can anyone clarify what the underlined text is supposed to say? Console The console can be found at http://localhost:8080/jbossesb Below is a screenshot of the console. The console requests MBean information from each node within the ESB registry, and then displays it back. Any attribute hat is a processing time a count is shown with a chart and a time sorted list, which all other data is displayed with just a time sorted list." -- 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

17 years, 7 months

4
5
0 / 0

[JBoss JIRA] Created: (JBESB-2028) Service Name / Category / Description should have length constraint

by Tom Cunningham (JIRA)

Service Name / Category / Description should have length constraint ------------------------------------------------------------------- Key: JBESB-2028 URL: https://jira.jboss.org/jira/browse/JBESB-2028 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 Reporter: Tom Cunningham Assignee: Tom Cunningham Service Name / Category and Description should have a length constraint in the XSD or at deployment time - length is limited to 255 characters by the JUDDI SQL. -- 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

17 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2048) Exception thrown during Quickstart business_ruleservice_RuleAgent as standalone

by Kevin Conner (JIRA)

Exception thrown during Quickstart business_ruleservice_RuleAgent as standalone ------------------------------------------------------------------------------- Key: JBESB-2048 URL: https://jira.jboss.org/jira/browse/JBESB-2048 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 Reporter: Kevin Conner Fix For: 4.4 CP1 Running as a standalone ESB deployment results in an exception being thrown as part of the pipeline 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

17 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2047) Merge current jonplugin into CP

by Kevin Conner (JIRA)

Merge current jonplugin into CP ------------------------------- Key: JBESB-2047 URL: https://jira.jboss.org/jira/browse/JBESB-2047 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP1 Pull across revision 22826 from trunk -- 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

17 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1728) Add some unit tests for ESJBProcessor

by Tom Fennelly (JIRA)

Add some unit tests for ESJBProcessor ------------------------------------- Key: JBESB-1728 URL: http://jira.jboss.com/jira/browse/JBESB-1728 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Adapters Reporter: Tom Fennelly -- 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, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-2045) readme for transform_CSV2XML points to old name of reference doc

by Mark Little (JIRA)

readme for transform_CSV2XML points to old name of reference doc ---------------------------------------------------------------- Key: JBESB-2045 URL: https://jira.jboss.org/jira/browse/JBESB-2045 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.4 Reporter: Mark Little Assignee: Mark Little Fix For: 4.4 CP1 -- 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

17 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2044) EJBProcessor should use ClassUtils for loading classes

by Ondrej Skutka (JIRA)

EJBProcessor should use ClassUtils for loading classes ------------------------------------------------------ Key: JBESB-2044 URL: https://jira.jboss.org/jira/browse/JBESB-2044 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Ondrej Skutka Priority: Critical Because of using Class.forName in EJBProcessor.java bad repository is used for loading classes. ClassUtil should be used instead. Please note, that it's used twice in EJBProcessor.java -- 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

17 years, 7 months

2
2
0 / 0

[JBoss JIRA] Commented: (JBESB-1895) Support back slash for windows in installing Jbossesb into JBoss AS.

by Jeff Yu (JIRA)

[ https://jira.jboss.org/jira/browse/JBESB-1895?page=com.atlassian.jira.plu... ] Jeff Yu commented on JBESB-1895: -------------------------------- Not myself, it was from jbossesb users maillist. I copied it here for convenience. -------------------- Tom, It does work. Thanks a lot. Lucy 在2008-08-02，"Tom Fennelly" <tom.fennelly(a)jboss.com> 写道： >Hi Lucy. > >Try setting the org.jboss.esb.server.home to "D:/jboss-4.2.2.GA " i.e. >try using forward slashes. > >Also... please don't cross post on the mailing list :-) > >Regards, > >T. > > >钱宇虹 wrote: >> >> Hi all, >> >> I am having trouble to deloy jbossesb to JBOSS AS. Any help are highly apprieciated : >> >> >> >> >> 1) I use jbossesb-4.3.GA.zip and jboss4.2.2.GA.zip. >> 2) I update the deployment.properties as follows: >> >> >> org.jboss.esb.server.home=D:\jboss-4.2.2.GA >> org.jboss.esb.server.config=default >> >> >> >> After I run "ant" or "ant deploy",I got error messages: Could not determine JMS provider: >> >> details as follows: >> >> D:\jbossesb-4.3.GA\install>ant deploy >> Buildfile: build.xml >> check.deploy.props: >> dependencies.source: >> dependencies.jbossesb: >> dependencies: >> jms.config.check: >> BUILD FAILED >> D:\jbossesb-4.3.GA\install\build.xml:70: Could not determine JMS provider >> Total time: 0 seconds >> >> >> Lucy >> > Support back slash for windows in installing Jbossesb into JBoss AS. > -------------------------------------------------------------------- > > Key: JBESB-1895 > URL: https://jira.jboss.org/jira/browse/JBESB-1895 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build and Release > Affects Versions: 4.3 > Reporter: Jeff Yu > Priority: Trivial > > Step to reproduce: > 1. Open up the deployment.properties in the $install directory, update: > org.jboss.esb.server.home=D:\jboss-4.2.2.GA > 2. Run "ant" or "ant deploy", you will have message: Could not determine JMS provider: > The problem is that we need to use the 'forward slash' instead of 'back slash' in the org.jboss.esb.server.home. It would be better if we provide a capability to support the back slash. -- 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

17 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-1901) Stateful rule service cannot be used in cluster and does not persist its state

by Jiri Pechanec (JIRA)

Stateful rule service cannot be used in cluster and does not persist its state ------------------------------------------------------------------------------ Key: JBESB-1901 URL: https://jira.jboss.org/jira/browse/JBESB-1901 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing, Documentation Affects Versions: 4.4 Reporter: Jiri Pechanec Fix For: 4.4 CP1 If the rule service is stateful and used in cluster it does not guarantee that all messages are processed by the same service instance . As the state is not replicated over the service instances it can break the business logic. This limitation has to be either documented or fixed. Moreover the state of working memory is not persisted in between invocations and thus can be lost in case of crash - which can affect business logic - this limitation must be documented. -- 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

17 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1997) On start, initialiseInstances is called in ManagedLifecycleController

by Tom Cunningham (JIRA)

On start, initialiseInstances is called in ManagedLifecycleController --------------------------------------------------------------------- Key: JBESB-1997 URL: https://jira.jboss.org/jira/browse/JBESB-1997 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.3 Reporter: Tom Cunningham If you stop a service, the message counters should not reset if you start it once again. When we start a service, we are calling initialiseInstances (see ManagedLifecycleController.java:69) which creates a new ActionProcessingPipeline. Shouldn't we be able to use the current ActionProcessingPipeline on a start? -- 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

17 years, 7 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 September 2008