February 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4390) restartable=false bach job can be restarted

by Takashi Nishigaya (JIRA)

[ https://issues.jboss.org/browse/WFLY-4390?page=com.atlassian.jira.plugin.... ] Takashi Nishigaya updated WFLY-4390: ------------------------------------ Attachment: batch-restartable.zip > restartable=false bach job can be restarted > ------------------------------------------- > > Key: WFLY-4390 > URL: https://issues.jboss.org/browse/WFLY-4390 > Project: WildFly > Issue Type: Bug > Components: Batch > Affects Versions: 8.2.0.Final > Reporter: Takashi Nishigaya > Assignee: Jason Greene > Attachments: batch-restartable.zip > > > The batch job defined with restartable=false must not be restartable, after failed or stopped. > GlassFish 4.1 results in the following: > [2015-02-26T19:56:34.860+0900] [glassfish 4.1] [SEVERE] [] [] [tid: _ThreadID=25 _ThreadName=Thread-9] [timeMillis: 1424948194860] [levelValue: 1000] [[ > javax.batch.operations.JobRestartException: javax.batch.operations.JobRestartException: Job Restartable attribute is false, Job cannot be restarted. > But WildFly tries to execute the stopped or failed job. > Please check the attached test case. > wildfly: > $ mvn clean test -P wildfly-managed (or -P wildly-remote) > glassfish: > $ glassfish4/bin/asadmin start-domain > $ mvn clean test -P glassfish-remote -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4390) restartable=false bach job can be restarted

by Takashi Nishigaya (JIRA)

[ https://issues.jboss.org/browse/WFLY-4390?page=com.atlassian.jira.plugin.... ] Takashi Nishigaya updated WFLY-4390: ------------------------------------ Description: The batch job defined with restartable=false must not be restartable, after failed or stopped. GlassFish 4.1 results in the following: [2015-02-26T19:56:34.860+0900] [glassfish 4.1] [SEVERE] [] [] [tid: _ThreadID=25 _ThreadName=Thread-9] [timeMillis: 1424948194860] [levelValue: 1000] [[ javax.batch.operations.JobRestartException: javax.batch.operations.JobRestartException: Job Restartable attribute is false, Job cannot be restarted. But WildFly tries to execute the stopped or failed job. Please check the attached test case. wildfly: $ mvn clean test -P wildfly-managed (or -P wildly-remote) glassfish: $ glassfish4/bin/asadmin start-domain $ mvn clean test -P glassfish-remote was: The batch job defined with restartable=false must not be restartable, after failed or stopped. GlassFish 4.1 results in the following: [2015-02-26T19:56:34.860+0900] [glassfish 4.1] [SEVERE] [] [] [tid: _ThreadID=25 _ThreadName=Thread-9] [timeMillis: 1424948194860] [levelValue: 1000] [[ javax.batch.operations.JobRestartException: javax.batch.operations.JobRestartException: Job Restartable attribute is false, Job cannot be restarted. But WildFly tries to execute the stopped or failed job. > restartable=false bach job can be restarted > ------------------------------------------- > > Key: WFLY-4390 > URL: https://issues.jboss.org/browse/WFLY-4390 > Project: WildFly > Issue Type: Bug > Components: Batch > Affects Versions: 8.2.0.Final > Reporter: Takashi Nishigaya > Assignee: Jason Greene > > The batch job defined with restartable=false must not be restartable, after failed or stopped. > GlassFish 4.1 results in the following: > [2015-02-26T19:56:34.860+0900] [glassfish 4.1] [SEVERE] [] [] [tid: _ThreadID=25 _ThreadName=Thread-9] [timeMillis: 1424948194860] [levelValue: 1000] [[ > javax.batch.operations.JobRestartException: javax.batch.operations.JobRestartException: Job Restartable attribute is false, Job cannot be restarted. > But WildFly tries to execute the stopped or failed job. > Please check the attached test case. > wildfly: > $ mvn clean test -P wildfly-managed (or -P wildly-remote) > glassfish: > $ glassfish4/bin/asadmin start-domain > $ mvn clean test -P glassfish-remote -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4390) restartable=false bach job can be restarted

by Takashi Nishigaya (JIRA)

[ https://issues.jboss.org/browse/WFLY-4390?page=com.atlassian.jira.plugin.... ] Takashi Nishigaya updated WFLY-4390: ------------------------------------ Description: The batch job defined with restartable=false must not be restartable, after failed or stopped. GlassFish 4.1 results in the following: [2015-02-26T19:56:34.860+0900] [glassfish 4.1] [SEVERE] [] [] [tid: _ThreadID=25 _ThreadName=Thread-9] [timeMillis: 1424948194860] [levelValue: 1000] [[ javax.batch.operations.JobRestartException: javax.batch.operations.JobRestartException: Job Restartable attribute is false, Job cannot be restarted. But WildFly tries to execute the stopped or failed job. > restartable=false bach job can be restarted > ------------------------------------------- > > Key: WFLY-4390 > URL: https://issues.jboss.org/browse/WFLY-4390 > Project: WildFly > Issue Type: Bug > Components: Batch > Affects Versions: 8.2.0.Final > Reporter: Takashi Nishigaya > Assignee: Jason Greene > > The batch job defined with restartable=false must not be restartable, after failed or stopped. > GlassFish 4.1 results in the following: > [2015-02-26T19:56:34.860+0900] [glassfish 4.1] [SEVERE] [] [] [tid: _ThreadID=25 _ThreadName=Thread-9] [timeMillis: 1424948194860] [levelValue: 1000] [[ > javax.batch.operations.JobRestartException: javax.batch.operations.JobRestartException: Job Restartable attribute is false, Job cannot be restarted. > But WildFly tries to execute the stopped or failed job. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4390) restartable=false bach job can be restarted

by Takashi Nishigaya (JIRA)

[ https://issues.jboss.org/browse/WFLY-4390?page=com.atlassian.jira.plugin.... ] Takashi Nishigaya updated WFLY-4390: ------------------------------------ Component/s: Batch > restartable=false bach job can be restarted > ------------------------------------------- > > Key: WFLY-4390 > URL: https://issues.jboss.org/browse/WFLY-4390 > Project: WildFly > Issue Type: Bug > Components: Batch > Affects Versions: 8.2.0.Final > Reporter: Takashi Nishigaya > Assignee: Jason Greene > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4390) restartable=false bach job can be restarted

by Takashi Nishigaya (JIRA)

[ https://issues.jboss.org/browse/WFLY-4390?page=com.atlassian.jira.plugin.... ] Takashi Nishigaya updated WFLY-4390: ------------------------------------ Affects Version/s: 8.2.0.Final > restartable=false bach job can be restarted > ------------------------------------------- > > Key: WFLY-4390 > URL: https://issues.jboss.org/browse/WFLY-4390 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.2.0.Final > Reporter: Takashi Nishigaya > Assignee: Jason Greene > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4390) restartable=false bach job can be restarted

by Takashi Nishigaya (JIRA)

Takashi Nishigaya created WFLY-4390: --------------------------------------- Summary: restartable=false bach job can be restarted Key: WFLY-4390 URL: https://issues.jboss.org/browse/WFLY-4390 Project: WildFly Issue Type: Bug Reporter: Takashi Nishigaya Assignee: Jason Greene -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1907) ENCRYPT: asymmetric encryption fails on merge

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-1907?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JGRP-1907: ----------------------------------------------- Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1187193|https://bugzilla.redhat.com/show_bug.cgi?id=1187193] from ASSIGNED to POST > ENCRYPT: asymmetric encryption fails on merge > --------------------------------------------- > > Key: JGRP-1907 > URL: https://issues.jboss.org/browse/JGRP-1907 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.6.2 > > Attachments: encrypt.xml, EncryptKeyStore.xml > > > {{ENCRYPT}} fails to communicate after a network split and subsequent merge with asymmetric encryption. This works with symmetric encryption. > To reproduce: > * Members A and B > * Add {{<DISCARD use_gui="true"/>}} on top of {{UDP}} > * Form cluster {{(A,B)}} > * Create a network split: {{(A)}} and {{(B)}} > * Remove the network split > * Observe that with both symmetric and asymmetric encryption, the merge forms cluster {{(A,B)}} > * However, with asymmetric encryption, {{ENCRYPT}} fails to process any messages and rejects all messages, whereas with symmetric encryption, this works. > * Symmetric encryption: {{EncryptKeyStore.xml}} > * Asymmetric encryption: {{encrypt.xml}} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-728) Rule with temporal operator incorrectly fires after KieSession serialization.

by Duncan Doyle (JIRA)

Duncan Doyle created DROOLS-728: ----------------------------------- Summary: Rule with temporal operator incorrectly fires after KieSession serialization. Key: DROOLS-728 URL: https://issues.jboss.org/browse/DROOLS-728 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 6.2.0.CR4 Environment: Mac OS X 10.10.2, Oracle Hotsport 1.7.0_71 Reporter: Duncan Doyle Assignee: Mario Fusco See the following reproducer: https://github.com/DuncanDoyle/drools-serialization-temporal-operators-issue Clone the repo and run: 'mvn clean test' What I'm trying to do is, for long running CEP sessions, change the underlying KieBase after a KieSession serialisation. The use-case is that our session can hold Events for weeks, maybe months. We periodically save the session to create save points to accommodate for engine crashes (so we can reload). We also want to be able to add new rules to our KieBase, without invalidating the session (if we would have to load a new KieSession after we've changed our rules this, would't allow us to use long running CEP sessions, we would loose events). This seems to be possible by serializing the session, and de-serializing it with a new (updated) KieBase. And there is where I see strange behaviour. My first unit test works correctly, I serialize the session and de-serialize it with the same KieBase and everything works as expected. However, my second unit-tests de-serializes the KieSession with a new KieBase which has a single additional rule (rule 3). This causes my rule with temporal operator (rule 2 in my reproducer) to incorrectly fire for one of the events (event 1). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-230) Failure by ProcessController to launch a server vm is not logged

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-230?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet commented on WFCORE-230: ------------------------------------------ This seems to be the case since 2012 at least. Found no evidence on why it shouldn't be this way > Failure by ProcessController to launch a server vm is not logged > ---------------------------------------------------------------- > > Key: WFCORE-230 > URL: https://issues.jboss.org/browse/WFCORE-230 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha11 > Reporter: Brian Stansberry > Assignee: ehsavoie Hugonnet > Fix For: 1.0.0.CR1 > > > In a domain configuration, if a server is associated with an incorrectly configurated jvm java-home (e.g. domain.xml -> server-groups -> jvm), it will fail silently (no error shown in logs). For example: > ``` > <server-group name="mySrvrGrp" profile="full"> > <jvm name="my-default" java-home="/usr/java/wrongPath"> > <heap size="1024m" max-size="4096m"/> > <permgen size="256m" max-size="256m"/> > <stack size="256k"/> > ``` -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-562) Wrong order of elements in jboss-cli.xml

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-562?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-562: ------------------------------------------------ Dominik Pospisil <dpospisi(a)redhat.com> changed the Status of [bug 1195132|https://bugzilla.redhat.com/show_bug.cgi?id=1195132] from ASSIGNED to POST > Wrong order of elements in jboss-cli.xml > ---------------------------------------- > > Key: WFCORE-562 > URL: https://issues.jboss.org/browse/WFCORE-562 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 1.0.0.Alpha19 > Reporter: Dominik Pospisil > Assignee: Dominik Pospisil > Fix For: 1.0.0.Beta1 > > > File bin/jboss-cli.xml has an incorrect order of elements. <history> tag should be before <resolve-parameter-values> tag. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 February 2015