That's what crossed my mind early this morning as I was waking up.  When I unchecked the Deploy on Save box, that problem went away. I hadn't noticed the existence of an automatic deploy folder in Tomcat.

It's only a problem because the 2 apps are not intended to run in the same memory space and when they do, they fight over port assignments and it brings everything down.


Don

On 10/30/19 3:01 PM, Geertjan Wielenga wrote:
Maybe remove them from the Tomcat automatic deploy folder, could solve it. But this is default behavior, should be default behavior on the command line too.

Gj

On Wed, Oct 30, 2019 at 7:46 PM Don <don.albert...@gmail.com <mailto:don.albert...@gmail.com>> wrote:

    In only happens when run from NetBeans.  Command line startup.sh
    is acting normally.  In addition, if I use Debug instead of Run,
    the problem is not apparent.

    Don

    On 10/30/19 2:38 PM, Geertjan Wielenga wrote:
    Best to ask on the Tomcat mailing lists.

    Gj

    On Wed, Oct 30, 2019 at 7:37 PM Don <don.albert...@gmail.com
    <mailto:don.albert...@gmail.com>> wrote:

        Where does it keep track of them? On the production server,
        they are in the webapps folder but when this is running,
        there is nothing in the local server's webapps folder.  Is
        there any way to NOT keep track of them and run them when
        they are not wanted?

        Don

        On 10/30/19 2:22 PM, Geertjan Wielenga wrote:
        So those projects were deployed before to Tomcat and Tomcat
        keeps tracks of them and redeploys them when Tomcat restarts.

        Find out more about Tomcat here: https://tomcat.apache.org/

        Gj


        On Wed, Oct 30, 2019 at 6:57 PM Don <don.albert...@gmail.com
        <mailto:don.albert...@gmail.com>> wrote:

            When I select a project and right-click and select Run,
            it prints

            init:
            deps-module-jar:
            deps-ear-jar:
            deps-jar:
            library-inclusion-in-archive:
            library-inclusion-in-manifest:
            compile:
            compile-jsps:
            Starting Tomcat process...
            Waiting for Tomcat...

            In the Tomcat output window I can see that it is
            starting projects that
            are not open in NetBeans and that I do not want to run
            (because they
            have issues).

            Right after 'Startup sequence completed in 327ms'  it
            starts to print
            output from a .class file for an app listener followed
            from another
            .class file for a different app listener in a different
            project neither
            of which is the one I want to run.

            Why is it executing code in other projects?


            Don


            
---------------------------------------------------------------------
            To unsubscribe, e-mail:
            users-unsubscr...@netbeans.apache.org
            <mailto:users-unsubscr...@netbeans.apache.org>
            For additional commands, e-mail:
            users-h...@netbeans.apache.org
            <mailto:users-h...@netbeans.apache.org>

            For further information about the NetBeans mailing
            lists, visit:
            https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Reply via email to