[JBoss JIRA] (WFLY-38) EJB3 deployment metrics missing
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-38?page=com.atlassian.jira.plugin.sy... ]
RH Bugzilla Integration commented on WFLY-38:
---------------------------------------------
Chao Wang <chaowan(a)redhat.com> changed the Status of [bug 911117|https://bugzilla.redhat.com/show_bug.cgi?id=911117] from NEW to ASSIGNED
> EJB3 deployment metrics missing
> -------------------------------
>
> Key: WFLY-38
> URL: https://issues.jboss.org/browse/WFLY-38
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Stefan Negrea
> Assignee: Carlo de Wolf
> Priority: Critical
> Labels: rhq
> Fix For: 8.0.0.Alpha1
>
>
> The following metrics are missing from AS7 EJB3 subsystem from deployment when compared to AS5 exposed metrics:
> Stateless Session Bean
> Method Invocation Time - The minimum, maximum, and average invocation times for each of the methods exposed by this EJB
> Stateful Session Bean
> Method Invocation Time - The minimum, maximum, and average invocation times for each of the methods exposed by this EJB
> Cache Size - Cache Size
> Passivated Count - Passivated Count
> Total Size - Total Size
--
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
12 years, 4 months
[JBoss JIRA] (WFLY-1589) requiredSecret attribute on the AJP connector
by Tom Fonteyne (JIRA)
Tom Fonteyne created WFLY-1589:
----------------------------------
Summary: requiredSecret attribute on the AJP connector
Key: WFLY-1589
URL: https://issues.jboss.org/browse/WFLY-1589
Project: WildFly
Issue Type: Feature Request
Components: Web (JBoss Web)
Reporter: Tom Fonteyne
Assignee: Remy Maucherat
Priority: Minor
In JBoss 5 I could set the requiredSecret attribute of the AJP connector. This is no longer possible in JBoss AS 7 and WildFly
This request is to get it implemented similarly to WFLY-254 for tomcatAuthentication
--
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
12 years, 4 months
[JBoss JIRA] (WFLY-1533) UT015005: Error invoking method requestDestroyed on listener class
by Jozef Hartinger (JIRA)
[ https://issues.jboss.org/browse/WFLY-1533?page=com.atlassian.jira.plugin.... ]
Jozef Hartinger updated WFLY-1533:
----------------------------------
Assignee: Jozef Hartinger (was: Stuart Douglas)
Component/s: CDI / Weld
(was: Web (Undertow))
> UT015005: Error invoking method requestDestroyed on listener class
> -------------------------------------------------------------------
>
> Key: WFLY-1533
> URL: https://issues.jboss.org/browse/WFLY-1533
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 8.0.0.Alpha2
> Reporter: Juergen Zimmermann
> Assignee: Jozef Hartinger
>
> I'm using a WildFly snapshot with Undertow 1.0.0.Alpha19 and Weld 2.0.1.Final. I'm getting the following stacktrace:
> 16:55:04,534 ERROR [io.undertow.servlet.request] UT015005: Error invoking method requestDestroyed on listener class org.jboss.weld.servlet.WeldListener: java.lang.IllegalStateException: UT000010: Session not found MDEkG_Aum5OlXUsjh11kGkh9
> at io.undertow.server.session.InMemorySessionManager$SessionImpl.getAttribute(InMemorySessionManager.java:221) [undertow-core-1.0.0.Alpha19.jar:1.0.0.Alpha19]
> at io.undertow.servlet.spec.HttpSessionImpl.getAttribute(HttpSessionImpl.java:106) [undertow-servlet-1.0.0.Alpha19.jar:1.0.0.Alpha19]
> at org.jboss.weld.context.http.HttpConversationContextImpl.getSessionAttribute(HttpConversationContextImpl.java:25) [weld-core-impl-2.0.1.Final.jar:2013-06-03 10:29]
> at org.jboss.weld.context.http.HttpConversationContextImpl.getSessionAttribute(HttpConversationContextImpl.java:13) [weld-core-impl-2.0.1.Final.jar:2013-06-03 10:29]
> at org.jboss.weld.context.AbstractConversationContext.dissociate(AbstractConversationContext.java:161) [weld-core-impl-2.0.1.Final.jar:2013-06-03 10:29]
> at org.jboss.weld.servlet.ConversationContextActivator.disassociateConversationContext(ConversationContextActivator.java:162) [weld-core-impl-2.0.1.Final.jar:2013-06-03 10:29]
> at org.jboss.weld.servlet.HttpContextLifecycle.requestDestroyed(HttpContextLifecycle.java:159) [weld-core-impl-2.0.1.Final.jar:2013-06-03 10:29]
> at org.jboss.weld.servlet.WeldListener.requestDestroyed(WeldListener.java:91) [weld-core-impl-2.0.1.Final.jar:2013-06-03 10:29]
> at io.undertow.servlet.core.ApplicationListeners.requestDestroyed(ApplicationListeners.java:196) [undertow-servlet-1.0.0.Alpha19.jar:1.0.0.Alpha19]
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:159) [undertow-servlet-1.0.0.Alpha19.jar:1.0.0.Alpha19]
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:114) [undertow-servlet-1.0.0.Alpha19.jar:1.0.0.Alpha19]
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:47) [undertow-servlet-1.0.0.Alpha19.jar:1.0.0.Alpha19]
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:90) [undertow-servlet-1.0.0.Alpha19.jar:1.0.0.Alpha19]
> at io.undertow.server.HttpHandlers.executeRootHandler(HttpHandlers.java:36) [undertow-core-1.0.0.Alpha19.jar:1.0.0.Alpha19]
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:607) [undertow-core-1.0.0.Alpha19.jar:1.0.0.Alpha19]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
--
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
12 years, 4 months