November 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1712) Erroneous name attribute on root-logger after add-handler operation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1712?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1712: ----------------------------------------------- James Perkins <jperkins(a)redhat.com> changed the Status of [bug 1017881|https://bugzilla.redhat.com/show_bug.cgi?id=1017881] from ASSIGNED to CLOSED > Erroneous name attribute on root-logger after add-handler operation > -------------------------------------------------------------------- > > Key: WFLY-1712 > URL: https://issues.jboss.org/browse/WFLY-1712 > Project: WildFly > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > Execution of the {{add-handler}} operation adds a name attribute with the handlers name to the root-logger model. > {code} > "root-logger" => {"ROOT" => { > "filter" => undefined, > "filter-spec" => undefined, > "handlers" => [ > "FILE", > "CONSOLE" > ], > "level" => "INFO", > "name" => "CONSOLE" > }} > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3529) UT000010: Session not found

by Rune Steinseth (JIRA)

[ https://issues.jboss.org/browse/WFLY-3529?page=com.atlassian.jira.plugin.... ] Rune Steinseth commented on WFLY-3529: -------------------------------------- I created a new issue for this: https://issues.jboss.org/browse/WELD-1802 > UT000010: Session not found > ---------------------------- > > Key: WFLY-3529 > URL: https://issues.jboss.org/browse/WFLY-3529 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Environment: Wildfly 8.1.0.Final , > Reporter: Youssef BIKHCHICHE > Assignee: Stuart Douglas > Attachments: WFLY-3529.tar.gz, WFLY-3529.war > > > After migration our AS from Woldfly 8.0.0 to 8.1.0 we get this issue that we think has been fixed in the previous release of wildfly. > ERREOR code : > 2014-06-20 12:45:21,092 ERROR [io.undertow.request] (default task-11) Blocking request failed HttpServerExchange{ GET /xenturion/faces/public/500.xhtml}: java.lang.RuntimeException: java.lang.IllegalStateException: UT000010: Session not found cX6YRwOmoXcB8FFUdNY2r7Te > at io.undertow.servlet.spec.RequestDispatcherImpl.error(RequestDispatcherImpl.java:408) > at io.undertow.servlet.spec.RequestDispatcherImpl.error(RequestDispatcherImpl.java:311) > at io.undertow.servlet.spec.HttpServletResponseImpl.sendError(HttpServletResponseImpl.java:128) > at io.undertow.servlet.spec.HttpServletResponseImpl.sendError(HttpServletResponseImpl.java:142) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:273) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:177) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:727) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40] > Caused by: java.lang.IllegalStateException: UT000010: Session not found cX6YRwOmoXcB8FFUdNY2r7Te > at io.undertow.server.session.InMemorySessionManager$SessionImpl.getAttribute(InMemorySessionManager.java:319) > at io.undertow.servlet.spec.HttpSessionImpl.getAttribute(HttpSessionImpl.java:121) > at org.springframework.security.web.context.HttpSessionSecurityContextRepository.readSecurityContextFromSession(HttpSessionSecurityContextRepository.java:144) > at org.springframework.security.web.context.HttpSessionSecurityContextRepository.loadContext(HttpSessionSecurityContextRepository.java:86) > at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:82) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192) > at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160) > at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:343) > at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:260) > at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:60) > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) > at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:229) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchToPath(ServletInitialHandler.java:172) > at io.undertow.servlet.spec.RequestDispatcherImpl.error(RequestDispatcherImpl.java:402) > ====================================================== > this issue happens after a http session invalidate action and it' not a regular problems. > Best regards, > Youssef -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-305) No file name information in detail error when compiling the java file

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWEB-305?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWEB-305: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1155635|https://bugzilla.redhat.com/show_bug.cgi?id=1155635] from MODIFIED to ON_QA > No file name information in detail error when compiling the java file > ---------------------------------------------------------------------- > > Key: JBWEB-305 > URL: https://issues.jboss.org/browse/JBWEB-305 > Project: JBoss Web > Issue Type: Bug > Affects Versions: JBossWeb-7.4.0.GA, JBossWeb-7.5.0.GA > Reporter: Aaron Ogburn > Assignee: Remy Maucherat > Priority: Minor > > JBossWeb does not have a fix to https://issues.apache.org/bugzilla/show_bug.cgi?id=54466. Helpful file name information can be left off of compilation errors, for example: > {code} > ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/helloworld2].[jsp]] (http-/127.0.0.1:8080-1) JBWEB000236: Servlet.service() for servlet jsp threw exception: org.apache.jasper.JasperException: JBWEB004062: Unable to compile class for JSP: > JBWEB004061: An error occurred at line: 32 in the generated java file > The code of method _jspService(HttpServletRequest, HttpServletResponse) is exceeding the 65535 bytes limit > JBWEB004211: Stacktrace: > at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:85) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4] > at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:69) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4] > at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:451) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4] > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

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: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1077156|https://bugzilla.redhat.com/show_bug.cgi?id=1077156] from MODIFIED to ON_QA > 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)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-195) Outbound LDAP connection in domain mode test case

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-195?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-195: ------------------------------------------------ Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1148400|https://bugzilla.redhat.com/show_bug.cgi?id=1148400] from MODIFIED to ON_QA > Outbound LDAP connection in domain mode test case > ------------------------------------------------- > > Key: WFCORE-195 > URL: https://issues.jboss.org/browse/WFCORE-195 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management, Security, Test Suite > Affects Versions: 1.0.0.Alpha11 > Reporter: Ondrej Kotek > Assignee: Ondrej Kotek > Fix For: 1.0.0.Alpha11 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1521) Deployment runtime-name is not being handled properly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1521?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1521: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 964446|https://bugzilla.redhat.com/show_bug.cgi?id=964446] from MODIFIED to ON_QA > Deployment runtime-name is not being handled properly > ----------------------------------------------------- > > Key: WFLY-1521 > URL: https://issues.jboss.org/browse/WFLY-1521 > Project: WildFly > Issue Type: Feature Request > Affects Versions: 8.0.0.Alpha1 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 8.0.0.Alpha4 > > > In case archive is deployed with runtime name that does not match archive name, it breaks CLI/GUI commands. > [standalone@localhost:9999 /] deploy --runtime-name=nnn.ear /home/baranowb/redhat/git/jboss-as-quickstart/ejb-in-ear/ear/target/jboss-as-ejb-in-ear-ear-xxxx.ear > [standalone@localhost:9999 /] /deployment=jboss-as-ejb-in-ear-ear-xxxx.ear/subdeployment=jboss-as-ejb-in-ear-ejb.jar/subsystem=ejb3/stateful-session-bean=GreeterEJB:read-resource(include-runtime=true) > { > "outcome" => "failed", > "rolled-back" => true > } > 14:05:23,235 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) JBAS014612: Operation ("read-attribute") failed - address: ([ > ("deployment" => "jboss-as-ejb-in-ear-ear-xxxx.ear"), > ("subdeployment" => "jboss-as-ejb-in-ear-ejb.jar"), > ("subsystem" => "ejb3"), > ("stateful-session-bean" => "GreeterEJB") > ]): org.jboss.msc.service.ServiceNotFoundException: Service service jboss.deployment.subunit."jboss-as-ejb-in-ear-ear-xxxx.ear"."jboss-as-ejb-in-ear-ejb.jar".component.GreeterEJB.START not found > at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:448) [jboss-msc-1.0.4.GA.jar:1.0.4.GA] > at org.jboss.as.controller.OperationContextImpl$OperationContextServiceRegistry.getRequiredService(OperationContextImpl.java:1068) [jboss-as-controller-7.2.2-internal-SNAPSHOT.jar:7.2.2-internal-SNAPSHOT] > at org.jboss.as.ejb3.subsystem.deployment.AbstractRuntimeMetricsHandler.executeRuntimeStep(AbstractRuntimeMetricsHandler.java:69) > at > .... > However some seem unaffected: > [standalone@localhost:9990 /] /deployment=jboss-as-ejb-in-ear-ear-xxxx.ear:read-resource > { > "outcome" => "success", > "result" => { > "content" => [{"hash" => bytes { > 0x5c, 0x22, 0x14, 0x99, 0xff, 0x23, 0x45, 0xfc, > 0x15, 0xaf, 0x1b, 0x97, 0x8c, 0x14, 0x75, 0x06, > 0xa2, 0xeb, 0xfb, 0x58 > }}], > "enabled" => true, > "name" => "jboss-as-ejb-in-ear-ear-xxxx.ear", > "persistent" => true, > "runtime-name" => "nnn.ear", > "subsystem" => undefined, > "subdeployment" => { > "jboss-as-ejb-in-ear-web.war" => undefined, > "jboss-as-ejb-in-ear-ejb.jar" => undefined > } > } > } > [standalone@localhost:9990 /] -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3435) jboss-as-infinispan_1_X.xsd schema has incorrect default value for flush-lock-timeout in write-behind

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3435?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3435: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1007015|https://bugzilla.redhat.com/show_bug.cgi?id=1007015] from MODIFIED to ON_QA > jboss-as-infinispan_1_X.xsd schema has incorrect default value for flush-lock-timeout in write-behind > ----------------------------------------------------------------------------------------------------- > > Key: WFLY-3435 > URL: https://issues.jboss.org/browse/WFLY-3435 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 9.0.0.Alpha1 > > > Description of problem: > In org.infinispan.loaders.decorators.AsyncStoreConfig, the default flushLockTimeout is set to 5000. However, the default in the JBoss Infinispan schema ($JBOSS_HOME/docs/schema/jboss-as-infinispan_1_X.xsd) is set to 1. Because of this, if the thread-pool-size for write-behind is increased, then it is likely that one of the threads will not be able to obtain the state map lock within the 1 millisecond time provided by the schema default. This results in the following error: > ERROR o.i.loaders.decorators.AsyncStore.run - ISPN000051: Unexpected error > org.infinispan.CacheException: Unable to acquire lock on update map > at org.infinispan.loaders.decorators.AsyncStore.acquireLock(AsyncStore.java:293) ~[infinispan-core-5.1.3.FINAL.jar:5.1.3.FINAL] > at org.infinispan.loaders.decorators.AsyncStore.access$900(AsyncStore.java:86) ~[infinispan-core-5.1.3.FINAL.jar:5.1.3.FINAL] > at org.infinispan.loaders.decorators.AsyncStore$AsyncProcessor.innerRun(AsyncStore.java:336) ~[infinispan-core-5.1.3.FINAL.jar:5.1.3.FINAL] > at org.infinispan.loaders.decorators.AsyncStore$AsyncProcessor.run(AsyncStore.java:312) ~[infinispan-core-5.1.3.FINAL.jar:5.1.3.FINAL] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) ~[na:1.6.0_31] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) ~[na:1.6.0_31] > at java.lang.Thread.run(Thread.java:662) ~[na:1.6.0_31] > Version-Release number of selected component (if applicable): > Infinispan version 5.1.8 > How reproducible: > Code inspection > Steps to Reproduce: > 1. Check the default value for flush-lock-timeout in $JBOSS_HOME/docs/schema/jboss-as-infinispan_1_3.xsd > 2. Check the default value for flushLockTimeout in the org.infinispan.loaders.decorators.AsyncStoreConfig class > 3. Note the disparity > Actual results: > Default in schema is 1 > Expected results: > Default in schema is 5000 > Additional info: -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-163) add-user only escaping first occurrence of special characters

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-163?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-163: ------------------------------------------------ Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1150020|https://bugzilla.redhat.com/show_bug.cgi?id=1150020] from MODIFIED to ON_QA > add-user only escaping first occurrence of special characters > ------------------------------------------------------------- > > Key: WFCORE-163 > URL: https://issues.jboss.org/browse/WFCORE-163 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha10 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3937) Jackson libs are Private, should be Public

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3937?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3937: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1094937|https://bugzilla.redhat.com/show_bug.cgi?id=1094937] from MODIFIED to CLOSED > Jackson libs are Private, should be Public > ------------------------------------------ > > Key: WFLY-3937 > URL: https://issues.jboss.org/browse/WFLY-3937 > Project: WildFly > Issue Type: Bug > Environment: EAP 6.3.0.ER2 > Reporter: Marek Novotny > Assignee: Marek Novotny > Fix For: 9.0.0.Beta1 > > > The following libraries have their module.xml files set to *private*: > * org.codehaus.jackson.jackson-core-asl > * org.codehaus.jackson.jackson-mapper-asl > * org.codehaus.jackson.jackson-jaxrs > * org.codehaus.jackson.jackson-xc > After talking with [~bill.burke], these should be *public*. > While these modules are private, the use of them creates WARNings in the stack trace. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2551) AS7.2 - JMX Datasource pool & jdbc statistics dissapear if you enable validation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2551?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2551: ----------------------------------------------- Martin Simka <msimka(a)redhat.com> changed the Status of [bug 1150821|https://bugzilla.redhat.com/show_bug.cgi?id=1150821] from ON_QA to VERIFIED > AS7.2 - JMX Datasource pool & jdbc statistics dissapear if you enable validation > -------------------------------------------------------------------------------- > > Key: WFLY-2551 > URL: https://issues.jboss.org/browse/WFLY-2551 > Project: WildFly > Issue Type: Bug > Components: JCA, JMX > Reporter: Will Tatam > Assignee: Brian Stansberry > Fix For: 9.0.0.Alpha1 > > > If you just create a basic datasource under AS 7.2 the you can view the current statistics about the pool under > jboss.as:subsystem=datasources,data-source=mySQL,statistics=pool > However, if you add the following then sometimes the statistics=pool and statistics=jdbc entries disspaear > <validation><check-valid-connection-sql>select 1</check-valid-connection-sql></validation> -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

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