Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Passive Resource Duplicate Probe Context #32

Open
stiesssh opened this issue Jul 5, 2023 · 2 comments
Open

Passive Resource Duplicate Probe Context #32

stiesssh opened this issue Jul 5, 2023 · 2 comments

Comments

@stiesssh
Copy link
Collaborator

stiesssh commented Jul 5, 2023

[Worker-11: Launching RMCU] ERROR: An error occurred: UndeclaredThrowableException:: null
java.lang.reflect.UndeclaredThrowableException
	at jdk.proxy20/jdk.proxy20.$Proxy82.newProbeMeasurementAvailable(Unknown Source)
	at org.palladiosimulator.probeframework.probes.Probe.notifyMeasurementSourceListener(Probe.java:53)
	at org.palladiosimulator.analyzer.slingshot.monitor.probes.EventBasedProbe.takeMeasurement(EventBasedProbe.java:64)
	at org.palladiosimulator.analyzer.slingshot.behavior.resourcesimulation.monitor.PassiveResourceProbeTable.currentTimeOfPassiveResourceAcquired(PassiveResourceProbeTable.java:46)
	at org.palladiosimulator.analyzer.slingshot.behavior.resourcesimulation.monitor.PassiveResourceMonitoringBehavior.onPassiveResourceAcquired(PassiveResourceMonitoringBehavior.java:80)
	at jdk.internal.reflect.GeneratedMethodAccessor61.invoke(Unknown Source)
[...]
Caused by: java.lang.IllegalStateException: First measurement to the same context arrived while previous series of the same context did not complete.
	at org.palladiosimulator.probeframework.calculator.Calculator.newProbeMeasurementAvailable(Calculator.java:180)
	... 41 more
@stiesssh
Copy link
Collaborator Author

stiesssh commented Jul 5, 2023

I think this also happens in SimuLizar, and it is probably cause by the fact, that different Users request and release the resources.

For now, i will not put much more time into this.

@stiesssh
Copy link
Collaborator Author

stiesssh commented Jul 5, 2023

actually, only holdingTime breaks. waitingTime still works. it just looked as if both were broken, because when the holdingTime run into the exception, the entire PassiveResourceMonitoringBehavior got unregistered.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant