[Design of JBoss Profiler] - Jboss Profiler 2.0 Beta 3 and JBoss AS 4.3.0.GA_CP02 -> NPE
by rhills
We're running JBoss AS 4.3.0.GA_CP02 + Seam 2.1.0.GA and today I tried to install the Jboss Profiler 2.0 Beta 3 to do some profiling.
I followed the readme.txt carefully, putting jboss-profiler.jar, jboss-profiler.properties, jboss-profiler-plugins.jar and javassist.jar in my jboss-as/bin directory and jboss-profiler.sar into my jboss-as/server/default/deploy directory (this is on my desktop development machine).
Initially, I've not changed any of the configuration (jboss-profiler.properties or jboss-profiler.sar/META-INF/jboss-service.xml).
I started up JBoss-AS without our own applications deployed and it seems to start cleanly. The first two lines in the log are:
JBoss Profiler 2.0.Beta3 (Sun Microsystems Inc. 1.6.0_03)
| JBoss Profiler depends on external communication module
|
I assume the second line is reporting a satisfied dependency and not an unsatisfied one!
Later on, I see:
2008-11-24 17:18:25,375 INFO [org.jboss.profiler.as.Profiler] JBoss Profiler: ProfilerMBean started
| 2008-11-24 17:18:25,375 INFO [org.jboss.profiler.as.Communicator] JBoss Profiler: Communicator for JBoss Profiler 2.0.Beta3
| 2008-11-24 17:18:25,406 INFO [org.jboss.profiler.as.Communicator] JBoss Profiler: Socket=0.0.0.0:5400
| 2008-11-24 17:18:34,031 INFO [org.jboss.wsf.stack.jbws.NativeServerConfig] JBoss Web Services - Native
| 2008-11-24 17:18:34,031 INFO [org.jboss.wsf.stack.jbws.NativeServerConfig] jbossws-native-2.0.1.SP2_CP03 (build=200808011456)
| 2008-11-24 17:18:38,578 INFO [org.apache.catalina.core.AprLifecycleListener] Loaded Apache Tomcat Native library 1.1.13.
| 2008-11-24 17:18:38,578 INFO [org.apache.catalina.core.AprLifecycleListener] APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
| 2008-11-24 17:18:40,765 INFO [org.apache.coyote.http11.Http11AprProtocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8090
| 2008-11-24 17:18:40,781 INFO [org.apache.coyote.http11.Http11AprProtocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8443
|
However, as soon as I try and view my jmx-console, I get a NPE:
| 2008-11-24 17:20:01,921 ERROR [org.apache.catalina.core.ContainerBase] Servlet.service() for servlet jsp threw exception
| java.lang.NullPointerException
| at org.jboss.profiler.agent.ProfilerThreadImpl.allocation(ProfilerThreadImpl.java:226)
| at org.apache.jsp.index_jsp.<init>(index_jsp.java:7)
| at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
| at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
| at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
| at java.lang.reflect.Constructor.newInstance(Unknown Source)
| at java.lang.Class.newInstance0(Unknown Source)
| at java.lang.Class.newInstance(Unknown Source)
| at org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:145)
| at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:323)
| at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
| at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
| at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
| at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
| at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:853)
| at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:579)
| at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1513)
| at java.lang.Thread.run(Unknown Source)
|
When I debug and stop at ProfilerThreadImpl.java, line 226, I find that activeFrame (and hence fi) is null and this apparently causes the NPE. Why is this happening? Is there something wrong with my configuration, or is there something in the newer version of JBoss (4.3) that's causing this?
Cheers,
Rob Hills
Waikiki, Western Australia
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191619#4191619
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191619
17 years, 4 months
[Design of EJB 3.0] - Re: EJBTHREE-1396 MockServer must report startup / shutdown
by jaikiran
I just did a clean install of the entire project including my r81462 changes. The test case is passing on my setup:
| -------------------------------------------------------------------------------
| Test set: org.jboss.ejb3.test.proxy.remoteaccess.unit.RemoteAccessTestCase
| -------------------------------------------------------------------------------
| Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.563 sec
12:06:19,823 INFO [RedirectClassloader] Replacing request for jndi.properties with jndi-remote.properties
| 12:06:19,917 DEBUG [MockServerController] Remote Process working directory: D:\JBoss\CleanEJB3\proxy
| 12:06:19,917 INFO [MockServerController] Launching in separate process: C:\jdk1.5.0_10\bin\java -cp "D:\JBoss\CleanEJB3\proxy\target\classes;D:\JBoss\CleanEJB3\proxy\target\tests-classes;D:\JBoss\CleanEJB3\proxy\conf;C:\Documents and Settings\jaikiran_pai\.m2\repository\apache-log4j\log4j\1.2.14\log4j-1.2.14.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\apache-xerces\xercesImpl\2.9.1\xercesImpl-2.9.1.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\apache-xerces\xml-apis\2.9.1\xml-apis-2.9.1.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\javassist\javassist\3.8.0.GA\javassist-3.8.0.GA.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\javax\activation\activation\1.0.2\activation-1.0.2.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\javax\security\jacc\1.0\jacc-1.0.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\javax\xml\bind\jaxb-api\2.1\jaxb-api-2.1.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\javax\xml\stream\stax-api\1.0-2\stax-api-1.0-2.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\jboss\jboss-serialization\1.0.3.GA\jboss-serialization-1.0.3.GA.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\jboss\jbossws\jboss-jaxrpc\1.0.4.GA\jboss-jaxrpc-1.0.4.GA.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\junit\junit\4.4\junit-4.4.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\apache\ant\ant\1.7.0\ant-1.7.0.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\apache\ant\ant-launcher\1.7.0\ant-launcher-1.7.0.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\jboss-common-core\2.2.5.GA\jboss-common-core-2.2.5.GA.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\jboss-jaxws\2.0.1.GA\jboss-jaxws-2.0.1.GA.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\jboss-mdr\2.0.0.Beta17\jboss-mdr-2.0.0.Beta17.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\jboss-reflect\2.0.0.Beta13\jboss-reflect-2.0.0.Beta13.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\jboss-transaction-spi\5.0.0.Beta4\jboss-transaction-spi-5.0.0.Beta4.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\jboss-vfs\2.0.0.Beta18\jboss-vfs-2.0.0.Beta18.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\jbossxb\2.0.0.CR12\jbossxb-2.0.0.CR12.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\aop\jboss-aop\2.0.0.CR15\jboss-aop-2.0.0.CR15.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\aspects\jboss-current-invocation-aspects\1.0.0.CR1\jboss-current-invocation-aspects-1.0.0.CR1.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\aspects\jboss-remoting-aspects\1.0.1.CR3\jboss-remoting-aspects-1.0.1.CR3.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\aspects\jboss-security-aspects\1.0.0.Beta1\jboss-security-aspects-1.0.0.Beta1.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\aspects\jboss-transaction-aspects\1.0.0.Beta1\jboss-transaction-aspects-1.0.0.Beta1.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\ejb3\jboss-ejb3-common\0.1.5\jboss-ejb3-common-0.1.5.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\ejb3\jboss-ejb3-ext-api\0.4\jboss-ejb3-ext-api-0.4.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\ejb3\jboss-ejb3-interceptors\0.13.3\jboss-ejb3-interceptors-0.13.3.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\ejb3\jboss-ejb3-metadata\0.12.2\jboss-ejb3-metadata-0.12.2.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\ejb3\jboss-ejb3-test\1.0.0-Beta1\jboss-ejb3-test-1.0.0-Beta1.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\javaee\jboss-ejb-api\3.0.0.CR1\jboss-ejb-api-3.0.0.CR1.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\javaee\jboss-jaspi-api\1.0.0.CR1\jboss-jaspi-api-1.0.0.CR1.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\javaee\jboss-jca-api\1.5.0.CR1\jboss-jca-api-1.5.0.CR1.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\javaee\jboss-jms-api\1.1.0.CR1\jboss-jms-api-1.1.0.CR1.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\javaee\jboss-persistence-api\3.0.0.CR1\jboss-persistence-api-3.0.0.CR1.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\javaee\jboss-transaction-api\1.0.1.CR1\jboss-transaction-api-1.0.1.CR1.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\logging\jboss-logging-log4j\2.0.5.GA\jboss-logging-log4j-2.0.5.GA.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\logging\jboss-logging-spi\2.0.5.GA\jboss-logging-spi-2.0.5.GA.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\metadata\jboss-metadata\1.0.0.Beta37\jboss-metadata-1.0.0.Beta37.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\microcontainer\jboss-dependency\2.0.0.Beta17\jboss-dependency-2.0.0.Beta17.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\microcontainer\jboss-kernel\2.0.0.Beta17\jboss-kernel-2.0.0.Beta17.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\naming\jnpserver\5.0.0.CR1\jnpserver-5.0.0.CR1.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\remoting\jboss-remoting\2.4.0.CR2\jboss-remoting-2.4.0.CR2.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\security\jboss-security-spi\2.0.2.Beta5\jboss-security-spi-2.0.2.Beta5.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\security\jbosssx-client\2.0.2.Beta5\jbosssx-client-2.0.2.Beta5.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\org\jboss\ws\jbossws-spi\1.0.3.GA\jbossws-spi-1.0.3.GA.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\oswego-concurrent\concurrent\1.3.4-jboss-update1\concurrent-1.3.4-jboss-update1.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\qdox\qdox\1.6\qdox-1.6.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\trove\trove\1.0.2\trove-1.0.2.jar;C:\Documents and Settings\jaikiran_pai\.m2\repository\wutka-dtdparser\dtdparser121\1.2.1\dtdparser121-1.2.1.jar" -ea org.jboss.ejb3.test.proxy.remoteaccess.MockServer org.jboss.ejb3.test.proxy.remoteaccess.unit.RemoteAccessTestCase localhost 12345
| 12:06:19,917 INFO [MockServerController] Remote process = java.lang.ProcessImpl@3901c6
| 12:06:21,151 INFO [MockServerInvocationHandler] Received request: START
| 12:06:21,182 DEBUG [EmbeddedTestMcBootstrap] Starting org.jboss.ejb3.test.mc.bootstrap.EmbeddedTestMcBootstrap@1174b07...
| 12:06:21,448 INFO [EmbeddedTestMcBootstrap] Started: org.jboss.ejb3.test.mc.bootstrap.EmbeddedTestMcBootstrap@1174b07
| 12:06:21,464 DEBUG [Ejb3McRegistrar] Created Ejb3McRegistrar with backing Kernel: org.jboss.kernel.Kernel@1808199
| .....
| 12:06:23,948 INFO [MockServer] MockServer started
| 12:06:23,948 DEBUG [MockServerInvocationHandler] Server in STARTED state
| 12:06:23,948 INFO [MockServerController] Server started. Status = STARTED
| 12:06:23,948 INFO [RemoteAccessTestCase] MockServer started in 4063 milli sec.
|
I suspect that on the Hudson setup, the MockServer is failing to start, maybe some port/socket connection related exception in the remote process, which ultimately results in the failure of the (client) test case.
anonymous wrote :
| If you've got a platform-specific problem here, I'll be happy to look into it. Just let me know.
That would be great. I think we would have to attach a debugger with a breakpoint in the MockServer constructor. Let me know if i can be of any help in this. Thanks!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191603#4191603
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191603
17 years, 4 months