[jira] Closed: (GERONIMO-2783) CXF-based WebServices support: webservices.xml file is no longer required

[Davanum Srinivas (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Davanum Srinivas closed GERONIMO-2783.
--

Resolution: Fixed

Comitted (svn revision 500959)

thanks,
dims

> CXF-based WebServices support: webservices.xml file is no longer required
> -
>
> Key: GERONIMO-2783
> URL: https://issues.apache.org/jira/browse/GERONIMO-2783
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: webservices
>Affects Versions: 2.0-beta1
>Reporter: Jarek Gawor
> Attachments: GERONIMO-2783.patch
>
>
> The attached patch allows for JAX-WS web services (CXF-based) to be deployed 
> without webservices.xml file. The patch also contains a minor update to the 
> handlers.xml file in jaxws-tests.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (SM-827) Invalid element in top pom

[Guillaume Nodet (JIRA)]

 [ 
https://issues.apache.org/activemq/browse/SM-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet resolved SM-827.


   Resolution: Fixed
Fix Version/s: 3.1
 Assignee: Guillaume Nodet

Author: gnodet
Date: Mon Jan 29 00:39:43 2007
New Revision: 500968

URL: http://svn.apache.org/viewvc?view=rev&rev=500968
Log:
SM-282: Invalid element in top pom
Patch provided by Anders Hammar, thx !

Modified:
   incubator/servicemix/trunk/pom.xml


> Invalid element in top pom
> --
>
> Key: SM-827
> URL: https://issues.apache.org/activemq/browse/SM-827
> Project: ServiceMix
>  Issue Type: Improvement
>  Components: servicemix-assembly
>Affects Versions: 3.1
> Environment: n/a
>Reporter: Anders Hammar
> Assigned To: Guillaume Nodet
>Priority: Minor
> Fix For: 3.1
>
>
> Validating against the Maven v4.0.0 xml schema 
> (http://maven.apache.org/maven-v4_0_0.xsd) I found some invalid elements in 
> the top pom.xml. However, this doesn't break Maven build.
> The invalid elements are marked in red below:
> 
> ServiceMix Developer List
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> servicemix-dev@geronimo.apache.org
> 
> http://www.nabble.com/ServiceMix---Dev-f12051.html
> 
> 
> <{color:red}archive{color}>http://dir.gmane.org/gmane.comp.java.servicemix.devel
> 
> <{color:red}archive{color}>http://mail-archives.apache.org/mod_mbox/geronimo-servicemix-dev/
> 
> 
> 
> ServiceMix User List
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> servicemix-users@geronimo.apache.org
> 
> http://www.nabble.com/ServiceMix---User-f12050.html
> 
> 
> <{color:red}archive{color}>http://dir.gmane.org/gmane.comp.java.servicemix.user
> 
> <{color:red}archive{color}>http://mail-archives.apache.org/mod_mbox/geronimo-servicemix-users/
> 
> 
> It should be:
> 
> blabla
> 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQCPP-58) Possible memory leak when reestablishing connection

[Albert Strasheim (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQCPP-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38034
 ] 

Albert Strasheim commented on AMQCPP-58:


Using the latest program you posted in AMQCPP-59 I'm still seeing many leaks if 
I keep the program running as I start and stop the broker repeatedly. Have you 
tried Valgrind? It's really useful. I run it like this:

{noformat}
valgrind \
--tool=memcheck \
--leak-check=yes \
--error-limit=no \
--num-callers=20 \
--freelist-vol=536870912 \
-v \
someprogram
{noformat}

> Possible memory leak when reestablishing connection
> ---
>
> Key: AMQCPP-58
> URL: https://issues.apache.org/activemq/browse/AMQCPP-58
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Albert Strasheim
> Assigned To: Nathan Mittler
> Fix For: 2.0
>
> Attachments: leaker.cpp, purify-example.txt, socketleak1.diff
>
>
> Brought over from AMQCPP-46.
> There seems to be a memory leak when running the example program from 
> AMQCPP-46 which reconnects whenever the broker goes down.
> Valgrind says:
> {noformat}
> ==15493== 149,520 (89,712 direct, 59,808 indirect) bytes in 1,869 blocks are 
> definitely lost in loss record 55 of 55
> ==15493==at 0x4A19DE3: operator new(unsigned long) 
> (vg_replace_malloc.c:168)
> ==15493==by 0x45DEDD: 
> activemq::network::SocketFactory::createSocket(activemq::util::Properties 
> const&) (SocketFactory.cpp:96)
> ==15493==by 0x458D0C: 
> activemq::transport::TcpTransport::TcpTransport(activemq::util::Properties 
> const&, activemq::transport::Transport*, bool) (TcpTransport.cpp:42)
> ==15493==by 0x42B3EE: 
> activemq::transport::TcpTransportFactory::createTransport(activemq::util::Properties
>  const&) (TcpTransportFactory.cpp:55)
> ==15493==by 0x404CC0: 
> activemq::core::ActiveMQConnectionFactory::createConnection(std::string 
> const&, std::string const&, std::string const&) 
> (ActiveMQConnectionFactory.cpp:130)
> ==15493==by 0x4042D5: 
> activemq::core::ActiveMQConnectionFactory::createConnection() 
> (ActiveMQConnectionFactory.cpp:69)
> ==15493==by 0x403D67: main (main.cpp:30)
> {noformat}
> Purify also seems to indicate that there is a link, along with with possibly 
> spurious leaks or leaks that might be related to the leak reported by 
> Valgrind.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Long file path problem in WinXP

[Davanum Srinivas]

Anita,
Checked in a fix for the long file path problem. Could you please
check if this work for you as well? when you get a chance.
http://svn.apache.org/viewvc?view=rev&revision=500995

Jason,
I know what you think about Windows. But this problem was caused by a
bug in the JDK implementation :)
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6374379

thanks,
dims

--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

Re: JSR-88 1.2 Proposed Design for Geronimo Annotation Processing

[Tim McConnell]

Hi Jarek, yes, the intent is for the module builders to get updated 
deployment plan so that Tomcat, Jetty, etc will do the resource lookups 
with JNDI just like they do currently. There has been some discussions on 
the devlist (started by Sachin) as to whether we want or should accommodate 
annotations for Geronimo-specific deployment descriptors. I'm not exactly 
sure where it was left off, but I think the agreement was to only 
accommodate the JEE5 annotations (e..g, resource-ref in your example below) 
at least in the 2.0 timeframe. Thanks.


Jarek Gawor wrote:

Tim,

A couple of questions on the design/implementation:

1) Since the module builders will get an updated deployment
descriptors, in general, the annotation processors in Tomcat, Jetty,
Web services, EJB, etc. will just need to lookup the resources in
JNDI, right?

2) One thing I'm unclear of is how we are going to deal with the
geronimo-*.xml deployment descriptors? For example, if a service wants
to access the system data source it needs to provide the following
information (in geronimo-web.xml file):


   
  
   
   org.apache.geronimo.configs
   system-database
   
   
  
   
   jdbc/MyDataSource
   SystemDatasource
   


I think the annotation.mappedName can be used for the resource-ref
info but what about the dependency? Will user still need to provide
that or Geronimo will attempt to figure it out somehow?

Thanks,
Jarek

On 1/17/07, Tim McConnell <[EMAIL PROTECTED]> wrote:
Hi, I still think there needs to be a general consensus for the 
handling of annotations in Geronimo.

So, to better explain this design proposal I've
created a few simple UML diagrams that demonstrates how it might work 
with one of the Geronimo

builders--i.e. Tomcat.

Here's the link to the URL diagrams: 
http://cwiki.apache.org/GMOxDEV/jsr-88-12.html


-- The first is just a diagram of the pertinent high-level use cases 
for JSR-88 1.2


-- The second is an interaction diagram of deployment at a very 
high-level as it currently works for

Tomcat

-- The third is the proposed interaction diagram of how deployment 
will generally flow with

annotations. Namely:
 -- Geronimo will find/discover all the annotations in the 
artifact being deployed prior to

the createModule invocation on the TomcatBuilder
 -- Geronimo will then update the deployment descriptor tags 
in the XML accordingly and then

set the Metadata-Complete tag
 -- Finally, during installation of module, Geronimo will 
invoke Tomcat's
AnnotationProcessor implementation and pass it the array of 
annotations that have been discovered,
and Tomcat's AnnotationProcessor will handle handle those runtime-type 
annotations (e.g.,
PreDestory, PostConstruct, etc...) without corresponding deployment 
descriptor tags. Note also that

Tomcat's AnnotationProcessor handles the resource injection as well.

-- The fourth is just a class diagram (not yet complete) that shows 
the new Geronimo annotation classes



Questions:
-- Is this a pattern that can be consistently used for other builders 
as well like Jetty, Axis,

OpenEJB, Web Services, etc ??
-- Is it reasonable to assume that these other components will have 
their own AnnotationProcessor
implementation (like Tomcat) that can be invoked by Geronimo during 
deployment ??


--
Thanks,
Tim McConnell





--
Thanks,
Tim McConnell

[jira] Commented: (AMQCPP-60) message information is lost from stomp message to jms

[Nathan Mittler (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQCPP-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38039
 ] 

Nathan Mittler commented on AMQCPP-60:
--

Many bugs have been fixed since 1.0 - I would recommend trying the latest trunk 
(or even the 1.1 tag).

> message information is lost from stomp message to jms
> -
>
> Key: AMQCPP-60
> URL: https://issues.apache.org/activemq/browse/AMQCPP-60
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
>  Components: Stomp
>Affects Versions: 1.1
> Environment: Using Windows XP SP2, JDK 1.6.0, Bea Weblogic Server 8.1 
> SP6, ActiveMQ-CPP 1.0, ActiveMQ 4.1 patched with Fix for AMQ-1110
>Reporter: Kay Stanke
> Assigned To: Nathan Mittler
>Priority: Critical
> Fix For: 2.0
>
>
> As my producer is a cpp server program i downloaded and compiled activemq-cpp 
> 1.0. I managed to make activemq-cpp compile and link as shared lib / dll 
> under vc 7.1 (Visual Studio .NET 2003). My consumer is located on a bea wls 
> 8.1 I use the jms to jms bridge to forward the messages. For other reasons 
> (see AMQ-1141) the forward fails. I can see in the dumped message:
> message: ActiveMQTextMessage {commandId = 3, responseRequired = false, 
> messageId = ID:KStanke-2844-1170064566619-5:0:-1:1:1, 
> originalDestination = null, 
> originalTransactionId = null, 
> producerId = ID:KStanke-2844-1170064566619-5:0:-1:1, 
> destination = queue://TEST.FOO, 
> transactionId = null, expiration = 0, 
> timestamp = 1170064774288, 
> arrival = 0, 
> correlationId = null, 
> replyTo = null, 
> persistent = false, 
> type = null, 
> priority = 4, 
> groupID = null, 
> groupSequence = 0, targetConsumerId = null, compressed = false, 
> userID = null, content = [EMAIL PROTECTED], 
> marshalledProperties = [EMAIL PROTECTED], dataStructure = null, 
> redeliveryCounter = 0, size = 0, properties = {request-id=2}, 
> readOnlyProperties = true, 
> readOnlyBody = true, droppable = false, text = null}
> i'm missing the persistence as i used pProducer->setDeliveryMode( 
> DeliveryMode::PERSISTANT ); As my message is a text message i'm missing the 
> message text as well. I created the message with: pMessage = 
> pSession->createTextMessage(messageText); with an nonempty string. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (AMQCPP-60) message information is lost from stomp message to jms

[Nathan Mittler (JIRA)]

 [ 
https://issues.apache.org/activemq/browse/AMQCPP-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nathan Mittler updated AMQCPP-60:
-

Affects Version/s: (was: 1.0)
   2.0

> message information is lost from stomp message to jms
> -
>
> Key: AMQCPP-60
> URL: https://issues.apache.org/activemq/browse/AMQCPP-60
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
>  Components: Stomp
>Affects Versions: 1.1
> Environment: Using Windows XP SP2, JDK 1.6.0, Bea Weblogic Server 8.1 
> SP6, ActiveMQ-CPP 1.0, ActiveMQ 4.1 patched with Fix for AMQ-1110
>Reporter: Kay Stanke
> Assigned To: Nathan Mittler
>Priority: Critical
> Fix For: 2.0
>
>
> As my producer is a cpp server program i downloaded and compiled activemq-cpp 
> 1.0. I managed to make activemq-cpp compile and link as shared lib / dll 
> under vc 7.1 (Visual Studio .NET 2003). My consumer is located on a bea wls 
> 8.1 I use the jms to jms bridge to forward the messages. For other reasons 
> (see AMQ-1141) the forward fails. I can see in the dumped message:
> message: ActiveMQTextMessage {commandId = 3, responseRequired = false, 
> messageId = ID:KStanke-2844-1170064566619-5:0:-1:1:1, 
> originalDestination = null, 
> originalTransactionId = null, 
> producerId = ID:KStanke-2844-1170064566619-5:0:-1:1, 
> destination = queue://TEST.FOO, 
> transactionId = null, expiration = 0, 
> timestamp = 1170064774288, 
> arrival = 0, 
> correlationId = null, 
> replyTo = null, 
> persistent = false, 
> type = null, 
> priority = 4, 
> groupID = null, 
> groupSequence = 0, targetConsumerId = null, compressed = false, 
> userID = null, content = [EMAIL PROTECTED], 
> marshalledProperties = [EMAIL PROTECTED], dataStructure = null, 
> redeliveryCounter = 0, size = 0, properties = {request-id=2}, 
> readOnlyProperties = true, 
> readOnlyBody = true, droppable = false, text = null}
> i'm missing the persistence as i used pProducer->setDeliveryMode( 
> DeliveryMode::PERSISTANT ); As my message is a text message i'm missing the 
> message text as well. I created the message with: pMessage = 
> pSession->createTextMessage(messageText); with an nonempty string. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (AMQCPP-60) message information is lost from stomp message to jms

[Nathan Mittler (JIRA)]

 [ 
https://issues.apache.org/activemq/browse/AMQCPP-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nathan Mittler updated AMQCPP-60:
-

Affects Version/s: (was: 2.0)
   1.1
Fix Version/s: 2.0

> message information is lost from stomp message to jms
> -
>
> Key: AMQCPP-60
> URL: https://issues.apache.org/activemq/browse/AMQCPP-60
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
>  Components: Stomp
>Affects Versions: 1.1
> Environment: Using Windows XP SP2, JDK 1.6.0, Bea Weblogic Server 8.1 
> SP6, ActiveMQ-CPP 1.0, ActiveMQ 4.1 patched with Fix for AMQ-1110
>Reporter: Kay Stanke
> Assigned To: Nathan Mittler
>Priority: Critical
> Fix For: 2.0
>
>
> As my producer is a cpp server program i downloaded and compiled activemq-cpp 
> 1.0. I managed to make activemq-cpp compile and link as shared lib / dll 
> under vc 7.1 (Visual Studio .NET 2003). My consumer is located on a bea wls 
> 8.1 I use the jms to jms bridge to forward the messages. For other reasons 
> (see AMQ-1141) the forward fails. I can see in the dumped message:
> message: ActiveMQTextMessage {commandId = 3, responseRequired = false, 
> messageId = ID:KStanke-2844-1170064566619-5:0:-1:1:1, 
> originalDestination = null, 
> originalTransactionId = null, 
> producerId = ID:KStanke-2844-1170064566619-5:0:-1:1, 
> destination = queue://TEST.FOO, 
> transactionId = null, expiration = 0, 
> timestamp = 1170064774288, 
> arrival = 0, 
> correlationId = null, 
> replyTo = null, 
> persistent = false, 
> type = null, 
> priority = 4, 
> groupID = null, 
> groupSequence = 0, targetConsumerId = null, compressed = false, 
> userID = null, content = [EMAIL PROTECTED], 
> marshalledProperties = [EMAIL PROTECTED], dataStructure = null, 
> redeliveryCounter = 0, size = 0, properties = {request-id=2}, 
> readOnlyProperties = true, 
> readOnlyBody = true, droppable = false, text = null}
> i'm missing the persistence as i used pProducer->setDeliveryMode( 
> DeliveryMode::PERSISTANT ); As my message is a text message i'm missing the 
> message text as well. I created the message with: pMessage = 
> pSession->createTextMessage(messageText); with an nonempty string. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (AMQCPP-59) Exception is thrown when destroying consumer after connection failure

[Nathan Mittler (JIRA)]

 [ 
https://issues.apache.org/activemq/browse/AMQCPP-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nathan Mittler closed AMQCPP-59.


Resolution: Fixed

Since it sounds like it's working now, I'm closing this issue.

> Exception is thrown when destroying consumer after connection failure
> -
>
> Key: AMQCPP-59
> URL: https://issues.apache.org/activemq/browse/AMQCPP-59
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Albert Strasheim
> Assigned To: Nathan Mittler
> Fix For: 2.0
>
>
> Brought over from AMQCPP-46.
> In a program that reconnects when it detects a connection failure using an 
> exception listener, there seem to be two different places where exceptions 
> can originate.
> In most cases when I shut down the broker and the exception listener fires 
> properly and I can clean up everything (without deletes throwing exceptions), 
> the stack trace that gets printed on the console looks like this:
> {noformat}
> WARNING: activemq::io::SocketInputStream::read - The connection is broken
> FILE: ..\src\main\activemq\network\SocketInputStream.cpp, LINE: 137
> FILE: ..\src\main\activemq\io\BufferedInputStream.cpp, LINE: 199
> FILE: ..\src\main\activemq\io\BufferedInputStream.cpp, LINE: 83
> FILE: ..\src\main\activemq\connector\stomp\StompCommandReader.cpp, 
> LINE: 216
> FILE: ..\src\main\activemq\connector\stomp\StompCommandReader.cpp, 
> LINE: 120
> FILE: ..\src\main\activemq\connector\stomp\StompCommandReader.cpp, 
> LINE: 71
> FILE: ..\src\main\activemq\transport\IOTransport.cpp, LINE: 175
> {noformat}
> The message is printed twice with different tids, from the two threads that 
> are active.
> Sometimes when I shut down the broker and the exception handler fires and I 
> clean up everything but then the consumer's destructor throws an exception. 
> In that case, the stack trace that is printed looks like this:
> {noformat}
> WARNING: activemq::io::SocketInputStream::read - An existing connection was 
> forcibly closed by the remote host.
> FILE: ..\src\main\activemq\network\SocketInputStream.cpp, LINE: 145
> FILE: ..\src\main\activemq\io\BufferedInputStream.cpp, LINE: 199
> FILE: ..\src\main\activemq\io\BufferedInputStream.cpp, LINE: 83
> FILE: ..\src\main\activemq\connector\stomp\StompCommandReader.cpp, 
> LINE: 216
> FILE: ..\src\main\activemq\connector\stomp\StompCommandReader.cpp, 
> LINE: 120
> FILE: ..\src\main\activemq\connector\stomp\StompCommandReader.cpp, 
> LINE: 71
> FILE: ..\src\main\activemq\transport\IOTransport.cpp, LINE: 175
> {noformat}
> Again I see this message from both threads. Note the slightly different line 
> numbers in SocketInputStream.cpp and the slighty different error message 
> (this is on Windows XP SP2). In this case the failure of the socket is 
> probably being detected in a slightly different place.
> If the socket failure happens in the second way, it seems that destructors of 
> consumers (and possibly producers and sessions) don't properly catch the 
> exception when being destroying, causing their destructors to throw an 
> exception, which isn't what we want.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Why is GERONIMO_HOME not passed into the server?

[Sachin Patel]

I forget which properties do what, but I think it is needed for  
multiple instance support.


On Jan 26, 2007, at 9:40 AM, Ted Kirby wrote:


Providing the org.apache.geronimo.home.dir system property to allow
the home directory to be passed in is good, but if this is not used
(and I'd don't feel it should be required/used in the normal case),
DirectoryUtils.getGeronimoInstallDirectory() is used to determine the
home directory.  This method uses machinations that do not resolve
correctly if the home directory is a symbolic link.  Since the
invoking geronimo script sets and uses GERONIMO_HOME, why does it not
pass this value into the server?  I would think that BasicServerInfo
would want to set baseDirectory to GERONIMO_HOME (if the
org.apache.geronimo.home.dir system property is not set), and invoke
DirectoryUtils.getGeronimoInstallDirectory() only if GERONIMO_HOME is
not set.



-sachin

Security and authorization requirements on RequestBroker

[Rossmanith, Philipp]

Dear all,

Apologies for the long mail, but there seemed to be no reasonable way of
splitting this up.

I'm working in a project where we will use ServiceMix (base: v3.0) as a
router connecting several Web services (SOAP1.1 with attachments) and
for providing commonly needed services, such as user and group
management, authentication, authorization, XML-based data persistence,
and others.

In this project we will develop a number of extensions to/components,
which - if there is interest - we might donate to the SM project, as
well.

Last week I was investigating SM security (for results: see
http://goopen.org/confluence/pages/createpage.action?spaceKey=SM&title=S
ecurity&linkCreation=true&fromPageId=13484 in the confluence; hasn't
been activated yet)

My findings suggest the following:
- Authorization has to be done at the first endpoint where the
normalized message (NM) appears
- The SecuredBroker performs allows access based on the belonging of the
normalized message's subject's roles. The permissions of the roles are
given via the AuthorizationMap. The SecuredBroker DOES NOT check which
service provided the original message.

In our project, we have a setup where one and the same user may have
different permissions depending on which service he's utilizing. Given
that my findings are correct and that SM doesn't yet provide this
function, I'd like to extend the authorization to include the
originating service. (cp. JAAS authorization where a policy defines
permissions based on codebase and Principal)

Requirements:
- *Authentication of calling service*: the consumer service starting a
flow of messages (i.e. the one where the NM appears in the ESB) needs to
be authenticated.
- *Authentication of calling user*, the user using the calling service.
Implementation: e.g. user tags in WS-Security.
*Every service invocation needs to both authenticate user and service.*
- *Client side permission specification* Client services need to be able
to change permissions via service invocation. Hence, expanding the
AuthorizationMap mechanism doesn't seem feasible.

Ideas for implementation/realization:
- *In general*: A new Broker as subclass of DefaultBroker/SecuredBroker
authorizing based on calling service

- *Authentication of calling service*:
  - For servicemix-http/external consumers: signing SOAP messages.
  - "ESB-internal" endpoints which are assumed to be trusted: lookup in
the Broker's component registry.
  - Assuming that the NM's Subject refers to user information, the
security information about the calling service (e.g. Subject) may be
attached via NM's setProperty(...) method.

- *Client side permission specification*:
  - Via group and user administration, or via a service engine
replacing/complementing the AuthorizationMap (AuthorizationEntrys as
SUs)

Questions:
1. Are my assumptions about Security issues correct? (See page: "User's
guide -> Security" in the confluence)
2. What do you think about this component? Is the outlined functionality
already available in the current implementation?
3. Comments on/Ideas for implementation/realization?
4. My account in confluence seems to be disabled. When I log in, the
system recognizes me but tells me: "You are not permitted to perform
this operation." Any ideas?

Thanks in advance,
Ciao,
Philipp Rossmanith

This e-mail may contain confidential or privileged information. Any unauthorised
copying, use or distribution of this information is strictly prohibited.

Re: [VOTE] 2.0-M2 Milestone ready for review and JACC Specs

[Sachin Patel]

My +1

On Jan 27, 2007, at 1:01 AM, Matt Hogstrom wrote:


All,

I have made the binaries from Geronimo 2.0-M2 available for review at:

http://people.apache.org/~hogstrom/2.0-M2-rc1

In this directory you will find the various assemblies for your  
review as well as one massive tar ball that has the various  
artifacts that will ultimately be distributed.


The files are being uploaded as this is being written so give them  
some time.


Also included in this vote are the artifacts for the JACC spec 1.0- 
M2 which is required for 2.0-M2.


Remember...this is a milestone and not a full release.

Thanks for David Blevins for being quite the helper tonight in  
getting the Release Notes in line and helping out with Open EJB.


Thanks

This vote will conclude on Tuesday at 0100 Eastern.

Cheers.

Matt



-sachin

Re: Why is GERONIMO_HOME not passed into the server?

[Gianny Damour]

On 29/01/2007, at 3:56 AM, David Jencks wrote:



On Jan 28, 2007, at 3:48 AM, Gianny Damour wrote:


On 28/01/2007, at 7:26 PM, David Jencks wrote:




I don't see any value in having a hierarchy here: I think that  
each item should be present in exactly one place.  For instance  
if you have identical artifacts in 2 repos I'd regard that as an  
error, although since they are identical it wouldn't matter which  
one you picked.   Could you provide an example of something your  
proposed search strategy would be useful for?


i think that this may be useful in some very specific scenario.  
For instance, a developer may want to upgrade some dependencies  
used by a module his team is working on in a sandbox. If he simply  
drops a newer version in the shared repository, then all the  
developers will see the newer version upon server restart. This  
can be avoided by updating the artifact_aliases property file of  
each developer; however, this is less transparent than a solution  
based on an hierarchical dependency resolution mechanism.




I don't think I understand what you have in mind yet.  I would  
expect that in a setup with multiple servers the stuff that's  
specific to a particular server would be in the server-specific  
repo we've been talking about.  So if you want to upgrade a  
dependency to a newer version you'd put the newer version in your  
server-specific repo where your apps would find it but no one  
else's apps would.  The only scenario I can think of so far where  
this wouldn't work is if it's a snapshot dependency so the old and  
new files have exactly the same file name.  I really think we  
should NOT support anything that tries to distinguish between 2  
files with the same artifact Id.  If people want to have different  
versions of a snapshot artifact in the server they should all be in  
server-specific repos.


I was trying to consider the case where a non server-specific  
dependency is to be upgraded. I was wrongly believing that artifact  
version resolution was returning the highest version available of the  
first Repository storing the to be resolved Artifact. Following your  
comment, I checked the artifact resolution approach implemented by  
DefaultArtifactResolver and I now understand why hierarchical  
dependency resolution is useless. Thanks for taking the time to  
explain it.


Gianny


thanks
david jencks

3.1 release

[Guillaume Nodet]

I have create a branch and a tag for 3.1 release.
The trunk has moved to 3.2-SNAPSHOT.
I will upload the binaries asap and will start
a vote once done.

--
Cheers,
Guillaume Nodet

Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/

Re: [VOTE] 2.0-M2 Milestone ready for review and JACC Specs

[anita kulshreshtha]

+1 

   Please note the following issues for future releases:
1. Clicking on LDAP Viewer produces stack trace: 
08:49:59,484 WARN  [ExecuteQuery] Method execution failed: 
java.lang.Exception: Problem connecting to directory server:
localhost:1389
at
org.apache.geronimo.console.ldapmanager.LDAPManagerHelper.(LDAPManagerHelper.java:113)

2. ClassLoader Viewer throws error:
08:51:13,203 ERROR [RowFragment_jsp]] Servlet.service() for servlet
jsp.WEB_002dINF.aggregation.RowFragment_jsp threw exception
javax.servlet.ServletException: Java heap space

3. The Create and Install Plugins page lists all entries as 'not
available', e.g.
 * 
 * Geronimo Admin Console (Tomcat) (Not available; View Details)
 * .
  It should probably read as 'View Availability'.

Thanks
Anita

--- Matt Hogstrom <[EMAIL PROTECTED]> wrote:

> All,
> 
> I have made the binaries from Geronimo 2.0-M2 available for review
> at:
> 
> http://people.apache.org/~hogstrom/2.0-M2-rc1
> 
> In this directory you will find the various assemblies for your  
> review as well as one massive tar ball that has the various artifacts
>  
> that will ultimately be distributed.
> 
> The files are being uploaded as this is being written so give them  
> some time.
> 
> Also included in this vote are the artifacts for the JACC spec 1.0-M2
>  
> which is required for 2.0-M2.
> 
> Remember...this is a milestone and not a full release.
> 
> Thanks for David Blevins for being quite the helper tonight in  
> getting the Release Notes in line and helping out with Open EJB.
> 
> Thanks
> 
> This vote will conclude on Tuesday at 0100 Eastern.
> 
> Cheers.
> 
> Matt
> 



 

Be a PS3 game guru.
Get your game face on with the latest PS3 news and previews at Yahoo! Games.
http://videogames.yahoo.com/platform?platform=120121

[jira] Closed: (GERONIMO-2760) Upgrade tomcat to version 6.0.8a

[Paul McMahan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paul McMahan closed GERONIMO-2760.
--

Resolution: Fixed

> Upgrade tomcat to version 6.0.8a
> 
>
> Key: GERONIMO-2760
> URL: https://issues.apache.org/jira/browse/GERONIMO-2760
> Project: Geronimo
>  Issue Type: Task
>  Security Level: public(Regular issues) 
>  Components: Tomcat
>Affects Versions: 2.0-M2
>Reporter: Paul McMahan
> Assigned To: Paul McMahan
> Fix For: 2.0-M2
>
>
> Upgrade to tomcat 6.0.8a.  Also discontinue usage of snapshot version by 
> enabling tomcat's new m2 repo at 
> http://tomcat.apache.org/dev/dist/m2-repository/

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Release Notes for 2.0-M2 - Limitations and Issues Fixed sections

[Dave Colasurdo]

Agreed..  Seems like the list still has some stale entries and should be 
refreshed..


Here is a link to the current refreshed list.

http://cwiki.apache.org/confluence/display/GMOxSBOX/Test13


BTW, the query being used here is the one that Hernan created for 2.0-M2 
and is contained in the source of this wiki page.



Thanks
-Dave-

Vamsavardhana Reddy wrote:
I am noticing that "Known Issues and Limitations" section still lists 
some (atleast one, G-2745) JIRAs that have been addressed.  "Known 
Issues and Limitations" and "Specific Issues, Features and Improvements 
fixed in Version 2.0-M2" sections need review.


Vamsi

[jira] Created: (GERONIMO-2784) Samples cleanup

[Paul McMahan (JIRA)]

Samples cleanup
---

 Key: GERONIMO-2784
 URL: https://issues.apache.org/jira/browse/GERONIMO-2784
 Project: Geronimo
  Issue Type: Task
  Security Level: public (Regular issues)
  Components: sample apps
Affects Versions: 2.0-beta1
Reporter: Paul McMahan
Priority: Minor


As discussed on dev: 
  http://mail-archives.apache.org/mod_mbox/geronimo-dev/200701.mbox/[EMAIL 
PROTECTED]

# Move the following modules from server/trunk/applications to samples/trunk
** demo (security demo)
** geronimo-examples
** geronimo-ldap-demo
** magicGball
# Move anything worth keeping from server/trunk/applications/daytrader to 
daytrader/trunk
# Remove the configs for these modules from server/trunk/configs
# Enable samples/trunk to build CARs so that the samples can be installed as 
plugins
# Publish the CARs built in samples/trunk to a maven repo
# Update the plugin catalog at site/trunk/plugins/ to reference the samples in 
maven repo

-- 
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

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38053
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 16:16:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:16:13 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291516Z2SAVPG8
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38054
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 16:18:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:18:14 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291518CXXNBSJN
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38055
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 16:20:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:20:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291520Z2SAVPL7
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38056
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 16:22:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:22:22 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291522Z2SAVP3P
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38057
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 16:24:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:24:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291524CXXNBSS2
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38058
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 16:26:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:26:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291526Z2SAVP4W
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38059
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 16:28:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:28:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291528CXXNBSXN
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38060
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 16:30:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:30:43 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291530Z2SAVP5A
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38061
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 16:32:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:32:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291532Z2SAVP7V
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38062
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 16:34:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:34:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291534CXXNBS9Z
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38063
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 16:36:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:36:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291536Z2SAVQB9
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38064
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 16:38:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:38:04 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291538Z2SAVQ1W
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38065
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 16:40:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:40:11 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291540CXXNBTHA
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Where should we put Samples and Plug-ins?

[Paul McMahan]

My preference for option #2 really had more to do with where the
optional modules (like directory, clustering, etc) should go than
where the samples should go.  I think we're in agreement that the
samples should go into samples/trunk.  I created GERONIMO-2784 to
outline what I think are the right steps to make that happen.  Please
review that JIRA and provide feedback if necessary.

Best wishes,
Paul

On 1/26/07, Prasad Kashyap <[EMAIL PROTECTED]> wrote:

This is how I see it. The apps in geronimo/server/trunk/applications
should be the ones that are absolutely required by the server. Eg:
console, welcome app etc.

The optional apps like servlet-examples, jsp-examples should be moved
elsewhere to a samples directory or project. There is no need to build
these samples every time we build the server. This will greatly reduce
our build time.

Next, I don't know why we make "car" out some of these example apps.
If we need to include a few of them in the assembly, we should just
"deploy" them.

Lastly, there is the Q about where the optional samples end up:

1. geronimo/server/trunk/samples
Pros:
  a) samples version closely tied with the server.

   Cons:
 a) increases the time it takes to download the server tree
