January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3492) Create UX proposal to show/edit Test Scenario (Preview) global setting

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3492?page=com.atlassian.jira.plugi... ] Klara Kufova commented on DROOLS-3492: -------------------------------------- [~zhutaojiajia], I agree. Test Tools tab opened by default sounds good to me. > Create UX proposal to show/edit Test Scenario (Preview) global setting > ---------------------------------------------------------------------- > > Key: DROOLS-3492 > URL: https://issues.jboss.org/browse/DROOLS-3492 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: tao zhu > Priority: Major > Labels: ScenarioSimulation, UXD, UXTeam > Attachments: 11unnamed.png, TestScenario_Cheatsheet.png, TestScenario_TestEditor.png, TestScenario_TestReport.png, TestScenario_whole.png, test-report-icon.png, 屏幕快照 2019-01-22 下午4.44.04.png, 屏幕快照 2019-01-23 下午4.08.30.png, 屏幕快照 2019-01-23 下午4.08.30.png > > > As user I want to be able to see/edit editor global settings. > For instance DMN file linked to the scenario or the Session name of a Rule scenario -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8197) Following https://github.com/wildfly/quickstart/tree/10.x/security-vault-askpass with wildfly-10.1.0-7.fc25.noarch fails

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-8197?page=com.atlassian.jira.plugin.... ] Eduardo Martins closed WFLY-8197. --------------------------------- Resolution: Out of Date Quickstart does not exists since WildFly 11. > Following https://github.com/wildfly/quickstart/tree/10.x/security-vault-askpass with wildfly-10.1.0-7.fc25.noarch fails > ------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-8197 > URL: https://issues.jboss.org/browse/WFLY-8197 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Environment: wildfly-10.1.0-7.fc25.noarch > Reporter: Jan Pazdziora > Assignee: Eduardo Martins > Priority: Trivial > > I try to follow the README in this quickstart but the parameters to the keytool command seem to create keystore which vault.sh does not like, resulting in > {noformat} > Problem occurred: > java.lang.Exception: WFLYSEC0045: Exception encountered: > at org.jboss.as.security.vault.VaultSession.initSecurityVault(VaultSession.java:194) > at org.jboss.as.security.vault.VaultSession.startVaultSession(VaultSession.java:212) > at org.jboss.as.security.vault.VaultTool.execute(VaultTool.java:193) > at org.jboss.as.security.vault.VaultTool.main(VaultTool.java:83) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.modules.Module.run(Module.java:330) > at org.jboss.modules.Main.main(Main.java:505) > Caused by: org.jboss.security.vault.SecurityVaultException: java.lang.RuntimeException: PBOX00137: Security Vault does not contain SecretKey entry under alias (vault) > at org.picketbox.plugins.vault.PicketBoxSecurityVault.readVaultContent(PicketBoxSecurityVault.java:487) > at org.picketbox.plugins.vault.PicketBoxSecurityVault.init(PicketBoxSecurityVault.java:214) > at org.jboss.as.security.vault.VaultSession.initSecurityVault(VaultSession.java:191) > ... 9 more > Caused by: java.lang.RuntimeException: PBOX00137: Security Vault does not contain SecretKey entry under alias (vault) > at org.picketbox.plugins.vault.PicketBoxSecurityVault.readVersionedVaultContent(PicketBoxSecurityVault.java:609) > at org.picketbox.plugins.vault.PicketBoxSecurityVault.readVaultContent(PicketBoxSecurityVault.java:480) > ... 11 more > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11605) Slave Artemis in Wildfly 10.1.0.Final is starting without Master Shutdown - Split brain

by Srinivas ev (Jira)

