Hi Arne,
Thanks for your reply. I could not found Geotools/Databases/HSQL , in
temp-directory such as /opt/apache-tomcat-6.0.26/temp/ .
For our application we are using Apache Tomcat. In test environment, many
times we are shutting down the Tomcat and restarting. Is this the case
that some times the Apache Tomcat is down and Geoserver is trying to
access something from the Tomcat server and then Geoserver fails?
Because in other environments, we are not facing this problem, where we do
not shut down and start the Apache Tomcat frequently. If this is the case
then I do not have to worry.
Please explain.
Regards,
Dharmendra Sonawane
From:
Arne Kepp <a...@tiledmarble.org>
To:
Dharmendra Sonawane <dharmendra.sonaw...@tcs.com>
Cc:
geoserver-users@lists.sourceforge.net
Date:
02/10/2011 05:22 PM
Subject:
Re: [Geoserver-users] GeoServer shutting down ...
Hi Dharmendra,
My guess is that the EPSG database connection should not be shutting down
during startup. Perhaps it's running in a separate thread and there are
more messages further up. But regardless, you can try stopping GeoServer
and deleting Geotools/Databases/HSQL , which you'll find in some
temp-directory such as /opt/apache-tomcat-6.0.26/temp/ .
A new one will be generated on startup.
-Arne
On 2/9/11 8:10 AM, Dharmendra Sonawane wrote:
Thanks Arne,
I am using GeoServer 2.0.0 (OS independent).
As suggested, I changed the logging to Geotools developer and got below
log:
2011-02-08 17:28:17,078 DEBUG [org.geotools.jdb] - Setting parameter 1 as
MDSYS.SDO_GEOMETRY(2003,8307,NULL,MDSYS.SDO_ELEM_INFO_ARRAY(1,1003,3),MDSYS.SDO_ORDINATE_ARRAY(coordinateddeleted))
2011-02-08 17:28:17,078 DEBUG [org.geotools.jdbc] - 1 = POLYGON
((coordinated deleted))
2011-02-08 17:28:17,078 DEBUG [org.geotools.jdbc] - 2 = -86.0
2011-02-08 17:28:17,078 DEBUG [org.geotools.jdbc] - 3 = -86.0
2011-02-08 17:28:17,078 DEBUG [org.geotools.jdbc] - 4 = 0
2011-02-08 17:28:17,078 DEBUG [org.geotools.jdbc] - 5 = 0
2011-02-08 17:28:17,923 TRACE [org.geotools.resource] - Loaded resources
for English from bundle "org.geotools.resources.i18n".
2011-02-08 17:28:17,923 DEBUG [org.geotools.referencing.factory] - Closed
the EPSG database connection.
2011-02-08 17:28:18,040 WARN
[org.geowebcache.storage.metastore.jdbc.JDBCMBWrapper] - SHUTDOWN call to
JDBC resulted in: Database is already closed (to disable automatic closing
at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-104]
2011-02-08 17:28:20,866 INFO [org.geoserver.catalog] - Disposing datastore
'DataStoreInfoImpl-4e0b98bf:12475d46fdd:-7fdb'
2011-02-08 17:28:20,867 INFO [org.geoserver.catalog] - Disposing datastore
'DataStoreInfoImpl-4e0b98bf:12475d46fdd:-7fda'
2011-02-08 17:28:20,867 INFO [org.geoserver.catalog] - Disposing datastore
'DataStoreInfoImpl-4e0b98bf:12475d46fdd:-7fd9'
2011-02-08 17:28:20,867 INFO [org.geoserver.catalog] - Disposing datastore
'DataStoreInfoImpl-4e0b98bf:12475d46fdd:-7fdc'
2011-02-08 17:28:20,867 INFO [org.geoserver.catalog] - Disposing datastore
'DataStoreInfoImpl--2a55deaa:12d17078466:-8000'
2011-02-08 17:28:30,742 DEBUG [org.geotools.jdbc] - CLOSE CONNECTION
2011-02-08 17:28:30,742 DEBUG [org.geotools.rendering] - Style cache hit
ratio: 0.92 , hits 23, requests 25
2011-02-08 17:28:30,742 DEBUG [org.geotools.renderer.shape] - Style cache
hit ratio: NaN , hits 0, requests 0
2011-02-08 17:28:30,776 ERROR [org.geoserver.ows] -
org.mortbay.jetty.EofException
at
org.mortbay.jetty.AbstractGenerator$Output.write(AbstractGenerator.java:629)
at
org.mortbay.jetty.AbstractGenerator$Output.write(AbstractGenerator.java:577)
at
org.geoserver.filters.AlternativesResponseStream.write(AlternativesResponseStream.java:59)
at java.io.BufferedOutputStream.flushBuffer(Unknown Source)
at java.io.BufferedOutputStream.flush(Unknown Source)
Please help me in understanding this!
Thanks and regards,
Dharmendra
From:
Arne Kepp <a...@tiledmarble.org>
To:
Dharmendra Sonawane <dharmendra.sonaw...@tcs.com>
Cc:
geoserver-users@lists.sourceforge.net
Date:
02/08/2011 12:13 PM
Subject:
Re: [Geoserver-users] GeoServer shutting down ...
You need to look at least a few lines before this message ,
GeoWebCacheDispatcher.destroy() is part of the shut down routine, so by
then it's already too late.
If there's nothing there, try to increase the logging to the geoserver or
geotools developer profiles.
Also, include what version of GeoServer you are using with every email.
-Arne
On 2/8/11 7:31 AM, Dharmendra Sonawane wrote:
Hello List,
Can anybody please help me in understanding why the GeoServer is shutdown?
Is it a problem on Oracle Database side and how to manage this?
2011-01-26 09:41:39,749 INFO [geowebcache.GeoWebCacheDispatcher] -
GeoWebCacheDispatcher.destroy() was invoked, shutting down.
2011-01-26 09:41:39,753 WARN [jdbc.JDBCMBWrapper] - SHUTDOWN call to JDBC
resulted in: Database is already closed (to disable automatic closing at
VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-104]
Thanks and regards,
Dharmendra Sonawane
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