unnecessarily. (svn checkout)
 b) have to use a separate profile to build them. More pom.xml
maintenance. This is assuming the fact that we don't build "car" for
these. If we have to build "car" too, then the story becomes more
complex.

2. geronimo/samples/trunk
 Pros:
 a) separate tree built and published separately.
 b) the server tree now builds faster.
 c) if assemblies need to include it, just add the artifact as a dependency.

 Cons:
 a) have to keep the version of this project in synch with the
version of the server. (Not really a big deal, similar to what we
could with specs). This means keeping the plans and DD updated with
every server release.

With every server release, we have broken the samples on the wiki
page. The plans and DD have changed  and we have not kept that
updated.

Cheers
Prasad




On 1/25/07, Donald Woods <[EMAIL PROTECTED]> wrote:
> Any thoughts on what we do with the new Samples being added to
> /geronimo/samples/trunk and the /geronimo/plugins/trunk files?
>
> We currently have 5 places for samples and plugins (the above 2
> locations plus server/applications, server/configs and
> geronimo/daytrader) and I would like to spend some time getting all of
> this "optional" code (except for maybe Daytrader) into the same location
> in svn before we release 2.0.
>
>
> -Donald
>
> Paul McMahan wrote:
> > Thanks Donald for migrating this discussion onto [EMAIL PROTECTED]  I 
posted some
> > feedback about option #1 in the JIRA you referenced.  To sum up, I was
> > concerned about moving optional modules to an area called "plugins",
> > since IMO that's a misnomer since optional modules aren't always
> > plugins and plugins aren't always optional :-)   I am also concerned
> > about complicating release management for optional modules that are
> > sensitive to the Geronimo server version.
> >
> > I think we can solve the problem described in G2728 without
> > reorganizing the source tree, for example by adjusting the server
> > dependencies.  But if there is also some motivation to further trim
> > down what's in server/trunk (to speed up the build, perhaps) then I
> > like option #2 better.
> >
> > Best wishes,
> > Paul
> >
> > On 1/24/07, Donald Woods <[EMAIL PROTECTED]> wrote:
> >> As part of the discussion on G2728 relating to the Directory server and
> >> LDAP-Demo sample -
> >> https://issues.apache.org/jira/browse/GERONIMO-2728
> >> I'm wondering how others would like to see us handle optional server
> >> components for 2.0, as we currently have some samples and plug-ins in
> >> geronimo/server/trunk/, but others are under geronimo/samples/trunk and
> >> geronimo/plugins/trunk.
> >>
> >> Should we:
> >> 1) Move them out of geronimo/server/trunk and
> >> - move all sample apps (like Magicgball, ldap-demo, ...) to the
> >> existing geronimo/samples/trunk and have them automatically built and
> >> published by gbuild
> >> - move all optional and non-Geronimo plugins (like ApacheDS) to the
> >> existing geronimo/plugins/trunk and have then built and published by
> >> gbuild
> >>
> >> 2) Keep all the samples and plug-ins in the server tree, but under a new
> >> directory like server/trunk/samples or server/trunk/opt and use a maven
> >> profile so they are not always built, but always build and publish them
> >> from gbuild
> >>
> >> I could also see us moving the minimal assemblies to the same location
> >> as #2, for those people interested in them
> >>
> >> Thoughts?
> >>
> >>
> >> -Donald
> >>
> >>
> >>
> >
> >
>
>
>

