June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-88) Recovery not fully triggered when distributed transaction falls down at prepare phase of 2PC

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-88?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-88: --------------------------------------------- Radovan STANCEL <rstancel(a)redhat.com> changed the Status of [bug 952746|https://bugzilla.redhat.com/show_bug.cgi?id=952746] from ASSIGNED to NEW > Recovery not fully triggered when distributed transaction falls down at prepare phase of 2PC > -------------------------------------------------------------------------------------------- > > Key: WFLY-88 > URL: https://issues.jboss.org/browse/WFLY-88 > Project: WildFly > Issue Type: Bug > Components: EJB, Remoting > Reporter: Ivo Studensky > Assignee: jaikiran pai > Fix For: 8.0.0.Alpha1 > > Attachments: logs_prepareHaltClient.tgz > > > It looks like recovery process is not fully triggered on a distributed transaction when the transaction falls down at prepare phase of 2PC. In the new crash recovery tests over propagated transactions only one of two servers recovers from the crash, but the other keeps an unfinished tx in its tx log. > It corresponds to prepareHaltClient and prepareHaltServer test methods of org.jboss.as.test.jbossts.crashrec.txpropagation.TxPropagationCrashRecoveryTestCase, see JBQA-2604 for general description of the new tests. The prepareHaltClient test crashes the server which initiated the transaction, while as the prepareHaltServer test crashes the second server. > The tests are written against EAP6.x branch, so for reproducing this it is needed a built server from the 7.1 branch of AS7. > Steps to reproduce. > 1. git clone -b as7 git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-transactions.git > 2. cd eap-tests-transactions > 3. git checkout tx_propag_crashrec_tests > 4a. mvn clean verify -Dtest=TxPropagationCrashRecoveryTestCase#prepareHaltClient -Djboss.dist=<path to jboss-as-7.1.3.Final-SNAPSHOT> > or > 4b. mvn clean verify -Dtest=TxPropagationCrashRecoveryTestCase#prepareHaltServer -Djboss.dist=<path to jboss-as-7.1.3.Final-SNAPSHOT> > The logs of prepareHaltClient run attached to this jira. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1612) Throw compilation error when using collect hit policy with aggr. function and multiple outputs

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1612?page=com.atlassian.jira.plugi... ] Tibor Zimányi commented on DROOLS-1612: --------------------------------------- PR with reproducer is here: https://github.com/kiegroup/drools/pull/1320 The test for this is DMNDecisionTableHitPolicyTest.testSimpleDecisionTableHitPolicyCollectSumMultipleOutputs(). > Throw compilation error when using collect hit policy with aggr. function and multiple outputs > ---------------------------------------------------------------------------------------------- > > Key: DROOLS-1612 > URL: https://issues.jboss.org/browse/DROOLS-1612 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.0.0.Final > Reporter: Tibor Zimányi > Assignee: Edson Tirelli > Fix For: 7.1.0.Final > > > According to the DMN spec., "Decision tables with compound outputs support only the following hit policies: Unique, Any, Priority, First, Output > order, Rule order and Collect without operator, because the collect operator is undefined over multiple outputs." > However when I use decision table with "COLLECT" hit policy, "sum" aggregate function and multiple outputs, the table compiles. When evaluating the table, I get nulls as output value results, but no error message in DMNResult. > I will provide a reproducer in a PR. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1613) NPE when evaluating a DMN decision table with multiple outputs and one of the outputs has wrong type

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1613?page=com.atlassian.jira.plugi... ] Tibor Zimányi commented on DROOLS-1613: --------------------------------------- PR with reproducer is her: https://github.com/kiegroup/drools/pull/1320 Reproducer test is DMNDecisionTableRuntimeTest.testSimpleDecisionTableMultipleOutputWrongOutputType(). > NPE when evaluating a DMN decision table with multiple outputs and one of the outputs has wrong type > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-1613 > URL: https://issues.jboss.org/browse/DROOLS-1613 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.0.0.Final > Reporter: Tibor Zimányi > Assignee: Matteo Mortari > Fix For: 7.1.0.Final > > > When I have a decision table with hit policy Priority and multiple outputs and I change one of the outputs in a rule to a wrong type, the evaluation ends with NullPointerException. > E.g. having output entry like this: > <outputEntry id="_7f03803d-2636-40ab-8346-7fd7f38ab695-3"> > <text>1</text> > </outputEntry> > I will provide PR with reproducer for this. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1613) NPE when evaluating a DMN decision table with multiple outputs and one of the outputs has wrong type

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1613?page=com.atlassian.jira.plugi... ] Tibor Zimányi edited comment on DROOLS-1613 at 6/13/17 6:32 AM: ---------------------------------------------------------------- PR with reproducer is here: https://github.com/kiegroup/drools/pull/1320 Reproducer test is DMNDecisionTableRuntimeTest.testSimpleDecisionTableMultipleOutputWrongOutputType(). was (Author: tzimanyi): PR with reproducer is her: https://github.com/kiegroup/drools/pull/1320 Reproducer test is DMNDecisionTableRuntimeTest.testSimpleDecisionTableMultipleOutputWrongOutputType(). > NPE when evaluating a DMN decision table with multiple outputs and one of the outputs has wrong type > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-1613 > URL: https://issues.jboss.org/browse/DROOLS-1613 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.0.0.Final > Reporter: Tibor Zimányi > Assignee: Matteo Mortari > Fix For: 7.1.0.Final > > > When I have a decision table with hit policy Priority and multiple outputs and I change one of the outputs in a rule to a wrong type, the evaluation ends with NullPointerException. > E.g. having output entry like this: > <outputEntry id="_7f03803d-2636-40ab-8346-7fd7f38ab695-3"> > <text>1</text> > </outputEntry> > I will provide PR with reproducer for this. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1614) Revise coverage of DMN decision tables runtime tests

