[JBoss-dev] CVS update: jbossmq/src/etc/conf/default jbossmq-service.xml
User: chirino Date: 02/03/08 22:11:47 Modified:src/etc/conf/default jbossmq-service.xml Log: Added a EnableTcpNoDelay option to the UIL and OIL mbeans. Revision ChangesPath 1.21 +3 -1 jbossmq/src/etc/conf/default/jbossmq-service.xml Index: jbossmq-service.xml === RCS file: /cvsroot/jboss/jbossmq/src/etc/conf/default/jbossmq-service.xml,v retrieving revision 1.20 retrieving revision 1.21 diff -u -r1.20 -r1.21 --- jbossmq-service.xml 6 Mar 2002 17:29:23 - 1.20 +++ jbossmq-service.xml 9 Mar 2002 06:11:47 - 1.21 @@ -1,6 +1,6 @@ - + @@ -145,6 +145,7 @@ XAConnectionFactory 8090 6 +true UILXAConnectionFactory 8091 6 +true ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbossmq/src/etc/conf/default jbossmq-service.xml jbossmq-state.xml jbossmq-testsuite-service.xml
User: pra Date: 02/03/06 09:29:23 Modified:src/etc/conf/default jbossmq-service.xml jbossmq-state.xml jbossmq-testsuite-service.xml Log: Configuration updated to support new security architecture Revision ChangesPath 1.20 +24 -6 jbossmq/src/etc/conf/default/jbossmq-service.xml Index: jbossmq-service.xml === RCS file: /cvsroot/jboss/jbossmq/src/etc/conf/default/jbossmq-service.xml,v retrieving revision 1.19 retrieving revision 1.20 diff -u -r1.19 -r1.20 --- jbossmq-service.xml 13 Feb 2002 04:17:06 - 1.19 +++ jbossmq-service.xml 6 Mar 2002 17:29:23 - 1.20 @@ -1,6 +1,6 @@ - + @@ -14,6 +14,16 @@ jboss.mq:service=StateManager + + jboss.mq:service=Server + jboss.mq:service=SecurityManager + + + + + - +jbossmq-oldstate.xml + +--> + + jbossmq-state.xml @@ -107,7 +124,7 @@ -jboss.mq:service=Server +jboss.mq:service=SecurityAdapter java:/ConnectionFactory java:/XAConnectionFactory 0 @@ -115,7 +132,7 @@ -jboss.mq:service=Server +jboss.mq:service=SecurityAdapter RMIConnectionFactory RMIXAConnectionFactory 6 @@ -123,7 +140,7 @@ -jboss.mq:service=Server +jboss.mq:service=SecurityAdapter ConnectionFactory XAConnectionFactory 8090 @@ -132,7 +149,7 @@ -jboss.mq:service=Server +jboss.mq:service=SecurityAdapter UILConnectionFactory UILXAConnectionFactory 8091 @@ -148,6 +165,7 @@ jboss.mq:service=Server + jboss.mq:service=SecurityManager 1.3 +41 -21jbossmq/src/etc/conf/default/jbossmq-state.xml Index: jbossmq-state.xml === RCS file: /cvsroot/jboss/jbossmq/src/etc/conf/default/jbossmq-state.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- jbossmq-state.xml 13 Feb 2002 04:17:06 - 1.2 +++ jbossmq-state.xml 6 Mar 2002 17:29:23 - 1.3 @@ -1,24 +1,44 @@ - - - - - - - - - - - - guest - guest - - - - john - needle - DurableSubscriberExample - + + + john + needle + DurableSubscriberExample + + + guest + guest + + + nobody + nobody + + + dynsub + dynsub + + + + + guest + john + + + john + + + john + dynsub + + + john + dynsub + + + nobody + + + + - 1.2 +46 -2 jbossmq/src/etc/conf/default/jbossmq-testsuite-service.xml Index: jbossmq-testsuite-service.xml === RCS file: /cvsroot/jboss/jbossmq/src/etc/conf/default/jbossmq-testsuite-service.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- jbossmq-testsuite-service.xml 13 Feb 2002 04:17:06 - 1.1 +++ jbossmq-testsuite-service.xml 6 Mar 2002 17:29:23 - 1.2 @@ -1,6 +1,6 @@ - + - + jboss.mq:service=Server +jboss.mq:service=SecurityManager + + + + + + + + + + +jboss.mq:service=Server +jboss.mq:service=SecurityManager + + + + + + + +jboss.mq:service=Server +jboss.mq:service=SecurityManager + + + + + + + + + jboss.mq:service=Server +jboss.mq:service=SecurityManager + + + + + + + ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbossmq/src/etc/conf/default jbossmq-service.xml
User: mnf999 Date: 02/01/20 07:07:18 Modified:src/etc/conf/default jbossmq-service.xml Log: Revision ChangesPath 1.18 +5 -5 jbossmq/src/etc/conf/default/jbossmq-service.xml Index: jbossmq-service.xml === RCS file: /cvsroot/jboss/jbossmq/src/etc/conf/default/jbossmq-service.xml,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- jbossmq-service.xml 2002/01/03 04:00:53 1.17 +++ jbossmq-service.xml 2002/01/20 15:07:18 1.18 @@ -6,14 +6,14 @@ - + - + + - + + ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbossmq/src/etc/conf/default jbossmq-service.xml
User: user57
Date: 02/01/02 20:00:53
Modified:src/etc/conf/default jbossmq-service.xml
Log:
o migrated all components to a new JMX domain name model. jboss.system
is now where to core/spine components live. moved all components that
were in JBOSS-SYSTEM that did not move into a jboss.* domain into
jboss (where the server is now registered). The point was to limit the
members of jboss.system to core bits only.
o Created org.jboss.system.Server, which does the work of initialization
that org.jboss.Main used to do. Main now only parses the command line,
sets up basic legecy properties and creates a Server instance.
o Moved functionality of Shutdown (component not cl tool) into Server (
which is bound as jboss.system:service=Server)
o Moved more Runtime access from Info into Server. Exposed memory info
as attributes.
o Logging a WARN everywhere that uses System.getProperty("jboss.system.home")
as that should go away soon/eventually.
o Initialized the invokerMap in the harmi impl to avoid NPE
o Made getopt.jar a member of the lib/* dir instead of adding it to the
run.jar and shutdown.jars each time.
o Minor cosmetic changes along the way.
Revision ChangesPath
1.17 +49 -52jbossmq/src/etc/conf/default/jbossmq-service.xml
Index: jbossmq-service.xml
===
RCS file: /cvsroot/jboss/jbossmq/src/etc/conf/default/jbossmq-service.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- jbossmq-service.xml 2001/12/18 21:30:50 1.16
+++ jbossmq-service.xml 2002/01/03 04:00:53 1.17
@@ -1,19 +1,16 @@
-
-
+
-
+ | This contains the default configuration of jbossmq
+ -->
@@ -23,9 +20,9 @@
-JBossMQ:service=PersistenceManager
-JBossMQ:service=StateManager
+ name="jboss.mq:service=Server">
+jboss.mq:service=PersistenceManager
+jboss.mq:service=StateManager
+ name="jboss.mq:service=MessageCache">
500
600
-JBossMQ:service=CacheStore
+jboss.mq:service=CacheStore
+ name="jboss.mq:service=CacheStore">
tmp/jbossmq
@@ -58,15 +55,15 @@
| For example: what durable subscriptions are active.
-->
+ name="jboss.mq:service=StateManager">
conf/default/jbossmq-state.xml
+ name="jboss.mq:service=PersistenceManager">
db/jbossmq/file/
-JBossMQ:service=MessageCache
+jboss.mq:service=MessageCache
-JBossMQ:service=Server
+ name="jboss.mq:service=InvocationLayer,type=JVM">
+jboss.mq:service=Server
java:/ConnectionFactory
java:/XAConnectionFactory
0
-JBossMQ:service=Server
+ name="jboss.mq:service=InvocationLayer,type=RMI">
+jboss.mq:service=Server
RMIConnectionFactory
RMIXAConnectionFactory
6
-JBossMQ:service=Server
+ name="jboss.mq:service=InvocationLayer,type=OIL">
+jboss.mq:service=Server
ConnectionFactory
XAConnectionFactory
8090
@@ -139,8 +136,8 @@
-JBossMQ:service=Server
+ name="jboss.mq:service=InvocationLayer,type=UIL">
+jboss.mq:service=Server
UILConnectionFactory
UILXAConnectionFactory
8091
@@ -153,16 +150,16 @@
| testTopic, example, bob
-->
-JBossMQ:service=Server
+ name="jboss.mq.destination:service=Topic,name=testTopic">
+jboss.mq:service=Server
-JBossMQ:service=Server
+ name="jboss.mq.destination:service=Topic,name=example">
+jboss.mq:service=Server
-JBossMQ:service=Server
+ name="jboss.mq.destination:service=Topic,name=bob">
+jboss.mq:service=Server
-JBossMQ:service=Server
+ name="jboss.mq.destination:service=Queue,name=testQueue">
+jboss.mq:service=Server
-JBossMQ:service=Server
+ name="jboss.mq.destination:service=Queue,name=controlQueue">
+jboss.mq:service=Server
-JBossMQ:service=Server
+ name="jboss.mq.destination:service=Queue,name=A">
+jboss.mq:service=Server
-JBossMQ:service=Server
+ name="jboss.mq.destination:service=Queue,name=B">
+jboss.mq:service=Server
-JBossMQ:service=Server
+ name="jboss.mq.destination:service=Queue,name=C">
+jboss.mq:service=Server
-JBossMQ:service=Server
+ name="jboss.mq.destination:service=Queue,name=D">
+jboss.mq:service=Server
-JBossMQ:service=Server
+ name="jboss.mq.destination:service=Queue,name=E">
+jboss.mq
[JBoss-dev] CVS update: jbossmq/src/etc/conf/default jbossmq-service.xml
User: mnf999 Date: 01/12/18 13:30:53 Modified:src/etc/conf/default jbossmq-service.xml Log: depends and attribute for mbean to mbean dependency Revision ChangesPath 1.16 +24 -24jbossmq/src/etc/conf/default/jbossmq-service.xml Index: jbossmq-service.xml === RCS file: /cvsroot/jboss/jbossmq/src/etc/conf/default/jbossmq-service.xml,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- jbossmq-service.xml 2001/11/14 04:23:26 1.15 +++ jbossmq-service.xml 2001/12/18 21:30:50 1.16 @@ -7,7 +7,7 @@ - + -JBossMQ:service=Server +JBossMQ:service=Server java:/ConnectionFactory java:/XAConnectionFactory 0 @@ -123,7 +123,7 @@ -JBossMQ:service=Server +JBossMQ:service=Server RMIConnectionFactory RMIXAConnectionFactory 6 @@ -131,7 +131,7 @@ -JBossMQ:service=Server +JBossMQ:service=Server ConnectionFactory XAConnectionFactory 8090 @@ -140,7 +140,7 @@ -JBossMQ:service=Server +JBossMQ:service=Server UILConnectionFactory UILXAConnectionFactory 8091 @@ -154,15 +154,15 @@ --> -JBossMQ:service=Server +JBossMQ:service=Server -JBossMQ:service=Server +JBossMQ:service=Server -JBossMQ:service=Server +JBossMQ:service=Server -JBossMQ:service=Server +JBossMQ:service=Server -JBossMQ:service=Server +JBossMQ:service=Server -JBossMQ:service=Server +JBossMQ:service=Server -JBossMQ:service=Server +JBossMQ:service=Server -JBossMQ:service=Server +JBossMQ:service=Server -JBossMQ:service=Server +JBossMQ:service=Server -JBossMQ:service=Server +JBossMQ:service=Server -JBossMQ:service=Server +JBossMQ:service=Server -JBossMQ:service=Server +JBossMQ:service=Server -JBossMQ:service=Server +JBossMQ:service=Server ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbossmq/src/etc/conf/default jbossmq-service.xml
User: chirino Date: 01/11/13 20:23:27 Modified:src/etc/conf/default jbossmq-service.xml Log: Factored out a CacheStore object from the message store. This should lay the ground work needed so that the MessageCache can use a PM for saving and loading messages. Also fixed a small bug in the file PM. It was not properly restoring the message after a server restart. Revision ChangesPath 1.15 +10 -1 jbossmq/src/etc/conf/default/jbossmq-service.xml Index: jbossmq-service.xml === RCS file: /cvsroot/jboss/jbossmq/src/etc/conf/default/jbossmq-service.xml,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- jbossmq-service.xml 2001/11/12 17:00:26 1.14 +++ jbossmq-service.xml 2001/11/14 04:23:26 1.15 @@ -7,7 +7,7 @@ - + + tmp/jbossmq ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] CVS update: jbossmq/src/etc/conf/default jbossmq-service.xml
That's a very good point. I am glad you've explained it. I have reverted my changes to MessageLog (i.e. remove the commit() call) and use the NoTransDS in the xml file. I have add some comments to the XML file in case anyone wonder. Thanks! Charles --- David Jencks <[EMAIL PROTECTED]> wrote: > Calling Connection.commit() would work fine in a > non-managed environment > where the connections from the datasource are not > under tm control. > However, since the connections from DefaultDS ARE > under tm control, you are > inviting disaster by calling commit on it by hand. > In fact, if you are > using DefaultDS for something else from the same ejb > as you used jms from, > such as some BMP, you will get the same connection > as you used with the BMP > work, and will be committing that work too! > > I think with the separate transaction handling in > jdbc pm, the best bet is > to have a separate no-trans datasource and leave the > connections > autocommit. This does work (sort of), doesn't > interfere with other uses of > the datasource, and avoids needing to call commit() > so often. > > Longer term, I think we need a better implementation > of jdbc pm, that > relies on the database's transaction management. > I have been thinking a > little bit about this, and think that the best way > may be to modify the PM > interface to expose a XAResource: for the jdbc PM > this would be the > XAResource from the (jca-wrapped) jdbc driver. > Since the current jdbc > implementation doesn't actually support any kind of > transactional recovery, > I don't have a big problem insisting that the jdbc > pm be based on a > xa-capable driver. > > Also, I think calling any of the pm's xa capable is > a bit excessive at this > point since none implement a recover method on the > exposed XAResource. > > Glad you like the mbean-ref's. I thought they were > pretty neat too. I'd > still like to get rid of the remaining static > methods in JMSServer -- I > want to be able to have many running at once, at > least so we can test all > the pm's > > Thanks! > david jencks > > On 2001.11.11 22:14:03 -0500 Charles Chan wrote: > > Hi, David, > > > > I think JDBC PM relies on MessageLog to commit its > > changes on each method call. I didn't change this. > In > > fact, I made JDBC MessageLog to conform to this by > > calling Connection.commit() after each update SQL > > statement is executed. > > > > Also, if your JMS Session is transacted and if you > > didn't call Session.commit(), the PM will not be > > invoked. So, db transactions are not performed > until > > Session.commit() is called. > > > > Please correct me if I am wrong. I did test my > changes > > with a combination of transacted/non-transacted > > sessions with Queue senders and receivers. > > > > Thanks! > > Charles > > > > Btw, your mbean-ref changes are really cool. :) > Save > > me a lot of time! > > > > > > --- David Jencks <[EMAIL PROTECTED]> > > wrote: > > > Are you really sure this change is correct? I > have > > > been told that the jdbc > > > pm RELIES on unmanaged connections with > autocommit = > > > true. That is why I > > > created the NoTransDS and used it here. There > is no > > > appropriate > > > transaction control from the container that I > can > > > discern. > > > > > > I believe with TM-managed transactions on a > > > datasource used in jdbc - pm > > > there is an at least 50% chance that the jdbc > > > DataSource XAResource (or > > > local transaction) will get commit called before > the > > > jms-xa XAResource gets > > > commit called - so the db transaction will be > > > comitted before all the > > > end-of-transaction work can be done. > > > > > > david jencks > > > > > > On 2001.11.11 14:43:33 -0500 Charles Chan wrote: > > > > User: charles_chan > > > > Date: 01/11/11 11:43:33 > > > > > > > > Modified:src/etc/conf/default > > > jbossmq-service.xml > > > > Log: > > > > - minor changes to JDBC PM configuration and > > > remove extraneous spaces. > > > > > > > > Revision ChangesPath > > > > 1.10 +28 -21 > > > jbossmq/src/etc/conf/default/jbossmq-service.xml > > > > > > > > Index: jbossmq-service.xml > > > > > > > > > > === > > > > RCS file: > > > > > > /cvsroot/jboss/jbossmq/src/etc/conf/default/jbossmq-service.xml,v > > > > retrieving revision 1.9 > > > > retrieving revision 1.10 > > > > diff -u -r1.9 -r1.10 > > > > --- jbossmq-service.xml 2001/11/10 21:38:03 > 1.9 > > > > +++ jbossmq-service.xml 2001/11/11 19:43:33 > 1.10 > > > > @@ -7,9 +7,9 @@ > > > > > > > > > > > > > > > > - > > > > + > > > > > > > > - > > > | THis contains the default > configuration > > > of jbossmq > > > > | > > > > --> > > > > @@ -33,28 +33,28 @@ > > > > > > > > > name="PersistenceManager">JBossMQ:service=PersistenceManager > > > > > > > > > name="StateManager"
[JBoss-dev] CVS update: jbossmq/src/etc/conf/default jbossmq-service.xml
User: charles_chan Date: 01/11/12 09:00:29 Modified:src/etc/conf/default jbossmq-service.xml Log: - use NoTransDS for JMS datasource Revision ChangesPath 1.14 +7 -3 jbossmq/src/etc/conf/default/jbossmq-service.xml Index: jbossmq-service.xml === RCS file: /cvsroot/jboss/jbossmq/src/etc/conf/default/jbossmq-service.xml,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- jbossmq-service.xml 2001/11/12 03:34:08 1.13 +++ jbossmq-service.xml 2001/11/12 17:00:26 1.14 @@ -7,7 +7,7 @@ - +
Re: [JBoss-dev] CVS update: jbossmq/src/etc/conf/default jbossmq-service.xml
Calling Connection.commit() would work fine in a non-managed environment where the connections from the datasource are not under tm control. However, since the connections from DefaultDS ARE under tm control, you are inviting disaster by calling commit on it by hand. In fact, if you are using DefaultDS for something else from the same ejb as you used jms from, such as some BMP, you will get the same connection as you used with the BMP work, and will be committing that work too! I think with the separate transaction handling in jdbc pm, the best bet is to have a separate no-trans datasource and leave the connections autocommit. This does work (sort of), doesn't interfere with other uses of the datasource, and avoids needing to call commit() so often. Longer term, I think we need a better implementation of jdbc pm, that relies on the database's transaction management.I have been thinking a little bit about this, and think that the best way may be to modify the PM interface to expose a XAResource: for the jdbc PM this would be the XAResource from the (jca-wrapped) jdbc driver. Since the current jdbc implementation doesn't actually support any kind of transactional recovery, I don't have a big problem insisting that the jdbc pm be based on a xa-capable driver. Also, I think calling any of the pm's xa capable is a bit excessive at this point since none implement a recover method on the exposed XAResource. Glad you like the mbean-ref's. I thought they were pretty neat too. I'd still like to get rid of the remaining static methods in JMSServer -- I want to be able to have many running at once, at least so we can test all the pm's Thanks! david jencks On 2001.11.11 22:14:03 -0500 Charles Chan wrote: > Hi, David, > > I think JDBC PM relies on MessageLog to commit its > changes on each method call. I didn't change this. In > fact, I made JDBC MessageLog to conform to this by > calling Connection.commit() after each update SQL > statement is executed. > > Also, if your JMS Session is transacted and if you > didn't call Session.commit(), the PM will not be > invoked. So, db transactions are not performed until > Session.commit() is called. > > Please correct me if I am wrong. I did test my changes > with a combination of transacted/non-transacted > sessions with Queue senders and receivers. > > Thanks! > Charles > > Btw, your mbean-ref changes are really cool. :) Save > me a lot of time! > > > --- David Jencks <[EMAIL PROTECTED]> > wrote: > > Are you really sure this change is correct? I have > > been told that the jdbc > > pm RELIES on unmanaged connections with autocommit = > > true. That is why I > > created the NoTransDS and used it here. There is no > > appropriate > > transaction control from the container that I can > > discern. > > > > I believe with TM-managed transactions on a > > datasource used in jdbc - pm > > there is an at least 50% chance that the jdbc > > DataSource XAResource (or > > local transaction) will get commit called before the > > jms-xa XAResource gets > > commit called - so the db transaction will be > > comitted before all the > > end-of-transaction work can be done. > > > > david jencks > > > > On 2001.11.11 14:43:33 -0500 Charles Chan wrote: > > > User: charles_chan > > > Date: 01/11/11 11:43:33 > > > > > > Modified:src/etc/conf/default > > jbossmq-service.xml > > > Log: > > > - minor changes to JDBC PM configuration and > > remove extraneous spaces. > > > > > > Revision ChangesPath > > > 1.10 +28 -21 > > jbossmq/src/etc/conf/default/jbossmq-service.xml > > > > > > Index: jbossmq-service.xml > > > > > > === > > > RCS file: > > > /cvsroot/jboss/jbossmq/src/etc/conf/default/jbossmq-service.xml,v > > > retrieving revision 1.9 > > > retrieving revision 1.10 > > > diff -u -r1.9 -r1.10 > > > --- jbossmq-service.xml 2001/11/10 21:38:03 1.9 > > > +++ jbossmq-service.xml 2001/11/11 19:43:33 1.10 > > > @@ -7,9 +7,9 @@ > > > > > > > > > > > > - > > > + > > > > > > - > > | THis contains the default configuration > > of jbossmq > > > | > > > --> > > > @@ -33,28 +33,28 @@ > > > > > name="PersistenceManager">JBossMQ:service=PersistenceManager > > > > > name="StateManager">JBossMQ:service=StateManager > > > > > > - > > > - > > | The MessageCache decides where to put > > JBossMQ message that > > > | are sitting around waiting to be > > consumed by a client. > > > | > > > | The memory marks are in Megabytes. Once > > the JVM memory usage > > > hits > > > | the high memory mark, the old messages > > in the cache will start > > > getting > > > - | stored in the DataDirectory. As memory > > usage gets closer to > > > the > > > + | stored in the DataDirectory. As memory > > usage gets closer to > > > the > > > |
[JBoss-dev] CVS update: jbossmq/src/etc/conf/default jbossmq-service.xml
User: d_jencks Date: 01/11/10 13:38:04 Modified:src/etc/conf/default jbossmq-service.xml Log: Changed mbean dependencies to work directly by mbean-references: eliminated depends tag from *service.xml files Revision ChangesPath 1.9 +58 -25jbossmq/src/etc/conf/default/jbossmq-service.xml Index: jbossmq-service.xml === RCS file: /cvsroot/jboss/jbossmq/src/etc/conf/default/jbossmq-service.xml,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- jbossmq-service.xml 2001/11/09 06:26:37 1.8 +++ jbossmq-service.xml 2001/11/10 21:38:03 1.9 @@ -7,23 +7,16 @@ - + - JBOSS-SYSTEM:service=Naming + name="JBossMQ:service=Server"> +JBossMQ:service=PersistenceManager +JBossMQ:service=StateManager + -db/jbossmq/ +db/jbossmq/file/ +JBossMQ:service=MessageCache + + +JBossMQ:service=Server java:/ConnectionFactory java:/XAConnectionFactory 0 @@ -82,6 +86,7 @@ +JBossMQ:service=Server RMIConnectionFactory RMIXAConnectionFactory 6 @@ -89,6 +94,7 @@ +JBossMQ:service=Server ConnectionFactory XAConnectionFactory 8090 @@ -97,6 +103,7 @@ +JBossMQ:service=Server UILConnectionFactory UILXAConnectionFactory 8091 @@ -120,11 +127,17 @@ | testTopic, example, bob --> + name="JBossMQ:service=Topic,name=testTopic"> +JBossMQ:service=Server + + name="JBossMQ:service=Topic,name=example"> +JBossMQ:service=Server + + name="JBossMQ:service=Topic,name=bob"> +JBossMQ:service=Server + + name="JBossMQ:service=Queue,name=testQueue"> +JBossMQ:service=Server + + name="JBossMQ:service=Queue,name=controlQueue"> +JBossMQ:service=Server + + name="JBossMQ:service=Queue,name=A"> +JBossMQ:service=Server + + name="JBossMQ:service=Queue,name=B"> +JBossMQ:service=Server + + name="JBossMQ:service=Queue,name=C"> +JBossMQ:service=Server + + name="JBossMQ:service=Queue,name=D"> +JBossMQ:service=Server + + name="JBossMQ:service=Queue,name=E"> +JBossMQ:service=Server + + name="JBossMQ:service=Queue,name=F"> +JBossMQ:service=Server + + name="JBossMQ:service=Queue,name=ex"> +JBossMQ:service=Server + + name="JBossMQ:service=Queue,name=DLQ"> +JBossMQ:service=Server + ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] CVS update: jbossmq/src/etc/conf/default jbossmq-service.xml
Hiram, I am jumping up and down here in excitement. Is this really what it look like: a first cut of a clustered JBossMQ? Tell me its true. //Peter On 8 Nov, Hiram Chirino wrote: > User: chirino > Date: 01/11/08 22:26:37 > > Modified:src/etc/conf/default jbossmq-service.xml > Log: > Created a new JBossMQ IL that uses the HA framework. > > Revision ChangesPath > 1.8 +15 -2 jbossmq/src/etc/conf/default/jbossmq-service.xml > > Index: jbossmq-service.xml > === > RCS file: /cvsroot/jboss/jbossmq/src/etc/conf/default/jbossmq-service.xml,v > retrieving revision 1.7 > retrieving revision 1.8 > diff -u -r1.7 -r1.8 > --- jbossmq-service.xml 2001/10/28 01:27:00 1.7 > +++ jbossmq-service.xml 2001/11/09 06:26:37 1.8 > @@ -7,7 +7,7 @@ > > > > - > + > > > @@ -100,6 +102,17 @@ >8091 >6 > > + > + > + > >
[JBoss-dev] CVS update: jbossmq/src/etc/conf/default jbossmq-service.xml
User: chirino Date: 01/11/08 22:26:37 Modified:src/etc/conf/default jbossmq-service.xml Log: Created a new JBossMQ IL that uses the HA framework. Revision ChangesPath 1.8 +15 -2 jbossmq/src/etc/conf/default/jbossmq-service.xml Index: jbossmq-service.xml === RCS file: /cvsroot/jboss/jbossmq/src/etc/conf/default/jbossmq-service.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- jbossmq-service.xml 2001/10/28 01:27:00 1.7 +++ jbossmq-service.xml 2001/11/09 06:26:37 1.8 @@ -7,7 +7,7 @@ - + @@ -100,6 +102,17 @@ 8091 6 + + +
[JBoss-dev] CVS update: jbossmq/src/etc/conf/default jbossmq-service.xml
User: chirino Date: 01/10/27 18:27:00 Modified:src/etc/conf/default jbossmq-service.xml Log: Commiting my initial implementation of a message cache for the JBossMQ messages. This should allow the server to scale so it can hold a larger number of message. Revision ChangesPath 1.7 +17 -1 jbossmq/src/etc/conf/default/jbossmq-service.xml Index: jbossmq-service.xml === RCS file: /cvsroot/jboss/jbossmq/src/etc/conf/default/jbossmq-service.xml,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- jbossmq-service.xml 2001/10/21 05:38:12 1.6 +++ jbossmq-service.xml 2001/10/28 01:27:00 1.7 @@ -7,7 +7,7 @@ - + + +500 +600 +tmp/jbossmq +
[JBoss-dev] CVS update: jbossmq/src/etc/conf/default jbossmq-service.xml
User: chirino Date: 01/10/20 22:38:12 Modified:src/etc/conf/default jbossmq-service.xml Log: Feature add: You can now setup a JBossMQ connection with out using JNDI. The ConnectionTestCase has a test case in case your interested on how it is done. Revision ChangesPath 1.6 +3 -3 jbossmq/src/etc/conf/default/jbossmq-service.xml Index: jbossmq-service.xml === RCS file: /cvsroot/jboss/jbossmq/src/etc/conf/default/jbossmq-service.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- jbossmq-service.xml 2001/09/27 04:21:25 1.5 +++ jbossmq-service.xml 2001/10/21 05:38:12 1.6 @@ -7,7 +7,7 @@ - +
[JBoss-dev] CVS update: jbossmq/src/etc/conf/default jbossmq-service.xml
User: chirino Date: 01/09/26 21:21:25 Modified:src/etc/conf/default jbossmq-service.xml Log: Re-enabled an old feature we used to have: we can now set the ports that the UIL and OIL services bind to via MBean Revision ChangesPath 1.5 +3 -1 jbossmq/src/etc/conf/default/jbossmq-service.xml Index: jbossmq-service.xml === RCS file: /cvsroot/jboss/jbossmq/src/etc/conf/default/jbossmq-service.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- jbossmq-service.xml 2001/09/27 03:27:42 1.4 +++ jbossmq-service.xml 2001/09/27 04:21:25 1.5 @@ -7,7 +7,7 @@ - +
[JBoss-dev] CVS update: jbossmq/src/etc/conf/default jbossmq-service.xml
User: chirino Date: 01/09/26 20:27:42 Modified:src/etc/conf/default jbossmq-service.xml Log: Due to popular demand the PingThread is now shared by all the connections in one VM. And the the ping period is configurable at each ConnectionFactory. Revision ChangesPath 1.4 +5 -1 jbossmq/src/etc/conf/default/jbossmq-service.xml Index: jbossmq-service.xml === RCS file: /cvsroot/jboss/jbossmq/src/etc/conf/default/jbossmq-service.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- jbossmq-service.xml 2001/09/11 03:05:26 1.3 +++ jbossmq-service.xml 2001/09/27 03:27:42 1.4 @@ -7,7 +7,7 @@ - +
[JBoss-dev] CVS update: jbossmq/src/etc/conf/default jbossmq-service.xml
User: dmaplesden Date: 01/09/10 20:05:26 Modified:src/etc/conf/default jbossmq-service.xml Log: Altered configuration to work with new deployment mechanism Revision ChangesPath 1.3 +4 -59 jbossmq/src/etc/conf/default/jbossmq-service.xml Index: jbossmq-service.xml === RCS file: /cvsroot/jboss/jbossmq/src/etc/conf/default/jbossmq-service.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- jbossmq-service.xml 2001/09/09 05:40:47 1.2 +++ jbossmq-service.xml 2001/09/11 03:05:26 1.3 @@ -7,7 +7,7 @@ - + @@ -116,60 +116,5 @@ name="JBossMQ:service=Queue,name=ex"/> - - - -DefaultJMSProvider - - org.jboss.jms.jndi.JBossMQProvider - -java:/XAConnectionFactory -java:/XAConnectionFactory - - - - -StdJMSPool - - org.jboss.jms.asf.StdServerSessionPoolFactory - - - - - -JmsXA -JCA:service=RARDeployer -JMS Adapter -MinervaXACMFactory - - # Pool type - uncomment to force, otherwise it is the default - #PoolConfiguration=per-factory - - # Connection pooling properties - see - # org.jboss.resource.connectionmanager.PoolParameters - MinSize=0 - MaxSize=10 - BlockingTimeoutMillis=5000 - CleanupEnabled=false - IdleTimeoutEnabled=false - InvalidateOnError=false - TrackLastUsed=false - GCIntervalMillis=12 - GCMinIdleMillis=120 - IdleTimeoutMillis=180 - MaxIdleTimeoutPercent=1.0 - - - - org.jboss.resource.security.ManyToOnePrincipalMapping - - - - - - ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbossmq/src/etc/conf/default jbossmq-service.xml
User: d_jencks Date: 01/09/08 22:40:47 Modified:src/etc/conf/default jbossmq-service.xml Log: added missing hsql-default-service.xml and a couple of fixes. Revision ChangesPath 1.2 +2 -2 jbossmq/src/etc/conf/default/jbossmq-service.xml Index: jbossmq-service.xml === RCS file: /cvsroot/jboss/jbossmq/src/etc/conf/default/jbossmq-service.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- jbossmq-service.xml 2001/09/08 19:32:22 1.1 +++ jbossmq-service.xml 2001/09/09 05:40:47 1.2 @@ -7,7 +7,7 @@ - + -jbossmq-state.xml +conf/default/jbossmq-state.xml ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbossmq/src/etc/conf/default jbossmq-service.xml
User: d_jencks Date: 01/09/08 12:32:22 Added: src/etc/conf/default jbossmq-service.xml Log: Reorganized connector packaging under connector (from pool), made jca stuff into a sar, made default hypsersonic DefaultDS into hsql-default-service.xml, and made jbossmq into jbossmq-service.xml Revision ChangesPath 1.1 jbossmq/src/etc/conf/default/jbossmq-service.xml Index: jbossmq-service.xml === jbossmq-state.xml db/jbossmq/ java:/ConnectionFactory java:/XAConnectionFactory RMIConnectionFactory RMIXAConnectionFactory ConnectionFactory XAConnectionFactory UILConnectionFactory UILXAConnectionFactory DefaultJMSProvider org.jboss.jms.jndi.JBossMQProvider java:/XAConnectionFactory java:/XAConnectionFactory StdJMSPool org.jboss.jms.asf.StdServerSessionPoolFactory JmsXA JCA:service=RARDeployer JMS Adapter MinervaXACMFactory # Pool type - uncomment to force, otherwise it is the default #PoolConfiguration=per-factory # Connection pooling properties - see # org.jboss.resource.connectionmanager.PoolParameters MinSize=0 MaxSize=10 BlockingTimeoutMillis=5000 CleanupEnabled=false IdleTimeoutEnabled=false InvalidateOnError=false TrackLastUsed=false GCIntervalMillis=12 GCMinIdleMillis=120 IdleTimeoutMillis=180 MaxIdleTimeoutPercent=1.0 org.jboss.resource.security.ManyToOnePrincipalMapping ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