[jira] Created: (SM-828) OutBinding doesn't allow for DeliveryChannel.accept()

[James Lorenzen (JIRA)]

OutBinding doesn't allow for DeliveryChannel.accept()
-

 Key: SM-828
 URL: https://issues.apache.org/activemq/browse/SM-828
 Project: ServiceMix
  Issue Type: Bug
  Components: servicemix-core
Affects Versions: 3.0
 Environment: Windows XP
ServiceMix 3.0
JDK 1.5
Reporter: James Lorenzen
Priority: Blocker
 Attachments: OutBinding.java

The incorrect use of AtomicBoolean in OutBinding prevents components from ever 
receiving a new MessageExchange through the DeliveryChannel accept() method.
The variable stop gets initialized with false. The start method sets it to 
true. The run method checks the value and only calls accept if this statement 
is true:
while(!stop.get()).

Since the value of stop is true, the component never calls 
DeliveryChannel.accept().

This bug has been found because we attempted to deploy our component, who 
extends OutBinding, in OpenESB/Glassfish. Our component was never receiving the 
message and this is how we discovered the bug.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: @EJB injection for Jetty

[Jarek Gawor]

Not sure what happened but it is also working for me know (using latest trunk).

Jarek

On 1/27/07, Prasad Kashyap <[EMAIL PROTECTED]> wrote:

