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

Ask Your Question
0

Jetty Webapp is not accessible

I have deployed jetty webapp to Gigaspaces.

GSM Logs:

2009-09-17 01:59:50,147 GSM INFO [com.gigaspaces.grid.gsm] - Deploying jettycomet 2009-09-17 01:59:50,199 GSM INFO [com.gigaspaces.grid.gsm.provision] - Requesting allocation of [jettycomet [1]] on [GSC pid[5540] host[localhost.localdomain/127.0.0.1]] 2009-09-17 01:59:50,226 GSM INFO [com.gigaspaces.grid.gsm.peer] - Adding [jettycomet] from GSM - [GSM pid[15738] host[localhost.localdomain/127.0.0.1]] 2009-09-17 01:59:51,603 GSM INFO [com.gigaspaces.grid.gsm.provision] - Allocated [jettycomet [1]] on [GSC pid[5540] host[localhost.localdomain/127.0.0.1]]

When i try to acess the jetty through browser I am getting following response:

Contexts known to this server are: /jettycomet ---> org.mortbay.jetty.webapp.WebAppContex... [failed]

The response shows failed. Can anyone please tell me what is wrong?

Regards,

Abhilash

{quote}This thread was imported from the previous forum. For your reference, the original is [available here|http://forum.openspaces.org/thread.jspa?threadID=3237]{quote}

asked 2009-09-16 15:37:04 -0500

abhilash428 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

Can you post the GSC output?

Shay

answered 2009-09-16 16:54:54 -0500

shay hassidim gravatar image
edit flag offensive delete link more

Comments

In GSC there is not log for jetty web app.

Now I am getting following logs from GSM:

2009-09-17 19:19:03,452 GSM INFO [com.gigaspaces.grid.gsm.peer] - Adding [jettycomet] from GSM - [GSM pid[3056] host[localhost.localdomain/127.0.0.1]] 2009-09-17 19:19:04,805 LUS INFO [com.sun.jini.reggie] - Exception sending event to [DynamicSmartStub [ImplObjClass: net.jini.lookup.ServiceDiscoveryManager$LookupCacheImpl$LookupListener, ConnectionURL: NIO://localhost.localdomain:46174/pid[24321]/1538690892777457_1_8086775617915064518, MaxConnPool: 1024 ]] with ServiceID [caa1cb4a-7e90-478a-971e-deddeff1d637]; Caused by: java.rmi.NoSuchObjectException: Object 1538690892777457 not found in object registry 2009-09-17 19:19:04,805 LUS INFO [com.sun.jini.reggie] - Exception sending event to [DynamicSmartStub [ImplObjClass: net.jini.lookup.ServiceDiscoveryManager$LookupCacheImpl$LookupListener, ConnectionURL: NIO://localhost.localdomain:46174/pid[24321]/1538690892777457_1_8086775617915064518, MaxConnPool: 1024 ]] with ServiceID [cd225fc2-ee59-4628-9456-eb62f80b6c54]; Caused by: java.rmi.NoSuchObjectException: Object 1538690892777457 not found in object registry 2009-09-17 19:19:04,805 LUS INFO [com.sun.jini.reggie] - Exception sending event to [DynamicSmartStub [ImplObjClass: net.jini.lookup.ServiceDiscoveryManager$LookupCacheImpl$LookupListener, ConnectionURL: NIO://localhost.localdomain:46174/pid[24321]/1538690892777457_1_8086775617915064518, MaxConnPool: 1024 ]] with ServiceID [67c2a069-2526-40db-b149-0b709b30e368]; Caused by: java.rmi.NoSuchObjectException: Object 1538690892777457 not found in object registry 2009-09-17 19:19:04,805 LUS INFO [com.sun.jini.reggie] - Exception sending event to [DynamicSmartStub [ImplObjClass: net.jini.lookup.ServiceDiscoveryManager$LookupCacheImpl$LookupListener, ConnectionURL: NIO://localhost.localdomain:46174/pid[24321]/1538690892777457_1_8086775617915064518, MaxConnPool: 1024 ]] with ServiceID [6671b8f2-b009-4da0-b78b-c919775d5e55]; Caused by: java.rmi.NoSuchObjectException: Object 1538690892777457 not found in object registry

Logs from deploy console:

[root@localhost bin]# ./gs.sh deploy /opt/jettycomet.war java version "1.6.0" OpenJDK Runtime Environment (build 1.6.0-b09) OpenJDK Server VM (build 1.6.0-b09, mixed mode)

Log file: /opt/gigaspaces-xap-premium-7.0.0-ga/logs/2009-09-17~19.18-gigaspaces-cli-localhost.localdomain-24321.log Found 5 GSMs Deploying [jettycomet.war] with name [jettycomet] under groups [gigaspaces-7.0.0-XAPPremium-ga] and locators [] Uploading [jettycomet] to [ http://localhost.localdomain:59574/ ] Waiting for [1] processing unit instances to be deployed... [jettycomet] [1] deployed successfully on [127.0.0.1] Finished deploying [1] processing unit instances

abhilash428 gravatar imageabhilash428 ( 2009-09-17 08:51:19 -0500 )edit

If you are running your deployment on multiple machines, please note that the servers are binding to localhost instead of to the IP address of the machine. I'm not sure it's the cause of what you're seeing, but this is not right. Please make sure the machine IP is properly configured, and in case of multiple IP addresses please set the NIC_ADDR to the right IP.

nirpaz gravatar imagenirpaz ( 2009-09-17 08:57:42 -0500 )edit

How's your hosts file looks like? Something is wrong with it. Make sure you use your machine IP and not localhost. Shay

shay hassidim gravatar imageshay hassidim ( 2009-09-17 09:49:15 -0500 )edit

Shay,

GSC is not able to refresh the processing units. I have undeployed the jetty web app but jetty still shows the jetty web app context and processing unit. How can i refresh the jetty context and gigaspaces processigng unit.

Thanks,

Abhilash

abhilash428 gravatar imageabhilash428 ( 2009-09-17 10:09:51 -0500 )edit

If you undeploy the WAR , the web application should be removed from the GSC. If this does not work for you , you should check the connectivity between the GSM and GSC. Shay

shay hassidim gravatar imageshay hassidim ( 2009-09-18 17:26:44 -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-09-16 15:37:04 -0500

Seen: 61 times

Last updated: Sep 16 '09