[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjms-developer
Subject:    [openjms-developer] [ openjms-Bugs-667126 ] Multiple connectors cannot be used at the same time
From:       "SourceForge.net" <noreply () sourceforge ! net>
Date:       2003-05-13 21:44:45
[Download RAW message or body]

Bugs item #667126, was opened at 2003-01-13 12:31
Message generated for change (Comment added) made by tanderson
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=667126&group_id=54559

Category: transport
Group: v0.7.4
>Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Tim Anderson (tanderson)
Assigned to: Jim Alateras (jalateras)
Summary: Multiple connectors cannot be used at the same time

Initial Comment:
The OpenJMS server doesn't allow multiple 
connectors to be configured at the same time as 
binding is handled by the singleton JndiServerIfc 
implementation, rather than on a per-connector 
basis.

This has been partially solved on the  
tima_dev_0_7_3 branch, but as the messenger 
component is soon to be made obsolete, the 
changes aren't worth merging back.

----------------------------------------------------------------------

>Comment By: Tim Anderson (tanderson)
Date: 2003-05-13 21:44

Message:
Logged In: YES 
user_id=557161

Closing this. Multiple connector support is available in 
the 0.7.5 release.

----------------------------------------------------------------------

Comment By: Tim Anderson (tanderson)
Date: 2003-03-11 13:39

Message:
Logged In: YES 
user_id=557161

Fixed in CVS. The change will be available in the 0.7.5 
release.

In order to configure multiple connectors, simply add a 
<Connector> entry for each desired connector. Note 
that each connection factory must have a different name 
e.g, to configure tcp and rmi:

  <Connectors>
    <Connector scheme="rmi">
      <ConnectionFactories>
        <QueueConnectionFactory 
name="RMIQueueConnectionFactory" />
        <TopicConnectionFactory 
name="RMITopicConnectionFactory" />
      </ConnectionFactories>
    </Connector>
    <Connector scheme="tcp">
      <ConnectionFactories>
        <QueueConnectionFactory 
name="TCPQueueConnectionFactory" />
        <TopicConnectionFactory 
name="TCPTopicConnectionFactory" />
      </ConnectionFactories>
    </Connector>
  </Connectors>
 

 

----------------------------------------------------------------------

Comment By: Jim Alateras (jalateras)
Date: 2003-01-24 21:11

Message:
Logged In: YES 
user_id=28602

yes we will have a look at it after we release 0.7.4

----------------------------------------------------------------------

Comment By: Raicho Minev (raicho)
Date: 2003-01-24 16:49

Message:
Logged In: YES 
user_id=696098

I found out some interesting behaviour connected to using 
multiple connection schemas.

If you start the OpenJMS server with say "embedded" 
schema, it stores its jndi names into the database. After 
running the server, you can change the schema to "tcp". After 
that you will be able to lookup from both schemas as if they 
are both active.

This works because the embedded jndi does not need any 
connection resources, so the database contets is just 
enough.

However tihs approach is not very good, because every time 
you delete the database you will need to repeat the steps 
above.

Also this behaviour might be taken into consideration for 
future releases, because the fact that jndi names from old 
configurations are left in database might lead client 
applications use the wrong bindings.

Raicho Minev.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=667126&group_id=54559


-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

_______________________________________________
openjms-developer mailing list
openjms-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openjms-developer
[prev in list] [next in list] [prev in thread] [next in thread]