argument type mismatch about rqueue HOT 13 CLOSED

Yeah, thanks for the help you saved me a day 👍
I will look for a solution and if I find I will open a PR :)

from rqueue.

Hi @mertkiray
Thanks for reporting issue.
Can you please confirm, if you don't have multiple JobX class in the codebase ?

This issue is likely happening due to the Class.forName is creating different class's object while the listener is expecting different type of object.

Also this can be verified by executing LRANGE command on Redis list rqueue-processing::delayed-queue-job

from rqueue.

@sonus21 I am pretty sure there is no multiple JobX class in the codebase. What can I provide to help you debug the problem?
This is an example entry in the list

{
  "@class": "com.github.sonus21.rqueue.core.RqueueMessage",
  "id": "delayed-queue-job8f333748-763b-4702-bc01-ef5f7255ef5b",
  "queueName": "delayed-queue-job",
  "message": "{\"msg\":\"{\\\"message\\\":\\\"test\\\",\\\"id\\\":\\\"1\\\"}\",\"name\":\"com.octovan.service.redis.queue.JobX\"}",
  "retryCount": null,
  "queuedTime": 1582738630242,
  "processAt": 0,
  "reEnqueuedAt": null,
  "failureCount": 0
}

from rqueue.

I think that it may be due to RedisTemplate defined in RedisUtil.class, any solution to overwrite the redistemplate used in the project to debug?

from rqueue.

No, we can't overwrite that. Can you provide a sample spring code to reproduce this issue?
Also if possible please share spring-messaging and spring-boot versions.

from rqueue.

Let me try to reproduce the issue.

spring-messaging version: 5.2.2.RELEASE
spring-boot versions: 2.2.2.RELEASE

from rqueue.

Hi @sonus21 ,
I was able to reproduce the issue

https://github.com/mertkiray/rqueue-bug

from rqueue.

Thanks, Let me check why this error is occurring. Something strange, I'll update you once I find the root cause.

from rqueue.

Sure waiting for your reply ^^

from rqueue.

Can you please remove devtool dependency and try? This is the culprit, I'm not sure exactly why that's causing this issue. We might have to raise bug to the spring team.

Working Dependencies

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
	<modelVersion>4.0.0</modelVersion>
	<parent>
		<groupId>org.springframework.boot</groupId>
		<artifactId>spring-boot-starter-parent</artifactId>
		<version>2.2.2.RELEASE</version>
		<relativePath/> <!-- lookup parent from repository -->
	</parent>
	<groupId>test.rqueue</groupId>
	<artifactId>demo</artifactId>
	<version>0.0.1-SNAPSHOT</version>
	<name>demo</name>
	<description>Demo project for Spring Boot</description>

	<properties>
		<java.version>1.8</java.version>
	</properties>

	<dependencies>
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-web</artifactId>
		</dependency>
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-test</artifactId>
			<scope>test</scope>
		</dependency>
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-actuator</artifactId>
		</dependency>
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-data-redis</artifactId>
		</dependency>
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-security</artifactId>
		</dependency>
		<dependency>
			<groupId>redis.clients</groupId>
			<artifactId>jedis</artifactId>
		</dependency>
		<dependency>
			<groupId>com.github.sonus21</groupId>
			<artifactId>rqueue-spring-boot-starter</artifactId>
			<version>1.3-RELEASE</version>
		</dependency>
	</dependencies>

</project>

from rqueue.

When I removed dev-tools, it worked! :)
But this is definitely an issue with dev-tools, how should we proceed?

from rqueue.

If you don't need devtools then you can remove and in production it's very unlikely you will be using. So this error should not come but you need to test in some test environment to confirm the theory.

Other people are also facing similar issues neo4j/neo4j-ogm#743

from rqueue.

@mertkiray
I can confirm this is a bug in Rqueue lib code. It will be fixed in version 2.0.1 due to release over this weekend. This is happening due to Class.forName uses different class loaders while dev tools provide different class loaders.

from rqueue.