December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5033) Upgrade Infinispan to 8.0

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5033?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5033. ---------------------------- > Upgrade Infinispan to 8.0 > ------------------------- > > Key: WFLY-5033 > URL: https://issues.jboss.org/browse/WFLY-5033 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 10.0.0.Alpha6 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 10.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4901) Fix or @Ignore org.jboss.as.test.integration.ws.wsse.signencrypt.EJBSignEncryptTestCase.encryptedAndSignedRequest

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4901?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4901. ---------------------------- > Fix or @Ignore org.jboss.as.test.integration.ws.wsse.signencrypt.EJBSignEncryptTestCase.encryptedAndSignedRequest > ----------------------------------------------------------------------------------------------------------------- > > Key: WFLY-4901 > URL: https://issues.jboss.org/browse/WFLY-4901 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Rostislav Svoboda > Assignee: Alessio Soldano > Fix For: 10.0.0.Beta2 > > > Brian Stansberry @here who is going to fix or @Ignore org.jboss.as.test.integration.ws.wsse.signencrypt.EJBSignEncryptTestCase.encryptedAndSignedRequest ? > Stuart Douglas I am pretty sure it is a web services issue > Stuart Douglas these failures started happening after a WS upgrade a while back > David M. Lloyd @RostislavSvoboda added it -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4863) Journal file size configuration attribute changed

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4863?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4863. ---------------------------- > Journal file size configuration attribute changed > ------------------------------------------------- > > Key: WFLY-4863 > URL: https://issues.jboss.org/browse/WFLY-4863 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 10.0.0.Alpha5 > > > Attribute journal file-size is set to 102400 bytes in messaging subsystem (in Wildfly 9 with ActiveMQ). This attribute was not set in EAP 6.x and its default value was 10Mb. Current value 102400 bytes causes warnings if message of specific size is sent to server as it is the same value of the connection-factory's min-large-message-size -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4653) Weld thread pool should be wildfly global

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4653?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4653. ---------------------------- > Weld thread pool should be wildfly global > ----------------------------------------- > > Key: WFLY-4653 > URL: https://issues.jboss.org/browse/WFLY-4653 > Project: WildFly > Issue Type: Enhancement > Components: CDI / Weld > Affects Versions: 9.0.0.CR1 > Reporter: Sebastian Maurer > Assignee: Jozef Hartinger > Fix For: 10.0.0.Alpha3 > > > Weld keeps a thread pool for each deployment. > Per default the pool is filled with "numProcessors" threads (see http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html) > When having many deployments, a single thread pool for the wildfly instance could improve the overall performance. > This thread pool should be configurable in the weld subsystem of the wildfly configuration (e.g. standalone.xml). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5064) Upgrade HAL to 2.8.5

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5064?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5064. ---------------------------- > Upgrade HAL to 2.8.5 > -------------------- > > Key: WFLY-5064 > URL: https://issues.jboss.org/browse/WFLY-5064 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Fix For: 10.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5161) Can't set attributes of element transport-config in CLI

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5161?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5161. ---------------------------- > Can't set attributes of element transport-config in CLI > ------------------------------------------------------- > > Key: WFLY-5161 > URL: https://issues.jboss.org/browse/WFLY-5161 > Project: WildFly > Issue Type: Bug > Components: IIOP > Affects Versions: 10.0.0.Beta1 > Reporter: Ondra Chaloupka > Assignee: Tomasz Adamski > Fix For: 10.0.0.CR1 > > > It's not possible to set attributes of element {{transport-config}} in CLI. > When I run {{:read-resource()}} I get > {code} > /subsystem=iiop-openjdk:read-resource() > { > "outcome" => "success", > "result" => { > "add-component-via-interceptor" => true, > "auth-method" => "username_password", > "caller-propagation" => "none", > "client-requires" => "None", > "client-supports" => "ServerAuth", > "confidentiality" => "none", > "detect-misordering" => "none", > "detect-replay" => "none", > "export-corbaloc" => true, > "giop-version" => "1.2", > "high-water-mark" => undefined, > "integrity" => "required", > "number-to-reclaim" => undefined, > "persistent-server-id" => "1", > "properties" => undefined, > "realm" => undefined, > "required" => false, > "root-context" => "JBoss/Naming/root", > "security" => "identity", > "security-domain" => undefined, > "server-requires" => "None", > "server-supports" => "MutualAuth", > "socket-binding" => "iiop", > "ssl-socket-binding" => "iiop-ssl", > "support-ssl" => false, > "transactions" => "spec", > "trust-in-client" => "none", > "trust-in-target" => "none" > } > } > {code} > but XML can contain two emelents > {code} > <client-transport integrity="supported" confidentiality="supported" trust-in-target="supported" trust-in-client="supported" detect-replay="supported" detect-misordering="supported" /> > <transport-config integrity="supported" confidentiality="supported" trust-in-target="supported" trust-in-client="supported" detect-replay="supported" detect-misordering="supported" /> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4969) Update JSF based on Mojarra 2.2.12

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4969?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4969. ---------------------------- > Update JSF based on Mojarra 2.2.12 > ---------------------------------- > > Key: WFLY-4969 > URL: https://issues.jboss.org/browse/WFLY-4969 > Project: WildFly > Issue Type: Component Upgrade > Components: JSF > Reporter: Farah Juma > Assignee: Farah Juma > Fix For: 9.0.2.Final, 10.0.0.Beta1 > > > Update JSF since Mojarra 2.2.12 was just released. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5215) [Migration operation] [Web to Undertow] Scheme attribute of ajp connector is not migrated

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5215?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5215. ---------------------------- > [Migration operation] [Web to Undertow] Scheme attribute of ajp connector is not migrated > ----------------------------------------------------------------------------------------- > > Key: WFLY-5215 > URL: https://issues.jboss.org/browse/WFLY-5215 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Beta2 > Reporter: Radim Hatlapatka > Assignee: Stuart Douglas > Fix For: 10.0.0.CR1 > > > Scheme attribute of AJP connector is not migrated. > Web AJP configuration > {noformat} > <connector name="ajp" protocol="AJP/1.3" scheme="http" socket-binding="ajp"/> > {noformat} > should be migrated to > {noformat} > <ajp-listener name="ajp" socket-binding="ajp" scheme="http"/> > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4854) Exclude org.jboss.logmanager:jboss-logmanager from wildfly-client-all (jboss-client.jar)

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4854?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4854. ---------------------------- > Exclude org.jboss.logmanager:jboss-logmanager from wildfly-client-all (jboss-client.jar) > ---------------------------------------------------------------------------------------- > > Key: WFLY-4854 > URL: https://issues.jboss.org/browse/WFLY-4854 > Project: WildFly > Issue Type: Bug > Components: Application Client > Reporter: Martin Simka > Assignee: Jeff Mesnil > Fix For: 10.0.0.Alpha5 > > > Exclude org.jboss.logmanager:jboss-logmanager from wildfly-client-all (jboss-client.jar) > its presence causes TCK failures with error: > {noformat} > IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager") > {noformat} > as LogManager is loaded twice, from jboss-client.jar and from module. It was brought in together with ActiveMQ Artemis messaging. > {noformat} > [INFO] --- maven-dependency-plugin:2.9:tree (default-cli) @ wildfly-client-all --- > [INFO] org.wildfly:wildfly-client-all:jar:10.0.0.Alpha5-SNAPSHOT > [INFO] +- org.wildfly:wildfly-ejb-client-bom:pom:10.0.0.Alpha5-SNAPSHOT:compile > [INFO] | +- org.jboss:jboss-ejb-client:jar:2.1.1.Final:compile > [INFO] | +- org.jboss:jboss-remote-naming:jar:2.0.4.Final:compile > [INFO] | +- org.jboss.logging:jboss-logging:jar:3.2.1.Final:compile > [INFO] | +- org.jboss.marshalling:jboss-marshalling:jar:1.4.10.Final:compile > [INFO] | +- org.jboss.marshalling:jboss-marshalling-river:jar:1.4.10.Final:compile > [INFO] | +- org.jboss.remoting:jboss-remoting:jar:4.0.9.Final:compile > [INFO] | +- org.jboss.sasl:jboss-sasl:jar:1.0.5.Final:compile > [INFO] | +- org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec:jar:1.0.0.Final:compile > [INFO] | +- org.jboss.spec.javax.ejb:jboss-ejb-api_3.2_spec:jar:1.0.0.Final:compile > [INFO] | +- org.jboss.xnio:xnio-api:jar:3.3.1.Final:compile > [INFO] | \- org.jboss.xnio:xnio-nio:jar:3.3.1.Final:compile > [INFO] +- org.wildfly:wildfly-jms-client-bom:pom:10.0.0.Alpha5-SNAPSHOT:compile > [INFO] | +- org.apache.activemq:artemis-commons:jar:1.0.0:compile > [INFO] | | +- org.jboss.logmanager:jboss-logmanager:jar:2.0.0.Final:compile > [INFO] | | \- commons-beanutils:commons-beanutils:jar:1.9.2:compile > [INFO] | | \- commons-collections:commons-collections:jar:3.2.1:compile > [INFO] | +- org.apache.activemq:artemis-core-client:jar:1.0.0:compile > [INFO] | | +- org.jgroups:jgroups:jar:3.6.4.Final:compile > [INFO] | | +- org.apache.activemq:artemis-selector:jar:1.0.0:compile > [INFO] | | \- org.apache.activemq:artemis-journal:jar:1.0.0:compile > [INFO] | | \- org.apache.activemq:artemis-native:jar:1.0.0:compile > [INFO] | +- org.apache.activemq:artemis-jms-client:jar:1.0.0:compile > [INFO] | | +- org.apache.geronimo.specs:geronimo-jms_2.0_spec:jar:1.0-alpha-1:compile > [INFO] | | \- javax.inject:javax.inject:jar:1:compile > [INFO] | +- org.hornetq:hornetq-commons:jar:2.4.7.Final:compile > [INFO] | +- org.hornetq:hornetq-core-client:jar:2.4.7.Final:compile > [INFO] | | \- org.hornetq:hornetq-journal:jar:2.4.7.Final:compile > [INFO] | | \- org.hornetq:hornetq-native:jar:2.4.7.Final:compile > [INFO] | +- org.hornetq:hornetq-jms-client:jar:2.4.7.Final:compile > [INFO] | +- io.netty:netty-all:jar:4.0.26.Final:compile > [INFO] | +- org.jboss.spec.javax.jms:jboss-jms-api_2.0_spec:jar:1.0.0.Final:compile > [INFO] | \- org.slf4j:jcl-over-slf4j:jar:1.7.7.jbossorg-1:compile > [INFO] | \- org.slf4j:slf4j-api:jar:1.7.7.jbossorg-1:compile > [INFO] +- org.jboss.remotingjmx:remoting-jmx:jar:2.0.1.Final:compile > [INFO] \- org.wildfly.checkstyle:wildfly-checkstyle-config:jar:1.0.3.Final:compile > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5099) Transaction subsystem startup failed with setting the "use-hornetq-store"

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5099?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5099. ---------------------------- > Transaction subsystem startup failed with setting the "use-hornetq-store" > ------------------------------------------------------------------------- > > Key: WFLY-5099 > URL: https://issues.jboss.org/browse/WFLY-5099 > Project: WildFly > Issue Type: Bug > Components: Transactions > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 10.0.0.Beta2 > > > using <use-hornetq-store enable-async-io="true"/> in standalone.xml and wildfly starts failed with > {code} > 21:45:42,140 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "transactions")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.txn.ArjunaRecoveryManager" => "org.jboss.msc.service.StartException in service jboss.txn.ArjunaRecoveryManager: Failed to start service > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError: ARJUNA012135: Could not create Store type: com.arjuna.ats.internal.arjuna.objectstore.hornetq.HornetqObjectStoreAdaptor > Caused by: java.lang.NoClassDefFoundError: org/apache/activemq/artemis/core/journal/SequentialFileFactory > Caused by: java.lang.ClassNotFoundException: org.apache.activemq.artemis.core.journal.SequentialFileFactory from [Module \"org.jboss.jts:main\" from local module loader @2aae9190 (finder: local module finder @2f333739 (roots: /home/zhfeng/work/zhfeng/jboss-as/build/target/wildfly-10.0.0.Beta2-SNAPSHOT/modules,/home/zhfeng/work/zhfeng/jboss-as/build/target/wildfly-10.0.0.Beta2-SNAPSHOT/modules/system/layers/base))]"}} > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 2017