Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
turbo ans sandboxes
diago
hello
when we tried to test turboibm with SmallApp ou DemoApp
we have the following error when we create the ligthweight sandbox :
com.interwoven.turbo.ibm.SandboxException: STAGING Does not Exist
at com.interwoven.turbo.ibm.SandboxServlet.createSandboxPool(SandboxServlet.java:452)
at com.interwoven.turbo.ibm.SandboxServlet.processRequest(SandboxServlet.java:164)
at com.interwoven.turbo.ibm.SandboxServlet.doPost(SandboxServlet.java:143)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.servlet.engine.webapp.SingleThreadModelServlet.service(SingleThreadModelServlet.java:73)
at com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.java:827)
at com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleServlet.java:167)
at com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.java:297)
at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.java:110)
at com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:472)
at com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager.java:1012)
at com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.java:913)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:665)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:331)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:117)
at com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:124)
at com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:218)
at com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:67)
at com.ibm.servlet.engine.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:106)
at com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:125)
at com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java:315)
at com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java:60)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:323)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:252)
at com.ibm.ws.util.CachedThread.run(ThreadPool.java:137)
despite the fact we submit the contacts of the workarea
we use turboibm 5.5.2 , teamsite 5.5.2 SP2 on solaris and WAS 4.0.2 on solaris
regards
Eric Grandjean
Find more posts tagged with
Comments
Migrateduser
Have you made any progress on this issue. If you've submitted the SmallApp to staging this should work.
Darren Knipp
Group Product Manager
Interwoven
diago
Hello
You re right
we need to submit workarea content before building sandbox pool
when we create a new application
what is the minimal set offiles we need to submit before creating sandbox pool ?
regards
Eric Grandjean
Migrateduser
You should submit the entire contents of your workarea containing the web-app(s) into the staging area for the branch including application.xml. For a lightweight sandbox pool, Turbo uses the EJBs from staging for all the workareas on that branch, and then takes the web components (servlets, files, jsps, etc..) from each workarea. The EJBs must come from staging because they can only be registered once with the application server.
In a heavyweight sandbox, all the contents for the sandbox are taken directly from the workarea and you can only have one heavyweight sandbox per IBM node again because of the way EJBs are registered with WAS using JNDI.
Hope this helps. I think the product guide also talk to this if they don't let us know.
Darren
Interwoven
