3 Replies Latest reply on Aug 1, 2015 8:52 AM by andrejt

    WildFly 9.0 with open BIMserver deployed: WebSocket Error

    andrejt

      I tried to run BIMserver within the WildFly 9.0. The .war file is deployed without errors, but with some (I think non-critical) warnings. The server launches with the set-up page. When I enter my new user details and confirm I got the "WebSocket error".
      Screenshot is here: Dropbox - Screenshot 2015-07-24 11.32.31.png

       

      WildFly log is here:

      Herango:bin andrejt$ /bin/bash standalone.sh

      JBoss Bootstrap Environment

      JBOSS_HOME: /Users/andrejt/Projects/Programiranje/wildfly-9.0.0.Final

      JAVA: java

      JAVA_OPTS: -server -XX:+UseCompressedOops -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

      Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
      11:26:10,441 INFO  org.jboss.modules JBoss Modules version 1.4.3.Final
      11:26:12,529 INFO  org.jboss.msc JBoss MSC version 1.2.6.Final
      11:26:12,580 INFO  org.jboss.as WFLYSRV0049: WildFly Full 9.0.0.Final (WildFly Core 1.0.0.Final) starting
      11:26:13,334 INFO  org.jboss.as.controller.management-deprecated WFLYCTL0028: Attribute 'job-repository-type' in the resource at address '/subsystem=batch' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
      11:26:13,343 INFO  org.jboss.as.controller.management-deprecated WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
      11:26:14,038 INFO  org.jboss.as.server WFLYSRV0039: Creating http management service using socket-binding (management-http)
      11:26:14,053 INFO  org.xnio XNIO version 3.3.1.Final
      11:26:14,061 INFO  org.xnio.nio XNIO NIO Implementation Version 3.3.1.Final
      11:26:14,082 INFO  org.jboss.as.security WFLYSEC0002: Activating Security Subsystem
      11:26:14,082 WARN  org.jboss.as.txn WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
      11:26:14,087 INFO  org.wildfly.extension.io WFLYIO001: Worker 'default' has auto-configured to 16 core threads with 128 task threads based on your 8 available processors
      11:26:14,090 INFO  org.jboss.as.security WFLYSEC0001: Current PicketBox version=4.9.2.Final
      11:26:14,101 INFO  org.jboss.as.jsf WFLYJSF0007: Activated the following JSF Implementations: [main]
      11:26:14,101 INFO  org.jboss.as.clustering.infinispan WFLYCLINF0001: Activating Infinispan subsystem.
      11:26:14,135 INFO  org.jboss.as.naming WFLYNAM0001: Activating Naming Subsystem
      11:26:14,144 INFO  org.jboss.as.webservices WFLYWS0002: Activating WebServices Extension
      11:26:14,146 INFO  org.wildfly.extension.undertow WFLYUT0003: Undertow 1.2.8.Final starting
      11:26:14,146 INFO  org.wildfly.extension.undertow WFLYUT0003: Undertow 1.2.8.Final starting
      11:26:14,160 INFO  org.jboss.as.connector WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.4.Final)
      11:26:14,165 INFO  org.jboss.as.connector.subsystems.datasources WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
      11:26:14,180 INFO  org.jboss.as.connector.deployers.jdbc WFLYJCA0018: Started Driver service with driver-name = h2
      11:26:14,265 INFO  org.jboss.as.naming WFLYNAM0003: Starting Naming Service
      11:26:14,265 INFO  org.jboss.as.mail.extension WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
      11:26:14,266 INFO  org.jboss.remoting JBoss Remoting version 4.0.9.Final
      11:26:14,357 INFO  org.wildfly.extension.undertow WFLYUT0014: Creating file handler for path /Users/andrejt/Projects/Programiranje/wildfly-9.0.0.Final/welcome-content
      11:26:14,382 INFO  org.wildfly.extension.undertow WFLYUT0012: Started server default-server.
      11:26:14,394 INFO  org.wildfly.extension.undertow WFLYUT0018: Host default-host starting
      11:26:14,469 INFO  org.wildfly.extension.undertow WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080
      11:26:14,581 INFO  org.jboss.as.connector.subsystems.datasources WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
      11:26:14,682 INFO  org.jboss.as.server.deployment.scanner WFLYDS0013: Started FileSystemDeploymentService for directory /Users/andrejt/Projects/Programiranje/wildfly-9.0.0.Final/standalone/deployments
      11:26:14,685 INFO  org.jboss.as.server.deployment WFLYSRV0027: Starting deployment of "bimserver-1.4.0-2015-07-20.war" (runtime-name: "bimserver-1.4.0-2015-07-20.war")
      11:26:14,772 INFO  org.jboss.ws.common.management JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Final
      11:26:17,995 WARN  org.jboss.as.server.deployment WFLYSRV0059: Class Path entry jsr-275-1.0-beta-2.jar in /content/bimserver-1.4.0-2015-07-20.war/WEB-INF/lib/geoapi-2.3-M1.jar does not point to a valid jar for a Class-Path reference.
      11:26:17,997 WARN  org.jboss.as.server.deployment WFLYSRV0059: Class Path entry jsr-275-1.0-beta-2.jar in /content/bimserver-1.4.0-2015-07-20.war/WEB-INF/lib/geoapi-pending-2.3-M1.jar does not point to a valid jar for a Class-Path reference.
      11:26:18,005 WARN  org.jboss.as.server.deployment WFLYSRV0059: Class Path entry jaxb-api-2.2.12-b140109.1041.jar in /content/bimserver-1.4.0-2015-07-20.war/WEB-INF/lib/jaxb-core-2.2.10-b140310.1920.jar does not point to a valid jar for a Class-Path reference.
      11:26:18,006 WARN  org.jboss.as.server.deployment WFLYSRV0059: Class Path entry istack-commons-runtime-2.19.jar in /content/bimserver-1.4.0-2015-07-20.war/WEB-INF/lib/jaxb-core-2.2.10-b140310.1920.jar does not point to a valid jar for a Class-Path reference.
      11:26:18,006 WARN  org.jboss.as.server.deployment WFLYSRV0059: Class Path entry txw2-2.2.10-b140310.1920.jar in /content/bimserver-1.4.0-2015-07-20.war/WEB-INF/lib/jaxb-core-2.2.10-b140310.1920.jar does not point to a valid jar for a Class-Path reference.
      11:26:18,006 WARN  org.jboss.as.server.deployment WFLYSRV0059: Class Path entry jaxb-core.jar in /content/bimserver-1.4.0-2015-07-20.war/WEB-INF/lib/jaxb-impl-2.2.10-b140310.1920.jar does not point to a valid jar for a Class-Path reference.
      11:26:18,007 WARN  org.jboss.as.server.deployment WFLYSRV0059: Class Path entry jaxb-core.jar in /content/bimserver-1.4.0-2015-07-20.war/WEB-INF/lib/jaxb-xjc-2.2.10-b140310.1920.jar does not point to a valid jar for a Class-Path reference.
      11:26:18,007 WARN  org.jboss.as.server.deployment WFLYSRV0059: Class Path entry jaxb-impl.jar in /content/bimserver-1.4.0-2015-07-20.war/WEB-INF/lib/jaxb-xjc-2.2.10-b140310.1920.jar does not point to a valid jar for a Class-Path reference.
      11:26:18,552 WARN  org.jboss.as.dependency.private WFLYSRV0018: Deployment "deployment.bimserver-1.4.0-2015-07-20.war" is using a private module ("org.apache.cxf.impl:main") which may be changed or removed in future versions without notice.
      11:26:18,552 WARN  org.jboss.as.dependency.private WFLYSRV0018: Deployment "deployment.bimserver-1.4.0-2015-07-20.war" is using a private module ("org.apache.cxf.impl:main") which may be changed or removed in future versions without notice.
      11:26:18,739 WARN  org.jboss.as.ee WFLYEE0007: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to an exception (enable DEBUG log level to see the cause)
      11:26:33,973 INFO  javax.enterprise.resource.webcontainer.jsf.config Initializing Mojarra 2.2.11-jbossorg-1 20150505-1501 for context '/bimserver-1.4.0-2015-07-20'
      11:26:40,235 INFO  org.wildfly.extension.undertow WFLYUT0021: Registered web context: /bimserver-1.4.0-2015-07-20
      11:26:40,262 INFO  org.jboss.as.server WFLYSRV0010: Deployed "bimserver-1.4.0-2015-07-20.war" (runtime-name : "bimserver-1.4.0-2015-07-20.war")
      11:26:40,340 INFO  org.jboss.as WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
      11:26:40,341 INFO  org.jboss.as WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
      11:26:40,341 INFO  org.jboss.as WFLYSRV0025: WildFly Full 9.0.0.Final (WildFly Core 1.0.0.Final) started in 30128ms - Started 284 of 465 services (221 services are lazy, passive or on-demand)

      Can you advice me how to solve the problem?

      Best regards,
      Andrej

        • 1. Re: WildFly 9.0 with open BIMserver deployed: WebSocket Error
          ctomc

          From log everything looks fine.

           

          Are you maybe running behind proxy server which doesn't support web sockets?

           

          Just btw, you jvm options should be bit different given that you are running on JDK8.

          JAVA_OPTS: -server -XX:+UseCompressedOops -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

          i would at least change it to:

          -server -Xms128m -Xmx768m  -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

          not that it has anything to do with your original problem.

          • 2. Re: WildFly 9.0 with open BIMserver deployed: WebSocket Error
            andrejt

            Hi Tomaž,

            thanks for your ideas.

            I don't use proxy on any of my networks. The behaviour is the same inside 3 tested networks.

            I modified my jvm options as you recommended.

            Problem still the same.

            Are there any web socket tests available for WildFly? However I understand that WildFly is "web socket ready"

            Are there any new ideas?

            • 3. Re: WildFly 9.0 with open BIMserver deployed: WebSocket Error
              andrejt

              Hi Tomaž,

              the error log console in my Safari browser could also be useful to find solution:

               

              Screenshot 2015-08-01 14.48.02.png