April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-320) Allow jconsole to be launched as a modular application

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-320?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-320: ---------------------------------- Assignee: (was: Brian Stansberry) > Allow jconsole to be launched as a modular application > ------------------------------------------------------ > > Key: WFLY-320 > URL: https://issues.jboss.org/browse/WFLY-320 > Project: WildFly > Issue Type: Feature Request > Components: JMX, Scripts > Reporter: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > Make the jconsole scripts launch jconsole as as a modular application. Get rid of the classpath building that resulted in AS7-6498. > Some (mildly edited) discussion: > bstansberry: BTW, I filed a JIRA to make the vault tool a proper modular app in AS next. I'm not sure if that's doable for jconsole > [10:37am] darranl: bstansberry: Yes vault should be modular - I don't believe jconsole is as easily possible unless we add a module for the jconsole classes > [10:38am] darranl: bstansberry: the problem with jconsole was that we actually needed to call jconsole which I think was a binary so we were just created an extended classpath for that binary to use > [10:38am] bstansberry: darranl: ok, will do. I didn't file a JIRA for modular jconsole because I figured there would be problems > [10:39am] darranl: bstansberry: having said that it may be possible now to just switch to use the client jar - that did not exist at the time the jconsole script was first written > [10:40am] darranl: but at this point may be safer to just update the root of the modules folder and switch to client later > [10:40am] bstansberry: darranl: this will become more of an issue once we have patching > [10:40am] bstansberry: since this script won't pick up any patches we may have issued for the listed modules > [10:40am] bstansberry: and no way are we going to add that to the script > [10:43am] dmlloyd: I've booted jconsole from within modules before > [10:43am] dmlloyd: it's possible > [10:43am] darranl: If it is possbile then maybe we can just make it modular > [10:44am] dmlloyd: java -jar ~/.m2/repository/org/jboss/modules/jboss-modules/1.1.4.GA/jboss-modules-1.1.4.GA.jar -jar ~/local/jdk/home/lib/jconsole.jar > [10:44am] dmlloyd: easy as bananas > [10:45am] dmlloyd: if you use -cp you can also add dependencies via -dep > [10:45am] dmlloyd: or we could create a jconsole module from openjdk even -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-188) It is difficult to identify an EJB Timer with the logged timer-id, especially if it is non persistent

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-188?page=com.atlassian.jira.plugin.s... ] James Perkins updated WFLY-188: ------------------------------- Assignee: Wolf-Dieter Fink (was: James Perkins) > It is difficult to identify an EJB Timer with the logged timer-id, especially if it is non persistent > ----------------------------------------------------------------------------------------------------- > > Key: WFLY-188 > URL: https://issues.jboss.org/browse/WFLY-188 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Wolf-Dieter Fink > Assignee: Wolf-Dieter Fink > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > The JBAS14143 message and other skip messages log the timer id, but this is not very helpful as it is complicated to find the related application bean if the timer is persistent or not possible if it is a non persistent timer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-307) Add ability to migrate timers between data stores

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-307?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-307: ---------------------------------- Assignee: Stuart Douglas (was: Brian Stansberry) > Add ability to migrate timers between data stores > ------------------------------------------------- > > Key: WFLY-307 > URL: https://issues.jboss.org/browse/WFLY-307 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha1 > > > It should be possible to move timers between data stores, so that timers can be migrated from the legacy file store. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-454) Task for tracking all workarounds / hacks needed to have undertow & jbossweb living together

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-454?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar reassigned WFLY-454: -------------------------------- Assignee: Tomaz Cerar (was: Brian Stansberry) > Task for tracking all workarounds / hacks needed to have undertow & jbossweb living together > -------------------------------------------------------------------------------------------- > > Key: WFLY-454 > URL: https://issues.jboss.org/browse/WFLY-454 > Project: WildFly > Issue Type: Task > Components: Web (JBoss Web) > Affects Versions: 8.0.0.Alpha1 > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 8.0.0.CR1 > > > There are many workarounds in undertow subsystem code just to make it behave exactly as jbossweb did but that is wrong in many cases. > This issue is here just to track such occurrences and resolutions for this issue should eventual removal of this hacks when web subsystem is removed from AS8 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-454) Task for tracking all workarounds / hacks needed to have undertow & jbossweb living together

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-454?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar updated WFLY-454: ----------------------------- Component/s: Web (Undertow) (was: Web (JBoss Web)) > Task for tracking all workarounds / hacks needed to have undertow & jbossweb living together > -------------------------------------------------------------------------------------------- > > Key: WFLY-454 > URL: https://issues.jboss.org/browse/WFLY-454 > Project: WildFly > Issue Type: Task > Components: Web (Undertow) > Affects Versions: 8.0.0.Alpha1 > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 8.0.0.CR1 > > > There are many workarounds in undertow subsystem code just to make it behave exactly as jbossweb did but that is wrong in many cases. > This issue is here just to track such occurrences and resolutions for this issue should eventual removal of this hacks when web subsystem is removed from AS8 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-301) Undertow management API

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-301?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-301: ---------------------------------- Assignee: Tomaz Cerar (was: Brian Stansberry) > Undertow management API > ----------------------- > > Key: WFLY-301 > URL: https://issues.jboss.org/browse/WFLY-301 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management, Web (JBoss Web) > Reporter: Heiko Braun > Assignee: Tomaz Cerar > Fix For: 8.0.0.Beta1 > > > Expose undertow subsystem management opertions -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-454) Task for tracking all workarounds / hacks needed to have undertow & jbossweb living together

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-454?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar updated WFLY-454: ----------------------------- Component/s: Web (JBoss Web) > Task for tracking all workarounds / hacks needed to have undertow & jbossweb living together > -------------------------------------------------------------------------------------------- > > Key: WFLY-454 > URL: https://issues.jboss.org/browse/WFLY-454 > Project: WildFly > Issue Type: Task > Components: Web (JBoss Web), Web (Undertow) > Affects Versions: 8.0.0.Alpha1 > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 8.0.0.CR1 > > > There are many workarounds in undertow subsystem code just to make it behave exactly as jbossweb did but that is wrong in many cases. > This issue is here just to track such occurrences and resolutions for this issue should eventual removal of this hacks when web subsystem is removed from AS8 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1159) Allow configure SSL connection in stanalone.xml for email servers

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-1159?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-1159: --------------------------------- Assignee: Tomaz Cerar (was: Darran Lofthouse) > Allow configure SSL connection in stanalone.xml for email servers > ----------------------------------------------------------------- > > Key: WFLY-1159 > URL: https://issues.jboss.org/browse/WFLY-1159 > Project: WildFly > Issue Type: Feature Request > Components: Mail > Reporter: Alexey Volkov > Assignee: Tomaz Cerar > Priority: Optional > > Allow to configure SSL connection to email servers into stanalone.xml > Here is the discussion into community https://community.jboss.org/thread/205364 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-249) Look into whether READ_ONLY but not RUNTIME_ONLY domain server ops should be visible to users

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-249?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-249: ---------------------------------- Assignee: (was: Brian Stansberry) > Look into whether READ_ONLY but not RUNTIME_ONLY domain server ops should be visible to users > --------------------------------------------------------------------------------------------- > > Key: WFLY-249 > URL: https://issues.jboss.org/browse/WFLY-249 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > Ops registered on a domain server without the RUNTIME_ONLY flag are hidden from users (e.g. in read-operation-names results etc) in order to not delude users into thinking they can do something like :write-attribute directly on a server (instead of modifying host or domain config elements.) > But shouldn't a READ_ONLY flag be sufficient as well? An op that only reads config should be valid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-250) Expose webservices endpoint metrics in console

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-250?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-250: ---------------------------------- Assignee: Heiko Braun (was: Brian Stansberry) > Expose webservices endpoint metrics in console > ---------------------------------------------- > > Key: WFLY-250 > URL: https://issues.jboss.org/browse/WFLY-250 > Project: WildFly > Issue Type: Feature Request > Components: Web Console, Web Services > Reporter: Alessio Soldano > Assignee: Heiko Braun > Fix For: 8.0.0.Alpha1 > > > The Status->Subsystems->Webservices section of the Runtime area of the console contains basic info regarding deployed ws endpoints. It does not currently use all the available information for each of them in the model (e.g. [1]), in particular the metrics are missing and should really be added to the console (average-processing-time, fault-count, max-processing-time, min-processing-time, request-count, response-count, total-processing-time) > [1] /deployment=foo.war/subsystem=webservices/endpoint=foo-ep -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013