[JBoss JIRA] (WFLY-1745) WeldServices may get into inconsistent state
by Jozef Hartinger (JIRA)
Jozef Hartinger created WFLY-1745:
-------------------------------------
Summary: WeldServices may get into inconsistent state
Key: WFLY-1745
URL: https://issues.jboss.org/browse/WFLY-1745
Project: WildFly
Issue Type: Bug
Components: CDI / Weld
Affects Versions: 8.0.0.Alpha3
Reporter: Jozef Hartinger
Assignee: Stuart Douglas
Fix For: 8.0.0.Beta1
WeldBootstrapService performs an initial bootstrap of the Weld container and also performs Weld shutdown when the service is stopping.
WeldStartService finishes initialization of Weld container and performs nothing on stop() (WeldBootstrapService is expected to shut down Weld).
WeldStartService has a dependency on WeldBootstrapService.
This works fine 99% of the time. However, if a dependency of WeldStartService is restarted (e.g. due to management operation), WeldStartService as its parent is also restarted but WeldBootstrapService is not.
As a result, WeldStartService expects to find Weld container in an early initialization phase and wants to finish initialization. However, since WeldBootstrapService was not restarted, the Weld container is still in the initialized state and deployment fails when WSS tries to finish initialization again.
To reproduce modify EjbRemoveUnitTestCase for test-session-remove.jar to contain empty beans.xml file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 12 months
[JBoss JIRA] (JGRP-1666) Thread is blocking in Relayer forever
by Igor Mazur (JIRA)
Igor Mazur created JGRP-1666:
--------------------------------
Summary: Thread is blocking in Relayer forever
Key: JGRP-1666
URL: https://issues.jboss.org/browse/JGRP-1666
Project: JGroups
Issue Type: Bug
Affects Versions: 3.3.3
Reporter: Igor Mazur
Assignee: Bela Ban
Hi,
Probably i've found small issue.
We had problem in next case: two ore more clusters connected via RELAY2. And when connection was broken for some time and site went from state UNKNOWN to DOWN and after that connection restored and site went UP - messages didnt pass between clusters at all.
After some discovering of this problem I found that Relayer is blocking thread at putting message to blocking queue. And this thread will be blocked forever. Because it doesnt free this queue when site goes from state UNKNOWN to DOWN (method changeStatusToDown). Also this blocked thread is blocking of passing of any new messages through this relay - because on level NAKACK2 in method removeAndPassUp buf.getProcessing() was already setted up to true in blocked thread, and we hold this lock forever until relay goes down.
I made pull request for this issue at github - https://github.com/belaban/JGroups/pull/87
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 12 months