1 2 Previous Next 16 Replies Latest reply on May 17, 2011 10:02 AM by devinderpal

classformatError Illegal class name

devinderpal May 10, 2011 8:55 PM

I'm getting this complicated error, which I don't have much clue about. I'll really appreciate if someone can help. I get this error while clicking on one of the screens that uses http connection to get data from restful web service APIs. Below is the error:

0:16:27,297 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/truverify]] StandardWrapper.Throwable: com.google.common.collect.ComputationException: org.jboss.weld.exceptions.WeldException: by java.lang.ClassFormatError: Illegal class name "com/truverify/ws/util/org$jboss$weld$bean-jboss$classloader:id="vfs:$$$opt$jboss-6$0$0$Final$server$default$deploy$truverify$ear$truverifyWeb$war$"-ManagedBean-com$truverify$ws$util$TruverifyApp[@javax$enterprise$context$ApplicationScoped()]{}_$$_WeldClientProxy" in class file com/truverify/ws/util/org$jboss$weld$bean-jboss$classloader:id="vfs:$$$opt$jboss-6$0$0$Final$server$default$deploy$truverify$ear$truverifyWeb$war$"-ManagedBean-com$truverify$ws$util$TruverifyApp[@javax$enterprise$context$ApplicationScoped()]{}_$$_WeldClientProxy

at com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:218) [:]

at com.google.common.collect.ComputingConcurrentHashMap.apply(ComputingConcurrentHashMap.java:100) [:]

at com.google.common.collect.MapMaker$ComputingMapAdapter.get(MapMaker.java:515) [:]

at org.jboss.weld.bean.proxy.ClientProxyProvider.getClientProxy(ClientProxyProvider.java:113) [:6.0.0.Final]

at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:660) [:6.0.0.Final]

at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:707) [:6.0.0.Final]

at org.jboss.resteasy.cdi.CdiConstructorInjector.construct(CdiConstructorInjector.java:65) [:6.0.0.Final]

at org.jboss.resteasy.spi.ResteasyDeployment.createApplication(ResteasyDeployment.java:249) [:6.0.0.Final]

at org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:192) [:6.0.0.Final]

at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:67) [:6.0.0.Final]

at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.init(HttpServletDispatcher.java:36) [:6.0.0.Final]

at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1208) [:6.0.0.Final]

at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:955) [:6.0.0.Final]

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:188) [:6.0.0.Final]

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) [:6.0.0.Final]

at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.0.0.Final]

at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501) [:6.0.0.Final]

at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) [:1.1.0.Final]

at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) [:1.1.0.Final]

at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) [:6.0.0.Final]

at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.0.0.Final]

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) [:6.0.0.Final]

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.0.0.Final]

at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.0.0.Final]

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.0.0.Final]

at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.0.0.Final]

at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.0.0.Final]

at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.0.0.Final]

at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.0.0.Final]

at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.0.0.Final]

at java.lang.Thread.run(Thread.java:662) [:1.6.0_25]

1. classformatError Illegal class name

alesj May 11, 2011 2:34 AM (in response to devinderpal)

You're probably hitting https://issues.jboss.org/browse/WELD-856.
Actions
2. classformatError Illegal class name

devinderpal May 11, 2011 8:28 AM (in response to alesj)

I'm running this server on Amazon Cloud and tried it with both Amazon Linux and Suse, but the same error.
Is it possible that it's some other issue?
Actions
3. classformatError Illegal class name

devinderpal May 11, 2011 8:29 AM (in response to devinderpal)

But the same error doesn't come on Redhat Linux system, which is not on the cloud but my personal box.
Actions
4. classformatError Illegal class name

jaikiran May 11, 2011 8:38 AM (in response to devinderpal)

Out of curiosity why does the proxy name have to have such replace logic (like in https://issues.jboss.org/browse/WELD-856)? Why not name the proxies similar to what java.lang.reflect.Proxy does? Also, I currently see that the proxy name exposes the physical file path of the server instance to the client. Is that a good thing?
Actions
5. classformatError Illegal class name

alesj May 11, 2011 10:00 AM (in response to jaikiran)

Out of curiosity why does the proxy name have to have such replace logic (like in https://issues.jboss.org/browse/WELD-856)?
I guess you have to ask Pete about this, as this was there long ago.
And I'm sure there is a reason for such an ugly name. :-)

Why not name the proxies similar to what java.lang.reflect.Proxy does?
You mean plain "Proxy" + hash?

Also, I currently see that the proxy name exposes the physical file path of the server instance to the client. Is that a good thing?
This is already fixed in AS6 trunk.
Actions
6. classformatError Illegal class name

jaikiran May 11, 2011 10:16 AM (in response to alesj)

Ales Justin wrote:

Why not name the proxies similar to what java.lang.reflect.Proxy does?
You mean plain "Proxy" + hash?

Yeah, "$Proxy" + someUniqueNumber.
Actions
7. classformatError Illegal class name

devinderpal May 11, 2011 1:42 PM (in response to jaikiran)

so is this fixed? If yes, how do I get hold of latest JBoss.. Download site just has just 6.0.0 final
Actions
8. classformatError Illegal class name

devinderpal May 11, 2011 9:27 PM (in response to devinderpal)

I just tried this with jboss 6.1.0 snapshot and still runs into this problem..

Can someone tell how to install latest version of weld onto jboss 6, so that I don't run into it..
Is there any way I can just copy weld jar files over jboss? I would prefer not to go through maven
Actions
9. classformatError Illegal class name

alesj May 12, 2011 5:23 AM (in response to devinderpal)

Can someone tell how to install latest version of weld onto jboss 6, so that I don't run into it..
Is there any way I can just copy weld jar files over jboss? I would prefer not to go through maven
You also need to check out Weld:
* https://github.com/weld/core
And then you can run
* mvn clean install -Pupdate-jboss-as
where you need to set -Djboss.home=<JBOSS_HOME>
Actions
10. classformatError Illegal class name

devinderpal May 12, 2011 7:29 AM (in response to alesj)

I tried using maven but ran into this issue. help? I ran maven from weld-core-98422a8 dir.

[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project org.jboss.weld:weld-core-jboss-as-updater:1.1.0-SNAPSHOT (/tmp/weld-core-98422a8/jboss-as/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM: Could not find artifact org.jboss.weld:weld-core-parent:pom:1.1.0-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 9, column 12 -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
[
Actions
11. classformatError Illegal class name

devinderpal May 12, 2011 5:58 PM (in response to devinderpal)

anyone?
Actions
12. classformatError Illegal class name

devinderpal May 13, 2011 7:26 AM (in response to devinderpal)

finally fixed it!!
Apparently, jboss-as/pom.xml in the weld 1.1.1 FInal is not correct. It list version numbers as 1.1.0 instead of 1.1.1.. I changed the version in this file to match other pom.xml in weld 1.1.1 Final and it worked.
Actions
13. classformatError Illegal class name

jaikiran May 13, 2011 7:43 AM (in response to devinderpal)

So you no longer see the ClassFormatError?
Actions
14. classformatError Illegal class name

devinderpal May 13, 2011 7:53 AM (in response to jaikiran)

after updating JBoss with weld 1.1.1 Final, I don't see it. So I guess it's fixed in the latest weld release.
Actions

1 2 Previous Next

Go to original post