Styjun

Why is the design of haulage companies so “special”?

Lied on resume at previous job

What does it exactly mean if a random variable follows a distribution

Information to fellow intern about hiring?

How would photo IDs work for shapeshifters?

What are the advantages and disadvantages of running one shots compared to campaigns?

Ideas for 3rd eye abilities

Why do we use polarized capacitors?

Landlord wants to switch my lease to a "Land contract" to "get back at the city"

Is there a way to make member function NOT callable from constructor?

Is this food a bread or a loaf?

Is there a familial term for apples and pears?

Are objects structures and/or vice versa?

Is Social Media Science Fiction?

What is the meaning of "of trouble" in the following sentence?

Was there ever an axiom rendered a theorem?

How to make payment on the internet without leaving a money trail?

How to answer pointed "are you quitting" questioning when I don't want them to suspect

Is it wise to focus on putting odd beats on left when playing double bass drums?

Prime joint compound before latex paint?

Where to refill my bottle in India?

Crop image to path created in TikZ?

When blogging recipes, how can I support both readers who want the narrative/journey and ones who want the printer-friendly recipe?

How could a lack of term limits lead to a "dictatorship?"

multiple instances of superclass member attribute

NPE on constructor and superclassKotlin: Superclass is not accessible from traitMultiple variable let in KotlinSort collection by multiple fields in KotlinKotlin and generics, implementing abstract generic class with generic arrayExpecting member declaration in KotlinLazy initialization of nullable memberKotlin superClass KclassDagger2 generate multiple instancesKotlin reflection change instance and all members that use the instance

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;

0

I have an abstract stub class that needs to be subclasses to add spring annotations.

abstract class ConsumerStub<TYPE>

 val receivedMessages: MutableMap<String, TYPE> = ConcurrentHashMap()

 open fun processMessage(@Payload payload: TYPE, record: ConsumerRecord<String, *>) 
 this.receivedMessages[record.key()] = payload
 

 fun receivedMessageWithKey(key: String): Boolean = this.receivedMessages.contains(key)

 fun receivedMessageWithKeyCallable(key: String): Callable<Boolean> = Callable receivedMessageWithKey(key) 

 fun getReceiveMessageWithKey(key: String): TYPE? = this.receivedMessages[key]

 fun reset() 
 this.receivedMessages.clear()
 

for example:

open class WorkflowRequestConsumerStub: ConsumerStub<InternalWorkflowRequest>() 

 @KafkaListener(
 id = "xyzRequestConsumerStub",
 topics = ["abc-workflow-requests"]
 )
 override fun processMessage(
 @Payload payload: InternalWorkflowRequest,
 record: ConsumerRecord<String, *>
 ) 
 super.processMessage(payload, record)
 

I am seeing some really weird behaviour with the receivedMessages.
After some debugging I realised there seem to be 2 instances of receivedMessages.

stub.reset() throws a null pointer exception

after changing the code to initialize receivedMessages in reset(), processMessage() and receivedMessageWithKey() are seeing 2 different receivedMessages with different objectIds.

what's going on? In java the subclass should have access to any protected members in the super, so I assume the same applies to kotlin.

UPDATE: this works as expected when defining receivedMessages abstract and override in the implementations. That really sucks if this is how it should be done in kotlin. In this case there is no need for the implementation to care about the map.

kotlin

share|improve this question

edited Mar 22 at 6:40

miklesw

asked Mar 22 at 1:45

mikleswmiklesw

234416

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  If you're seeing 2 different instances of receivedMessages that most likely means that you have 2 different instances of a ConsumerStub subclass.
  
  – Erwin Bolwidt
  Mar 22 at 3:37
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  In that case they should be both initialised to concurrenthashmap. In some cases it's null. Unless spring is doing some reflection magic with the bean
  
  – miklesw
  Mar 22 at 3:40
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Nothing in the code you show should lead to such problems. Try creating a Minimal, Complete, and Verifiable example (stackoverflow.com/help/mcve).
  
  – Alexey Romanov
  Mar 22 at 7:44
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  could be an issue of how kotlin generated binaries work with spring proxying. This kind of setup works fine in java+spring. using an abstract receivedMessages solved the problem. but it's a bad solution
  
  – miklesw
  Mar 22 at 8:35
  
  

  
  
  
  

add a comment | 

0

I have an abstract stub class that needs to be subclasses to add spring annotations.

abstract class ConsumerStub<TYPE>

 val receivedMessages: MutableMap<String, TYPE> = ConcurrentHashMap()

 open fun processMessage(@Payload payload: TYPE, record: ConsumerRecord<String, *>) 
 this.receivedMessages[record.key()] = payload
 

 fun receivedMessageWithKey(key: String): Boolean = this.receivedMessages.contains(key)

 fun receivedMessageWithKeyCallable(key: String): Callable<Boolean> = Callable receivedMessageWithKey(key) 

 fun getReceiveMessageWithKey(key: String): TYPE? = this.receivedMessages[key]

 fun reset() 
 this.receivedMessages.clear()
 

for example:

