October 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3446) cli system props specified with -Dxxx for jboss-cli.sh/bat are ignored

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3446?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3446: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1103620|https://bugzilla.redhat.com/show_bug.cgi?id=1103620] from ON_QA to ASSIGNED > cli system props specified with -Dxxx for jboss-cli.sh/bat are ignored > ---------------------------------------------------------------------- > > Key: WFLY-3446 > URL: https://issues.jboss.org/browse/WFLY-3446 > Project: WildFly > Issue Type: Bug > Components: CLI, Scripts > Affects Versions: 8.1.0.Final > Reporter: Alexey Loubyansky > Assignee: Tomaz Cerar > Fix For: 8.2.0.CR1, 9.0.0.Beta1 > > > E.g. ./jboss-cli.sh -Djboss.cli.config=<PATH>/jboss-cli.xml > The system property won't be set, instead the argument will treated as simply a command line argument. > This has to be fixed in the scripts themselves launching the CLI. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4010) Cli icon path to be loaded from the Manifest of product module.

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/WFLY-4010?page=com.atlassian.jira.plugin.... ] Panagiotis Sotiropoulos closed WFLY-4010. ----------------------------------------- Resolution: Won't Fix Cli should not be dependent on other module. > Cli icon path to be loaded from the Manifest of product module. > --------------------------------------------------------------- > > Key: WFLY-4010 > URL: https://issues.jboss.org/browse/WFLY-4010 > Project: WildFly > Issue Type: Task > Components: Build System, CLI > Affects Versions: 9.0.0.Alpha1 > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > Fix For: 9.0.0.CR1 > > > The cli icon path should be loaded from the MANIFEST.MF file of module product using param : JBoss-Product-Icon -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-191) Syslog reconnect timeout does not take effect at runtime

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-191?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-191: ------------------------------------------------ Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1148433|https://bugzilla.redhat.com/show_bug.cgi?id=1148433] from ON_QA to VERIFIED > Syslog reconnect timeout does not take effect at runtime > -------------------------------------------------------- > > Key: WFCORE-191 > URL: https://issues.jboss.org/browse/WFCORE-191 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha10 > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 1.0.0.Alpha11 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4028) Can't register cache-container with more than one local-cache entries

by Dmitry Lisovsky (JIRA)

