If I can solve the address problem, I'll see further.
Thanks and good night, Michael Am 13.06.17 um 01:51 schrieb Taher Alkhateeb:
All dependencies are stored in the gradle cache and referenced in the generated ofbiz.jar. So I guess it's somewhere in the cache. Can't you find it there? On Jun 13, 2017 2:49 AM, "Michael Brohl" <michael.br...@ecomify.de> wrote: Where would you expect the jar file to be stored? I'll try to track down the errors. I was able to reduce the error messages by adding -Djava.net.preferIPv4Stack=true to the jvm arguments in build.gradle def jvmArguments = ['-Xms128M', '-Xmx1024M', "-Djava.net.preferIPv4Stack=tr ue"] (see https://stackoverflow.com/questions/6862364/slp-java-functio n-causing-socketexception-due-to-ip-multicast-if). I know get one more exception org.apache.catalina.tribes.ChannelException: java.net.SocketException: Can't assign requested address; No faulty members identified. After a brief internet search, this could be a problem with my MacOS, I'll try this tomorrow. It would be great if others could check if OFBiz runs on their machine with configured cluster support. Regards, Michael Am 13.06.17 um 01:01 schrieb Taher Alkhateeb: A compile dependency is also a runtime dependency in gradle (as opposed tocompileOnly). So if it is defined in gradle then it is available in runtime. On Jun 13, 2017 1:57 AM, "Michael Brohl" <michael.br...@ecomify.de> wrote: Quick checked the cluster config and see that the cluster configuration depends on org.apache.catalina.ha.session.DeltaManager, whose package is configured in Gradle as a compile dependency (org.apache.tomcat:tomcat-cata lina-ha:8.5.15). Do you have this package/jar available at runtime? I cannot find it anywhere on my machine after compile. Michael Am 13.06.17 um 00:11 schrieb Taher Alkhateeb: Hi Michael,Hmmm, I didn't know that it is actively used. Essentially, you get exceptions / crashes when you uncomment the clustering section in catalina's ofbiz-component.xml. Also, I could be wrong, but I thought instead of using Tomcat's clustering, you instead cluster your infrastructure itself behind load balancers and mirroring solutions and whatnot. Anyway, if I'm wrong, then the second option is to try and figure out what's wrong with clustering and how to fix it. It's a big section of CatalinaContainer and it's currently crashing because of a missing context and a manager and a few other things. Cheers, Taher Alkhateeb On 13/06/17 01:03, Michael Brohl wrote: Hi Taher,clustering support is an important feature for enterprise installations and it worked in the past. It should be fixed if it is broken. What makes you think that clustering is broken? How did you test it? What is not working exactly? I recently updated the Tomcat version, could this be a source of the problem? Maybe there were changes in the configuration I have missed, although I did not find anything in the release notes. Regards, Michael Am 12.06.17 um 22:57 schrieb Taher Alkhateeb: Hi Everyone,In reference to [1] and the refactoring work, and after multiple different tests, I came to realize that Tomcat clustering implementation is broken (both before and after the refactoring). The reasons are complex but they essentially have to do with setting up the right parameters for the cluster. So I suspect no one is using this feature? It is therefore, my recommendation to remove clustering from CatalinaContainer which would substantially reduce complexity of both the component configuration file and the accompanying source code which would shave off at least 120 lines of code. WDYT [1] https://issues.apache.org/jira/browse/OFBIZ-9392 On Thu, Jun 8, 2017 at 3:38 PM, Taher Alkhateeb < slidingfilame...@gmail.com> wrote: Hey folks,It was very painful and slow, but I finally got a working almost full-rewrite of the CatalinaContainer. I need help with testing, reviews, and code improvements. Details are found in [1]. There are no functional changes, just a rewrite. I appreciate all the help and feedback. [1] https://issues.apache.org/jira/browse/OFBIZ-9392 Cheers, Taher Alkhateeb
smime.p7s
Description: S/MIME Cryptographic Signature
