[Geoserver-users] GS stuck and servlet failed Errors

i just downloaded 1.6RC2 version and everything seemed to be working fine,
until i got the following errors. I dont know if they have to do with
weblogic or geoserver, but if anyone has any clue what they are please let
me know thanks....ps. one stacktrace is long so i shortened it.

<Jan 9, 2008 8:27:57 AM PST> <Error> <HTTP> <BEA-101020>
<[weblogic.servlet.internal.WebAppServletContext@anonymised.com - appName:
'geoserver', name: 'geoserver', context-path: '/geoserver'] Servlet failed
with Exception
java.lang.RuntimeException: java.net.SocketException: Write failed: Broken
pipe
        at
org.geoserver.wfs.response.WfsExceptionHandler.handle1_0(WfsExceptionHandler.java:104)
        at
org.geoserver.wfs.response.WfsExceptionHandler.handleServiceException(WfsExceptionHandler.java:50)
        at org.geoserver.ows.Dispatcher.exception(Dispatcher.java:1179)
        at
org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:198)
        at
org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:139)
        Truncated. see log file for complete stacktrace
java.net.SocketException: Write failed: Broken pipe
        at jrockit.net.SocketNativeIO.writeBytesPinned(I[BII)V(Native
Method)
        at
jrockit.net.SocketNativeIO.socketWrite(Ljava.io.FileDescriptor;[BII)V(Unknown
Source)
        at
java.net.SocketOutputStream.socketWrite0(Ljava.io.FileDescriptor;[BII)V(SocketOutputStream.java:???)
        at
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
        Truncated. see log file for complete stacktrace

<Jan 9, 2008 8:28:00 AM PST> <Error> <WebLogicServer> <BEA-000337> <[STUCK]
ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)' has
been busy for "635" seconds working on the request "Http Request:
/geoserver/wfs", which is more than the configured time (StuckThreadMaxTime)
of "600" seconds. Stack trace:
Thread-66 "[STUCK] ExecuteThread: '11' for queue: 'weblogic.kernel.Default
(self-tuning)'" <alive, in native, blocked, priority=1, DAEMON> {
    -- Blocked trying to get lock:
org.apache.log4j.spi.RootLogger@anonymised.com[fat lock]
    jrockit.vm.Threads.waitForSignal(Native Method)
    jrockit.vm.Locks.fatLockBlockOrSpin(Unknown Source)
    jrockit.vm.Locks.lockFat(Unknown Source)
    jrockit.vm.Locks.monitorEnterSecondStage(Unknown Source)
    jrockit.vm.Locks.monitorEnter(Unknown Source)
    org.apache.log4j.Category.callAppenders(Category.java:201)
    org.apache.log4j.Category.forcedLog(Category.java:388)
    org.apache.log4j.Category.debug(Category.java:257)
    org.geotools.util.logging.Log4JLogger.finer(Log4JLogger.java:134)
   
org.geoserver.wfs.InsertElementHandler.execute(InsertElementHandler.java:72)
    org.geoserver.wfs.Transaction.execute(Transaction.java:328)
    org.geoserver.wfs.Transaction.transaction(Transaction.java:104)
   
org.geoserver.wfs.DefaultWebFeatureService.transaction(DefaultWebFeatureService.java:156)
    jrockit.vm.RNI.c2java(Native Method)
    jrockit.reflect.NativeMethodInvoker.invoke0(Native Method)
    jrockit.reflect.NativeMethodInvoker.invoke(Unknown Source)
    jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)
    java.lang.reflect.Method.invoke(Unknown Source)
   
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:292)
   
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:155)
   
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:144)
    org.geoserver.wfs.WFSLogger.invoke(WFSLogger.java:44)
   
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:144)
   
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:174)
    $Proxy117.transaction(Unknown Source)
    jrockit.vm.RNI.c2java(Native Method)
    jrockit.reflect.NativeMethodInvoker.invoke0(Native Method)
    jrockit.reflect.NativeMethodInvoker.invoke(Unknown Source)
    jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)
    java.lang.reflect.Method.invoke(Unknown Source)
   
org.geoserver.security.OperationSecurityInterceptor.invoke(OperationSecurityInterceptor.java:41)
    org.geoserver.ows.Dispatcher.execute(Dispatcher.java:495)
    org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:188)
   
