November 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1899) Discovery returns after 16 responses even if there are no coord responses

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-1899?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JGRP-1899: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1168329 > Discovery returns after 16 responses even if there are no coord responses > ------------------------------------------------------------------------- > > Key: JGRP-1899 > URL: https://issues.jboss.org/browse/JGRP-1899 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.5.2, 3.6.1 > > > Discovery sets {{Responses.num_expected_rsps}} to 16 if no member list is defined. This makes discovery return after 16 responses even if no response from a coordinator has been received. > This is a problem if we have a cluster of size > 16 and the coordinator doesn't respond imediately, e.g. because it is busy processing other requests. > h5. Solution > * Set {{num_expected_rsps}} to 0 (= wait until at least 1 coord rsp has been received -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4128) Move JAX-RS 2.0 API into JBoss Specs

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4128?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-4128: ------------------------------ Affects Version/s: 8.2.0.Final (was: 9.0.0.Beta1) > Move JAX-RS 2.0 API into JBoss Specs > ------------------------------------ > > Key: WFLY-4128 > URL: https://issues.jboss.org/browse/WFLY-4128 > Project: WildFly > Issue Type: Task > Components: REST > Affects Versions: 8.2.0.Final > Reporter: Fernando Nasser > Assignee: Tomaz Cerar > Priority: Minor > > Currently the JAX-RS 2.0 API comes from the RESTEasy project but we should have a JBoss Spec JAX-RS 2.0 API and use that one instead. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4128) Move JAX-RS 2.0 API into JBoss Specs

by Fernando Nasser (JIRA)

Fernando Nasser created WFLY-4128: ------------------------------------- Summary: Move JAX-RS 2.0 API into JBoss Specs Key: WFLY-4128 URL: https://issues.jboss.org/browse/WFLY-4128 Project: WildFly Issue Type: Task Components: REST Affects Versions: 9.0.0.Beta1 Reporter: Fernando Nasser Assignee: Tomaz Cerar Priority: Minor Currently the JAX-RS 2.0 API comes from the RESTEasy project but we should have a JBoss Spec JAX-RS 2.0 API and use that one instead. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4126) java.lang.ExceptionInInitializerError when invoking BIRT service

by Chezy Palani (JIRA)

