[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
13 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
13 years, 4 months
[JBoss JIRA] Created: (JBAS-8865) caching ejb3 entities tutorial demo does not work in JBoss 6
by Leos Literak (JIRA)
caching ejb3 entities tutorial demo does not work in JBoss 6
------------------------------------------------------------
Key: JBAS-8865
URL: https://issues.jboss.org/browse/JBAS-8865
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Documentation
Reporter: Leos Literak
Priority: Minor
I run this demo: http://docs.jboss.org/ejb3/docs/tutorial/1.0.7/html/Caching_EJB3_Entities...
in jboss 6 and it fails:
Caused by: org.hibernate.HibernateException: could not instantiate RegionFactory [org.hibernate.cache.jbc2.JndiMultiplexedJBossCacheRegionFactory]
at org.hibernate.cfg.SettingsFactory.createRegionFactory(SettingsFactory.java:423) [:3.6.0.Final]
at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:280) [:3.6.0.Final]
at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2833) [:3.6.0.Final]
at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2829) [:3.6.0.Final]
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1840) [:3.6.0.Final]
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:902) [:3.6.0.Final]
... 78 more
Caused by: java.lang.ClassNotFoundException: org.hibernate.cache.jbc2.JndiMultiplexedJBossCacheRegionFactory from BaseClassLoader@a63599{vfs:///C:/Users/llitera
rver/default/conf/jboss-service.xml}
at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:480) [jboss-classloader.jar:2.2.0.GA]
at java.lang.ClassLoader.loadClass(ClassLoader.java:248) [:1.6.0_22]
at java.lang.Class.forName0(Native Method) [:1.6.0_22]
at java.lang.Class.forName(Class.java:169) [:1.6.0_22]
at org.hibernate.util.ReflectHelper.classForName(ReflectHelper.java:192) [:3.6.0.Final]
at org.hibernate.cfg.SettingsFactory.createRegionFactory(SettingsFactory.java:409) [:3.6.0.Final]
... 83 more
please update the demo to work in current jboss, thanks
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (JBAS-9406) Bean class local SFSB fails to replicate
by Jozef Hartinger (JIRA)
Bean class local SFSB fails to replicate
----------------------------------------
Key: JBAS-9406
URL: https://issues.jboss.org/browse/JBAS-9406
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Reporter: Jozef Hartinger
Assignee: Carlo de Wolf
Priority: Critical
The attached application contains a simple @SessionScoped SFSB:
@SessionScoped
@Stateful
@Named
public class Foo implements Serializable {
private String text;
public String getText() {
return text;
}
public void setText(String text) {
this.text = text;
}
public void submit()
{
}
@Remove
public void remove() {
}
}
When an action is invoked on the bean, I can see replication failing in the server log. See the attached logs for details. In the first one, the Foo bean does not implement serializable (as it is not required to do so). The second log was captured after the bean has been changed to implement the Serializable interface.
To reproduce:
1) Create two JBoss AS 6 instances as described at https://github.com/weld/core/blob/master/examples/README.md
2) Deploy the attached war file
3) Open http://localhost:8080/foo/foo.xhtml
4) Enter any text and click submit
This is where the replication fails and errors appear in the log
5) Verify text appears at http://localhost:8180/foo/foo.xhtml - you'll need to copy session id parameter as well, e.g. http://localhost:8180/foo/foo.xhtml;jsessionid=PX5Q-ORdeUJLifFqqrOkQA__
Note that the replication succeeds if I use an explicit @Local interface for the Foo bean.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months