February 2016 - jboss-jira - Jboss List Archives

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

by Ravi Soni (JIRA)

[ https://issues.jboss.org/browse/WFLY-3805?page=com.atlassian.jira.plugin.... ] Ravi Soni commented on WFLY-3805: --------------------------------- Jboss Eap 6.4.4 is still having this issue and I am patching code from your PR to make it working HornetQ over Jgroups. EAP 6X should get this fix as its long term supported. > 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.Final > > > 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)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6083) Removing of non-existent login-module finishes with outcome success

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-6083?page=com.atlassian.jira.plugin.... ] Ondrej Lukas updated WFLY-6083: ------------------------------- Affects Version/s: 10.0.0.Final > Removing of non-existent login-module finishes with outcome success > ------------------------------------------------------------------- > > Key: WFLY-6083 > URL: https://issues.jboss.org/browse/WFLY-6083 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 10.0.0.Final > Reporter: Ondrej Lukas > Assignee: Dmitrii Tikhomirov > Priority: Minor > > In case when non-existent login-module is removed through Management CLI, opertation should finish with failure. However it finishes with outcome success and nothing is changed. It can be confusing since wrong command seems same as correct command. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6101) Removing of non-existent policy-module finishes with outcome success

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-6101?page=com.atlassian.jira.plugin.... ] Ondrej Lukas updated WFLY-6101: ------------------------------- Affects Version/s: 10.0.0.Final > Removing of non-existent policy-module finishes with outcome success > -------------------------------------------------------------------- > > Key: WFLY-6101 > URL: https://issues.jboss.org/browse/WFLY-6101 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 10.0.0.Final > Reporter: Ondrej Lukas > Assignee: Alexey Loubyansky > Priority: Minor > > In case when non-existent policy-module is removed through Management CLI, operation should finish with failure. However it finishes with outcome success and nothing is changed. It can be confusing since wrong command seems same as correct command. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6102) Removing of non-existent mapping-module finishes with outcome success

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-6102?page=com.atlassian.jira.plugin.... ] Ondrej Lukas updated WFLY-6102: ------------------------------- Affects Version/s: 10.0.0.Final > Removing of non-existent mapping-module finishes with outcome success > --------------------------------------------------------------------- > > Key: WFLY-6102 > URL: https://issues.jboss.org/browse/WFLY-6102 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 10.0.0.Final > Reporter: Ondrej Lukas > Assignee: Alexey Loubyansky > Priority: Minor > > In case when non-existent mapping-module is removed through Management CLI, operation should finish with failure. However it finishes with outcome success and nothing is changed. It can be confusing since wrong command seems same as correct command. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6101) Removing of non-existent policy-module finishes with outcome success

by Ondrej Lukas (JIRA)

Ondrej Lukas created WFLY-6101: ---------------------------------- Summary: Removing of non-existent policy-module finishes with outcome success Key: WFLY-6101 URL: https://issues.jboss.org/browse/WFLY-6101 Project: WildFly Issue Type: Bug Components: CLI Reporter: Ondrej Lukas Assignee: Alexey Loubyansky Priority: Minor In case when non-existent policy-module is removed through Management CLI, operation should finish with failure. However it finishes with outcome success and nothing is changed. It can be confusing since wrong command seems same as correct command. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6102) Removing of non-existent mapping-module finishes with outcome success

by Ondrej Lukas (JIRA)

Ondrej Lukas created WFLY-6102: ---------------------------------- Summary: Removing of non-existent mapping-module finishes with outcome success Key: WFLY-6102 URL: https://issues.jboss.org/browse/WFLY-6102 Project: WildFly Issue Type: Bug Components: CLI Reporter: Ondrej Lukas Assignee: Alexey Loubyansky Priority: Minor In case when non-existent mapping-module is removed through Management CLI, operation should finish with failure. However it finishes with outcome success and nothing is changed. It can be confusing since wrong command seems same as correct command. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6100) org.wildfly.bom tag for version 10.0.0.Final

by Leandro Kersting de Freitas (JIRA)

Leandro Kersting de Freitas created WFLY-6100: ------------------------------------------------- Summary: org.wildfly.bom tag for version 10.0.0.Final Key: WFLY-6100 URL: https://issues.jboss.org/browse/WFLY-6100 Project: WildFly Issue Type: Task Affects Versions: 10.0.0.Final Reporter: Leandro Kersting de Freitas Assignee: Jason Greene Generate maven bom dependencies. {code:xml} <dependency> <groupId>org.wildfly.bom</groupId> <artifactId>wildfly-javaee7</artifactId> <version>10.0.0.Final</version> <type>pom</type> <scope>import</scope> </dependency> <dependency> <groupId>org.wildfly.bom</groupId> <artifactId>wildfly-javaee7-with-tools</artifactId> <version>10.0.0.Final</version> <type>pom</type> <scope>import</scope> </dependency> {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6099) JPA's persistence.xml is deployed before datasources are created through application.xml

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-6099?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-6099: -------------------------------------- is the javax.sql.DataSource class packaged somewhere in your deployment? > JPA's persistence.xml is deployed before datasources are created through application.xml > ---------------------------------------------------------------------------------------- > > Key: WFLY-6099 > URL: https://issues.jboss.org/browse/WFLY-6099 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.Final > Reporter: Renann Prado > Assignee: Jason Greene > Attachments: server_with_mysql_driver.log > > > Please refer to discussion > https://developer.jboss.org/thread/267371 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-509) Correctly deal with deployment service restart

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-509?page=com.atlassian.jira.plugin... ] Stuart Douglas resolved WFCORE-509. ----------------------------------- Resolution: Rejected > Correctly deal with deployment service restart > ---------------------------------------------- > > Key: WFCORE-509 > URL: https://issues.jboss.org/browse/WFCORE-509 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > At the moment a lot of deployment services are not restartable, as they rely on transient state. The DeploymentUnitService has a device that will restart the whole deployment if it detects a restart, we should investigate adding something similar to other deployment services. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5911) Update fasterxml.jackson.* from 2.5.4 to 2.6.4.

by Juergen Zimmermann (JIRA)

[ https://issues.jboss.org/browse/WFLY-5911?page=com.atlassian.jira.plugin.... ] Juergen Zimmermann commented on WFLY-5911: ------------------------------------------ Upgrading to 2.6.4/2.6.5 (and not to 2.7.x) should be preferred: * https://github.com/FasterXML/jackson-databind/issues/1079 * https://github.com/FasterXML/jackson-databind/issues/1087 * https://jira.spring.io/browse/SPR-13853 > Update fasterxml.jackson.* from 2.5.4 to 2.6.4. > ----------------------------------------------- > > Key: WFLY-5911 > URL: https://issues.jboss.org/browse/WFLY-5911 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Affects Versions: 10.0.0.CR5 > Reporter: Frank Langelage > Assignee: Stuart Douglas > Fix For: 10.1.0.Final > > > Update com.fasterxml.jackson to latest version. > Precondition: update of resteasy to latest version. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2016