webapp classloader exception
by 小明哥
Hi all,
I deploy chartdirector demo app(chartdir_java.war) to jboss as 7, exception as follows:
any help?
javax.servlet.ServletException: java.lang.LinkageError: Failed to link ChartDirector/bA (Module "deployment.chartdir_java.war:main" from Service Module Loader) org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:862) org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:791) org.apache.jsp.jspdemo.cdinfo_jsp._jspService(cdinfo_jsp.java:111) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) javax.servlet.http.HttpServlet.service(HttpServlet.java:847) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253) javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
root cause
java.lang.LinkageError: Failed to link ChartDirector/bA (Module "deployment.chartdir_java.war:main" from Service Module Loader) org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:372) org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:248) org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:72) org.jboss.modules.Module.loadModuleClass(Module.java:576) org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:176) org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:357) org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:329) org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:306) org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:100) ChartDirector.Chart.getBootLog(SourceFile:652) org.apache.jsp.jspdemo.cdinfo_jsp._jspService(cdinfo_jsp.java:97) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) javax.servlet.http.HttpServlet.service(HttpServlet.java:847) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253) javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
root cause
java.lang.NoClassDefFoundError: ChartDirector/bA (wrong name: ChartDirector/ba) java.lang.ClassLoader.defineClass1(Native Method) java.lang.ClassLoader.defineClassCond(ClassLoader.java:632) java.lang.ClassLoader.defineClass(ClassLoader.java:616) java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:368) org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:248) org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:72) org.jboss.modules.Module.loadModuleClass(Module.java:576) org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:176) org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:357) org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:329) org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:306) org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:100) ChartDirector.Chart.getBootLog(SourceFile:652) org.apache.jsp.jspdemo.cdinfo_jsp._jspService(cdinfo_jsp.java:97) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) javax.servlet.http.HttpServlet.service(HttpServlet.java:847) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253) javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
note The full stack trace of the root cause is available in the JBoss Web/7.0.0.Beta4 logs.
JBoss Web/7.0.0.Beta4
12 years, 8 months
Error reporting and deployment failure for services with unresolved dependencies
by Jaikiran Pai
While integrating EJB3 service into current AS trunk, I noticed that if
a Component's service (or any service in general) has unresolved
dependencies, although the service stays in DOWN state (as expected), no
error is reported and the deployment does *not* fail. As a side effect
of this, a runtime invocation on the service (a InitialContext.lookup()
leading to the ServiceReferenceObjectFactory.getObjectInstance() in this
case) ended up hanging indefinitely http://pastebin.com/jK0i1aCi
To debug this, I had to use jconsole and then get a list of all the
services, their dependencies and the state and then figure out what's
missing:
Service
"jboss.deployment.unit.ejb3-example.jar.component.SimpleStatelessSessionBean"
(class org.jboss.as.ee.component.service.ComponentService) mode ACTIVE
state DOWN (dependencies:
jboss.naming.context.java.module.ejb3-example.jar,
jboss.naming.context.java.app.ejb3-example.jar,
jboss.naming.context.java.comp.ejb3-example.jar.SimpleStatelessSessionBean,
jboss.naming.context.java.global."ejb3-example/SimpleStatelessSessionBean!org.jboss.as.demos.ejb3.archive.SimpleStatelessSessionLocal")
(has missing dependency)
Shouldn't a unresolved dependency on a service result in deployment failure?
-Jaikiran
12 years, 8 months
BETA1 must have list additions?
by Alessio Soldano
Hi,
can I ask if we can include moving to jboss-module 1.0.0.Beta16 in the
stuff to be done before Beta1? That has the fixes Jason did for the JAXP
related ws regressions.
Thanks
Alessio
--
Alessio Soldano
Web Service Lead, JBoss
12 years, 8 months
Management API Security - Part 2 ;-)
by Darran Lofthouse
Following on from the discussions this week please find below some
updated articles: -
This first article specified the mechanisms to be supported for the two
transports: -
http://community.jboss.org/docs/DOC-16587
The next article is a sample configuration to provide this: -
http://community.jboss.org/docs/DOC-16576
DOC-16576 contains quite a bit of detail but the idea here is to provide
(need a better word) components that either are the required callback
handlers or components that supply the required callback handlers for
SASL - the HTTP API will then also make use of these in the same way.
Regards,
Darran Lofthouse.
12 years, 8 months
Customising the HTTP Server
by Darran Lofthouse
We currently have the code for the HTTP server in GIT, what level of
changes can be made to this?
I don't need to go to the extreme of HTTP session management but I do
need something to reliably associate some state with the connection from
the client. At the moment I can detect the address is the same as one
before but I can't verify it is the same connection.
Regards,
Darran Lofthouse.
12 years, 8 months
Making Admin Console Accessible over HTTP API
by Darran Lofthouse
Do we have any plans regarding when the console will be accessible to be
served up from a HTTP API connection?
I have started to define the authentication mechanisms to be supported
over HTTP so shortly we may want to start verifying GWT with these
mechanisms but I think we may have issues if communicating with a
different host to the one that made the console available.
Regards,
Darran Lofthouse.
12 years, 8 months
ThreadLocal JNDI View?
by Darran Lofthouse
Do we have any mechanism to make a JNDI view available to a specific thread?
I am just thinking about some scenarios were legacy LoginModules may be
used with the management API security and some of these may have an
assumption that they can use JNDI to lookup the things they need.
One option could be to establish a very simple JNDI view that would be
accessible of the module creates a new InitialContext so just checking
if we already have anything in this area.
Regards,
Darran Lofthouse.
12 years, 9 months
CLI parsing of complex params
by Brian Stansberry
I find myself using the CLI a lot for quick testing, so I'm trying out
some fairly complex operations.
This one doesn't work:
[~]
:composite(steps=[{"operation"=>"add-system-property","name"=>"test","value"="newValue"},{"operation"=>"add-system-property","name"=>"test2","value"=>"test2"}])
Argument name '"name"' is not a valid identifier or the format is wrong
for the argument list.
This one does, so I know the ability to create a dmr ModelNode from a
param value is still there.
[~] :add-namespace(namespace={"test"=>"test"})
{
"outcome" => "success",
"result" => undefined,
"compensating-operation" => {
"operation" => "remove-namespace",
"address" => [],
"namespace" => "test"
}
}
I think the issue is the parser is searching for indexOf(',') as the way
to decide the end of a parameter name/value pair. It's probably going to
need to be more of a state-machine kind of thing where chars are read
one at a time and trigger state transitions.
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
12 years, 9 months