by Tibor Zimányi (JIRA)

Tibor Zimányi created DROOLS-1614: ------------------------------------- Summary: Revise coverage of DMN decision tables runtime tests Key: DROOLS-1614 URL: https://issues.jboss.org/browse/DROOLS-1614 Project: Drools Issue Type: Task Components: dmn engine Affects Versions: 7.0.0.Final Reporter: Tibor Zimányi Assignee: Tibor Zimányi Fix For: 7.1.0.Final Revision of DMN decision tables runtime tests should be made. I will provide PR for this. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8928) JMS broker does not allow the use of a transacted session in a Servlet

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-8928?page=com.atlassian.jira.plugin.... ] Jeff Mesnil moved JBEAP-11515 to WFLY-8928: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8928 (was: JBEAP-11515) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: ActiveMQ) (was: JMS) Affects Version/s: 11.0.0.Alpha1 (was: 7.0.0.GA) (was: 7.1.0.DR14) (was: 7.1.0.DR18) > JMS broker does not allow the use of a transacted session in a Servlet > ---------------------------------------------------------------------- > > Key: WFLY-8928 > URL: https://issues.jboss.org/browse/WFLY-8928 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 11.0.0.Alpha1 > Environment: JBoss-EAP-7.0.0 > ActiveMQ Artemis 1.1.0.SP16 > Reporter: Jeff Mesnil > Assignee: Andy Taylor > Priority: Blocker > > The JMS broker does not allow the creation of a transacted session inside a Servlet. It is essential for a Servlet to use a transacted session at the absence of JTA support. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2883) Unignore RemoveManagementRealmTestCase

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2883?page=com.atlassian.jira.plugi... ] Jean-Francois Denise updated WFCORE-2883: ----------------------------------------- Comment: was deleted (was: There is no PR yet.) > Unignore RemoveManagementRealmTestCase > -------------------------------------- > > Key: WFCORE-2883 > URL: https://issues.jboss.org/browse/WFCORE-2883 > Project: WildFly Core > Issue Type: Task > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > Unignore it once CLI is based on aesh-readline. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2948) Errors publishing a large deployment to a remote server (EAP 7.1 management)

