We have recently migrated the JBoss-AS-7.1 to JBoss-eap-6.1 for supporting the web-socket connection for our application and then we have deployed all the modules to the eap server.
There is no changes in the web module (war packaging) which is working fine(all static files are loading properly in the browser) in the JBoss-AS-7.1
and not working ( some important files are not loading into the browser ) in the JBoss-eap-6.1.
This issue is not raising if the GUI code is not supporting web-socket connection and
Issue is raising if the GUI code is supporting web-socket connection.
Aws Instance Type : m3.xlarge
OS : Ubuntu 13.04 (GNU/Linux 3.8.0-19-generic x86_64)
GUI is using the web-socket connection.
Native libraries are enabled.
For html & jsp file :
Resource interpreted as Document but transferred with MIME type application/octet-stream
For css :
Resource interpreted as Stylesheet but transferred with MIME type application/octet-stream
Resource interpreted as Script but transferred with MIME type application/octet-stream
In that case, browser is about to download the file instead of loading.
And some times it is showing error as below in browser console.
GET http://domain/file.css net::ERR_INVALID_CHUNKED_ENCODING
GET http://domain/file.js net::ERR_INVALID_CHUNKED_ENCODING
For websockets you might want to go with EAP 6.3 which properly implements WS.
Impl before 6.3 was limited only to one connector and was mostly experimental.
There is beta version of EAP 6.3 available for download, with .GA coming soon.