Re: HTTP request status text is changed


Ben Hale <bhale@...>
 

The Java Buildpack creates a very complex command to start applications (since it needs to manage the JVM’s memory space within the container’s memory space). Therefore, it detects standard artifact types listed in the documentation[1] and builds the command based on that. For self-executable JARs, detection is based on the Java standard `Main-Class` key in the `META-INF/MANFIEST.MF`[2]. You’ll need to remember that when you push the WAR or JAR to Cloud Foundry, it is expanded and presented to the buildpack in an exploded form. We read files off the filesystem and execute the application in that layout. So, for example, there is no `testId.war` on the filesystem in the container, only the contents of the WAR that was pushed.


-Ben Hale
Cloud Foundry Java Experience



[1]: https://github.com/cloudfoundry/java-buildpack#additional-documentation
[2]: https://github.com/cloudfoundry/java-buildpack/blob/master/docs/container-java_main.md

On May 3, 2016, at 11:25, Stanley Shen <meteorping(a)gmail.com> wrote:

Can you have a try with the attached jettty.zip.txt in previous reply to see if you reproduce it?
It's used to simulate my APP, you can just download it and change to jetty.zip and unzip it.
There is a manifest file along with a war file and jetty runner.
You can push it to a bosh lite VM and you should see the issue.

In this sample, actually there is nothing special configured for jetty.
we just run it like "java -jar jetty-runner.jar --port $PORT testId.war" in the container.

My APP is quite large and has many dependencies, which make it not easy to post somewhere.

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.