Some more info:
- My Producer's delivery mode is PERSISTANT
- I have no consumers who would have taken the messages (and I can see htem
when restarting the Master)
- attached is my config - but its basically just the given example.
spiderman2 wrote:
>
> I've gotten the slave to succesfully wai
I've gotten the slave to succesfully wait on the db lock. Then it claims it
when I shut the master down :)
The bad part: I've placed 100 message in the Master's queue before shutdown.
Used Jconsole to verify they're there. When the Slave gets the lock and
becomes broker, Jconsole shows that it ha
Yes - so fingers crossed once you've got your classpath sorted it should be fine
On 2/9/07, spiderman2 <[EMAIL PROTECTED]> wrote:
You are right! Thanks! I'm fairly sure this is the problem. I had the
datasource commented out! AH!
Now I am pointing the #oracle-ds as in the example. My only next
You are right! Thanks! I'm fairly sure this is the problem. I had the
datasource commented out! AH!
Now I am pointing the #oracle-ds as in the example. My only next issue is
adding the 'oracle.jdbc.driver.OracleDriver' to my classpath. I didn't
realize this wasn't included in the distrubution and
That looks like the problem then :)
If you post the complete XML config you're using we can point out the
mistake. You basically need to refer to the #oracle-ds in your
like the example does...
On 2/9/07, spiderman2 <[EMAIL PROTECTED]> wrote:
I've now tried running the Master and Sl
I've now tried running the Master and Slave on different hosts, as the JDBC
Master-Slave example intends. I see the same thing.
James, it seems you are right in that they don't seem to be using the same
DB. They are both configured to use:
HOWEVER, from the logs I'll
Note that with JDBC Master/Slave you don't network them together -
with JDBC Master/Slave there is no direct master-slave communication.
Nor should they be aware of each other, as the slave does not start
listening on any sockets until it becomes the master (for JDBC
master/slave).
Could you show
