[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_38423
]
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:52:05 +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:52:26 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300352Z2SAV7BC
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_38422
]
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:50: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:50:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300350CXXNB969
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_38421
]
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:48: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:48:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300348CXXNB96S
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_38420
]
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:46: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:46:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300346Z2SAV7AJ
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_38419
]
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:44: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:44:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300344CXXNB96A
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_38418
]
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:42:06 +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:42:10 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300342CXXNB95Y
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_38417
]
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:40: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:40:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300340CXXNB953
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_38416
]
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:38: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:38:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300338CXXNB95C
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_38415
]
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:36: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:36:37 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300336Z2SAV69N
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_38414
]
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:34: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:34:47 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300334CXXNB9ZB
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_38413
]
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:32: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:32:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300332Z2SAV68N
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_38412
]
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:30: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:30:10 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300330CXXNB9X3
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_38411
]
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:28: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:28:05 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300328Z2SAV665
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_38410
]
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:26: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:26:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300326CXXNB9WD
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_38409
]
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:24: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:24:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300324CXXNB9VX
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_38408
]
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:22:05 +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:22:09 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300322Z2SAV65K
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_38407
]
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:02: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:02:05 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300302Z2SAV6S1
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_38406
]
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:00:25 +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:00:48 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300300CXXNB9MJ
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_38405
]
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 03:58: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 03:58:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300258Z2SAV6RF
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_38404
]
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 03:56: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 03:56:21 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300256CXXNB9LW
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_38403
]
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 03:54:05 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Tue, 30 Jan 2007 03:54:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300254CXXNB9LH
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_38402
]
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 03:52: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 03:52:09 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300252Z2SAV6QJ
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_38401
]
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 03:50:05 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Tue, 30 Jan 2007 03:50:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300250Z2SAV6P6
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_38400
]
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 03:48: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 03:48:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300248Z2SAV6PT
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_38399
]
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 03:46: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 03:46:09 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300246CXXNB9J8
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_38398
]
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 03:44: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 03:44:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300244Z2SAV6PD
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_38397
]
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 03:42: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 03:42:05 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300242Z2SAV63R
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_38396
]
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 03:40: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 03:40:11 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300240CXXNB92P
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_38395
]
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 03:38: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 03:38:48 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300238CXXNB92B
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_38394
]
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 03:36: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 03:36:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300236CXXNB9HX
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_38393
]
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 03:34: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 03:34:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300234CXXNB9HN
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_38392
]
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 03:32: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 03:32:11 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300232CXXNB9HC
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_38391
]
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 03:30: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 03:30:05 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300230Z2SAV6MH
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_38390
]
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 03:28:05 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Tue, 30 Jan 2007 03:28:10 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300228CXXNB9GR
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_38389
]
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 03:26: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 03:26:38 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300226Z2SAV6LT
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_38388
]
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 03:24: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 03:24:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300224CXXNB9FZ
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_38387
]
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 03:22: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 03:22:05 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300222Z2SAV6KT
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_38386
]
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 03:20: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 03:20:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300220Z2SAV6KF
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_38385
]
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 03:18: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 03:18:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300218Z2SAV6J7
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_38384
]
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 03:16: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 03:16:09 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300216CXXNB91K
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_38383
]
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 03:14: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 03:14:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300214Z2SAV6JF
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_38382
]
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 03:12: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 03:12:11 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300212CXXNB9DX
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_38381
]
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 03:10: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 03:10:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300210CXXNB9DQ
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_38380
]
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 03:08: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 03:08:11 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300208CXXNB9C6
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_38379
]
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 03:06: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 03:06:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300206CXXNB9CB
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_38378
]
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 03:04: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 03:04:10 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300204CXXNB9BW
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_38377
]
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 03:02: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 03:02:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300202CXXNB9BK
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_38376
]
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 03:00:21 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Tue, 30 Jan 2007 03:00:25 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300200Z2SAV6G1
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_38375
]
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 02:58: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 02:58:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300158CXXNB9AV
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_38374
]
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 02:56: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 02:56:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300156CXXNB9AL
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_38373
]
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 02: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 02:54:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300154CXXNB806
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_38372
]
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 02:52: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 02:52:38 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300152CXXNB804
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_38371
]
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 02:50: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 02:50:05 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300150Z2SAV61L
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_38370
]
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 02:48: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 02:48:05 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300148Z2SAV611
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_38369
]
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 02:46: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 02:46:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300146Z2SAV6D9
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_38368
]
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 02:44: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 02:44:05 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300144Z2SAV6D4
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_38367
]
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 02:42: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 02:42:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300142Z2SAV6D2
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_38366
]
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 02:40: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 02:40:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300140CXXNB89D
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_38365
]
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 02:38: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 02:38:09 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300138CXXNB88Y
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_38364
]
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 02:36: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 02:36:10 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300136CXXNB88L
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_38363
]
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 02:34: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 02:34:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300134Z2SAV6B9
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_38362
]
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 02:32: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 02:32:11 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300132Z2SAV6BT
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_38361
]
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 02:30: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 02:30:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300130Z2SAV6B1
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_38360
]
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 02:28: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 02:28:11 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300128CXXNB866
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_38359
]
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 02:26: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 02:26:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300126Z2SAV6A3
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_38358
]
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 02:24: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 02:24:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300124Z2SAV6AB
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_38357
]
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 02:22: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 02:22:05 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300122Z2SAV50W
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_38356
]
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 02:20: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 02:20:09 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300120Z2SAV50G
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_38355
]
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 02:18:05 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Tue, 30 Jan 2007 02:18:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300118CXXNB8Z7
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_38354
]
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 02:16: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 02:16:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300116CXXNB8XN
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_38353
]
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 02:14: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 02:14:05 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300114Z2SAV56H
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_38352
]
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 02:12: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 02:12:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300112CXXNB8V7
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_38351
]
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 02:10: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 02:10:05 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300110Z2SAV553
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_38350
]
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 02:08: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 02:08:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300108Z2SAV5Z8
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_38349
]
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 02:06: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 02:06:05 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300106Z2SAV5Z4
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_38348
]
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 02:04: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 02:04:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300104Z2SAV5ZH
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_38347
]
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 02:02: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 02:02:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300102CXXNB841
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_38346
]
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 02:00:29 +0100
did not reach the following recipient(s):
c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Tue, 30 Jan 2007 02:00:34 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300100CXXNB8T6
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_38345
]
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:58: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 01:58:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300058CXXNB8TQ
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_38344
]
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:56: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 01:56:13 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300056Z2SAV5YD
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_38343
]
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:54:05 +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:54:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300054Z2SAV5XZ
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_38342
]
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:52: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:52:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300052Z2SAV5XP
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_38341
]
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:50: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:50:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300050CXXNB8SD
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_38340
]
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:48: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:48:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300048Z2SAV5WW
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_38339
]
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:46:06 +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:46:11 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300046Z2SAV5W3
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_38338
]
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:44: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:44:05 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300044Z2SAV5WA
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_38337
]
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:42: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:42:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300042CXXNB8Q3
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_38336
]
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:40: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:40:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300040CXXNB8Q1
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_38335
]
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:38:05 +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:38:10 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300038CXXNB8JP
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_38332
]
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:32: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:32:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300032Z2SAV5MM
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_38331
]
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:30: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:30:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300030CXXNB8G4
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_38330
]
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:28: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:28:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300028Z2SAV5K8
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_38329
]
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:26: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 01:26:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300026CXXNB8FX
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_38328
]
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:24:05 +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:24:18 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300024CXXNB8FF
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_38327
]
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:22: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:22:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300022CXXNB815
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_38326
]
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:20: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:20:09 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300020CXXNB81M
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_38325
]
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:18: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:18:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300018CXXNB8D8
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_38324
]
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:16: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 01:16:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300016CXXNB8D3
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_38323
]
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:14: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:14:05 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300014Z2SAV521
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_38322
]
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:12: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 01:12:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701300012Z2SAV5HY
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.
