You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Dejan Bosanac (JIRA)" <ji...@apache.org> on 2016/05/03 12:51:12 UTC

[jira] [Resolved] (AMQ-6195) Fileserver webapps doesn't works out of the box

     [ https://issues.apache.org/jira/browse/AMQ-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dejan Bosanac resolved AMQ-6195.
--------------------------------
    Resolution: Won't Fix

We removed the fileserver webapp, as it's never been production ready. 

It has been deprecated with [AMQ-5754] and removed with [AMQ-6276]. I think there's a room for the embeddable Java web app that serves this purpose, but it should be properly developed as a separate project (not within message broker).

Users are advised to use proper FTP / file servers for transferring blob messages.

> Fileserver webapps doesn't works out of the box
> -----------------------------------------------
>
>                 Key: AMQ-6195
>                 URL: https://issues.apache.org/jira/browse/AMQ-6195
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Distribution
>    Affects Versions: 5.12.0, 5.12.1, 5.11.3, 5.13.0, 5.12.2, 5.11.4, 5.13.1, 5.12.3
>         Environment: Microsoft Windows 7 32 bits
> Oracle JDK 1.8.0u51
>            Reporter: Nicolas V.
>              Labels: easyfix, newbie, windows
>             Fix For: 5.x
>
>
> Since version 5.11.3 (and maybe 5.11.2 but we can't download any release archive for this version) the fileserver webapp doesn't works out of the box.
> Downloading archive from affected version, extracting it in a folder, and enabling fileserver context (when needed, as only recent release need to enable the context in jetty.xml) without changing anything else. Then we can't use the fileserver (in a browser we have a not found error, and in an application using blobmessage we have error on put method).
> Little hack to solve the problem : replace files (webapps/fileserver/WEB-INF/classes/*) of any version (tested on 5.13.1) with files coming from release v5.11.1 makes the fileserver works again.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)