[JBoss JIRA] (SWSQE-2) Create Sprint-1 Acceptance Tests
by Matt Mahoney (JIRA)
[ https://issues.jboss.org/browse/SWSQE-2?page=com.atlassian.jira.plugin.sy... ]
Matt Mahoney updated SWSQE-2:
-----------------------------
Description:
Acceptance Criteria - 1 Verify graph against Prometheus metrics graphs - data should be the same
Acceptance Criteria - 2 Verify graph against ISTIO graphs - data should be the same
was:
Acceptance Criteria - 1 Verify graph against Prometheus metrics graphs - data should be the same
Aceptance Criteria - 2 Verify graph against ISTIO graphs - data should be the same
> Create Sprint-1 Acceptance Tests
> --------------------------------
>
> Key: SWSQE-2
> URL: https://issues.jboss.org/browse/SWSQE-2
> Project: Swift Sunshine QE
> Issue Type: Task
> Reporter: Matt Mahoney
> Assignee: Michael Foley
>
> Acceptance Criteria - 1 Verify graph against Prometheus metrics graphs - data should be the same
> Acceptance Criteria - 2 Verify graph against ISTIO graphs - data should be the same
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3608) There is no way to define core pool size for io subsystem
by Richard Janík (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3608?page=com.atlassian.jira.plugi... ]
Richard Janík moved JBEAP-14230 to WFCORE-3608:
-----------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-3608 (was: JBEAP-14230)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: IO
(was: IO)
Affects Version/s: 4.0.0.Alpha10
(was: 7.1.0.DR10)
> There is no way to define core pool size for io subsystem
> ---------------------------------------------------------
>
> Key: WFCORE-3608
> URL: https://issues.jboss.org/browse/WFCORE-3608
> Project: WildFly Core
> Issue Type: Enhancement
> Components: IO
> Affects Versions: 4.0.0.Alpha10
> Reporter: Richard Janík
>
> There is no way how to define core pool size for underlying thread pool in IO subsystem's worker ({{/subsystem=io/worker=*}}). It is only possible to set task-max-threads which defines max pool size for underlying thread pool.
> Suggestion for improvement: Add new attribute to set core pool size to IO subsystem worker
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (SWSQE-2) Create Sprint-1 Acceptance Tests
by Matt Mahoney (JIRA)
Matt Mahoney created SWSQE-2:
--------------------------------
Summary: Create Sprint-1 Acceptance Tests
Key: SWSQE-2
URL: https://issues.jboss.org/browse/SWSQE-2
Project: Swift Sunshine QE
Issue Type: Task
Reporter: Matt Mahoney
Assignee: Michael Foley
Acceptance Criteria - 1 Verify graph against Prometheus metrics graphs - data should be the same
Aceptance Criteria - 2 Verify graph against ISTIO graphs - data should be the same
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9829) EJB JNDI naming discrepancy between stdout and doc
by tommaso borgato (JIRA)
tommaso borgato created WFLY-9829:
-------------------------------------
Summary: EJB JNDI naming discrepancy between stdout and doc
Key: WFLY-9829
URL: https://issues.jboss.org/browse/WFLY-9829
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 12.0.0.Alpha1
Reporter: tommaso borgato
Priority: Minor
On documentation https://docs.jboss.org/author/display/WFLY/EJB+invocations+from+a+remote+... the EJB JNDI name starts with ejb:
{code}
ejb:/jboss-as-ejb-remote-app//CalculatorBean!org.jboss.as.quickstarts.ejb.remote.stateless.RemoteCalculator
{code}
When the server is started (./bin/standalone.sh --server-config=standalone-ha.xml) and the EJB application is deployed, the logs say:
{code:tile stdout}
15:20:16,327 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'CalculatorBean' in deployment unit 'deployment "ejb-server.war"' are as follows:
java:global/jboss-as-ejb-remote-app/CalculatorBean!com.redhat.samples.ejb.stateless.LocalCalculator
java:app/jboss-as-ejb-remote-app/CalculatorBean!com.redhat.samples.ejb.stateless.LocalCalculator
java:module/CalculatorBean!com.redhat.samples.ejb.stateless.LocalCalculator
java:global/jboss-as-ejb-remote-app/CalculatorBean!com.redhat.samples.ejb.stateless.RemoteCalculator
java:app/jboss-as-ejb-remote-app/CalculatorBean!com.redhat.samples.ejb.stateless.RemoteCalculator
java:module/CalculatorBean!com.redhat.samples.ejb.stateless.RemoteCalculator
java:jboss/exported/jboss-as-ejb-remote-app/CalculatorBean!com.redhat.samples.ejb.stateless.RemoteCalculator
{code}
None of them matches the JNDI name mentioned in the documentation.
The JNDI name in the documentation works correctly.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3607) Fix build & testsuite for JDK 10
by Tomaz Cerar (JIRA)
Tomaz Cerar created WFCORE-3607:
-----------------------------------
Summary: Fix build & testsuite for JDK 10
Key: WFCORE-3607
URL: https://issues.jboss.org/browse/WFCORE-3607
Project: WildFly Core
Issue Type: Task
Components: Remoting
Reporter: Tomaz Cerar
Assignee: Tomaz Cerar
Currently all remoting related code and tests fail on JDK 10.
Cause is tracked in JBMAR-216
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months