[JBoss JIRA] Created: (JBAOP-796) Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader
by Flavia Rainone (JIRA)
Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader
------------------------------------------------------------------------------------------------
Key: JBAOP-796
URL: https://jira.jboss.org/browse/JBAOP-796
Project: JBoss AOP
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.1.9.Alpha1
Reporter: Flavia Rainone
Assignee: Flavia Rainone
Fix For: 2.1.6 CP01, 2.1.9.GA, 2.2.1.GA
Currently, an Advisor is created by calling AspectManager.instance().getAdvisor().
The correct is to create the advisor by calling AspectManager.instance(WovenClass.class).getAdvisor(WovenClass.class).
Otherwise, the Advisor will be created as part of the AspectManager/Domain corresponding to the current context class loader:
public static synchronized AspectManager instance()
{
return instance(Thread.currentThread().getContextClassLoader());
}
In the JBoss AS environment, if the woven class is loaded during an archive deployment, this is equivalent to say that the Advisor will be erroneously created by the domain of the current deployment, instead of being created by the appropriate AspectManager/Domain instance.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] Created: (JBAOP-806) Using UnmodifiableLinkedHashMap constructor causes an UnsupportedOperationException exception to be thrown on IBM JDK
by Dustin Kut Moy Cheung (JIRA)
Using UnmodifiableLinkedHashMap constructor causes an UnsupportedOperationException exception to be thrown on IBM JDK
---------------------------------------------------------------------------------------------------------------------
Key: JBAOP-806
URL: https://issues.jboss.org/browse/JBAOP-806
Project: JBoss AOP
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Aspect Library
Environment: OS: Fedora 14
JDK: IBM JDK
Reporter: Dustin Kut Moy Cheung
Priority: Critical
Read Summary. This error is caused because the IBM JDK LinkedHashMap invokes the putAll method on HashMap. Since the putAll method is overwridden in UnmodifiableLinkedHashMap.java, the UnmodifiableLinkedHashMap putAll method is called instead of the HashMap constructor and therefore throws that exception.
The fix is to change the signature of the constructor being called (LinkedHashMap constructor) so that the putAll method is not called.
Please see the patch that attempts to solve this issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (AS7-4862) Remote EJB SFSB load balancing still very suboptimal
by Radoslav Husar (JIRA)
Radoslav Husar created AS7-4862:
-----------------------------------
Summary: Remote EJB SFSB load balancing still very suboptimal
Key: AS7-4862
URL: https://issues.jboss.org/browse/AS7-4862
Project: Application Server 7
Issue Type: Bug
Components: Clustering, EJB
Affects Versions: 7.1.2.Final (EAP)
Reporter: Radoslav Husar
Assignee: jaikiran pai
Fix For: 7.1.3.Final (EAP)
Looking at the load-balancing again, it seems still wrong. Checking the logs, servers were started *and cluster was formed* ~10 seconds prior to starting the client and load-balancing was roughly:
* node perf18: ~50% of sessions
* node perf19: 0
* node perf20: 0
* node perf21: ~50% of sessions
I let all the session to be created in one minute (not all at once).
The nodes were also specified in the properties.
{noformat}
node perf18
[JBossINF] 07:01:53,991 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (CacheService lifecycle - 1) ISPN000094: Received new cluster view: [perf19/ejb|3] [perf19/ejb, perf21/ejb, perf20/ejb, perf18/ejb]
node perf19
[JBossINF] 07:01:53,781 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-19,null) ISPN000094: Received new cluster view: [perf19/ejb|3] [perf19/ejb, perf21/ejb, perf20/ejb, perf18/ejb]
node perf20
[JBossINF] 07:01:53,781 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-14,null) ISPN000094: Received new cluster view: [perf19/ejb|3] [perf19/ejb, perf21/ejb, perf20/ejb, perf18/ejb]
node perf21
[JBossINF] 07:01:53,780 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-12,null) ISPN000094: Received new cluster view: [perf19/ejb|3] [perf19/ejb, perf21/ejb, perf20/ejb, perf18/ejb]
controller node
2012/05/22 07:02:02:932 EDT [DEBUG][TestController] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Setting thread count: 2000, was: 0
2012/05/22 07:02:53:731 EDT [DEBUG][TestController] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - All runners (2000) started in 50799 milliseconds
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months