February 2015 - jboss-jira - Jboss List Archives

[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)

8 years, 7 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)

8 years, 7 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)

8 years, 7 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)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1005) SemaphoreArrayListManagedConnectionPool should FIFO

by None None (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1005?page=com.atlassian.jira.plugin... ] None None commented on JBJCA-1005: ---------------------------------- I used Jira to communicate with the developer and not with the community. Made more sense to me in this point. I want to add one more thing because I think you misunderstood me. My point is that now every connection in the pool is used even if the required amount of connections is far less than what is in the pool. Thus, none of these connections can ever timeout (*which was the case before* and is a desired behavior). I hope you get my point. > SemaphoreArrayListManagedConnectionPool should FIFO > --------------------------------------------------- > > Key: JBJCA-1005 > URL: https://issues.jboss.org/browse/JBJCA-1005 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.15.Final, 1.1.0.Beta4 > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.0.16.Final, 1.1.0.Beta5 > > > Currently behaving in FILO manner -- This message was sent by Atlassian JIRA (v6.3.11#6341)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4389) Upgrade HAL to 2.6.4.Final

by Harald Pehl (JIRA)

Harald Pehl created WFLY-4389: --------------------------------- Summary: Upgrade HAL to 2.6.4.Final Key: WFLY-4389 URL: https://issues.jboss.org/browse/WFLY-4389 Project: WildFly Issue Type: Component Upgrade Components: Web Console Reporter: Harald Pehl Assignee: Harald Pehl Fix For: 9.0.0.Beta1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4389) Upgrade HAL to 2.6.4.Final

by Harald Pehl (JIRA)

[ https://issues.jboss.org/browse/WFLY-4389?page=com.atlassian.jira.plugin.... ] Harald Pehl updated WFLY-4389: ------------------------------ Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/6830) > Upgrade HAL to 2.6.4.Final > -------------------------- > > Key: WFLY-4389 > URL: https://issues.jboss.org/browse/WFLY-4389 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Fix For: 9.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1915) JDBC_PING discovery fails when stale entries are found in the database

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1915?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1915: --------------------------- Fix Version/s: 3.6.3 > JDBC_PING discovery fails when stale entries are found in the database > ---------------------------------------------------------------------- > > Key: JGRP-1915 > URL: https://issues.jboss.org/browse/JGRP-1915 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.1 > Reporter: Patrick Haas > Assignee: Bela Ban > Fix For: 3.6.3 > > > Node: "CHQ-PATRICKH-55008" > Database contains two rows.. other node is dead but was unable to remove the JDBC entry. > 1) JChannel.connect(...) > 2) JChannel.down(Event[CONNECT_WITH_STATE_TRANSFER_USE_FLUSH]) > 3) STATE_TRANSFER -> FRAG2 -> MFC -> UFC -> GMS > 4) GMS.down(...) calls out to joinWithStateTransfer -> joinInternal(...) > JDBC pulls the node list from the database table. > Ping Data: > - CHQ-PATRICKH-3895, name=CHQ-PATRICKH-3895, addr=10.1.130.228:55503, server > - CHQ-PATRICKH-55008, name=CHQ-PATRICKH-55008, addr=10.1.130.228:57489 > joinInternal is a never-terminating while loop: > - down: Event.FIND_INITIAL_MBRS_EVT > - inspect responses -- no valid join responses > - responses are NOT empty -> does not become singletonMember > - gets all coordinators (none) > - Sorts all nodes by GUID in a TreeSet > - Is first of all joiners? > - No, another joiner is listed first > ... repeat forever > When the process is restarted and a node ID < than the existing db entry is generated, it successfully takes over as owner. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4386) EJB annotations ignored if classes are packaged as JBOSS modules

by Jan Martiska (JIRA)

[ https://issues.jboss.org/browse/WFLY-4386?page=com.atlassian.jira.plugin.... ] Jan Martiska commented on WFLY-4386: ------------------------------------ Well, I agree that it's confusing. But I suspect there are reasons for it to be that way. For example, if a module contains EJB beans and your application depends on that module, but you want to choose whether the application should deploy those EJBs (including JNDI entries etc.) as if they were part of the application. Because that's what it will do if the app imports annotations from the module. > EJB annotations ignored if classes are packaged as JBOSS modules > ---------------------------------------------------------------- > > Key: WFLY-4386 > URL: https://issues.jboss.org/browse/WFLY-4386 > Project: WildFly > Issue Type: Bug > Components: Class Loading, EJB > Affects Versions: JBoss AS7 7.1.1.Final > Reporter: Tihomir Meščić > Assignee: David Lloyd > > I have an EJB that writes something to the DB and I have a custom checked exception that is marked as @javax.ejb.ApplicationException(rollback=true), which means that when the exception is thrown, transaction should be rollbacked. > {code:title=Test.java.java|borderStyle=solid} > @ApplicationException(rollback=true) > public class MyException extends Exception { > {code} > > This exception is packaged in a separate JAR. > > When this JAR is included in the lib/ folder of the EAR with my EJB, everything works as expected (when the EJB throws MyException, the transaction is rollbacked). > However, when this JAR is deployed as a JBOSS module (so, in jboss_folder/modules/... folder), and the EAR declares a dependency on this module (MANIFEST.MF -> Dependencies: ....) , then the transaction is NOT rollbacked. So the EJB container ignores the annotation. > > One workaround (that I don't really like) is to specify that this is an application exception in the jboss-ejb3.xml (then, the transaction will be rollbacked). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4387) Unable to configure ajaxTimeout in wildfly 8.2_Final

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-4387?page=com.atlassian.jira.plugin.... ] Stuart Douglas closed WFLY-4387. -------------------------------- Resolution: Rejected Please use the forum to ask for help. There is nothing in Wildfly that will throw an exception after 10 seconds, most likely it is something in your application. > Unable to configure ajaxTimeout in wildfly 8.2_Final > ---------------------------------------------------- > > Key: WFLY-4387 > URL: https://issues.jboss.org/browse/WFLY-4387 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.2.0.Final > Environment: OS : Windows 8.1 > WildFly: 8.2_Final > Reporter: Manjunatha KB > Assignee: Jason Greene > Labels: wildfly > > Hi. Am newbie to wildfly. Am facing an issue in getting ajax response as my DB is taking some quite time due to huge data. I guess wildfly is throwing internal server error after exactly 10 seconds of request time. So i need to know is there is any attribute which I need to set in standalone.xml to increase this timeout. Exactly as there is "ajaxTimeOut" in apache Tomcat. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

8 years, 7 months

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2015