[JBoss JIRA] (WFLY-2906) WildFly 8.0.0 Final keeps lock on Manifest.mf files in exploded deployment
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2906?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2906:
-----------------------------------------------
Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1085294|https://bugzilla.redhat.com/show_bug.cgi?id=1085294] from ON_QA to VERIFIED
> WildFly 8.0.0 Final keeps lock on Manifest.mf files in exploded deployment
> --------------------------------------------------------------------------
>
> Key: WFLY-2906
> URL: https://issues.jboss.org/browse/WFLY-2906
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JSF, Web (Undertow)
> Affects Versions: 8.0.0.Final
> Environment: Windows7x64, Oracle Java 1.7.0_51
> Reporter: Wolfgang Knauf
> Assignee: Tomaz Cerar
> Fix For: 8.1.0.CR1
>
>
> I have a small JSF web app. When performing exploded deployment, after a ".dodeploy"/."undeploy"/".dodeploy"/".undeploy" cycle, the manifest.mf files are locked (I cannot delete the files, Windows tells me that they are used by a Java process)
> A similar sample without JSF (and beans.xml) does not show this problem.
> See the forum post for more details and the zip file of the "to be deployed" app.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
12 years, 2 months
[JBoss JIRA] (WFLY-2850) AJP connector with external authentication
by Sylvain Brouillat (JIRA)
[ https://issues.jboss.org/browse/WFLY-2850?page=com.atlassian.jira.plugin.... ]
Sylvain Brouillat commented on WFLY-2850:
-----------------------------------------
Thanks Stuart, I'll try this out.
> AJP connector with external authentication
> ------------------------------------------
>
> Key: WFLY-2850
> URL: https://issues.jboss.org/browse/WFLY-2850
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.0.0.CR1
> Reporter: Geert Coelmont
> Assignee: Stuart Douglas
> Priority: Critical
> Fix For: 8.1.0.Final
>
>
> Tomcat allows to set the tomcatAuthentication attribute of the AJP connector to false to allow external web servers (e.g. apache httpd) to handle the authentication and pass that along.
> A similar option was added recently to JBossWeb as well (see WFLY-254), but JBossWeb has been replaced by Undertow. With Undertow this option isn't available as far as I can see.
> For me this is a critical problem as there is currently no way I can do negotiated (SPNEGO) authentication from within WildFly+Undertow. (See also WFLY-2404).
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
12 years, 2 months
[JBoss JIRA] (WFLY-155) standalone.bat has an error for setting debug mode with --debug
by Heiko Rupp (JIRA)
[ https://issues.jboss.org/browse/WFLY-155?page=com.atlassian.jira.plugin.s... ]
Heiko Rupp commented on WFLY-155:
---------------------------------
It looks like this error may still exist in WFLY 8.0.0.GA
snert:wildfly-8.0.0.Final hrupp$ bin/standalone.sh --debug
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /Users/hrupp/downloads/wildfly-8.0.0.Final
JAVA: /Library/Java/JavaVirtualMachines/1.7.0u.jdk/Contents/Home/bin/java
JAVA_OPTS: -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n
=========================================================================
Listening for transport dt_socket at address: 8787
08:10:58,385 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final
08:10:58,643 ERROR [stderr] (main) JBAS015801: Invalid option ''
[...]
08:10:58,663 INFO [stdout] (main) --debug [<port>] Activate debug mode with an optional
> standalone.bat has an error for setting debug mode with --debug
> ---------------------------------------------------------------
>
> Key: WFLY-155
> URL: https://issues.jboss.org/browse/WFLY-155
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Scripts
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Minor
> Fix For: 8.0.0.Alpha1
>
>
> In the released EAP 6.1.0-alpha, standalone.bat has these lines:
> {code}
> rem Set debug settings if not already set
> if "%DEBUG_MODE%" == "true" (
> echo "%JAVA_OPTS%" | findstr /I "\-agentlib:jdwp" > nul
> if errorlevel == 1 (
> echo Debug already enabled in JAVA_OPTS, ignoring --debug argument
> ) else (
> set "JAVA_OPTS=%JAVA_OPTS% -agentlib:jdwp=transport=dt_socket,address=%DEBUG_PORT%,server=y,suspend=n"
> )
> )
> {code}
> The check on the error level is wrong. If "findstr" *can* find the agentlib setting, then errorlevel will be 0.
> So the correction is:
> {code}
> if errorlevel == 1 (
> {code}
> should be:
> {code}
> if errorlevel == 0 (
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
12 years, 2 months
[JBoss JIRA] (WFLY-155) standalone.bat has an error for setting debug mode with --debug
by Heiko Rupp (JIRA)
[ https://issues.jboss.org/browse/WFLY-155?page=com.atlassian.jira.plugin.s... ]
Heiko Rupp edited comment on WFLY-155 at 5/5/14 2:18 AM:
---------------------------------------------------------
It looks like this error may still exist in WFLY 8.0.0.GA -- passing a port allows to continue,
but the help syntax clearly says that the port is optional.
snert:wildfly-8.0.0.Final hrupp$ bin/standalone.sh --debug
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /Users/hrupp/downloads/wildfly-8.0.0.Final
JAVA: /Library/Java/JavaVirtualMachines/1.7.0u.jdk/Contents/Home/bin/java
JAVA_OPTS: -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n
=========================================================================
Listening for transport dt_socket at address: 8787
08:10:58,385 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final
08:10:58,643 ERROR [stderr] (main) JBAS015801: Invalid option ''
[...]
08:10:58,663 INFO [stdout] (main) --debug [<port>] Activate debug mode with an optional
was (Author: pilhuhn):
It looks like this error may still exist in WFLY 8.0.0.GA
snert:wildfly-8.0.0.Final hrupp$ bin/standalone.sh --debug
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /Users/hrupp/downloads/wildfly-8.0.0.Final
JAVA: /Library/Java/JavaVirtualMachines/1.7.0u.jdk/Contents/Home/bin/java
JAVA_OPTS: -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n
=========================================================================
Listening for transport dt_socket at address: 8787
08:10:58,385 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final
08:10:58,643 ERROR [stderr] (main) JBAS015801: Invalid option ''
[...]
08:10:58,663 INFO [stdout] (main) --debug [<port>] Activate debug mode with an optional
> standalone.bat has an error for setting debug mode with --debug
> ---------------------------------------------------------------
>
> Key: WFLY-155
> URL: https://issues.jboss.org/browse/WFLY-155
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Scripts
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Minor
> Fix For: 8.0.0.Alpha1
>
>
> In the released EAP 6.1.0-alpha, standalone.bat has these lines:
> {code}
> rem Set debug settings if not already set
> if "%DEBUG_MODE%" == "true" (
> echo "%JAVA_OPTS%" | findstr /I "\-agentlib:jdwp" > nul
> if errorlevel == 1 (
> echo Debug already enabled in JAVA_OPTS, ignoring --debug argument
> ) else (
> set "JAVA_OPTS=%JAVA_OPTS% -agentlib:jdwp=transport=dt_socket,address=%DEBUG_PORT%,server=y,suspend=n"
> )
> )
> {code}
> The check on the error level is wrong. If "findstr" *can* find the agentlib setting, then errorlevel will be 0.
> So the correction is:
> {code}
> if errorlevel == 1 (
> {code}
> should be:
> {code}
> if errorlevel == 0 (
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
12 years, 2 months
[JBoss JIRA] (JBEE-154) ClassCastException in JSPs where spring-web tags and jstl tags are used
by James Livingston (JIRA)
[ https://issues.jboss.org/browse/JBEE-154?page=com.atlassian.jira.plugin.s... ]
James Livingston updated JBEE-154:
----------------------------------
Description:
WFLY-3100 incorporated a fix to the 2.3 version of the JSP APIs, and it would be good to have it in the 2.2 APIs as well.
There is currently no maintenance branch for the 2.2 APIs, so we would need to create one similar to what was done in JBEE-147.
was:
WFLY-3100 incorporated a fix to the 2.3 version of the JSP APIs, and it would be good to have it in the 2.2 APIs as well.
There is currently no maintenance branch for the 2.2 APIs, so we would need to create one.
> ClassCastException in JSPs where spring-web tags and jstl tags are used
> -----------------------------------------------------------------------
>
> Key: JBEE-154
> URL: https://issues.jboss.org/browse/JBEE-154
> Project: JBoss JavaEE Spec APIs
> Issue Type: Bug
> Components: jboss-jsp-api
> Reporter: James Livingston
> Assignee: Shelly McGowan
>
> WFLY-3100 incorporated a fix to the 2.3 version of the JSP APIs, and it would be good to have it in the 2.2 APIs as well.
> There is currently no maintenance branch for the 2.2 APIs, so we would need to create one similar to what was done in JBEE-147.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
12 years, 2 months
[JBoss JIRA] (JBEE-154) ClassCastException in JSPs where spring-web tags and jstl tags are used
by James Livingston (JIRA)
[ https://issues.jboss.org/browse/JBEE-154?page=com.atlassian.jira.plugin.s... ]
James Livingston commented on JBEE-154:
---------------------------------------
I have moved the version to 1.0.3-SNAPSHOT, since some EE 7 changes were done under the 1.0.2-SNAPSHOT number so this reduced confusion.
Since there is no maintenance branch upstream, you would need to push my branch rather than merge a PR, since github doesn't let you create a PR with a new branch.
> ClassCastException in JSPs where spring-web tags and jstl tags are used
> -----------------------------------------------------------------------
>
> Key: JBEE-154
> URL: https://issues.jboss.org/browse/JBEE-154
> Project: JBoss JavaEE Spec APIs
> Issue Type: Bug
> Components: jboss-jsp-api
> Reporter: James Livingston
> Assignee: Shelly McGowan
>
> WFLY-3100 incorporated a fix to the 2.3 version of the JSP APIs, and it would be good to have it in the 2.2 APIs as well.
> There is currently no maintenance branch for the 2.2 APIs, so we would need to create one.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
12 years, 2 months