November 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5626) EAP is unable to destroy the protocol stack with full-ha profile

by Richard Janík (JIRA)

[ https://issues.jboss.org/browse/WFLY-5626?page=com.atlassian.jira.plugin.... ] Richard Janík commented on WFLY-5626: ------------------------------------- The exception is also reproducible with any profile that has a protocol stack to destroy - standalone-ec2-full-ha.xml or standalone-ha.xml with a clustered deployment. Dennis Reed might know more according to his comments on https://bugzilla.redhat.com/show_bug.cgi?id=1268186 which might be relevant (EAP6 with fixes backported from Wildfly). I don't see the exception with Wildfy 10.0.0.CR5-SNAPSHOT though (built from master). > EAP is unable to destroy the protocol stack with full-ha profile > ---------------------------------------------------------------- > > Key: WFLY-5626 > URL: https://issues.jboss.org/browse/WFLY-5626 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR4 > Reporter: Marek Kopecký > Assignee: Paul Ferraro > > *Description of problem:* > EAP is unable to destroy the protocol stack with full-ha profile. > *How reproducible:* > Always > *Steps to Reproduce:* > # ./bin/standalone.sh -c standalone-full-ha.xml > # Stop EAP (Ctrl+C) > *Actual results:* > {noformat} > 14:13:21,292 ERROR [org.jgroups.JChannel] (MSC service thread 1-5) JGRP000020: failed destroying the protocol stack: java.lang.IllegalStateException > at org.jboss.as.network.SocketBindingManagerImpl$UnnamedRegistryImpl.unregisterBinding(SocketBindingManagerImpl.java:501) > at org.jboss.as.network.ManagedDatagramSocketBinding.close(ManagedDatagramSocketBinding.java:73) > at org.jboss.as.clustering.jgroups.ManagedSocketFactory.close(ManagedSocketFactory.java:148) > at org.jgroups.protocols.UDP.closeUnicastSocket(UDP.java:577) > at org.jgroups.protocols.UDP.destroySockets(UDP.java:429) > at org.jgroups.protocols.UDP.destroy(UDP.java:294) > at org.jgroups.stack.ProtocolStack.destroy(ProtocolStack.java:887) > at org.jgroups.JChannel.stopStack(JChannel.java:1005) > at org.jgroups.JChannel._close(JChannel.java:990) > at org.jgroups.JChannel.close(JChannel.java:385) > at org.wildfly.clustering.jgroups.spi.service.ChannelBuilder.stop(ChannelBuilder.java:91) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017) > 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) > {noformat} > *Expected results:* > No errors on output -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5590) Shared object store recovery problem

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/WFLY-5590?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on WFLY-5590: --------------------------------------- I found two issues. Firstly, TestXAResourceRecoveryHelper on server 2 overrides record made by server 1. Changing TEST_XA_RESOURCE_FILE to be unique on each server/resource solves this bit. Secondly, currentXid in TestXAResourceCommon is null after the recovery. Therefore, JNDI names are identical in any instance of TestXAResourceRecovered. Server 1 commits its test resource and assumes another server's resource to be committed too because of [1]. It then removes transaction records for both servers. After that, test resource on server 2 is rolled back by the orphan filter. [1] https://issues.jboss.org/browse/JBTM-860 > Shared object store recovery problem > ------------------------------------ > > Key: WFLY-5590 > URL: https://issues.jboss.org/browse/WFLY-5590 > Project: WildFly > Issue Type: Bug > Components: Transactions > Affects Versions: 10.0.0.CR3 > Reporter: Hayk Hovsepyan > Assignee: Gytis Trikleris > Priority: Critical > Attachments: Server1.log, Server2.log > > > There is a problem with recovery of crashed transactions on two servers when they share the same object store. > The server which starts the recovery second, has problems with processing the logs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5590) Shared object store recovery problem

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/WFLY-5590?page=com.atlassian.jira.plugin.... ] Gytis Trikleris reassigned WFLY-5590: ------------------------------------- Assignee: Hayk Hovsepyan (was: Gytis Trikleris) > Shared object store recovery problem > ------------------------------------ > > Key: WFLY-5590 > URL: https://issues.jboss.org/browse/WFLY-5590 > Project: WildFly > Issue Type: Bug > Components: Transactions > Affects Versions: 10.0.0.CR3 > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Critical > Attachments: Server1.log, Server2.log > > > There is a problem with recovery of crashed transactions on two servers when they share the same object store. > The server which starts the recovery second, has problems with processing the logs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5626) EAP is unable to destroy the protocol stack with full-ha profile

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/WFLY-5626?page=com.atlassian.jira.plugin.... ] Marek Kopecký moved JBEAP-1753 to WFLY-5626: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-5626 (was: JBEAP-1753) Workflow: GIT Pull Request workflow (was: CDW v1) Component/s: Clustering (was: Clustering) Target Release: (was: 7.0.0.GA) Affects Version/s: 10.0.0.CR4 (was: 7.0.0.DR13 (Alpha)) > EAP is unable to destroy the protocol stack with full-ha profile > ---------------------------------------------------------------- > > Key: WFLY-5626 > URL: https://issues.jboss.org/browse/WFLY-5626 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR4 > Reporter: Marek Kopecký > Assignee: Paul Ferraro > > *Description of problem:* > EAP is unable to destroy the protocol stack with full-ha profile. > *How reproducible:* > Always > *Steps to Reproduce:* > # ./bin/standalone.sh -c standalone-full-ha.xml > # Stop EAP (Ctrl+C) > *Actual results:* > {noformat} > 14:13:21,292 ERROR [org.jgroups.JChannel] (MSC service thread 1-5) JGRP000020: failed destroying the protocol stack: java.lang.IllegalStateException > at org.jboss.as.network.SocketBindingManagerImpl$UnnamedRegistryImpl.unregisterBinding(SocketBindingManagerImpl.java:501) > at org.jboss.as.network.ManagedDatagramSocketBinding.close(ManagedDatagramSocketBinding.java:73) > at org.jboss.as.clustering.jgroups.ManagedSocketFactory.close(ManagedSocketFactory.java:148) > at org.jgroups.protocols.UDP.closeUnicastSocket(UDP.java:577) > at org.jgroups.protocols.UDP.destroySockets(UDP.java:429) > at org.jgroups.protocols.UDP.destroy(UDP.java:294) > at org.jgroups.stack.ProtocolStack.destroy(ProtocolStack.java:887) > at org.jgroups.JChannel.stopStack(JChannel.java:1005) > at org.jgroups.JChannel._close(JChannel.java:990) > at org.jgroups.JChannel.close(JChannel.java:385) > at org.wildfly.clustering.jgroups.spi.service.ChannelBuilder.stop(ChannelBuilder.java:91) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017) > 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) > {noformat} > *Expected results:* > No errors on output -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5625) <datasource-class> in <driver> is ignored

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/WFLY-5625?page=com.atlassian.jira.plugin.... ] Jesper Pedersen reassigned WFLY-5625: ------------------------------------- Assignee: Stefano Maestri (was: Jesper Pedersen) > <datasource-class> in <driver> is ignored > ----------------------------------------- > > Key: WFLY-5625 > URL: https://issues.jboss.org/browse/WFLY-5625 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Martin Simka > Assignee: Stefano Maestri > Priority: Critical > > {code:xml} > <driver name="oracle-ucp" module="com.oracle.ucp"> > <xa-datasource-class>[class]</xa-datasource-class> > <datasource-class>[class]</datasource-class> > </driver> > {code} > datasource-class setting is ignored and Driver class is used instead, DataSource class should have priority over Driver if defined > <datasource-class> in <datasource> works -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5625) <datasource-class> in <driver> is ignored

