[JBoss JIRA] Created: (JBAS-5232) HAR deployment broken
by Javid Jamae (JIRA)
HAR deployment broken
---------------------
Key: JBAS-5232
URL: http://jira.jboss.com/jira/browse/JBAS-5232
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployment services
Affects Versions: JBossAS-5.0.0.Beta4
Reporter: Javid Jamae
Assigned To: Dimitris Andreadis
I tried deploying a HAR both standalone and inside of an EAR and got an exception:
21:10:08,156 ERROR [AbstractKernelController] Error installing to Start: name=jbia.har:app=Video state=Create mode=Manual requiredState=Installed
org.jboss.deployment.DeploymentException: Unable to determine urls from classloader [BaseClassLoader@1e6661{vfsfile:/C:/jboss-5.0.0.Beta4/server/deployment/deploy/video.har}]
at org.jboss.hibernate.jmx.Hibernate.scanForMappings(Hibernate.java:272)
...
See forum reference for full stack trace.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 1 month
[JBoss JIRA] Created: (JGRP-716) TCP based configs need UNICAST for correct ordering
by Bela Ban (JIRA)
TCP based configs need UNICAST for correct ordering
---------------------------------------------------
Key: JGRP-716
URL: http://jira.jboss.com/jira/browse/JGRP-716
Project: JGroups
Issue Type: Task
Reporter: Bela Ban
Assigned To: Bela Ban
Fix For: 2.6.3, 2.7
In a TCP based config *without* UNICAST, messages can get delivered out of order if a thread pool is enabled at the transport level. Example:
- Sender A sends unicast messages (same for multicast messages) M1, M2 and M3 to B
- B's transport dispatches the 3 messages to a thread pool (if bundling is enabled, then this issue might not occur as all 3 messages might have gotten bundled, and will then get delivered as a bundle, by the same thread)
- M1 is processed by thread-1, M2 by thread-2 and M3 by thread-3
==> There are no guarantees with respect to ordering now, as thread pool destroyed ordering and there is no UNICAST to make sure messages arriving in different threads get ordered accoring to sequence number
TODO: ship all TCP based protocols with UNICAST
WORKAROUND: disable the thread pool(s) in the TCP transport
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 1 month