OK. Now I have verified the @EJB injection jack for Jetty on TRUNK and
have found it to be working.

Cheers
Prasad

On 1/27/07, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
> No I haven't verified the @EJB injection on Jetty. I believe it is
> only on trunk. I was working on getting my M2 build to work. (unable
> to resolve dependency o.a.g.specs.geronimo-ejb_3.0_specs//jar)
>
> When I finally gave on M2 build and work on  trunk, I hit the
> following problem -
>
> Missing:
> --
> 1) org.apache.openejb:container:pom:3.0-incubating-SNAPSHOT
>   Path to dependency:
> 1) org.apache.geronimo.modules:geronimo-openejb:jar:2.0-SNAPSHOT
> 2) org.apache.openejb:openejb-ejbd:jar:3.0-incubating-SNAPSHOT
> 3) org.apache.openejb:container:pom:3.0-incubating-20070126.211327-22
>
> Cheers
> Prasad
>
>
> On 1/26/07, Dain Sundstrom <[EMAIL PROTECTED]> wrote:
> > What did you run? This worked great for me an Prasad.
> >
> > Anyway, I changed the code to catch Exception instead of just
> > NamingExcetpion.
> >
> > -dain
> >
> > On Jan 26, 2007, at 9:26 AM, Jarek Gawor wrote:
> >
> > > Dain,
> > >
> > > This hack is causing problems:
> > >
> > > java.lang.NullPointerException
> > >at
> > > org.apache.xbean.naming.context.ContextFlyweight.listBindings(Context
> > > Flyweight.java:92)
> > >at
> > > org.apache.xbean.naming.context.ContextFederation.getFederatedBinding
> > > s(ContextFederation.java:72)
> > >at
> > > org.apache.xbean.naming.context.AbstractFederatedContext.getBindings(
> > > AbstractFederatedContext.java:63)
> > >at org.apache.xbean.naming.context.AbstractContext.getBinding
> > > (AbstractCo
> > > ntext.java:86)
> > >at org.apache.xbean.naming.context.AbstractContext.lookup
> > > (AbstractContex
> > > t.java:128)
> > >at org.apache.xbean.naming.context.AbstractContext.lookup
> > > (AbstractContex
> > > t.java:607)
> > >at org.apache.xbean.naming.context.AbstractContext.lookup
> > > (AbstractContex
> > > t.java:151)
> > >at org.apache.xbean.naming.context.AbstractContext.lookup
> > > (AbstractContex
> > > t.java:593)
> > >at javax.naming.InitialContext.lookup(InitialContext.java:351)
> > >at
> > > org.apache.geronimo.jetty6.InjectionServletHandler.processAnnotations
> > > (InjectionServletHandler.java:48)
> > >at
> > > org.apache.geronimo.jetty6.InjectionServletHandler.customizeServlet(I
> > > njectionServletHandler.java:38)
> > >
> > > I think you need setup the component context properly first (see code
> > > in jetty6.handler.ComponentContextHandler) in order to get the JNDI
> > > context.
> > >
> > > Jarek
> > >
> > > On 1/25/07, Dain Sundstrom <[EMAIL PROTECTED]> wrote:
> > >> I added a simple hack to get @EJB injection working in Jetty.  It is
> > >> hack is just a trimmed down version of the Tomcat
> > >> DefaultAnnotationProcess or which only handles @EJB injection.
> > >>
> > >> As with the Tomcat version, this is only in there to demonstrate the
> > >> @EJB annotation use and is by no means a final solution for
> > >> annotation processing.
> > >>
> > >> -dain
> > >>
> >
> >
>

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38066
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 16:42:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:42:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291542CXXNBTJ9
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38067
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 16:44:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:44:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291544Z2SAVQM0
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38068
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 16:46:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:46:11 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291546Z2SAVQQB
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: @EJB injection for Jetty

[Paul McMahan]

I think the NPE you saw was addressed by
http://svn.apache.org/viewvc?view=rev&revision=500424

Best wishes,
Paul

On 1/29/07, Jarek Gawor <[EMAIL PROTECTED]> wrote:

Not sure what happened but it is also working for me know (using latest trunk).

Jarek

On 1/27/07, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
> OK. Now I have verified the @EJB injection jack for Jetty on TRUNK and
> have found it to be working.
>
> Cheers
> Prasad
>
> On 1/27/07, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
> > No I haven't verified the @EJB injection on Jetty. I believe it is
> > only on trunk. I was working on getting my M2 build to work. (unable
> > to resolve dependency o.a.g.specs.geronimo-ejb_3.0_specs//jar)
> >
> > When I finally gave on M2 build and work on  trunk, I hit the
> > following problem -
> >
> > Missing:
> > --
> > 1) org.apache.openejb:container:pom:3.0-incubating-SNAPSHOT
> >   Path to dependency:
> > 1) org.apache.geronimo.modules:geronimo-openejb:jar:2.0-SNAPSHOT
> > 2) org.apache.openejb:openejb-ejbd:jar:3.0-incubating-SNAPSHOT
> > 3) 
org.apache.openejb:container:pom:3.0-incubating-20070126.211327-22
> >
> > Cheers
> > Prasad
> >
> >
> > On 1/26/07, Dain Sundstrom <[EMAIL PROTECTED]> wrote:
> > > What did you run? This worked great for me an Prasad.
> > >
> > > Anyway, I changed the code to catch Exception instead of just
> > > NamingExcetpion.
> > >
> > > -dain
> > >
> > > On Jan 26, 2007, at 9:26 AM, Jarek Gawor wrote:
> > >
> > > > Dain,
> > > >
> > > > This hack is causing problems:
> > > >
> > > > java.lang.NullPointerException
> > > >at
> > > > org.apache.xbean.naming.context.ContextFlyweight.listBindings(Context
> > > > Flyweight.java:92)
> > > >at
> > > > org.apache.xbean.naming.context.ContextFederation.getFederatedBinding
> > > > s(ContextFederation.java:72)
> > > >at
> > > > org.apache.xbean.naming.context.AbstractFederatedContext.getBindings(
> > > > AbstractFederatedContext.java:63)
> > > >at org.apache.xbean.naming.context.AbstractContext.getBinding
> > > > (AbstractCo
> > > > ntext.java:86)
> > > >at org.apache.xbean.naming.context.AbstractContext.lookup
> > > > (AbstractContex
> > > > t.java:128)
> > > >at org.apache.xbean.naming.context.AbstractContext.lookup
> > > > (AbstractContex
> > > > t.java:607)
> > > >at org.apache.xbean.naming.context.AbstractContext.lookup
> > > > (AbstractContex
> > > > t.java:151)
> > > >at org.apache.xbean.naming.context.AbstractContext.lookup
> > > > (AbstractContex
> > > > t.java:593)
> > > >at javax.naming.InitialContext.lookup(InitialContext.java:351)
> > > >at
> > > > org.apache.geronimo.jetty6.InjectionServletHandler.processAnnotations
> > > > (InjectionServletHandler.java:48)
> > > >at
> > > > org.apache.geronimo.jetty6.InjectionServletHandler.customizeServlet(I
> > > > njectionServletHandler.java:38)
> > > >
> > > > I think you need setup the component context properly first (see code
> > > > in jetty6.handler.ComponentContextHandler) in order to get the JNDI
> > > > context.
> > > >
> > > > Jarek
> > > >
> > > > On 1/25/07, Dain Sundstrom <[EMAIL PROTECTED]> wrote:
> > > >> I added a simple hack to get @EJB injection working in Jetty.  It is
> > > >> hack is just a trimmed down version of the Tomcat
> > > >> DefaultAnnotationProcess or which only handles @EJB injection.
> > > >>
> > > >> As with the Tomcat version, this is only in there to demonstrate the
> > > >> @EJB annotation use and is by no means a final solution for
> > > >> annotation processing.
> > > >>
> > > >> -dain
> > > >>
> > >
> > >
> >
>

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38069
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 16:48:04 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:48:15 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291548Z2SAVQS7
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38070
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 16:50:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:50:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291550CXXNBT4P
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38071
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 16:52:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:52:05 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291552Z2SAVQYP
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38072
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 16:54:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:54:09 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291554CXXNBTZW
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38073
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 16:56:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:56:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291556CXXNBT65
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38074
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 16:58:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 16:58:15 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291558CXXNBT88
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38075
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 17:00:18 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:00:24 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291600Z2SAVRCB
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38076
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 17:02:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:02:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291602CXXNB4CX
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Testsuit is downloading jars in offline mode!

