[jboss-jira] [JBoss JIRA] (WFLY-4709) Invalid Last-Modified header

[Davy De Durpel (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072696#comment-13072696 ] 

Davy De Durpel commented on WFLY-4709:
--------------------------------------

Until now the issue only occured on our customers' production environment.  We haven't been able to reproduce it on their test environments.
Our customer does not allow me to update WildFly in the production environment at this moment.  By the end of this week I will deploy a patch of our applet  
If this workaround works than we are allowed to do a (temporary) update to WildFly 9 CR1.  I can't say when exactly this will be done but I think that it will be in the second half of june.
One other important remarkt though.  When the issue occurs it's not for all the requests. Some are good and some are bad.  This seems to indicate that the issue is linked to a web socket (thread). 

> Invalid Last-Modified header
> ----------------------------
>
>                 Key: WFLY-4709
>                 URL: https://issues.jboss.org/browse/WFLY-4709
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web (Undertow)
>    Affects Versions: 8.2.0.Final
>         Environment: Windows Server 2008
>            Reporter: Davy De Durpel
>            Assignee: Stuart Douglas
>
> After 2 months of use Wildfly suddenly started to send an invalid Last-Modified header.  Normally it should be in the format:
> Fri, 10 Oct 2014 19:35:55 GMT
> But sometimes it sends:
> Fri, 10 Oct 2014 21:35:55 CEST
> Or even:
> Fri, 10 Oct 2014 21:35:55 CEST GMT
> The URLConnection.getLastModified() method cannot handle these 2 last formats as it uses an old and deprecated Date.parse(..) method.
> A restart of the service fixes the issue for a few hours after which it reappears but not for all requests.  We switched back to JBoss 7.1.1 and the issue disappeared completely so we're pretty sure that it's a bug in WildFly.  No updates were done to windows, java and Wildfly that could have triggered the issue.  We noticed the issue because we have a java applet running at the customer side.  We use URLConnection to download some files based on the last modification date of these files.  Browsers don't seem to be affected by the issue.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)