Results 1 to 2 of 2

Thread: GWT 2.8.0 deployment error

  1. #1
    Sencha Premium User
    Join Date
    Sep 2015
    Posts
    6

    Default GWT 2.8.0 deployment error

    I am trying to deploy my GWT app with GXT 4.0.2 to a Weblogic 12.2.1 server. I get the following error.
    I don't get the error with GWT 2.7.0 everything else being identical(except the module xml file).
    Anyone else see this error? I read that GWT 2.8.0 implements websockets. Is this issue related to that?
    I would appreciate any help. Thanks.

    Ramesh


    Caused by: javax.servlet.ServletException: Not running on Jetty, JSR-356 support unavailable
    at org.eclipse.jetty.websocket.jsr356.server.deploy.WebSocketServerContainerInitializer.onStartup(WebSocketServerContainerInitializer.java:146)
    at weblogic.servlet.internal.WebAppServletContext.initContainerInitializer(WebAppServletContext.java:1420)
    at weblogic.servlet.internal.WebAppServletContext.initContainerInitializers(WebAppServletContext.java:1359)
    at weblogic.servlet.internal.WebAppServletContext.initContainerInitializers(WebAppServletContext.java:1340)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1906)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3063)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1830)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:875)
    at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:360)
    at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:356)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
    at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:138)

  2. #2
    Sencha - Forum Administrator
    Join Date
    Sep 2017
    Posts
    1,006
    Answers
    5

    Default

    Hi Ramesh,

    Sorry for the delay in responding. I have shared this with the support team and asked that they follow up with you to provide some assistance. Thank you for your patience!

    Michele

Similar Threads

  1. ADB Geolocation Error after Sench Touch app build and deployment
    By ronaldoneal in forum Sencha Touch 2.x: Q&A
    Replies: 2
    Last Post: 12 Apr 2012, 11:31 AM
  2. [FIXED] Deployment notification no longer lists deployment path
    By azuroff in forum Sencha Architect 2.x: Bugs
    Replies: 2
    Last Post: 20 Feb 2012, 8:25 AM
  3. parseNamespace error occurs when preparing application for deployment
    By parky128 in forum Sencha Touch 2.x: Discussion
    Replies: 7
    Last Post: 14 Feb 2012, 11:17 AM
  4. Replies: 5
    Last Post: 26 Sep 2011, 1:07 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •