March 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-169) Review sasl mechanism indexes

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-169: ------------------------------------ Summary: Review sasl mechanism indexes Key: ELY-169 URL: https://issues.jboss.org/browse/ELY-169 Project: WildFly Elytron Issue Type: Task Components: SASL Reporter: Darran Lofthouse Fix For: 1.0.0.Alpha1 External needs to be way up the list if not first as that one can easilt succeed or fail silently based on information external to the auth. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4447) Configuring transport thread pool results in NPE

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4447?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-4447: -------------------------------------- Probably missed when upgrading to Infinispan 7, fixing here: https://github.com/infinispan/infinispan/pull/3321 Honestly I am failing to see the reason why the methods have been even kept since they just return null. > Configuring transport thread pool results in NPE > ------------------------------------------------ > > Key: WFLY-4447 > URL: https://issues.jboss.org/browse/WFLY-4447 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 9.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 9.0.0.Beta1 > > > One line fix to use correct builder method. > {noformat} > /extension=org.jboss.as.threads:add > /subsystem=threads:add > /subsystem=threads/bounded-queue-thread-pool=transport:add(max-threads=20,queue-length=1000) > /subsystem=infinispan/cache-container=web/transport=TRANSPORT:write-attribute(name=executor,value=transport) > deploy /home/rhusar/git/clusterbench/clusterbench-ee7-ear/target/clusterbench-ee7.ear > {noformat} > yields > {noformat} > 12:37:30,142 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.infinispan.web.config: org.jboss.msc.service.StartException in service jboss.infinispan.web.config: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) > 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) > Caused by: java.lang.NullPointerException > at org.jboss.as.clustering.infinispan.subsystem.CacheContainerConfigurationBuilder.getValue(CacheContainerConfigurationBuilder.java:144) > at org.jboss.as.clustering.infinispan.subsystem.CacheContainerConfigurationBuilder.getValue(CacheContainerConfigurationBuilder.java:65) > at org.jboss.msc.service.ValueService.start(ValueService.java:49) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > ... 3 more > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4446) Make sure testsuite runs on systems with 4GB ram

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4446?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-4446: ------------------------------ Summary: Make sure testsuite runs on systems with 4GB ram (was: Make sure testsuite runs on systems with 4GG ram) > Make sure testsuite runs on systems with 4GB ram > ------------------------------------------------ > > Key: WFLY-4446 > URL: https://issues.jboss.org/browse/WFLY-4446 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 9.0.0.Alpha1 > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > > Currently build agents that have swap disabled and only 4GB of ram are not able to complete domain testsuite as kernel kills the process as result of OOM -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4447) Configuring transport thread pool results in NPE

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-4447: ------------------------------------ Summary: Configuring transport thread pool results in NPE Key: WFLY-4447 URL: https://issues.jboss.org/browse/WFLY-4447 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 9.0.0.Alpha1 Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 9.0.0.Beta1 One line fix to use correct builder method. {noformat} /extension=org.jboss.as.threads:add /subsystem=threads:add /subsystem=threads/bounded-queue-thread-pool=transport:add(max-threads=20,queue-length=1000) /subsystem=infinispan/cache-container=web/transport=TRANSPORT:write-attribute(name=executor,value=transport) deploy /home/rhusar/git/clusterbench/clusterbench-ee7-ear/target/clusterbench-ee7.ear {noformat} yields {noformat} 12:37:30,142 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.infinispan.web.config: org.jboss.msc.service.StartException in service jboss.infinispan.web.config: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) 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) Caused by: java.lang.NullPointerException at org.jboss.as.clustering.infinispan.subsystem.CacheContainerConfigurationBuilder.getValue(CacheContainerConfigurationBuilder.java:144) at org.jboss.as.clustering.infinispan.subsystem.CacheContainerConfigurationBuilder.getValue(CacheContainerConfigurationBuilder.java:65) at org.jboss.msc.service.ValueService.start(ValueService.java:49) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) ... 3 more {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4446) Make sure testsuite runs on systems with 4GG ram

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFLY-4446: --------------------------------- Summary: Make sure testsuite runs on systems with 4GG ram Key: WFLY-4446 URL: https://issues.jboss.org/browse/WFLY-4446 Project: WildFly Issue Type: Enhancement Components: Test Suite Affects Versions: 9.0.0.Alpha1 Reporter: Tomaz Cerar Assignee: Tomaz Cerar Currently build agents that have swap disabled and only 4GB of ram are not able to complete domain testsuite as kernel kills the process as result of OOM -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-487) Instability in RespawnHttpTestCase

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-487?page=com.atlassian.jira.plugin... ] Tomaz Cerar commented on WFCORE-487: ------------------------------------ REM3-204 fixes RespawnHttpTestCase properly. the other failure is related to bit different build agent setup. > Instability in RespawnHttpTestCase > ----------------------------------- > > Key: WFCORE-487 > URL: https://issues.jboss.org/browse/WFCORE-487 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Affects Versions: 1.0.0.Alpha14 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Fix For: 1.0.0.Beta1 > > Attachments: respawn-http-threads.txt > > > We have the following error message in the traces: > 2014-12-15 19:19:53,574 ERROR [org.jboss.remoting.remote.connection] (XNIO-1 I/O-1) JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host > http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=32341&buildTyp...! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4444) Ability to set WSDL URL

