Hey Andrea, Thanks so much for the info! I really appreciate your prospective. I'm still struggling to get JMS setup in AWS. I had thought of using AmazonMQ (hosted ActiveMQ) service as the broker service. My thought is that I would just be able to update the brokerURL with that of the AmazonMQ instance, disable the embedded Broker. However, i get this error:
2019-05-01 16:32:17,923 WARN [client.JMSContainer] - Setup of JMS message listener invoker failed for destination 'queue://Consumer.46883c30-cd00-4097-84d1-b68adceedf8e.VirtualTopic.geoserver' - trying to recover. Cause: java.lang.IllegalStateException: Pool not open I'm clearly doing something wrong or misunderstanding the config. Anyone know if AmazonMQ would even work? Or if i'm missing a configuration step here. Thanks! Jason On Wed, May 1, 2019 at 1:36 AM Andrea Aime <andrea.a...@geo-solutions.it> wrote: > On Wed, May 1, 2019 at 6:50 AM Jason Cradit <jasoncra...@gmail.com> wrote: > >> With the JMS extension, it seems that if we use the JDBC extension it >> won't even start the container. So it's like JDBC and JMS can't be >> installed together. That may not be true, but that's what i'm seeing, >> currently. There is also an issue with using multi-cast in AWS, it doesn't >> work. So i'm reading to figure out how that challenge could be overcome. >> > > While JMS works mostly off generic catalog interfaces, it has never been > used, as far as I know, along with JDBCConfig, so not surprised if you get > in trouble there. > > One note about JDBCConfig, make sure that's the long term direction you > want to go, once you have the data in the database, I don't believe there > is a procedure to get it back out on the file system. > Also, if the configuration elements in GeoServer change (e.g., a field > disappears), I don't recall any presence of an upgrade procedures either > (the module maps certain properties out of the XML blobs into indexable > columns, it might not work properly anymore if one of those disappear). > The same goes if the module is modified to map out new attributes to get > better performance in some use cases (which has happened in the past), also > in the case there is, AFAIK, no procedure > to map out the new attribute from XML blobs already stored in the DB. > > Might not be like that anymore, that seemed to be the case when I tried it > out years ago, but I'd at least double check. > > Cheers > Andrea > > == > > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf > Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa > (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 > http://www.geo-solutions.it http://twitter.com/geosolutions_it > ------------------------------------------------------- *Con riferimento > alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - > Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni > circostanza inerente alla presente email (il suo contenuto, gli eventuali > allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i > destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per > errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le > sarei comunque grato se potesse darmene notizia. This email is intended > only for the person or entity to which it is addressed and may contain > information that is privileged, confidential or otherwise protected from > disclosure. We remind that - as provided by European Regulation 2016/679 > “GDPR” - copying, dissemination or use of this e-mail or the information > herein by anyone other than the intended recipient is prohibited. If you > have received this email by mistake, please notify us immediately by > telephone or e-mail.* >
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
