[JBoss JIRA] (WFLY-2950) jboss-cli using https-remoting: command not executed if certificate is unrecognised
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2950?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2950:
-----------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1026418|https://bugzilla.redhat.com/show_bug.cgi?id=1026418] from POST to MODIFIED
> jboss-cli using https-remoting: command not executed if certificate is unrecognised
> -----------------------------------------------------------------------------------
>
> Key: WFLY-2950
> URL: https://issues.jboss.org/browse/WFLY-2950
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: CLI, Domain Management
> Affects Versions: 8.0.0.Final
> Environment: Windows 7 Pro
> Reporter: Darren Jones
> Assignee: Darran Lofthouse
> Labels: cli, shutdown
> Fix For: 8.0.1.Final
>
>
> When using the https management interface from jboss-cli, commands passed with a command line option (such as --command=:shutdown) are not executed if the server certificate is unrecognised - even if accepting the certificate [T]emporarily or [P]ermenantly.
> It appears to be due to the CommandContextImpl.handleSSLFailure() method, which calls error("Unable to connect..."). The error() method sets the exitCode to 1. So, when CliLauncher.processCommands() subsequently runs, it sees that the cmdCtx.exitCode is 1 and ignores any commands.
> I guess the handleSSLFailure needs to reset the exitCode to 0 if the user chooses [T] or [P].
--
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
10 years, 10 months
[JBoss JIRA] (WFLY-3134) Upgrade Infinispan to 6.0.2.Final
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/WFLY-3134?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero commented on WFLY-3134:
---------------------------------------
There might be more reasons to not update, but license is not the only change.
Infinispan 6.0.1.Final used JBoss Marshaller 1.3.18.GA
Infinispan 6.0.2.Final used JBoss Marshaller 1.4.4.Final and has a couple of lines changed to address a compatibility issue with this Marshaller version
WildFly (master as of today) is using Marshaller 1.4.3.Final; since there are no other differences between Infinispan 6.0.1 and 6.0.2 I think it would be safer to actually do the upgrade of both components.
> Upgrade Infinispan to 6.0.2.Final
> ---------------------------------
>
> Key: WFLY-3134
> URL: https://issues.jboss.org/browse/WFLY-3134
> Project: WildFly
> Issue Type: Component Upgrade
> Security Level: Public(Everyone can see)
> Components: Clustering
> Affects Versions: 8.0.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> 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
10 years, 10 months
[JBoss JIRA] (JBWEB-290) Optimize string literals inside jsp expressions
by Andrig Miller (JIRA)
[ https://issues.jboss.org/browse/JBWEB-290?page=com.atlassian.jira.plugin.... ]
Andrig Miller commented on JBWEB-290:
-------------------------------------
In terms of being responsible for this code? If so, we can take ownership of it (the performance team), I have no problem with that at all. It's actually a fairly simple change, and its also been incorporated into upstream with Undertow as well. So, Stuart is also familiar with the change.
> Optimize string literals inside jsp expressions
> ------------------------------------------------
>
> Key: JBWEB-290
> URL: https://issues.jboss.org/browse/JBWEB-290
> Project: JBoss Web
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Tomcat
> Affects Versions: JBossWeb-3.0.0.Final
> Reporter: John O'Hara
> Assignee: Remy Maucherat
> Fix For: JBossWeb-7.4.0.GA
>
>
> After setting genStringAsCharArray=true, we continue to see StringBuilder concatenating string literals for each jsp request for some of our jsp pages; instead of creating a static char[].
> This occurs when a string literal is included in a jsp expression, e.g.;
> <%="<INPUT type=\"hidden\" name=\"name\" value=\"" + obj.getName() + "\">"%>
> Is it possible to identify string literals inside expressions during the tokenization phase of parsing jsp pages in apache jasper and treat them as text nodes so that the apache jasper generator can apply the same optimizations as string literals outside the jsp expression?
--
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
10 years, 10 months