by John Ament (JIRA)

[ https://issues.jboss.org/browse/WFLY-4444?page=com.atlassian.jira.plugin.... ] John Ament commented on WFLY-4444: ---------------------------------- Ok, let me give that a shot. I'm just using my local machine's fully qualified name, to verify that it shows that instead of localhost. > Ability to set WSDL URL > ----------------------- > > Key: WFLY-4444 > URL: https://issues.jboss.org/browse/WFLY-4444 > Project: WildFly > Issue Type: Feature Request > Components: Web Services > Affects Versions: 8.2.0.Final > Reporter: John Ament > Assignee: Alessio Soldano > > There's no way to correctly set a WSDL URL. The properties are: > {code} > <modify-wsdl-address>true</modify-wsdl-address> > <wsdl-host>${public.app.host:localhost}</wsdl-host> > <wsdl-port>${public.http.port:80}</wsdl-port> > <wsdl-secure-port>${public.https.port:443}</wsdl-secure-port> > {code} > We need a way to set the WSDL URL, regardless of the protocol used. The issue being that our app servers run on HTTP, but the incoming request to the first load balancer is over HTTPS. The result is that the WSDL generated includes http://public-host:80/ instead of https://public-host:443/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-487) Instability in RespawnHttpTestCase

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-487?page=com.atlassian.jira.plugin... ] David Lloyd commented on WFCORE-487: ------------------------------------ It was assumed that REM3-204 was the cause of this, but it probably isn't. > Instability in RespawnHttpTestCase > ----------------------------------- > > Key: WFCORE-487 > URL: https://issues.jboss.org/browse/WFCORE-487 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Affects Versions: 1.0.0.Alpha14 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Fix For: 1.0.0.Beta1 > > Attachments: respawn-http-threads.txt > > > We have the following error message in the traces: > 2014-12-15 19:19:53,574 ERROR [org.jboss.remoting.remote.connection] (XNIO-1 I/O-1) JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host > http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=32341&buildTyp...! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4444) Ability to set WSDL URL

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-4444?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on WFLY-4444: --------------------------------------- mmh... we do have a test that verifies the scenario with disabled address rewrite. Not sure if you can provide me a sample app to reproduce your exact scenario (app + wfly conf, the only missing element being the load balancer). Btw, which exact soap address location have you actually written in the wsdl this time? Perhaps you can get the JBossWS 4.3.2.Final sources, attach a debugger there and step through MetadataBuilder#processAddressRewrite method [1] to see why the address is being rewritten? [1] http://anonsvn.jboss.org/repos/jbossws/stack/cxf/tags/jbossws-cxf-4.3.2.F... > Ability to set WSDL URL > ----------------------- > > Key: WFLY-4444 > URL: https://issues.jboss.org/browse/WFLY-4444 > Project: WildFly > Issue Type: Feature Request > Components: Web Services > Affects Versions: 8.2.0.Final > Reporter: John Ament > Assignee: Alessio Soldano > > There's no way to correctly set a WSDL URL. The properties are: > {code} > <modify-wsdl-address>true</modify-wsdl-address> > <wsdl-host>${public.app.host:localhost}</wsdl-host> > <wsdl-port>${public.http.port:80}</wsdl-port> > <wsdl-secure-port>${public.https.port:443}</wsdl-secure-port> > {code} > We need a way to set the WSDL URL, regardless of the protocol used. The issue being that our app servers run on HTTP, but the incoming request to the first load balancer is over HTTPS. The result is that the WSDL generated includes http://public-host:80/ instead of https://public-host:443/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4445) Remove "path" and "relative-to" attributes from CLI from transactions subsystem

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4445?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-4445: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1039081 > Remove "path" and "relative-to" attributes from CLI from transactions subsystem > ------------------------------------------------------------------------------- > > Key: WFLY-4445 > URL: https://issues.jboss.org/browse/WFLY-4445 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management, Transactions > Reporter: Ondřej Chaloupka > Assignee: Brian Stansberry > Priority: Minor > > As "process-id/file" functionality is not yet added in EAP, the "path" and "relative-to" attributes are useless in transactions subsystem of CLI. > Please remove them. > Also please remove them from "jboss-as-txn***.xsd" file as well. > For detailed discussion please refer to https://bugzilla.redhat.com/show_bug.cgi?id=1039081 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 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 March 2015