nuessgens

Results 11 comments of nuessgens

Having exact the same issue. Ironically I created a local WAMP installation because of the following recommendation (from the Plugin-Site) > The best way around this timeout issue is to...

Almost forgot: I fixed it locally by modifiying the method that inserts the plugin-paths (that will be analyzed) into the database. I simply replaced the windows path-seperator (backslashes) with unix...

Wanted to comment on OAuth/OIDC: Personally I'd love to see this feature as I'm currently evaluating Authentik and I think that would be very cool as it can also be...

I know. Therefore sendText is only called by a single thread in my application, too. But the "deadlock"/ block still is occurring. It's the internal Tyrus implementation that is not...

A little update: swapping the lines at https://github.com/eclipse-ee4j/tyrus/blob/f6dfb4749019502c2030848dd48a19950543834c/containers/jdk-client/src/main/java/org/glassfish/tyrus/container/jdk/client/TaskQueueFilter.java#L151-L152 and https://github.com/eclipse-ee4j/tyrus/blob/f6dfb4749019502c2030848dd48a19950543834c/containers/jdk-client/src/main/java/org/glassfish/tyrus/container/jdk/client/TaskQueueFilter.java#L140-L141 fixes the problem for me. What do you think folks is the better fix? * Make the class thread-safe due...

I'll try to create a pull request any time soon (currently I'm a little busy but maybe I manage to create one in the next two weeks) I'll try to...

I guess you have to _flip_ the ByteBuffer in your MessageEncoder before returning it: https://docs.oracle.com/javase/8/docs/api/java/nio/Buffer.html#flip-- Alternatively you could use `ByteBuffer.wrap(message.getMsg())` and return the resulting ByteBuffer instance.

To simulate the Thread Scheduling madness one can add `Thread.sleep()` or `Thread.yield()` between shutting down the executor service and setting it to null: `BaseContainer` ```java public void shutdown() { if...

Furthermore due the RejectedExecutionException `activeClientCounter` is not decremented / `onConnectionTerminated` is never called. Therefore activeClientCounter remains > 0 forever and the auto-cleanup mechanism does not work anymore / exec will...

It seems that the same happens for opcode 0x9 (PING). Or - to be preceise - the exception is thrown for anything other than opcode 0x2 (BINARY) and opcode 0x8...