by Michal Jurc (JIRA)

Michal Jurc created WFCORE-2948: ----------------------------------- Summary: Errors publishing a large deployment to a remote server (EAP 7.1 management) Key: WFCORE-2948 URL: https://issues.jboss.org/browse/WFCORE-2948 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Michal Jurc Assignee: ehsavoie Hugonnet I tried to verify EAP 7.1 incremental deployment (JBIDE-23784). So I first deployed a simple dynamic web project over management API to a remote EAP 7.1 (on a remote machine). Everything fine so far. Then I just copied a big jar (devstudio installer) into the WebContent dir of the project. Then I did a Refresh of the project in Eclipse and I immediately got an error: {code} Could not publish to the server. org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.util.concurrent.ExecutionException: Operation failed at org.jboss.ide.eclipse.as.internal.management.wf11.DeploymentOperationResult.getStatus(DeploymentOperationResult.java:68) at org.jboss.ide.eclipse.as.internal.management.wf11.WildFly11Manager.waitFor(WildFly11Manager.java:231) at org.jboss.ide.eclipse.as.internal.management.wf11.WildFly11Manager.incrementalPublish(WildFly11Manager.java:601) at org.jboss.ide.eclipse.as.internal.management.wf11.WildFly11ManagerService.incrementalPublish(WildFly11ManagerService.java:201) at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.incrementalPublish(JBoss7ManagerServiceProxy.java:134) at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController$IncrementalManagementPublishRunner.incrementalPublish(ManagementPublishController.java:530) at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.incrementalPublish(ManagementPublishController.java:474) at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.publishModule(ManagementPublishController.java:257) at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.publishModule(ControllableServerBehavior.java:143) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1091) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1183) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:987) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3182) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:355) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) Caused by: java.util.concurrent.ExecutionException: Operation failed at org.jboss.threads.AsyncFutureTask.operationFailed(AsyncFutureTask.java:74) at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:281) at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:62) at org.jboss.as.controller.client.impl.ConvertingDelegatingAsyncFuture.get(ConvertingDelegatingAsyncFuture.java:69) at org.jboss.as.controller.client.impl.ConvertingDelegatingAsyncFuture.get(ConvertingDelegatingAsyncFuture.java:41) at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:94) at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42) at org.jboss.ide.eclipse.as.internal.management.wf11.DeploymentOperationResult.getStatus(DeploymentOperationResult.java:65) ... 15 more Caused by: java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOf(Arrays.java:3236) at java.io.ByteArrayOutputStream.grow(ByteArrayOutputStream.java:118) at java.io.ByteArrayOutputStream.ensureCapacity(ByteArrayOutputStream.java:93) at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:153) at org.jboss.as.protocol.StreamUtils.copyStream(StreamUtils.java:52) at org.jboss.as.controller.client.impl.InputStreamEntry$InMemoryEntry.initialize(InputStreamEntry.java:76) at org.jboss.as.controller.client.impl.AbstractModelControllerClient$ReadAttachmentInputStreamRequestHandler$1.execute(AbstractModelControllerClient.java:220) at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at org.jboss.threads.JBossThread.run(JBossThread.java:320) {code} The server adapter showed [Republish]. So I tried to do a full publish, but that kind of failed. It first showed 19 %, now it's been at 29 % for 5 minutes and nothing seems to be happening. The server adapter says [Started, Publishing...] and the module says [Republish]. And I can't even stop the server, it's stuck. I restarted the IDE. Killed the EAP server on the remote host. Started the server again in the IDE. It showed my module is started. The index worked, the jar was not found. So now I did a full publish on the module. I could see that something was being sent over the network. Then the traffic was over and it was at 33 % for a while and finally it finished successfully this time. So at least that. Then I could add another jsp and it redeployed the module without having to send over the big file again. So at least that worked now. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1242) External CS, create attribute is ignored

