You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2019/02/11 09:36:00 UTC
[jira] [Commented] (JCR-4414) HTTP 503 Error - Service Unavailable
- Standalone Jar
[ https://issues.apache.org/jira/browse/JCR-4414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764797#comment-16764797 ]
Julian Reschke commented on JCR-4414:
-------------------------------------
bq. the Same issue has been reported earlier and status is showing closed
and the issue number was?
> HTTP 503 Error - Service Unavailable - Standalone Jar
> -----------------------------------------------------
>
> Key: JCR-4414
> URL: https://issues.apache.org/jira/browse/JCR-4414
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jca
> Affects Versions: 2.16.2, 2.14.6, 2.18.0
> Reporter: Debu Paul
> Priority: Major
> Attachments: Actual Error.PNG, Http 500 error.PNG, Up & RUnning.PNG
>
>
> While running this command "java -jar jackrabbit-standalone-2.18.0.jar --port 8085" getting HTTP 500 Error and Jack-rabbit log getting "java.io.FileNotFoundException: jackrabbit-standalone.jar" Error.
> Please note: the Same issue has been reported earlier and status is showing closed. But this issue still persists.
> This same issue is happening for all the jars. Jack-rabbit standalone jar is unable to resolve it automatically. To resolve that issue we need to rename it into "jackrabbit-standalone.jar".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)