[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38433
]
Adrian Co commented on AMQ-1142:
Also, I'm not sure if this is a bug or not. :)
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38432
]
Adrian Co commented on AMQ-1142:
IMHO, I think the appropriate way to accomplish this is to set the JMSReplyTo
property of the message with the temporary queue. And upon receipt of the
message, get the reply to property and send to that.
Let me know if that works for you.
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38424
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Tue, 30 Jan 2007 04:54:04 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Tue, 30 Jan 2007 04:54:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300354Z2SAV7BM
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38334
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Tue, 30 Jan 2007 01:36:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Tue, 30 Jan 2007 01:36:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300036CXXNB826
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38333
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Tue, 30 Jan 2007 01:34:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Tue, 30 Jan 2007 01:34:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300034CXXNB82K
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38218
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 21:45:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:45:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701292045Z2SAVXZ3
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38217
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 21:43:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:43:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701292043Z2SAVXYR
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38216
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 21:41:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:41:05 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701292041Z2SAVXXL
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38215
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 21:39:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:39:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701292039CXXNB5SZ
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38214
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 21:37:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:37:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701292037CXXNB5R9
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38213
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 21:35:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:35:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701292035Z2SAVX4X
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38212
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 21:33:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:33:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701292033CXXNB5PH
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38211
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 21:31:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:31:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701292031Z2SAVXS1
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38210
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 21:29:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:29:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701292029CXXNB5N3
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38209
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 21:27:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:27:20 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701292027CXXNB5MT
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38208
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 21:25:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:25:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701292025CXXNB5LW
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38207
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 21:23:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:23:10 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701292023Z2SAVX3Z
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38206
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 21:21:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:21:05 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701292021Z2SAVXN8
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38205
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 21:19:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:19:09 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701292019CXXNB520
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38204
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 21:17:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:17:05 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701292017Z2SAVXMK
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38203
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 21:15:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:15:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701292015CXXNB5HP
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38202
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 21:13:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:13:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701292013CXXNB5GX
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38201
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 21:11:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:11:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701292011CXXNB5F9
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38200
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 21:09:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:09:05 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701292009Z2SAVX2W
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38199
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 21:07:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:07:37 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701292007CXXNB51D
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38198
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 21:05:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:05:10 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701292005Z2SAVXG0
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38197
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 21:03:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:03:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701292003Z2SAVXGF
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38087
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 17:24:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:24:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291624CXXNB485
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38086
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 17:22:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:22:09 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291622CXXNB46L
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38085
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 17:20:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:20:04 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291620Z2SAVR5R
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38084
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 17:18:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:18:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291618CXXNB4W3
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38083
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 17:16:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:16:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291616Z2SAVRVW
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38082
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 17:14:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:14:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291614Z2SAVRT1
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38081
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 17:12:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:12:45 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291612Z2SAVRRC
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38080
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 17:10:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:10:24 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291610CXXNB4M5
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38079
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 17:08:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:08:25 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291608CXXNB4KR
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38078
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 17:06:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:06:40 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291606Z2SAVRJ6
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38077
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 17:04:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:04:09 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291604CXXNB4F3
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38076
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 17:02:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:02:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291602CXXNB4CX
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38075
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 17:00:18 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:00:24 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291600Z2SAVRCB
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38074
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 16:58:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:58:15 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291558CXXNBT88
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38073
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 16:56:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:56:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291556CXXNBT65
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38072
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 16:54:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:54:09 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291554CXXNBTZW
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38071
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 16:52:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:52:05 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291552Z2SAVQYP
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38070
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 16:50:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:50:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291550CXXNBT4P
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38069
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 16:48:04 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:48:15 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291548Z2SAVQS7
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38068
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 16:46:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:46:11 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291546Z2SAVQQB
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38067
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 16:44:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:44:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291544Z2SAVQM0
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38066
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 16:42:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:42:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291542CXXNBTJ9
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38065
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 16:40:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:40:11 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291540CXXNBTHA
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38064
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 16:38:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:38:04 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291538Z2SAVQ1W
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38063
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 16:36:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:36:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291536Z2SAVQB9
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38062
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 16:34:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:34:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291534CXXNBS9Z
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38061
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 16:32:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:32:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291532Z2SAVP7V
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38060
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 16:30:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:30:43 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291530Z2SAVP5A
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38059
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 16:28:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:28:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291528CXXNBSXN
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38058
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 16:26:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:26:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291526Z2SAVP4W
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38057
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 16:24:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:24:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291524CXXNBSS2
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38056
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 16:22:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:22:22 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291522Z2SAVP3P
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38055
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 16:20:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:20:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291520Z2SAVPL7
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38054
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 16:18:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:18:14 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291518CXXNBSJN
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1142) TemporaryQueue communication not working
[
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38053
]
System Administrator commented on AMQ-1142:
---
Your message
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
Sent:Mon, 29 Jan 2007 16:16:03 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:16:13 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291516Z2SAVPG8
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient
DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Fortis rules out any and every liability resulting from any electronic
transmission.
**
> TemporaryQueue communication not working
>
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a
> MQSerie getQueue API call, instead a createQueue, because queus are defined,
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
