[JBoss JIRA] Created: (JASSIST-38) ClassFormatError 0000 6305 on OS400/jdk15
by Mounir Bakkali (JIRA)
ClassFormatError 0000 6305 on OS400/jdk15
-----------------------------------------
Key: JASSIST-38
URL: http://jira.jboss.com/jira/browse/JASSIST-38
Project: Javassist
Issue Type: Bug
Environment: OS400/jdk15/jboss-4.2.2.GA/javassist-3.6.GA
Reporter: Mounir Bakkali
Assigned To: Shigeru Chiba
I have been using JBoss Seam framework and when using it on OS/400 (i-series/IBM)
with jdk15, javassist generates an exception:
Caused by: javassist.CannotCompileException: by
java.lang.ClassFormatError: <mypkg>/SubCategoryRevision_$$_javassist_0
0000 6305
at java.lang.Throwable.<init>(Throwable.java:196)
at java.lang.Exception.<init>(Exception.java:41)
at javassist.CannotCompileException.<init>(CannotCompileException.java:73)
at javassist.util.proxy.FactoryHelper.toClass(FactoryHelper.java:125)
at javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:169)
... 48 more
Caused by: java.lang.ClassFormatError:
<mypkg>/SubCategoryRevision_$$_javassist_0 0000 6305
at java.lang.Throwable.<init>(Throwable.java:196)
at java.lang.Error.<init>(Error.java:49)
at java.lang.LinkageError.<init>(LinkageError.java:36)
at java.lang.ClassFormatError.<init>(ClassFormatError.java:35)
at java.lang.ClassLoader.defineClass(ClassLoader.java:651)
at java.lang.ClassLoader.defineClass(ClassLoader.java:496)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at javassist.util.proxy.FactoryHelper.toClass(FactoryHelper.java:117)
Also, when I use cglib everything works so I assume this is a javassist issue.
When I use Hibernate alone(no Seam), it also gives me the exact same exception
but when I change the configuration to force Hibernate to use cglib, everything works fine again.
Also any Seam-2.0.0.GA example will generate the same exception!
Sorry to bother you again, but would you have any idea of how to fix this?
(I would like to use JBoss Seam but at some point the Seam framework uses
javassist).
This problem only occurs when I use the OS400 jdk15. When I use the Sun jdk on my
PC it all works very well.
Any idea of how to solve this issue?
--
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
17 years, 1 month
[JBoss JIRA] Created: (JBMICROCONT-220) Support for nested properties
by Trustin Lee (JIRA)
Support for nested properties
-----------------------------
Key: JBMICROCONT-220
URL: http://jira.jboss.com/jira/browse/JBMICROCONT-220
Project: JBoss MicroContainer
Issue Type: Feature Request
Environment: N/A
Reporter: Trustin Lee
Priority: Minor
Support for nested properties make beans XML more concise and easy to understand.
Before:
<bean name="beanX" ...>
...
</bean>
<bean name="propA" ...>
<constructor><factory bean="beanX" method="getPropA"/></constructor>
<property name="propB">...</property>
</bean>
<bean name="beanY" ...>
<property name="propC"><inject bean="propA" property="propB"/></property>
</bean>
After:
<bean name="beanX" ...>
<property name="propA.propB">...</property>
</bean>
<bean name="beanY" ...>
<!-- Ales's suggestion: is this supported now? -->
<property name="propC"><inject bean="beanX" property="propA.propB"/></property>
<!-- Spring style: not sure if this is better or not, but it's somewhat finger friendly :) -->
<property name="propC ref="beanX.propA.propB"/>
</bean>
--
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
17 years, 1 month
[JBoss JIRA] Created: (JBCACHE-1234) Region activation requests partial state transfer from wrong nodes
by Brian Stansberry (JIRA)
Region activation requests partial state transfer from wrong nodes
------------------------------------------------------------------
Key: JBCACHE-1234
URL: http://jira.jboss.com/jira/browse/JBCACHE-1234
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: 2.1.0.CR2, 1.4.1.SP7, 2.0.0.GA
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Priority: Critical
Fix For: 1.4.1.SP8, 2.1.0.GA
When requesting partial state transfer as part of activating a region, we are asking for state from the wrong nodes:
// Get the state from each DataOwner and integrate in their
// respective buddy backup cache
List<Address> buddies = buddyManager.getBuddyAddresses();
for (Address buddy : buddies)
{
List<Address> sources = new ArrayList<Address>(1);
sources.add(buddy);
Fqn buddyRoot = BuddyManager.getBackupFqn(buddy, fqn);
subtreeRoot = cache.findNode(buddyRoot);
....
cache.fetchPartialState(sources, fqn, subtreeRoot.getFqn());
}
}
BuddyManager.getBuddyAddresses() returns the nodes who are backing up *our* data, not those for whom we are serving as a buddy. We want the state for the latter. This comes from the package-private BuddyManager.buddyGroupsIParticipateIn field, so BuddyManager is going to have to expose that somehow.
--
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
17 years, 1 month
[JBoss JIRA] Updated: (JBAS-2793) Quick overview wrt. to used modules + version
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2793?page=all ]
Dimitris Andreadis updated JBAS-2793:
-------------------------------------
Fix Version/s: JBossAS-5.0.0.CR1
Assignee: Dimitris Andreadis
> Quick overview wrt. to used modules + version
> ---------------------------------------------
>
> Key: JBAS-2793
> URL: http://jira.jboss.com/jira/browse/JBAS-2793
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Build System
> Environment: JBoss 4.x, OS: *x
> Reporter: Jens Elkner
> Assigned To: Dimitris Andreadis
> Priority: Optional
> Fix For: JBossAS-5.0.0.CR1
>
> Attachments: components2html.xsl, createComponentList.sh
>
>
> Sometimes one needs to know, which thirdparty modules are used by jboss and especially which version. So a simple html formatted overview would be handy.
> Since the info is already there, I made a simple script + stylesheet to create such an html file, which might packaged with the docs ...
> Feel free to use/modify it as you want ;-)
--
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
17 years, 1 month
[JBoss JIRA] Created: (JBAS-4228) Preferred server HASingletonElectionPolicy
by Brian Stansberry (JIRA)
Preferred server HASingletonElectionPolicy
------------------------------------------
Key: JBAS-4228
URL: http://jira.jboss.com/jira/browse/JBAS-4228
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
An HASingletonElectionPolicy impl that allows configurable specification of a "preferred server". If the preferred server is running, it's the master, otherwise the master is deterministically selected based on the standard policy.
1) Determine if you are the preferred server by comparing you node name to the configured "preferred server" value.
2) When you get a view change, check if preferred server is in the view. If yes, and you're the preferred server, become master, otherwise don't. If preferred server is not in view, fall back on the base policy.
Have to make sure the mechanism of identifying and matching the "preferred server" is bullet proof (machine names vs. configuration-specified names vs. IP addresses, plus ports.)
--
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
17 years, 1 month