org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:139)
   
org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:44)
   
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:684)
   
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:626).............................................................................................

--
View this message in context: http://www.nabble.com/GS-stuck-and-servlet-failed-Errors-tp14723155p14723155.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

Hi Dominique,

The first exception looks like something that happens when the client
closes a connection before the server is done writing the response. The
second exception has be baffled... never seen this one before. Although
I have never run GeoServer on rockit or in weblogic before. Is it
possible for you to try running on a sun jdk?

Also, what are the steps you are taking to reproduce. Is there a single
request that triggers the problem... or does it occur at random?

-Justin

dbhalsema wrote:

i just downloaded 1.6RC2 version and everything seemed to be working fine,
until i got the following errors. I dont know if they have to do with
weblogic or geoserver, but if anyone has any clue what they are please let
me know thanks....ps. one stacktrace is long so i shortened it.

<Jan 9, 2008 8:27:57 AM PST> <Error> <HTTP> <BEA-101020>
<[weblogic.servlet.internal.WebAppServletContext@anonymised.com - appName:
'geoserver', name: 'geoserver', context-path: '/geoserver'] Servlet failed
with Exception
java.lang.RuntimeException: java.net.SocketException: Write failed: Broken
pipe
        at
org.geoserver.wfs.response.WfsExceptionHandler.handle1_0(WfsExceptionHandler.java:104)
        at
org.geoserver.wfs.response.WfsExceptionHandler.handleServiceException(WfsExceptionHandler.java:50)
        at org.geoserver.ows.Dispatcher.exception(Dispatcher.java:1179)
        at
org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:198)
        at
org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:139)
        Truncated. see log file for complete stacktrace
java.net.SocketException: Write failed: Broken pipe
        at jrockit.net.SocketNativeIO.writeBytesPinned(I[BII)V(Native
Method)
        at
jrockit.net.SocketNativeIO.socketWrite(Ljava.io.FileDescriptor;[BII)V(Unknown
Source)
        at
java.net.SocketOutputStream.socketWrite0(Ljava.io.FileDescriptor;[BII)V(SocketOutputStream.java:???)
        at
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
        Truncated. see log file for complete stacktrace
<Jan 9, 2008 8:28:00 AM PST> <Error> <WebLogicServer> <BEA-000337> <[STUCK]
ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)' has
been busy for "635" seconds working on the request "Http Request:
/geoserver/wfs", which is more than the configured time (StuckThreadMaxTime)
of "600" seconds. Stack trace:
Thread-66 "[STUCK] ExecuteThread: '11' for queue: 'weblogic.kernel.Default
(self-tuning)'" <alive, in native, blocked, priority=1, DAEMON> {
    -- Blocked trying to get lock:
org.apache.log4j.spi.RootLogger@anonymised.com[fat lock]
    jrockit.vm.Threads.waitForSignal(Native Method)
    jrockit.vm.Locks.fatLockBlockOrSpin(Unknown Source)
    jrockit.vm.Locks.lockFat(Unknown Source)
    jrockit.vm.Locks.monitorEnterSecondStage(Unknown Source)
    jrockit.vm.Locks.monitorEnter(Unknown Source)
    org.apache.log4j.Category.callAppenders(Category.java:201)
    org.apache.log4j.Category.forcedLog(Category.java:388)
    org.apache.log4j.Category.debug(Category.java:257)
    org.geotools.util.logging.Log4JLogger.finer(Log4JLogger.java:134)
   
org.geoserver.wfs.InsertElementHandler.execute(InsertElementHandler.java:72)
    org.geoserver.wfs.Transaction.execute(Transaction.java:328)
    org.geoserver.wfs.Transaction.transaction(Transaction.java:104)
   
org.geoserver.wfs.DefaultWebFeatureService.transaction(DefaultWebFeatureService.java:156)
    jrockit.vm.RNI.c2java(Native Method)
    jrockit.reflect.NativeMethodInvoker.invoke0(Native Method)
    jrockit.reflect.NativeMethodInvoker.invoke(Unknown Source)
    jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)
    java.lang.reflect.Method.invoke(Unknown Source)
   
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:292)
   
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:155)
   
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:144)
    org.geoserver.wfs.WFSLogger.invoke(WFSLogger.java:44)
   
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:144)
   
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:174)
    $Proxy117.transaction(Unknown Source)
    jrockit.vm.RNI.c2java(Native Method)
    jrockit.reflect.NativeMethodInvoker.invoke0(Native Method)
    jrockit.reflect.NativeMethodInvoker.invoke(Unknown Source)
    jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)
    java.lang.reflect.Method.invoke(Unknown Source)
   
