Indeed, as I already mentioned, monitor-hibernate and geofence-plugin are simply incompatible. The version of hibernate that monitoring uses is even older than geofence. Monitoring needs some code changes though to make it work with a newer version. Who maintains this module?

On 30-08-17 16:12, Steve Omondi wrote:
I'm trying to use the Geofence Internal Server together with Monitoring Plugin + Monitor-hibernate to allow persisting the monitoring data to Postgis. I have checked the .jar files in geofence-plugin and those in monitor-hibernate and they are of different versions. Installing them together in on Geoserver breaks everything and Geoserver refuses to start

Will this upgrade also consider the Monitoring Hibernate plugin. And as we wait fro the upgrade, what is the solution of running plugins with conflicting .jar libraries?

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>


Kind regards,
Steve Omondi

On Tue, Aug 29, 2017 at 11:22 AM, Andrea Aime <andrea.a...@geo-solutions.it <mailto:andrea.a...@geo-solutions.it>> wrote:

    Hi,
    separate mail for the upgrade tests.

    On Tue, Aug 29, 2017 at 10:18 AM, Andrea Aime
    <andrea.a...@geo-solutions.it
    <mailto:andrea.a...@geo-solutions.it>> wrote:

        On Tue, Aug 29, 2017 at 12:32 AM, Niels Charlier
        <ni...@scitus.be <mailto:ni...@scitus.be>> wrote:

            An update on this issue:

            I have tested the migration jar file and it did a
            succesfull, automatic upgrade for disk quota, jdbcconfig,
            jdbcstore, geofence-server and monitoring. It failed for a
            netcdf datastore (the upgrade stopped with an exception),
            however the good thing about netcdf is that you can simply
            delete it and it rebuilds automatically so it is less
            crucial (and could be perhaps automated in this way).


    This seems promising. NetCDF wise, the worry I have is that these
    files are sprinkled around on the file system,
    sidecars to the netcdf files themselves. Wondering if the removal
    and rebuild could be automated?

    The other issue is that the upgrade will make it impossible to
    move back, while this is unavoidable, it needs to be
    well advertised. And it will cause pain for a year long for
    developers jumping across branches (e.g., everybody
    working in the GeoServer stable/maintenance branches).
    I'm afraid it's a bridge we'll have to cross sooner or later...
    hum... thinking out loud, would it make sense to create parallel
    databases,
    old version and new version, with a different name? I guess the
    pain is that this would require point by point changes in the code...

    Cherees
    Andrea


--
    Regards,

    Andrea Aime

    ==GeoServer Professional Services from the experts! Visit
    http://goo.gl/it488V for more information.==Ing. Andrea Aime
    @geowolfTechnical LeadGeoSolutions S.A.S.Via di Montramito
    3/A55054  Massarosa (LU)phone: +39 0584 962313fax: +39 0584
    1660272mob: +39  339
    8844549http://www.geo-solutions.ithttp://twitter.com/geosolutions_it
    <http://twitter.com/geosolutions_it>

    AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

    Le informazioni contenute in questo messaggio di posta elettronica
    e/o nel/i file/s allegato/i sono da considerarsi strettamente
    riservate. Il loro utilizzo è consentito esclusivamente al
    destinatario del messaggio, per le finalità indicate nel messaggio
    stesso. Qualora riceviate questo messaggio senza esserne il
    destinatario, Vi preghiamo cortesemente di darcene notizia via
    e-mail e di procedere alla distruzione del messaggio stesso,
    cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
    divulgarlo anche in parte, distribuirlo ad altri soggetti,
    copiarlo, od utilizzarlo per finalità diverse, costituisce
    comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

    The information in this message and/or attachments, is intended
    solely for the attention and use of the named addressee(s) and may
    be confidential or proprietary in nature or covered by the
    provisions of privacy act (Legislative Decree June, 30 2003,
    no.196 - Italy's New Data Protection Code).Any use not in accord
    with its purpose, any disclosure, reproduction, copying,
    distribution, or either dissemination, either whole or partial, is
    strictly forbidden except previous formal approval of the named
    addressee(s). If you are not the intended recipient, please
    contact immediately the sender by telephone, fax or e-mail and
    delete the information in this message that has been received in
    error. The sender does not give any warranty or accept liability
    as the content, accuracy or completeness of sent messages and
    accepts no responsibility  for changes made after they were sent
    or for other risks which arise as a result of e-mail transmission,
    viruses, etc.


    
------------------------------------------------------------------------------
    Check out the vibrant tech community on one of the world's most
    engaging tech sites, Slashdot.org! http://sdm.link/slashdot
    _______________________________________________
    Geoserver-devel mailing list
    Geoserver-devel@lists.sourceforge.net
    <mailto:Geoserver-devel@lists.sourceforge.net>
    https://lists.sourceforge.net/lists/listinfo/geoserver-devel
    <https://lists.sourceforge.net/lists/listinfo/geoserver-devel>



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to