The server is sending a 302 that is unexpected.
Either you are not hitting the CometdServlet, or you have a filter
that redirects before, or something like that.
Simon
--
http://bordet.blogspot.com
---
Finally, no matter how good the architecture and design are,
to deliver bug-free software with optimal performance and reliability,
the implementation technique must be flawless. Victoria Livschitz
<filter> <filter-name>continuation</filter-name> <filter-class>org.eclipse.jetty.continuation.ContinuationFilter</filter-class> </filter> <filter-mapping> <filter-name>continuation</filter-name> <url-pattern>/cometd/*</url-pattern> </filter-mapping>
I also checked that there are no other filters. How can I check if the CometdServlet is loaded and the cometd services are up and running?
Thanks.
Sorry if I ask, but are you pointing to the correct URL ?
Sure you are using "https" and not "http" as scheme ?
Nothing in CometD sends a 302 so it must be something else that is
being hit before... perhaps the redirection to the confidential port
by Tomcat ?