February 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-332) Add sessionDrainingStrategy configuration option to modcluster subsystem

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-332?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-332: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 922042|https://bugzilla.redhat.com/show_bug.cgi?id=922042] from MODIFIED to ON_QA > Add sessionDrainingStrategy configuration option to modcluster subsystem > ------------------------------------------------------------------------ > > Key: WFLY-332 > URL: https://issues.jboss.org/browse/WFLY-332 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Radoslav Husar > Assignee: Jean-Frederic Clere > Fix For: 8.0.0.Beta1 > > > Add sessionDrainingStrategy configuration option to modcluster subsystem > * xsd 1.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2913) Generic http management operation upload handler

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2913?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2913: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1066476|https://bugzilla.redhat.com/show_bug.cgi?id=1066476] from MODIFIED to ON_QA > Generic http management operation upload handler > ------------------------------------------------ > > Key: WFLY-2913 > URL: https://issues.jboss.org/browse/WFLY-2913 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Emanuel Muckenhuber > Assignee: Emanuel Muckenhuber > Fix For: 8.0.1.Final > > > The current /management http API handler, does not support generic content uploads, where the add-content handler only allows addition to the content repository. Since operations might attach multiple streams to the operation we need a http handler which can deal with those requests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2266) Deployment Overlay feature is not able to replace the application libraries.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2266?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2266: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1016995|https://bugzilla.redhat.com/show_bug.cgi?id=1016995] from MODIFIED to ON_QA > Deployment Overlay feature is not able to replace the application libraries. > ---------------------------------------------------------------------------- > > Key: WFLY-2266 > URL: https://issues.jboss.org/browse/WFLY-2266 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Beta1 > Environment: All Operating Systems > Reporter: Jay Kumar SenSharma > Assignee: Stuart Douglas > Labels: deployment > Fix For: 8.0.0.CR1 > > > ----------------------- > According to the documentation: [1] the deployment overlay feature is applicable for "swapping out deployment descriptors, modifying static web resources to change the branding of an application, or even replacing jar libraries with different versions." > Here it talks about "replacing jar libraries" which is not working as expected and causes the following error. > [1] https://docs.jboss.org/author/display/AS72/Deployment+Overlays > Follow the below sequence of deployment and overlay: > Steps to Reproduce: > ------------------ > *Step-1).* Undeploy if any existing application is deployed and then freshly deploy the application. > {quote} > [standalone@localhost:9999 /] undeploy DeploymentOverlayDemo.war > [standalone@localhost:9999 /] deploy /home/jaysensharma/TestApp/build/DeploymentOverlayDemo.war > {quote} > *Step-2).* Make some changes in java code _"Hello.java"_ . Create a new JAR Hello.jar which we want to replace at _(/WEB-INF/lib/Hello.jar)_ using deployment-overlay feature. In the attached ant based Demo just do _"ant compile"_ to create a new Jar _"${project.dir}/tmp/Hello.jar"_ > *Step-3).* Use the following command in order to replace the "/WEB-INF/lib/Hello.jar" with the newly created Hello.jar using deployment overlay feature as following: > {quote} > [standalone@localhost:9999 /] deployment-overlay add --name=myOverLay_1 --content=/WEB-INF/lib/Hello.jar=/home/jaysensharma/TestApp/tmp/Hello.jar --deployments=DeploymentOverlayDemo.war --redeploy-affected > {quote} > > Above causes the following Exception: > {quote} > 12:09:59,736 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS018224: Unregister web context: /DeploymentOverlayDemo > 12:09:59,760 WARN [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017530: Could not delete servlet temp file /NotBackedUp/SVN_16_Jan/WildFly/build_Apps/wildfly-8.0.0.Beta2-SNAPSHOT/standalone/tmp/DeploymentOverlayDemo.war/org/apache/jsp > 12:09:59,761 WARN [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017530: Could not delete servlet temp file /NotBackedUp/SVN_16_Jan/WildFly/build_Apps/wildfly-8.0.0.Beta2-SNAPSHOT/standalone/tmp/DeploymentOverlayDemo.war/org/apache > 12:09:59,761 WARN [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017530: Could not delete servlet temp file /NotBackedUp/SVN_16_Jan/WildFly/build_Apps/wildfly-8.0.0.Beta2-SNAPSHOT/standalone/tmp/DeploymentOverlayDemo.war/org > 12:09:59,762 WARN [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017530: Could not delete servlet temp file /NotBackedUp/SVN_16_Jan/WildFly/build_Apps/wildfly-8.0.0.Beta2-SNAPSHOT/standalone/tmp/DeploymentOverlayDemo.war > 12:09:59,787 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment DeploymentOverlayDemo.war (runtime-name: DeploymentOverlayDemo.war) in 56ms > 12:09:59,789 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "DeploymentOverlayDemo.war" (runtime-name: "DeploymentOverlayDemo.war") > 12:09:59,799 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."DeploymentOverlayDemo.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."DeploymentOverlayDemo.war".STRUCTURE: JBAS018733: Failed to process phase STRUCTURE of deployment "DeploymentOverlayDemo.war" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1944) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1877) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21] > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018776: Failed to get content for deployment overlay myOverLay_1 at /WEB-INF/lib/Hello.jar > at org.jboss.as.server.deployment.ContentOverrideDeploymentUnitProcessor.deploy(ContentOverrideDeploymentUnitProcessor.java:70) [wildfly-server-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT] > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT] > ... 5 more > Caused by: java.io.IOException: VFS000017: Filesystem already mounted at mount point ""/content/DeploymentOverlayDemo.war/WEB-INF/lib/Hello.jar"" > at org.jboss.vfs.VFS.mount(VFS.java:127) [jboss-vfs-3.2.2.Final.jar:3.2.2.Final] > at org.jboss.vfs.VFS.doMount(VFS.java:336) [jboss-vfs-3.2.2.Final.jar:3.2.2.Final] > at org.jboss.vfs.VFS.mountReal(VFS.java:423) [jboss-vfs-3.2.2.Final.jar:3.2.2.Final] > at org.jboss.as.server.deployment.ContentOverrideDeploymentUnitProcessor.deploy(ContentOverrideDeploymentUnitProcessor.java:67) [wildfly-server-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT] > ... 6 more > 12:09:59,805 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) JBAS014613: Operation ("redeploy") failed - address: ([("deployment" => "DeploymentOverlayDemo.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"DeploymentOverlayDemo.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"DeploymentOverlayDemo.war\".STRUCTURE: JBAS018733: Failed to process phase STRUCTURE of deployment \"DeploymentOverlayDemo.war\" > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018776: Failed to get content for deployment overlay myOverLay_1 at /WEB-INF/lib/Hello.jar > Caused by: java.io.IOException: VFS000017: Filesystem already mounted at mount point \"\"/content/DeploymentOverlayDemo.war/WEB-INF/lib/Hello.jar\"\""}} > 12:09:59,809 ERROR [org.jboss.as.server] (management-handler-thread - 3) JBAS015860: Redeploy of deployment "DeploymentOverlayDemo.war" was rolled back with the following failure message: > {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"DeploymentOverlayDemo.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"DeploymentOverlayDemo.war\".STRUCTURE: JBAS018733: Failed to process phase STRUCTURE of deployment \"DeploymentOverlayDemo.war\" > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018776: Failed to get content for deployment overlay myOverLay_1 at /WEB-INF/lib/Hello.jar > Caused by: java.io.IOException: VFS000017: Filesystem already mounted at mount point \"\"/content/DeploymentOverlayDemo.war/WEB-INF/lib/Hello.jar\"\""}} > 12:09:59,814 INFO [org.jboss.as.controller] (management-handler-thread - 3) JBAS014774: Service status report > JBAS014777: Services which failed to start: service jboss.deployment.unit."DeploymentOverlayDemo.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."DeploymentOverlayDemo.war".STRUCTURE: JBAS018733: Failed to process phase STRUCTURE of deployment "DeploymentOverlayDemo.war" > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2536) NPE in cli is thrown when using preserve, override without parameter

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2536?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2536: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1032041|https://bugzilla.redhat.com/show_bug.cgi?id=1032041] from MODIFIED to ON_QA > NPE in cli is thrown when using preserve, override without parameter > -------------------------------------------------------------------- > > Key: WFLY-2536 > URL: https://issues.jboss.org/browse/WFLY-2536 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Patching > Affects Versions: 8.0.0.Beta1 > Reporter: Emanuel Muckenhuber > Assignee: Alexey Loubyansky > Priority: Minor > Fix For: 8.0.0.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2849) Upgrade jboss-remote-naming to 2.0.0 Final or later

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2849?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2849: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1024153|https://bugzilla.redhat.com/show_bug.cgi?id=1024153] from MODIFIED to ON_QA > Upgrade jboss-remote-naming to 2.0.0 Final or later > --------------------------------------------------- > > Key: WFLY-2849 > URL: https://issues.jboss.org/browse/WFLY-2849 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Naming > Affects Versions: 8.0.0.CR1 > Reporter: Brad Maxwell > Assignee: Eduardo Martins > > Upgrade jboss-remote-naming to 2.0.0 Final or later to resolve linked issues -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2995) Using a log4j appender as a custom-handler should invoke the activateOptions if required

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2995?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2995: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1066606|https://bugzilla.redhat.com/show_bug.cgi?id=1066606] from MODIFIED to ON_QA > Using a log4j appender as a custom-handler should invoke the activateOptions if required > ---------------------------------------------------------------------------------------- > > Key: WFLY-2995 > URL: https://issues.jboss.org/browse/WFLY-2995 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: James Perkins > Assignee: James Perkins > Fix For: 8.0.1.Final > > > Currently the {{OptionHandler.activateOptions}} is only invoked during construction of a log4j appender. This invocation should happen if any property is updated or added. The invocation of this method should also only happen once. Multiple invocation could result in errors or leave the appender in an invalid state. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2922) Add description to Messaging subsystem XML Schema

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2922?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2922: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1019069|https://bugzilla.redhat.com/show_bug.cgi?id=1019069] from MODIFIED to ON_QA > Add description to Messaging subsystem XML Schema > ------------------------------------------------- > > Key: WFLY-2922 > URL: https://issues.jboss.org/browse/WFLY-2922 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JMS > Affects Versions: 8.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.1.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-822) MBean created via EAR/META-INF/jboss-service.xml from class defined in JBoss module gets wrong TCCL

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-822?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-822: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1054972|https://bugzilla.redhat.com/show_bug.cgi?id=1054972] from MODIFIED to ON_QA > MBean created via EAR/META-INF/jboss-service.xml from class defined in JBoss module gets wrong TCCL > --------------------------------------------------------------------------------------------------- > > Key: WFLY-822 > URL: https://issues.jboss.org/browse/WFLY-822 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Class Loading, Server > Environment: Java 6u31 > Reporter: Zachary Bedell > Assignee: jaikiran pai > Labels: classloader, mbean, modules > Fix For: 8.0.0.Alpha3 > > Attachments: SarTcclTst.tbz > > > When an MBean is loaded from jboss-service.xml within an EAR, the TCCL should point to the EAR deployment so that config files and other resources can be classloaded from the EAR. Under JBoss 7.1.1.Final, the TCCL in a module loaded MBean's start() method is the module's ClassLoader. No reference to the EAR deployment's classloader is available, thus EAR resources are not available within the MBean. > It appears that org.jboss.as.service.AbstractService::invokeLifecycleMethod() incorrectly sets the TCCL to the module's defining classloader rather than the EAR's: > {{{ > protected void invokeLifecycleMethod(final Method method) throws InvocationTargetException, IllegalAccessException { > if (method != null) { > final ClassLoader old = SecurityActions.setThreadContextClassLoader(mBeanInstance.getClass().getClassLoader()); > try { > method.invoke(mBeanInstance); > } finally { > SecurityActions.resetThreadContextClassLoader(old); > } > } > } > }}} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBEE-147) QueryTagSupport does not close prepared statements and result sets correctly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBEE-147?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on JBEE-147: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1065854|https://bugzilla.redhat.com/show_bug.cgi?id=1065854] from MODIFIED to ON_QA > QueryTagSupport does not close prepared statements and result sets correctly > ---------------------------------------------------------------------------- > > Key: JBEE-147 > URL: https://issues.jboss.org/browse/JBEE-147 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Components: jboss-jstl-api > Reporter: James Livingston > Assignee: Shelly McGowan > Fix For: jboss-jstl-api_1.2_spec-1.0.5.Final, jboss-jstl-api_1.2_spec-1.1.0.Final > > > The JSTL spec artifact contain implementation code forked from the Apache taglib project. > One bug fixed upstreak since the fork is https://issues.apache.org/bugzilla/show_bug.cgi?id=17388, which can cause prepared statement and/or result set objects not to be closed correctly. > The fix can be cherry-picked from (http://svn.apache.org/viewvc/jakarta/taglibs/proper/standard/trunk/src/or...), unless there was a plan to rebase on the recently released upstream 1.2.1 which includes the fix -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-795) AdvancedLdap login module does not handle a user that has a slash character in the uid

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-795?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-795: -------------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1039955|https://bugzilla.redhat.com/show_bug.cgi?id=1039955] from MODIFIED to ON_QA > AdvancedLdap login module does not handle a user that has a slash character in the uid > -------------------------------------------------------------------------------------- > > Key: SECURITY-795 > URL: https://issues.jboss.org/browse/SECURITY-795 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_2_5 > Reporter: Derek Horton > Assignee: Derek Horton > Fix For: Negotiation_2_2_7 > > Attachments: SECURITY-795.patch > > > AdvancedLdap login module does not handle a user that has a slash character in the uid. > For example, JBoss will fail to authenticate the following user correctly: > dn: uid=weird/user,ou=Users,dc=my-domain,dc=com > uid: weird/user > cn: Weird User -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 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 February 2014