Webhook Triggering failure

Camunda 8 Topics Discussion & Questions
, ,
1

Hi All,

I am trying to trigger a Webhook from Postman, but I am getting the below exception in the broker cmd:

I use the the self-managed Camunda platform and the desktop modeler.

I appreciate your help.

URL:
http://localhost:26500/inbound/FishingLocations

Exception:
INFO: Transport failed
io.netty.handler.codec.http2.Http2Exception: Unexpected HTTP/1.x request: POST /inbound/FishingLocations
at io.netty.handler.codec.http2.Http2Exception.connectionError(Http2Exception.java:109)
at io.netty.handler.codec.http2.Http2ConnectionHandler$PrefaceDecoder.readClientPrefaceString(Http2ConnectionHandler.java:317)
at io.netty.handler.codec.http2.Http2ConnectionHandler$PrefaceDecoder.decode(Http2ConnectionHandler.java:247)
at io.netty.handler.codec.http2.Http2ConnectionHandler.decode(Http2ConnectionHandler.java:453)
at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:529)
at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:468)
at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:290)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:440)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:1583)

UPDATE:
When I tried using curl in cmd it tried to connect but close this connection immediately:

curl --verbose --location “http://localhost:26500/inbound/FishingLocations” --data “{"fish": "Pike","status": "Fish Person","id": "Yasmeen"}”

  • Trying localhost:26500…
  • Connected to localhost port 26500 (#0)

POST /inbound/FishingLocations HTTP/1.1
Host: localhost:26500
User-Agent: curl/8.0.1
Accept: /
Content-Length: 56
Content-Type: application/x-www-form-urlencoded

  • Received HTTP/0.9 when not allowed
  • Closing connection 0
    curl: (1) Received HTTP/0.9 when not allowed
2

@Niall @Ingo_Richtsmeier @jonathan.lukas

Can you please help?

3

Hello @yasmeenhesham ,

it looks like you send the connector request to zeebe itself - instead you should use a connectors-bundle.

It is contained in the docker-compose of Camunda Platform:

You will be able to trigger a webhook when sending the request towards localhost:8085/inbound/FishingLocations

I hope this helps

Jonathan

4

Hello @jonathan.lukas

Let me explain to you what I have done. Firstly, I followed the manual installation here Manual installation on local machine | Camunda 8 Docs

and in the part of connectors, I have made a spring boot application instead of using command as mentioned, and then I have downloaded the connector runtime bundle and added its dependency in my project. Am I misunderstood the documentation?

If there is any configuration must be made in the broker application.yaml file regarding the connectors , or in the spring boot properties?

application.yaml file
application.yaml (5.9 KB)

spring boot properties file
zeebe.client.broker.gateway-address=localhost:26500

zeebe.client.security.plaintext=true

Sorry, if my questions are trivial, but I am newbie in Camunda and I am trying to explore it.

Thanks for your support

5

Hello @yasmeenhesham ,

it looks like you are trying bundle everything to one application.

In fact, the easiest way to getting everything up and running is by using the linked docker-compose from my previous response.

I would consider the manual installation a “last resort” if you have no possibility to use docker at all… this will require you to set up multiple separate java applications and let them interact via the host machine network.

Please let me know if setting up the platform using docker-compose works for you.

Jonathan

1 Like
6

Hello @jonathan.lukas

Thanks for your response.

Currently, I couldn’t use docker-compose, so the manual installation is my only way for now.

Could you please share with me tutorial, documentation… to help me (if any) as I don’t know what is wrong with my steps and this part not clear for me in the documentation shared before?

Thanks again for your support.
Yasmeen

7

Hello @jonathan.lukas

Now, it seems that the Webhook connector is activated and triggered successfully, but the process not started.

Spring boot Console
. ____ _ __ _ _
/\ / ’ __ _ () __ __ _ \ \ \
( ( )__ | '_ | '| | ’ / ` | \ \ \
\/ )| |)| | | | | || (| | ) ) ) )
’ || .__|| ||| |_, | / / / /
=========||==============|/=////
:: Spring Boot :: (v3.1.5)

2023-11-22T17:01:30.713+02:00 INFO 18736 — [ main] com.ejada.CamundaAppApplication : Starting CamundaAppApplication using Java 17.0.6 with PID 18736 (E:\Enablement\Camunda\Workspace\camunda-app\target\classes started by yhesham in E:\Enablement\Camunda\Workspace\camunda-app)
2023-11-22T17:01:30.718+02:00 INFO 18736 — [ main] com.ejada.CamundaAppApplication : No active profile set, falling back to 1 default profile: “default”
2023-11-22T17:01:31.475+02:00 INFO 18736 — [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data JPA repositories in DEFAULT mode.
2023-11-22T17:01:31.492+02:00 INFO 18736 — [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 7 ms. Found 0 JPA repository interfaces.
2023-11-22T17:01:31.496+02:00 INFO 18736 — [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data JPA repositories in DEFAULT mode.
2023-11-22T17:01:31.541+02:00 INFO 18736 — [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 44 ms. Found 1 JPA repository interfaces.
2023-11-22T17:01:32.208+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘io.camunda.zeebe.spring.client.annotation.processor.AnnotationProcessorConfiguration’ of type [io.camunda.zeebe.spring.client.annotation.processor.AnnotationProcessorConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.211+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘io.camunda.connector.runtime.outbound.OutboundConnectorRuntimeConfiguration’ of type [io.camunda.connector.runtime.outbound.OutboundConnectorRuntimeConfiguration$$SpringCGLIB$$0] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.273+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘zeebe.client-io.camunda.zeebe.spring.client.properties.ZeebeClientConfigurationProperties’ of type [io.camunda.zeebe.spring.client.properties.ZeebeClientConfigurationProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.279+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘io.camunda.zeebe.spring.client.configuration.ZeebeClientAllAutoConfiguration’ of type [io.camunda.zeebe.spring.client.configuration.ZeebeClientAllAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.282+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘io.camunda.zeebe.spring.client.configuration.ExecutorServiceConfiguration’ of type [io.camunda.zeebe.spring.client.configuration.ExecutorServiceConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.283+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘org.springframework.boot.actuate.autoconfigure.metrics.export.prometheus.PrometheusMetricsExportAutoConfiguration’ of type [org.springframework.boot.actuate.autoconfigure.metrics.export.prometheus.PrometheusMetricsExportAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.290+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘management.prometheus.metrics.export-org.springframework.boot.actuate.autoconfigure.metrics.export.prometheus.PrometheusProperties’ of type [org.springframework.boot.actuate.autoconfigure.metrics.export.prometheus.PrometheusProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.293+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘prometheusConfig’ of type [org.springframework.boot.actuate.autoconfigure.metrics.export.prometheus.PrometheusPropertiesConfigAdapter] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.297+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘collectorRegistry’ of type [io.prometheus.client.CollectorRegistry] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.298+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘org.springframework.boot.actuate.autoconfigure.metrics.MetricsAutoConfiguration’ of type [org.springframework.boot.actuate.autoconfigure.metrics.MetricsAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.299+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘micrometerClock’ of type [io.micrometer.core.instrument.Clock$1] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.341+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘prometheusMeterRegistry’ of type [io.micrometer.prometheus.PrometheusMeterRegistry] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.359+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘zeebeClientThreadPool’ of type [io.camunda.zeebe.spring.client.jobhandling.ZeebeClientExecutorService] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.363+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘commandExceptionHandlingStrategy’ of type [io.camunda.zeebe.spring.client.jobhandling.DefaultCommandExceptionHandlingStrategy] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.365+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘io.camunda.zeebe.spring.client.CamundaAutoConfiguration’ of type [io.camunda.zeebe.spring.client.CamundaAutoConfiguration$$SpringCGLIB$$0] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.367+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘io.camunda.connector.runtime.OutboundConnectorsAutoConfiguration’ of type [io.camunda.connector.runtime.OutboundConnectorsAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.577+02:00 INFO 18736 — [ main] org.camunda.feel.FeelEngine : Engine created. [value-mapper: CompositeValueMapper(List(org.camunda.feel.impl.JavaValueMapper@77524ca7)), function-provider: io.camunda.connector.feel.FeelConnectorFunctionProvider@3c7279a5, clock: SystemClock, configuration: {externalFunctionsEnabled: false}]
2023-11-22T17:01:32.763+02:00 INFO 18736 — [ main] org.camunda.feel.FeelEngine : Engine created. [value-mapper: CompositeValueMapper(List(org.camunda.feel.impl.JavaValueMapper@d8835af)), function-provider: io.camunda.connector.feel.FeelConnectorFunctionProvider@16681017, clock: SystemClock, configuration: {externalFunctionsEnabled: false}]
2023-11-22T17:01:32.778+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘objectMapper’ of type [com.fasterxml.jackson.databind.json.JsonMapper] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.779+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘zeebeJsonMapper’ of type [io.camunda.zeebe.client.impl.ZeebeObjectMapper] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.779+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘io.camunda.zeebe.spring.client.configuration.ZeebeActuatorConfiguration’ of type [io.camunda.zeebe.spring.client.configuration.ZeebeActuatorConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.796+02:00 INFO 18736 — [ main] i.c.z.s.c.a.MicrometerMetricsRecorder : Enabling Micrometer based metrics for spring-zeebe (available via Actuator)
2023-11-22T17:01:32.796+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘micrometerMetricsRecorder’ of type [io.camunda.zeebe.spring.client.actuator.MicrometerMetricsRecorder] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.798+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘jobWorkerManager’ of type [io.camunda.zeebe.spring.client.jobhandling.JobWorkerManager] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.804+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘outboundConnectorFactory’ of type [io.camunda.connector.runtime.core.outbound.DefaultOutboundConnectorFactory] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.808+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘defaultSecretProvider’ of type [io.camunda.connector.runtime.env.SpringEnvironmentSecretProvider] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.810+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘springSecretProviderAggregator’ of type [io.camunda.connector.runtime.core.secret.SecretProviderAggregator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.813+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘outboundConnectorManager’ of type [io.camunda.connector.runtime.outbound.lifecycle.OutboundConnectorManager] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.815+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘annotationProcessor’ of type [io.camunda.connector.runtime.outbound.lifecycle.OutboundConnectorAnnotationProcessor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.818+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘deploymentPostProcessor’ of type [io.camunda.zeebe.spring.client.annotation.processor.ZeebeDeploymentAnnotationProcessor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.820+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘propertyBasedZeebeWorkerValueCustomizer’ of type [io.camunda.zeebe.spring.client.properties.PropertyBasedZeebeWorkerValueCustomizer] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.823+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘zeebeWorkerPostProcessor’ of type [io.camunda.zeebe.spring.client.annotation.processor.ZeebeWorkerAnnotationProcessor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.824+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘io.camunda.connector.runtime.inbound.InboundConnectorRuntimeConfiguration’ of type [io.camunda.connector.runtime.inbound.InboundConnectorRuntimeConfiguration$$SpringCGLIB$$0] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.826+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘io.camunda.connector.runtime.inbound.lifecycle.InboundConnectorLifecycleConfiguration’ of type [io.camunda.connector.runtime.inbound.lifecycle.InboundConnectorLifecycleConfiguration$$SpringCGLIB$$0] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.835+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘springInboundConnectorFactory’ of type [io.camunda.connector.runtime.core.inbound.DefaultInboundConnectorFactory] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:32.836+02:00 INFO 18736 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘inboundConnectorAnnotationProcessor’ of type [io.camunda.connector.runtime.inbound.lifecycle.InboundConnectorAnnotationProcessor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-22T17:01:33.144+02:00 INFO 18736 — [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 8082 (http)
2023-11-22T17:01:33.156+02:00 INFO 18736 — [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat]
2023-11-22T17:01:33.157+02:00 INFO 18736 — [ main] o.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/10.1.15]
2023-11-22T17:01:33.301+02:00 INFO 18736 — [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext
2023-11-22T17:01:33.302+02:00 INFO 18736 — [ main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 2530 ms
2023-11-22T17:01:33.573+02:00 INFO 18736 — [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Starting…
2023-11-22T17:01:33.936+02:00 INFO 18736 — [ main] com.zaxxer.hikari.pool.HikariPool : HikariPool-1 - Added connection ConnectionID:1 ClientConnectionId: a5d729f5-7e33-4225-a09f-57edc31d8fcd
2023-11-22T17:01:33.938+02:00 INFO 18736 — [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Start completed.
2023-11-22T17:01:33.984+02:00 INFO 18736 — [ main] o.hibernate.jpa.internal.util.LogHelper : HHH000204: Processing PersistenceUnitInfo [name: default]
2023-11-22T17:01:34.047+02:00 INFO 18736 — [ main] org.hibernate.Version : HHH000412: Hibernate ORM core version 6.2.13.Final
2023-11-22T17:01:34.051+02:00 INFO 18736 — [ main] org.hibernate.cfg.Environment : HHH000406: Using bytecode reflection optimizer
2023-11-22T17:01:34.423+02:00 INFO 18736 — [ main] o.s.o.j.p.SpringPersistenceUnitInfo : No LoadTimeWeaver setup: ignoring JPA class transformer
2023-11-22T17:01:34.489+02:00 WARN 18736 — [ main] org.hibernate.orm.deprecation : HHH90000025: SQLServerDialect does not need to be specified explicitly using ‘hibernate.dialect’ (remove the property setting and it will be selected by default)
2023-11-22T17:01:35.511+02:00 INFO 18736 — [ main] o.h.e.t.j.p.i.JtaPlatformInitiator : HHH000489: No JTA platform available (set ‘hibernate.transaction.jta.platform’ to enable JTA platform integration)
2023-11-22T17:01:35.515+02:00 INFO 18736 — [ main] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit ‘default’
2023-11-22T17:01:35.768+02:00 WARN 18736 — [ main] ocalVariableTableParameterNameDiscoverer : Using deprecated ‘-debug’ fallback for parameter name resolution. Compile the affected code with ‘-parameters’ instead or avoid its introspection: com.ejada.workers.SaveAbsenceRequestWorker
2023-11-22T17:01:35.770+02:00 INFO 18736 — [ main] z.s.c.a.p.ZeebeWorkerAnnotationProcessor : Configuring 1 Zeebe worker(s) of bean ‘saveAbsenceRequestWorker’: [ZeebeWorkerValue{type=‘SaveAbsenceRequest’, name=‘saveAbsenceRequestWorker#saveAbsenceRequest’, timeout=-1, maxJobsActive=-1, requestTimeout=-1, pollInterval=-1, autoComplete=true, fetchVariables=, enabled=true, methodInfo=io.camunda.zeebe.spring.client.bean.MethodInfo@36995784}]
2023-11-22T17:01:35.812+02:00 WARN 18736 — [ main] JpaBaseConfiguration$JpaWebConfiguration : spring.jpa.open-in-view is enabled by default. Therefore, database queries may be performed during view rendering. Explicitly configure spring.jpa.open-in-view to disable this warning
2023-11-22T17:01:36.009+02:00 INFO 18736 — [ main] org.camunda.feel.FeelEngine : Engine created. [value-mapper: CompositeValueMapper(List(org.camunda.feel.impl.JavaValueMapper@6f959640)), function-provider: io.camunda.connector.feel.FeelConnectorFunctionProvider@5fdebe73, clock: SystemClock, configuration: {externalFunctionsEnabled: false}]
2023-11-22T17:01:36.059+02:00 INFO 18736 — [ main] z.s.c.c.ZeebeClientProdAutoConfiguration : Creating ZeebeClient using ZeebeClientConfiguration [ZeebeClientConfigurationProperties{broker=Broker{gatewayAddress=‘localhost:26500’, keepAlive=PT45S}, cloud=io.camunda.zeebe.spring.client.properties.ZeebeClientConfigurationProperties$Cloud@2b08772d, worker=Worker{maxJobsActive=32, threads=1, defaultName=‘zeebe.client.worker.name’, defaultType=‘null’, override={}}, message=Message{timeToLive=PT1H}, security=Security{plaintext=true, overrideAuthority=‘null’, certPath=‘null’}, job=Job{timeout=PT5M, pollInterval=PT0.1S}, interceptors=, requestTimeout=PT10S, scheduledExecutorService=java.util.concurrent.ScheduledThreadPoolExecutor@125ace20[Running, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0], ownsJobWorkerExecutor=true}]
2023-11-22T17:01:37.054+02:00 INFO 18736 — [ main] o.s.b.a.e.web.EndpointLinksResolver : Exposing 1 endpoint(s) beneath base path ‘/actuator’
2023-11-22T17:01:37.133+02:00 INFO 18736 — [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 8082 (http) with context path ‘’
2023-11-22T17:01:37.145+02:00 INFO 18736 — [ main] i.c.z.s.c.jobhandling.JobWorkerManager : . Starting Zeebe worker: ZeebeWorkerValue{type=‘SaveAbsenceRequest’, name=‘saveAbsenceRequestWorker#saveAbsenceRequest’, timeout=-1, maxJobsActive=-1, requestTimeout=-1, pollInterval=-1, autoComplete=true, fetchVariables=, enabled=true, methodInfo=io.camunda.zeebe.spring.client.bean.MethodInfo@36995784}
2023-11-22T17:01:37.162+02:00 INFO 18736 — [ main] com.ejada.CamundaAppApplication : Started CamundaAppApplication in 6.964 seconds (process running for 8.278)
2023-11-22T17:01:37.296+02:00 INFO 18736 — [ scheduling-1] i.c.c.r.i.i.ProcessDefinitionImporter : Detected changes in process definitions
2023-11-22T17:01:37.297+02:00 INFO 18736 — [ scheduling-1] i.c.c.r.i.i.ProcessDefinitionImporter : . 7 newly deployed
2023-11-22T17:01:37.297+02:00 INFO 18736 — [ scheduling-1] i.c.c.r.i.i.ProcessDefinitionImporter : . . Process_1v5x7vb, version 13
2023-11-22T17:01:37.297+02:00 INFO 18736 — [ scheduling-1] i.c.c.r.i.i.ProcessDefinitionImporter : . . Process_0ox6k5i, version 2
2023-11-22T17:01:37.297+02:00 INFO 18736 — [ scheduling-1] i.c.c.r.i.i.ProcessDefinitionImporter : . . FishingExample, version 6
2023-11-22T17:01:37.297+02:00 INFO 18736 — [ scheduling-1] i.c.c.r.i.i.ProcessDefinitionImporter : . . Process_11lcl9t, version 9
2023-11-22T17:01:37.297+02:00 INFO 18736 — [ scheduling-1] i.c.c.r.i.i.ProcessDefinitionImporter : . . template-human-task-tutorial-1brcupt, version 1
2023-11-22T17:01:37.297+02:00 INFO 18736 — [ scheduling-1] i.c.c.r.i.i.ProcessDefinitionImporter : . . Process_0o31ggp, version 7
2023-11-22T17:01:37.297+02:00 INFO 18736 — [ scheduling-1] i.c.c.r.i.i.ProcessDefinitionImporter : . . send-email, version 2
2023-11-22T17:01:37.297+02:00 INFO 18736 — [ scheduling-1] i.c.c.r.i.i.ProcessDefinitionImporter : . 0 replaced with new version
2023-11-22T17:01:37.297+02:00 INFO 18736 — [ scheduling-1] i.c.c.r.i.i.ProcessDefinitionImporter : . 0 deleted
2023-11-22T17:01:37.986+02:00 INFO 18736 — [ scheduling-1] org.camunda.feel.FeelEngine : Engine created. [value-mapper: CompositeValueMapper(List(org.camunda.feel.impl.JavaValueMapper@64bb2113)), function-provider: io.camunda.connector.feel.FeelConnectorFunctionProvider@126a8f1c, clock: SystemClock, configuration: {externalFunctionsEnabled: false}]
2023-11-22T17:01:38.047+02:00 INFO 18736 — [ scheduling-1] org.camunda.feel.FeelEngine : Engine created. [value-mapper: CompositeValueMapper(List(org.camunda.feel.impl.JavaValueMapper@7663cba0)), function-provider: io.camunda.connector.feel.FeelConnectorFunctionProvider@1c56e996, clock: SystemClock, configuration: {externalFunctionsEnabled: false}]
2023-11-22T17:01:38.075+02:00 INFO 18736 — [ scheduling-1] org.camunda.feel.FeelEngine : Engine created. [value-mapper: CompositeValueMapper(List(org.camunda.feel.impl.JavaValueMapper@4783109a)), function-provider: io.camunda.connector.feel.FeelConnectorFunctionProvider@41d7c82c, clock: SystemClock, configuration: {externalFunctionsEnabled: false}]

BPMN
fishing-process.bpmn (7.3 KB)

Postman
URL: http://localhost:8082/inbound/FishingLocations
Request:
{
“fish”: “Pike”,
“status”: “Fish Person”,
“id”: “Yasmeen”
}
Response: 200 ok
{
“fish”: “Pike”,
“status”: “Fish Person”,
“id”: “Yasmeen”
}
Note: My Spring boot application that has Bundle runtime connector & Webhook connector dependencies runs on port 8082

Do you have any idea regarding this issue?

Thanks,
Yasmeen

8

Hello @yasmeenhesham ,

this also depends on the implementation of the connector. Do you have the process model available?

Jonathan

9

Hello @jonathan.lukas

Kindly find the Process attached
fishing-process.bpmn (7.0 KB)

Also, please can you check the previous reply?

Many Thanks

10

Hello @yasmeenhesham ,

as the webhook refers to “FishingSpot”, I would call it using…

http://localhost:8082/inbound/FishingSpot.

I hope this helps

Jonathan

11

Hello @jonathan.lukas

Thanks for your reply.

My Webhook ID is FishingLocations as shown below in screenshot, not FishingSpot

image

Also, please keep in mind that I use the Desktop Modeler, not the web Modeler.

Thanks for your help.
Yasmeen

12

Hello @yasmeenhesham ,

the BPMN file you provided contains the following extension elements for the Start Event:

  <bpmn:extensionElements>
        <zeebe:properties>
          <zeebe:property name="inbound.type" value="io.camunda:webhook:1" />
          <zeebe:property name="inbound.subtype" value="ConfigurableInboundWebhook" />
          <zeebe:property name="inbound.context" value="FishingSpot" />
          <zeebe:property name="inbound.shouldValidateHmac" value="disabled" />
          <zeebe:property name="inbound.activationCondition" value="=(&#10;  request.body.status = &#34;Fish Person&#34;&#10;)" />
          <zeebe:property name="inbound.variableMapping" value="={&#10;  fish : request.body.fish&#10;}" />
        </zeebe:properties>
      </bpmn:extensionElements>

I used the Desktop Modeler, but I had to download a very old version of the webhook element template. Please make sure to use the latest one. It can be found here.

Then, please verify you are running the correct version of your BPMN file.

Jonathan