I'm still confused. There's multiple broker configurations in the zip and questions about both static and dynamic discovery. For the sake of clarity, can we focus on just *one* issue? If possible, provide configuration for either static or dynamic discovery (i.e. not both) and ask questions that only deal with that particular configuration.
Also, please do not continue sending pptx files. Please use a more ubiquitous file format (e.g. txt, pdf, etc.), or better yet, just describe your use-case and the problem you're seeing directly in the body of the email as is customarily done on this mailing list. Folks providing support on this mailing list are doing so on a volunteer basis so it helps when folks needing support ask questions which are clear and concise as possible. Thanks! Justin On Thu, Oct 24, 2024 at 3:11 PM [email protected] <[email protected]> wrote: > Hi, > > I have simplified the configuration as you have suggested. However, the > same two issues still exist. > > The attached zip file contains: > - ArtemisMQ_Cluster_Oct172024.pptx This has configuration > descriptions and the questions > - primary_UDN_2 This folder has the UDN node > broker xml files > - primary_VM_2 This folder has the VM node broker > xml files > > Thank you for your help. > > Regards, > Tin (Tien) Lai > > > -----Original Message----- > From: Justin Bertram <[email protected]> > Sent: Thursday, October 24, 2024 12:40 PM > To: [email protected] > Subject: Re: EXTERNAL: Re: Artemis MQ 2.36.0 Load Balancing questions > > I looked on page 2 of the ArtemisMQ_Cluster_Oct172024.pptx in the archive > which you attached to your original email, but I found no questions. > However, I see that you've added them in your response. > > I find the questions and the configuration confusing. > > First, automatic discovery (e.g. via UDP) or static connectors can be used > to form a cluster. You cannot, as far as I'm aware, use both > simultaneously. Therefore, please choose one or the other. It's not clear > why you would even try to use both. > > Second, you say that messages are not forwarded, but you don't describe > the details of the use-case. For example, you make no mention of where > messages are sent, where consumers are created, etc. > > Last, generally speaking it's best to start simple and add complexity once > the desired functionality has been validated. In this case you're testing > message load-balancing which requires multiple primary servers. It doesn't > require any backups. It would be useful to simplify your configuration to > eliminate any complexity that isn't absolutely required to reproduce the > problem. In this case, you can drop your backups and simply focus on the > two clustered primary servers. > > > Justin > > On Thu, Oct 24, 2024 at 9:42 AM [email protected] <[email protected]> > wrote: > > > Hi, > > > > Thanks for the name correction. > > > > The questions are on page 2 of the ArtemisMQ_Cluster_Oct172024.pptx, > > which describes the configuration and the questions. They are listed > here: > > > > ------ > > Issue 1: > > - UDN node and VM node all use Dynamic discovery > > - Cluster connections were established > > - Messages either were not forwarded by UDN node, or were not received > > by VM node > > - Succeeded ONLY after restarting the UDN Primary Server > > > > QUESTION 1: How to configure so that UDN node server would forward > > messages to VM node server upon startup when all are using Dynamic > > discovery? > > > > ------ > > Issue 2: > > UDN node uses Dynamic discovery , VM uses Static Connectors: > > Added address name="PositionReport“, as shown below in attempt to > > forward only PositionReport to VM node – but all messages still got > > forwarded <address name="PositionReport"> > > <anycast/> > > </address> > > > > QUESTION 2: How to configure so that UDN node server would only > > forward certain message, such as PositionReport, to VM node server? > > > > > > Regards, > > Tin (Tien) Lai > > > > > > > > -----Original Message----- > > From: Justin Bertram <[email protected]> > > Sent: Thursday, October 24, 2024 8:30 AM > > To: [email protected] > > Subject: EXTERNAL: Re: Artemis MQ 2.36.0 Load Balancing questions > > > > Where are the actual questions? > > > > Also, the broker is named "ActiveMQ Artemis," not "ArtemisMQ." > > > > > > Justin > > > > On Wed, Oct 23, 2024 at 3:01 PM [email protected] > > <[email protected]> > > wrote: > > > > > Hi, > > > > > > > > > > > > Attached is a zip file describing the configuration and the > > > questions I have with Load Balancing. Let me know if I need to > > > provide any additional information. > > > > > > > > > > > > Regards, > > > > > > Tin (Tien) Lai > > > > > > > > > > > > -------------------------------------------------------------------- > > > - To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] For > > > further information, visit: https://activemq.apache.org/contact > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] For > > further information, visit: https://activemq.apache.org/contact > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > For further information, visit: https://activemq.apache.org/contact >
