[Red Hat JIRA] (WFLY-13969) signature test failures in Expression Language (jakarta.el)
by Scott Marlow (Jira)
[ https://issues.redhat.com/browse/WFLY-13969?page=com.atlassian.jira.plugi... ]
Scott Marlow commented on WFLY-13969:
-------------------------------------
I'm testing the https://github.com/jboss/jboss-jakarta-el-api_spec/pull/4 changes on the https://github.com/jboss/jboss-jakarta-el-api_spec/tree/3.0.x branch with a pom.xml change.
> signature test failures in Expression Language (jakarta.el)
> -----------------------------------------------------------
>
> Key: WFLY-13969
> URL: https://issues.redhat.com/browse/WFLY-13969
> Project: WildFly
> Issue Type: Sub-task
> Components: EE
> Reporter: Scott Marlow
> Assignee: Parul Sharma
> Priority: Major
> Labels: EE9
>
> jakarta.el
> {quote}
> Missing Methods
> [javatest.batch] ---------------
> [javatest.batch]
> [javatest.batch] jakarta.el.ELContext: method public java.lang.Object jakarta.el.ELContext.getContext(java.lang.Class<?>)
> [javatest.batch] jakarta.el.ELContext: method public void jakarta.el.ELContext.putContext(java.lang.Class<?>,java.lang.Object)
> [javatest.batch] jakarta.el.StandardELContext: method public java.lang.Object jakarta.el.StandardELContext.getContext(java.lang.Class<?>)
> [javatest.batch] jakarta.el.StandardELContext: method public void jakarta.el.StandardELContext.putContext(java.lang.Class<?>,java.lang.Object)
> [javatest.batch]
> [javatest.batch] Added Methods
> [javatest.batch] -------------
> [javatest.batch]
> [javatest.batch] jakarta.el.ELContext: method public java.lang.Object jakarta.el.ELContext.getContext(java.lang.Class)
> [javatest.batch] jakarta.el.ELContext: method public void jakarta.el.ELContext.putContext(java.lang.Class,java.lang.Object)
> [javatest.batch] jakarta.el.StandardELContext: method public java.lang.Object jakarta.el.StandardELContext.getContext(java.lang.Class)
> [javatest.batch] jakarta.el.StandardELContext: method public void jakarta.el.StandardELContext.putContext(java.lang.Class,java.lang.Object)
> {quote}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (AG-153) Application blocked getting Connection from shared handler cache.
by Jeremy Whiting (Jira)
[ https://issues.redhat.com/browse/AG-153?page=com.atlassian.jira.plugin.sy... ]
Jeremy Whiting updated AG-153:
------------------------------
Description:
I am inspecting an application that stopped nearly all processing.
A jstack dump reveals one of the thread pools (40 threads) has all threads blocked waiting for a database Connection. See the "summary-of-getConnection-method-calls.txt" file.
There are no other threads that already have a connection leased out.
was:
I am inspecting an application that stopped nearly all processing.
A jstack dump reveals a thread pool (40 threads) with all threads blocked waiting for a Connection. See the "summary-of-getConnection-method-calls.txt" file.
There are no other threads that already have a connection leased out.
> Application blocked getting Connection from shared handler cache.
> -----------------------------------------------------------------
>
> Key: AG-153
> URL: https://issues.redhat.com/browse/AG-153
> Project: Agroal
> Issue Type: Bug
> Components: pool
> Affects Versions: 1.8
> Reporter: Jeremy Whiting
> Assignee: Luis Barreiro
> Priority: Major
> Attachments: jstack-tree.txt, summary-of-getConnection-method-calls.txt
>
>
> I am inspecting an application that stopped nearly all processing.
> A jstack dump reveals one of the thread pools (40 threads) has all threads blocked waiting for a database Connection. See the "summary-of-getConnection-method-calls.txt" file.
> There are no other threads that already have a connection leased out.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (AG-153) Application blocked getting Connection from shared handler cache.
by Jeremy Whiting (Jira)
[ https://issues.redhat.com/browse/AG-153?page=com.atlassian.jira.plugin.sy... ]
Jeremy Whiting updated AG-153:
------------------------------
Description:
I am inspecting an application that stopped nearly all processing.
A jstack dump reveals a thread pool (40 threads) with all threads blocked waiting for a Connection. See the "summary-of-getConnection-method-calls.txt" file.
There are no other threads that already have a connection leased out.
was:
I am inspecting an application that stopped nearly all processing.
A jstack dump reveals a thread pool (40 threads) with all threads blocked waiting for a Connection.
There are no other threads that already have a connection leased out.
> Application blocked getting Connection from shared handler cache.
> -----------------------------------------------------------------
>
> Key: AG-153
> URL: https://issues.redhat.com/browse/AG-153
> Project: Agroal
> Issue Type: Bug
> Components: pool
> Affects Versions: 1.8
> Reporter: Jeremy Whiting
> Assignee: Luis Barreiro
> Priority: Major
> Attachments: jstack-tree.txt, summary-of-getConnection-method-calls.txt
>
>
> I am inspecting an application that stopped nearly all processing.
> A jstack dump reveals a thread pool (40 threads) with all threads blocked waiting for a Connection. See the "summary-of-getConnection-method-calls.txt" file.
> There are no other threads that already have a connection leased out.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months