June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5293) EJB3 method invocation statistics exposed incorrectly through JMX

by Vladislav Semchenko (JIRA)

[ https://issues.jboss.org/browse/WFLY-5293?page=com.atlassian.jira.plugin.... ] Vladislav Semchenko commented on WFLY-5293: ------------------------------------------- Hello. I faced with the same problem on wildfly-10.1.0.Final: I can't get invocation statistics of EJB3 beans in jvisualvm (or jconsole). Although statistics enabled in subsystem ejb3 in standalone.xml. Can we expect some kind of fix for this bug in nearest feature? > EJB3 method invocation statistics exposed incorrectly through JMX > ----------------------------------------------------------------- > > Key: WFLY-5293 > URL: https://issues.jboss.org/browse/WFLY-5293 > Project: WildFly > Issue Type: Bug > Components: JMX > Affects Versions: 9.0.1.Final > Reporter: Arto Huusko > Assignee: Kabir Khan > > EJB3 method invocation statistics, that is the "methods" attribute in an EJB3 session JMX object is exposed as CompositeDataSupport object that has the expected keys ("execution-time", and so on), but > - the values for the keys are always null > - there is only a single CompositeDataSupport object even when the session has several methods > - the method name is not available. > Possibly the invocation statistics should be exposed as an array of CompositeDataSupport objects where one of the keys is the method name. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2011) Inconsistency of formatter and named-formatter in console logging handler

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2011?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated WFCORE-2011: -------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1465941 Bugzilla Update: Perform > Inconsistency of formatter and named-formatter in console logging handler > ------------------------------------------------------------------------- > > Key: WFCORE-2011 > URL: https://issues.jboss.org/browse/WFCORE-2011 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 3.0.0.Alpha13 > Environment: It is possible to reproduce with all profiles and all modes. > All WildFly profiles > All WildFly clustering mode > * standalone mode > * domain mode > Reporter: Ted Won > Assignee: Ted Won > Priority: Minor > Labels: logging > Attachments: COLOR-PATTERN.png, CONSOLE-console-handler.png > > > In logging subsystem the default CONSOLE console-handler is defined with COLOR-PATTERN named-formatter. > And the COLOR-PATTERN named-formatter is defined with: {noformat}"%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"{noformat} > It is working as it is defined with colors in a console. > {code:title=standalone.xml} > ... > <subsystem xmlns="urn:jboss:domain:logging:3.0"> > <console-handler name="CONSOLE"> > <level name="INFO"/> > <formatter> > <named-formatter name="COLOR-PATTERN"/> > </formatter> > </console-handler> > ... > <formatter name="COLOR-PATTERN"> > <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"/> > </formatter> > </subsystem> > ... > {code} > However there is a inconsistency in the CLI and WildFly admin console views. > In the CLI, CONSOLE formatter is: {noformat}"%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"{noformat} It is wrong and different with the working logging format in a console. > {code:title=JBoss CLI} > [standalone@localhost:9990 /] /subsystem=logging/console-handler=CONSOLE:read-resource > { > "outcome" => "success", > "result" => { > "autoflush" => true, > "enabled" => true, > "encoding" => undefined, > "filter" => undefined, > "filter-spec" => undefined, > "formatter" => "%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n", > "level" => "INFO", > "name" => "CONSOLE", > "named-formatter" => "COLOR-PATTERN", > "target" => "System.out" > } > } > {code} > It should be fixed like below: > {code:title=Expected result} > [standalone@localhost:9990 /] /subsystem=logging/console-handler=CONSOLE:read-resource > { > "outcome" => "success", > "result" => { > "autoflush" => true, > "enabled" => true, > "encoding" => undefined, > "filter" => undefined, > "filter-spec" => undefined, > "formatter" => undefined, > "level" => "INFO", > "name" => "CONSOLE", > "named-formatter" => "COLOR-PATTERN", > "target" => "System.out" > } > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9017) Wrong Transaction behaviour for EJBs if JTS is enabled

by Fedor Gavrilov (JIRA)

Fedor Gavrilov created WFLY-9017: ------------------------------------ Summary: Wrong Transaction behaviour for EJBs if JTS is enabled Key: WFLY-9017 URL: https://issues.jboss.org/browse/WFLY-9017 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 8.1.0.Final Environment: standalone-full profile with JTS enabled Reporter: Fedor Gavrilov Assignee: David Lloyd If JTS is enabled the invocation of EJB's might show a arjuna warning for each method invocation: WARN [com.arjuna.ats.jts] (RequestProcessor-5) ARJUNA022261: ServerTopLevelAction detected that the transaction was inactive This is only the case if other resources are involved, i.e. a DB via JPA. If a simple bean is used (like ejb-remote quickstart) this warning is not shown. It looks like the transaction is local commited but in case of a SFSB @Remove method the result is a " WFLYEE0006: Failed to destroy component instance Instance of SFTestBean" and the lifecycle method @PreDestroy is not invoked. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8955) Upgrade Artemis 1.5.5.jbossorg-004

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-8955?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-8955: ------------------------------ Summary: Upgrade Artemis 1.5.5.jbossorg-004 (was: Upgrade Artemis 1.5.5.jbossorg-003 ) > Upgrade Artemis 1.5.5.jbossorg-004 > ---------------------------------- > > Key: WFLY-8955 > URL: https://issues.jboss.org/browse/WFLY-8955 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3801) Wrong Transaction behaviour for EJBs if JTS is enabled

by Fedor Gavrilov (JIRA)

[ https://issues.jboss.org/browse/WFLY-3801?page=com.atlassian.jira.plugin.... ] Fedor Gavrilov resolved WFLY-3801. ---------------------------------- Resolution: Done > Wrong Transaction behaviour for EJBs if JTS is enabled > ------------------------------------------------------ > > Key: WFLY-3801 > URL: https://issues.jboss.org/browse/WFLY-3801 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.1.0.Final > Environment: standalone-full profile with JTS enabled > Reporter: Wolf-Dieter Fink > Assignee: David Lloyd > Attachments: 456a624-withDestroy.log, 8d49872-error.log, enableJTS.cli, reproducer.zip, server.log > > > If JTS is enabled the invocation of EJB's might show a arjuna warning for each method invocation: > WARN [com.arjuna.ats.jts] (RequestProcessor-5) ARJUNA022261: ServerTopLevelAction detected that the transaction was inactive > This is only the case if other resources are involved, i.e. a DB via JPA. > If a simple bean is used (like ejb-remote quickstart) this warning is not shown. > It looks like the transaction is local commited but in case of a SFSB @Remove method the result is a " WFLYEE0006: Failed to destroy component instance Instance of SFTestBean" and the lifecycle method @PreDestroy is not invoked. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9016) SecurityDomain is lost when setting up remote outbound connections

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/WFLY-9016?page=com.atlassian.jira.plugin.... ] Pedro Igor updated WFLY-9016: ----------------------------- Summary: SecurityDomain is lost when setting up remote outbound connections (was: https://issues.jboss.org/browse/WFCORE-3024) > SecurityDomain is lost when setting up remote outbound connections > ------------------------------------------------------------------ > > Key: WFLY-9016 > URL: https://issues.jboss.org/browse/WFLY-9016 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 11.0.0.Alpha1 > Reporter: Pedro Igor > Assignee: Pedro Igor > > When setting up the {{AuthenticationConfiguration}} during deployment ({{EjbClientContextSetupProcessor}}), the SecurityDomain defined to forward/propagate identities is lost making impossible to propagate identities when connecting to a remote EJB. > The reference to the {{AuthenticationConfiguration}} should be obtained at runtime during invocations in order to be able to obtain the current identity for a given SecurityDomain. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9016) https://issues.jboss.org/browse/WFCORE-3024

by Pedro Igor (JIRA)

Pedro Igor created WFLY-9016: -------------------------------- Summary: https://issues.jboss.org/browse/WFCORE-3024 Key: WFLY-9016 URL: https://issues.jboss.org/browse/WFLY-9016 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 11.0.0.Alpha1 Reporter: Pedro Igor Assignee: Pedro Igor When setting up the {{AuthenticationConfiguration}} during deployment ({{EjbClientContextSetupProcessor}}), the SecurityDomain defined to forward/propagate identities is lost making impossible to propagate identities when connecting to a remote EJB. The reference to the {{AuthenticationConfiguration}} should be obtained at runtime during invocations in order to be able to obtain the current identity for a given SecurityDomain. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3024) SecurityDomain is lost when setting up remote outbound connections

by Pedro Igor (JIRA)

Pedro Igor created WFCORE-3024: ---------------------------------- Summary: SecurityDomain is lost when setting up remote outbound connections Key: WFCORE-3024 URL: https://issues.jboss.org/browse/WFCORE-3024 Project: WildFly Core Issue Type: Bug Components: Remoting Affects Versions: 3.0.0.Beta27 Reporter: Pedro Igor Assignee: Pedro Igor When setting up the {{AuthenticationConfiguration}} during the start of {{RemoteOutboundConnectionService}}, the {{SecurityDomain}} defined to forward/propagate identities is lost making impossible to propagate identities when connecting to a remote service (e.g.: EJB). The reference to the {{AuthenticationConfiguration}} can not be kept by the service but obtained at runtime during invocations in order to be able to obtain the current identity for a given {{SecurityDomain}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-126) [QE] - JMAN4-120 EAP Web Server Metrics Reporting

by Sunil kondkar (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-126?page=com.atlassian.jira.pl... ] Sunil kondkar reassigned HAWKULARQE-126: ---------------------------------------- Assignee: Sunil kondkar (was: Michael Foley) > [QE] - JMAN4-120 EAP Web Server Metrics Reporting > ------------------------------------------------- > > Key: HAWKULARQE-126 > URL: https://issues.jboss.org/browse/HAWKULARQE-126 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Sunil kondkar > Labels: 5.0, mm-integration-hawkular-qe > > See [JMAN4-120|https://issues.jboss.org/browse/JMAN4-120] > Requirement's Test Plan document: https://mojo.redhat.com/docs/DOC-1141232 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-104) Secure HAwkular server using SSL without validaton

by Prachi Yadav (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-104?page=com.atlassian.jira.pl... ] Prachi Yadav reassigned HAWKULARQE-104: --------------------------------------- Assignee: Prachi Yadav (was: Michael Foley) > Secure HAwkular server using SSL without validaton > -------------------------------------------------- > > Key: HAWKULARQE-104 > URL: https://issues.jboss.org/browse/HAWKULARQE-104 > Project: Hawkular QE > Issue Type: Task > Reporter: Prachi Yadav > Assignee: Prachi Yadav > > Need to setup Hawkular server which is running on SSL withour validation (doesn't verify the peer > certificate) > Reference Document: http://ruby-doc.org/stdlib-2.0.0/libdoc/openssl/rdoc/OpenSSL.html#module-... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2017