by Martin Simka (JIRA)

Martin Simka created WFLY-5625: ---------------------------------- Summary: <datasource-class> in <driver> is ignored Key: WFLY-5625 URL: https://issues.jboss.org/browse/WFLY-5625 Project: WildFly Issue Type: Bug Components: JCA Reporter: Martin Simka Assignee: Jesper Pedersen Priority: Critical {code:xml} <driver name="oracle-ucp" module="com.oracle.ucp"> <xa-datasource-class>[class]</xa-datasource-class> <datasource-class>[class]</datasource-class> </driver> {code} datasource-class setting is ignored and Driver class is used instead, DataSource class should have priority over Driver if defined <datasource-class> in <datasource> works -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5340) Unable to specify module when specifying custom JACC policy class.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5340?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-5340: ----------------------------------------------- Ondrej Lukas <olukas(a)redhat.com> changed the Status of [bug 1263336|https://bugzilla.redhat.com/show_bug.cgi?id=1263336] from ON_QA to VERIFIED > Unable to specify module when specifying custom JACC policy class. > ------------------------------------------------------------------ > > Key: WFLY-5340 > URL: https://issues.jboss.org/browse/WFLY-5340 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 10.0.0.Beta2 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 10.0.0.CR1 > > > It is currently possible to specify the 'javax.security.jacc.policy.provider' system property, however it is not possible to specify a module. > From the JACC specification: - > _For each JRE of a J2EE 1.4 or later version Java EE application server, if the > system property > “javax.security.jacc.policy.provider > ” is defined, > the application server must construct an > instance of the class identified by the > system property, confirm that the > resulting object is an instance of > java.security.Policy, > and set, by calling the > java.security.Policy.setPolicy > method, the resulting object as the > corresponding Policy object u > sed by the JRE. _ > The specification only specifies that the system property identifies the class, it does not specify how. > In it's simplest form we should assume this is just a class name, in a more complex form we should allow the module to be specified. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1297) Verify if a SQLException is fatal in all methods

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1297?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1297: ------------------------------------------------ Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1271806|https://bugzilla.redhat.com/show_bug.cgi?id=1271806] from ON_QA to VERIFIED > Verify if a SQLException is fatal in all methods > ------------------------------------------------ > > Key: JBJCA-1297 > URL: https://issues.jboss.org/browse/JBJCA-1297 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: WildFly/IronJacamar 1.3.1.Final, 1.2.6.Final > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: WildFly/IronJacamar 1.3.2.Final, 1.2.7.Final > > > WrappedConnection: > * setTransactionIsolation > * commit > * rollback > * setClientInfo -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5449) Custom socket factory for JGroups subsystem not set correctly

