July 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3805) JGroupsBroadcastGroupConfiguration Serialization Problem

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3805?page=com.atlassian.jira.plugin.... ] Jason Greene reopened WFLY-3805: -------------------------------- > JGroupsBroadcastGroupConfiguration Serialization Problem > -------------------------------------------------------- > > Key: WFLY-3805 > URL: https://issues.jboss.org/browse/WFLY-3805 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 8.1.0.Final > Reporter: Yong Hao Gao > Assignee: Yong Hao Gao > Fix For: 10.1.0.CR1 > > > When configuring JMS connection factories using jgroups discovery group, the client will get serialization exceptions because we pass a JChannel which is not serializable. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3805) JGroupsBroadcastGroupConfiguration Serialization Problem

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3805?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3805: ------------------------------- Fix Version/s: No Release (was: 10.1.0.CR1) > JGroupsBroadcastGroupConfiguration Serialization Problem > -------------------------------------------------------- > > Key: WFLY-3805 > URL: https://issues.jboss.org/browse/WFLY-3805 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 8.1.0.Final > Reporter: Yong Hao Gao > Assignee: Yong Hao Gao > Fix For: No Release > > > When configuring JMS connection factories using jgroups discovery group, the client will get serialization exceptions because we pass a JChannel which is not serializable. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-264) Add support for use1PcForAutoCommitTransactions

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-264?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-264: ------------------------------ Fix Version/s: 10.1.0.Final (was: 10.1.0.CR1) > Add support for use1PcForAutoCommitTransactions > ----------------------------------------------- > > Key: WFLY-264 > URL: https://issues.jboss.org/browse/WFLY-264 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Priority: Minor > Fix For: 10.1.0.Final > > > Since clustered web sessions/SFSBs won't ever incur inter-node concurrent access, we can tolerate a 1PC commit optimization - which will reduce the number of RPCs involved in replication/distribution. This should result it a significant performance gains for REPL_SYNC and DIST_SYNC caches. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2845) On WildFly clean shutdown: failed marshalling rsp (UnsuccessfulResponse)

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2845?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2845: ------------------------------- Fix Version/s: 10.1.0.Final (was: 10.1.0.CR1) > On WildFly clean shutdown: failed marshalling rsp (UnsuccessfulResponse) > ------------------------------------------------------------------------ > > Key: WFLY-2845 > URL: https://issues.jboss.org/browse/WFLY-2845 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.0.0.CR1 > Environment: RHEL6 x86_64; Oracle JDK 7 > Reporter: Michal Karm Babacek > Assignee: Paul Ferraro > Labels: clustering > Fix For: 10.1.0.Final > > > I've got two standalone-ha instances running on a one box. Each of these instances has {{<distributable/>}} [clusterbench|https://github.com/Karm/clusterbench/tree/simplified-and-pure] app deployed. When I start to shut the instances down via CLI command, one of them throws: > {noformat} > 08:59:33,341 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-4,shared=udp) ISPN000094: Received new cluster view: [jboss-eap-8.0/web|4] (1) [jboss-eap-8.0/web] > 08:59:33,368 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000082: Stopping the RpcDispatcher > 08:59:33,379 ERROR [org.jgroups.blocks.RequestCorrelator] (remote-thread-0) failed marshalling rsp (UnsuccessfulResponse): java.lang.NullPointerException > 08:59:33,380 ERROR [org.jgroups.blocks.RequestCorrelator] (remote-thread-1) failed marshalling rsp (UnsuccessfulResponse): java.lang.NullPointerException > 08:59:33,392 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015950: WildFly 8.0.0.Final-SNAPSHOT "WildFly" stopped in 558ms > {noformat} > In the log. It's a non-deterministic problem and it does not emerge always. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2297) Log reasons for implicit dependencies

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2297?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2297: ------------------------------- Fix Version/s: 10.1.0.Final (was: 10.1.0.CR1) > Log reasons for implicit dependencies > ------------------------------------- > > Key: WFLY-2297 > URL: https://issues.jboss.org/browse/WFLY-2297 > Project: WildFly > Issue Type: Enhancement > Reporter: David Lloyd > Priority: Minor > Fix For: 10.1.0.Final > > > We should log a {{DEBUG}} or {{TRACE}} message whenever we add an implicit dependency to a module, documenting the reason for the addition (e.g. adding because it's a servlet deployment, or because a particular annotation was used, etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2100) Vault.sh logging improvements

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2100?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2100: ------------------------------- Fix Version/s: 10.1.0.Final (was: 10.1.0.CR1) > Vault.sh logging improvements > ----------------------------- > > Key: WFLY-2100 > URL: https://issues.jboss.org/browse/WFLY-2100 > Project: WildFly > Issue Type: Feature Request > Components: Security > Affects Versions: 8.0.0.Alpha4 > Reporter: Chris Dolphy > Assignee: Peter Skopek > Fix For: 10.1.0.Final > > > Several errors with vault.sh (ineractive Vault Tool) do not display enough information to debug. > For example, "Exception occurred:PBOX000128: Unable to encrypt data". It would be nice if there was some way to see the cause of this exception either with additional logging options, a verbose option or by default. This one is caused by VaultInteraction.java only displaying the localized error message of the exception. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1535) SSLEJBRemoteClientTestCase runs into intermittent failures

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1535?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1535: ------------------------------- Fix Version/s: 10.1.0.Final (was: 10.1.0.CR1) > SSLEJBRemoteClientTestCase runs into intermittent failures > ---------------------------------------------------------- > > Key: WFLY-1535 > URL: https://issues.jboss.org/browse/WFLY-1535 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 8.0.0.Alpha1 > Reporter: jaikiran pai > Assignee: Paul Ferraro > Fix For: 10.1.0.Final > > > SSLEJBRemoteClientTestCase runs into intermittent failures on TeamCity. To make matters worse, a failure in one test method can have a side effect on other test methods in that testcase, given the way it's written. The entire run is here http://teamcity.cafe-babe.org/viewLog.html?buildId=5251&tab=buildResultsD.... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-459) javassist should also be exported to Hibernate (native) applications

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-459?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-459: ------------------------------ Fix Version/s: 10.1.0.Final (was: 10.1.0.CR1) > javassist should also be exported to Hibernate (native) applications > -------------------------------------------------------------------- > > Key: WFLY-459 > URL: https://issues.jboss.org/browse/WFLY-459 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Labels: downstream_dependency > Fix For: 10.1.0.Final > > > Originally this jira was to stop exporting the javassist module to JPA deployments but it turns out that is fine to do. In addition, native Hibernate applications that depend on Hibernate, should also get the javassist dependency. > # native Hibernate applications will get the javassist dependency via the application dependency on org.hibernate. > # container managed JPA applications will get the javassist dependency via org.jboss.as.jpa.processor.JPADependencyProcessor (JPA deployer). > # container managed JPA applications that embed their own copy of Hibernate jars will also get the javassist dependency via org.jboss.as.jpa.processor.JPADependencyProcessor (JPA deployer). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4186) Improve Infinispan module compatibility with older releases

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4186?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4186: ------------------------------- Fix Version/s: 10.1.0.Final (was: 10.1.0.CR1) > Improve Infinispan module compatibility with older releases > ----------------------------------------------------------- > > Key: WFLY-4186 > URL: https://issues.jboss.org/browse/WFLY-4186 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 9.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 10.1.0.Final > > > Infinispan 7 moved a bunch of classes from the org.infinispan:infinispan-core maven module into the org.infinispan:infinispan-commons module (which, itself, was introduced in Infinispan 6), which can cause user deployments that previously depended on org.infinispan to fail with mysterious NoClassDefFoundErrors if the org.infinispan.commons module was not also previously declared as a deployment dependency. > I suggest we either: > 1. Export org.infinispan.commons from the org.infinispan module > 2. Rename org.infinispan to org.infinispan.core, and create a new org.infinispan that exports both org.infinispan.core and org.infinispan.commons. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3582) Redesign mod_cluster xml subsystem parsers

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3582?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3582: ------------------------------- Fix Version/s: 10.1.0.Final (was: 10.1.0.CR1) > Redesign mod_cluster xml subsystem parsers > ------------------------------------------ > > Key: WFLY-3582 > URL: https://issues.jboss.org/browse/WFLY-3582 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 10.1.0.Final > > > As per https://github.com/wildfly/wildfly/pull/6449 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2016