[JBoss JIRA] (AS7-6738) The value wait-time of the EJB bean statistic is not calculated
by Wolf-Dieter Fink (JIRA)
Wolf-Dieter Fink created AS7-6738:
-------------------------------------
Summary: The value wait-time of the EJB bean statistic is not calculated
Key: AS7-6738
URL: https://issues.jboss.org/browse/AS7-6738
Project: Application Server 7
Issue Type: Feature Request
Components: EJB
Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
Reporter: Wolf-Dieter Fink
Assignee: jaikiran pai
Priority: Minor
If the statistic for EJB calls is enabled with
/subsystem=ejb3:write-attribute(name=enable-statistics, value=true)
call statistics are caclulated but the wait-time is never set even if a pool overload is forced.
--
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
13 years, 4 months
[JBoss JIRA] (AS7-6713) CLI: "pattern" and "replacement" should be required when creating logging filter
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6713?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-6713:
----------------------------------------------
James Perkins <jperkins(a)redhat.com> changed the Status of [bug 915835|https://bugzilla.redhat.com/show_bug.cgi?id=915835] from NEW to POST
> CLI: "pattern" and "replacement" should be required when creating logging filter
> --------------------------------------------------------------------------------
>
> Key: AS7-6713
> URL: https://issues.jboss.org/browse/AS7-6713
> Project: Application Server 7
> Issue Type: Bug
> Components: Logging
> Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
> Reporter: Chao Wang
> Assignee: James Perkins
> Attachments: AS7-6713.patch
>
>
> It's able to set filter attribute without "pattern" and "replacement" although they are not nillable.
> calling:
> /subsystem=logging/console-handler=CONSOLE:write-attribute(name=filter, value={replace => {"replace-all" => true}})
> will create useless filter:
> "filter" => {"replace" => {
> "replace-all" => true,
> "pattern" => "undefined",
> "replacement" => "undefined"
> }}
> "filter-spec" => "substituteAll(\"undefined\",\"undefined\")"
> only "replace-all" is actually required now:
> [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:update-properties(filter={replace => {"pattern" => "JBAS","replacement" => "SABJ"}})
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014749: Operation handler failed: null",
> "rolled-back" => true
> }
--
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
13 years, 4 months
[JBoss JIRA] (AS7-6458) Include deployment's class list and deployment descriptors
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6458?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6458:
----------------------------------
Assignee: Jesse Jaggars (was: Brian Stansberry)
> Include deployment's class list and deployment descriptors
> ----------------------------------------------------------
>
> Key: AS7-6458
> URL: https://issues.jboss.org/browse/AS7-6458
> Project: Application Server 7
> Issue Type: Enhancement
> Components: JDR
> Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
> Reporter: Brad Maxwell
> Assignee: Jesse Jaggars
> Fix For: Awaiting Volunteers
>
>
> Option to run JDR and create an extended report which will include the deployment descriptors or the deployments as well as a list of all classes packaged and the relative path to the jar in the deployment or WEB-INF/classes. This would allow us to look for JDK / J2EE classes, which should not be packaged as well as customers packaging jboss classes which should not be packaged. And look for issues in deployment descriptors.
--
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
13 years, 4 months
[JBoss JIRA] (AS7-6458) Include deployment's class list and deployment descriptors
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6458?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry reassigned AS7-6458:
-------------------------------------
Assignee: Brian Stansberry (was: Jesse Jaggars)
> Include deployment's class list and deployment descriptors
> ----------------------------------------------------------
>
> Key: AS7-6458
> URL: https://issues.jboss.org/browse/AS7-6458
> Project: Application Server 7
> Issue Type: Enhancement
> Components: JDR
> Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
> Reporter: Brad Maxwell
> Assignee: Brian Stansberry
> Fix For: Awaiting Volunteers
>
>
> Option to run JDR and create an extended report which will include the deployment descriptors or the deployments as well as a list of all classes packaged and the relative path to the jar in the deployment or WEB-INF/classes. This would allow us to look for JDK / J2EE classes, which should not be packaged as well as customers packaging jboss classes which should not be packaged. And look for issues in deployment descriptors.
--
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
13 years, 4 months