org.geoserver.security.OperationSecurityInterceptor.invoke(OperationSecurityInterceptor.java:41)
    org.geoserver.ows.Dispatcher.execute(Dispatcher.java:495)
    org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:188)
   
org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:139)
   
org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:44)
   
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:684)
   
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:626).............................................................................................

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

Hi,

I do not know if this is of any help, but I had quite the same stack
trace (the "broken pipe" one, to be exact) today when consuming WMS
from a coverage store.

My setup: Sun JDK 1.6, JBoss 4.2.1, GeoServer 1.6rc2.

Regards,
Andreas.

On Jan 9, 2008 11:50 PM, Justin Deoliveira <jdeolive@anonymised.com> wrote:

Hi Dominique,

The first exception looks like something that happens when the client
closes a connection before the server is done writing the response. The
second exception has be baffled... never seen this one before. Although
I have never run GeoServer on rockit or in weblogic before. Is it
possible for you to try running on a sun jdk?

Also, what are the steps you are taking to reproduce. Is there a single
request that triggers the problem... or does it occur at random?

-Justin

Yeah, that error really just means that the client moved on to something else. We really should make that exception just a line, instead of a big scary stack trace, since it happens fairly often that the client doesn't want something that it asked for. Anyone want to create a jira for it? I feel like we've talked about it before but never got an issue out of it.

C

Andreas Hocevar wrote:

Hi,

I do not know if this is of any help, but I had quite the same stack
trace (the "broken pipe" one, to be exact) today when consuming WMS
from a coverage store.

My setup: Sun JDK 1.6, JBoss 4.2.1, GeoServer 1.6rc2.

Regards,
Andreas.

On Jan 9, 2008 11:50 PM, Justin Deoliveira <jdeolive@anonymised.com> wrote:

Hi Dominique,

The first exception looks like something that happens when the client
closes a connection before the server is done writing the response. The
second exception has be baffled... never seen this one before. Although
I have never run GeoServer on rockit or in weblogic before. Is it
possible for you to try running on a sun jdk?

Also, what are the steps you are taking to reproduce. Is there a single
request that triggers the problem... or does it occur at random?

-Justin

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

!DSPAM:4005,478554e0120081030819293!

Chris Holmes ha scritto:

Yeah, that error really just means that the client moved on to something else. We really should make that exception just a line, instead of a big scary stack trace, since it happens fairly often that the client doesn't want something that it asked for. Anyone want to create a jira for it? I feel like we've talked about it before but never got an issue out of it.

Heh, I already tried to avoid these stack traces and in fact some
of them aren't being reported anymore, but evidently I did not
close all of them, or something changed in the way exception go up
to the dispatcher.

Opened the jira:
http://jira.codehaus.org/browse/GEOS-1663

Cheers
Andrea

I am not so much worried about the exception that occurs when the client
aborts but the one reported that hangs geoserver. It seems to be
blocking inside of a logging statement?

<Jan 9, 2008 8:28:00 AM PST> <Error> <WebLogicServer> <BEA-000337> <[STUCK]
ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)' has
been busy for "635" seconds working on the request "Http Request:
/geoserver/wfs", which is more than the configured time (StuckThreadMaxTime)
of "600" seconds. Stack trace:
Thread-66 "[STUCK] ExecuteThread: '11' for queue: 'weblogic.kernel.Default
(self-tuning)'" <alive, in native, blocked, priority=1, DAEMON> {
    -- Blocked trying to get lock:
org.apache.log4j.spi.RootLogger@anonymised.com[fat lock]
    jrockit.vm.Threads.waitForSignal(Native Method)
    jrockit.vm.Locks.fatLockBlockOrSpin(Unknown Source)
    jrockit.vm.Locks.lockFat(Unknown Source)
    jrockit.vm.Locks.monitorEnterSecondStage(Unknown Source)
    jrockit.vm.Locks.monitorEnter(Unknown Source)
    org.apache.log4j.Category.callAppenders(Category.java:201)
    org.apache.log4j.Category.forcedLog(Category.java:388)
    org.apache.log4j.Category.debug(Category.java:257)
    org.geotools.util.logging.Log4JLogger.finer(Log4JLogger.java:134)

