Issue to run the Server side in both examples "examples/chat/service" and "examples/helloworld/service" #57
Replies: 5 comments 2 replies
-
Hi @bantunes82, I want to acknowledge that I've seen your note. Actually, I've seen that message, but it didn't seem to interfere with the actual running of the examples, so I haven't looked into it yet. In the most recent version, I've made it possible to run 1) without an SSL connection; 2) with a one-way SSL connection, or 3) with a two-way SSL connection. I added the bash script configure (in the main directory) which will copy the appropriate files to the standalone/configuration directory. For example, configure oneway helloworld Right now, it just works with helloworld. I'll try to clean things up this week. That probably answers your question about using it in production. -Ron |
Beta Was this translation helpful? Give feedback.
-
By the way, @bantunes82, I'm curious about your interest in this project. It sounds like something you would be interested in using. Of course, we would be delighted to hear any more feedback you have. Also, in case you haven't seem it, there is some relatively new documentation in the docs/guide directory. |
Beta Was this translation helpful? Give feedback.
-
Hey @bantunes82, I believe pull request #59 fixes the complaint about the log file. |
Beta Was this translation helpful? Give feedback.
-
Hi @ronsigal the error message disappear, but the GRPC service is not being registered.
Response: Just to clarify this issue is happening only with the actual version in master, that right now it is 0.0.5-SNAPSHOT. |
Beta Was this translation helpful? Give feedback.
-
Hi @bantunes82, Right now the examples are a bit chaotic, and I need to clean them up. What I've been doing is running the helloworld example manually.
There are three options, depending on what kind of SSL connection you want:
So, you could run configure as
Similarly, you could run the client
These all work in the most recent version. I had to add examples/helloworld/client/src/main/resources/client.keystore.pem I haven't worked on chat yet. Sorry for the confusion. |
Beta Was this translation helpful? Give feedback.
-
Hi guys, I am trying to run both examples "examples/chat/service" and "examples/helloworld/service" in my local computer and I am having this issue when Wildfly is starting
12:58:20,088 INFO [org.wildfly.extension.grpc] (ServerService Thread Pool -- 25) WFLYGRPC0003: gRPC server for wildfly-grpc-examples-chat-service-0.0.4-SNAPSHOT.jar listening on localhost:9555 12:58:20,139 WARN [org.jboss.modules.define] (ServerService Thread Pool -- 25) Failed to define class io.netty.util.internal.logging.Log4J2Logger in Module "io.netty.netty-common" version 4.1.84.Final from local module loader @3e14c16d (finder: local module finder @3c989952 (roots: /home/bruno/projects/wildfly-grpc-feature-pack/examples/chat/service/target/server/modules,/home/bruno/projects/wildfly-grpc-feature-pack/examples/chat/service/target/server/modules/system/layers/base)): java.lang.NoClassDefFoundError: Failed to link io/netty/util/internal/logging/Log4J2Logger (Module "io.netty.netty-common" version 4.1.84.Final from local module loader @3e14c16d (finder: local module finder @3c989952 (roots: /home/bruno/projects/wildfly-grpc-feature-pack/examples/chat/service/target/server/modules,/home/bruno/projects/wildfly-grpc-feature-pack/examples/chat/service/target/server/modules/system/layers/base))): org/apache/logging/log4j/spi/ExtendedLoggerWrapper at java.base/java.lang.ClassLoader.defineClass1(Native Method) at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1017) at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:350) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:482) at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:276) at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:79) at org.jboss.modules.Module.loadModuleClass(Module.java:765) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:192) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) at io.netty.netty-common@4.1.84.Final//io.netty.util.internal.logging.Log4J2LoggerFactory.newInstance(Log4J2LoggerFactory.java:33) at io.netty.netty-common@4.1.84.Final//io.netty.util.internal.logging.InternalLoggerFactory.useLog4J2LoggerFactory(InternalLoggerFactory.java:76) at io.netty.netty-common@4.1.84.Final//io.netty.util.internal.logging.InternalLoggerFactory.newDefaultFactory(InternalLoggerFactory.java:47) at io.netty.netty-common@4.1.84.Final//io.netty.util.internal.logging.InternalLoggerFactory.getDefaultFactory(InternalLoggerFactory.java:111) at io.netty.netty-common@4.1.84.Final//io.netty.util.internal.logging.InternalLoggerFactory.getInstance(InternalLoggerFactory.java:134) at io.netty.netty-common@4.1.84.Final//io.netty.util.internal.logging.InternalLoggerFactory.getInstance(InternalLoggerFactory.java:127) at io.netty.netty-common@4.1.84.Final//io.netty.util.internal.PlatformDependent.<clinit>(PlatformDependent.java:81) at io.netty.netty-common@4.1.84.Final//io.netty.util.AsciiString.<init>(AsciiString.java:223) at io.netty.netty-common@4.1.84.Final//io.netty.util.AsciiString.<init>(AsciiString.java:210) at io.netty.netty-common@4.1.84.Final//io.netty.util.AsciiString.cached(AsciiString.java:1401) at io.netty.netty-common@4.1.84.Final//io.netty.util.AsciiString.<clinit>(AsciiString.java:48) at org.wildfly.grpc-dependency//io.grpc.netty.Utils.<clinit>(Utils.java:78) at org.wildfly.grpc-dependency//io.grpc.netty.NettyServerBuilder.<clinit>(NettyServerBuilder.java:84) at org.wildfly.extension.grpc@0.0.4-SNAPSHOT//org.wildfly.extension.grpc.GrpcServerService.startServer(GrpcServerService.java:350) at org.wildfly.extension.grpc@0.0.4-SNAPSHOT//org.wildfly.extension.grpc.GrpcServerService.lambda$start$0(GrpcServerService.java:331) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990) at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348) at java.base/java.lang.Thread.run(Thread.java:829) at org.jboss.threads@2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513)
Do you have any idea, what could be ? this problem is happening only with the version 0.0.4-SNAPSHOT
The other question is this feature is ready to be used in production ?
Thanks and regards
Beta Was this translation helpful? Give feedback.
All reactions