by Enrique González Martínez (JIRA)

[ https://issues.jboss.org/browse/WFLY-5449?page=com.atlassian.jira.plugin.... ] Enrique González Martínez reopened WFLY-5449: --------------------------------------------- see comments in BZ. > Custom socket factory for JGroups subsystem not set correctly > ------------------------------------------------------------- > > Key: WFLY-5449 > URL: https://issues.jboss.org/browse/WFLY-5449 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR2 > Reporter: Dennis Reed > Assignee: Paul Ferraro > Priority: Blocker > Fix For: 10.0.0.CR4 > > > Wildfly's JChannelFactory tries to set a custom socket factory on the JGroups transport. > This is not the correct API to use, and it gets overwritten when the JGroups channel starts. > A custom socket factory should be set on the JChannel. > The only time the custom socket factory is currently used is if there's a race condition where two channels are started at the same time, and the custom factory is set just before the other channel uses it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-360) External credential gathering for possible Credential Store SPI implementors

by Peter Skopek (JIRA)

Peter Skopek created ELY-360: -------------------------------- Summary: External credential gathering for possible Credential Store SPI implementors Key: ELY-360 URL: https://issues.jboss.org/browse/ELY-360 Project: WildFly Elytron Issue Type: Feature Request Components: API / SPI Reporter: Peter Skopek Assignee: Peter Skopek Create callbacks, callback handlers and utilities to gather various forms of external credentials to open Credential Store. All forms supported by PicketBox has to be supported. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 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 November 2015