Doing a quick google search it seems that deadlocks are not uncommon
with weblogic:

http://www.google.ca/search?hl=en&q=weblogic+%2B+Blocked+trying+to+get+lock

Like I said I have never used weblogic but it appears there might be
some tweaking that you can do on the server side.

-Justin

Andrea Aime wrote:

Chris Holmes ha scritto:

Yeah, that error really just means that the client moved on to something
else. We really should make that exception just a line, instead of a
big scary stack trace, since it happens fairly often that the client
doesn't want something that it asked for. Anyone want to create a jira
for it? I feel like we've talked about it before but never got an issue
out of it.

Heh, I already tried to avoid these stack traces and in fact some
of them aren't being reported anymore, but evidently I did not
close all of them, or something changed in the way exception go up
to the dispatcher.

Opened the jira:
http://jira.codehaus.org/browse/GEOS-1663

Cheers
Andrea

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

!DSPAM:4007,4785cde8258171096210785!

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

I just want to be clear on this…the error has to do with weblogic and not geoserver right. and i cant do anything with geoserver to avoid a deadlock.

On 1/10/08, Justin Deoliveira <jdeolive@anonymised.com> wrote:

I am not so much worried about the exception that occurs when the client
aborts but the one reported that hangs geoserver. It seems to be
blocking inside of a logging statement?