[ https://issues.jboss.org/browse/WFLY-11605?page=com.atlassian.jira.plugin... ] Srinivas ev updated WFLY-11605: ------------------------------- Attachment: Master and Slave logs.txt > Slave Artemis in Wildfly 10.1.0.Final is starting without Master Shutdown - Split brain > --------------------------------------------------------------------------------------- > > Key: WFLY-11605 > URL: https://issues.jboss.org/browse/WFLY-11605 > Project: WildFly > Issue Type: Bug > Components: Clustering, JMS > Affects Versions: 10.1.0.Final > Reporter: Srinivas ev > Assignee: Jeff Mesnil > Priority: Blocker > Labels: https://developer.jboss.org/thread/279503 > Attachments: Master and Slave logs.txt, Project component log.txt, Wildfly error abrupt failback.txt > > > Scenario - Master, and Slave Running on 2 VM's. > Master Wildfly - <replication-master cluster-name="my-cluster" group-name="srini-queues-cluster-group" check-for-live-server="true"/> > Slave Wildfly - <replication-slave cluster-name="my-cluster" group-name="srini-queues-cluster-group" allow-failback="false" max-saved-replicated-journal-size="1"/> > PFB below 2 errors. > At this time Slave will start deploying Queues even when Master wildfly is not stopped completely. Both management consoles can be reached. > Ideally, the Master server(Wildfly) should completely stop for Slave to start the deployment of queues and start the replication. > 2019/01/16 19:56:21,118+05:30 ERROR [org.apache.activemq.artemis.core.server] (default I/O-2) AMQ224044: error acknowledging message: java.lang.NullPointer > Exception > at org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.removeReferenceByID(ServerConsumerImpl.java:811) > 2019/01/16 19:56:21,121+05:30 ERROR [org.apache.activemq.artemis.core.server] (default I/O-2) AMQ224016: Caught exception: ActiveMQIllegalStateException[er > rorType=ILLEGAL_STATE message=null] > at org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.individualAcknowledge(ServerConsumerImpl.java:772) > at org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.individualAcknowledge(ServerSessionImpl.java:739) > Detailed logs are attached. > At this stage, 1st component in my project pipeline has identified the slave as master now and stick with sending messages to it. Whereas the other components in the pipeline still consuming from Master(based on consumer count). > This caused the break-in message flow. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11605) Slave Artemis in Wildfly 10.1.0.Final is starting without Master Shutdown - Split brain

by Srinivas ev (Jira)

[ https://issues.jboss.org/browse/WFLY-11605?page=com.atlassian.jira.plugin... ] Srinivas ev commented on WFLY-11605: ------------------------------------ Attached a few more logs for analysis. Please let me know if this really a Split brain or some paging problem happened. > Slave Artemis in Wildfly 10.1.0.Final is starting without Master Shutdown - Split brain > --------------------------------------------------------------------------------------- > > Key: WFLY-11605 > URL: https://issues.jboss.org/browse/WFLY-11605 > Project: WildFly > Issue Type: Bug > Components: Clustering, JMS > Affects Versions: 10.1.0.Final > Reporter: Srinivas ev > Assignee: Jeff Mesnil > Priority: Blocker > Labels: https://developer.jboss.org/thread/279503 > Attachments: Master and Slave logs.txt, Project component log.txt, Wildfly error abrupt failback.txt > > > Scenario - Master, and Slave Running on 2 VM's. > Master Wildfly - <replication-master cluster-name="my-cluster" group-name="srini-queues-cluster-group" check-for-live-server="true"/> > Slave Wildfly - <replication-slave cluster-name="my-cluster" group-name="srini-queues-cluster-group" allow-failback="false" max-saved-replicated-journal-size="1"/> > PFB below 2 errors. > At this time Slave will start deploying Queues even when Master wildfly is not stopped completely. Both management consoles can be reached. > Ideally, the Master server(Wildfly) should completely stop for Slave to start the deployment of queues and start the replication. > 2019/01/16 19:56:21,118+05:30 ERROR [org.apache.activemq.artemis.core.server] (default I/O-2) AMQ224044: error acknowledging message: java.lang.NullPointer > Exception > at org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.removeReferenceByID(ServerConsumerImpl.java:811) > 2019/01/16 19:56:21,121+05:30 ERROR [org.apache.activemq.artemis.core.server] (default I/O-2) AMQ224016: Caught exception: ActiveMQIllegalStateException[er > rorType=ILLEGAL_STATE message=null] > at org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.individualAcknowledge(ServerConsumerImpl.java:772) > at org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.individualAcknowledge(ServerSessionImpl.java:739) > Detailed logs are attached. > At this stage, 1st component in my project pipeline has identified the slave as master now and stick with sending messages to it. Whereas the other components in the pipeline still consuming from Master(based on consumer count). > This caused the break-in message flow. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-235) Unused code removal, Map.Entry usage, static inner classes

by Rostislav Svoboda (Jira)

Rostislav Svoboda created LOGMGR-235: ---------------------------------------- Summary: Unused code removal, Map.Entry usage, static inner classes Key: LOGMGR-235 URL: https://issues.jboss.org/browse/LOGMGR-235 Project: JBoss Log Manager Issue Type: Task Reporter: Rostislav Svoboda Assignee: Rostislav Svoboda Unused code removal - private method Map.Entry usage is more efficient than iterating through keySet() & calling map.get(key) static inner classes to avoid reference to the owner object -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4144) Clarification on the semantics of the pre-installed ExampleDS

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-4144?page=com.atlassian.jira.plugin.... ] Brian Stansberry resolved WFLY-4144. ------------------------------------ Assignee: Brian Stansberry (was: Jason Greene) Resolution: Out of Date I'm going to resolve this as out of date, as I was able to rename the ExampleDS in standalone.xml (which is equivalent to adding a 2nd DS that uses the H2 driver and then removing the stock ExampleDS) and the server starts fine. > Clarification on the semantics of the pre-installed ExampleDS > ------------------------------------------------------------- > > Key: WFLY-4144 > URL: https://issues.jboss.org/browse/WFLY-4144 > Project: WildFly > Issue Type: Enhancement > Affects Versions: 8.2.0.Final > Reporter: Lukas Eder > Assignee: Brian Stansberry > Priority: Major > > I'm a new user of WildFly, and I've spent quite a while figuring out that I apparently shouldn't delete the ExampleDS from my server instance. Once I deleted it: > - My own DataSources could no longer access the H2 driver > - My applications could no longer access their own datasources (even unmanaged ones) > - My applications could no longer be undeployed or redeployed > The only workaround I found was to completely re-install the entire server. > Now, I still don't completely understand the point of this ExampleDS, but I'll just leave it where it is and never touch it again. If this is some internal DataSource that is needed for JavaEE 7 compliance as suggested by Roberto Cortez in this Tweet: > https://twitter.com/radcortez/status/539394425370443776 > ... then I would suggest completely hiding it from the Web Console UI and making it an internal system thing that I'm not going to be concerned with. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4300) Different behaviour for jboss-ejb-client.xml configuration when undeploy/deploy or server restart

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-4300?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-4300: -------------------------------------- Assignee: (was: Jason Greene) > Different behaviour for jboss-ejb-client.xml configuration when undeploy/deploy or server restart > ------------------------------------------------------------------------------------------------- > > Key: WFLY-4300 > URL: https://issues.jboss.org/browse/WFLY-4300 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Wolf-Dieter Fink > Priority: Major > > If remote-outbound-connection to a cluster is used and the application contain a jboss-ejb-client.xml with <clusters> element and this element must be changed a simple undeploy/deploy will not change the behavior. A full server restart is needed! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4330) Async service with EJB pool blocks threads not used

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-4330?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-4330: -------------------------------------- Assignee: (was: Jason Greene) > Async service with EJB pool blocks threads not used > --------------------------------------------------- > > Key: WFLY-4330 > URL: https://issues.jboss.org/browse/WFLY-4330 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Affects Versions: 8.2.0.Final > Reporter: Janario Oliveira > Priority: Major > Attachments: wildfly-thread-pool.zip > > > I've created a bean pool to limit the number of some instances. In that case maximum 5 instances. > <pools> > <bean-instance-pools> > <strict-max-pool name="slsb-max5" max-pool-size="5" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/> > ... > </bean-instance-pools> > </pools> > The idea was to have some async service that work simultaneous. > @Stateless > @Pool("slsb-max5") > public class AsyncService { > @Asynchronous > public Future<LocalDateTime> async2Seconds() { > //some parallel work... > } > } > The problem is when I invoke simultaneous more than 5 times it blocks the threads even it is not using (async thread-pool-name="default", default=10) > Attached an example project (configure slsb-max5 pool and access /test-thread-pool/rest/async-resource) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4330) Async service with EJB pool blocks threads not used

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-4330?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-4330: ----------------------------------- Issue Type: Bug (was: Feature Request) > Async service with EJB pool blocks threads not used > --------------------------------------------------- > > Key: WFLY-4330 > URL: https://issues.jboss.org/browse/WFLY-4330 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.2.0.Final > Reporter: Janario Oliveira > Assignee: Jason Greene > Priority: Major > Attachments: wildfly-thread-pool.zip > > > I've created a bean pool to limit the number of some instances. In that case maximum 5 instances. > <pools> > <bean-instance-pools> > <strict-max-pool name="slsb-max5" max-pool-size="5" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/> > ... > </bean-instance-pools> > </pools> > The idea was to have some async service that work simultaneous. > @Stateless > @Pool("slsb-max5") > public class AsyncService { > @Asynchronous > public Future<LocalDateTime> async2Seconds() { > //some parallel work... > } > } > The problem is when I invoke simultaneous more than 5 times it blocks the threads even it is not using (async thread-pool-name="default", default=10) > Attached an example project (configure slsb-max5 pool and access /test-thread-pool/rest/async-resource) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4330) Async service with EJB pool blocks threads not used

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-4330?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-4330: ----------------------------------- Issue Type: Feature Request (was: Bug) > Async service with EJB pool blocks threads not used > --------------------------------------------------- > > Key: WFLY-4330 > URL: https://issues.jboss.org/browse/WFLY-4330 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Affects Versions: 8.2.0.Final > Reporter: Janario Oliveira > Assignee: Jason Greene > Priority: Major > Attachments: wildfly-thread-pool.zip > > > I've created a bean pool to limit the number of some instances. In that case maximum 5 instances. > <pools> > <bean-instance-pools> > <strict-max-pool name="slsb-max5" max-pool-size="5" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/> > ... > </bean-instance-pools> > </pools> > The idea was to have some async service that work simultaneous. > @Stateless > @Pool("slsb-max5") > public class AsyncService { > @Asynchronous > public Future<LocalDateTime> async2Seconds() { > //some parallel work... > } > } > The problem is when I invoke simultaneous more than 5 times it blocks the threads even it is not using (async thread-pool-name="default", default=10) > Attached an example project (configure slsb-max5 pool and access /test-thread-pool/rest/async-resource) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 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 January 2019