Announcement Announcement Module
Collapse
No announcement yet.
New server - template configuration Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • New server - template configuration

    STS 3.2.0 made changes to the new server wizard. I followed these steps:
    1. Go to 'Servers' view in Spring Tool Suite
    2. Right click within the Servers view and select "New > Server"
    3. Select the default server type i.e. "VMware vFabric tc Server v2.5, v2.6, v2.7, v2.8"
    4. Change the server name
    5. Click Next and select "Create New Instance"
    6. Enter a name for the tc Server instance
    7. Check the templates 'bio-ssl' and 'bio' and click on finish

    Under STS 2.8.0, the server would be created. STS 3.2.0 displays Template Configuration dialogs that I donít understand. In addition, some questions are duplicated:
    Please enter the password that the SSL keystore should protect itself with:
    Please enter the alias that the keystore should refer to the SSL private key as:
    Is there a way to go back to the prior method? If not, what do I do with these dialogs?

  • #2
    Hey!

    The new page that you are referring to provides the option to configure additional options for the selected tc Server templates that you have chosen. Those options are coming from the tc Server instances (not defined by STS itself) and where there in the past as well, but we didn't offer a way to configure them. This can now be done with this additional page in the wizard.

    In case you don't want to configure anything for those options, you should be able to just go ahead and press "Finish". But that option seems to be disabled in your case, so that is a bug. I filed a JIRA for this:

    https://issuetracker.springsource.com/browse/STS-3324

    As a workaround, you can go to the command line, create the template using the tcruntime-instance scripts, and import that instance into STS (by selecting it from the list of existing templates).

    HTH,
    Martin

    Comment


    • #3
      Thanks for the reponse but I having a problem with the workaround. I created the server instance as follows:

      C:\dev\springsource320\vfabric-tc-server-developer-2.8.2.RELEASE>tcruntime-instance create --template bio --template bio-ssl tcserver_with_ssl
      Creating instance 'tcserver_with_ssl' ...
      Using separate layout
      Creating bin\setenv.bat
      Creating conf\wrapper.conf
      Applying template 'base'
      Copying template's contents
      Applying fragment 'context-fragment.xml' to 'conf/context.xml'
      Applying fragment 'server-fragment.xml' to 'conf/server.xml'
      Applying fragment 'web-fragment.xml' to 'conf/web.xml'
      Applying fragment 'tomcat-users-fragment.xml' to 'conf/tomcat-users.xml'
      Applying fragment 'catalina-fragment.properties' to 'conf/catalina.properties'
      Applying template 'base-tomcat-7'
      Copying template's contents
      Applying fragment 'server-fragment.xml' to 'conf/server.xml'
      Applying fragment 'web-fragment.xml' to 'conf/web.xml'
      Applying fragment 'catalina-fragment.properties' to 'conf/catalina.properties'
      Applying template 'bio'
      Copying template's contents
      Applying fragment 'server-fragment.xml' to 'conf/server.xml'
      Applying template 'bio-ssl'
      Copying template's contents
      Applying fragment 'server-fragment.xml' to 'conf/server.xml'
      Applying fragment 'catalina-fragment.properties' to 'conf/catalina.properties'
      Creating SSL artifacts
      Generating SSL certificate and private key
      Creating conf/tc-server-bio-ssl.keystore
      Configuring instance 'tcserver_with_ssl' to use Tomcat version 7.0.35.B.RELEASE
      Setting permissions
      Instance created
      Connector summary
      Port: 8080 Type: Blocking IO Secure: false
      Port: 8443 Type: Blocking IO Secure: true


      When I selected the new instance an error is displayed, "The specified server is not valid. The .tc-runtime-instance is missing." However it does exist in the tcserver_with_ssl directory.

      Attachment
      Attached Files

      Comment


      • #4
        Hi Boaz.

        I've fixed STS-3324 for the next release, but your other error message puzzles me. If the .tc-runtime-instance file exists in the tcserver_with_ssl directory, then it should proceed normally. Can you check the permissions on the tcserver_with_ssl directory and the .tc-runtime-instance file? If either of those files were created with limited read permissions, then the Java File API might return them as not existing.

        Comment


        • #5
          Both the tcserver_with_ssl directory and the .tc-runtime-instance file allow Read and Read & execute.

          Comment


          • #6
            I re-tried the workaround and it worked. I don't know why it failed earlier and works now. Thanks for the help.

            Comment


            • #7
              Happy to hear that's working for you now. Cheers.

              Comment


              • #8
                I spoke too soon, the server was created but did not start.....

                Apr 22, 2013 12:44:49 PM com.springsource.tcserver.security.PropertyDecoder <init>
                INFO: tc Runtime property decoder using memory-based key
                Apr 22, 2013 12:44:49 PM com.springsource.tcserver.security.PropertyDecoder <init>
                INFO: tcServer Runtime property decoder has been initialized in 319 ms
                Apr 22, 2013 12:44:50 PM org.apache.tomcat.util.net.AbstractEndpoint adjustRelativePath
                WARNING: configured file:[C:\dev\workspaces\sts320\server-test\.metadata\.plugins\org.eclipse.wst.server.cor e\tmp1/conf/tc-server-bio-ssl.keystore] does not exist.
                Apr 22, 2013 12:44:50 PM org.apache.coyote.AbstractProtocol init
                INFO: Initializing ProtocolHandler ["http-bio-8080"]
                Apr 22, 2013 12:44:50 PM org.apache.coyote.AbstractProtocol init
                INFO: Initializing ProtocolHandler ["http-bio-8443"]
                Apr 22, 2013 12:44:51 PM org.apache.tomcat.util.net.jsse.JSSESocketFactory getStore
                SEVERE: Failed to load keystore type JKS with path C:\dev\workspaces\sts320\server-test\.metadata\.plugins\org.eclipse.wst.server.cor e\tmp1/conf/tc-server-bio-ssl.keystore due to C:\dev\workspaces\sts320\server-test\.metadata\.plugins\org.eclipse.wst.server.cor e\tmp1\conf\tc-server-bio-ssl.keystore (The system cannot find the file specified)
                java.io.FileNotFoundException: C:\dev\workspaces\sts320\server-test\.metadata\.plugins\org.eclipse.wst.server.cor e\tmp1\conf\tc-server-bio-ssl.keystore (The system cannot find the file specified)
                at java.io.FileInputStream.open(Native Method)
                at java.io.FileInputStream.<init>(FileInputStream.jav a:120)
                at org.apache.tomcat.util.net.jsse.JSSESocketFactory. getStore(JSSESocketFactory.java:400)
                at org.apache.tomcat.util.net.jsse.JSSESocketFactory. getKeystore(JSSESocketFactory.java:306)
                at org.apache.tomcat.util.net.jsse.JSSESocketFactory. getKeyManagers(JSSESocketFactory.java:565)
                at org.apache.tomcat.util.net.jsse.JSSESocketFactory. getKeyManagers(JSSESocketFactory.java:505)
                at org.apache.tomcat.util.net.jsse.JSSESocketFactory. init(JSSESocketFactory.java:449)
                at org.apache.tomcat.util.net.jsse.JSSESocketFactory. createSocket(JSSESocketFactory.java:158)
                at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEnd point.java:393)
                at org.apache.tomcat.util.net.AbstractEndpoint.init(A bstractEndpoint.java:610)
                at org.apache.coyote.AbstractProtocol.init(AbstractPr otocol.java:429)
                at org.apache.coyote.http11.AbstractHttp11JsseProtoco l.init(AbstractHttp11JsseProtocol.java:119)
                at org.apache.catalina.connector.Connector.initIntern al(Connector.java:981)
                at org.apache.catalina.util.LifecycleBase.init(Lifecy cleBase.java:102)
                at org.apache.catalina.core.StandardService.initInter nal(StandardService.java:559)
                at org.apache.catalina.util.LifecycleBase.init(Lifecy cleBase.java:102)
                at org.apache.catalina.core.StandardServer.initIntern al(StandardServer.java:814)
                at org.apache.catalina.util.LifecycleBase.init(Lifecy cleBase.java:102)
                at org.apache.catalina.startup.Catalina.load(Catalina .java:633)
                at org.apache.catalina.startup.Catalina.load(Catalina .java:658)
                at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
                at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
                at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
                at java.lang.reflect.Method.invoke(Method.java:597)
                at org.apache.catalina.startup.Bootstrap.load(Bootstr ap.java:281)
                at org.apache.catalina.startup.Bootstrap.main(Bootstr ap.java:455)
                Apr 22, 2013 12:44:51 PM org.apache.coyote.AbstractProtocol init
                SEVERE: Failed to initialize end point associated with ProtocolHandler ["http-bio-8443"]
                java.io.FileNotFoundException: C:\dev\workspaces\sts320\server-test\.metadata\.plugins\org.eclipse.wst.server.cor e\tmp1\conf\tc-server-bio-ssl.keystore (The system cannot find the file specified)
                at java.io.FileInputStream.open(Native Method)
                at java.io.FileInputStream.<init>(FileInputStream.jav a:120)
                at org.apache.tomcat.util.net.jsse.JSSESocketFactory. getStore(JSSESocketFactory.java:400)
                at org.apache.tomcat.util.net.jsse.JSSESocketFactory. getKeystore(JSSESocketFactory.java:306)
                at org.apache.tomcat.util.net.jsse.JSSESocketFactory. getKeyManagers(JSSESocketFactory.java:565)
                at org.apache.tomcat.util.net.jsse.JSSESocketFactory. getKeyManagers(JSSESocketFactory.java:505)
                at org.apache.tomcat.util.net.jsse.JSSESocketFactory. init(JSSESocketFactory.java:449)
                at org.apache.tomcat.util.net.jsse.JSSESocketFactory. createSocket(JSSESocketFactory.java:158)
                at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEnd point.java:393)
                at org.apache.tomcat.util.net.AbstractEndpoint.init(A bstractEndpoint.java:610)
                at org.apache.coyote.AbstractProtocol.init(AbstractPr otocol.java:429)
                at org.apache.coyote.http11.AbstractHttp11JsseProtoco l.init(AbstractHttp11JsseProtocol.java:119)
                at org.apache.catalina.connector.Connector.initIntern al(Connector.java:981)
                at org.apache.catalina.util.LifecycleBase.init(Lifecy cleBase.java:102)
                at org.apache.catalina.core.StandardService.initInter nal(StandardService.java:559)
                at org.apache.catalina.util.LifecycleBase.init(Lifecy cleBase.java:102)
                at org.apache.catalina.core.StandardServer.initIntern al(StandardServer.java:814)
                at org.apache.catalina.util.LifecycleBase.init(Lifecy cleBase.java:102)
                at org.apache.catalina.startup.Catalina.load(Catalina .java:633)
                at org.apache.catalina.startup.Catalina.load(Catalina .java:658)
                at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
                at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
                at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
                at java.lang.reflect.Method.invoke(Method.java:597)
                at org.apache.catalina.startup.Bootstrap.load(Bootstr ap.java:281)
                at org.apache.catalina.startup.Bootstrap.main(Bootstr ap.java:455)
                Apr 22, 2013 12:44:51 PM org.apache.catalina.core.StandardService initInternal
                SEVERE: Failed to initialize connector [Connector[HTTP/1.1-8443]]
                org.apache.catalina.LifecycleException: Failed to initialize component [Connector[HTTP/1.1-8443]]
                at org.apache.catalina.util.LifecycleBase.init(Lifecy cleBase.java:106)
                at org.apache.catalina.core.StandardService.initInter nal(StandardService.java:559)
                at org.apache.catalina.util.LifecycleBase.init(Lifecy cleBase.java:102)
                at org.apache.catalina.core.StandardServer.initIntern al(StandardServer.java:814)
                at org.apache.catalina.util.LifecycleBase.init(Lifecy cleBase.java:102)
                at org.apache.catalina.startup.Catalina.load(Catalina .java:633)
                at org.apache.catalina.startup.Catalina.load(Catalina .java:658)
                at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
                at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
                at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
                at java.lang.reflect.Method.invoke(Method.java:597)
                at org.apache.catalina.startup.Bootstrap.load(Bootstr ap.java:281)
                at org.apache.catalina.startup.Bootstrap.main(Bootstr ap.java:455)

                Comment


                • #9
                  Yeah, it looks like there's a problem when I use the combo to select a previously created instance. If I select the Browse... button instead to navigate to the instance location, then the server will start up correctly. I'm going to have to sort that out. Boaz, does it work for you when use the Browse... button to pick your instance?

                  Comment


                  • #10
                    Yes, after using Browse to pick the instance the server is created and it does start.

                    Comment


                    • #11
                      Thank you for the feedback. I've identified at least 2 issues with the "existing instance" option that I'll be looking into.

                      https://issuetracker.springsource.com/browse/STS-3339
                      https://issuetracker.springsource.com/browse/STS-3340

                      Comment

                      Working...
                      X