<Jan 9, 2008 8:28:00 AM PST> <[STUCK]
ExecuteThread: ‘11’ for queue: ‘weblogic.kernel.Default (self-tuning)’ has
been busy for “635” seconds working on the request “Http Request:
/geoserver/wfs”, which is more than the configured time (StuckThreadMaxTime)
of “600” seconds. Stack trace:
Thread-66 “[STUCK] ExecuteThread: ‘11’ for queue: ‘weblogic.kernel.Default
(self-tuning)’” <alive, in native, blocked, priority=1, DAEMON> {
– Blocked trying to get lock:
org.apache.log4j.spi.RootLogger@anonymised.com [fat lock]
jrockit.vm.Threads.waitForSignal(Native Method)
jrockit.vm.Locks.fatLockBlockOrSpin(Unknown Source)
jrockit.vm.Locks.lockFat(Unknown Source)
jrockit.vm.Locks.monitorEnterSecondStage(Unknown Source)
jrockit.vm.Locks.monitorEnter(Unknown Source)
org.apache.log4j.Category.callAppenders(Category.java:201)
org.apache.log4j.Category.forcedLog(Category.java:388)
org.apache.log4j.Category.debug(Category.java :257)
org.geotools.util.logging.Log4JLogger.finer(Log4JLogger.java:134)

Doing a quick google search it seems that deadlocks are not uncommon
with weblogic:

http://www.google.ca/search?hl=en&q=weblogic+%2B+Blocked+trying+to+get+lock

Like I said I have never used weblogic but it appears there might be
some tweaking that you can do on the server side.

-Justin

Andrea Aime wrote:

Chris Holmes ha scritto:

Yeah, that error really just means that the client moved on to something
else. We really should make that exception just a line, instead of a
big scary stack trace, since it happens fairly often that the client
doesn’t want something that it asked for. Anyone want to create a jira
for it? I feel like we’ve talked about it before but never got an issue
out of it.

Heh, I already tried to avoid these stack traces and in fact some
of them aren’t being reported anymore, but evidently I did not
close all of them, or something changed in the way exception go up
to the dispatcher.

Opened the jira:
http://jira.codehaus.org/browse/GEOS-1663

Cheers
Andrea


Check out the new SourceForge.net Marketplace.
It’s the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace


Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

!DSPAM:4007,4785cde8258171096210785!


Justin Deoliveira
The Open Planning Project
http://topp.openplans.org


Check out the new SourceForge.net Marketplace.
It’s the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace


Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Hi Dominique,

From what I found by doing a bit of web searching I would say yes. I

found posts on a number of forms of users having thread locking issues
with weblogic in different web applications.

Now there may be something we can do in GeoServer to prevent this... but
it is not evident what that may be. I would need a weblogic setup in
order to debug the problem. And even then the random nature of this
problem would make that difficult.

I suspect that it is more likely that we could find a solution by
performing some tweaks on the application server itself.

-Justin

Dominique Bessette - Halsema wrote:

I just want to be clear on this...the error has to do with weblogic and
not geoserver right. and i cant do anything with geoserver to avoid a
deadlock.

On 1/10/08, *Justin Deoliveira* <jdeolive@anonymised.com
<mailto:jdeolive@anonymised.com>> wrote:

    I am not so much worried about the exception that occurs when the client
    aborts but the one reported that hangs geoserver. It seems to be
    blocking inside of a logging statement?

    <Jan 9, 2008 8:28:00 AM PST> <Error> <WebLogicServer> <BEA-000337>
    <[STUCK]
    ExecuteThread: '11' for queue: 'weblogic.kernel.Default
    (self-tuning)' has
    been busy for "635" seconds working on the request "Http Request:
    /geoserver/wfs", which is more than the configured time
    (StuckThreadMaxTime)
    of "600" seconds. Stack trace:
    Thread-66 "[STUCK] ExecuteThread: '11' for queue:
    'weblogic.kernel.Default
    (self-tuning)'" <alive, in native, blocked, priority=1, DAEMON> {
       -- Blocked trying to get lock:
    org.apache.log4j.spi.RootLogger@anonymised.com [fat lock]
       jrockit.vm.Threads.waitForSignal(Native Method)
       jrockit.vm.Locks.fatLockBlockOrSpin(Unknown Source)
       jrockit.vm.Locks.lockFat(Unknown Source)
       jrockit.vm.Locks.monitorEnterSecondStage(Unknown Source)
       jrockit.vm.Locks.monitorEnter(Unknown Source)
       org.apache.log4j.Category.callAppenders(Category.java:201)
       org.apache.log4j.Category.forcedLog(Category.java:388)
       org.apache.log4j.Category.debug(Category.java :257)
       org.geotools.util.logging.Log4JLogger.finer(Log4JLogger.java:134)

    Doing a quick google search it seems that deadlocks are not uncommon
    with weblogic:

    http://www.google.ca/search?hl=en&q=weblogic+%2B+Blocked+trying+to+get+lock
    <http://www.google.ca/search?hl=en&q=weblogic+%2B+Blocked+trying+to+get+lock&gt;

    Like I said I have never used weblogic but it appears there might be
    some tweaking that you can do on the server side.

    -Justin

    Andrea Aime wrote:
    > Chris Holmes ha scritto:
    >> Yeah, that error really just means that the client moved on to
    something
    >> else. We really should make that exception just a line, instead
    of a
    >> big scary stack trace, since it happens fairly often that the client
    >> doesn't want something that it asked for. Anyone want to create
    a jira
    >> for it? I feel like we've talked about it before but never got
    an issue
    >> out of it.
    >
    > Heh, I already tried to avoid these stack traces and in fact some
    > of them aren't being reported anymore, but evidently I did not
    > close all of them, or something changed in the way exception go up
    > to the dispatcher.
    >
    > Opened the jira:
    > http://jira.codehaus.org/browse/GEOS-1663
    >
    > Cheers
    > Andrea
    >
    >
    -------------------------------------------------------------------------

    > Check out the new SourceForge.net Marketplace.
    > It's the best place to buy or sell services for
    > just about anything Open Source.
    >
    http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
    > _______________________________________________
    > Geoserver-users mailing list
    > Geoserver-users@lists.sourceforge.net
    <mailto:Geoserver-users@lists.sourceforge.net>
    > https://lists.sourceforge.net/lists/listinfo/geoserver-users
    >
    >
    >

    --
    Justin Deoliveira
    The Open Planning Project
    http://topp.openplans.org

    -------------------------------------------------------------------------

    Check out the new SourceForge.net Marketplace.
    It's the best place to buy or sell services for
    just about anything Open Source.
    http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
    _______________________________________________
    Geoserver-users mailing list
    Geoserver-users@lists.sourceforge.net
    <mailto:Geoserver-users@lists.sourceforge.net>
    https://lists.sourceforge.net/lists/listinfo/geoserver-users

!DSPAM:4007,4787fad2106828992556831!

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org