[Lift] Re: problems with tomcat
Update: The tomcat incompatability with the external server was caused by a Java version mismatch. I was compiling my scala code with a newer version of the JDK. I had an older JDK installed on the external server and this was causing a problem with some of my class files (but not others, oddly). Anyway, I updated my JDK version on the linux server and now the website is working correctly. Thanks for all the help! On Nov 17, 7:42 pm, Naftoli Gugenheim naftoli...@gmail.com wrote: If you call maven with the right parameter it will skip the tests. I think it's something like -Dmaven.tests.skip . - DavidVdavid.v.villa...@gmail.com wrote: More specifically, I am trying to follow the stack trace to lead me to some sort of URL so that I can see where and why this connection is trying to be made. I'm not sure why the AppTest needs to make a connection in the first place. Can I just skip the Test portion of the mvn package command? Or do I have hard code the proxy settings somewhere other than in my maven settings.xml file? I'm still struggling with this problem... On Nov 16, 10:54 am, DavidV david.v.villa...@gmail.com wrote: For the time being I have code that compiles correctly and I am leaving eclipse completely out of the picture. I am running Windows Vista 64bit. I have quit eclipse and tried to run a mvn clean install to rebuild my project, but I get the exact same error that I previously posted (ConnectException) regarding the AppTest failure when the install command executes the TESTS. Therefore, the build fails. ... --- T E S T S --- Running net.genomas.lift.test.AppTest Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.199 sec FA ILURE! Results : Tests in error: testXml(net.genomas.lift.test.AppTest) Tests run: 2, Failures: 0, Errors: 1, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. ... If I run the project with mvn cleantomcat:run it works fine because it doesn't execute the TESTS step. I think that myproblemswith remotetomcatserver may stem from eclipse messing up the correct maven packaging of the .war file. I'm still trying to figure out what is causing this ConnectException whenever AppTest.scala is executed that is preventing me from performing a normal mvn package On Nov 13, 6:39 pm, David Pollak feeder.of.the.be...@gmail.com wrote: On Fri, Nov 13, 2009 at 9:15 AM, DavidV david.v.villa...@gmail.com wrote: When running Lift-1.0.2 and Scala-2.7.5 I am able to compile and run my code through maven. However, I am concerned about my inability to run the mvn clean package command successfully without first running the clean command in eclipse. Yeah... Eclipse is generally a problem. Are you running Windows or Linux/Mac? Can you quite Eclipses before doing a build. I am afraid that this extra eclipse step may be interfering with the proper creation of the .war file which may be contributing to the problem. When I try to execute mvn clean package without eclipse I get the following error appearing in my surefire-report: --- Test set: net.genomas.lift.test.AppTest --- Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.251 sec FAILURE! testXml(net.genomas.lift.test.AppTest) Time elapsed: 1.228 sec ERROR! java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java: 195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:525) at java.net.Socket.connect(Socket.java:475) at sun.net.NetworkClient.doConnect(NetworkClient.java:163) at sun.net.www.http.HttpClient.openServer(HttpClient.java:394) at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) at sun.net.www.http.HttpClient.init(HttpClient.java:233) at sun.net.www.http.HttpClient.New(HttpClient.java:306) at sun.net.www.http.HttpClient.New(HttpClient.java:323) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient (HttpURLConnection.java:860) at
[Lift] Re: problems with tomcat
More specifically, I am trying to follow the stack trace to lead me to some sort of URL so that I can see where and why this connection is trying to be made. I'm not sure why the AppTest needs to make a connection in the first place. Can I just skip the Test portion of the mvn package command? Or do I have hard code the proxy settings somewhere other than in my maven settings.xml file? I'm still struggling with this problem... On Nov 16, 10:54 am, DavidV david.v.villa...@gmail.com wrote: For the time being I have code that compiles correctly and I am leaving eclipse completely out of the picture. I am running Windows Vista 64bit. I have quit eclipse and tried to run a mvn clean install to rebuild my project, but I get the exact same error that I previously posted (ConnectException) regarding the AppTest failure when the install command executes the TESTS. Therefore, the build fails. ... --- T E S T S --- Running net.genomas.lift.test.AppTest Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.199 sec FA ILURE! Results : Tests in error: testXml(net.genomas.lift.test.AppTest) Tests run: 2, Failures: 0, Errors: 1, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. ... If I run the project with mvn cleantomcat:run it works fine because it doesn't execute the TESTS step. I think that my problems with remotetomcatserver may stem from eclipse messing up the correct maven packaging of the .war file. I'm still trying to figure out what is causing this ConnectException whenever AppTest.scala is executed that is preventing me from performing a normal mvn package On Nov 13, 6:39 pm, David Pollak feeder.of.the.be...@gmail.com wrote: On Fri, Nov 13, 2009 at 9:15 AM, DavidV david.v.villa...@gmail.com wrote: When running Lift-1.0.2 and Scala-2.7.5 I am able to compile and run my code through maven. However, I am concerned about my inability to run the mvn clean package command successfully without first running the clean command in eclipse. Yeah... Eclipse is generally a problem. Are you running Windows or Linux/Mac? Can you quite Eclipses before doing a build. I am afraid that this extra eclipse step may be interfering with the proper creation of the .war file which may be contributing to the problem. When I try to execute mvn clean package without eclipse I get the following error appearing in my surefire-report: --- Test set: net.genomas.lift.test.AppTest --- Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.251 sec FAILURE! testXml(net.genomas.lift.test.AppTest) Time elapsed: 1.228 sec ERROR! java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java: 195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:525) at java.net.Socket.connect(Socket.java:475) at sun.net.NetworkClient.doConnect(NetworkClient.java:163) at sun.net.www.http.HttpClient.openServer(HttpClient.java:394) at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) at sun.net.www.http.HttpClient.init(HttpClient.java:233) at sun.net.www.http.HttpClient.New(HttpClient.java:306) at sun.net.www.http.HttpClient.New(HttpClient.java:323) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient (HttpURLConnection.java:860) at sun.net.www.protocol.http.HttpURLConnection.plainConnect (HttpURLConnection.java:801) at sun.net.www.protocol.http.HttpURLConnection.connect (HttpURLConnection.java:726) at sun.net.www.protocol.http.HttpURLConnection.getInputStream (HttpURLConnection.java:1049) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity (XMLEntityManager.java:677) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity (XMLEntityManager.java:1315) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity (XMLEntityManager.java:1282) at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.setInputSource (XMLDTDScannerImpl.java:283) at
[Lift] Re: problems with tomcat
I skipped the Test portion of mvn package by removing the testCompile goal from my pom file under the maven-scala-plugin. War packaging is now working correctly, but the webapp still isn't deploying on the remote Tomcat server...will keep at it and will post my solution if I find one... I think it still has to do with my database connection On Nov 17, 10:41 am, DavidV david.v.villa...@gmail.com wrote: More specifically, I am trying to follow the stack trace to lead me to some sort of URL so that I can see where and why this connection is trying to be made. I'm not sure why the AppTest needs to make a connection in the first place. Can I just skip the Test portion of the mvn package command? Or do I have hard code the proxy settings somewhere other than in my maven settings.xml file? I'm still struggling with this problem... On Nov 16, 10:54 am, DavidV david.v.villa...@gmail.com wrote: For the time being I have code that compiles correctly and I am leaving eclipse completely out of the picture. I am running Windows Vista 64bit. I have quit eclipse and tried to run a mvn clean install to rebuild my project, but I get the exact same error that I previously posted (ConnectException) regarding the AppTest failure when the install command executes the TESTS. Therefore, the build fails. ... --- T E S T S --- Running net.genomas.lift.test.AppTest Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.199 sec FA ILURE! Results : Tests in error: testXml(net.genomas.lift.test.AppTest) Tests run: 2, Failures: 0, Errors: 1, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. ... If I run the project with mvn cleantomcat:run it works fine because it doesn't execute the TESTS step. I think that my problems with remotetomcatserver may stem from eclipse messing up the correct maven packaging of the .war file. I'm still trying to figure out what is causing this ConnectException whenever AppTest.scala is executed that is preventing me from performing a normal mvn package On Nov 13, 6:39 pm, David Pollak feeder.of.the.be...@gmail.com wrote: On Fri, Nov 13, 2009 at 9:15 AM, DavidV david.v.villa...@gmail.com wrote: When running Lift-1.0.2 and Scala-2.7.5 I am able to compile and run my code through maven. However, I am concerned about my inability to run the mvn clean package command successfully without first running the clean command in eclipse. Yeah... Eclipse is generally a problem. Are you running Windows or Linux/Mac? Can you quite Eclipses before doing a build. I am afraid that this extra eclipse step may be interfering with the proper creation of the .war file which may be contributing to the problem. When I try to execute mvn clean package without eclipse I get the following error appearing in my surefire-report: --- Test set: net.genomas.lift.test.AppTest --- Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.251 sec FAILURE! testXml(net.genomas.lift.test.AppTest) Time elapsed: 1.228 sec ERROR! java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java: 195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:525) at java.net.Socket.connect(Socket.java:475) at sun.net.NetworkClient.doConnect(NetworkClient.java:163) at sun.net.www.http.HttpClient.openServer(HttpClient.java:394) at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) at sun.net.www.http.HttpClient.init(HttpClient.java:233) at sun.net.www.http.HttpClient.New(HttpClient.java:306) at sun.net.www.http.HttpClient.New(HttpClient.java:323) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient (HttpURLConnection.java:860) at sun.net.www.protocol.http.HttpURLConnection.plainConnect (HttpURLConnection.java:801) at sun.net.www.protocol.http.HttpURLConnection.connect (HttpURLConnection.java:726) at sun.net.www.protocol.http.HttpURLConnection.getInputStream (HttpURLConnection.java:1049) at
Re: [Lift] Re: problems with tomcat
Just delete the AppTest.scala file. On Tue, Nov 17, 2009 at 7:41 AM, DavidV david.v.villa...@gmail.com wrote: More specifically, I am trying to follow the stack trace to lead me to some sort of URL so that I can see where and why this connection is trying to be made. I'm not sure why the AppTest needs to make a connection in the first place. Can I just skip the Test portion of the mvn package command? Or do I have hard code the proxy settings somewhere other than in my maven settings.xml file? I'm still struggling with this problem... On Nov 16, 10:54 am, DavidV david.v.villa...@gmail.com wrote: For the time being I have code that compiles correctly and I am leaving eclipse completely out of the picture. I am running Windows Vista 64bit. I have quit eclipse and tried to run a mvn clean install to rebuild my project, but I get the exact same error that I previously posted (ConnectException) regarding the AppTest failure when the install command executes the TESTS. Therefore, the build fails. ... --- T E S T S --- Running net.genomas.lift.test.AppTest Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.199 sec FA ILURE! Results : Tests in error: testXml(net.genomas.lift.test.AppTest) Tests run: 2, Failures: 0, Errors: 1, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. ... If I run the project with mvn cleantomcat:run it works fine because it doesn't execute the TESTS step. I think that my problems with remotetomcatserver may stem from eclipse messing up the correct maven packaging of the .war file. I'm still trying to figure out what is causing this ConnectException whenever AppTest.scala is executed that is preventing me from performing a normal mvn package On Nov 13, 6:39 pm, David Pollak feeder.of.the.be...@gmail.com wrote: On Fri, Nov 13, 2009 at 9:15 AM, DavidV david.v.villa...@gmail.com wrote: When running Lift-1.0.2 and Scala-2.7.5 I am able to compile and run my code through maven. However, I am concerned about my inability to run the mvn clean package command successfully without first running the clean command in eclipse. Yeah... Eclipse is generally a problem. Are you running Windows or Linux/Mac? Can you quite Eclipses before doing a build. I am afraid that this extra eclipse step may be interfering with the proper creation of the .war file which may be contributing to the problem. When I try to execute mvn clean package without eclipse I get the following error appearing in my surefire-report: --- Test set: net.genomas.lift.test.AppTest --- Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.251 sec FAILURE! testXml(net.genomas.lift.test.AppTest) Time elapsed: 1.228 sec ERROR! java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java: 195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:525) at java.net.Socket.connect(Socket.java:475) at sun.net.NetworkClient.doConnect(NetworkClient.java:163) at sun.net.www.http.HttpClient.openServer(HttpClient.java:394) at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) at sun.net.www.http.HttpClient.init(HttpClient.java:233) at sun.net.www.http.HttpClient.New(HttpClient.java:306) at sun.net.www.http.HttpClient.New(HttpClient.java:323) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient (HttpURLConnection.java:860) at sun.net.www.protocol.http.HttpURLConnection.plainConnect (HttpURLConnection.java:801) at sun.net.www.protocol.http.HttpURLConnection.connect (HttpURLConnection.java:726) at sun.net.www.protocol.http.HttpURLConnection.getInputStream (HttpURLConnection.java:1049) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity (XMLEntityManager.java:677) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity (XMLEntityManager.java:1315) at
Re: [Lift] Re: problems with tomcat
If you call maven with the right parameter it will skip the tests. I think it's something like -Dmaven.tests.skip . - DavidVdavid.v.villa...@gmail.com wrote: More specifically, I am trying to follow the stack trace to lead me to some sort of URL so that I can see where and why this connection is trying to be made. I'm not sure why the AppTest needs to make a connection in the first place. Can I just skip the Test portion of the mvn package command? Or do I have hard code the proxy settings somewhere other than in my maven settings.xml file? I'm still struggling with this problem... On Nov 16, 10:54 am, DavidV david.v.villa...@gmail.com wrote: For the time being I have code that compiles correctly and I am leaving eclipse completely out of the picture. I am running Windows Vista 64bit. I have quit eclipse and tried to run a mvn clean install to rebuild my project, but I get the exact same error that I previously posted (ConnectException) regarding the AppTest failure when the install command executes the TESTS. Therefore, the build fails. ... --- T E S T S --- Running net.genomas.lift.test.AppTest Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.199 sec FA ILURE! Results : Tests in error: testXml(net.genomas.lift.test.AppTest) Tests run: 2, Failures: 0, Errors: 1, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. ... If I run the project with mvn cleantomcat:run it works fine because it doesn't execute the TESTS step. I think that my problems with remotetomcatserver may stem from eclipse messing up the correct maven packaging of the .war file. I'm still trying to figure out what is causing this ConnectException whenever AppTest.scala is executed that is preventing me from performing a normal mvn package On Nov 13, 6:39 pm, David Pollak feeder.of.the.be...@gmail.com wrote: On Fri, Nov 13, 2009 at 9:15 AM, DavidV david.v.villa...@gmail.com wrote: When running Lift-1.0.2 and Scala-2.7.5 I am able to compile and run my code through maven. However, I am concerned about my inability to run the mvn clean package command successfully without first running the clean command in eclipse. Yeah... Eclipse is generally a problem. Are you running Windows or Linux/Mac? Can you quite Eclipses before doing a build. I am afraid that this extra eclipse step may be interfering with the proper creation of the .war file which may be contributing to the problem. When I try to execute mvn clean package without eclipse I get the following error appearing in my surefire-report: --- Test set: net.genomas.lift.test.AppTest --- Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.251 sec FAILURE! testXml(net.genomas.lift.test.AppTest) Time elapsed: 1.228 sec ERROR! java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java: 195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:525) at java.net.Socket.connect(Socket.java:475) at sun.net.NetworkClient.doConnect(NetworkClient.java:163) at sun.net.www.http.HttpClient.openServer(HttpClient.java:394) at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) at sun.net.www.http.HttpClient.init(HttpClient.java:233) at sun.net.www.http.HttpClient.New(HttpClient.java:306) at sun.net.www.http.HttpClient.New(HttpClient.java:323) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient (HttpURLConnection.java:860) at sun.net.www.protocol.http.HttpURLConnection.plainConnect (HttpURLConnection.java:801) at sun.net.www.protocol.http.HttpURLConnection.connect (HttpURLConnection.java:726) at sun.net.www.protocol.http.HttpURLConnection.getInputStream (HttpURLConnection.java:1049) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity (XMLEntityManager.java:677) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity (XMLEntityManager.java:1315) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity
[Lift] Re: problems with tomcat
For the time being I have code that compiles correctly and I am leaving eclipse completely out of the picture. I am running Windows Vista 64bit. I have quit eclipse and tried to run a mvn clean install to rebuild my project, but I get the exact same error that I previously posted (ConnectException) regarding the AppTest failure when the install command executes the TESTS. Therefore, the build fails. ... --- T E S T S --- Running net.genomas.lift.test.AppTest Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.199 sec FA ILURE! Results : Tests in error: testXml(net.genomas.lift.test.AppTest) Tests run: 2, Failures: 0, Errors: 1, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. ... If I run the project with mvn clean tomcat:run it works fine because it doesn't execute the TESTS step. I think that my problems with remote tomcat server may stem from eclipse messing up the correct maven packaging of the .war file. I'm still trying to figure out what is causing this ConnectException whenever AppTest.scala is executed that is preventing me from performing a normal mvn package On Nov 13, 6:39 pm, David Pollak feeder.of.the.be...@gmail.com wrote: On Fri, Nov 13, 2009 at 9:15 AM, DavidV david.v.villa...@gmail.com wrote: When running Lift-1.0.2 and Scala-2.7.5 I am able to compile and run my code through maven. However, I am concerned about my inability to run the mvn clean package command successfully without first running the clean command in eclipse. Yeah... Eclipse is generally a problem. Are you running Windows or Linux/Mac? Can you quite Eclipses before doing a build. I am afraid that this extra eclipse step may be interfering with the proper creation of the .war file which may be contributing to the problem. When I try to execute mvn clean package without eclipse I get the following error appearing in my surefire-report: --- Test set: net.genomas.lift.test.AppTest --- Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.251 sec FAILURE! testXml(net.genomas.lift.test.AppTest) Time elapsed: 1.228 sec ERROR! java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java: 195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:525) at java.net.Socket.connect(Socket.java:475) at sun.net.NetworkClient.doConnect(NetworkClient.java:163) at sun.net.www.http.HttpClient.openServer(HttpClient.java:394) at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) at sun.net.www.http.HttpClient.init(HttpClient.java:233) at sun.net.www.http.HttpClient.New(HttpClient.java:306) at sun.net.www.http.HttpClient.New(HttpClient.java:323) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient (HttpURLConnection.java:860) at sun.net.www.protocol.http.HttpURLConnection.plainConnect (HttpURLConnection.java:801) at sun.net.www.protocol.http.HttpURLConnection.connect (HttpURLConnection.java:726) at sun.net.www.protocol.http.HttpURLConnection.getInputStream (HttpURLConnection.java:1049) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity (XMLEntityManager.java:677) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity (XMLEntityManager.java:1315) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity (XMLEntityManager.java:1282) at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.setInputSource (XMLDTDScannerImpl.java:283) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl $DTDDriver.dispatch(XMLDocumentScannerImpl.java:1193) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl $DTDDriver.next(XMLDocumentScannerImpl.java:1090) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl $PrologDriver.next(XMLDocumentScannerImpl.java:1003) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next (XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument
[Lift] Re: problems with tomcat
When running Lift-1.0.2 and Scala-2.7.5 I am able to compile and run my code through maven. However, I am concerned about my inability to run the mvn clean package command successfully without first running the clean command in eclipse. I am afraid that this extra eclipse step may be interfering with the proper creation of the .war file which may be contributing to the problem. When I try to execute mvn clean package without eclipse I get the following error appearing in my surefire-report: --- Test set: net.genomas.lift.test.AppTest --- Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.251 sec FAILURE! testXml(net.genomas.lift.test.AppTest) Time elapsed: 1.228 sec ERROR! java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java: 195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:525) at java.net.Socket.connect(Socket.java:475) at sun.net.NetworkClient.doConnect(NetworkClient.java:163) at sun.net.www.http.HttpClient.openServer(HttpClient.java:394) at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) at sun.net.www.http.HttpClient.init(HttpClient.java:233) at sun.net.www.http.HttpClient.New(HttpClient.java:306) at sun.net.www.http.HttpClient.New(HttpClient.java:323) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient (HttpURLConnection.java:860) at sun.net.www.protocol.http.HttpURLConnection.plainConnect (HttpURLConnection.java:801) at sun.net.www.protocol.http.HttpURLConnection.connect (HttpURLConnection.java:726) at sun.net.www.protocol.http.HttpURLConnection.getInputStream (HttpURLConnection.java:1049) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity (XMLEntityManager.java:677) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity (XMLEntityManager.java:1315) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity (XMLEntityManager.java:1282) at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.setInputSource (XMLDTDScannerImpl.java:283) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl $DTDDriver.dispatch(XMLDocumentScannerImpl.java:1193) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl $DTDDriver.next(XMLDocumentScannerImpl.java:1090) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl $PrologDriver.next(XMLDocumentScannerImpl.java:1003) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next (XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument (XMLDocumentFragmentScannerImpl.java:510) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse (XML11Configuration.java:807) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse (XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse (XMLParser.java:107) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse (AbstractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl $JAXPSAXParser.parse(SAXParserImpl.java:522) at javax.xml.parsers.SAXParser.parse(SAXParser.java:395) at scala.xml.parsing.FactoryAdapter.loadXML(FactoryAdapter.scala:292) at scala.xml.parsing.NoBindingFactoryAdapter.loadXML (NoBindingFactoryAdapter.scala:60) at scala.xml.XML$.loadFile(XML.scala:42) at net.genomas.lift.test.AppTest.wellFormed$1(AppTest.scala:52) at net.genomas.lift.test.AppTest$$anonfun$wellFormed$1$1.apply (AppTest.scala:48) at net.genomas.lift.test.AppTest$$anonfun$wellFormed$1$1.apply (AppTest.scala:48) at scala.Iterator$class.foreach(Iterator.scala:414) at scala.runtime.BoxedArray$AnyIterator.foreach(BoxedArray.scala:45) at scala.Iterable$class.foreach(Iterable.scala:256) at scala.runtime.BoxedArray.foreach(BoxedArray.scala:24) at net.genomas.lift.test.AppTest.wellFormed$1(AppTest.scala:48) at net.genomas.lift.test.AppTest$$anonfun$wellFormed$1$1.apply (AppTest.scala:48) at net.genomas.lift.test.AppTest$$anonfun$wellFormed$1$1.apply (AppTest.scala:48) at scala.Iterator$class.foreach(Iterator.scala:414) at scala.runtime.BoxedArray$AnyIterator.foreach(BoxedArray.scala:45) at
[Lift] Re: problems with tomcat
On Fri, Nov 13, 2009 at 9:15 AM, DavidV david.v.villa...@gmail.com wrote: When running Lift-1.0.2 and Scala-2.7.5 I am able to compile and run my code through maven. However, I am concerned about my inability to run the mvn clean package command successfully without first running the clean command in eclipse. Yeah... Eclipse is generally a problem. Are you running Windows or Linux/Mac? Can you quite Eclipses before doing a build. I am afraid that this extra eclipse step may be interfering with the proper creation of the .war file which may be contributing to the problem. When I try to execute mvn clean package without eclipse I get the following error appearing in my surefire-report: --- Test set: net.genomas.lift.test.AppTest --- Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.251 sec FAILURE! testXml(net.genomas.lift.test.AppTest) Time elapsed: 1.228 sec ERROR! java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java: 195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:525) at java.net.Socket.connect(Socket.java:475) at sun.net.NetworkClient.doConnect(NetworkClient.java:163) at sun.net.www.http.HttpClient.openServer(HttpClient.java:394) at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) at sun.net.www.http.HttpClient.init(HttpClient.java:233) at sun.net.www.http.HttpClient.New(HttpClient.java:306) at sun.net.www.http.HttpClient.New(HttpClient.java:323) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient (HttpURLConnection.java:860) at sun.net.www.protocol.http.HttpURLConnection.plainConnect (HttpURLConnection.java:801) at sun.net.www.protocol.http.HttpURLConnection.connect (HttpURLConnection.java:726) at sun.net.www.protocol.http.HttpURLConnection.getInputStream (HttpURLConnection.java:1049) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity (XMLEntityManager.java:677) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity (XMLEntityManager.java:1315) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity (XMLEntityManager.java:1282) at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.setInputSource (XMLDTDScannerImpl.java:283) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl $DTDDriver.dispatch(XMLDocumentScannerImpl.java:1193) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl $DTDDriver.next(XMLDocumentScannerImpl.java:1090) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl $PrologDriver.next(XMLDocumentScannerImpl.java:1003) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next (XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument (XMLDocumentFragmentScannerImpl.java:510) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse (XML11Configuration.java:807) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse (XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse (XMLParser.java:107) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse (AbstractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl $JAXPSAXParser.parse(SAXParserImpl.java:522) at javax.xml.parsers.SAXParser.parse(SAXParser.java:395) at scala.xml.parsing.FactoryAdapter.loadXML(FactoryAdapter.scala:292) at scala.xml.parsing.NoBindingFactoryAdapter.loadXML (NoBindingFactoryAdapter.scala:60) at scala.xml.XML$.loadFile(XML.scala:42) Just comment out the test for now. at net.genomas.lift.test.AppTest.wellFormed$1(AppTest.scala:52) at net.genomas.lift.test.AppTest$$anonfun$wellFormed$1$1.apply (AppTest.scala:48) at net.genomas.lift.test.AppTest$$anonfun$wellFormed$1$1.apply (AppTest.scala:48) at scala.Iterator$class.foreach(Iterator.scala:414) at scala.runtime.BoxedArray$AnyIterator.foreach(BoxedArray.scala:45) at scala.Iterable$class.foreach(Iterable.scala:256) at scala.runtime.BoxedArray.foreach(BoxedArray.scala:24) at net.genomas.lift.test.AppTest.wellFormed$1(AppTest.scala:48) at
[Lift] Re: problems with tomcat
Have you got any conflicting jars in TOMCAT_HOME/lib ? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: problems with tomcat
What version of Lift are you using? If it's Lift 1.1-M7 or 1.1-SNAPSHOT, please make sure you've got the Scala version set to 2.7.7 If you're using Eclipse for development, please make sure to do a mvn *clean * package to build your WAR file. The clean phase is super important. On Thu, Nov 12, 2009 at 11:07 AM, DavidV david.v.villa...@gmail.com wrote: I am having some issues deploying my Lift web application to a tomcat server. When I run tomcat through maven (mvn tomcat:run), the web application works properly and connects to my postgres database. However, when I use mvn package to create a war file which I then deploy to a local tomcat server (on my computer) only the HTML of the web application appears and the snippets with the application's content fail. It appears to be a problem with the sitemap loading properly, because I changed the sitemap by deleting one of many Loc.If parameters and the web application then worked as expected. However, when I then tried to deploy the same .war file to a tomcat server on a different computer, the web app failed again, showing only the HTML and not the snippets. I suspect that perhaps this is because I need to change my url to the postgres database, but I've tried many permutations of the url and none seem to work. To make things worse, the logging doesn't seem to be working properly making it difficult to diagnose the exact problem. I can't locate a stdout.log file anywhere. In my catalina.out file I get the following error: java.lang.NullPointerException at scala.runtime.BoxesRunTime.boxToInteger(Unknown Source) at scala.actors.Actor$$anonfun$scala$actors$Actor$$seq$1.apply (Actor.scala:800) at scala.actors.Actor$$anonfun$scala$actors$Actor$$seq$1.apply (Actor.scala:794) at scala.actors.Reaction.run(Reaction.scala:82) at net.liftweb.http.ActorSchedulerFixer$$anon$1$$anon$3.run (LiftServlet.scala:673) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask (ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) I also get an error that says: log4j:WARN Please initialize the log4j system properly. Do I need to configure log4j in order to get the stdout.log file? Any ideas of what might be going on here? Thanks, David -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Surf the harmonics --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: problems with tomcat
I don't appear to have any conflicting jars in my TOMCAT_HOME/common/ lib folder, however, I am now realizing that I have a postgres jdbc3 .jar file in there and I am using a jdbc4 .jar postres file in my webapp. Perhaps that is the problem? I'll check that out. I am using Lift 1.0.1 with Scala version 2.7.5 It does work with the tomcat on my computer, which leads me to believe that it should be compatible with the current versions of Lift/Scala that I'm using. Maybe that's an incorrect assumption though, as I'm not very familiar with tomcat. On Nov 12, 2:15 pm, David Pollak feeder.of.the.be...@gmail.com wrote: What version of Lift are you using? If it's Lift 1.1-M7 or 1.1-SNAPSHOT, please make sure you've got the Scala version set to 2.7.7 If you're using Eclipse for development, please make sure to do a mvn *clean * package to build your WAR file. The clean phase is super important. On Thu, Nov 12, 2009 at 11:07 AM, DavidV david.v.villa...@gmail.com wrote: I am having some issues deploying my Lift web application to a tomcat server. When I run tomcat through maven (mvn tomcat:run), the web application works properly and connects to my postgres database. However, when I use mvn package to create a war file which I then deploy to a local tomcat server (on my computer) only the HTML of the web application appears and the snippets with the application's content fail. It appears to be a problem with the sitemap loading properly, because I changed the sitemap by deleting one of many Loc.If parameters and the web application then worked as expected. However, when I then tried to deploy the same .war file to a tomcat server on a different computer, the web app failed again, showing only the HTML and not the snippets. I suspect that perhaps this is because I need to change my url to the postgres database, but I've tried many permutations of the url and none seem to work. To make things worse, the logging doesn't seem to be working properly making it difficult to diagnose the exact problem. I can't locate a stdout.log file anywhere. In my catalina.out file I get the following error: java.lang.NullPointerException at scala.runtime.BoxesRunTime.boxToInteger(Unknown Source) at scala.actors.Actor$$anonfun$scala$actors$Actor$$seq$1.apply (Actor.scala:800) at scala.actors.Actor$$anonfun$scala$actors$Actor$$seq$1.apply (Actor.scala:794) at scala.actors.Reaction.run(Reaction.scala:82) at net.liftweb.http.ActorSchedulerFixer$$anon$1$$anon$3.run (LiftServlet.scala:673) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask (ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) I also get an error that says: log4j:WARN Please initialize the log4j system properly. Do I need to configure log4j in order to get the stdout.log file? Any ideas of what might be going on here? Thanks, David -- Lift, the simply functional web frameworkhttp://liftweb.net Beginning Scalahttp://www.apress.com/book/view/1430219890 Follow me:http://twitter.com/dpp Surf the harmonics --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: problems with tomcat
On Thu, Nov 12, 2009 at 11:36 AM, DavidV david.v.villa...@gmail.com wrote: I don't appear to have any conflicting jars in my TOMCAT_HOME/common/ lib folder, however, I am now realizing that I have a postgres jdbc3 .jar file in there and I am using a jdbc4 .jar postres file in my webapp. Perhaps that is the problem? I'll check that out. I am using Lift 1.0.1 with Scala version 2.7.5 Please use Lift 1.0.2 Please delete ~/.m2 (or whereever your Maven repository is) Please do a mvn clean install Then test locally (mvn tomcat:run) If it works, copy to your other Tomcat instance and see how things work. It does work with the tomcat on my computer, which leads me to believe that it should be compatible with the current versions of Lift/Scala that I'm using. Maybe that's an incorrect assumption though, as I'm not very familiar with tomcat. On Nov 12, 2:15 pm, David Pollak feeder.of.the.be...@gmail.com wrote: What version of Lift are you using? If it's Lift 1.1-M7 or 1.1-SNAPSHOT, please make sure you've got the Scala version set to 2.7.7 If you're using Eclipse for development, please make sure to do a mvn *clean * package to build your WAR file. The clean phase is super important. On Thu, Nov 12, 2009 at 11:07 AM, DavidV david.v.villa...@gmail.com wrote: I am having some issues deploying my Lift web application to a tomcat server. When I run tomcat through maven (mvn tomcat:run), the web application works properly and connects to my postgres database. However, when I use mvn package to create a war file which I then deploy to a local tomcat server (on my computer) only the HTML of the web application appears and the snippets with the application's content fail. It appears to be a problem with the sitemap loading properly, because I changed the sitemap by deleting one of many Loc.If parameters and the web application then worked as expected. However, when I then tried to deploy the same .war file to a tomcat server on a different computer, the web app failed again, showing only the HTML and not the snippets. I suspect that perhaps this is because I need to change my url to the postgres database, but I've tried many permutations of the url and none seem to work. To make things worse, the logging doesn't seem to be working properly making it difficult to diagnose the exact problem. I can't locate a stdout.log file anywhere. In my catalina.out file I get the following error: java.lang.NullPointerException at scala.runtime.BoxesRunTime.boxToInteger(Unknown Source) at scala.actors.Actor$$anonfun$scala$actors$Actor$$seq$1.apply (Actor.scala:800) at scala.actors.Actor$$anonfun$scala$actors$Actor$$seq$1.apply (Actor.scala:794) at scala.actors.Reaction.run(Reaction.scala:82) at net.liftweb.http.ActorSchedulerFixer$$anon$1$$anon$3.run (LiftServlet.scala:673) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask (ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) I also get an error that says: log4j:WARN Please initialize the log4j system properly. Do I need to configure log4j in order to get the stdout.log file? Any ideas of what might be going on here? Thanks, David -- Lift, the simply functional web frameworkhttp://liftweb.net Beginning Scalahttp://www.apress.com/book/view/1430219890 Follow me:http://twitter.com/dpp Surf the harmonics -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Surf the harmonics --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: problems with tomcat
On a side note, while I'm installing Lift 1.0.2 with Scala2.7.5, I always execute a clean command before the mvn package. However, I also need to execute a clean in eclipse before the mvn package works properly. Otherwise, I get this error: --- T E S T S --- Running net.genomas.lift.test.AppTest Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.258 sec FA ILURE! Results : Tests in error: testXml(net.genomas.lift.test.AppTest) Tests run: 2, Failures: 0, Errors: 1, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. Please refer to c:\Source\trunk\eclipse\testLift\target\surefire- reports for the individual test results. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 32 seconds [INFO] Finished at: Thu Nov 12 15:21:06 EST 2009 [INFO] Final Memory: 29M/53M [INFO] I now have Lift-1.0.2 and Scala 2.7.7 and am testing with tomcat. On Nov 12, 2:43 pm, David Pollak feeder.of.the.be...@gmail.com wrote: On Thu, Nov 12, 2009 at 11:36 AM, DavidV david.v.villa...@gmail.com wrote: I don't appear to have any conflicting jars in my TOMCAT_HOME/common/ lib folder, however, I am now realizing that I have a postgres jdbc3 .jar file in there and I am using a jdbc4 .jar postres file in my webapp. Perhaps that is the problem? I'll check that out. I am using Lift 1.0.1 with Scala version 2.7.5 Please use Lift 1.0.2 Please delete ~/.m2 (or whereever your Maven repository is) Please do a mvn clean install Then test locally (mvn tomcat:run) If it works, copy to your other Tomcat instance and see how things work. It does work with the tomcat on my computer, which leads me to believe that it should be compatible with the current versions of Lift/Scala that I'm using. Maybe that's an incorrect assumption though, as I'm not very familiar with tomcat. On Nov 12, 2:15 pm, David Pollak feeder.of.the.be...@gmail.com wrote: What version of Lift are you using? If it's Lift 1.1-M7 or 1.1-SNAPSHOT, please make sure you've got the Scala version set to 2.7.7 If you're using Eclipse for development, please make sure to do a mvn *clean * package to build your WAR file. The clean phase is super important. On Thu, Nov 12, 2009 at 11:07 AM, DavidV david.v.villa...@gmail.com wrote: I am having some issues deploying my Lift web application to a tomcat server. When I run tomcat through maven (mvn tomcat:run), the web application works properly and connects to my postgres database. However, when I use mvn package to create a war file which I then deploy to a local tomcat server (on my computer) only the HTML of the web application appears and the snippets with the application's content fail. It appears to be a problem with the sitemap loading properly, because I changed the sitemap by deleting one of many Loc.If parameters and the web application then worked as expected. However, when I then tried to deploy the same .war file to a tomcat server on a different computer, the web app failed again, showing only the HTML and not the snippets. I suspect that perhaps this is because I need to change my url to the postgres database, but I've tried many permutations of the url and none seem to work. To make things worse, the logging doesn't seem to be working properly making it difficult to diagnose the exact problem. I can't locate a stdout.log file anywhere. In my catalina.out file I get the following error: java.lang.NullPointerException at scala.runtime.BoxesRunTime.boxToInteger(Unknown Source) at scala.actors.Actor$$anonfun$scala$actors$Actor$$seq$1.apply (Actor.scala:800) at scala.actors.Actor$$anonfun$scala$actors$Actor$$seq$1.apply (Actor.scala:794) at scala.actors.Reaction.run(Reaction.scala:82) at net.liftweb.http.ActorSchedulerFixer$$anon$1$$anon$3.run (LiftServlet.scala:673) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask (ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) I also get an error that says: log4j:WARN Please initialize the log4j system properly. Do I need to configure log4j in order to get the stdout.log file? Any ideas of what might be going on here? Thanks, David --
[Lift] Re: problems with tomcat
I just tried to run the same code that used to work with Lift-1.0.1
and Scala 2.7.5 with my updates to Lift 1.0.1 and Scala 2.7.7 and I
got the following error:
[INFO] [tomcat:run {execution: default-cli}]
[INFO] Running war on http://localhost:8080/portal
[INFO] Creating Tomcat server configuration at c:\Source\trunk\eclipse
\testLift\
target\tomcat
Nov 12, 2009 3:36:51 PM org.apache.catalina.startup.Embedded start
INFO: Starting tomcat server
Nov 12, 2009 3:36:51 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.16
Nov 12, 2009 3:36:53 PM org.apache.catalina.core.StandardContext
filterStart
SEVERE: Exception starting filter LiftFilter
java.lang.AbstractMethodError
at scala.actors.Scheduler$.impl(Scheduler.scala:35)
at scala.actors.Scheduler$.execute(Scheduler.scala:101)
at scala.actors.Actor$class.start(Actor.scala:783)
at net.liftweb.http.PointlessActorToWorkAroundBug$.start
(LiftServlet.sca
la:702)
at net.liftweb.http.PointlessActorToWorkAroundBug$.ctor
(LiftServlet.scal
a:767)
at net.liftweb.http.PointlessActorToWorkAroundBug$.init
(LiftServlet.sc
ala:776)
at net.liftweb.http.PointlessActorToWorkAroundBug$.clinit
(LiftServlet.
scala)
at net.liftweb.http.LiftFilter.init(LiftServlet.scala:563)
at org.apache.catalina.core.ApplicationFilterConfig.getFilter
(Applicatio
nFilterConfig.java:275)
at
org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(Applica
tionFilterConfig.java:397)
at org.apache.catalina.core.ApplicationFilterConfig.init
(ApplicationFi
lterConfig.java:108)
at org.apache.catalina.core.StandardContext.filterStart
(StandardContext.
java:3709)
at org.apache.catalina.core.StandardContext.start
(StandardContext.java:4
356)
at org.apache.catalina.core.ContainerBase.start
(ContainerBase.java:1045)
at org.apache.catalina.core.StandardHost.start
(StandardHost.java:719)
at org.apache.catalina.core.ContainerBase.start
(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start
(StandardEngine.java:443
)
at org.apache.catalina.startup.Embedded.start(Embedded.java:
825)
at org.codehaus.mojo.tomcat.AbstractRunMojo.startContainer
(AbstractRunMo
jo.java:385)
at org.codehaus.mojo.tomcat.AbstractRunMojo.execute
(AbstractRunMojo.java
:144)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo
(DefaultPlugi
nManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
Goal(DefaultLifecycleExecutor.java:569)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:348)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLi
fecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:
328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:
138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main
(CompatibleMain.java:6
0)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced
(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode
(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Nov 12, 2009 3:36:53 PM org.apache.catalina.core.StandardContext start
SEVERE: Error filterStart
Nov 12, 2009 3:36:53 PM org.apache.catalina.core.StandardContext start
SEVERE: Context [/portal] startup failed due to previous errors
Nov 12, 2009 3:36:53 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Nov 12, 2009 3:36:54 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
This seems more consistent with whatever is happening on the external
tomcat server...
Thoughts? Also, any ideas about the test failures during the mvn
clean package command?
Thanks, I finally feel like I'm getting somewhere now!
-David
On Nov 12, 3:21 pm, DavidV david.v.villa...@gmail.com wrote:
On a side note, while I'm installing Lift 1.0.2 with Scala2.7.5, I
always execute a clean command
[Lift] Re: problems with tomcat
Another potentially helpful detail is that I get the same liftFilter
error when running on a local jetty server through maven as I do when
running on tomcat (also through maven). I am executing a clean
command before running the web app each and every time.
...
2009-11-12 16:10:05.833::WARN: failed LiftFilter:
java.lang.AbstractMethodError
2009-11-12 16:10:05.834::WARN: failed
org.mortbay.jetty.plugin.Jetty6PluginWebA
ppcont...@14c0275{/,C:\Source\trunk\eclipse\testLift\src\main\webapp}:
java.lang
.AbstractMethodError
...
On Nov 12, 3:40 pm, DavidV david.v.villa...@gmail.com wrote:
I just tried to run the same code that used to work with Lift-1.0.1
and Scala 2.7.5 with my updates to Lift 1.0.1 and Scala 2.7.7 and I
got the following error:
[INFO] [tomcat:run {execution: default-cli}]
[INFO] Running war onhttp://localhost:8080/portal
[INFO] Creating Tomcat server configuration at c:\Source\trunk\eclipse
\testLift\
target\tomcat
Nov 12, 2009 3:36:51 PM org.apache.catalina.startup.Embedded start
INFO: Starting tomcat server
Nov 12, 2009 3:36:51 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.16
Nov 12, 2009 3:36:53 PM org.apache.catalina.core.StandardContext
filterStart
SEVERE: Exception starting filterLiftFilter
java.lang.AbstractMethodError
at scala.actors.Scheduler$.impl(Scheduler.scala:35)
at scala.actors.Scheduler$.execute(Scheduler.scala:101)
at scala.actors.Actor$class.start(Actor.scala:783)
at net.liftweb.http.PointlessActorToWorkAroundBug$.start
(LiftServlet.sca
la:702)
at net.liftweb.http.PointlessActorToWorkAroundBug$.ctor
(LiftServlet.scal
a:767)
at net.liftweb.http.PointlessActorToWorkAroundBug$.init
(LiftServlet.sc
ala:776)
at net.liftweb.http.PointlessActorToWorkAroundBug$.clinit
(LiftServlet.
scala)
at net.liftweb.http.LiftFilter.init(LiftServlet.scala:563)
at org.apache.catalina.core.ApplicationFilterConfig.getFilter
(Applicatio
nFilterConfig.java:275)
at
org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(Applica
tionFilterConfig.java:397)
at org.apache.catalina.core.ApplicationFilterConfig.init
(ApplicationFi
lterConfig.java:108)
at org.apache.catalina.core.StandardContext.filterStart
(StandardContext.
java:3709)
at org.apache.catalina.core.StandardContext.start
(StandardContext.java:4
356)
at org.apache.catalina.core.ContainerBase.start
(ContainerBase.java:1045)
at org.apache.catalina.core.StandardHost.start
(StandardHost.java:719)
at org.apache.catalina.core.ContainerBase.start
(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start
(StandardEngine.java:443
)
at org.apache.catalina.startup.Embedded.start(Embedded.java:
825)
at org.codehaus.mojo.tomcat.AbstractRunMojo.startContainer
(AbstractRunMo
jo.java:385)
at org.codehaus.mojo.tomcat.AbstractRunMojo.execute
(AbstractRunMojo.java
:144)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo
(DefaultPlugi
nManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
Goal(DefaultLifecycleExecutor.java:569)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:348)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLi
fecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:
328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:
138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main
(CompatibleMain.java:6
0)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced
(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode
(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Nov 12, 2009 3:36:53 PM org.apache.catalina.core.StandardContext start
SEVERE: Error filterStart
Nov 12, 2009 3:36:53 PM
[Lift] Re: problems with tomcat
Scala is very, very, super ultra mega version fragile. This means that code
compiled with 2.7.5 will not work with code compiled with 2.7.7 and vice
versa.
So, in your pom.xml file, please set your scala version to 2.7.5 (nothing
else... not 2.7.4, not 2.7.7) and lift to 1.0.2
Then mvn clean tomcat:run -- does it work?
Then mvn clean install -- does the WAR file work in Tomcat?
On Thu, Nov 12, 2009 at 1:10 PM, DavidV david.v.villa...@gmail.com wrote:
Another potentially helpful detail is that I get the same liftFilter
error when running on a local jetty server through maven as I do when
running on tomcat (also through maven). I am executing a clean
command before running the web app each and every time.
...
2009-11-12 16:10:05.833::WARN: failed LiftFilter:
java.lang.AbstractMethodError
2009-11-12 16:10:05.834::WARN: failed
org.mortbay.jetty.plugin.Jetty6PluginWebA
ppcont...@14c0275{/,C:\Source\trunk\eclipse\testLift\src\main\webapp}:
java.lang
.AbstractMethodError
...
On Nov 12, 3:40 pm, DavidV david.v.villa...@gmail.com wrote:
I just tried to run the same code that used to work with Lift-1.0.1
and Scala 2.7.5 with my updates to Lift 1.0.1 and Scala 2.7.7 and I
got the following error:
[INFO] [tomcat:run {execution: default-cli}]
[INFO] Running war onhttp://localhost:8080/portal
[INFO] Creating Tomcat server configuration at c:\Source\trunk\eclipse
\testLift\
target\tomcat
Nov 12, 2009 3:36:51 PM org.apache.catalina.startup.Embedded start
INFO: Starting tomcat server
Nov 12, 2009 3:36:51 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.16
Nov 12, 2009 3:36:53 PM org.apache.catalina.core.StandardContext
filterStart
SEVERE: Exception starting filterLiftFilter
java.lang.AbstractMethodError
at scala.actors.Scheduler$.impl(Scheduler.scala:35)
at scala.actors.Scheduler$.execute(Scheduler.scala:101)
at scala.actors.Actor$class.start(Actor.scala:783)
at net.liftweb.http.PointlessActorToWorkAroundBug$.start
(LiftServlet.sca
la:702)
at net.liftweb.http.PointlessActorToWorkAroundBug$.ctor
(LiftServlet.scal
a:767)
at net.liftweb.http.PointlessActorToWorkAroundBug$.init
(LiftServlet.sc
ala:776)
at net.liftweb.http.PointlessActorToWorkAroundBug$.clinit
(LiftServlet.
scala)
at net.liftweb.http.LiftFilter.init(LiftServlet.scala:563)
at org.apache.catalina.core.ApplicationFilterConfig.getFilter
(Applicatio
nFilterConfig.java:275)
at
org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(Applica
tionFilterConfig.java:397)
at org.apache.catalina.core.ApplicationFilterConfig.init
(ApplicationFi
lterConfig.java:108)
at org.apache.catalina.core.StandardContext.filterStart
(StandardContext.
java:3709)
at org.apache.catalina.core.StandardContext.start
(StandardContext.java:4
356)
at org.apache.catalina.core.ContainerBase.start
(ContainerBase.java:1045)
at org.apache.catalina.core.StandardHost.start
(StandardHost.java:719)
at org.apache.catalina.core.ContainerBase.start
(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start
(StandardEngine.java:443
)
at org.apache.catalina.startup.Embedded.start(Embedded.java:
825)
at org.codehaus.mojo.tomcat.AbstractRunMojo.startContainer
(AbstractRunMo
jo.java:385)
at org.codehaus.mojo.tomcat.AbstractRunMojo.execute
(AbstractRunMojo.java
:144)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo
(DefaultPlugi
nManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
Goal(DefaultLifecycleExecutor.java:569)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:348)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLi
fecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:
328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:
138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main
(CompatibleMain.java:6
0)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
