Process Definitions Statistic API not working

We are using camunda 7.14 and i am trying to use the below API to get the process defintions statistics API as per the below documentation.

Get statistics

When I query the API i get the below result as response.

API End point : http://localhost:8080/rest/process-definition/statistics?failedJobs=false
Response -

{
    "type": "NoSuchMethodError",
    "message": "org.camunda.bpm.engine.impl.ProcessDefinitionStatisticsQueryImpl.unboundedResultList()Ljava/util/List;"
}

When I try debugging the code, I found that there is no method with name unboundedResultList() exists in the class ProcessDefinitionStatisticsQueryImpl.

Similarly i had the same issue when i try to execute the API’s as specified in the below link.

https://docs.camunda.org/manual/7.14/reference/rest/process-definition/get-activity-statistics/

Could you please advice on this?

Hello @ChandruM ,

could it be that you have clashing versions? For example, rest api in 7.18.0 and engine in 7.14.0?

Jonathan

No not really. I did checked my dependencies all Camunda dependencies are 7.14 only.

Hello @ChandruM ,

I have to reproduce but I failed. Which setup do you use? Do you have a distro from us or did you build your own one (using spring-boot for example)?

Jonathan

THis is the dependencies we have used on our pom.


<properties>
		<maven.compiler.target>11</maven.compiler.target>
		<maven.compiler.source>11</maven.compiler.source>
		<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
		<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
		<spring.boot.version>2.6.6</spring.boot.version>
		<camunda.spring.boot.starter.version>7.14.0</camunda.spring.boot.starter.version>
		<togglz.version>3.0.0</togglz.version>
		<maven.surefire.version>2.19.1</maven.surefire.version>
		<powermock.version>2.0.9</powermock.version>
		<camunda.version>7.14.0</camunda.version>
		<glashfish.jersey.version>2.35</glashfish.jersey.version>
	</properties>

<dependencyManagement>
		<dependencies>
			<dependency>
				<groupId>org.springframework.boot</groupId>
				<artifactId>spring-boot-dependencies</artifactId>
				<version>${spring.boot.version}</version>
				<type>pom</type>
				<scope>import</scope>
			</dependency>
			<dependency>
				<groupId>org.camunda.bpm</groupId>
				<artifactId>camunda-bom</artifactId>
				<version>7.14.0</version>
				<scope>import</scope>
				<type>pom</type>
			</dependency>
		</dependencies>
	</dependencyManagement>

	<dependencies>
		<!-- Enable REST API of Camunda -->
		<dependency>
			<groupId>org.camunda.bpm</groupId>
			<artifactId>camunda-engine</artifactId>
			<version>${camunda.version}</version>
		</dependency>

		<dependency>
			<groupId>org.camunda.bpm.dmn</groupId>
			<artifactId>camunda-engine-dmn</artifactId>
			<version>${camunda.version}</version>
		</dependency>

		<dependency>
			<groupId>org.camunda.bpm.springboot</groupId>
			<artifactId>camunda-bpm-spring-boot-starter-webapp</artifactId>
			<version>${camunda.version}</version>
		</dependency>

		<dependency>
			<groupId>org.camunda.bpm.springboot</groupId>
			<artifactId>camunda-bpm-spring-boot-starter-rest</artifactId>
			<version>${camunda.version}</version>
		</dependency>

		<dependency>
			<groupId>org.camunda.bpm</groupId>
			<artifactId>camunda-engine-plugin-spin</artifactId>
			<version>7.14.0</version>
		</dependency>


		<!-- Email dependencies -->
		<dependency>
			<groupId>org.camunda.bpm.extension</groupId>
			<artifactId>camunda-bpm-mail-core</artifactId>
			<version>1.2.0</version>
			<exclusions>
				<exclusion>
					<artifactId>camunda-connect-core</artifactId>
					<groupId>org.camunda.connect</groupId>
				</exclusion>
			</exclusions>
		</dependency>

		<dependency>
			<groupId>org.camunda.bpm.extension.feel.scala</groupId>
			<artifactId>feel-engine-plugin</artifactId>
			<version>1.10.1</version>
		</dependency>

		<dependency>
			<groupId>org.camunda.bpm.springboot</groupId>
			<artifactId>camunda-bpm-spring-boot-starter-rest</artifactId>
			<version>${camunda.spring.boot.starter.version}</version>
			<exclusions>
				<exclusion>
					 <groupId>org.mybatis</groupId>
   					 <artifactId>mybatis</artifactId>
				</exclusion>
				<exclusion>
					 <groupId>org.hibernate</groupId>
   					 <artifactId>hibernate-validator</artifactId>
				</exclusion>
				<exclusion>
					<groupId>org.glassfish.jersey.media</groupId>
					<artifactId>jersey-media-jaxb</artifactId>
				</exclusion>
				<exclusion>
					<groupId>org.springframework</groupId>
					<artifactId>spring-web</artifactId>
				</exclusion>
			</exclusions>
		</dependency>

		<dependency>
			<groupId>org.camunda.bpm.springboot</groupId>
			<artifactId>camunda-bpm-spring-boot-starter-webapp</artifactId>
			<version>${camunda.spring.boot.starter.version}</version>
		</dependency>

		<dependency>
			<groupId>org.camunda.bpm</groupId>
			<artifactId>camunda-engine-plugin-connect</artifactId>
			<version>${camunda.spring.boot.starter.version}</version>
		</dependency>

		<!-- Event based listeners for Camunda -->
		<dependency>
			<groupId>org.camunda.bpm.extension.reactor</groupId>
			<artifactId>camunda-bpm-reactor-spring-starter</artifactId>
			<version>2.1.2</version>
		</dependency>

		<!-- Email dependencies -->
	  <dependency>
			<groupId>org.camunda.bpm.extension</groupId>
			<artifactId>camunda-bpm-mail-core</artifactId>
			<version>1.2.0</version>
		</dependency>

		<dependency>
			<groupId>org.camunda.connect</groupId>
			<artifactId>camunda-connect-connectors-all</artifactId>
			<version>1.2.2</version>
		</dependency>

		<dependency>
			<groupId>org.camunda.bpm</groupId>
			<artifactId>camunda-engine-plugin-connect</artifactId>
			<version>7.14.0</version>
		</dependency>
</dependencies>

Hello @ChandruM ,

it looks like the dependencies have grown over time.

It would first of all recommend to figure out which dependencies are really required and whether there are duplicates.

Then, I would use the IDE tooling to find out whether there are version conflicts in some transitive dependencies.

If there are, you can either exclude the unwanted version or (what I prefer) manage it explicitly.

Then, the error should be resolved.

If not, could you please post the stacktrace appearing on the server side.

Jonathan