Welcome to the new Gigaspaces XAP forum. To recover your account, please follow these instructions.

Ask Your Question
0

Issue about Web Processing Unit Container

Hi all,

I encounter HTTP Error 500 when visiting a web application instance which is after auto healing. The web application I deployed is the example, space-access, included in GigaSpaces 6.6.3

Environment: GigaSpaces 6.6.3 build 3210 OS: Linux CentsOS JDK: 1.6

Procedures: 1. start 1 GSM, 4 GSC

  1. start unmanaged space from GMC UI (Launch -> Unmanaged space)

  2. deploy example, SpaceAccess.war

  3. each web application instance located in seperate GSC

    • SpaceAccess.PU[1],SpaceAccess.PU[2],SpaceAccess.PU[3]
  4. the allocation of instances among GSCs: GSC 1 : mySpace.PU[1] GSC 2 : SpaceAccess.PU[1] GSC 3 : SpaceAccess.PU[2] GSC 4 : SpaceAccess.PU[3]

  5. open one of the instance within browser in GMC

  6. submit some data to mySpace thru the web browser

  7. destroy 1 GSC, say the one contains SpaceAccess.PU[2]

  8. after self healing, the allocation of instances among GSCs: GSC 1 : mySpace.PU[1], SpaceAccess.PU[2] GSC 2 : SpaceAccess.PU[1] GSC 4 : SpaceAccess.PU[3]

  9. open the instance, SpaceAccess.PU[2], within browser in GMC HTTP Error 500 occurs in browser

  10. SpaceAccess.PU[1], SpaceAccess.PU[3] retain normal

11. GSC console log, please see below.

Another scenario, Start with 1 GSM, 5 GSC

(i). the allocation of instances among GSCs: GSC 1 : mySpace.PU[1] GSC 2 : SpaceAccess.PU[1] GSC 3 : SpaceAccess.PU[2] GSC 4 : SpaceAccess.PU[3] GSC 5 : [empty]

(ii). open one of the instance within browser in GMC

(iii). submit some data to mySpace thru the web browser

(iv). destroy 1 GSC, say the one contains SpaceAccess.PU[2]

(v). after self healing, the allocation of instances among GSCs: GSC 1 : mySpace.PU[1] GSC 2 : SpaceAccess.PU[1] GSC 3 : SpaceAccess.PU[3] GSC 5 : SpaceAccess.PU[2]

[(vi). all the instances of SpaceAccess retain normal]

(vii). destroy 1 GSC, say the one contains SpaceAccess.PU[2]

(viii). after self healing, the allocation of instances among GSCs: GSC 1 : mySpace.PU[1], SpaceAccess.PU[2] GSC 2 : SpaceAccess.PU[1] GSC 3 : SpaceAccess.PU[3]

(ix). open the instance, SpaceAccess.PU[2], within browser in GMC HTTP Error 500 occurs in browser, same error occurs in GSC console

(x). SpaceAccess.PU[1], SpaceAccess.PU[3] retain normal


[Error in GSC console log]:

Mar 5, 2009 5:59:11 PM INFO [com.gigaspaces.cache]: Data source recovery: Found 0 entries in data source. Inserted to space 0 entries. Under transaction - 0 entries.

Mar 5, 2009 5:59:11 PM INFO [com.gigaspaces.core.common]: Space <myspace_container:myspace> with url [/./mySpace?schema=default&groups=koning&state=started] started successfully

2009-03-05 17:59:11.135::INFO: Logging to STDERR via org.mortbay.log.StdErrLog Mar 5, 2009 5:59:12 PM FINE [org.jini.rio.cybernode]: mySpace.PU [1]: advertised

Mar 5, 2009 5:59:12 PM INFO [org.jini.rio.cybernode]: Instantiated mySpace.PU [1]

Mar 5, 2009 6:01:04 PM INFO [org.jini.rio.cybernode]: Instantiating SpaceAccess.PU [3]

Mar 5, 2009 6:01:05 PM INFO [org.openspaces.pu.container.servicegrid.PUServiceBeanImpl]: [SpaceAccess.PU] ClusterInfo [name[SpaceAccess] schema[null] numberOfInstances[3] numberOfBackups[0] instanceId[3] backupId[null]]

Mar 5, 2009 6:01:05 PM INFO [org.openspaces.pu.container.servicegrid.PUServiceBeanImpl]: [SpaceAccess.PU] BeanLevelProperties Context {} Beans {}

2009-03-05 18:01:05.354::INFO: jetty-6.1.11 2009-03-05 18:01:05.377::INFO: Started SelectChannelConnector@0.0.0.0:8082 2009-03-05 18:01:05.482::INFO: org.mortbay.jetty.plus.webapp.Configuration does not support annotations on source. Use org.mortbay.jetty.annotations.Configuration instead 2009-03-05 18:01:05.483::INFO: No Transaction manager found - if your webapp requires one, please configure one. Mar 5, 2009 6:01:06 PM FINE [org.jini.rio.cybernode]: SpaceAccess.PU [3]: advertised

Mar 5, 2009 6:01:06 PM INFO [org.jini.rio.cybernode]: Instantiated SpaceAccess.PU [3]

* Got Request * 2009-03-05 18:01:18.970::WARN: /SpaceAccess/ org.openspaces.core.UncategorizedSpaceException: com.gigaspaces.examples.data.UserData; nested exception is java.lang.ArrayStoreException: com.gigaspaces.examples.data.UserData at org.openspaces.core.exception.DefaultExceptionTranslator.translate(DefaultExceptionTranslator.java:51) at org.openspaces.core.DefaultGigaSpace.readMultiple(DefaultGigaSpace.java:346) at org.openspaces.core.DefaultGigaSpace.readMultiple(DefaultGigaSpace.java:338) at com.gigaspaces.examples.web.AccessSpaceServlet.doPost(AccessSpaceServlet.java:75) at com.gigaspaces.examples.web.AccessSpaceServlet.doGet(AccessSpaceServlet.java:61) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:729) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:285) at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126) at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:767) at org.apache.jsp.index_jsp._jspService(org.apache.jsp.index_jsp:48) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:93) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:470) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:364) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:729) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:285) at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126) at org.mortbay.jetty.servlet.DefaultServlet.doGet(DefaultServlet.java:463) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet ...

(more)

asked 2009-03-05 04:19:17 -0500

twinsenc gravatar image

updated 2013-08-08 09:52:00 -0500

jaissefsfex gravatar image
edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

Any chance you can test this with 7.0 M5? I think this issue been resolved with 7.0 M5 with all the classloading improvements. Shay

answered 2009-03-05 06:48:03 -0500

shay hassidim gravatar image
edit flag offensive delete link more

Comments

Yes, I rebuilt the space-access example with 7.0m5 library (as there is no servlet-api.jar in 7.0 lib, I build with the one in 6.6.3 lib) and tested with GigaSpaces 7.0m5. Everything works fine. Thank you.

For ur information, in 6.6.3 such error only occurs when the re-instantiated instance is located within the GSC which contains the dedicated remote space for such instance.

twinsenc gravatar imagetwinsenc ( 2009-03-05 19:33:52 -0500 )edit

Thanks.
Shay

shay hassidim gravatar imageshay hassidim ( 2009-03-06 07:10:46 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2009-03-05 04:19:17 -0500

Seen: 40 times

Last updated: Mar 05 '09