Hi Leos-
JMSServerManager is only really used for loading JMS queue, topic and
connection factory descriptions from jbm-jms.xml into JNDI and also registering
them with JMX. The JMX call to createTopic in JMSServerManager basically just
does that. (Actually I think we should rename them to
Leos.Bitto wrote :
| Nice, but what is session?
http://java.sun.com/javaee/5/docs/api/javax/jms/Session.html
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4241110#4241110
Reply to the post :
OK fine, you should just be able to instantiate it directly as mentioned
previously :)
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4241115#4241115
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4241115
The exception is being thrown from the transaction manager code (JBoss
Transactions) which has been called from the JCA adapter with a call to commit
a transaction.
I'd say your best bet is to try the JCA user forum. (or JBoss TS forum)
View the original post :
gaohoward wrote :
| Using /ClusteredConnectionFactory, each time you gets a connection, you
connects to a different node (round robin load balancing by default).
|
| By enable Message Suckers in the cluster, messages will be pulled off from
nodes that have no local consumers to the nodes
Actually JBM 1.x does both. (BTW there is a FAQ on this, but I didn't right it
so can't vouch for it's accuracy).
When using a clustered connection factory, subsequent *connections* will
normally be created to different nodes of the cluster, by default in a round
robin fashion.
So connection
kennardconsulting wrote : Tim,
|
| What you say is very interesting. Could you please elaborate on what you
mean when you say:
|
| The local queue will first attempt to send messages to the local queue
| until it determines it is busy
|
| Do you mean the 'local queue will send
To clarify Jeff's answer a bit:
The MessagingServer you created is a core server. A core server knows nothing
about JMS - it's completely JMS agnostic, therefore it knows nothing about
topics.
This is discussed in the user manual:
gaohoward wrote : Q1: Is there a configurable way to define default message
headers from JBoss?
|
| --- I don't think it has a way to configure default values for message
headers.
|
|
Actually you can probably do this by providing an AOP interceptor in JBM 1.x.
In JBM 2.0
However, the user shouldn't have to put the JBM jars on the jconsole classpath,
we should only be passing back standard types not SimpleString.
We should look into this.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4240260#4240260
Reply to the post :
Hi Simon-
You can easily change the directories used by the server for persisting data.
The relevant params are:
journal-directory
bindings-directory
large-messages-directory
paging-directory
defaults are data/journal, data/bindings, data/large-messages, data/paging
More info here:
Jeff, please add a JIRA for this too.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4240413#4240413
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4240413
___
jboss-user mailing
ataylor wrote : Howard is correct, this functionality does not exist in JBM.
To be more precise, this functionality does not exist in JBM 1.x, but it does
exist in JBM 2.x
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4239728#4239728
Reply to the post :
I don't agree this is a bug.
Don't confuse creating queues with *putting queues in JNDI*.
You can access your queue directly by doing something like:
JBossQueue queue = new JBossQueue(queue_name);
you'll find it is there, just like with ActiveMQ.
View the original post :
jmesnil wrote :
| or use JMS API Session.createQueue(foo) (provided the JMS Queue was
| still created first by using the management API)
+1
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4239378#4239378
Reply to the post :
Can you explain why you think this is a bug in JBM 1.x, I don't follow your
reasoning here...
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4238969#4238969
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4238969
You could add a feature request JIRA if you like, if you want JBM 1.x to also
support sub contexts on the name too.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4238979#4238979
Reply to the post :
In JBM 1.x, if you want to do this kind of thing you need to use JNDIName as
Howard mentioned at the beginning of this thread.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4238977#4238977
Reply to the post :
unwavering wrote : Dear respectable community,
|
| I have a project in which JBoss Messaging 1.4 will be used as the messaging
component. One of the requirements is to define different groups of queues for
different parties. The purpose of the grouping concept is facilitate queues
In JBM 2.0 messages are paged to disk _before_ they are routed in the
postoffice, i.e. paging is a stage before routing.
Therefore any messages that are paged to disk are not in any queues yet. That's
why you don't see them on the queue message count.
Perhaps we should add a messageCount
Could you open a JIRA, and attach a client program that demonstrates the issue,
along with instructions for replicating?
Thanks.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4238403#4238403
Reply to the post :
JBoss Messaging 2.0 beta 2 is released and ready for download.
Beta 2 is a minor update release for beta 1 that we released last week.
We aim to be producing releases at a higher rate than we've previously done in
the project - following the release early, release often mantra.
Get it here:
The stacktrace shows the exception is thrown from the JCA adapter, not from
JBoss Messaging.
The generic JCA adapter is part of the application server project, it's not
handled by the JBoss Messaging team.
Your best bet would be to post in the JCA users forum.
View the original post :
Hi Carl-
If consumers crash or exit without cleanly closing their connections, then
sometime after the connection TTL time, the server should automatically close
them on the server which would result in any delivered but unacknowledged
messages going back on their queue(s).
Default connection
Also, this is not the right forum for MDB config questions.
There's another forum for that.
JBoss Messaging does not handle MDBs, that's part of the app server.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4236904#4236904
Reply to the post :
JBM 1.4.4 is *not* designed for JBoss 5, it won't work with it.
JBoss 5 has different internal apis and jars to JBoss 4.x. We can't create a
JBM 1.x release that will work with both JBoss AS 4.x and 5.x.
The latest release for JBoss 5 is JBM 1.4.3, and JBoss 5 comes with that
pre-installed.
If you create a JIRA and attach a self contained test program that we can run
to replicate the issue, someone can take a look at it.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4236674#4236674
Reply to the post :
Did you give each node in your cluster a unique server peer id?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4236610#4236610
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4236610
We haven't produced any scientific results and won't publish any until we can
do them properly (hopefully before GA), but we have done some ad-hoc tests, to
give you a taste:
Performance very much depends on your hardware. Using a single quad core Xeon
server with 16 GiB RAM and SAS hard
The JBoss messaging team are pleased to announce the release of JBoss Messaging
2.0 Beta.
JBoss Messaging 2.0 brings astonishing performance and a huge feature set, in
an all-new architecture.
With a focus on usability we've provided an extensive, easy-to-understand
user-manual and
The user guide for 2.0.beta is finished and in TRUNK and has a whole chapter on
topic hierarchies
http://anonsvn.jboss.org/repos/messaging/trunk/docs/user-manual/en/
Like Andy says, we'll be releasing 2.0.beta tomorrow probably.
View the original post :
saiya-jin wrote : ok my fault,
| I wanted to say we ALREADY have defined our own JMS connection factory,
which seems to be transactional by default. What we need to set is explicitly
turn of transactional behavior for this one.
| I hope i made myself more clear
In JMS there is no such
Because I need better precision I can't use scheduled executor any more in the
timedbuffer.
So *for now* each one has its own thread. So I added a close method to the
timedbuffer which gets called from the AsynchronousFuileImpl close() method, so
I can stop the thread.
But it seems this
I'm not familiar with this stopDelivery method - I guess this is something
added by the EJB team.
Like Howard says, perhaps it is doing something illegal, but without seeing the
code for it, it would be hard to tell.
View the original post :
Perhaps you are creating a huge number of sessions in your code?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4234068#4234068
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4234068
You didn't mention what version you are running so it's very hard to help you.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4234069#4234069
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4234069
Either that or perhaps there are different versions of the JBM and JBR libs on
client and server side.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4234071#4234071
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4234071
Again, looks like a jar issue. Make sure you have the correct jars on both
client and server side as per the user guide.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4234072#4234072
Reply to the post :
Also there is a wiki page that explains all of this in a lot of detail.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4234074#4234074
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4234074
Here is is
http://www.jboss.org/community/wiki/EJBJMSandJNDIoverHTTPwithUnifiedInvoker
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4234076#4234076
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4234076
Yes selectors do not work well with paged messages.
To implement it otherwise would be difficult - we'd have to scan the entire
file store for matching messages every time a consumer is added.
If you find yourself needing functionality like this, then it sounds like you
need a database not a
Well, as per JMS spec, JBoss Messaging lets you set the client id
programmatically after creating a connection, and you can define and set
selectors when creating a consumer.
However if you're using MDBs it's different, bear in mind MDBs are not part of
JBM, they're part of the app server, and
If you want a topic subscriber to receive all messages of a certain type and
also receive all messages sent directly to it, can't you assign each subscriber
an id and use a selector like:
| messageType='FOO' OR destinationID=myid
|
View the original post :
I guess I'm not understanding what the user is trying to achieve here.
Also I don't understand why the selector needs to be dynamic. The id is the
client id which can be in the deployment xml.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4232017#4232017
Guys-
Please post potential JBoss Messaging issues on the JBM forum.
I wasn't aware of this thread until some one pointed me in this direction, we
don't monitor this forum.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4232026#4232026
Reply to the post :
All those files should be in the AS 5.1 distro.
If they're not it's a colossal cockup.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4230187#4230187
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4230187
The files should certainly be in the distribution.
I'll ask Clebert/ Howard to investigate as they did the integration for AS 5
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4230194#4230194
Reply to the post :
maxogm wrote : Hi,
| did anyone has some example how to use LoadBalancingFactory...
| Thanks
http://www.jboss.org/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.3.GA/html_single/index.html#conf.connectionfactory.attributes.loadbalancingfactory
View the original post :
Also this is a question on JCA configuration, not JBoss Messaging config.
None of the above config is JBM config.
Please ask in the JCA user forum.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4229632#4229632
Reply to the post :
We don't provide a download of 1.4.3.GA because it is compiled against the
libraries for JBoss AS 5.0 only.
It won't run in EAP or AS 4.x.
Since it's already available as part of JBoss AS 5.0, there's no need to
provide a separate download, it's already pre-installed.
View the original post :
I'm having trouble understanding what you're trying to achieve.
Perhaps you could post a test program?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4226924#4226924
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4226924
I've re-opened the task, so Howard can take a look.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4226956#4226956
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4226956
___
There's no such release as 1.4.4.
All the downloads are on the download page.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4226712#4226712
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4226712
Temporary queues can take a little time to propagate across the network.
Are you creating a temp queue then immediately sending a message with that
queue as replyTo?
Are you creating a new temp queue for each message sent? (That would be a
classic anti-pattern).
Have you tried sleeping a
I can see from your stack trace that you're using JBoss MQ.
This the JBoss Messaging forum - JBoss Messaging is a different project from
JBoss MQ.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4226909#4226909
Reply to the post :
As many of you will be aware, for some time now Red Hat has had more than one
messaging system implementation in house:
JBoss Messaging - the project based at JBoss, (currently available in the JBoss
EAP and JBoss SOA-P products), and Red Hat Messaging, based on the Apache Qpid
project
desbonns62 wrote : Thanks for your answer timfox,
|
| Yes I have. I wrote a small piece of code that store a certain number of
messages in a buffer before sending all of them in a single JMS message (that's
what I called concatenate).
|
I said transaction, not message.
anonymous wrote
Have you tried sending multiple messages in a single JMS transaction?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4225467#4225467
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4225467
Isn't that in jboss-all-client.jar?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4224783#4224783
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4224783
___
jboss-user mailing list
willmark-
We do not recommend you trying to pull messages out of the JBM internal tables.
JBM internal storage is an implementation detail and liable to change at any
time, making any application that relies on its internal structure brittle.
View the original post :
The correct scripts for any release, including EAP releases are found in svn:
http://anonsvn.jboss.org/repos/messaging/tags
Select your release and click through to find the script.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4224268#4224268
Reply to the
In JBM 1.4 you can use JMS bridges to bridge nodes which are not part of the
same cluster.
In JBM 2.0 you can connect nodes in elaborate ways to form complex topologies.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4224269#4224269
Reply to the post :
I couldn't find this in the user or reference guide.
It's probably in there somewhere but you have no single page html version or
pdf version so it makes it hard to search.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4224271#4224271
Reply to the post :
Andy trawled the user guide and found it :)
However the user guide syntax appears wrong, should be:
| start ignored=true/
| stop ignored=true/
|
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4224276#4224276
Reply to the post :
You can use the JMX interface or a JMS Queue browser to see which messages are
in which queues.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4224359#4224359
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4224359
My guess is the user has a mix and match of different versions on client and
server side.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4224386#4224386
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4224386
I have a bean files declaring several beans. I want MC to inject them into each
other.
I *don't* want MC to call start/stop on the beans, just to inject.
Any ideas how this would be possible, declaratively in the xml..
Cheers
View the original post :
JBM 2.0 beta will be out in a few weeks.
JBM 2.0 does not use JBoss Remoting due to a long string of issues we have had
with it. Instead it has a fully pluggable transport system, and by default uses
Netty, Trustin Lee's NIO transport.
By default this is non blocking, so this should be a non
+1
I believe this is a serious issue and remoting should apply a fix as per the
AMQ fix.
Ron, do you have a JIRA and ETA for this?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4223504#4223504
Reply to the post :
lanceliao1 wrote :
| The remoting guys resolve the problem by setting TCP TTL.This is a ugly way.
JBM 1.x uses JBoss Remoting 2.x, all the transport stuff is handled by JBR so
it's up to the JBR team to fix issues related to tha.
FWIW JBM 2.0 does not use JBoss Remoting at all, it uses
1) You need to say what version of JBM and JBR you are using. Please *always*
state the version when making a post.
2) Please provide your remoting configuration.
3) Have you looked in JIRA? There have been many remoting timeout issues in the
past, all of which, to our knowledge are fixed.
There's already an old JIRA for this somewhere
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4222537#4222537
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4222537
___
jboss-user
Probably you have localhost resolving to 127.0.1.1 in your hosts file
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4221844#4221844
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4221844
Yes this should work, but you should try asking in the JBoss Remoting forum -
this is really a JBoss remoting question.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4221961#4221961
Reply to the post :
This is a classic description of a network partition (split brain) scenario.
JBM 1.x does not have any specific code for preventing split brain from
occurring. For JBM 1.x we recommend mitigating this by e.g. using IP bonding to
reduce the probability of this occurring.
If it does occur,
I asked Phillip from QA who posted that original JIRA what the problem was. He
said it as a configuration issue on his side, but couldn't remember the details.
Those tests are the JBoss AS integration tests. In JBM we have our own tests.
The AS integration tests are run successfully before each
Pooling of JMS connections is handled by the JMS JCA adapter *not* JBoss
Messaging.
The JBoss JMS RA only works in the app server / servlet container, it does not
work standalone. There are other JMS JCA adapters that do work standalone
(google)
If you want XA transactions on the client side,
vandana_awat wrote : this is an old thread but could you please let me know
if we can use the JCA JMS managed connection factory from a standalone java
application ?
I answered this in a post I made a couple of hours ago.
This is also answered on the wiki.
BTW, the best place to ask JCA
To summarise, AFAIK, JBoss JCA currently only works inside the app
server/servlet engine, it does not work standalone on the client side.
I believe the JCA team are currently working on providing a standalone JCA
implementation that will work on the client side, but I'm not sure of that.
The
My initial reaction would be this is not functionality that we have ever
claimed is supported in JBM 1.x.
But if you want to add the new feature then go for it :) If it's tested
properly and has no nasty side effects we can get it in the next CP.
View the original post :
This is probably an AOP problem caused by not having the correct libraries on
the client side.
Please check you have the correct libraries on the classpath as specified in
the user guide.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4220634#4220634
Reply to
Yes, this is the way JBM 2.0 already work (see JIRA).
JBM 1.x is in maintenance only mode, we're not planning on backporting new
features.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4220178#4220178
Reply to the post :
This is a known issue, fixed in JBM 2.0 (see JIRA)
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4220179#4220179
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4220179
___
You should explain what your test does and what your results mean.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4219815#4219815
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4219815
10 requests is nowhere near enough for this to be statistically significant.
You should try again with several thousands (or 10s of thousands) of requests.
Let the test run for several minutes before taking results.
View the original post :
or use the servlet transport. this is documented on the wiki then you can share
the port with other traffic
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4218573#4218573
Reply to the post :
http://www.jboss.org/community/docs/DOC-9632
http://www.jboss.org/community/docs/DOC-9631
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4218574#4218574
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4218574
This has been covered several times on this forum, I'm not going to repeat
myself again.
It's also in JIRA if you care to look for a solution. I am not going to act as
a search engine for people.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4217315#4217315
JBoss AS 4.2.2 does not ship with any esb related stuff.
I guess you are thinking of JBoss SOA platform.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4217334#4217334
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4217334
The JBM user guide is very explicit that should not use HSQL. There are also
wiki pages on this.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4217345#4217345
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4217345
What has JBM security config got to do with JTS? Nothing.
JBM does not use JTS and JTS does not use JBM, there's no dependency so I fail
to see the relevance.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4216879#4216879
Reply to the post :
This is remoting config.
There's a JIRA somewhere which explains how to configure it.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4216565#4216565
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4216565
The CP releases are for use with the EAP not the community version.
If you're running EAP fine, otherwise you should use the latest community
release.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4215607#4215607
Reply to the post :
Did you give each node a unique serverpeerid?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4215157#4215157
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4215157
___
jboss-user
I don't know what you mean by the first attempt to deliver a message is made
sychronously, and what makes you think that is the case.
Also I'm not sure what documentation you're referring to.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4214967#4214967
Reply
We are near to completion on beta.
There was an announcement on the public jboss-dev list a few days ago, but here
it is for completeness:
anonymous wrote :
| The AS 5.1 community schedule has been updated to account for the embedded
console time-line. Essentially an additional month was
JBM 2.0 has management notifications (I guess this is what you mean by
monitoring metrics).
I'd be interested in what specific notifications would be of interest to you so
we can ensure we have them in JBM 2.0
View the original post :
This is all JBoss Remoting config.
Your best bet for questions related to that is the JBoss Remoting forum.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4212554#4212554
Reply to the post :
What you're trying to do is NOTHING to do with JBM clustering, In fact nothing
to do with JBM.
To figure out how to get an MDB on one node to listen to a different server
there are documents on the wiki that explain how to do this.
This is a JCA configuration question and you should ask in the
Yes JBM can to do that, please look at the examples in the distro.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4211126#4211126
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4211126
101 - 200 of 1586 matches
Mail list logo
