Announcement Announcement Module
Collapse
No announcement yet.
problems with tcserver dev edition 2.0 Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • problems with tcserver dev edition 2.0

    Hi, I have downloaded latest tc server, but I get always this message when I launch it.
    Code:
    java.lang.ClassNotFoundException: org.springframework.web.context.ContextLoaderListener
    but If I use latest tomcat I don't have this problem.

    I am using spring 2.5.

  • #2
    hello,
    could you provide more information: what platform are you using, did you download the .zip file, or the tar.gz file etc. Also, are you trying this standalone, or through STS.

    thanks,
    _ellen

    Comment


    • #3
      hi, I have downloaded .zip.
      I have picked insight.war, and I have put inside tomcat-6.0.25.A-RELEASE/webapps folder, and all jar inside lib folder.

      I have tried both, from cmd and from latest sts.

      Comment


      • #4
        Try using the supplied spring-insight-instance

        The tc Server Developer kit comes with a pre-configured spring-insight-instance directory that you can use "as is" or better as a instance template.

        That instance directory has the insight.war in its webapps sub-directory. The lib directory includes three jar files necessary for Insight. (Based on your note, you must have found these already.) Also the conf sub-directory has some small changes necessary for Insight. The context.xml file contains three Insight specific entries. I'm not sure if there are any other conf changes.

        I've never tried putting Insight files directly into the tomcat-6.0.25.A-RELEASE like you mentioned. Perhaps you're missing the conf/context.xml change.

        Comment


        • #5
          I can start tcserver without problems, I can see insight, all fine, but when I try to deploy my war application I get errors I mentioned before.

          Comment


          • #6
            Let's try this again without modifying the tomcat distribution.

            I suggest we get the changes to the tomcat directory out of the picture. Let's restore the tomcat directory to its original state and try to deploy your application into the supplied instance or a copy of it.

            Unzip the developer kit again.

            Make yourself a new server instance directory, using the supplied instance as a template. The command would be (if using Windows):

            tcruntime-instance.bat -c -s myInstance -t spring-insight-instance

            Prepare the instance for your application as necessary. Copy any jars your application may need to the myInstance/lib directory. Update files in the conf/ directory as necessary.

            Start the server:

            tcruntime-ctl.bat myInstance run

            Check the logs to make sure they're clean.

            Deploy your app by copying it to the myInstance/webapps directory.

            Let us know if this helps!

            This link provides more install information:
            http://static.springsource.com/proje...eloper-edition

            --Bob

            Comment


            • #7
              I have a mistake in the command to create a new instance from an existing instance directory. After the -t switch you must specify the full path to the instance directory to be used as the template.

              Sorry about that.

              Also if you're going to use the spring-insight-instance directory as a template, then I recommend not ever starting a server instance with it. Otherwise the logs and work sub-directories, and maybe some others, get populated and carried forward into each newly created instance directory structure.

              Of course, you can always restore the template by unzipping the developer kit. ;-)

              Comment


              • #8
                ok, I will try it.

                Comment


                • #9
                  Following up

                  Any luck?

                  --Bob

                  Comment


                  • #10
                    when I can try it I will expose it.

                    Comment

                    Working...
                    X