by Martin Choma (JIRA)

Martin Choma created ELY-1242: --------------------------------- Summary: External CS, create attribute is ignored Key: ELY-1242 URL: https://issues.jboss.org/browse/ELY-1242 Project: WildFly Elytron Issue Type: Bug Reporter: Martin Choma Assignee: Darran Lofthouse Priority: Blocker {{location=secretdatafile}} have to exists, otherwise there occures NoSuchFileException {code} 09:13:34,368 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service org.wildfly.security.credential-store.fips-credential-store: org.jboss.msc.service.StartException in service org.wildfly.security.credential-store.fips-credential-store: WFLYELY00004: Unable to start the service. at org.wildfly.extension.elytron.CredentialStoreService.start(CredentialStoreService.java:123) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: org.wildfly.security.credential.store.CredentialStoreException: ELY09514: Unable to initialize credential store at org.wildfly.security.credential.store.impl.KeyStoreCredentialStore.setupExternalStorage(KeyStoreCredentialStore.java:945) at org.wildfly.security.credential.store.impl.KeyStoreCredentialStore.load(KeyStoreCredentialStore.java:821) at org.wildfly.security.credential.store.impl.KeyStoreCredentialStore.initialize(KeyStoreCredentialStore.java:213) at org.wildfly.security.credential.store.CredentialStore.initialize(CredentialStore.java:159) at org.wildfly.extension.elytron.CredentialStoreService.start(CredentialStoreService.java:117) ... 5 more Caused by: java.nio.file.NoSuchFileException: /home/mchoma/workspace/git-repositories/tests-security/fips/target/fips-cs-workdir/secure-data-file at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214) at java.nio.file.Files.newByteChannel(Files.java:361) at java.nio.file.Files.newByteChannel(Files.java:407) at java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:384) at java.nio.file.Files.newInputStream(Files.java:152) at org.wildfly.security.credential.store.impl.KeyStoreCredentialStore.setupExternalStorage(KeyStoreCredentialStore.java:936) ... 9 more 09:13:34,372 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "elytron"), ("credential-store" => "fips-credential-store") ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.security.credential-store.fips-credential-store" => "WFLYELY00004: Unable to start the service. Caused by: org.wildfly.security.credential.store.CredentialStoreException: ELY09514: Unable to initialize credential store Caused by: java.nio.file.NoSuchFileException: /home/mchoma/workspace/git-repositories/tests-security/fips/target/fips-cs-workdir/secure-data-file"}} {code} There is missing branch in code when {{create = true}} and {{dataLocation != null}} {code} if (useExternalStorage) { dataLocation = externalPath; setupExternalStorage(type, location); } else { dataLocation = location; keyStore = getKeyStoreInstance(type); } if (create) { if (dataLocation == null) { try { keyStore.load(null, null); } catch (CertificateException | IOException | NoSuchAlgorithmException e) { throw log.cannotInitializeCredentialStore(e); } } } {code} This issue pops up in ER1, because file based external CS feature was delivered in ER1 (JBEAP-10803) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-161) AsyncHandler is always creating a stacktrace dump

by Koen Janssens (JIRA)

Koen Janssens created LOGMGR-161: ------------------------------------ Summary: AsyncHandler is always creating a stacktrace dump Key: LOGMGR-161 URL: https://issues.jboss.org/browse/LOGMGR-161 Project: JBoss Log Manager Issue Type: Enhancement Components: core Affects Versions: 2.1.0.Alpha1 Reporter: Koen Janssens I have noticed that when introducing an AsyncHandler for logging, all log statement are copied before being put on the queue and as part of that copy a complete stack dump is done. This might be useful if the stack info is used by a downstream formatter (eg for line number identification), but even if the line numbers are not used anywhere, this still happens. I think this behavior should be at least optional. Source Location: org.jboss.logmanager.ExtLogRecord#copyAll -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 June 2017