Announcement Announcement Module
Collapse
No announcement yet.
Problems with SpringSource Tool Suite: NPE During Deployment Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Problems with SpringSource Tool Suite: NPE During Deployment

    We downloaded STS 2.1.0.SR01-e3.5-win32. Installed the SVN and FindBugs plugins without checking the box to search other locations for dependencies (which keeps them from forcing an upgrade to 3.5.1), and then configured our environment and started working with our test projects. We get two types of issues which are complete showstoppers. The second problem will be posted shortly.

    The first problem: deployment to Spring dm server results in an NPE. I tried reverting my workspace, and reverting the Spring dm server install. The problem appears to be in the sts directory someplace. I have to reinstall to make this one go away.

    The second problem will be posted shortly.

    Code:
    [2009-10-14 16:16:44.522] main                     <SPKB0001I> Server starting.
    [2009-10-14 16:16:45.319] main                     <SPOF0001I> OSGi telnet console available on port 2401.
    [2009-10-14 16:16:46.678] main                     <SPKE0000I> Boot subsystems installed.
    [2009-10-14 16:16:47.335] main                     <SPKE0001I> Base subsystems installed.
    [2009-10-14 16:16:48.007] server-dm-14             <SPPM0000I> Installing profile 'web'.
    [2009-10-14 16:16:48.507] server-dm-14             <SPPM0001I> Installed profile 'web'.
    [2009-10-14 16:16:48.569] server-dm-4              <SPSC0001I> Creating HTTP/1.1 connector with scheme http on port 8080.
    [2009-10-14 16:16:48.585] server-dm-4              <SPSC0001I> Creating HTTP/1.1 connector with scheme https on port 8443.
    [2009-10-14 16:16:48.600] server-dm-4              <SPSC0001I> Creating AJP/1.3 connector with scheme http on port 8009.
    [2009-10-14 16:16:48.616] server-dm-4              <SPSC0000I> Starting ServletContainer.
    [2009-10-14 16:16:49.007] server-dm-10             <SPPM0002I> Server open for business with profile 'web'.
    [2009-10-14 16:16:49.241] Deployer Recovery        <SPSC1000I> Creating web application '/admin'.
    [2009-10-14 16:16:49.428] async-delivery-thread-1  <SPSC1001I> Starting web application '/admin'.
    [2009-10-14 16:16:49.741] Deployer Recovery        <SPDE0010I> Deployment of 'com.springsource.server.servlet.admin' version '1.0.2.SR02' completed.
    [2009-10-14 16:16:49.835] Deployer Recovery        <SPSC1000I> Creating web application '/'.
    [2009-10-14 16:16:49.928] async-delivery-thread-1  <SPSC1001I> Starting web application '/'.
    [2009-10-14 16:16:50.022] Deployer Recovery        <SPDE0010I> Deployment of 'com.springsource.server.servlet.splash' version '1.0.2.SR02' completed.
    [2009-10-14 16:16:50.038] fs-watcher               <SPDE0048I> Processing 'INITIAL' event for file 'server.admin.web-1.0.2.SR02.jar'.
    [2009-10-14 16:16:50.038] fs-watcher               <SPDE0031I> File 'server.admin.web-1.0.2.SR02.jar' already deployed.
    [2009-10-14 16:16:50.038] fs-watcher               <SPDE0048I> Processing 'INITIAL' event for file 'server.admin.splash-1.0.2.SR02.jar'.
    [2009-10-14 16:16:50.038] fs-watcher               <SPDE0031I> File 'server.admin.splash-1.0.2.SR02.jar' already deployed.
    [2009-10-14 16:16:51.163]  Connection(3)-127.0.0.1 <SPFF0002I> Wrote dump file "R:\bin\springsource\dm-server-1.0.2.SR02\serviceability\dump\2009-10-14_16-16-50.dump"
    java.lang.NullPointerException
    	at com.springsource.server.deployer.core.internal.StandardApplicationDeployer.getFileName(StandardApplicationDeployer.java:411)
    	at com.springsource.server.deployer.core.internal.StandardApplicationDeployer.deploy(StandardApplicationDeployer.java:303)
    	at com.springsource.server.deployer.controls.StandardDeployerControl.deploy(StandardDeployerControl.java:100)
    	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    	at java.lang.reflect.Method.invoke(Method.java:597)
    	at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:36)
    	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    	at java.lang.reflect.Method.invoke(Method.java:597)
    	at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:243)
    	at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1074)
    	at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:955)
    	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
    	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
    	at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1426)
    	at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
    	at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264)
    	at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1359)
    	at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)
    	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    	at java.lang.reflect.Method.invoke(Method.java:597)
    	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
    	at sun.rmi.transport.Transport$1.run(Transport.java:159)
    	at java.security.AccessController.doPrivileged(Native Method)
    	at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
    	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
    	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
    	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
    	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    	at java.lang.Thread.run(Thread.java:619)
    
    [2009-10-14 16:16:55.147]  Connection(5)-127.0.0.1 <SPFF0002I> Wrote dump file "R:\bin\springsource\dm-server-1.0.2.SR02\serviceability\dump\2009-10-14_16-16-54.dump"
    java.lang.NullPointerException
    	at com.springsource.server.deployer.core.internal.StandardApplicationDeployer.getFileName(StandardApplicationDeployer.java:411)
    	at com.springsource.server.deployer.core.internal.StandardApplicationDeployer.deploy(StandardApplicationDeployer.java:303)
    	at com.springsource.server.deployer.controls.StandardDeployerControl.deploy(StandardDeployerControl.java:100)
    	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    	at java.lang.reflect.Method.invoke(Method.java:597)
    	at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:36)
    	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    	at java.lang.reflect.Method.invoke(Method.java:597)
    	at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:243)
    	at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1074)
    	at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:955)
    	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
    	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
    	at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1426)
    	at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
    	at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264)
    	at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1359)
    	at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)
    	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    	at java.lang.reflect.Method.invoke(Method.java:597)
    	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
    	at sun.rmi.transport.Transport$1.run(Transport.java:159)
    	at java.security.AccessController.doPrivileged(Native Method)
    	at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
    	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
    	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
    	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
    	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    	at java.lang.Thread.run(Thread.java:619)
    Last edited by jchamlin; Oct 14th, 2009, 04:40 PM.

  • #2
    Sorry to hear that you're having problems. Which version of dm Server are you using? Judging by the log output, it looks like 1.0.x but it'd be great if you could confirm the version you're using before we start investigating.

    Comment


    • #3
      Also,

      could you please provide a sample project that shows this error for you (you can either attach it to a JIRA or send it to me at christian DOT dupuis AT springsource DOT com). That will help to greatly speed up the time to find the root cause of this.

      Also could you add some more details about your filesystem setup you are using? E.g. is drive R:\ a local or network drive?

      Thanks,

      Christian

      Comment


      • #4
        I am having the same problem (we're on the same development team) and posted without realizing J.C. had already posted this. (See http://forum.springsource.org/showthread.php?t=79164)

        This is with the 1.0.2.SR02 build of dm server (I did the same STS upgrade J.C. did, also tried with full 3.5.1 upgrade - see my referenced post). With 2.0.0.M5 dm server I get a dump file with a different exception, also in my referenced post. (Please check that out - maybe I said something there that will help us diagnose this problem.)

        The kicker here is that this only happens when deploying from STS - dropping the same bundle into the pickup folder of either server works fine, even if that server is started from STS (if that matters).

        We can email one of the bundles that fail for us (they all do - and they all worked fine prior to the STS upgrade), but I don't think you'll see the problem unless you follow the upgrade path we did.

        Comment


        • #5
          Another way we found we can make this fail with the same exception is to take a raw/virgin STS install and update the Spring dm Server tool plugins (in my case I had already put FindBugs and Subclipse in as well, unselecting the option to search all my update sites for updates to avoid the 3.5.1 upgrade).

          We need the Spring dm Server tools to get the Bundlor update which scans web.xml, but apparently this dm server tool update also causes the problem with STS deploying to the dm Server.

          Hopefully this additional information is helpful. Let me know if you want a JIRA created out of this.

          Comment


          • #6
            Follow-up: in a separate email thread with Christian, it appears as tho this will be fixed in the upcoming STS 2.2.0 release.

            Thanks!

            Comment

            Working...
            X