May 2014 - esb-issues - Jboss List Archives

[JBoss JIRA] (JBESB-3968) Eliminate (avg) metrics, make message counts trendsup

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3968?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3968: ---------------------------------- Affects Version/s: 4.12 > Eliminate (avg) metrics, make message counts trendsup > ----------------------------------------------------- > > Key: JBESB-3968 > URL: https://issues.jboss.org/browse/JBESB-3968 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tooling > Affects Versions: 4.12 > Reporter: Tom Cunningham > > Eliminate (avg) message count metrics, make Message Counts themselves trendsup. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (JBESB-3968) Eliminate (avg) metrics, make message counts trendsup

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3968?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3968: ---------------------------------- Component/s: Tooling > Eliminate (avg) metrics, make message counts trendsup > ----------------------------------------------------- > > Key: JBESB-3968 > URL: https://issues.jboss.org/browse/JBESB-3968 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tooling > Affects Versions: 4.12 > Reporter: Tom Cunningham > > Eliminate (avg) message count metrics, make Message Counts themselves trendsup. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (JBESB-3968) Eliminate (avg) metrics, make message counts trendsup

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3968: ------------------------------------- Summary: Eliminate (avg) metrics, make message counts trendsup Key: JBESB-3968 URL: https://issues.jboss.org/browse/JBESB-3968 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Tom Cunningham Eliminate (avg) message count metrics, make Message Counts themselves trendsup. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (JBESB-3821) Camel gateway classes are not loaded by deployer after VFS cache expiration

by Robert Balent (JIRA)

