December 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7807) Update XSD with deprecations from infinispan 4.1 model

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-7807: ------------------------------------ Summary: Update XSD with deprecations from infinispan 4.1 model Key: WFLY-7807 URL: https://issues.jboss.org/browse/WFLY-7807 Project: WildFly Issue Type: Bug Reporter: Radoslav Husar Assignee: Radoslav Husar {quote} Also, in the infinispan subsystem 4.1, attributes queue-flush-interval and queue-size are deprecated and ignored. This should be reflected in the new jboss-as-infinispan_4_1.xsd as well. {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7807) Update XSD with deprecations from infinispan 4.1 model

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-7807?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-7807: --------------------------------- Priority: Trivial (was: Major) > Update XSD with deprecations from infinispan 4.1 model > ------------------------------------------------------ > > Key: WFLY-7807 > URL: https://issues.jboss.org/browse/WFLY-7807 > Project: WildFly > Issue Type: Bug > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Trivial > > {quote} > Also, in the infinispan subsystem 4.1, attributes queue-flush-interval and queue-size are deprecated and ignored. This should be reflected in the new jboss-as-infinispan_4_1.xsd as well. > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7544) @Startup @Singleton fails to invoke EJB via Remote interface in PostConstruct

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-7544?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-7544: ----------------------------------------------- Miroslav Sochurek <msochure(a)redhat.com> changed the Status of [bug 1389428|https://bugzilla.redhat.com/show_bug.cgi?id=1389428] from POST to MODIFIED > @Startup @Singleton fails to invoke EJB via Remote interface in PostConstruct > ----------------------------------------------------------------------------- > > Key: WFLY-7544 > URL: https://issues.jboss.org/browse/WFLY-7544 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.1.0.Final > Reporter: Fedor Gavrilov > Assignee: Fedor Gavrilov > Labels: downstream_dependency > Fix For: 11.0.0.Alpha1 > > > While cross-vm calls to beans through remote interfaces while their @PostConstruct is not done yet should be disallowed, in-vm calls should be able to proceed normally. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7529) Singleton subsystem remove operation must require reload

by Michal Vinkler (JIRA)

[ https://issues.jboss.org/browse/WFLY-7529?page=com.atlassian.jira.plugin.... ] Michal Vinkler reopened WFLY-7529: ---------------------------------- Reopening due to the fact that reload is not required on remove. > Singleton subsystem remove operation must require reload > -------------------------------------------------------- > > Key: WFLY-7529 > URL: https://issues.jboss.org/browse/WFLY-7529 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.Alpha1 > > > Since the add operation registers deployment unit processors, the remove operation must require a server reload. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7528) Infinispan subsystem remove operation must require reload

by Michal Vinkler (JIRA)

[ https://issues.jboss.org/browse/WFLY-7528?page=com.atlassian.jira.plugin.... ] Michal Vinkler reopened WFLY-7528: ---------------------------------- Reopening due to the fact that reload is not required on remove. > Infinispan subsystem remove operation must require reload > --------------------------------------------------------- > > Key: WFLY-7528 > URL: https://issues.jboss.org/browse/WFLY-7528 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.Alpha1 > > > Since the add operation registers deployment unit processors, the remove operation must require a server reload. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7806) Undertow mod_cluster: advertise-socket-binding should be auxiliary

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-7806?page=com.atlassian.jira.plugin.... ] Radoslav Husar moved JBEAP-7910 to WFLY-7806: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7806 (was: JBEAP-7910) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: mod_cluster Web (Undertow) (was: mod_cluster) (was: Undertow) Target Release: (was: 7.1.0.GA) Affects Version/s: (was: 7.1.0.DR9) > Undertow mod_cluster: advertise-socket-binding should be auxiliary > ------------------------------------------------------------------ > > Key: WFLY-7806 > URL: https://issues.jboss.org/browse/WFLY-7806 > Project: WildFly > Issue Type: Bug > Components: mod_cluster, Web (Undertow) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > it is not possible to disable advertising for undertow mod_cluster configuration. > {noformat} > [standalone@localhost:9990 /] /subsystem=undertow/configuration=filter/mod-cluster=modcluster:add(management-socket-binding=http) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0155: advertise-socket-binding may not be null", > "rolled-back" => true > } > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7806) Undertow mod_cluster: advertise-socket-binding should be auxiliary

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-7806?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-7806: --------------------------------- Affects Version/s: 10.0.0.Final > Undertow mod_cluster: advertise-socket-binding should be auxiliary > ------------------------------------------------------------------ > > Key: WFLY-7806 > URL: https://issues.jboss.org/browse/WFLY-7806 > Project: WildFly > Issue Type: Bug > Components: mod_cluster, Web (Undertow) > Affects Versions: 10.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > it is not possible to disable advertising for undertow mod_cluster configuration. > {noformat} > [standalone@localhost:9990 /] /subsystem=undertow/configuration=filter/mod-cluster=modcluster:add(management-socket-binding=http) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0155: advertise-socket-binding may not be null", > "rolled-back" => true > } > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-836) CredentialStore resource name and CS alias in memory are case sensitive but CredentialStore aliases are persisted in lowercase.

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/ELY-836?page=com.atlassian.jira.plugin.sy... ] Hynek Švábek moved WFLY-7742 to ELY-836: ---------------------------------------- Project: WildFly Elytron (was: WildFly) Key: ELY-836 (was: WFLY-7742) Component/s: Credential Store (was: Security) > CredentialStore resource name and CS alias in memory are case sensitive but CredentialStore aliases are persisted in lowercase. > ------------------------------------------------------------------------------------------------------------------------------- > > Key: ELY-836 > URL: https://issues.jboss.org/browse/ELY-836 > Project: WildFly Elytron > Issue Type: Bug > Components: Credential Store > Reporter: Hynek Švábek > Assignee: Peter Skopek > > CredentialStore resource name is case sensitive but CredentialStore alias is convert to lowercase. > *How to reproduce* > {code} > /subsystem=elytron/credential-store=csfile001:add(uri="cr-store://test/csfile001.jceks?store.password=pass123;create.storage=true") > {code} > {code} > /subsystem=elytron/credential-store=csfile001/alias=csname001:add(secret-value=secValue123456) > {code} > {code} > /subsystem=elytron/credential-store=csfile001/alias=csNAME001:add(secret-value=secValue987654) > {code} > In csfile001.jceks you can see only "csname001" entry. > *There is biggest problem that in memory are right case sensitive aliases and you can load them. But in backed CS file is only last one in lowercase.* > {code} > /subsystem=elytron/credential-store=csfile001/alias=csFF:add(secret-value=Elytron) > {code} > {code} > /subsystem=elytron/credential-store=csfile001/alias=csff:add(secret-value=ElytronWrong) > {code} > And now you can use both (csFF and csff) as CredStoreRef alias > e.g. > {code} > /subsystem=elytron/key-store=fireflyKS001:add(path=firefly.keystore,relative-to=jboss.server.data.dir,type=JKS,credential-reference= {store=csfile001,alias=csFF}) > {code} > Another big problem for me is that you have a lot of CS Alias RESOURCES which reference to ONE entry and update value in CS. > *NOTE* > https://docs.oracle.com/javase/8/docs/api/java/security/KeyStore.html > {code} > Whether aliases are case sensitive is implementation dependent. In order to avoid problems, it is recommended not to use aliases in a KeyStore that only differ in case. > {code} > *Suggestions for solution* > * We must unite case (in)sensitive between CS keystore file and CS in memory > * implement case sensitive (Our implementation looks ok, IMO there is another problem with it...) > * something else -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1998) Custom NameService by sun.net.spi.nameservice.provider.n doesn't work on WildFly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1998?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1998: ------------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1395543|https://bugzilla.redhat.com/show_bug.cgi?id=1395543] from MODIFIED to ON_QA > Custom NameService by sun.net.spi.nameservice.provider.n doesn't work on WildFly > -------------------------------------------------------------------------------- > > Key: WFCORE-1998 > URL: https://issues.jboss.org/browse/WFCORE-1998 > Project: WildFly Core > Issue Type: Bug > Components: Modules > Affects Versions: 2.2.0.Final > Reporter: Osamu Nagano > Assignee: Osamu Nagano > Labels: downstream_dependency > Fix For: 3.0.0.Alpha13 > > Attachments: nameserviceProviderTest.zip > > > System property {{sun.net.spi.nameservice.provider.<n>}} allows a user to customize a NameService. It works on a standalone java, which is using JBoss Modules, if {{services="import"}} is added on sun.jdk module dependency and the sun.jdk module has the following additional dependencies. > {code} > <path name="sun/net/spi/nameservice"/> > <path name="sun/net/spi/nameservice/dns"/> > {code} > Though it doesn't work as a web application which has the same module path and the same dependency in jboss-deployment-structure.xml. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4957) After failback backup prints warnings to log

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4957?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4957: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1159290|https://bugzilla.redhat.com/show_bug.cgi?id=1159290] from MODIFIED to ON_QA > After failback backup prints warnings to log > -------------------------------------------- > > Key: WFLY-4957 > URL: https://issues.jboss.org/browse/WFLY-4957 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Alpha5 > Environment: Fedora 22 > openjdk 8 > Reporter: Erich Duda > Assignee: Jeff Mesnil > Priority: Critical > Fix For: 10.0.0.CR5 > > Attachments: master.xml, slave.xml > > > 15:34:59,123 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 4) WFLYMSGAMQ0004: Failed to destroy queue: ExpiryQueue: java.lang.IllegalStateException: Cannot access JMS Server, core server is not yet active > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.checkInitialised(JMSServerManagerImpl.java:1640) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.access$1100(JMSServerManagerImpl.java:101) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl$3.runException(JMSServerManagerImpl.java:752) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.runAfterActive(JMSServerManagerImpl.java:1847) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.removeQueueFromBindingRegistry(JMSServerManagerImpl.java:741) > at org.wildfly.extension.messaging.activemq.jms.JMSQueueService$2.run(JMSQueueService.java:101) > 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) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > 15:34:59,123 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 68) WFLYMSGAMQ0004: Failed to destroy queue: AsyncQueue: java.lang.IllegalStateException: Cannot access JMS Server, core server is not yet active > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.checkInitialised(JMSServerManagerImpl.java:1640) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.access$1100(JMSServerManagerImpl.java:101) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl$3.runException(JMSServerManagerImpl.java:752) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.runAfterActive(JMSServerManagerImpl.java:1847) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.removeQueueFromBindingRegistry(JMSServerManagerImpl.java:741) > at org.wildfly.extension.messaging.activemq.jms.JMSQueueService$2.run(JMSQueueService.java:101) > 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) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > 15:34:59,123 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 9) WFLYMSGAMQ0004: Failed to destroy queue: DLQ: java.lang.IllegalStateException: Cannot access JMS Server, core server is not yet active > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.checkInitialised(JMSServerManagerImpl.java:1640) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.access$1100(JMSServerManagerImpl.java:101) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl$3.runException(JMSServerManagerImpl.java:752) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.runAfterActive(JMSServerManagerImpl.java:1847) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.removeQueueFromBindingRegistry(JMSServerManagerImpl.java:741) > at org.wildfly.extension.messaging.activemq.jms.JMSQueueService$2.run(JMSQueueService.java:101) > 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) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 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 December 2016