[anita kulshreshtha]

   The console testsuit does not respect the offline flag and downloads
maven jars.

Thanks
Anita

C:\anita\geronimo\g2.0\testsuite>mvn -o clean install
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in
your local
repository will be inaccessible.

[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO]   Geronimo TestSuite
[INFO]   Geronimo TestSuite, Console
[INFO]   Geronimo TestSuite :: Deployment Testsuite
[INFO]   Geronimo TestSuite, Enterprise Tier
[INFO]   Geronimo TestSuite :: Web-tier Testsuite
[INFO]   Geronimo TestSuite :: WebServices TestSuite
[INFO]

[INFO] Building Geronimo TestSuite
[INFO]task-segment: [clean, install]
[INFO]

[INFO] snapshot
org.apache.geronimo.plugins:testsuite-maven-plugin:2.0-SNAPSHOT:
checking
for updates from apache-snapshots
[INFO] snapshot
org.apache.geronimo.plugins:testsuite-maven-plugin:2.0-SNAPSHOT:
checking
for updates from codehaus-snapshots
[INFO] snapshot
org.apache.geronimo.plugins:testsuite-maven-plugin:2.0-SNAPSHOT:
checking
for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.plugins:maven-plugins:2.0-SNAPSHOT:
checking for updat
es from jtidy.sourceforge
[INFO] [clean:clean]
[INFO] Deleting directory C:\anita\geronimo\g2.0\testsuite\target
[INFO] Deleting directory
C:\anita\geronimo\g2.0\testsuite\target\classes
[INFO] Deleting directory
C:\anita\geronimo\g2.0\testsuite\target\test-classes
[INFO] [tools:require-java-version {execution: validate-java-version}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] [site:attach-descriptor]
[INFO] [install:install]
[INFO] Installing C:\anita\geronimo\g2.0\testsuite\pom.xml to
C:\Documents and Settings\An
ita\.m2\repository\org\apache\geronimo\testsuite\testsuite\2.0-SNAPSHOT\testsuite-2.0-SNAP
SHOT.pom
[INFO]

[INFO] Building Geronimo TestSuite, Console
[INFO]task-segment: [clean, install]
[INFO]

[INFO] artifact org.apache.geronimo.plugins:selenium-maven-plugin:
checking for updates fr
om codehaus
[INFO] artifact org.apache.geronimo.plugins:selenium-maven-plugin:
checking for updates fr
om central
[INFO] snapshot
org.apache.geronimo.plugins:selenium-maven-plugin:2.0-SNAPSHOT:
checking f
or updates from apache-snapshots
[INFO] snapshot
org.apache.geronimo.plugins:selenium-maven-plugin:2.0-SNAPSHOT:
checking f
or updates from codehaus-snapshots
[INFO] snapshot
org.apache.geronimo.plugins:geronimo-maven-plugin:2.0-SNAPSHOT:
checking f
or updates from apache-snapshots
[INFO] snapshot
org.apache.geronimo.plugins:geronimo-maven-plugin:2.0-SNAPSHOT:
checking f
or updates from codehaus-snapshots
[INFO] snapshot
org.apache.geronimo.plugins:geronimo-maven-plugin:2.0-SNAPSHOT:
checking f
or updates from apache.snapshots
[INFO] [clean:clean]
[INFO] Deleting directory
C:\anita\geronimo\g2.0\testsuite\console-testsuite\target
[INFO] Deleting directory
C:\anita\geronimo\g2.0\testsuite\console-testsuite\target\classe
s
[INFO] Deleting directory
C:\anita\geronimo\g2.0\testsuite\console-testsuite\target\test-c
lasses
[INFO] [maven:invoke {execution: clean}]
[INFO] Invoking:
C:\anita\geronimo\g2.0\testsuite\console-testsuite\basic\pom.xml
[INFO] + Error stacktraces are turned on.
[INFO] [INFO] Scanning for projects...
[INFO] [INFO]


[INFO] [INFO] Building Geronimo TestSuite, Console :: Basic
[INFO] [INFO]task-segment: [clean]
[INFO] [INFO]


[INFO] [INFO] snapshot org.apache.geronimo:geronimo:2.0-SNAPSHOT:
checking for updates fro
m jtidy.sourceforge
[INFO] [INFO] snapshot
org.apache.maven.plugins:maven-surefire-plugin:2.3-SNAPSHOT: checki
ng for updates from apache-snapshots
[INFO] [INFO] snapshot
org.apache.maven.plugins:maven-surefire-plugin:2.3-SNAPSHOT: checki
ng for updates from codehaus-snapshots
[INFO] [INFO] snapshot
org.apache.maven.plugins:maven-surefire-plugin:2.3-SNAPSHOT: checki
ng for updates from apache.snapshots
[INFO] [INFO] snapshot org.apache.maven.surefire:surefire:2.3-SNAPSHOT:
checking for updat
es from apache-snapshots
[INFO] [INFO] snapshot org.apache.maven.surefire:surefire:2.3-SNAPSHOT:
checking for updat
es from codehaus-snapshots
[INFO] [INFO] snapshot org.apache.maven.surefire:surefire:2.3-SNAPSHOT:
checking for updat
es from apache.snapshots
[INFO] Downloading:
http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/
surefire/surefire/2.3-SNAPSHOT/surefire-2.3-20070124.041233-4.pom
[INFO] 4K downloaded
[INFO] [INFO] snapshot org.apache.maven:maven-parent:5-SNAPSHOT:
checking for updates from
 apache-snapshots
[INFO] [INFO] snapshot org.apache.maven:

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38077
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 17:04:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:04:09 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291604CXXNB4F3
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38078
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 17:06:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:06:40 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291606Z2SAVRJ6
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38079
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 17:08:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:08:25 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291608CXXNB4KR
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38080
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 17:10:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:10:24 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291610CXXNB4M5
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Patches in RTC (Geronimo - 2007-01-29)

[dblevins]

Geronimo - Monday, January 29, 2007

  5 Patches in RTC

[GERONIMO-2638] Improve ModuleBuilder and ConfigurationBuilder interfaces 
to replace use of JarFile
  - Assignee: Sachin Patel
  - Reporter: Sachin Patel
  - Created:  Thu Dec 07 23:41:31 GMT 2006
  - Updated:  Tue Jan 23 16:16:35 GMT 2007
  - Votes: 0
  - http://issues.apache.org/jira/browse/GERONIMO-2638

[GERONIMO-2485] PersistenceUnitGBean needs a NamespaceDrivenDeployer
  - Assignee: David Jencks
  - Reporter: David Jencks
  - Created:  Wed Oct 11 21:23:29 GMT 2006
  - Updated:  Tue Jan 09 08:25:55 GMT 2007
  - Votes: 0
  - http://issues.apache.org/jira/browse/GERONIMO-2485

[GERONIMO-1277] Change group-id to org.apache.geronimo
  - Assignee: Jason Dillon
  - Reporter: Dain Sundstrom
  - Created:  Sat Dec 03 10:55:12 GMT 2005
  - Updated:  Tue Nov 07 23:57:44 GMT 2006
  - Votes: 0
  - http://issues.apache.org/jira/browse/GERONIMO-1277

[GERONIMO-2015] Let's replace JKS to PKCS12 key store type
  - Assignee: Unassigned
  - Reporter: Nikolay Chugunov
  - Created:  Fri May 12 21:54:17 GMT 2006
  - Updated:  Wed Dec 06 06:57:11 GMT 2006
  - Votes: 0
  - http://issues.apache.org/jira/browse/GERONIMO-2015

[GERONIMODEVTOOLS-112] Loading deployment plan editor on empty file should 
auto-create plan
  - Assignee: Sachin Patel
  - Reporter: Sachin Patel
  - Created:  Wed Oct 11 21:45:57 GMT 2006
  - Updated:  Tue Jan 02 16:27:54 GMT 2007
  - Votes: 0
  - http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-112


NOTE: This email is generated and does not constitute and offical
vote or vote result.  All official voting is done on the dev list.

If you do not see your issue here, click the "Begin RTC Review"
link under the "Available Workflow Actions" of the JIRA page.

If you do not see your vote here, click the "Vote" link under the
"Operations" section of the JIRA page.


 *** ALL COMMUNITY MEMBERS ARE ENCOURAGED TO VOTE ***

Template: 
http://svn.apache.org/repos/asf/geronimo/gbuild/jirareports/patchesInRtc.vm

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38081
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 17:12:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:12:45 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291612Z2SAVRRC
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38082
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 17:14:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:14:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291614Z2SAVRT1
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Why is GERONIMO_HOME not passed into the server?

[David Jencks]

I'm really glad someone took the time to check that this actually  
works!.  I'd like to see it be a standard plugin.  IIRC there might  
be some way to get the plugin machinery to create the directory for you?


One slight convenience I thought of would be to add a flag to the  
Maven2Repository to determine if it resolves root against the base or  
server directory from serverinfo.  With what we have now, you'd  
presumably put the new repo inside var, but then if you used the  
command line to relocate var, you'd have to override the root  
location in config.xml so the correct repo was picked up.  With a  
flag in the repo gbean, the standard repo could be resolved against  
base but the additional repo from the plugin could be resolved  
against server.


thanks
david jencks

On Jan 28, 2007, at 1:20 PM, Ted Kirby wrote:


On 1/27/07, David Jencks <[EMAIL PROTECTED]> wrote:

AFAIK support for everything needed to do this is already there, all
you need is another module with an additional repository which might
be located by default in var/repository.

Existing command line properties:
-Dorg.apache.geronimo.home.dir=/path/to/geronimo/home speciifies
where the geronimo installation (bin dir etc) are located.  I haven't
figured out how this is useful yet but its there.
-Dorg.apache.geronimo.server.name=foo makes geronimo look for var at
/foo
-Dorg.apache.geronimo.server.dir=/path/to/var/dir specifies where var
is as an absolute path (if you don't supply a absolute path, its the
same as "name")

We support running with multiple repositories, and deploying to a
specific repository with a deployer command line argument
java -jar bin/deployer.jar -target repo-name

All we need is to add another module/configuration that has a
repository gbean and a config store gbean pointing to var/
repository.  I think this should be a plugin.


This second repo stuff is just way cool!  It also works, in 1.1 and  
2.0!


Here is my repo2.xml plan:

http://geronimo.apache.org/xml/ns/deployment-1.2";>
 
   
 org.example.configs
 myrepo
 2.0-SNAPSHOT
 car
   
   
 
   org.apache.geronimo.configs
   j2ee-system
   2.0-SNAPSHOT
   car
 
   
   
   
 
 
 
   repo2/
   
 ServerInfo
   
 
 
 class="org.apache.geronimo.system.configuration.RepositoryConfiguratio 
nStore">

   
 Repo2
   
 


mkdir 
java deployer.jar list-targets


Available Targets:
 org.example.configs/myrepo/2.0-SNAPSHOT/car? 
ServiceModule=org.example.configs/myrepo/2.0-SNAPSHOT/ 
car,j2eeType=ConfigurationStore,name=Local2
 org.apache.geronimo.configs/j2ee-system/2.0-SNAPSHOT/car? 
