Jump to content

[Inactive] 404 even though the war is deployed


Amoss

Recommended Posts

The first time you deploy a war with a new file name, it takes until the next Apache restart to actually start working, and shows a 404 until then.

 

Have you waited a few hours after deploying?

Link to comment
Share on other sites

Well, this war is old and the name is the same. It was on "deployed" mode when the problem occurred so I re-deployed it just in case but to no avail. Even now, few hours later, it gives 404, you can check yourself with the link above.

Edited by Amoss
Link to comment
Share on other sites

Ofcourse it did, maybe something bad happened to it and that is the problem?

I understand correctly that I need to re-upload it? I already made changes to it so I don't have the same war now

Any chance the file can be restored from somewhere?

Edited by Amoss
Link to comment
Share on other sites

Linux doesn't have a recycle bin. When you delete or overwrite something it's gone. Since the server is constantly writing and rewriting to the hard drive recovery tools won't work because they can only see deleted info that hasn't been overwritten. The version on the server was uploaded on May 11th. You'll need to check your own hard drive for older versions.

Link to comment
Share on other sites

Here's what is deployed on the server. Note there is no index.jsp or anything so that's why you're seeing the 404 error:

stockdi1_MyHelioServlet
.
├── META-INF
│   ├── MANIFEST.MF
│   ├── maven
│   │   └── com.resty
│   │       └── resty
│   │           ├── pom.properties
│   │           └── pom.xml
│   └── war-tracker
└── WEB-INF
    ├── classes
    │   └── com
    │       └── resty
    │           └── resty
    │               ├── Resty$1.class
    │               ├── Resty$2.class
    │               ├── Resty$3.class
    │               ├── Resty$4.class
    │               └── Resty.class
    ├── lib
    │   ├── activation-1.1.1.jar
    │   ├── aopalliance-repackaged-2.5.0-b32.jar
    │   ├── hk2-api-2.5.0-b32.jar
    │   ├── hk2-locator-2.5.0-b32.jar
    │   ├── hk2-utils-2.5.0-b32.jar
    │   ├── javassist-3.20.0-GA.jar
    │   ├── javax.annotation-api-1.2.jar
    │   ├── javax.inject-2.5.0-b32.jar
    │   ├── javax.ws.rs-api-2.0.1.jar
    │   ├── jersey-client-2.25.1.jar
    │   ├── jersey-common-2.25.1.jar
    │   ├── jersey-container-servlet-2.25.1.jar
    │   ├── jersey-container-servlet-core-2.25.1.jar
    │   ├── jersey-guava-2.25.1.jar
    │   ├── jersey-media-jaxb-2.25.1.jar
    │   ├── jersey-server-2.25.1.jar
    │   ├── json-20170516.jar
    │   ├── mail-1.4.7.jar
    │   ├── mysql-connector-java-6.0.6.jar
    │   ├── osgi-resource-locator-1.0.1.jar
    │   └── validation-api-1.1.0.Final.jar
    └── web.xml

10 directories, 31 files
Link to comment
Share on other sites

I don't see any index.jsp on my local project as well, I only have 1 class that serves my needs. Was there any change in helio that made the existence of index.jsp mandatory?

What should be in that file?

I did upload the file in 11th may and it worked since, suddenly few days ago I started getting this 404.

Link to comment
Share on other sites

  • 1 month later...

I work with Eclipse and it has some functions for my mobile app.

I developed a mobile app using vscode (in Ionic) and this war is my server side.

It also works with rested extension of Firefox but when I upload and deployed it to Helios, it doesn't even knows it's there.

 

I didn't change anything in my project setup, it looks like Helios started expecting something from the WAR and I don't know what it is.

post-120484-0-40337000-1530945287_thumb.png

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...