java.nio.BufferOverflowException: null

Hello, When using WsWebSocketContainer.connectToServer with ClientEndpointConfig I get java.nio.BufferOverflowException in case the HTTP headers are more than 4k. The used ByteBuffer is 4k:

Re: context root with relative path

Hi, Have you decided if the proposed fix make since? If the corner case is :/, then it can be handled as well, not to remove the slash in case the previous char is :. Best Regards, Dimitar On Thu, Apr 21, 2016 at 7:12 PM, Leo Donahue wrote: > On Apr 21, 2016 10:38 AM,

Re: context root with relative path

System.out.println(new File("C:").exists()); prints true, so I guess it works okay. On Wed, Apr 20, 2016 at 3:31 PM, Konstantin Kolinko <knst.koli...@gmail.com> wrote: > 2016-04-19 22:42 GMT+03:00 Mark Thomas <ma...@apache.org>: > > On 19/04/2016 19:38, Dimit

Re: context root with relative path

s". I think that with java.io.File APIs there's nothing that can give the needed behaviour (the getCanonicalPath will resolve symlinks) Best Regards, Dimitar Valov On Tue, Apr 19, 2016 at 10:42 PM, Mark Thomas <ma...@apache.org> wrote: > On 19/04/2016 19:38, Dimitar Valov wrote:

context root with relative path

n accomplish the correct thing. Do you think that is something that can be fixed? Maybe the above is not the best approach, however it's the least invasive. Best Regards Dimitar Valov

Re: Tomcat's JNDI lookups fail if java.naming.factory.object property is specified

On Thu, Nov 5, 2015 at 1:51 PM, Dimitar Valov <dimitar.va...@gmail.com> wrote: > Hello, > > Exceptions such as this are found in the logs when > java.naming.factory.object is present > 04-Nov-2015 15:40:51.560 SEVERE [main] > org.apache.catalina.realm.UserDatabaseRealm.startIn