ServiceModule=org.apache.geronimo.configs/j2ee-system/2.0-SNAPSHOT/ 
car,j2eeType=ConfigurationStore,name=Local


Use of environment variables recommended for command-line use.

To deploy to the new repo, use:

deploy --targets %REPO2% sample.war

deploy list-modules also gives those long target names on each module.

However, deploy list-modules %REPO2% gives the accustomed short  
output.



So, I don't think this requires any code, just someone to write the
module plan and check everything works.  I don't see how this affects
the server file structure except for the already present capability
to relocate var.

Not everyone will want to have a separate per server additional
repository for running many servers off one files system copy.  For
instance if all the servers use the same apps you might as well
deploy them all to the regular repository.

thanks
david jencks

On Jan 27, 2007, at 2:38 PM, Jason Dillon wrote:

> I think in order to allow multiple instances to work off of the
> same installation effectively we need to have a tiered repository
> support, so that each instance could include a shared read-only
> repository (the system repository), and then a read-write
> repository (instance repository), where artifact resolution would
> first check the instance repo, then the system repo.
>
> If we do want to start supporting this, I suggest we also revisit
> the basic server's file structure, as we will need to insert a
> hierarchy for the instance data.
>
> --jason
>
>
> On Jan 27, 2007, at 1:51 PM, Matt Hogstrom wrote:
>
>> I've been looking at this recently interms of being able to run
>> multiple oag instances out of the same filesystem.  This means we
>> need to identify several different points in the filesystem.  This
>> is not exhaustive but really for discussion since Ted brought  
it up.

>>
>> One is the location of the Geronimo server.  I'll refer to this as
>> $GERONIMO_HOME.  This directory is the root of the Geronimo
>> installation.
>>
>> The next Location is the $GERONIMO_INSTANCE which would contain
>> the parts of the repository that an individual instance would
>> need.  This would include a repository, var entries for config,
>> logs, etc.  One approach would be to make the GERONIMO_INSTANCE be
>> a shadow of the normal dir structure for GERONIMO_HOME that is
>> only populated with items that are different

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38083
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 17:16:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:16:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291616Z2SAVRVW
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38084
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 17:18:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:18:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291618CXXNB4W3
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38085
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 17:20:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:20:04 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701291620Z2SAVR5R
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38086
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 17:22:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:22:09 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291622CXXNB46L
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38087
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 17:24:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 17:24:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701291624CXXNB485
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: How to find the context root of a webapp when a EAR is deployed ?

[Prasad Kashyap]

OK. Can we design it in such a way that the WARs do show up in that
list with maybe just the context root ? It'd be ok if the other
operations are not permitted on such a webapp.

That will be a huge usability enhancement wherein you can now directly
go to the context root URL of an application.This will be specially
useful for plugins and samples where the user downloads readily
available EARs and deploys them. He doesn't have to have the added
hassle of knowing what the just deployed app's context root is.

Cheers
Prasad

On 1/28/07, Paul McMahan <[EMAIL PROTECTED]> wrote:

I suspect the reason that WARs contained in EARs are not listed in the
Web App WARs portlet is because the start, stop, restart, and
uninstall controls would not work as expected.

Best wishes,
Paul

On 1/28/07, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
> After the samples application EAR is deployed, it shows up only in the
> "Application EARs" portlet.
>
> It's webapp does not show up in the list of Web App WARs.  So one
> cannot find it's context root (URL) and go to it.
>
> Is this by design ?
>
> Cheers
> Prasad
>

Re: How to find the context root of a webapp when a EAR is deployed ?

[Vamsavardhana Reddy]

I guess there is already a JIRA on this.  If not, it is better to create one
to track this.

Vamsi

On 1/29/07, Prasad Kashyap <[EMAIL PROTECTED]> wrote:


OK. Can we design it in such a way that the WARs do show up in that
list with maybe just the context root ? It'd be ok if the other
operations are not permitted on such a webapp.

That will be a huge usability enhancement wherein you can now directly
go to the context root URL of an application.This will be specially
useful for plugins and samples where the user downloads readily
available EARs and deploys them. He doesn't have to have the added
hassle of knowing what the just deployed app's context root is.

Cheers
Prasad

On 1/28/07, Paul McMahan <[EMAIL PROTECTED]> wrote:
> I suspect the reason that WARs contained in EARs are not listed in the
> Web App WARs portlet is because the start, stop, restart, and
> uninstall controls would not work as expected.
>
> Best wishes,
> Paul
>
> On 1/28/07, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
> > After the samples application EAR is deployed, it shows up only in the
> > "Application EARs" portlet.
> >
> > It's webapp does not show up in the list of Web App WARs.  So one
> > cannot find it's context root (URL) and go to it.
> >
> > Is this by design ?
> >
> > Cheers
> > Prasad
> >
>

Re: How to find the context root of a webapp when a EAR is deployed ?

[Paul McMahan]

That sounds like a good improvement.  Wanna open a JIRA?  In the
meantime you can look for the context root in the server startup
output.

Best wishes,
Paul

On 1/29/07, Prasad Kashyap <[EMAIL PROTECTED]> wrote:

OK. Can we design it in such a way that the WARs do show up in that
list with maybe just the context root ? It'd be ok if the other
operations are not permitted on such a webapp.

That will be a huge usability enhancement wherein you can now directly
go to the context root URL of an application.This will be specially
useful for plugins and samples where the user downloads readily
available EARs and deploys them. He doesn't have to have the added
hassle of knowing what the just deployed app's context root is.

Cheers
Prasad

On 1/28/07, Paul McMahan <[EMAIL PROTECTED]> wrote:
> I suspect the reason that WARs contained in EARs are not listed in the
> Web App WARs portlet is because the start, stop, restart, and
> uninstall controls would not work as expected.
>
> Best wishes,
> Paul
>
> On 1/28/07, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
> > After the samples application EAR is deployed, it shows up only in the
> > "Application EARs" portlet.
> >
> > It's webapp does not show up in the list of Web App WARs.  So one
> > cannot find it's context root (URL) and go to it.
> >
> > Is this by design ?
> >
> > Cheers
> > Prasad
> >
>

Re: [VOTE] 2.0-M2 Milestone ready for review and JACC Specs

[Christopher M. Cardona]

anita kulshreshtha wrote:
+1 


   Please note the following issues for future releases:
1. Clicking on LDAP Viewer produces stack trace: 
08:49:59,484 WARN  [ExecuteQuery] Method execution failed: 
java.lang.Exception: Problem connecting to directory server:

localhost:1389
at
org.apache.geronimo.console.ldapmanager.LDAPManagerHelper.(LDAPManagerHelper.java:113)

  


By default the LDAP Viewer portlet connects to the embedded Apache DS 
and if it's not started it will result to this stack trace and it should 
pop some warning message followed by displaying the 'Connect Info' tab 
to allow users to change settings and reconnect. We can possibly consume 
the exception when DWR creates the LDAP utility class to avoid the stack 
trace.



2. ClassLoader Viewer throws error:
08:51:13,203 ERROR [RowFragment_jsp]] Servlet.service() for servlet
jsp.WEB_002dINF.aggregation.RowFragment_jsp threw exception
javax.servlet.ServletException: Java heap space

  

I also see this randomly on one of my Windows box.

I'm ok with these issues for this release. Here's my +1.

chris

ejbjars with geronimo plans fail deployment

[Sachin Patel]

It looks as if a deployment fails for ejbjar's containing a geronimo  
plan, unable to recognize any of the openejb specific elements.  Is  
this a known issue?  What needs to be updated in the geronimo-openejb  
schema to fix this?  Or does this involve more then a schema update?


-sachin

Re: [VOTE] 2.0-M2 Milestone ready for review and JACC Specs

[Paul McMahan]

+1

I compiled the source.zip from your directory, which also required
building openejb-r500340 and geronimo-jacc_1.1_spec--1.0-M2 locally.
I tested the admin console and plugins,  updating the plugin catalog
to support this new release.  Nice job everyone!

Best wishes,
Paul

On 1/27/07, Matt Hogstrom <[EMAIL PROTECTED]> wrote:

All,

I have made the binaries from Geronimo 2.0-M2 available for review at:

http://people.apache.org/~hogstrom/2.0-M2-rc1

In this directory you will find the various assemblies for your
review as well as one massive tar ball that has the various artifacts
that will ultimately be distributed.

The files are being uploaded as this is being written so give them
some time.

Also included in this vote are the artifacts for the JACC spec 1.0-M2
which is required for 2.0-M2.

Remember...this is a milestone and not a full release.

Thanks for David Blevins for being quite the helper tonight in
getting the Release Notes in line and helping out with Open EJB.

Thanks

This vote will conclude on Tuesday at 0100 Eastern.

Cheers.

Matt

Re: windows build failure

[Hernan Cunico]

Enabling extensions did not work for me.

Cheers!
Hernan

Donald Woods wrote:
If you're using WinXP or Win2003 without Cygwin or other shell changes, 
try changing the following line in your \bin\mvn.bat -

   if "%OS%"=="Windows_NT" @setlocal
to:
   if "%OS%"=="Windows_NT" @setlocal enableextensions


-Donald

Joe Bohn wrote:
No, I haven't attempted that yet.  I'll give that a try a little 
later.  Right now I'm trying to see if building OpenEJB3 locally makes 
any difference since I know of at least one person that isn't hitting 
this problem but has built openejb3.


Thanks for the responses and ideas.

Joe


anita kulshreshtha wrote:

  Have you tried moving these 2 files to their rightful place, i.e. in
3.0-incubating-SNAPSHOT directory?

container-3.0-incubating-20070123.025044-17.pom
container-3.0-incubating-20070123.025044-17.pom.sha1

Thanks
Anita

--- Joe Bohn <[EMAIL PROTECTED]> wrote:


I think the problem that Hernan reported last week building on
Windows is still alive and well.  It doesn't seem to cause any 
problems on

OSX.

I was hitting it yesterday and just hit it again today with the
2.0-M2 branch, rev. 499407.


It seems to me that there is something fishy with the 
container-3.0-incubating-SNAPSHOT.pom that only seems to cause grief

on windows (see the messages below between the "***" lines I
inserted where there is an error reading and error in opening the 
zip file).



This results in some strange entries in my local repo for the openejb

container:

+---3.0-incubating-20070123.025044-17
|   container-3.0-incubating-20070123.025044-17.pom
|   container-3.0-incubating-20070123.025044-17.pom.sha1
|
\---3.0-incubating-SNAPSHOT
 container-3.0-incubating-SNAPSHOT.pom


Deleting these time-stamp entries and running again doesn't seem to 
avoid the problem.   This is building with a completely empty repo
and clean %tmp% with a fresh checkout.   I've recreated on 2 
different machines.   I think something is screwed up with the pom 
or maven-metadata but I'm not up on maven enough to know what it is.





[INFO]
 


[INFO] Building Geronimo :: OpenEJB :: Builder
[INFO]task-segment: [clean, install]
[INFO]
 


[INFO] [clean:clean]
[INFO] Deleting directory 
C:\geronimo2.0-M2\modules\geronimo-openejb-builder\target
[INFO] Deleting directory 
C:\geronimo2.0-M2\modules\geronimo-openejb-builder\target\classes

[INFO] Deleting directory

C:\geronimo2.0-M2\modules\geronimo-openejb-builder\target\test-classes

