[JBoss JIRA] Commented: (EMBJOPR-300) Admin console on 6.0.0.M3 fails with NoClassDefFoundError when adding a new resource
5:12 a.m.
[
https://jira.jboss.org/browse/EMBJOPR-300?page=com.atlassian.jira.plugin....
]
Tim Fox commented on EMBJOPR-300:
---------------------------------
Just wanted to make a comment here.
The HornetQ team spent literally months getting the new HornetQ admin functionality
integrated into the JBoss AS console, only to have it broken at the very last minute by
this bug just before the release. This is particularly frustrating due to the large amount
of effort spent trying to hit the M3 release, and it reflects badly on the HornetQ project
(even though it wasn't a problem in HornetQ).
I know that shit happens and people make mistakes - that is par for the course. However
what this shows is a lack of smoke testing of core functionality before cutting a
release.
Can I suggest that before cutting any AS release someone spends an hour to test the
distribution?- click through the admin console and make sure most things work ok. This is
something we always do in the HQ project - test our distros before releasing them to the
world at large.
Admin console on 6.0.0.M3 fails with NoClassDefFoundError when adding
a new resource
-------------------------------------------------------------------------------------
Key: EMBJOPR-300
URL: https://jira.jboss.org/browse/EMBJOPR-300
Project: Embedded Jopr
Issue Type: Bug
Reporter: jaikiran pai
Assignee: Ian Springer
Fix For: 1.4.0
As mentioned in the referenced forum thread, the admin-console shipped in AS 6.0.0.M3
throws this exception (for most of the "Add new resource" operations):
javax.servlet.ServletException: org/richfaces/validator/NullValueValidator
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:325)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:336)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:38)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:206)
at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:388)
at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515)
at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
at org.jboss.on.embedded.LazyStartupFilter.doFilter(LazyStartupFilter.java:87)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:293)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95)
at
org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at
org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:872)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
at java.lang.Thread.run(Thread.java:619)
One such operation is Admin console -> JMS Manager -> JMS queues -> Add new
resource
--
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
5333
days inactive
5333
days old
embjopr-issues@lists.jboss.org
0 comments
1 participants
participants (1)
-
Tim Fox (JIRA)