jboss-jira June 2014

jboss-jira@lists.jboss.org

1 participants
1515 discussions

[JBoss JIRA] (WFLY-3123) Update Java EE APIs

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3123?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3123: ------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.1.0.Final) > Update Java EE APIs > ------------------- > > Key: WFLY-3123 > URL: https://issues.jboss.org/browse/WFLY-3123 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EE > Reporter: Shelly McGowan > Assignee: Tomaz Cerar > Fix For: 8.2.0.CR1 > > > There were a few bug fix releases of the JBoss Java EE API projects to include in WildFly. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1006) Upgrade XOM to 1.2.10

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1006?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1006: ------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.1.0.Final) > Upgrade XOM to 1.2.10 > --------------------- > > Key: WFLY-1006 > URL: https://issues.jboss.org/browse/WFLY-1006 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: XML Frameworks > Reporter: Júlio Pires > Assignee: Tomaz Cerar > Fix For: 8.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-458) ServerInventory#reconnectServer should take auto-start into account

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-458?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-458: ------------------------------ Fix Version/s: 8.2.0.CR1 (was: 8.1.0.Final) > ServerInventory#reconnectServer should take auto-start into account > ------------------------------------------------------------------- > > Key: WFLY-458 > URL: https://issues.jboss.org/browse/WFLY-458 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Emanuel Muckenhuber > Fix For: 8.2.0.CR1 > > > When reconnecting to stopped (but not removed) servers, the ServerInventory should take the auto-start property into account. Otherwise the process will just get removed, however started with the next :reload of the HC. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3421) Rehashing on view change can result in premature session/ejb expiration

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3421?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3421: ------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.1.0.Final) (was: 9.0.0.Alpha1) > Rehashing on view change can result in premature session/ejb expiration > ----------------------------------------------------------------------- > > Key: WFLY-3421 > URL: https://issues.jboss.org/browse/WFLY-3421 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.1.0.CR2 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Fix For: 8.2.0.CR1 > > > Session/ejb expiration is scheduled only the the owning node of a given session/ejb. When a node leaves each node that assumes ownership of the sessions/ejbs that were previously owned by the leaving node schedules expiration of those sessions. However, view change can also lead to ownership changes for any session/ejb. We are currently handling this properly. If a session/ejb changes ownership, the expiration scheduling is never cancelled, and that session/ejb will expire prematurely, unless the node reacquires ownership. When using sticky sessions, this issue is not apparent, since subsequent requests will direct to the previous owner, who will cancel expiration on the old owner and reschedule expiration on the new owner properly. However, this will be a problem for web sessions if sticky sessions is disabled - and for @Stateful EJBs, if the ejb client receives updated affinity information prior to subsequent requests. > There are at least 2 ways to address this: > # When a request arrives for an existing session/ejb, we immediately cancel any scheduled expiration/eviction. This is currently a unicast, which typically results in a local call - but can go remote if the ownership has changed. Making this a cluster-wide broadcast would fix the issue. > # We can allow the scheduler to expose the set of keys that are currently schedule, and, on topology change, cancel those sessions/ejbs for which the current node is no longer the owner - and reschedule on the new owner. > Option 1 adds an additional cluster-wide RPC per request. > Option 2 adds N*(N-1) unicast RPCs per view change, where N is the cluster size (i.e. each node sends 1 rpc to every other node containing the set of session/ejb IDs to schedule for expiration), > Option 2 is the least invasive solution of the two. > EDIT: There is a 3rd options, i.e. modify the expiration tasks such that they skip expiration if the session/ejb is not owned by the current node. This is prevents the premature expiration issue, but we need some additional strategy to reschedule the session/ejb expiration on the node on the current owner. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3419) beans in module jars are not discovered except the first jar in module

by Petr Sakař (JIRA)

[ https://issues.jboss.org/browse/WFLY-3419?page=com.atlassian.jira.plugin.... ] Petr Sakař commented on WFLY-3419: ---------------------------------- [~swd847] both jar files in module do contain beans.xml - please check module.multiplejars.zip > beans in module jars are not discovered except the first jar in module > ---------------------------------------------------------------------- > > Key: WFLY-3419 > URL: https://issues.jboss.org/browse/WFLY-3419 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CDI / Weld > Affects Versions: 8.0.0.Final, 8.1.0.Final > Reporter: Petr Sakař > Assignee: Jason Greene > Attachments: jboss-module-test.src.zip, module.multiplejars.zip, module.ok.zip, servlet-cdi-test-jar.src.zip, servlet-cdi-test3.src.zip, servlet-cdi-test3.war > > > CDI does not scan module with multiple jars. Only first jar is scanned. > Workaround is to package everything in single jar file. > To reproduce: > {CODE} > #download attached files > #download and unzip wildfly > cd wildfly-9.0.0.Alpha1-SNAPSHOT #or other version > 8.0.0 > unzip ../module.multiplejars.zip > cp ../servlet-cdi-test3.war standalone/deployments/ > ./bin/standalone.sh > # observe deployment fails > # stop server > unzip ../module.ok.zip > ./bin/standalone.sh > # observe deployment succeeds > {CODE} > The same scenario succeeds in both cases on EAP 6.2.x. > module.ok.zip was created from module.multiplejars.zip by merging jar files into single one -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 3 months

1
0
0 / 0

← Newer
1
...
149
150
151
152
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2014