Most AOP frameworks have the ability to make class proxies as well as interface
proxies.
You could suggest to the Spring team they use such a framework then they
wouldn't have this limitation.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4074684#4074684
Already fixed in TRUNK
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4074736#4074736
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4074736
___
jboss-user mailing list
I have followed your instructions and tried to replicate this with AS 4.2.0.GA
(CR1 is only tested with 4.2.0), but I cannot replicate.
Can you verify if the problem occurs with 4.2.0? Otherwise I will mark as
cannot replicate.
View the original post :
In the distro there is a file call jms-ds.xml.
This contains all the configuration for a *local* jms provider.
If you use the JCA resource adaptor at java:/JmsXA then you will be talking to
the local JMS provider (via a resource adaptor).
You can create another one of these files (or you can
I just copied what you posted.
If you can package up a test program and exact step by step instructions I will
try again
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4074971#4074971
Reply to the post :
btsibr wrote : I think the only issue is that it isn't possible to propagate
the client credentials from the JAAS client login to the standard
ConnectionFactory. This would be a feature request.
|
Please feel free to add a feature request in JIRA.
(BTW this feature is not supported by
Sorry I have taken so long to look at this.
Before I investigate any deeper, there is one obvious thing I can see wrong in
your remote jms provider config:
| !-- The combined connection factory --
| attribute name=FactoryRefjava:/XAConnectionFactory/attribute
| !-- The queue
Ok, I just validated that I can successfully consume from a remote jms provider
and send to a local jms provider using the bridge and a remote jms provider
loader configured using global JNDI namespace.
I'm using TRUNK but there haven't been any bridge code changes between CR1 and
TRUNK.
I'm
It looks like there is an error in your configuration - you have configured
your remote jms provider to use the local java: namespace.
So linked-to thread for more details.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4073977#4073977
Reply to the post :
In your remote jms provider, you are using the local JNDI namespace (java:) to
do your lookup:
| mbean code=org.jboss.jms.jndi.JMSProviderLoader
| name=jboss.messaging:service=JMSProviderLoader,name=CSMJMSProvider
| attribute name=ProviderNameCSMJMSProvider/attribute
|
Ok, you make a good case:
I'll put the old SPs and GAs up again as soon as I have some time...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4073980#4073980
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4073980
You could use a request-response pattern.
I.e. send a response back once you have consumed the message from the topic.
This is a classic pattern, google it for more info.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4073982#4073982
Reply to the post :
aslak wrote : In this case, the 1.3.0 behavior seems to be more correct.
Yes, but we are having to work around an active mq bug here, see
http://jira.jboss.com/jira/browse/JBMESSAGING-988 for more details.
View the original post :
aslak wrote :
|
| 1. The bridges source consumer receives a ActiveMQMessage from the
ActiveMQProvider
| 2. The bridge tries to send the message to the target JbossProducer.
| 3. The JbossProducer figures out it is a foreign message and converts the
message to a JbossMessage. The
The standard non HA jms provider loader exists in a file called jms-ds.xml in
the standard AS distribution.
You just want to create a new one (either in the same file, or a different file
- it doesn't matter) referencing your remote provider as per the wiki page.
View the original post :
I am struggling to see what the issue is here.
AFAICT this is just a difficulty in configuration. Onced Madhu had configured
it correctly it works.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4074052#4074052
Reply to the post :
After some thought, I consider this a bug in Spring - Spring is making
assumptions about how a particular JMS provider implements its destinations
which is incorrect.
I suggest pinging the Spring team and lodging a bug report with them.
View the original post :
You haven't said what version you are using.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4074063#4074063
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4074063
___
jboss-user
Sorry, I don't know what this trailblazer is, that you are referring to.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4074066#4074066
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4074066
Well... JBoss 4 currently ships with JBoss MQ, not JBoss Messaging, so if you
remove JBoss MQ then it's hardly surprising the trailblazer application that
uses JBoss MQ no longer works :)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4074075#4074075
Reply to
You should have write access. If not, ping me.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4074084#4074084
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4074084
___
jboss-user
Changing the datasource should be trivial.
Just need to update it in xxx-persistence-service.xml.
There's no need to change anything related to jgroups
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4073691#4073691
Reply to the post :
There is an issue with having a remote provider for the bridge source - this
has been mentioned several times in this forum.
It will be fixed for CR2 once I find enough time to investigate.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4073692#4073692
Reply
mskonda wrote : Also, could you please confirm me that the SP_patch_00017255
succeds 1_2_0_SP1 (I am sure it must have, but want to double check).
|
| Thanks
| Madhu
Answered on the support portal.
View the original post :
We deliberately don't have all the old versions for download, since we want to
encourage people to use the later versions.
With the very limited resources we have we need to limit the number of versions
we support.
However, all the versions are available by simply checking out on the
Yes, there is a whole stack of JBoss remoting issues in the version in AS 4.2.0
which will be fixed for the next release.
BTW in your timer ejb, are you using the managed connection factory (i.e. the
one at /JmsXA), or are you manually creating a connection each time to send to
the topic using
aslak wrote :
| Looking at the 1.4.0.CR1 code, the restriction on JbossMessage needing a
JbossDestination has changed. So now the destination is set, but it is a
ActiveMqTopic and results in a ClassCastException in
|
| ServerConnectionEndpoint.sendMessage:
| JBossDestination dest =
We don't use the smoke test script any more, maybe you are referring to an
earlier version?
Nowadays our smoke tests are just running the examples against a 4.2.0 instance
(which is basically what they were before anyway).
View the original post :
aslak wrote : hmm... spoke to soon..
|
| The order issue I found was when in batch mode.
|
| Same batch mode issue is also in
| JDBCPersistenceManager.handleBeforePrepare(List, List, Transaction)
|
|
| There seem to be the same in non batch mode as well..
|
|
aslak wrote : I have setup a JbossMessaging Bridge to listen to a ActiveMQ
queue via a ActiveMQ JMSProvider configured on Jboss.
|
| The Bridge reads the sourceDestination messages from ActiveMQ fine, it's
sending this ActiveMQ Message object to the targetProducer/targetDestination
that is
There is another issue with the bridge, also due to be fixed in CR2 (out in the
next week probably).
Not sure if itis related, in any case we wil investigate this in the next few
days.
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072512#4072512
http://jira.jboss.com/jira/browse/JBMESSAGING-1042
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072513#4072513
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4072513
___
In the distro, there is a working example that demonstrates how to do this.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072522#4072522
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4072522
The smoke tests *are* just the examples, so by running the examples you have
run the smoke tests.
Maybe you are referring to the perf tests? There is a wiki page that explains
how to do this.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072641#4072641
Looks like that file somehow didn't make it into the distro.
You can find it here
http://anonsvn.jboss.org/repos/messaging/tags/JBossMessaging_1_4_0_CR1/src/etc/remoting/
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072683#4072683
Reply to the post :
The script works fine when run on the main source (where things are in a
different place) but for some reason it didn't get munged properly before
getting put in the distro.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072700#4072700
Reply to the post :
geeky2 wrote : the current build is also missing examples.properties
|
Yes, it's the examples.properties which overrides the properties to give the
correct paths.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072709#4072709
Reply to the post :
http://jira.jboss.com/jira/browse/JBMESSAGING-1029
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072143#4072143
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4072143
___
Hi -
You should post this in the JBoss MQ forum - this is the JBoss messaging forum.
(see note at top of forum)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072145#4072145
Reply to the post :
We don't currently support this, but you can add a feature request in JIRA if
you like.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072146#4072146
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4072146
http://jira.jboss.com/jira/browse/JBMESSAGING-1031
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072149#4072149
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4072149
___
http://jira.jboss.com/jira/browse/JBMESSAGING-1032
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072152#4072152
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4072152
___
http://www.jboss.org/index.html?module=bbop=viewtopicp=4072152#4072152
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072153#4072153
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4072153
But you can inspect the parameters to get the destination.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072154#4072154
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4072154
___
Not sure yet, but sometime Q1 or Q2, 2008 probably.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072156#4072156
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4072156
___
http://jira.jboss.com/jira/browse/JBMESSAGING-1035
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072158#4072158
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4072158
___
http://jira.jboss.com/jira/browse/JBMESSAGING-1036
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072160#4072160
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4072160
___
Hi genman - did you solve this yet?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072162#4072162
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4072162
___
jboss-user mailing list
Yes, we are very busy.
We'll get around to it eventually.
If you want to lend a hand you would be most welcome. I have plenty of JIRA
tasks I could assign to you?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4070058#4070058
Reply to the post :
Yep, we'll put it in CR2.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4070060#4070060
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4070060
___
jboss-user mailing list
mwelss wrote :
|
| I have the complete thread dump, if neccessary.
| /quote]
|
| Yes please.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4069564#4069564
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4069564
| java.sql.SQLException: Column not found: NODE_ID in statement [SELECT
TRANSACTION_ID, BRANCH_QUAL, F
| ORMAT_ID, GLOBAL_TXID FROM JBM_TX WHERE NODE_ID = ?]
|
This is because in 1.4.0 there is an extra column NODE_ID in the table JBM_TX
View the original post :
Craig-
As already mentioned, 1.0.1.GA is *not* the latest in the 1.0 series.
Also, 1.2.0.GA is *not* the latest 1.2 release (1.2.0.SP2 is).
The latest GA release is 1.3.0.GA, and 1.4.0.CR2 will be out shortly followed
shortly after by 1.4.0.GA.
We simply do not have the time to give free
Yes you could add your own interceptor (aspecy) on the server aop stack.
Take a look at the aspects that already exist e.g. SecurityAspect for an idea
of how to do this.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4069409#4069409
Reply to the post :
All this information is available in JIRA.
There are links to JIRA from the project main page and the user wiki
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4068655#4068655
Reply to the post :
boniek wrote : I'm getting this when starting JBoss Messaging with mysql 5:
|
| 20:03:05,175 WARN [JDBCPersistenceManager]
|
| JBoss Messaging Warning: DataSource connection transaction isolation should
be READ_COMMITTED, but it is currently REPEATABLE_READ.
|
This is doing exactly what it says on the tin.
You have killed your client, the server has detected it and is cleaning up
server side resources associated with that client.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4068658#4068658
Reply to the post :
The 1.0 series is old now. We don't recommend any new users use it.
We are bringing out a new version 1.4.0 shortly (there is already a release
candidate (non production) out now) so we would recommend you wait for that.
It's a drain on our resources to keep supporting old versions.
View the
Yes, we understand there was a typo in the doco for 1.0.
This was fixed many months ago for the 1.2 release.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4068662#4068662
Reply to the post :
You should be able to see any differences by looking at the user guide or
release notes.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4068663#4068663
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4068663
The JAAS login module is used on the server side to authenticate/authorise the
user specified in the call to createConnection.
When using the standard connection factories security credentials are not
propagated from client to server.
View the original post :
This was covered in an earlier thread:
http://www.jboss.com/index.html?module=bbop=viewtopict=114049
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4068536#4068536
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4068536
Craig2007 wrote : I very much appreciate for your reply.
|
| Do provide me way to configure the fullSize, pageSize and DownCacheSize
parameter for all those destination specified in our application
|
It's FullSize, PageSize, DownCacheSize, not fullSize, pageSize, downCacheSize
View the
The latest version in the 1.0 line is 1.0.1.SP5.
There have been many fixes between 1.0.1.GA and 1.0.1.SP5, please see JIRA for
details.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4068452#4068452
Reply to the post :
Have a look at setting the paging params on your queues
http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/guide-1.0.1.SP5/html/configuration.html#conf.destination.paging
This enables you to limit the number of messages a queue will have in memory at
any one time
Ok, that would make sense.
I made a change between 1.3.0 and 1.4.0 so it no longer assumes the jndi name
is in the java namespace.
I'll update the doco appropriately.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4068285#4068285
Reply to the post :
Yes, currently the check to see if a message is expired is only done on
delivery. This is sufficient to be JMS spec compliant.
It would be a fairly intensive operation to continously scour the queues for
expired messages.
However I have added a task for JBM 2.0 to implement this.
View the
Thanks Noxis-
We'll take a look at this next week.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4068283#4068283
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4068283
___
But JBAS 4.2.0 uses JBoss MQ not JBoss Messaging.
Or maybe you have de-installed JBoss MQ and installed JBoss Messaging? It
wasn't clear from your post.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4068329#4068329
Reply to the post :
genman wrote : What I did for JBoss MQ is schedule a timeout to occur for all
expiring messages, similar to the scheduled message feature, which does the
move/removal.
|
| There are some scalability issues with doing that. Namely, every soon and
not-so-soon expired message ID is kept in
twistah wrote :
| I've searched all that I know and am unable to find any pointers to what
causes this.
|
http://jira.jboss.com/jira/browse/JBMESSAGING-985
http://www.jboss.org/index.html?module=bbop=viewtopict=107795
View the original post :
Chip-
I will take a look at this and try and replicate ASAP, but will probably be
next week since we are really snowed under (what's new?) right now. :)
Thx
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4068036#4068036
Reply to the post :
This was covered in an earlier thread:
http://www.jboss.com/index.html?module=bbop=viewtopict=114049
1.4.0.RC1 is only tested against Mysql - sorry I should have been more explicit
about this in the release notes.
Of course, for the GA we will have tested against all supported databases.
View
This is because the Arjuna recovery manager is starting up and starting it's
recovery cycle before the JMSProviderLoader has been deployed and can't find it.
This should be harmless.
I will however make sure the error message is suppressed on RC2/GA since it's
pretty ugly.
View the original
Hi Chip-
The two links I posted:
http://jira.jboss.com/jira/browse/JBMESSAGING-999
http://www.jboss.org/index.html?module=bbop=viewtopict=111456
Refer to a known issue which was fixed in 1.4.0.CR1 (see the JIRA link).
I think this is the same issue.
View the original post :
In the examples there's an example of sending a message from a web service (a
servlet).
You just need to deploy a JMSProviderLoader pointing to your remote provider
(there should be some wiki pages about this), then make sure you lookup the
connection factory corresponding to this provide.
Can you please give instructions on how to replicate?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4067303#4067303
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4067303
___
Currently the connection factory needs to be downloaded from the server since
it contains important information needed for operating properly.
For JBM 2.0 we will be supporting a full range of clients:
C++/C, C#, perl, etc
View the original post :
aaubry wrote :
|
| I do think that this more a Spring issue due to the fact that Spring is not
reusing connection to optimize the number of concurrent TCP/IP connection but,
if someone did have the same issue and found a workaround, I would be very
please to read it.
|
| Fyi, I wrote
We don't currently support embedding JBM (as a set of POJOs or whatever), but
this will be supported when we move to a Microcontainer based set of services
which is scheduled from JBM 2.0
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4067306#4067306
Reply to
Does this file exist? - maybe it has been accidentally deleted or the file has
become corrupted (bad disk?)
| Failed to find META-INF/jboss-service.xml for archive jbos
| s-aop.deployer
|
Try re-installing the aop deployer from a fresh jboss installation (i.e.
replace the directory
aaubry wrote : timfox wrote :
| | Though, if I compare commercial product to jBoss messaging, the
behavior is quite different. In a commercial product that I won't quote here,
it's quite easy to configure a queue or a topic with no datasource associated
to it (storing enable=true or false
This should help
http://wiki.jboss.org/wiki/Wiki.jsp?page=HowDoIConfigureTheJMSResourceAdapterToUseARemoteConnectionFactory
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4067591#4067591
Reply to the post :
I think this is the same as this:
http://jira.jboss.com/jira/browse/JBMESSAGING-999
http://www.jboss.org/index.html?module=bbop=viewtopict=111456
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4067594#4067594
Reply to the post :
Yes, we have simplified clustering considerably in 1.4.0.
One of the changes is there are no longer separate clustered and non clustered
persistence config files.
I recommend you look at the 1.4.0 userguide, since a few other things have
changed in clustering too (no more default router policy
Please post your JMSProviderLoader configuration (both of them), also what
version are you using?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4067160#4067160
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4067160
If you send a message as non persistent (DeliveryMode.NON_PERSISTENT) then it
won't get persisted.
If you don't control over this, them there's not much you can do currently.
There is a task scheduled for this for JBM2.0
http://jira.jboss.com/jira/browse/JBMESSAGING-381
View the original post
Failover kicks in when a server *dies*.
CTRL-C does not kill a server, it shuts it down cleanly - this won't cause
failover.
Kill it using kill, or using task manager in windows.
There have been long discussions on this in other threads.
View the original post :
See also http://www.jboss.com/index.html?module=bbop=viewtopict=110632
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4066102#4066102
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4066102
CR1 is not currently tested with anything other than MySQL.
Remove the FK and you will probably be ok
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4066112#4066112
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4066112
rodgerca wrote :
| I've figured out another way of doing it anyway.
Can you share this with us?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4066220#4066220
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4066220
joshiashutosh wrote : Thanks for the response, Tim.
| I think I too will go with method 2.
| I looked at the Bridge code and am myself using an identical one. One
problem I am facing is that it gives an exception while setting the property
JMSXDeliveryCount. It seems to be an internal
Not sure I understood what the problem is from your explanation.
Can you explain in more detail?
When you say failover does not work as I would expect it - how would you
expect it to work?
If you can give me a step by step to reproduce and state what you your expected
behaviour is that would
The tables
HILOSEQUENCES
TIMERS
are nothing to do with JBM - they're tables created by JBoss AS - I don't know
what they're used for.
Best ask in the AS forum
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4065995#4065995
Reply to the post :
Yes, this is a pain isn't it?
We have the JMS spec to blame for that.
Either of your two methods will work.
Actually we have exactly this problem in the message bridge where we have to
forward a message from one source to a a target.
In that case we use method 2)
Take a look at the message
Have a search in this forum too.
I vaguely recall people having similar problems moving from 1.2.0 to 1.3.0 and
they resolved it. Some problem in their config - maybe something to do with
scoping (in 1.3.0 you shouldn't scope anything)
View the original post :
You should ask this in the EJB3 forum.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4065103#4065103
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4065103
___
jboss-user mailing
The messaging team is pleased to announce the release of JBoss Messaging
1.4.0.CR1.
This is a candidate release for JBoss Messaging 1.4.0.
This release fixes several important bugs from the previous release, full
details of which can be found in the release notes.
The other major changes in
rodgerca wrote : btw I'm aware of scheduled delivery - that is not what I am
looking for. I'm looking for something that can put in a delay of x seconds
That is exactly what scheduled delivery does.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4064634#4064634
sem wrote : Sounds like potential problem because it would be difficult to
monitor this things on production environment.
Can you explain in more detail?
I didn't quite understand.
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4063412#4063412
Reply
901 - 1000 of 1586 matches
Mail list logo