[ https://issues.jboss.org/browse/WFLY-4126?page=com.atlassian.jira.plugin.... ] Chezy Palani commented on WFLY-4126: ------------------------------------ This is the other part of stack from the log file: Caused by: java.lang.ExceptionInInitializerError at org.apache.jasper.el.ELContextImpl.<init>(ELContextImpl.java:72) [jastow-1.0.0.Final.jar:1.0.0.Final] at org.apache.jasper.compiler.Validator$ValidateVisitor.checkXmlAttributes(Validator.java:1188) [jastow-1.0.0.Final.jar:1.0.0.Final] at org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:844) [jastow-1.0.0.Final.jar:1.0.0.Final] at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1530) [jastow-1.0.0.Final.jar:1.0.0.Final] at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2377) [jastow-1.0.0.Final.jar:1.0.0.Final] at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2427) [jastow-1.0.0.Final.jar:1.0.0.Final] at org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2433) [jastow-1.0.0.Final.jar:1.0.0.Final] at org.apache.jasper.compiler.Node$Root.accept(Node.java:495) [jastow-1.0.0.Final.jar:1.0.0.Final] at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2377) [jastow-1.0.0.Final.jar:1.0.0.Final] at org.apache.jasper.compiler.Validator.validateExDirectives(Validator.java:1768) [jastow-1.0.0.Final.jar:1.0.0.Final] at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:211) [jastow-1.0.0.Final.jar:1.0.0.Final] at org.apache.jasper.compiler.Compiler.compile(Compiler.java:359) [jastow-1.0.0.Final.jar:1.0.0.Final] at org.apache.jasper.compiler.Compiler.compile(Compiler.java:339) [jastow-1.0.0.Final.jar:1.0.0.Final] at org.apache.jasper.compiler.Compiler.compile(Compiler.java:326) [jastow-1.0.0.Final.jar:1.0.0.Final] at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:604) [jastow-1.0.0.Final.jar:1.0.0.Final] at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:309) [jastow-1.0.0.Final.jar:1.0.0.Final] at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326) [jastow-1.0.0.Final.jar:1.0.0.Final] at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:259) [jastow-1.0.0.Final.jar:1.0.0.Final] ... 42 more Caused by: java.lang.NullPointerException at javax.el.CompositeELResolver.add(CompositeELResolver.java:117) [jboss-el-api_3.0_spec-1.0.3.Final.jar:1.0.3.Final] at org.apache.jasper.el.ELResolverImpl.<clinit>(ELResolverImpl.java:51) [jastow-1.0.0.Final.jar:1.0.0.Final] ... 60 more > java.lang.ExceptionInInitializerError when invoking BIRT service > ---------------------------------------------------------------- > > Key: WFLY-4126 > URL: https://issues.jboss.org/browse/WFLY-4126 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.2.0.Final > Environment: Windows 7 and JDK 1.8 > Reporter: Chezy Palani > Assignee: Stuart Douglas > > There was no error during the deployment of the Application. Even hitting landing page works fine. When our service is invoked, we get this exception. > Context Path: > /actuatejavacomponent > Servlet Path: > /iv > Path Info: > null > Query String: > __report=%2fPublic%2fBIRT%20and%20BIRT%20Studio%20Examples%2fCustomer%20Dashboard%2erptdocument&closex=true&__vp=workgroup&showBanner=true&showBreadCrumb=false&locale=en_US > Stack Trace > javax.servlet.ServletException: java.lang.ExceptionInInitializerError > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267) > javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) > io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) > io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:249) > io.undertow.servlet.handlers.ServletInitialHandler.dispatchToServlet(ServletInitialHandler.java:198) > io.undertow.servlet.spec.RequestDispatcherImpl.include(RequestDispatcherImpl.java:279) > com.actuate.iv.presentation.aggregation.IVBaseFragment.service(IVBaseFragment.java:261) > com.actuate.iv.servlet.IVHttpDispatcher.handleRequest(IVHttpDispatcher.java:144) > com.actuate.iv.servlet.IVServlet.doGet(IVServlet.java:261) > javax.servlet.http.HttpServlet.service(HttpServlet.java:687) > org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327) > javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) > io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) > io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) > io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56) > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) > io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:63) > io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) > io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) > io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) > io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:247) > io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:76) > io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:166) > io.undertow.server.Connectors.executeRootHandler(Connectors.java:197) > io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:759) > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4054) Unexpected attribute can be added to elements in Transactions Subsystem

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4054?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4054: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1156032|https://bugzilla.redhat.com/show_bug.cgi?id=1156032] from MODIFIED to ASSIGNED > Unexpected attribute can be added to elements in Transactions Subsystem > ----------------------------------------------------------------------- > > Key: WFLY-4054 > URL: https://issues.jboss.org/browse/WFLY-4054 > Project: WildFly > Issue Type: Bug > Components: Transactions > Reporter: Amos Feng > Assignee: Amos Feng > > If you add unexpected argument to element in standalone.xml then it's expected to get error of "Unexpected attribute '...' encountered" [1] when server is started. > When you add a random argument to some of the elements in transactions then no error is thrown. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-42) Vault

by Peter Skopek (JIRA)

[ https://issues.jboss.org/browse/ELY-42?page=com.atlassian.jira.plugin.sys... ] Peter Skopek reassigned ELY-42: ------------------------------- Assignee: Peter Skopek > Vault > ----- > > Key: ELY-42 > URL: https://issues.jboss.org/browse/ELY-42 > Project: WildFly Elytron > Issue Type: Feature Request > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Peter Skopek > Fix For: 1.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-259) Improve realm readiness handling

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-259?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-259: ------------------------------------------------ Ondrej Lukas <olukas(a)redhat.com> changed the Status of [bug 1161668|https://bugzilla.redhat.com/show_bug.cgi?id=1161668] from ON_QA to VERIFIED > Improve realm readiness handling > -------------------------------- > > Key: WFCORE-259 > URL: https://issues.jboss.org/browse/WFCORE-259 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha14 > > > Currently we display an error message informing users that they need to add a new user if any of the authentication mechanisms within a realm report that they are not ready to handle requests. > The reason for this was so that if properties backed authentication we available along with local authentication then the local authentication would not prevent the prompt from being displayed. > However there could be additional mechanisms suitable for use with HTTP so we need a small modification to stop taking into account the local authentication mechanism but allow requests in if any of the other HTTP compatible mechanisms are ready to handle requests. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3690) Not possible to start XTS transaction on IPv6 with server bound to ::1

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3690?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3690: ----------------------------------------------- Ondrej Chaloupka <ochaloup(a)redhat.com> changed the Status of [bug 1077156|https://bugzilla.redhat.com/show_bug.cgi?id=1077156] from ON_QA to VERIFIED > Not possible to start XTS transaction on IPv6 with server bound to ::1 > ---------------------------------------------------------------------- > > Key: WFLY-3690 > URL: https://issues.jboss.org/browse/WFLY-3690 > Project: WildFly > Issue Type: Bug > Components: Transactions, XTS > Reporter: Stefano Maestri > Assignee: Amos Feng > > Currently we have the following configuration element: <xts-environment url="http://${jboss.bind.address:127.0.0.1}:8080/ws-c11/ActivationService"/> > If bind address is set to ::1, then xts environment URL becomes http://::1:8080/ws-c11/ActivationService. This is incorrect, because IPv6 address with port number in it suppose to have brackets. > we could need to split url in 4 different attribute: > * protocol > * host > * port > * path > but there isn't a easy way to do the transformer by adding these new attributes. So it's just another solution to split the url and check the address if startsWith ::1, then it needs to add the brackets and join them again. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-1721) AUTH and ENCRYPT protocols configured with plain text passwords

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-1721?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JGRP-1721: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1021819|https://bugzilla.redhat.com/show_bug.cgi?id=1021819] from NEW to ASSIGNED > AUTH and ENCRYPT protocols configured with plain text passwords > --------------------------------------------------------------- > > Key: JGRP-1721 > URL: https://issues.jboss.org/browse/JGRP-1721 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4 > Reporter: Martin Gencur > Assignee: Bela Ban > Fix For: 3.5 > > > The following parameters of AUTH protocol are stored as plain text: > * keystore_password > The following parameters of ENCRYPT protocol are stored as plain text: > * store_password > * key_password > Example: > {code} > <ENCRYPT key_store_name="defaultStore.keystore" store_password="changeit" alias="myKey"/> > {code} > Requirements for storing passwords: https://docspace.corp.redhat.com/docs/DOC-131628 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-213) Clean unreferenced items from the content repository

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-213?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-213: ------------------------------------------------ Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1018026|https://bugzilla.redhat.com/show_bug.cgi?id=1018026] from ASSIGNED to VERIFIED > Clean unreferenced items from the content repository > ---------------------------------------------------- > > Key: WFCORE-213 > URL: https://issues.jboss.org/browse/WFCORE-213 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emmanuel Hugonnet > Fix For: 1.0.0.Alpha14 > > > The algorithm for removing unused deployments from the content repository is based on doing this as part of undeploy operation execution. This doesn't cover cases where the content is never explicitly undeployed. For example: > 1) Scanner content that is updated when the server is offline; the old content will not have been "undeployed" during shutdown, and on startup the new content will be installed. > 2) Similar issues with deployments generated from module resources (see "A Mixed Approach on https://community.jboss.org/wiki/ExtendingAS7). When the server shuts down, there is no "subsystem remove" as part of shutdown, so the content added during start will not be removed. > Note that the content repository can include things other than deployments. Currently it also includes management-client-content (specifically rollout plans) and can potentially include anything. This is why it's a "content repository" and not a "deployment repository." The solution for this needs to deal with all cases. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2014