openwms / org.openwms.common.comm Goto Github PK

After running mvn clean build the build is generated smoothly. But once you try to run the application we are getting the below-mentioned error.

C:\Users\nazim\OpenWMS\org.openwms.common.comm\target>java -Dowms.driver.server.port=30001 -jar tcpip-driver-exec.jar
2022-03-04 20:33:10.251 INFO [27656/1] - o.h.validator.internal.util.Version : HV000001: Hibernate Validator 6.2.0.Final
. .
|- ,-. ,-. , . ,-. ,-| ,-. . . , ,-. ,-.
| | | | / | | | | | | | | / |-' |
' -' |-' ' ' |-' -^ ' ' ' `-' '
| |
' '
2022-03-04 20:33:12.058 INFO [27656/1] - org.openwms.common.comm.DriverStarter : No active profile set, falling back to default profiles: default
2022-03-04 20:33:14.245 INFO [27656/1] - o.a.coyote.http11.Http11NioProtocol : Initializing ProtocolHandler ["http-nio-30008"]
2022-03-04 20:33:14.246 INFO [27656/1] - o.apache.catalina.core.StandardService : Starting service [Tomcat]
2022-03-04 20:33:14.247 INFO [27656/1] - org.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/9.0.56]
2022-03-04 20:33:14.308 INFO [27656/1] - o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext
2022-03-04 20:33:14.942 INFO [27656/1] - BOOT : Driver instantiated in [N/A] mode
2022-03-04 20:33:15.368 INFO [27656/1] - BOOT : -- w/ ServiceLayerAspect
2022-03-04 20:33:15.370 INFO [27656/1] - BOOT : -- w/ MeasuredAspect
2022-03-04 20:33:15.371 INFO [27656/1] - BOOT : -- w/ IntegrationLayerAspect
2022-03-04 20:33:15.372 INFO [27656/1] - BOOT : -- w/ PresentationLayerAspect
2022-03-04 20:33:15.472 WARN [27656/1] - ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.springframework.boot.autoconfigure.web.servlet.WebMvcAutoConfiguration$EnableWebMvcConfiguration': Unsatisfied dependency expressed through method 'setConfigurers' parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.ameba.http.ctx.CallContextWebMvcConfiguration': Unsatisfied dependency expressed through field 'callContextProvider'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'traceableCallContextProvider' defined in class path resource [org/ameba/http/ctx/sleuth/TraceableCallContextConfiguration.class]: Unsatisfied dependency expressed through method 'traceableCallContextProvider' parameter 0; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'org.springframework.cloud.sleuth.Tracer' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {}
2022-03-04 20:33:15.489 INFO [27656/1] - o.apache.catalina.core.StandardService : Stopping service [Tomcat]
2022-03-04 20:33:15.536 ERROR [27656/1] - o.s.b.d.LoggingFailureAnalysisReporter :

APPLICATION FAILED TO START

Description:

Parameter 0 of method traceableCallContextProvider in org.ameba.http.ctx.sleuth.TraceableCallContextConfiguration required a bean of type 'org.springframework.cloud.sleuth.Tracer' that could not be found.

Action:

Consider defining a bean of type 'org.springframework.cloud.sleuth.Tracer' in your configuration.

Is it that I am doing something wrong or is there an error?

Thanks!

• Client/Server
• Multiple handles per instance
• group general config on top

Each socket configuration must be configurable with a Tenant name that is then used to identify the driver instance with surrounding systems

In a distributed environment the driver shall pick up runtime configuration, like port config, from a centralized configuration server. But during development it is more convenient to start the driver with a default configuration and without the need of surrounding infrastructure services

I set the profile as ASYNCHRONUS, I executed ping to address 127.0.0.1 and port 300008. PacketSender doesn't receive any erros, but the server doesn't loggs any information. Where is the problem? Can I find any documenation and guide how to operate this program?

Communication to subsystems MUST work over a single TCP/IP socket connection bidirectionally.