Skip navigation
$Nith$
$Nith$
Currently Being Moderated

Content Space not accessible - 404 error

Sep 5, 2010 1:16 AM

I have recently configured Content Services ES2 module through Configuration Manager.

 

I am able to see the relevant services (storeContent, retreiveContent etc.) in AdminUI.

 

However I am unable to access contentspace using the following URL. Why?

 

http://localhost:8080/contentspace

 

I am belonging to Contentspace Administrator & ContentSpace User role.

 

Please Advise!

 

Nith

1173 Views   8 Replies   Latest reply: $Nith$, Sep 25, 2010 10:23 PM
 
Replies
  • Raghu A
    Currently Being Moderated
    1. Raghu A,
    Sep 6, 2010 12:33 AM   in reply to $Nith$
    Report

    Can you also please attach back the contentservices.log file in case the application server is Jboss? It should be in the <JBoss>/bin/contentservices.log

     
    |
    Mark as:
  • $Nith$
    Currently Being Moderated
    2. $Nith$,
    Sep 6, 2010 2:26 AM   in reply to Raghu A
    Report

    Hi Raghu,

     

    I did a silly mistake Sorry.

     

    I din't deploy the EAR after configuring the archive using LCM. Dint notice the deployed solution components as well.

     

    After manually deploying the EAR file, it works now

     

     

    Now another issue

    After deploying the Content Service module, the AdminUI and Workspace crashes frequently. No errors in the contentservices log file.

     

    Any advise on this new issue?

     

    Thanks,

    Nith

     
    |
    Mark as:
  • Raghu A
    Currently Being Moderated
    3. Raghu A,
    Sep 6, 2010 2:30 AM   in reply to Raghu A
    Report

    Looks like your machine RAM is insufficient. What are the machine configurations you are using?

     

    The exact reason would be available in the jboss log file. Default location:- <JBoss>/deploy/lc_turnkey{Or Any other profile where livecycle is deployed}/log/server.log

     
    |
    Mark as:
  • Raghu A
    Currently Being Moderated
    4. Raghu A,
    Sep 6, 2010 2:32 AM   in reply to Raghu A
    Report

    Sorry I think i pasted the wrong path. Its  <JBoss>/server/lc_turnkey{Or Any other profile where livecycle is deployed}/log/server.log

     
    |
    Mark as:
  • $Nith$
    Currently Being Moderated
    5. $Nith$,
    Sep 6, 2010 3:42 AM   in reply to Raghu A
    Report

    2010-09-06 13:35:34,185 WARN  [com.adobe.idp.dsc.workmanager.adapter.WorkListenerAdapter] WM: Work item 3e4ca108-fa5f-412d-8ee6-2d627f7b35ed has been rejected by the J2EE work manager

     

     

    This is the only error shown in the server.log file.

     

    Nith

     
    |
    Mark as:
  • $Nith$
    Currently Being Moderated
    6. $Nith$,
    Sep 6, 2010 3:46 AM   in reply to $Nith$
    Report

    Server has 8 GB of RAM running on Windows 2003 platform

     

    When I try to access contentspace from Windows 7 client within IE 8, the Jboss (windows service) stops automatically.

     

    Nith

     
    |
    Mark as:
  • Raghu A
    Currently Being Moderated
    7. Raghu A,
    Sep 6, 2010 6:58 AM   in reply to $Nith$
    Report

    What are the values of the following:- set JAVA_HEAP_ARGS=-XX:PermSize=128m -XX:MaxPermSize=192m -Xms1024m -Xmx1024m

     

    Can you consider increasing the values of xms and xmx?

     

    Looks wierd, if memory is not the problem, addition of ContentServices EAR should not lead to Jboss stopping. Can you please attach both contentservices.log and server.log files?

     
    |
    Mark as:
  • $Nith$
    Currently Being Moderated
    8. $Nith$,
    Sep 25, 2010 10:23 PM   in reply to Raghu A
    Report

    I created another sandbox with a fresh installation which works now.

     

    Thanks for all your responses..

     

     

    Nith

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points