01-07-2019 02:19 PM
I still have no idea why I get the error, the environment was deployed with the pre-release version and it worked fine. I also tested the jetty server independently without GMSC and it works, connects ok with the client.
Appreciate all suggestions, ideas on the issue
01-08-2019 07:04 PM
Just some update on the issue. I now have the GMSC version 16.5.308.1 (the last GMSC update 3 pre-release version) and my websocket server is working just fine. In addition, we use port 7020 for communicating; however, before starting the server we have a function to check to make sure we grab the free port (starting from 7020).
So, it looks to me that some changes in the core GMSC from the latest pre-release version to the official version that block my server.
Appreciate all suggestions and insights,
01-09-2019 12:30 AM
I compared the dependency list of both versions and your issue is related to a version conflict.
The integrated commons-logging version of 16.5.320.2 defines the servlet-api 2.3 as required (see https://issues.apache.org/jira/browse/LOGGING-113) but Jetty needs a newer version of that.
That's a common issue which is well kown under the term "JAR Hell". To avoid such cases it would be important that you as a plugin developer ensure that your plugin only use dependencies which are compatible with the existing GMSC dependencies.
In case of the servlet-api is that very hard to achieve because the servlet-api 2.3 is a very old and even Jetty 6 (from 2010) uses a newer version.
Therefore I checked the commons-logging release notes and I'm confident that we can force an upgrade to a commons-logging version which fixes this issue.
Please open a new Support Ticket and we provide you a new GMSC setup which uses commons-logging 1.2.
In the meanwhile, just delete the following and try if this solves your issue
01-09-2019 08:18 AM
Removing the 3 jar solves the problem.
Is there any side effect by doing this?
01-09-2019 08:29 AM
The better way would be the request of a new GMSC setup but in the end there should be no side effect if you repair your installation before the next upgrade.
The commons-logging developers just used the wrong property at the pom.xml:
01-09-2019 08:36 AM
We have to provide GMSC 2018 u3 to our customer this Friday.
We will give them a procedure to delete the 3 jars (to make the plugin works).
When the next release will comes we will give them the procedure where they have to repair the installation prior to install the new release.