Dmitry Lisovsky created WFLY-4028: ------------------------------------- Summary: Can't register cache-container with more than one local-cache entries Key: WFLY-4028 URL: https://issues.jboss.org/browse/WFLY-4028 Project: WildFly Issue Type: Bug Affects Versions: 9.0.0.Alpha1 Reporter: Dmitry Lisovsky Assignee: Jason Greene When I try to add my cache-container with more then one local-cache entries in standalone-full.xml I got error: {noformat} ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 38) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "infinispan"), ("cache-container" => "my-container-name"), ("local-cache" => "my-2nd-local-cache-name") ]): org.jboss.msc.service.DuplicateServiceException: Service jboss.naming.context.java.jboss.true is already registered at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:767) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at org.jboss.as.controller.OperationContextImpl$ContextServiceBuilder.install(OperationContextImpl.java:1866) [wildfly-controller-1.0.0.Alpha8.jar:1.0.0.Alpha8] at org.jboss.as.clustering.infinispan.subsystem.CacheAddHandler.installJndiService(CacheAddHandler.java:318) at org.jboss.as.clustering.infinispan.subsystem.CacheAddHandler.installRuntimeServices(CacheAddHandler.java:225) at org.jboss.as.clustering.infinispan.subsystem.CacheAddHandler.performRuntime(CacheAddHandler.java:180) at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:131) [wildfly-controller-1.0.0.Alpha8.jar:1.0.0.Alpha8] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:695) [wildfly-controller-1.0.0.Alpha8.jar:1.0.0.Alpha8] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:530) [wildfly-controller-1.0.0.Alpha8.jar:1.0.0.Alpha8] at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:303) [wildfly-controller-1.0.0.Alpha8.jar:1.0.0.Alpha8] at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:298) [wildfly-controller-1.0.0.Alpha8.jar:1.0.0.Alpha8] at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:355) [wildfly-controller-1.0.0.Alpha8.jar:1.0.0.Alpha8] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final] {noformat} The XML I'm trying to add: {noformat} <cache-container name="my-container-name" jndi-name="java:jboss/infinispan/container/my-container-name"> <local-cache name="my-1st-local-cache-name" batching="true"> <eviction strategy="LRU" max-entries="10000"/> <expiration max-idle="100000"/> </local-cache> <local-cache name="my-2nd-local-cache-name" batching="true"> <eviction strategy="LRU" max-entries="10000"/> <expiration max-idle="100000"/> </local-cache> <local-cache name="my-3rd-local-cache-name" batching="true"> <eviction strategy="LRU" max-entries="10000"/> <expiration max-idle="100000"/> </local-cache> </cache-container> {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-108) Incorrect use of ReloadRequiredWriteAttributeHandler for host resources

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-108?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-108: ------------------------------------------------ Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1085228|https://bugzilla.redhat.com/show_bug.cgi?id=1085228] from POST to MODIFIED > Incorrect use of ReloadRequiredWriteAttributeHandler for host resources > ----------------------------------------------------------------------- > > Key: WFCORE-108 > URL: https://issues.jboss.org/browse/WFCORE-108 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Chao Wang > Priority: Critical > Fix For: 1.0.0.Alpha9 > > > ReloadRequiredWriteAttributeHandler inherits the default behavior of AbstractWriteAttributeHandler.requiresRuntime(), which is to only process Stage.RUNTIME if context.isNormalServer(). So any use in host resources needs to override that behavior. This isn't done in at least some places. See https://bugzilla.redhat.com/show_bug.cgi?id=1085228 for an example. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

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: ----------------------------------------------- Chao Wang <chaowan(a)redhat.com> changed the Status of [bug 1155638|https://bugzilla.redhat.com/show_bug.cgi?id=1155638] from NEW to MODIFIED > 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.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4023) javax.el.ImportHandler#importClass & #importPackage doesn't import WEB-INF/classes

by Patrick Garner (JIRA)

[ https://issues.jboss.org/browse/WFLY-4023?page=com.atlassian.jira.plugin.... ] Patrick Garner edited comment on WFLY-4023 at 10/28/14 8:02 PM: ---------------------------------------------------------------- foo.bar.EnumConfig is where you want to set the break point (at line 30). Go to http://localhost:8080/ImportHandlerDebug/index.xhtml Take a look at ImportHandler.notAClass and notice that it contains the entry "foo.bar.enumeration.YesOrNo" which indicates that the class was not found. was (Author: pgarner): foo.bar.EnumConfig is where you want to set the break point. Go to http://localhost:8080/ImportHandlerDebug/index.xhtml Take a look at ImportHandler.notAClass and notice that it contains the entry "foo.bar.enumeration.YesOrNo" which indicates that the class was not found. > javax.el.ImportHandler#importClass & #importPackage doesn't import WEB-INF/classes > ---------------------------------------------------------------------------------- > > Key: WFLY-4023 > URL: https://issues.jboss.org/browse/WFLY-4023 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 8.1.0.Final > Environment: Win7, Wildfly 8.1.0.Final > Reporter: Patrick Garner > Assignee: Farah Juma > Attachments: ImportHandlerDebug.zip > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > ImportHandler is not importing classes in WEB-INF/classes and, thus, developers are unable to import classes into the EL evaluation environment per EL 3.0 spec. section 1.22.2 "Imports of Packages, Classes, and Static Fields" > Here's the ImportHandler relevant code (https://github.com/jboss/jboss-el-api_spec/blob/master/src/main/java/java...) > {code:java} > private Class<?> getClassFor(String className) { > if (!notAClass.contains(className)) { > try { > return Class.forName(className, false, getClass().getClassLoader()); > } catch (ClassNotFoundException ex) { > notAClass.add(className); > } > } > return null; > } > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4023) javax.el.ImportHandler#importClass & #importPackage doesn't import WEB-INF/classes

by Patrick Garner (JIRA)

[ https://issues.jboss.org/browse/WFLY-4023?page=com.atlassian.jira.plugin.... ] Patrick Garner edited comment on WFLY-4023 at 10/28/14 8:01 PM: ---------------------------------------------------------------- [~fjuma] Yes I do have an app to share. Where do I put it? Should I zip it up? Not sure how to share it with you... UPDATE: I attached the app as ImportHandlerDebug.zip was (Author: pgarner): [~fjuma] Yes I do have an app to share. Where do I put it? Should I zip it up? Not sure how to share it with you... > javax.el.ImportHandler#importClass & #importPackage doesn't import WEB-INF/classes > ---------------------------------------------------------------------------------- > > Key: WFLY-4023 > URL: https://issues.jboss.org/browse/WFLY-4023 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 8.1.0.Final > Environment: Win7, Wildfly 8.1.0.Final > Reporter: Patrick Garner > Assignee: Farah Juma > Attachments: ImportHandlerDebug.zip > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > ImportHandler is not importing classes in WEB-INF/classes and, thus, developers are unable to import classes into the EL evaluation environment per EL 3.0 spec. section 1.22.2 "Imports of Packages, Classes, and Static Fields" > Here's the ImportHandler relevant code (https://github.com/jboss/jboss-el-api_spec/blob/master/src/main/java/java...) > {code:java} > private Class<?> getClassFor(String className) { > if (!notAClass.contains(className)) { > try { > return Class.forName(className, false, getClass().getClassLoader()); > } catch (ClassNotFoundException ex) { > notAClass.add(className); > } > } > return null; > } > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4023) javax.el.ImportHandler#importClass & #importPackage doesn't import WEB-INF/classes

by Patrick Garner (JIRA)

[ https://issues.jboss.org/browse/WFLY-4023?page=com.atlassian.jira.plugin.... ] Patrick Garner updated WFLY-4023: --------------------------------- Attachment: ImportHandlerDebug.zip foo.bar.EnumConfig is where you want to set the break point. Go to http://localhost:8080/ImportHandlerDebug/index.xhtml Take a look at ImportHandler.notAClass and notice that it contains the entry "foo.bar.enumeration.YesOrNo" which indicates that the class was not found. > javax.el.ImportHandler#importClass & #importPackage doesn't import WEB-INF/classes > ---------------------------------------------------------------------------------- > > Key: WFLY-4023 > URL: https://issues.jboss.org/browse/WFLY-4023 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 8.1.0.Final > Environment: Win7, Wildfly 8.1.0.Final > Reporter: Patrick Garner > Assignee: Farah Juma > Attachments: ImportHandlerDebug.zip > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > ImportHandler is not importing classes in WEB-INF/classes and, thus, developers are unable to import classes into the EL evaluation environment per EL 3.0 spec. section 1.22.2 "Imports of Packages, Classes, and Static Fields" > Here's the ImportHandler relevant code (https://github.com/jboss/jboss-el-api_spec/blob/master/src/main/java/java...) > {code:java} > private Class<?> getClassFor(String className) { > if (!notAClass.contains(className)) { > try { > return Class.forName(className, false, getClass().getClassLoader()); > } catch (ClassNotFoundException ex) { > notAClass.add(className); > } > } > return null; > } > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4023) javax.el.ImportHandler#importClass & #importPackage doesn't import WEB-INF/classes

by Patrick Garner (JIRA)

[ https://issues.jboss.org/browse/WFLY-4023?page=com.atlassian.jira.plugin.... ] Patrick Garner commented on WFLY-4023: -------------------------------------- [~fjuma] Yes I do have an app to share. Where do I put it? Should I zip it up? Not sure how to share it with you... > javax.el.ImportHandler#importClass & #importPackage doesn't import WEB-INF/classes > ---------------------------------------------------------------------------------- > > Key: WFLY-4023 > URL: https://issues.jboss.org/browse/WFLY-4023 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 8.1.0.Final > Environment: Win7, Wildfly 8.1.0.Final > Reporter: Patrick Garner > Assignee: Farah Juma > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > ImportHandler is not importing classes in WEB-INF/classes and, thus, developers are unable to import classes into the EL evaluation environment per EL 3.0 spec. section 1.22.2 "Imports of Packages, Classes, and Static Fields" > Here's the ImportHandler relevant code (https://github.com/jboss/jboss-el-api_spec/blob/master/src/main/java/java...) > {code:java} > private Class<?> getClassFor(String className) { > if (!notAClass.contains(className)) { > try { > return Class.forName(className, false, getClass().getClassLoader()); > } catch (ClassNotFoundException ex) { > notAClass.add(className); > } > } > return null; > } > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

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 October 2014