Hi,
Would it be possible that first request comes to a node in the web farm
which initialised the Service Bus - i.e creates Rhino Queue folders, etc. -
then a second request comes through and it's forwarded to a second node.
The second node's AppPool will initialise the Bus again and try to get
access to the Rhino Queues ESENT files.
Apologies if the scenario above doesn't make any sense - haven't used
neither RSB nor web load balance before.
If this was the problem, would there be any workaround?
Another problem we have here is that our "corporative" platform doesn't
allow us to write on the web server file system, hence we have had to
create the client queue folders on a shared. Our web.config RSB section
looks like below:
<rhino.esb>
<bus threadCount="1" numberOfRetries="1"
endpoint="rhino.queues://#web_hostname#/ICE_WEB" name="client"
path="\\#shared_drive#\ICEBus" />
<messages>
<add name="CS.RAR.ICE.Common.Messages"
endpoint="rhino.queues://#backend_hostname#/ICE_ETL" />
</messages>
</rhino.esb>
Any thoughts?
Thanks.
On Monday, November 5, 2012 6:03:59 PM UTC, Daventry wrote:
> Hi,
>
> We thought we had fix it, still having problems.
>
> Looks like it happens when running in IIS with load balance enabled. It is
> all right when running off our workstations. Have you seen this before?
>
> Thanks.
--
You received this message because you are subscribed to the Google Groups
"Rhino Tools Dev" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/rhino-tools-dev/-/_TTp5h4IerQJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/rhino-tools-dev?hl=en.