[INFO] [tools:require-java-version {execution:
validate-java-version}]
Downloading:
http://tomcat.apache.org/dev/dist/m2-repository//org/apache/geronimo/specs/geronimo-ejb_3.0_spec/1.0-M1/geronimo-ejb_3.0_spec-1.0-M1.jar 

[WARNING] Unable to get resource from repository tomcat-m2-repo 
(http://tomcat.apache.org/dev/dist/m2-repository/)

Downloading:
http://people.apache.org/repo/m2-incubating-repository//org/apache/geronimo/specs/geronimo-ejb_3.0_spec/1.0-M1/geronimo-ejb_3.0_spec-1.0-M1.jar 

[WARNING] Unable to get resource from repository apache-incubator 
(http://people.apache.org/repo/m2-incubating-repository/)

Downloading:
http://repository.codehaus.org/org/apache/geronimo/specs/geronimo-ejb_3.0_spec/1.0-M1/geronimo-ejb_3.0_spec-1.0-M1.jar 

[WARNING] Unable to get resource from repository codehaus 
(http://repository.codehaus.org)

Downloading:
http://people.apache.org/repo/m2-incubating-repository/org/apache/geronimo/specs/geronimo-ejb_3.0_spec/1.0-M1/geronimo-ejb_3.0_spec-1.0-M1.jar 

[WARNING] Unable to get resource from repository 
apache-incubating-repository 
(http://people.apache.org/repo/m2-incubating-repository)

Downloading:
http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-ejb_3.0_spec/1.0-M1/geronimo-ejb_3.0_spec-1.0-M1.jar 


31K downloaded
[INFO] [xmlbeans:xmlbeans {execution: default}]
Time to build schema type system: 0.156 seconds
Time to generate code: 0.125 seconds

***

error: error reading
c:\m2repo\org\apache\openejb\container\3.0-incubating-SNAPSHOT\container-3.0-incubating-SNAPSHOT.pom; 


error in opening zip file
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
1 error

***


BUILD FAILED
[INFO]



[ERROR] BUILD ERROR
[INFO]



[INFO] XmlBeans compile failed:
  xml ErrorLoading schema file
C:\geronimo2.0-M2\modules\geronimo-openejb-builder\src\main\schema\geronimo-openejb-2.0.xsd 


xml ErrorLoading config file
C:\geronimo2.0-M2\modules\geronimo-openejb-builder\src\main\schema\xmlconfig.xml 


[INFO]



[INFO] For more information, run Maven with the -e switch
[INFO]

Re: [VOTE] 2.0-M2 Milestone ready for review and JACC Specs

[Paul McMahan]

On 1/29/07, anita kulshreshtha <[EMAIL PROTECTED]> wrote:

+1

   Please note the following issues for future releases:
1. Clicking on LDAP Viewer produces stack trace:
08:49:59,484 WARN  [ExecuteQuery] Method execution failed:
java.lang.Exception: Problem connecting to directory server:
localhost:1389
at
org.apache.geronimo.console.ldapmanager.LDAPManagerHelper.(LDAPManagerHelper.java:113)


You can avoid this by starting the directory module from the System
Modules portlet before starting the LDAP viewer.


2. ClassLoader Viewer throws error:
08:51:13,203 ERROR [RowFragment_jsp]] Servlet.service() for servlet
jsp.WEB_002dINF.aggregation.RowFragment_jsp threw exception
javax.servlet.ServletException: Java heap space


I think Kevan has fixed this in trunk...


3. The Create and Install Plugins page lists all entries as 'not
available', e.g.
 * 
 * Geronimo Admin Console (Tomcat) (Not available; View Details)
 * .
  It should probably read as 'View Availability'.


I updated the plugin catalog to include 2.0-M2 as a compatible version
for the plugins.  This causes the right plugins to show up as
available.  The updated catalog should be propogated to
geronimo.apache.org within the hour.



Thanks
Anita

--- Matt Hogstrom <[EMAIL PROTECTED]> wrote:

> All,
>
> I have made the binaries from Geronimo 2.0-M2 available for review
> at:
>
> http://people.apache.org/~hogstrom/2.0-M2-rc1
>
> In this directory you will find the various assemblies for your
> review as well as one massive tar ball that has the various artifacts
>
> that will ultimately be distributed.
>
> The files are being uploaded as this is being written so give them
> some time.
>
> Also included in this vote are the artifacts for the JACC spec 1.0-M2
>
> which is required for 2.0-M2.
>
> Remember...this is a milestone and not a full release.
>
> Thanks for David Blevins for being quite the helper tonight in
> getting the Release Notes in line and helping out with Open EJB.
>
> Thanks
>
> This vote will conclude on Tuesday at 0100 Eastern.
>
> Cheers.
>
> Matt
>





Be a PS3 game guru.
Get your game face on with the latest PS3 news and previews at Yahoo! Games.
http://videogames.yahoo.com/platform?platform=120121

Re: svn commit: r501156 - /geronimo/server/trunk/modules/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/ClientEjbReference.java

[Jacek Laskowski]

On 1/29/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

Author: sppatel
Date: Mon Jan 29 11:39:20 2007
New Revision: 501156

URL: http://svn.apache.org/viewvc?view=rev&rev=501156
Log:
typo in property name, missing "."


Whoa! How did you find it? Just wondering what tools people use to
spot such annoying errors.

Jacek

--
Jacek Laskowski
http://www.JacekLaskowski.pl

Re: svn commit: r501156 - /geronimo/server/trunk/modules/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/ClientEjbReference.java

[Sachin Patel]

By luck :), noticed it after bringing it up in a an editor debugging  
a CNF exception


On Jan 29, 2007, at 2:45 PM, Jacek Laskowski wrote:


On 1/29/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

Author: sppatel
Date: Mon Jan 29 11:39:20 2007
New Revision: 501156

URL: http://svn.apache.org/viewvc?view=rev&rev=501156
Log:
typo in property name, missing "."


Whoa! How did you find it? Just wondering what tools people use to
spot such annoying errors.

Jacek

--
Jacek Laskowski
http://www.JacekLaskowski.pl



-sachin

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38197
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 21:03:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:03:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701292003Z2SAVXGF
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38198
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 21:05:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:05:10 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701292005Z2SAVXG0
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38199
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 21:07:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:07:37 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701292007CXXNB51D
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38200
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 21:09:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:09:05 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701292009Z2SAVX2W
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38201
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 21:11:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:11:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701292011CXXNB5F9
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38202
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 21:13:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:13:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701292013CXXNB5GX
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38203
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 21:15:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:15:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701292015CXXNB5HP
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38204
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 21:17:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:17:05 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701292017Z2SAVXMK
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38205
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 21:19:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:19:09 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701292019CXXNB520
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38206
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 21:21:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:21:05 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701292021Z2SAVXN8
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38207
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 21:23:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:23:10 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701292023Z2SAVX3Z
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38208
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 21:25:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:25:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701292025CXXNB5LW
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38209
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 21:27:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:27:20 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701292027CXXNB5MT
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38210
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 21:29:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:29:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701292029CXXNB5N3
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38211
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 21:31:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:31:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701292031Z2SAVXS1
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38212
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 21:33:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:33:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701292033CXXNB5PH
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (AMQ-1143) Need a way to set tcpNoDelay on peer transport TCP network connections

[Andrew Steele (JIRA)]

Need a way to set tcpNoDelay on peer transport TCP network connections
--

 Key: AMQ-1143
 URL: https://issues.apache.org/activemq/browse/AMQ-1143
 Project: ActiveMQ
  Issue Type: Improvement
  Components: Transport
Affects Versions: 4.1.0
 Environment: Windows XP Professional / JRE 1.5.0_11
Reporter: Andrew Steele


I really like the peer transport in ActiveMQ.  It seems to be just the kind of 
setup we need.  However, we do have low round-trip latency requirements in some 
applications.  I was seeing unacceptably bad latencies (~200ms) for synchronous 
round trips.  I installed Wireshark and performed network analysis to see what 
was going on.  It appeared to be a Nagle algorithm / TCP ACK delay issue.  
Essentially, after the first message request and reply, the next request 
message may be delayed while waiting for a delayed ACK from the other broker.  
This should be resolvable by enabling tcpNoDelay.  However, the peer transport 
URI provides no mechanism to enable tcpNoDelay.  In fact, I went into the 
source code and found that the TCP network connecter specified in the 
PeerTransportFactory is hard coded to tcp://localhost:0.  Basically, I need a 
way to turn on tcpNoDelay in peer transport.

-- 
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

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38213
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 21:35:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:35:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701292035Z2SAVX4X
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38214
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 21:37:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:37:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701292037CXXNB5R9
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38215
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 21:39:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:39:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701292039CXXNB5SZ
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38216
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 21:41:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:41:05 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701292041Z2SAVXXL
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38217
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 21:43:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:43:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701292043Z2SAVXYR
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38218
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Mon, 29 Jan 2007 21:45:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Mon, 29 Jan 2007 21:45:07 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA010701292045Z2SAVXZ3
MSEXCH:IMS:Fortis:DBIB:DBIBAA01 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-2781) Improved CXF-based POJO WebService support

[Dan Diephouse (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-2781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468407
 ] 

Dan Diephouse commented on GERONIMO-2781:
-

Jarek - is there a way we can make our APIs more extensible so you don't have 
to redo functionality which is in CXF? Specifically the annotation processor 
which you refer to?

> Improved CXF-based POJO WebService support
> --
>
> Key: GERONIMO-2781
> URL: https://issues.apache.org/jira/browse/GERONIMO-2781
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: webservices
>Affects Versions: 2.0-beta1
>Reporter: Jarek Gawor
> Attachments: GERONIMO-2781.patch
>
>
> The attached patch contains numerous improvements to JAX-WS support for POJOs 
> (via CXF):
> 1) Annotation support for the service and handlers. The following annotation 
> are recognized: @Resource, @EJB, @WebServiceRef, @PreDestroy, @PostConstruct. 
> The values are injected if the given resource is defined in JNDI. The patch 
> includes a basic annotation processor. The processor itself is pretty basic 
> but is generic and pluggable and can be (re)used in other places. It was 
> necessary to add one because CXF annotation processor only handles @Resource 
> annotations and it was not very extensible.
> 2) WebServicesContext.getUserPricipa() and .isUserInRole() are now properly 
> implemented by delegating the calls to the Servlet class
> 3) Improved webservices.xml file parsing and information passing to the web 
> container. Information specified in the webservices.xml file can now 
> overwrite the information specified in the annotations. For example, 
> @HandlerChain can be overwritten by  element. Same with 
> wsdl-port, wsdl-service, and wsdl-file.
> 4) Switched to using Commons Logging API instead of Java Logging API

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (XBEAN-73) XsdGenerator generates incorrectly

[Kohsuke Kawaguchi (JIRA)]

XsdGenerator generates  incorrectly


 Key: XBEAN-73
 URL: https://issues.apache.org/jira/browse/XBEAN-73
 Project: XBean
  Issue Type: Bug
  Components: spring
Affects Versions: 2.8
Reporter: Kohsuke Kawaguchi


On XsdGenerator.java line 102, the code reads:

if (complexCount > 0) {
out.println("  ");
for (Iterator iterator = element.getAttributes().iterator(); 
iterator.hasNext();) {
AttributeMapping attributeMapping = (AttributeMapping) 
iterator.next();
if (!namespaceMapping.isSimpleType(attributeMapping.getType())) 
{
generateElementMappingComplexProperty(out, 
namespaceMapping, attributeMapping);
}
}
out.println(""); // <--- 
PROBLEM!
out.println("  ");
}

but it really needs to be:
out.println("");