open class WorkflowRequestConsumerStub: ConsumerStub<InternalWorkflowRequest>() 

 @KafkaListener(
 id = "xyzRequestConsumerStub",
 topics = ["abc-workflow-requests"]
 )
 override fun processMessage(
 @Payload payload: InternalWorkflowRequest,
 record: ConsumerRecord<String, *>
 ) 
 super.processMessage(payload, record)
 

I am seeing some really weird behaviour with the receivedMessages.
After some debugging I realised there seem to be 2 instances of receivedMessages.

stub.reset() throws a null pointer exception

after changing the code to initialize receivedMessages in reset(), processMessage() and receivedMessageWithKey() are seeing 2 different receivedMessages with different objectIds.

what's going on? In java the subclass should have access to any protected members in the super, so I assume the same applies to kotlin.

UPDATE: this works as expected when defining receivedMessages abstract and override in the implementations. That really sucks if this is how it should be done in kotlin. In this case there is no need for the implementation to care about the map.

kotlin

share|improve this question

edited Mar 22 at 6:40

miklesw

asked Mar 22 at 1:45

mikleswmiklesw

234416

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  If you're seeing 2 different instances of receivedMessages that most likely means that you have 2 different instances of a ConsumerStub subclass.
  
  – Erwin Bolwidt
  Mar 22 at 3:37
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  In that case they should be both initialised to concurrenthashmap. In some cases it's null. Unless spring is doing some reflection magic with the bean
  
  – miklesw
  Mar 22 at 3:40
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Nothing in the code you show should lead to such problems. Try creating a Minimal, Complete, and Verifiable example (stackoverflow.com/help/mcve).
  
  – Alexey Romanov
  Mar 22 at 7:44
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  could be an issue of how kotlin generated binaries work with spring proxying. This kind of setup works fine in java+spring. using an abstract receivedMessages solved the problem. but it's a bad solution
  
  – miklesw
  Mar 22 at 8:35
  
  

  
  
  
  

add a comment | 

I have an abstract stub class that needs to be subclasses to add spring annotations.

abstract class ConsumerStub<TYPE>

 val receivedMessages: MutableMap<String, TYPE> = ConcurrentHashMap()

 open fun processMessage(@Payload payload: TYPE, record: ConsumerRecord<String, *>) 
 this.receivedMessages[record.key()] = payload
 

 fun receivedMessageWithKey(key: String): Boolean = this.receivedMessages.contains(key)

 fun receivedMessageWithKeyCallable(key: String): Callable<Boolean> = Callable receivedMessageWithKey(key) 

 fun getReceiveMessageWithKey(key: String): TYPE? = this.receivedMessages[key]

 fun reset() 
 this.receivedMessages.clear()
 

for example:

open class WorkflowRequestConsumerStub: ConsumerStub<InternalWorkflowRequest>() 

 @KafkaListener(
 id = "xyzRequestConsumerStub",
 topics = ["abc-workflow-requests"]
 )
 override fun processMessage(
 @Payload payload: InternalWorkflowRequest,
 record: ConsumerRecord<String, *>
 ) 
 super.processMessage(payload, record)
 

I am seeing some really weird behaviour with the receivedMessages.
After some debugging I realised there seem to be 2 instances of receivedMessages.

stub.reset() throws a null pointer exception

after changing the code to initialize receivedMessages in reset(), processMessage() and receivedMessageWithKey() are seeing 2 different receivedMessages with different objectIds.

what's going on? In java the subclass should have access to any protected members in the super, so I assume the same applies to kotlin.

UPDATE: this works as expected when defining receivedMessages abstract and override in the implementations. That really sucks if this is how it should be done in kotlin. In this case there is no need for the implementation to care about the map.

kotlin

share|improve this question

edited Mar 22 at 6:40

miklesw

asked Mar 22 at 1:45

mikleswmiklesw

234416

abstract class ConsumerStub<TYPE>

 val receivedMessages: MutableMap<String, TYPE> = ConcurrentHashMap()

 open fun processMessage(@Payload payload: TYPE, record: ConsumerRecord<String, *>) 
 this.receivedMessages[record.key()] = payload
 

 fun receivedMessageWithKey(key: String): Boolean = this.receivedMessages.contains(key)

 fun receivedMessageWithKeyCallable(key: String): Callable<Boolean> = Callable receivedMessageWithKey(key) 

 fun getReceiveMessageWithKey(key: String): TYPE? = this.receivedMessages[key]

 fun reset() 
 this.receivedMessages.clear()
 

open class WorkflowRequestConsumerStub: ConsumerStub<InternalWorkflowRequest>() 

 @KafkaListener(
 id = "xyzRequestConsumerStub",
 topics = ["abc-workflow-requests"]
 )
 override fun processMessage(
 @Payload payload: InternalWorkflowRequest,
 record: ConsumerRecord<String, *>
 ) 
 super.processMessage(payload, record)
 

share|improve this question

edited Mar 22 at 6:40

miklesw

asked Mar 22 at 1:45

mikleswmiklesw

234416

share|improve this question

edited Mar 22 at 6:40

miklesw

asked Mar 22 at 1:45

mikleswmiklesw

234416

asked Mar 22 at 1:45

mikleswmiklesw

234416

asked Mar 22 at 1:45

mikleswmiklesw

234416