Hi,
I just have to give my 2 cent on this (but it IS just 2 cents).
First a question: is there any one doing any work in this area among
JBoss developers? I have seen nothing on dev or in cvs on it (except the
old Zoap support).
I have been waiting on the JAXM spec for some time, wanting to
Yea, your my man ;-)
It's working really fine. I do think we now have a killer JBossMQ/MDB
product. Great!
I could not see any problems with the commits in the code I know any
thing about (the JBoss server stuff), except the indentation in
JMSContainerInvoker (which I will fix).
//Peter
On
on 1-08-16 09.58, Peter Antman at [EMAIL PROTECTED] wrote:
my dream is a XML based routing messaging infrastructure build
around or into JBoss and JBossMQ.
I been thinking of implementing a module that is enabling the managment of a
distributed colocated execution area, in effect a routing
On Wed, 15 Aug 2001, Dan - Blue Lotus Software wrote:
My opinion of it back 5 months ago was that it was not really even close to
usable yet. Have things changed radically since then?
Well, I think the emergence of UDDI/WSDL gave them a boost to speed
up, and all the core specs seem to
On 16 Aug, Till: [EMAIL PROTECTED] wrote:
1. JBoss should begin by focusing on the specs publishes by the java
community process, such as:
JAXM (XML messaging)
JAXR (XML registry)
JAXRPC (XML RPC)
Just for the record:
JSR:
67 Java APIs for XML Messaging 1.0 (public review with ea
Maybe it could be a key/pass combination.
Once the password is entered. It is kept in mememory
throughout the entire jBoss process.
d.
-Original Message-
From: danch [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 15, 2001 11:26 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev]
Is there a more prefered way short of the loaders?
--jason
On Thu, 16 Aug 2001, David Jencks wrote:
Ok, I finally got the rewritten XADataSourceLoader into cvs. All you need
to do to try with jca should be to use latest cvs rabbithole. The
XADataSourceLoader should do the conversion for
I may have time to look at this today, else I will get to it this weekend.
Thanks.
--jason
On Wed, 15 Aug 2001, Sacha Labourey wrote:
Hello,
You'll find attached to this document two version of a win32 command prompt
batch file that aims to replace the old one.
They no more needs the
Feature Requests item #451610, was opened at 2001-08-16 09:07
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376688aid=451610group_id=22866
Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous
Was this ever resolved?
--jason
On Sun, 12 Aug 2001, Scott M Stark wrote:
The profile shows two traces from
org.jboss.ejb.plugins.jrmp.interfaces.EntityHandleImpl.getEJBObject()
into JNDI. The first takes 1600 ms, the second 100 ms. The only
difference between the two calls
is the order
On Tue, 14 Aug 2001, Hiram Chirino wrote:
I was looking for a way to fill in those description fields that
DynamicMBeans can fill out. But I did not want to have to replace all the
JBossMQ MBeans with DynamicMBeans. So this is what I did:
Why not? Aren't DynamicMBeans easier to work with?
Alright. It is too bad that Category does not expose support to detect when
levels change, such that a helper object could cache this value and not
affect the dynamic nature of the system as a whole.
--jason
On Wed, 15 Aug 2001, Scott M Stark wrote:
Caching the values destroys the dynamic
Is there a general guide line for domain usage under jmx? Are there any
plans to exploit this in a more organized manner? Should domain refer to
components on a single agent, or cross multiple agents? For example in a
clustered environment, domain could refer to a particular node group, or
Do you know what the bug is? Can we get around it by adding extra
whitespace or something like that in the meantime?
--jason
On Wed, 15 Aug 2001, Chris Kimpton wrote:
Hi,
It is supposedly fixed with patch 50 (?), but its not in a released
build yet...
You can get a candidate build from
How about a JINI modules with adapters for all of the services from sun into
MBeans or better yet lgpl impls of the same functionality?
--jason
On Thu, 16 Aug 2001 [EMAIL PROTECTED] wrote:
Feature Requests item #451610, was opened at 2001-08-16 09:07
You can respond by visiting:
What ever happend with this? Does anyone know if we should look into this
further? What exaclt does ECperf do and how will it help make JBoss better?
--jason
On Thu, 9 Aug 2001, Scott Stirling wrote:
Hi,
I am on the ECperf 1.1 JSR expert group, representing Macromedia. Since all
the
might be broken... perhaps?
--jason
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
Nope, I haven't had a chance to look at it. Although, right now, I'm in the
JNDI code, I can probably investigate it.
Bill
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jason
Dillon
Sent: Thursday, August 16, 2001 12:23 PM
To: [EMAIL PROTECTED]
Hi
I installed Jboss2.2.1 in SunOS 5.8,sparc running Java 1.3.0.
When io tried to start jboss it fails with the following message and
shutsdown.
===
javax.management.RuntimeErrorException: Error thrown trting to invoke
the getter for the
attribute Logging
What could cause this
Can we not be this verbose here... it is very distracting.
--jason
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
What are the TX timeout semantics for the JBoss tx manager? Once a given tx
starts does it have a finite time to finish before it times out, or is it's
lifetime more dynamic?
For example, if I have Bean1 that invokes Bean2 which then invokes Bean3.
If the timeout is 5 minutes, does the entire
What is ResourceAdapterName used for?
--jason
On Wed, 15 Aug 2001, David Jencks wrote:
Hi,
This discussion comes up in various places on various lists. Since you
don't mention otherwise I assume you are planning to decrypt in code
without manual intervention. As I understand the
Hi Jasson
Yes, I plan to reorganize the MBean Object Names for the implementation
of the server-side JBossMGT.
According to their spec it would be maybe good to have something like this:
- domain: is the JBoss server instance which can be default be the host
computer
name but
Hi
- Original Message -
From: Jason Dillon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, August 16, 2001 9:29 AM
Subject: Re: [JBoss-dev] How to get MBeans to describe it's fields like a
DynamicMBean does
On Tue, 14 Aug 2001, Hiram Chirino wrote:
I was looking for a way to
I've been thinking a little bit about a jca adapter to a javaspace, set up
so you can use JAWS, with entity bean -- entry. I'm not entirely sure
yet what advantages this would have over jms. I'm also not clear about what
would fetch entries out of the javaspace. Maybe jca 2 will help, I think
Do you have debug enabled? I currently have org.jboss = debug, which
produces a lot of stuff, but this is a bit excessive I believe.
--jason
On Thu, 16 Aug 2001, Scott M Stark wrote:
There is no such msg in main. Where are you seeing this?
- Original Message -
From: Jason Dillon
You have been free to convert all your db access to the jca framework for
the last 6 months, it appears noone has. The XADataSourceLoader change
more or less converts it for you. If you don't want to run on rabbithole
you could just use it for the conversion and copy the
ConnectionFactoryLoader
I just switched over and found one rather large problem, that is that my
beans deploy before the resource adapters. It could be that I am explicitly
listing the .jars to deploy, but I have the deploy/lib directory listed
before it, so I expected that it would do the right thing.
I think it will
Where should I put JDBCUser and Password now? Should they go into
PrincipalMappingProperties? Do I need to do anything else to make that
work. I have been ignoring the security stuff for the most part, since I do
not really understand it, and it is not currently required.
Any ways, I tried
Let me know if this turns out to be a bug/problem with the bean handle and
the InitialContextHandle stuff.
--jason
On Thu, 16 Aug 2001, Bill Burke wrote:
Nope, I haven't had a chance to look at it. Although, right now, I'm in the
JNDI code, I can probably investigate it.
Bill
Can you provide an example for what this might look like? I am thinking
something url like, but I am not sure what the spec will allow for a domain
name. So the domain for the jms stuff might look like this:
myhost.mydomain.com:/supercluster/jboss/jms
^^^
Is there any reason why we are explicitly use DefaultDomain:XXX and
implicily with :XXX in several places now? How about using :XXX everywhere
instead of DefaultDomain:XXX since it just takes up more space.
--jason
On Thu, 16 Aug 2001, Andreas Schaefer wrote:
Hi Jasson
Yes, I plan to
I've been thinking a little bit about a jca adapter to a javaspace, set up
Wouldn't you have to make an adapter to the jini tx service? or would the
jca adapter to a space deal with all the tx under the covers (and ignore
client requests to do it).
so you can use JAWS, with entity bean --
Let's not worry about micro-management level details in main that are going
to
change.
- Original Message -
From: Jason Dillon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, August 16, 2001 12:26 PM
Subject: Re: [JBoss-dev] Container.java
Is there any reason why we are
This was just added by vharcq so I was not seeing it because I did not have
the latest code. Messages like this should be using trace level priorities
through
the custom JBossCategory which will become Logger next week.
- Original Message -
From: Jason Dillon [EMAIL PROTECTED]
To: [EMAIL
I personally think that the domain should be structured but for your
example a colon (:) is not possible because it is reserved for the JMX
Object Name.
Andy
- Original Message -
From: Jason Dillon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, August 16, 2001 12:17 PM
Subject:
True, I did not remeber that. Any ways I think you get my point.
--jason
On Thu, 16 Aug 2001, Andreas Schaefer wrote:
I personally think that the domain should be structured but for your
example a colon (:) is not possible because it is reserved for the JMX
Object Name.
Andy
-
On 2001.08.16 15:35:22 -0400 Jason Dillon wrote:
I've been thinking a little bit about a jca adapter to a javaspace, set
up
Wouldn't you have to make an adapter to the jini tx service? or would
the
jca adapter to a space deal with all the tx under the covers (and ignore
client requests
Yes, as far as I can tell the user and password go into the
PrincipalMappingProperties. There is probably some way to get them into
somewhere else but I haven't figured it out yet. They are certainly used
if in the PrincipalMappingProperties.
btw. thanks for cleaning up my xml. Do you have a
ResourceAdapterName identifies which resource adapter supplies the
ConnectionFactory (and ManagedConnectionFactory etc etc) for the
ConnectionFactoryLoader to load. (It's the display-name tag in ra.xml) If
you were using firebird as your database, this could be the firebird
jca/jdbc driver.
User: user57
Date: 01/08/16 14:24:48
Modified:src/main/org/jboss/ejb AutoDeployer.java
Log:
o changed Category to JBossCategory and the Wait for... message priority to
trace.
o factored directory scanning out of run() into scanDirectories() and
scanDirectory().
o
On Thu, 16 Aug 2001, David Jencks wrote:
Yes, as far as I can tell the user and password go into the
PrincipalMappingProperties. There is probably some way to get them into
somewhere else but I haven't figured it out yet. They are certainly used
if in the PrincipalMappingProperties.
I will
Due to the changes to the CVSROOT/modules
fileone can't checkout the 2.4 branch
of the jbossmq source using the previous syntax.
The 2.4 branch needs to be checked
out using:
cvs co -r Branch_2_4 -P
_jboss_messaging
which creates a messaging rather than jbossmq
directory.
Why not leave
From: Jason Dillon [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] How to get MBeans to describe it's fields like a
DynamicMBean does
Date: Thu, 16 Aug 2001 09:29:01 -0700 (PDT)
On Tue, 14 Aug 2001, Hiram Chirino wrote:
I was looking for a way to
Hi jason, I forgot about this problem.
AutoDeploy works ok for me if the autodeployer conf looks like this:
mbean code=org.jboss.ejb.AutoDeployer name=EJB:service=AutoDeployer
attribute name=Deployers
JCA:service=RARDeployer;
J2EE:service=J2eeDeployer
/attribute
I must apologise to all for my IDE's total lack of proper auto formating...
Maybe Visual Age for Java 4.5 will get it right
Regards,
Hiram
From: David Maplesden [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: '[EMAIL PROTECTED]'
[EMAIL PROTECTED]
Subject: RE: [JBoss-dev] MDB has stopped
User: user57
Date: 01/08/16 14:49:11
Modified:src/main/org/jboss/resource RARDeployer.java
Log:
o use mkdirs() instead of mkdir() when creating the temp directory to avoid
exceptions when the base directory does not exist.
Revision ChangesPath
1.5 +6 -4
I am using something like this:
attribute name=URLs
../deploy/lib,
../deploy/bean1.jar,
../deploy/bean2.jar
/attribute
Since the beans are already urls ready for deploying they are added to the
list right away. The lib directory is only scanned once a pass is made on
run(),
In XAManagedConnectionFactory.getXADS() is returning null due to the return
null at the bottom of the method. It looks like this wants either an
xaDataSourceClass or xaDataSourceName to be set, if not it returns null.
Which then causes the pooling stuff to hang indefinently.
This is confusing
User: user57
Date: 01/08/16 15:23:30
Modified:src/main/org/jboss/ejb/plugins/jaws/jdbc
JDBCFinderCommand.java
Log:
o When execute() failes, log an error (instead of a debug) and throw
FinderException with more detail about the problem.
Revision
Why not? Aren't DynamicMBeans easier to work with? I am actually a little
confused about the different types, short of the basic MBean that
implements a mgmt interface.
NO they are harder to implement. A dynamic MBean has to explicitly export
all of it's managment interface. There is
On Thu, 16 Aug 2001, Scott M Stark wrote:
Due to the changes to the CVSROOT/modules file one can't checkout the 2.4 branch
of the jbossmq source using the previous syntax. The 2.4 branch needs to be checked
out using:
cvs co -r Branch_2_4 -P _jboss_messaging
which creates a messaging
Hi,
Ill look at this more later...
I think you also need
in properties
DataSourceClass=oracle class
and maybe ConnectionURL=url=jdbc
weird but maybe right.
I'll try some things out later this evening.
david jencks
On 2001.08.16 18:04:28 -0400 Jason Dillon wrote:
I am using something
Hi,
I want to know what persistance scheme is preferred
these days. I am going to start a new project and evaluating
Entity Bean, JDO, Castor etc. Its going to be a
heavy-load site with lots of concurrent users.
I will appreciate Pros and Cons of above
options.
Tony Grey
It looks like ResourceAdapterName is used to bind a connection factory
loader to a deployed adapter's display-name (as david mentioned). It also
looks like if the connection factory specifies an invalid name (one that
does not match up with the one in the ra.xml), that it will not complain and
Depends on your data model and expected usage. Take it to jboss-user for
more information.
--jason
On Thu, 16 Aug 2001, Tony wrote:
Hi,
I want to know what persistance scheme is preferred these days. I am going to start
a new project and evaluating
Entity Bean, JDO, Castor etc. Its
Hm !
I noticed your checkins on jboss-dev and wondered what
you were up to
Making life better I hope.
There are plans afoot to merge a repackaged version of
Jetty into the main JBoss tree and use it as the
default web container with JBoss. i.e. my
understanding is that
But once there is a common abstract to sub-class or a concreate wrapper
(that would proxy to an object), that seems like it would be easier than
the
interface as well as provide more functionality.
No, I think that the easiest way to expose attributes and functions is to
list them in a
I did briefly, but what I really want is a conversion guide. I did not have
much luck with taking bist from jboss-auto.jcml. I could try again though.
I am using the loader in the time being.
--jason
On Thu, 16 Aug 2001, David Jencks wrote:
Did you try the autoconverter
Weird. If you can set me straight on what needs to be done it would be a
huge, huge, massive, did I mention huge... help!
--jason
On Thu, 16 Aug 2001, David Jencks wrote:
Hi,
Ill look at this more later...
I think you also need
in properties
DataSourceClass=oracle class
and maybe
It doesn't help that jboss server is using 3 spaces and jboss mq
uses tabs...
jbossmq should be using 3 spaces too... but the task of changing this over
is daunting.
--jason
___
Jboss-development mailing list
[EMAIL PROTECTED]
User: user57
Date: 01/08/16 16:53:15
Removed: jetty/src/build build.bat build.sh
Log:
o integrating plugins/jetty with buildmagic
___
Jboss-development mailing list
[EMAIL PROTECTED]
User: user57
Date: 01/08/16 16:53:15
Added: jetty/src/etc README VERSION demo.xml jetty.properties
jetty.xml
Log:
o integrating plugins/jetty with buildmagic
Revision ChangesPath
1.2 +44 -0 contrib/jetty/src/etc/README
User: user57
Date: 01/08/16 16:53:14
Added: jettybuild.sh build.xml config.xml
Removed: jettyREADME TODO
Log:
o integrating plugins/jetty with buildmagic
Revision ChangesPath
1.2 +131 -0contrib/jetty/build.sh
1.2 +490 -0
User: user57
Date: 01/08/16 16:53:15
Added: jetty/docs README TODO
Log:
o integrating plugins/jetty with buildmagic
Revision ChangesPath
1.2 +45 -0 contrib/jetty/docs/README
1.2 +18 -0 contrib/jetty/docs/TODO
User: user57
Date: 01/08/16 16:54:14
Modified:src/resources/jdbc-rar/META-INF ra.xml
Log:
o updated DOCTYPE to reflect the actually location of the dtd on java.sun.com
Revision ChangesPath
1.4 +53 -49jbosspool/src/resources/jdbc-rar/META-INF/ra.xml
User: user57
Date: 01/08/16 16:54:15
Modified:src/resources/xa-rar/META-INF ra.xml
Log:
o updated DOCTYPE to reflect the actually location of the dtd on java.sun.com
Revision ChangesPath
1.2 +69 -63jbosspool/src/resources/xa-rar/META-INF/ra.xml
Index:
User: user57
Date: 01/08/16 16:57:48
Modified:src/resources/org/jboss/jms/ra/META-INF ra.xml
Log:
o updated doctype to reflect the dtd's location on java.sun.com
Revision ChangesPath
1.4 +28 -24jboss/src/resources/org/jboss/jms/ra/META-INF/ra.xml
User: user57
Date: 01/08/16 17:00:56
Modified:.modules
Log:
o added plugins/jetty to jboss-all-plugins module (which is part of jboss-all)
Revision ChangesPath
1.47 +2 -4 CVSROOT/modules
Index: modules
User: user57
Date: 01/08/16 17:01:47
Modified:jbossconfig.xml
Log:
o made plugings/jetty a memeber of the standard-plugins group (part of the
default build of jboss-all)
Revision ChangesPath
1.2 +3 -3 build/jboss/config.xml
Index: config.xml
I could run a code beautifier on it..
Regards,
Hiram
From: Jason Dillon [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: '[EMAIL PROTECTED]'
[EMAIL PROTECTED]
Subject: RE: [JBoss-dev] MDB has stopped working
Date: Thu, 16 Aug 2001 16:55:01 -0700 (PDT)
It doesn't help that jboss server is
User: user57
Date: 01/08/16 17:19:23
Modified:src/main/org/jboss/ejb AutoDeployer.java
Log:
o log an info message when scanDirectory finds a file to deploy
Revision ChangesPath
1.23 +2 -1 jboss/src/main/org/jboss/ejb/AutoDeployer.java
Index:
On Thu, 16 Aug 2001, Hiram Chirino wrote:
I could run a code beautifier on it..
Ok. =)
--jason
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
It looks like the recent jca datasource loaders have introduced
inconsistency in the transaction integrety of the entity system.
I have not yet been able to track this down, but based on an application
that was working the day before yesterday, which is now non-functional after
more than one
What are we going todo about logging from resource adapters and such? It
looks like there is alot of stuff that:
if (logger != null) {
// some use full message
}
Or it will not log anything at all... even error conditions. It also looks
like there is alot of System.out|err usage too,
But once there is a common abstract to sub-class or a concreate wrapper
(that would proxy to an object), that seems like it would be easier
than
the
interface as well as provide more functionality.
No, I think that the easiest way to expose attributes and functions is
to
list them
Right now there are any number of ways to cause JBoss to spin in a tight
loop
trying to deliver a transacted msg to an mdb due to a problem with either
the msg or mdb code that either causes an exception thrown from onMessage()
or the tx to be rolled back. A trivial example of the latter is to
User: pkendall
Date: 01/08/16 18:29:34
Modified:src/main/org/jboss/mq SpyMessageConsumer.java
Log:
Fix message listener acknowledgements
Revision ChangesPath
1.4 +2 -2 jbossmq/src/main/org/jboss/mq/SpyMessageConsumer.java
Index: SpyMessageConsumer.java
Per spec the MDB should not be throwing any exceptions.. This would mean
that it's thier responsibility to put the message to a 'rejected' queue.
But I think that is the best solution would be to allow the MDB to be
configured with the 'rejected' queue in it's deployment descriptor. I know
User: chirino
Date: 01/08/16 18:35:35
Modified:.modules
Log:
To checkout the standalone JBossMQ server you should now use the jboss-mq module.
Revision ChangesPath
1.48 +4 -3 CVSROOT/modules
Index: modules
Hi,
Unfortunately it doesn't seem to be possible to issue a warning if you
supply the wrong resource adapter name, since the way it works is:
ConnectionFactoryLoader mbean gets its ResourceAdapterName and registers as
a NotificationListener with the jmx server, filtering on Deployment events
Ok I've changed the standalone MQ module name to 'jboss-qm'.
So to all you mq folks working on the head branch... checkout the
standalone server using the
jboss-mq
modules name... The jbossmq module only contains the sources... no build
system is included. This should also fix Scott's
Start with the fact that the bank unit test deadlocks and the server is
spewing tons
of messages at info level to the console:
[DefaultDS] Pool
org.jboss.pool.connector.jdbc.JDBCManagedConnectionFactory-1 is full
(10/10)!
[DefaultDS] Pool
The mdb does not have to thrown an exception to cause this behavior. If it
interacts with another ejb that is transacted and that bean rolls the
transaction
back the msg will get redeliverd. I have a trivally test case that causes
the problem:
public void onMessage(Message m)
{
try
{
User: pkendall
Date: 01/08/16 18:52:33
Modified:src/main/org/jboss/mq SpyMessageConsumer.java
Log:
Handle runtime exceptions in message listener code
Revision ChangesPath
1.5 +53 -46jbossmq/src/main/org/jboss/mq/SpyMessageConsumer.java
Index:
Well, the current level of logging coming from the datasource layer is
absurd. If this is
due to PrintWriter interface screw the spec. Unless someone has called
setLogger the
JBoss RAs should be defaulting to log4j.
- Original Message -
From: Jason Dillon [EMAIL PROTECTED]
To: [EMAIL
Hi,
Sorry I broke your app, I was kind of worried when I realized the xa rar
had never been assembled, but noone said no. Is there some usable or
automatic way to mark in cvs all the changes that go together like the ones
I made?
Can you provide any more details of what's going on? Did you
User: chirino
Date: 01/08/16 20:02:40
jbossmq/src/etc/.Refactory - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: chirino
Date: 01/08/16 20:04:04
Modified:src/main/org/jboss/mq/il/jvm JVMClientIL.java
JVMClientILService.java JVMServerIL.java
JVMServerILFactory.java JVMServerILService.java
JVMServerILServiceMBean.java
User: chirino
Date: 01/08/16 20:04:01
Added: src/etc/.Refactory pretty.settings
Log:
Used the ejbdoclet pretty task to auto-indent the source files to
the 3 space standard.
Revision ChangesPath
1.1 jbossmq/src/etc/.Refactory/pretty.settings
User: chirino
Date: 01/08/16 20:04:01
Modified:.build.xml
Log:
Used the ejbdoclet pretty task to auto-indent the source files to
the 3 space standard.
Revision ChangesPath
1.5 +14 -1 jbossmq/build.xml
Index: build.xml
User: chirino
Date: 01/08/16 20:04:04
Modified:src/main/org/jboss/mq/il/rmi RMIClientIL.java
RMIClientILRemote.java RMIClientILService.java
RMIServerIL.java RMIServerILRemote.java
RMIServerILService.java
User: chirino
Date: 01/08/16 20:04:03
Modified:src/main/org/jboss/mq/cluster/transport
InvalidConfigurationException.java
InvalidStateException.java NodeId.java
SerializerUtil.java Transport.java
User: chirino
Date: 01/08/16 20:04:03
Modified:src/main/org/jboss/mq/il ClientIL.java ClientILService.java
ServerIL.java ServerILFactory.java
ServerILJMXService.java
ServerILJMXServiceMBean.java
Log:
Used the
User: chirino
Date: 01/08/16 20:04:06
Modified:src/main/org/jboss/mq/referenceable ObjectRefAddr.java
SpyConnectionFactoryObjectFactory.java
SpyDestinationObjectFactory.java
Log:
Used the ejbdoclet pretty task to auto-indent the
User: chirino
Date: 01/08/16 20:04:05
Modified:src/main/org/jboss/mq/pm PersistenceManager.java Tx.java
TxManager.java
Log:
Used the ejbdoclet pretty task to auto-indent the source files to
the 3 space standard.
Revision ChangesPath
1.2
User: chirino
Date: 01/08/16 20:04:04
Modified:src/main/org/jboss/mq/il/uil/multiplexor
DemuxInputStream.java MultiplexorTest.java
MuxOutputStream.java SocketMultiplexor.java
StreamDemux.java StreamMux.java
Log:
Scott...
I wanted to know how I should handle tagging the CVS for the upcomming
versioning of the MQ module to 1.0 beta.
First of all if I go by the admin howto on the website it would have to be
1.0.0.0 beta right??
And would I tag with Rel_1_0_0_0??? or should I use a RelMQ_1_0_0_0 or
I can't argue with the idea that Aaron might possibly have logged things a
bit heavily, however my banktest completed successfully after 2860.064
seconds. What form did this deadlock take? Is running 50 threads through
10 connections with ~10,000 transactions a reasonable unit test?
david
Releases are major.minor.patch so it is a 1.0.0 release. Only the
internal tags use 4 digits: Rel_major.even_minor.patch.build
You can't use Rel_xxx tags as these will conflict with the JBoss use of
them so it would have to be RelMQ_1_0_0_0. The final 1.0.0 release
should be tagged with
1 - 100 of 113 matches
Mail list logo
