JAMon do not work after serialization+deserialization

[George Mitev]

Hi Steve,

Thanks for the great library. It helps a lot in my company :)

I experienced an issue with jamon and I kindly ask for help.

The flow of my performance testing needs JAMon monitor to go through these steps:

1. created,
2. serialized
3. deserialized
4. deserialized copy to be stopped

But the following scenario do not work (step 4 has no effect). Could you provide my an fix or an workaround?

I placed an question in stackoverflow also. It contains full code to illustrate mentioned behaviour:

http://stackoverflow.com/questions/35637408/jamon-do-not-work-after-serializationdeserialization

Kind regards,
George

[Steve Souza]

I will look into this. I have a newborn so my time is limited, but will look into this when time permits. Any further info you can provide would be helpful.

[George Mitev]

Thanks for the reply.

I workarounded the issue by serializing the start moment only. In the end moment I submit the time difference. With this approach I lose the statistics for active items, but I have the performance statistics.

Check stackoverflow link for source code.

[Steve Souza]

ok, thanks for the followup. What is the use case you are working on?

[Steve Souza]

Note if active is important you could also serialize that and populate it manually. There is probably a method like monitor.setMaxActive(10). I don't recall the exact syntax, but i am pretty sure it is doable. Let me know if you are interested.

[George Mitev]

Hi. Here is the usecase: I have got an JMS service:
1. producer creates a number of messages and
2. consumers which process them.
I need to analize the timeframe between creating a message in the producer and start of processing it in a worker. (message wait time)

I tried serializing the monitor inside the message, but it is not possible.

I did not understand how could I get correct "active" elements...

Kind regards