Topic
11 replies Latest Post - ‏2012-07-05T08:54:31Z by Emily Jiang
RileyChen
RileyChen
5 Posts
ACCEPTED ANSWER

Pinned topic The blog sample can't start -- Please help!

‏2010-04-20T10:04:54Z |
I install the blog sample according the readme.txt but the Business-level application Blog sample can't start. The appserver's log show error message same as "Problems with SLF4J" showed. How can I to fix it? I also have 2 questions
1) where I can find any log information for BLA start/stop related ?
2) When I follow WAS server admin console to create a new BLA, at "Add assets" step,I can config the web module's content root like "/blog" for blog sample. But it seems I can't see/modify after I finish the "Add assets" step, why?

My environment is windows 2003 server + WAS ND 7.0.0.7.
Anyone can help me? Thanks a lot!
Updated on 2012-07-05T08:54:31Z at 2012-07-05T08:54:31Z by Emily Jiang
  • SystemAdmin
    SystemAdmin
    153 Posts
    ACCEPTED ANSWER

    Re: The blog sample can't start -- Please help!

    ‏2010-04-20T10:40:24Z  in response to RileyChen
    The problem described in the "Problems with SLF4J" as they relate to the blog sample are benign and do not prevent the application running.

    Generally problems starting an application via BLA get reported in the normal log files. If you could attach the server logs and ffdc's I can take a look and see what seems to be the problem. Also when you say it can't start is this reported in the admin console when you start the application, or is the web app not accessible?

    We haven't added support for seeing/modifying the web module context root via the admin console yet. This is on our TODO list.

    Alasdair
    • RileyChen
      RileyChen
      5 Posts
      ACCEPTED ANSWER

      Re: The blog sample can't start -- Please help!

      ‏2010-04-21T06:58:15Z  in response to SystemAdmin
      Alasdair,Thanks for your reply.
      Attach please find my server's logs, could you help to check?

      Attachments

      • RileyChen
        RileyChen
        5 Posts
        ACCEPTED ANSWER

        Re: The blog sample can't start -- Please help!

        ‏2010-04-21T08:36:37Z  in response to RileyChen
        Hi Alasdair,as my environment is WAS ND version.
        Please also find the dmgr logs attached, too.

        After my rough check, it seems the com.ibm.json.java and javax.persistence is Missing. But I had added the com.ibm.json.java into "OSGi bundle repositories--Internal bundle repository". Please help me to check.
        Thanks a lot!
        4/21/10 14:24:55:961 GMT+08:00 00000015 AriesApplicat E CWSAI0003E: Cannot start the bundle com.ibm.ws.eba.example.blog.web because of org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Import-Package: com.ibm.json.java; version="[1.0.0,2.0.0)"

        4/21/10 14:24:55:977 GMT+08:00 00000015 AriesApplicat E CWSAI0003E: Cannot start the bundle com.ibm.ws.eba.example.blog.persistence because of org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Import-Package: javax.persistence; version="1.0.0"
        • SystemAdmin
          SystemAdmin
          153 Posts
          ACCEPTED ANSWER

          Re: The blog sample can't start -- Please help!

          ‏2010-04-21T10:41:33Z  in response to RileyChen
          Hi,

          I think I know what the problem is. There is a bug in the beta that only affects ND where the application is not fully synchronised automatically. To resolve this problem you need for force a full resynchronise.

          This can be forced in the console by going to:

          System administration > Nodes

          then selecting the desired node and clicking the Full Synchronise button.

          Alasdair
          • chenbin2
            chenbin2
            5 Posts
            ACCEPTED ANSWER

            Re: The blog sample can't start -- Please help!

            ‏2010-04-21T13:14:29Z  in response to SystemAdmin
            Thanks Alasdair! After I do nodes fully synchronised, the blog sample application can started!
            But I meet another issue below. I can't access the application at browser! According below error logs, its seems the blog application's web module can bound to default_host:9080,:80,:9443,:5060,:5061,:443. But as I create a new application server instance named OSGI_Serv01, I already added new *:9081 and *:9444 into default_host, but it seems the BLA application can't know the changed Virtual hosts setting.

            4/21/10 14:27:44:196 GMT+08:00 00000029 CompositionUn E WSVR0194E: Composition unit WebSphere:cuname=com.ibm.ws.eba.example.blog_0001.eba in BLA WebSphere:blaname=Blog Sample failed to start.
            4/21/10 20:50:01:727 GMT+08:00 00000029 CompositionUn A WSVR0190I: Starting composition unit WebSphere:cuname=com.ibm.ws.eba.example.blog_0001.eba in BLA WebSphere:blaname=Blog Sample.
            4/21/10 20:50:11:524 GMT+08:00 00000029 wtp W org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ContainerImpl getFiles No load strategy is available for http:// com.ibm.ws.eba.example.blog.web_1.0.0
            4/21/10 20:50:11:711 GMT+08:00 00000029 webapp I com.ibm.ws.webcontainer.webapp.WebGroupImpl WebGroup SRVE0169I: Loading Web Module: Blog Application.
            4/21/10 20:50:12:102 GMT+08:00 00000029 WASSessionCor I SessionContextRegistry getSessionContext SESN0176I: Will create a new session context for application key default_hostblog
            4/21/10 20:50:12:180 GMT+08:00 00000029 webcontainer I com.ibm.ws.wswebcontainer.VirtualHost addWebApplication SRVE0250I: Web Module Blog Application has been bound to default_host:9080,:80,:9443,:5060,:5061,:443.
            4/21/10 20:50:12:274 GMT+08:00 00000029 WorkSpaceMana A WKSP0500I: Workspace configuration consistency check is disabled.
            4/21/10 20:50:12:368 GMT+08:00 00000029 FfdcProvider I com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on D:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\ffdc\OSGI_Serv01_76647664_10.04.21_20.50.12.3681854944217142479339.txt com.ibm.ws.policyset.runtime.server.FileLocatorImpl.getAttachmentPath FFDC-4
            4/21/10 20:50:12:383 GMT+08:00 00000029 FileLocatorIm E CWPST0164E: The com.ibm.ws.eba.example.blog.eba composition unit is not found.
            4/21/10 20:50:12:399 GMT+08:00 00000029 CompositionUn A WSVR0191I: Composition unit WebSphere:cuname=com.ibm.ws.eba.example.blog_0001.eba in BLA WebSphere:blaname=Blog Sample started.
            4/21/10 20:50:48:696 GMT+08:00 00000036 util W com.ibm.ws.webcontainer.util.VirtualHostContextRootMapper map SRVE0316W: Request matches the context root [/blog/*] under the virtual host alias of *:5060.
            4/21/10 20:50:48:696 GMT+08:00 00000036 util W com.ibm.ws.webcontainer.util.VirtualHostContextRootMapper map SRVE0317W: You may need to add a new virtual host alias of :<your port> to the same virtual host that :5060 is under.
            4/21/10 20:50:48:696 GMT+08:00 00000036 webcontainer E com.ibm.ws.webcontainer.WebContainer handleRequest SRVE0255E: A WebGroup/Virtual Host to handle /blog has not been defined.
            4/21/10 20:50:53:368 GMT+08:00 00000036 util W com.ibm.ws.webcontainer.util.VirtualHostContextRootMapper map SRVE0316W: Request matches the context root [/blog/*] under the virtual host alias of *:5060.
            4/21/10 20:50:53:368 GMT+08:00 00000036 util W com.ibm.ws.webcontainer.util.VirtualHostContextRootMapper map SRVE0317W: You may need to add a new virtual host alias of :<your port> to the same virtual host that :5060 is under.
            4/21/10 20:50:53:368 GMT+08:00 00000036 webcontainer E com.ibm.ws.webcontainer.WebContainer handleRequest SRVE0255E: A WebGroup/Virtual Host to handle /blog/ has not been defined.
            4/21/10 20:52:13:196 GMT+08:00 00000036 util W com.ibm.ws.webcontainer.util.VirtualHostContextRootMapper map SRVE0316W: Request matches the context root [/blog/*] under the virtual host alias of *:5060.
            4/21/10 20:52:13:196 GMT+08:00 00000036 util W com.ibm.ws.webcontainer.util.VirtualHostContextRootMapper map SRVE0317W: You may need to add a new virtual host alias of :<your port> to the same virtual host that :5060 is under.
            4/21/10 20:52:13:196 GMT+08:00 00000036 webcontainer E com.ibm.ws.webcontainer.WebContainer handleRequest SRVE0255E: A WebGroup/Virtual Host to handle /blog/index.html has not been defined.
            • chenbin2
              chenbin2
              5 Posts
              ACCEPTED ANSWER

              Re: The blog sample can't start -- Please help!

              ‏2010-04-21T13:37:09Z  in response to chenbin2
              After I switch the blog sample to default server1 (with http port 9080). The web module is work. I can access it at http://server_ip:9080/blog/
              Could you help to check why it can not bound with new server's (9081 port)? Thanks!
              • chenbin2
                chenbin2
                5 Posts
                ACCEPTED ANSWER

                Re: The blog sample can't start -- Please help!

                ‏2010-04-21T13:55:02Z  in response to chenbin2
                I fix the issue. Still the node ynchronised problem. After I do node fully synchronised. The issue is fixed. Thanks!
                • Documentum
                  Documentum
                  4 Posts
                  ACCEPTED ANSWER

                  Re: The blog sample can't start -- Please help!

                  ‏2012-07-04T10:51:11Z  in response to chenbin2
                  I am new to Websphere world can some one tell me how to perform following ?

                  After I do node fully synchronised

                  I am also getting following error. I have created new server as server2 and deployed application and application is starting up but in getting no page found.
                  sysout.log gives following error
                  7/4/12 11:15:41:940 BST 00000026 util W com.ibm.ws.webcontainer.util.VirtualHostContextRootMapper map SRVE0317W: You may need to add a new virtual host alias of :<your port> to the same virtual host that :5060 is under.
                  7/4/12 11:15:41:955 BST 00000026 webcontainer E com.ibm.ws.webcontainer.WebContainer handleRequest SRVE0255E: A WebGroup/Virtual Host to handle /taskspace has not been defined.
                  • Emily Jiang
                    Emily Jiang
                    73 Posts
                    ACCEPTED ANSWER

                    Re: The blog sample can't start -- Please help!

                    ‏2012-07-04T14:23:11Z  in response to Documentum
                    It looks like you are using the port of 5060. Is it correct? If you are sure it is the correct port for your application, you need to add the port to Virtual Hosts > default_host > Host Aliases under the left pane of Environment and then Virtual hosts.

                    Hope this helps.
                    Thanks
                    Emily
                    • Documentum
                      Documentum
                      4 Posts
                      ACCEPTED ANSWER

                      Re: The blog sample can't start -- Please help!

                      ‏2012-07-05T04:56:38Z  in response to Emily Jiang
                      No I am using 9082 port. Unique port genrated by WebSphere Admin console only when we create new server.

                      I have already added to location which you have suggested. Still getting issue.
                    • Emily Jiang
                      Emily Jiang
                      73 Posts
                      ACCEPTED ANSWER

                      Re: The blog sample can't start -- Please help!

                      ‏2012-07-05T08:54:31Z  in response to Emily Jiang
                      Just checking: when you deploy your app, did you bound it to the vitual host or admin host? If you deploy it on virtual host, it is normally 9080 or 9443. You can look at your serverindex.xml from WAS_Installation_dir/profiles/your_profile_name/config/cells/your_profile_name/nodes/your_profile_name/serverindex.xml.
                      e.g.
                      non-secured default host:
                      <specialEndpoints xmi:id="NamedEndPoint_1183122129647" endPointName="WC_defaulthost">
                      <endPoint xmi:id="EndPoint_1183122129647" host="*" port="9080"/>
                      </specialEndpoints>
                      secured default host:
                      <specialEndpoints xmi:id="NamedEndPoint_1183122129650" endPointName="WC_defaulthost_secure">
                      <endPoint xmi:id="EndPoint_1183122129650" host="*" port="9443"/>
                      </specialEndpoints>
                      Double check to find your defaulthost and then make sure your url uses the correct port number.

                      Hope this helps. If not, please collect trace with the trace string of com.ibm.ws.eba.*=all.

                      Emily