-- 
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

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38333
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Tue, 30 Jan 2007 01:34:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Tue, 30 Jan 2007 01:34:08 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300034CXXNB82K
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1142) TemporaryQueue communication not working

[System Administrator (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38334
 ] 

System Administrator commented on AMQ-1142:
---

Your message

  To:  [EMAIL PROTECTED]
  Subject: [jira] Commented: (AMQ-1142) TemporaryQueue communication not
working
  Sent:Tue, 30 Jan 2007 01:36:03 +0100

did not reach the following recipient(s):

c=NL;a=400Net;p=Fortis;o=DBIB;dda:[EMAIL PROTECTED]; on
Tue, 30 Jan 2007 01:36:06 +0100
The recipient name is not recognized
The MTS-ID of the original message is:
c=nl;a=400net;p=fortis;l=DBIBAA060701300036CXXNB826
MSEXCH:IMS:Fortis:DBIB:DBIBAA06 0 (000C05A6) Unknown Recipient




DISCLAIMER***
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Fortis sluit iedere 
aansprakelijkheid uit die voortvloeit uit electronische verzending. 

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Fortis rules out any and every liability resulting from any electronic 
transmission. 
**


> TemporaryQueue communication not working
> 
>
> Key: AMQ-1142
> URL: https://issues.apache.org/activemq/browse/AMQ-1142
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMS client
>Affects Versions: 4.1.0
> Environment: WinXP, Java 1.4.2
>Reporter: Jos
> Attachments: Client.java, Server.java
>
>
> Assume a (old legacy, yes this is out of date and better solutions are 
> available) point to point architecture:
> Client creates temporary queues and send the queuename to the server by a 
> fixed queue ('command queue')
> Server uses the received queue names to send messages to the client.
> See the attached Code snippets:
> * Start the Server
> * Start the Client
> * The Client creates a temporary queue and sends the name to the server
> * Server receives message and sends a test message back.
> * Client NEVER receives the test message
> This works 100% on IBM MQSeries (the only source diff is the line that has a 
> MQSerie getQueue API call, instead a createQueue, because queus are defined, 
> and not dynamical as in ActiveMQ)
> ActiveMQ LOG information:
> The temporary queue is logged, but later it says that there are no 
> subscriptions
> (..)
> DEBUG AbstractRegion - Adding destination: 
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:TIGER-2615-1170064714906-1:0:1
> DEBUG JournalPersistenceAdapter  - Checkpoint done.
> DEBUG TIGER-2615-1170064714906-1:0:1 - No subscriptions registered, will not 
> dispatch message at this time.
> (...)
> Can this bug be fixed?
> Thank you, Jos

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: svn commit: r501232 - /geronimo/server/trunk/modules/geronimo-jaxws/pom.xml

[Jarek Gawor]

Why is that needed here?

Jarek

On 1/29/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

Author: dims
Date: Mon Jan 29 15:33:49 2007
New Revision: 501232

URL: http://svn.apache.org/viewvc?view=rev&rev=501232
Log:
oops! add missing repo

Modified:
geronimo/server/trunk/modules/geronimo-jaxws/pom.xml

Modified: geronimo/server/trunk/modules/geronimo-jaxws/pom.xml
URL: 
http://svn.apache.org/viewvc/geronimo/server/trunk/modules/geronimo-jaxws/pom.xml?view=diff&rev=501232&r1=501231&r2=501232
==
--- geronimo/server/trunk/modules/geronimo-jaxws/pom.xml (original)
+++ geronimo/server/trunk/modules/geronimo-jaxws/pom.xml Mon Jan 29 15:33:49 
2007
@@ -32,6 +32,23 @@
 geronimo-jaxws
 Geronimo :: JAXWS

+
+
+maven-repo1
+maven official repo
+http://repo1.maven.org/maven/
+legacy
+
+
+
+true
+
+ws-zones
+ws.zones maven repository
+http://ws.zones.apache.org/repository/
+legacy
+
+
 

 

Re: svn commit: r501215 - in /geronimo/server/trunk/modules: ./ geronimo-axis2/ geronimo-cxf-builder/src/main/java/org/apache/geronimo/cxf/builder/ geronimo-cxf-builder/src/main/java/org/apache/geroni

[Jarek Gawor]

Dims,

The following dependency needs to be added to configs/cxf/pom.xml:


   org.apache.geronimo.modules
   geronimo-jaxws
   ${version}
   

Jarek

On 1/29/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

Author: dims
Date: Mon Jan 29 14:51:09 2007
New Revision: 501215

URL: http://svn.apache.org/viewvc?view=rev&rev=501215
Log:
move the common jaxws code into a separate maven module, next step would be to 
fix axis2 modules to reuse the common code

Added:
geronimo/server/trunk/modules/geronimo-jaxws/
geronimo/server/trunk/modules/geronimo-jaxws/LICENSE.txt
geronimo/server/trunk/modules/geronimo-jaxws/NOTICE.txt
geronimo/server/trunk/modules/geronimo-jaxws/pom.xml
geronimo/server/trunk/modules/geronimo-jaxws/src/
geronimo/server/trunk/modules/geronimo-jaxws/src/main/
geronimo/server/trunk/modules/geronimo-jaxws/src/main/java/
geronimo/server/trunk/modules/geronimo-jaxws/src/main/java/org/
geronimo/server/trunk/modules/geronimo-jaxws/src/main/java/org/apache/

geronimo/server/trunk/modules/geronimo-jaxws/src/main/java/org/apache/geronimo/

geronimo/server/trunk/modules/geronimo-jaxws/src/main/java/org/apache/geronimo/jaxws/
  - copied from r501199, 
geronimo/server/trunk/modules/geronimo-cxf/src/main/java/org/apache/geronimo/jaxws/

geronimo/server/trunk/modules/geronimo-jaxws/src/main/java/org/apache/geronimo/jaxws/builder/
  - copied from r501199, 
geronimo/server/trunk/modules/geronimo-cxf-builder/src/main/java/org/apache/geronimo/jaxws/builder/
Removed:

geronimo/server/trunk/modules/geronimo-cxf-builder/src/main/java/org/apache/geronimo/jaxws/builder/

geronimo/server/trunk/modules/geronimo-cxf/src/main/java/org/apache/geronimo/jaxws/
Modified:
geronimo/server/trunk/modules/geronimo-axis2/pom.xml

geronimo/server/trunk/modules/geronimo-cxf-builder/src/main/java/org/apache/geronimo/cxf/builder/CXFBuilder.java
geronimo/server/trunk/modules/geronimo-cxf/pom.xml

geronimo/server/trunk/modules/geronimo-cxf/src/main/java/org/apache/geronimo/cxf/CXFEndpoint.java

geronimo/server/trunk/modules/geronimo-jaxws/src/main/java/org/apache/geronimo/jaxws/PortInfo.java
geronimo/server/trunk/modules/pom.xml

Modified: geronimo/server/trunk/modules/geronimo-axis2/pom.xml
URL: 
http://svn.apache.org/viewvc/geronimo/server/trunk/modules/geronimo-axis2/pom.xml?view=diff&rev=501215&r1=501214&r2=501215
==
--- geronimo/server/trunk/modules/geronimo-axis2/pom.xml (original)
+++ geronimo/server/trunk/modules/geronimo-axis2/pom.xml Mon Jan 29 14:51:09 
2007
@@ -53,7 +53,7 @@
 
 
 org.apache.geronimo.modules
-geronimo-webservices
+geronimo-jaxws
 ${version}
 


Modified: 
geronimo/server/trunk/modules/geronimo-cxf-builder/src/main/java/org/apache/geronimo/cxf/builder/CXFBuilder.java
URL: 
http://svn.apache.org/viewvc/geronimo/server/trunk/modules/geronimo-cxf-builder/src/main/java/org/apache/geronimo/cxf/builder/CXFBuilder.java?view=diff&rev=501215&r1=501214&r2=501215
==
--- 
geronimo/server/trunk/modules/geronimo-cxf-builder/src/main/java/org/apache/geronimo/cxf/builder/CXFBuilder.java
 (original)
+++ 
geronimo/server/trunk/modules/geronimo-cxf-builder/src/main/java/org/apache/geronimo/cxf/builder/CXFBuilder.java
 Mon Jan 29 14:51:09 2007
@@ -22,6 +22,7 @@
 import org.apache.cxf.jaxws.javaee.ServiceImplBeanType;
 import org.apache.cxf.jaxws.javaee.WebserviceDescriptionType;
 import org.apache.cxf.jaxws.javaee.WebservicesType;
+import org.apache.cxf.jaxws.javaee.HandlerChainsType;
 import org.apache.geronimo.common.DeploymentException;
 import org.apache.geronimo.jaxws.PortInfo;
 import org.apache.geronimo.gbean.GBeanInfo;
@@ -119,7 +120,7 @@
 portInfo.setEnableMTOM(port.getEnableMtom().isValue());
 }

-portInfo.setHandlers(port.getHandlerChains());
+portInfo.setHandlers(HandlerChainsType.class, 
port.getHandlerChains());

 if (port.getWsdlPort() != null) {
 portInfo.setWsdlPort(port.getWsdlPort().getValue());

Modified: geronimo/server/trunk/modules/geronimo-cxf/pom.xml
URL: 
http://svn.apache.org/viewvc/geronimo/server/trunk/modules/geronimo-cxf/pom.xml?view=diff&rev=501215&r1=501214&r2=501215
==
--- geronimo/server/trunk/modules/geronimo-cxf/pom.xml (original)
+++ geronimo/server/trunk/modules/geronimo-cxf/pom.xml Mon Jan 29 14:51:09 2007
@@ -53,6 +53,12 @@
 

 
+org.apache.geronimo.modules
+geronimo-jaxws
+${version}
+
+
+
 org.apache.cxf
 cxf-rt-frontend-jaxws
 

Modified: 
geronimo/s

Re: svn commit: r501232 - /geronimo/server/trunk/modules/geronimo-jaxws/pom.xml

[Davanum Srinivas]

Jarek,

You remember the discussion we had about using jaxws api jar and saaj
api jar from axis2. We need this for that. I believe there is a JIRA
item as well regarding getting rid of sun's jars.

-- dims



On 1/29/07, Jarek Gawor <[EMAIL PROTECTED]> wrote:

Why is that needed here?

Jarek

On 1/29/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Author: dims
> Date: Mon Jan 29 15:33:49 2007
> New Revision: 501232
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=501232
> Log:
> oops! add missing repo
>
> Modified:
> geronimo/server/trunk/modules/geronimo-jaxws/pom.xml
>
> Modified: geronimo/server/trunk/modules/geronimo-jaxws/pom.xml
> URL: 
http://svn.apache.org/viewvc/geronimo/server/trunk/modules/geronimo-jaxws/pom.xml?view=diff&rev=501232&r1=501231&r2=501232
> ==
> --- geronimo/server/trunk/modules/geronimo-jaxws/pom.xml (original)
> +++ geronimo/server/trunk/modules/geronimo-jaxws/pom.xml Mon Jan 29 15:33:49 
2007
> @@ -32,6 +32,23 @@
>  geronimo-jaxws
>  Geronimo :: JAXWS
>
> +
> +
> +maven-repo1
> +maven official repo
> +http://repo1.maven.org/maven/
> +legacy
> +
> +
> +
> +true
> +
> +ws-zones
> +ws.zones maven repository
> +http://ws.zones.apache.org/repository/
> +legacy
> +
> +
>  
>
>  
>
>
>




--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers