Spring-websocket | Spring整合websocket实现即时通讯 | Websocket library

TL;DR

Build and keep the JDKs executor and shut down the executor when finished.

Details:

stack smashing detected usually indicates a NullReferenceException in C# code.

Set COMPlus_EnableAlternateStackCheck environment variable to 1 before running your app to see full stack trace (this works for .NET Core 3.0 and later).

https://ignite.apache.org/docs/latest/net-specific/net-troubleshooting#stack-smashing-detected-dotnet-terminated

I have okhttp3 and logging-interceptor 4.7.2 versions. I have java.lang.NoSuchMethodError: okhttp3.internal.Platform.log

It is a Dependency issue, You are using :

1. okhttp-4.7.2
2. logging-interceptor-4.7.2
3. okhttp-digest-2.0

And Runtime dependency of okhttp-digest-2.0 is okhttp-4.0.1

Maven Repo: https://mvnrepository.com/artifact/com.burgstaller/okhttp-digest/2.0

So now you have two different versions of same library

1.okhttp-4.0.1 from okhttp-digest-2.0

2.okhttp-4.7.2

There was a change in log function(Which is what error is saying NoSuchMethodError:okhttp3.internal.Platform.log) we can see in the image

Solutions:

1. You Can Update version of okhttp-digest which can work with okhttp-4.7.2
2. You could exclude the okhttp dependency from okhttl-digest if you're not using the features relying on it.

jetty-websocket-client-api supports both.

Based on error log snippet, I could see that the error is related to the deadlock in the DB transactions. I think Artifactory is running with the default derby DB. The below error log snippet tells that there was deadlock situation in Derby,

Caused by: org.apache.derby.iapi.error.StandardException: A lock could not be obtained due to a deadlock, cycle of locks and waiters is: Lock : ROW, NODES, (2975,6) Waiting XID : {230127895, S} , APP, SELECT * FROM nodes WHERE repo = ? AND node_path = ? AND depth = ? Granted XID : {230127897, X} Lock : ROW, NODES, (991,272) Waiting XID : {230127897, S} , APP, SELECT * FROM nodes WHERE repo = ? AND node_path = ? AND depth = ? Granted XID : {230127895, X}

I had a similar JenkinFile which deploys Artifacts to Artifactory and never faced this issue. I believe a simple restart of Artifactory should be enough to remove the Derby DB from the deadlock state.

Looks like you're successfully initializing the bean, but not doing anything with the result. To be precise, calling the method:

I found the reason by myself. Though there might be many issues with 'clientinbounchannel', in my case It was just a simple problem caused by difference of versions between spring framework dependencies added in pom.xml. Especially 'spring-messaging'. So if anyone encountered the same issue of mine or any other, please check your pom.xml once again just in case.

As @Mark pointed out, the codebase containing the source for the TomcatWebSocketTestServer is under the standard maven test source path so is unlikely to be published anywhere. However, the source code can be viewed in github along with the source code for other web socket test servers.

Hopefully this should give you a guide to what you would need to implement yourself for this to work.

EDIT: I know SO guidelines suggest posting code snippets rather than links, however this Spring Framework repo is unlikely to be removed anytime soon and the source is also (obviously) copyright protected and I did not want to post a copy, or snippets of it here.

Try to create a fat jar which contains all the dependencies and classes.

Update build.gradle script to this given below :