Hi,
at first glance "Request URI is too large" suggest that asadmin sends
HTTP request with URI, which exceeds limits, which is not normal.
Is it possible for you to check if there is the same problem on
Glassfish 3.1.2.2?
You can also try to increase the buffer-size like:
$asadmin set
configs.config.default-config.network-config.transports.transport.tcp.buffer-size-bytes=16384
WBR,
Alexey.
On 09/06/2012 09:27 PM, forums_at_java.net wrote:
> OK, executed stop domain and this time I get the following response:
> ./asadmin stop-domain java.net.SocketException: Unexpected end of file
> from
> server and the log file shows:
> [#|2012-09-06T15:50:47.381-0400|SEVERE|glassfish3.1.1|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=21;_ThreadName=Thread-2;|GRIZZLY0039:
>
> Request URI is too large. java.nio.BufferOverflowException at
> com.sun.grizzly.tcp.http11.InternalInputBuffer.fill(InternalInputBuffer.java:765)
>
> at
> com.sun.grizzly.tcp.http11.InternalInputBuffer.parseRequestLine(InternalInputBuffer.java:402)
>
> at
> com.sun.grizzly.http.ProcessorTask.parseRequest(ProcessorTask.java:861) at
>
> com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:692) at
> com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1019) at
> com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225)
>
> at
> com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
>
> at
> com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
>
> at
> com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
> at
> com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
> at
> com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
>
> at
> com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
>
> at com.sun.grizzly.ContextTask.run(ContextTask.java:71) at
> com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
>
> at
> com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
>
> at java.lang.Thread.run(Thread.java:662) |#]
> [#|2012-09-06T15:50:47.381-0400|SEVERE|glassfish3.1.1|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=21;_ThreadName=Thread-2;|GRIZZLY0051:
>
> ProcessorTask exception. java.lang.NullPointerException at
> java.nio.CharBuffer.put(CharBuffer.java:896) at
> com.sun.enterprise.web.accesslog.CommonAccessLogFormatterImpl.appendRequestInfo(CommonAccessLogFormatterImpl.java:203)
>
> at
> com.sun.enterprise.web.accesslog.CommonAccessLogFormatterImpl.appendLogEntry(CommonAccessLogFormatterImpl.java:133)
>
> at
> com.sun.enterprise.web.accesslog.CombinedAccessLogFormatterImpl.appendLogEntry(CombinedAccessLogFormatterImpl.java:68)
>
> at
> com.sun.enterprise.web.PEAccessLogValve.postInvoke(PEAccessLogValve.java:592)
>
> at
> com.sun.enterprise.web.VirtualServer$2.onParsingError(VirtualServer.java:1698)
>
> at
> com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:709) at
> com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1019) at
> com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225)
>
> at
> com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
>
> at
> com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
>
> at
> com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
> at
> com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
> at
> com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
>
> at
> com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
>
> at com.sun.grizzly.ContextTask.run(ContextTask.java:71) at
> com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
>
> at
> com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
>
> at java.lang.Thread.run(Thread.java:662) |#] The server isn't really hung
> though because it continues to service other requests just fine. I ran
> jstack, but there are too many threads to include here. I don't see
> anything
> all that interesting in the stack trace. Is there any particular
> thread that
> I should be examining?
>
> --
>
> [Message sent by forum member 'slominskir']
>
> View Post: http://forums.java.net/node/889712
>
>