Little error on graniteds-reference-guide.pdf

13 views
Skip to first unread message

maven dev

unread,
Dec 5, 2011, 4:22:37 AM12/5/11
to Granite Data Services Forum
hello,

FYI there is a little error on this reference PDF (page 144 on the
table).

For GlassFish 3.x and Tomcat 7.x/Jetty 8.x package for servlet
gravity class is org.granite.gravity.async whereas the real package is
org.granite.gravity.servlet3.

I'm using 2.3 docs maybe this has changed from prior version.

cheers

Olivier

maven dev

unread,
Dec 5, 2011, 6:15:27 AM12/5/11
to Granite Data Services Forum
but....

when I'm using org.granite.gravity.servlet3.GravityAsyncServlet with
GlassFish 3+ I receive a javax.servlet.ServletException :


[#|2011-12-05T12:06:28.859+0100|WARNING|glassfish3.1.1|
javax.enterprise.system.container.web.com.sun.enterprise.web|
_ThreadID=118;_ThreadName=Thread-2;|
StandardWrapperValve[GravityServlet]: PWC1406: Servlet.service() for
servlet GravityServlet threw exception
javax.servlet.ServletException: Asynchronous requests are not
supported with this servlet. Please check your web.xml
at
org.granite.gravity.servlet3.GravityAsyncServlet.doPost(GravityAsyncServlet.java:
57)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at
org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:
1539)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:
281)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:
175)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:
655)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:
595)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:98)
at
com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:
91)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:
162)
at
org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:
330)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:
231)
at
com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:
174)
at
com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:
828)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:
725)
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:722)

using org.granite.gravity.generic.GravityGenericServlet solve this
problem.

Cannot use org.granite.gravity.servlet3.GravityAsyncServlet with
GlassFish ?

Thanks

Olivier

William Draï

unread,
Dec 5, 2011, 6:55:51 AM12/5/11
to gran...@googlegroups.com
You have to add <async-supported>true</async-supported> to your servlet descriptor in web.xml. And ensure that your web.xml has a header with version 3.0:

maven dev

unread,
Dec 5, 2011, 8:06:40 AM12/5/11
to Granite Data Services Forum
Very nice it works like a charm now !

Thanks a lot.

For my information, with
org.granite.gravity.generic.GravityGenericServlet it's mentioned
that's there is no asynchronous
support for this class. What does it mean exactly ?

Does it mean that :

- it's impossible for a not connected consumer to receive a producer
message in a future connection ?
- sending a message will block in any way consumers...?
- what else...?

Thanks for clarification

Olivier

Reply all
Reply to author
Forward
0 new messages