Version 10 always gives 500 error

[mmccool]

After installing the binary release following the instructions, localhost:8080 always gives a 500 error. Here is an example (all other URLs give the same response);

HTTP ERROR: 500
Problem accessing /api.json. Reason:

javax.servlet.http.HttpServletRequest.isAsyncStarted()Z

Powered by Jetty://

[vcharpenay]

This is probably due to incompatibilities with Java 9+. Two solutions:

• run the TDir with Java 8
• build the project and run the .war in directory-servlet/build/libs in a J2EE container (I tested with the nightly release of Jetty, 9.4.12-v20180830)

[mmccool]

I was running Java 8, version 1.8, as instructed. Are you using OpenJDK or Oracle Java?

[hasbel]

I am also having this issue while running Java 8. Only downgrading to TDir v9 seems to solve the problem.

[MatthiasLaeufer]

I'm also struggeling with this version. Java-Version: Oracle jre1.8.0_191

[karaleina]

I have the same problem. I use Java 1.8 as is specified in README.md.

[6d77]

The release package of 0.10.0 has two versions of javax.servlet.api in the classpath:

• javax.servlet-api-3.1.0.jar
• servlet-api-2.5.jar

Both are also mentioned in the classpath in the directory-app startup script (just a snippet):

... :$APP_HOME/lib/servlet-api-2.5.jar:$APP_HOME/lib/javax.servlet-api-3.1.0.jar: ...

This causes the outdated classes from 2.5 to be loaded instead of the actually needed classed from 3.1.0

Just removing the servlet-api-2.5.jar from the lib directory and the classpath solves this issue.

[karaleina]

@6d77, I used your help, but it looks like 10 version still behaves differently than version 9 and is still incompatible with Swagger documentation.

I created Postman client based on api.json file and tried to list available things (expecting empty list) or register a new thing. First gave me 405 ERROR and second gave me 500 ERROR. Exactly the same requests work with version 9.

[6d77]

Please create separate issues for that. This issue is just about the isAsyncStarted() problem.

And yes, you're right, it is also my experience that the Swagger API and the implementation are not in line.