[ https://issues.jboss.org/browse/JBESB-3821?page=com.atlassian.jira.plugin... ] Robert Balent closed JBESB-3821. -------------------------------- Resolution: Done Resolved - see bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=780334 > Camel gateway classes are not loaded by deployer after VFS cache expiration > --------------------------------------------------------------------------- > > Key: JBESB-3821 > URL: https://issues.jboss.org/browse/JBESB-3821 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Deployment, Rosetta > Affects Versions: 4.11 > Environment: SOA-P 5.2 and later > Reporter: Robert Balent > > There is ESB deployer in JBoss SOA-P platform. When ESB application is deployed, libraries from directory esb.deployer/lib should be available for application. > Problem occurs when VFS Cache expires and therefore classes are not loaded for one SOA-P component. It is specifically Camel component[1]. Timeout is in default set to 30 minutes (could be changed). After 30 minutes the ESB application is deployed, but when application tries to use library from esb.deployer/lib directory, it fails. If it's needed to use library at deployment time, it will fail too. > This problem is tracked in SOA-2743 and then continues in bugzilla[2]. There are also attached logs and reproducer for this problem. > [1] https://community.jboss.org/wiki/CamelGateway > [2] https://bugzilla.redhat.com/show_bug.cgi?id=780334 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (JBESB-3967) Single deployment method for JARs and KARs in a distributed fabric

by Susan Javurek (JIRA)

[ https://issues.jboss.org/browse/JBESB-3967?page=com.atlassian.jira.plugin... ] Susan Javurek commented on JBESB-3967: -------------------------------------- Hi, This JIRA project is for a different product in JBOSS. I'll close this request out and your comments to the associated ticket you logged through support. We don't have the Fuse projects configured to log requests directly. Logging a ticket as you did through support is process. The engineer assigned to that case will update the Engineering request. Alternatively, you can log requests upstream in the FABRIC8 project - https://github.com/fabric8io/fabric8/issues and cross reference them in our support tickets. For this issue, I'll make sure the request is logged and on our ENH list. Kindest regards, Susan > Single deployment method for JARs and KARs in a distributed fabric > ------------------------------------------------------------------ > > Key: JBESB-3967 > URL: https://issues.jboss.org/browse/JBESB-3967 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Evgeny Minkevich > Priority: Critical > > As a solution architect I would like a single method to deploy all types of artifacts to a fabric with more than one ensemble server. > Preferred option would be to use mvn:deploy - similar to what is used now to deploy JAR bundles. > I would like the maven proxy to be enhanced with two capabilities: > - to be able to accept and process KARs > - to be able to sync the deployed components between maven proxies running on ensemble servers > Relates to > * ENTESB-1373 > * ENTESB-1374 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (JBESB-3967) Single deployment method for JARs and KARs in a distributed fabric

by Susan Javurek (JIRA)

[ https://issues.jboss.org/browse/JBESB-3967?page=com.atlassian.jira.plugin... ] Susan Javurek edited comment on JBESB-3967 at 5/2/14 12:11 PM: --------------------------------------------------------------- Hi, This JIRA project is for a different product in JBoss. I'll close this request out and your comments to the associated ticket you logged through support. We don't have the Fuse projects configured to log requests directly. Logging a ticket as you did through support is process. The engineer assigned to that case will update the Engineering request. Alternatively, you can log requests upstream in the FABRIC8 project - https://github.com/fabric8io/fabric8/issues and cross reference them in our support tickets. For this issue, I'll make sure the request is logged and on our ENH list. Kindest regards, Susan was (Author: sjavurek): Hi, This JIRA project is for a different product in JBOSS. I'll close this request out and your comments to the associated ticket you logged through support. We don't have the Fuse projects configured to log requests directly. Logging a ticket as you did through support is process. The engineer assigned to that case will update the Engineering request. Alternatively, you can log requests upstream in the FABRIC8 project - https://github.com/fabric8io/fabric8/issues and cross reference them in our support tickets. For this issue, I'll make sure the request is logged and on our ENH list. Kindest regards, Susan > Single deployment method for JARs and KARs in a distributed fabric > ------------------------------------------------------------------ > > Key: JBESB-3967 > URL: https://issues.jboss.org/browse/JBESB-3967 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Evgeny Minkevich > Priority: Critical > > As a solution architect I would like a single method to deploy all types of artifacts to a fabric with more than one ensemble server. > Preferred option would be to use mvn:deploy - similar to what is used now to deploy JAR bundles. > I would like the maven proxy to be enhanced with two capabilities: > - to be able to accept and process KARs > - to be able to sync the deployed components between maven proxies running on ensemble servers > Relates to > * ENTESB-1373 > * ENTESB-1374 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (JBESB-3967) Single deployment method for JARs and KARs in a distributed fabric

by Evgeny Minkevich (JIRA)

[ https://issues.jboss.org/browse/JBESB-3967?page=com.atlassian.jira.plugin... ] Evgeny Minkevich commented on JBESB-3967: ----------------------------------------- [~sjavurek] Is it the right place to create a request ? Responding to your comment at ENTESB-1374 > Single deployment method for JARs and KARs in a distributed fabric > ------------------------------------------------------------------ > > Key: JBESB-3967 > URL: https://issues.jboss.org/browse/JBESB-3967 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Evgeny Minkevich > Priority: Critical > > As a solution architect I would like a single method to deploy all types of artifacts to a fabric with more than one ensemble server. > Preferred option would be to use mvn:deploy - similar to what is used now to deploy JAR bundles. > I would like the maven proxy to be enhanced with two capabilities: > - to be able to accept and process KARs > - to be able to sync the deployed components between maven proxies running on ensemble servers > Relates to > * ENTESB-1373 > * ENTESB-1374 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (JBESB-3967) Single deployment method for JARs and KARs in a distributed fabric

by Evgeny Minkevich (JIRA)

Evgeny Minkevich created JBESB-3967: --------------------------------------- Summary: Single deployment method for JARs and KARs in a distributed fabric Key: JBESB-3967 URL: https://issues.jboss.org/browse/JBESB-3967 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Evgeny Minkevich Priority: Critical As a solution architect I would like a single method to deploy all types of artifacts to a fabric with more than one ensemble server. Preferred option would be to use mvn:deploy - similar to what is used now to deploy JAR bundles. I would like the maven proxy to be enhanced with two capabilities: - to be able to accept and process KARs - to be able to sync the deployed components between maven proxies running on ensemble servers Relates to * ENTESB-1373 * ENTESB-1374 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues May 2014