Please state what versions of JBM and JBR you are using when making a post.
Without that information no one will be able to help you.
Please also ensure you have the correct versions of JBM and JBR on both the
client and server side (as explained in the user guide).
Also please paste a java
Next time it occurs, please get a kill -3 thread dump, and we'll take it from
there.
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4150333#4150333
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4150333
Can you get the stack using kill -3 please (or CTRL-BREAK on windows)?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4150338#4150338
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4150338
I am failing to understand what this thread is about.
JBM fully supports all ordering semantics as defined in the JMS spec.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4150052#4150052
Reply to the post :
That should certainly never happen.
JBM will (as per JMS spec) always deliver messages in the order they were sent
from a particular producer.
Please post a simple test case demonstrating the issue. Also please mention
what version of JBM you are using.
View the original post :
If you create a non durable subscriber it will only receive messages that are
sent while that subscriber exists. That is *as per JMS spec*.
If you want to receive messages that were sent while the subscriber is not is
connected, you need to use a durable subscriber.
Again, I would suggest
You can't configure JBoss Messaging to prevent your firewall closing
connections!
If your firewall decides to close connections then no application can stop it -
if it could it would be a pretty useless firewall (think of the exploits).
You need to read your firewall manual and find out how to
Please see my previous comment, here it is again :)
anonymous wrote :
| JBM doesn't support clients in applets or other restricted sandboxes (like
webstart), this is because JBoss Remoting (which JBM 1.x uses) doesn't support
this.
|
| This is being fixed in JBoss remoting 2.4.0, see
What has this got to do with JBoss Messaging?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4149899#4149899
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4149899
___
jboss-user
This question is completely impossible to answer since it is totally subjective
and lacks any meaningful information.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4149900#4149900
Reply to the post :
anonymous wrote :
| Thank you very much Tom, that helps.
No problem ;)
By the way, my name is Tim, not Tom
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4149901#4149901
Reply to the post :
Not sure why you would need to patch JBM.
AFAIK this is a JBoss Remoting issue.
You should post this in the JBR forum so they are aware of this.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4149913#4149913
Reply to the post :
Perhaps you should ask your firewall manufacturer or read your firewall manual?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4149733#4149733
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4149733
scotthkao wrote : I read from the online document somewhere that one
distinctive added feature of JBoss Messaging(JBM) is transparent failover, i.e.
failover without the client-side code to handle connection exception. But I
just wonder that could there be any message lost during the
JBoss Messaging does not use CORBA as a transport.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4149317#4149317
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4149317
___
genman wrote : But maybe you could use Corba from an MDB? I don't know if
that's technically the messaging system talking to legacy code.
|
Yes, maybe (IIOP), but that's not a JBoss Messaging question, that an EJB
question :)
View the original post :
scotthkao wrote : So, the transparent failover of JBM can be turned off in
the xml configuration file?
| [/quote}
|
| Yes, this is covered in the user guide:
|
JBM doesn't support clients in applets or other restricted sandboxes (like
webstart), this is because JBoss Remoting (which JBM 1.x uses) doesn't support
this.
This is being fixed in JBoss remoting 2.4.0, see JIRA:
http://jira.jboss.org/jira/browse/JBREM-978
View the original post :
I would check you have the correct version of JBoss Remoting on *both* the
client and server side. The remoting jar should be on the client classpath
before any other entries (see userguide).
The same version should be on both the client and server side.
View the original post :
harish43 wrote :
| 1. Lookup /ConnectionFactory
| 2. Lookup Queue
| 3. Create Connection
| 4. Create Session
| 5. Create Producer
| 6. Create Text Message
| 7. Send message
| 8. Create Consumer
| 9. Start the connection
| 10. Receive text message
| 11. Close connection
|
harish43 wrote : I
|
| 769946 .. 168189k . char[]
| 2814906 . 98961k .. java.util.HashMap$Entry
| 936726 .. 88564k .. java.util.HashMap$Entry[]
| 2008055 . 54907k .. java.lang.String
| 936446 .. 51211k .. java.util.HashMap
| 434925 .. 25114k .. java.lang.Object[]
| 634584 ..
Adding a FK constraint is not recommended.
If you read the JIRA you will notice in a later comment I say Am 99.9% sure
this is due to using a non transacted datastore so closing. In other words the
FK comment is a *red herring*
Also, you didn't mention what version of JBM you are using...
If you can produce a step by step description of how to replicate this issue we
can re-open the JIRA and take a look.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4148767#4148767
Reply to the post :
Right, 1.4.1 is for JB 5 only - maybe you can get it to work with JBoss 4.x,
maybe not.
Once we've got JBM 2.0 alpha out we'll release another stable version for 4.x
(where x =2), probably in the next coupld of months, depending on resources.
View the original post :
ssjboss wrote : please try this
|
| qbrowser = qsession.createBrowser(queue);
| Enumeration e = qbrowser.getEnumeration(); // gets list of messages.
|
| while (e.hasMoreElements()) {
|// counter variable
| }
|
| ---
| SS
That's really not a good idea -
Read the stack trace!
anonymous wrote :
| Caused by: java.lang.NoSuchMethodException: src.service.Listener.()
|
It's saying you haven't defined a default constructor in your class.
I suggest you do a little more research before posting on this forum :)
View the original post :
tnine wrote : I haven't forgotten about this, but I have had to put it off
while working on production issues. I'm now reading from the DLQ, however I'm
getting very erratic behavior. Somtimes a read with receiveNoWait will
return messages on the DLQ, other times I'll have to call it 4 or 5
Please post post JBoss MQ questions on the JBoss MQ forum, not the JBoss
Messaging forum.
See sticky post at the top of this forum,
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4146978#4146978
Reply to the post :
Actually, that datasheet is pretty out of date now.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4146979#4146979
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4146979
___
harish43 wrote : I am not certain whether we are using the JCA connection
pool. Assuming that we are not using the connection pool is there a fix for the
issue mentioned by Kevin Conner?
It's slightly worrying that you don't know if your using the JCA managed
conection factory or not, since
The stack trace shows this is in jboss remoting. Have you tried asking in the
jboss remoting forum?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4146991#4146991
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4146991
Please do as Jeff has suggested, also please stop spamming this list with
annoying messages about basic JNDI.
If you do not understand how to use JNDI I would suggest buying good JNDI book
or doing one of the surely many tutorials on line.
After that, if JBoss JNDI is not working for you, try
If you're using the JCA connection pool as you say, then the old problem should
never occur since the JCA layer will cache connections.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4146784#4146784
Reply to the post :
chip_schoch wrote : Thank you Andy and Clebert for taking the time to explain
this in detail. To reiterate, what you are saying is that if I need to have
multiple consumers processing messages from a clustered queue in FIFO order,
than I should have all my client consumers connect to the same
Short answer - don't use 1.3.0.GA.
I believe this was fixed ages ago - look in JIRA and you should find the report.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4144220#4144220
Reply to the post :
jmesnil wrote :
| The load balancing is not a true round robin: the local node is always
favored if it can consume messages.
| This avoids unnecessary network hops to send the message to another node if
it can be consumed locally:
|
|
To elaborate on what Clebert has already said - also I think this has been
covered before on other threads.
JBoss Messaging has connection load balancing - this means that if you use a
connection factory with the attribute supportsLoadBalancing set to true, then
subsequent create connection
chip_schoch wrote : Isn't what I posted a stack trace? We have been looking
into this and it seems that there is a firewall that is between the client and
the server that drops connections that are inactive for a certain period of
time.
|
| I am not sure what other stack trace you are
It seems like your real requirement here is to ensure that all messages from a
queue are processed by only one consumer.
Limiting consumers is one solution to that problem, another more flexible way
is message grouping - which guarantees that messages in a specific group always
get processed
The way message grouping would work is as follows:
Before you send a message you set a special header on the message - not sure
what it is going to be called yet, but let's call it GROUP_ID for now.
Before JBM delivers the message to a consumer, it checks if the GROUP_ID header
is present, if
dsmiley wrote : If group_id is not specified by the clients that connect then
where is it specified? (i.e. how do I set REDHAT_STOCK in your example)
|
Sorry, to clarify, GROUP_ID is specified by the sender (consumer id isn't)
anonymous wrote :
| I tend to think my suggested
This is a known issue http://jira.jboss.org/jira/browse/JBMESSAGING-924 which
was fixed about a year ago.
It's also discussed here:
http://jboss.com/index.html?module=bbop=viewtopicp=4028694
Moral of the story: If you have a problem always search the forums and JIRA
first to see if it's
If a consumer is closed (is that what you mean by destroyed?), before the
session is acknowledged, then the messages won't be visible to any other
session until the session commits/rolls back.
This is normal JMS operation.
Can you be more specific about
a) What you are doing
b) What you
FullSize is the maximum number of messages to hold in memory for that queue at
any one time
PageSize is the number of messages to to load from disk in one go
So yes, pageSize must be less than downCacheSize
View the original post :
Stack trace please?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4140352#4140352
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4140352
___
jboss-user mailing list
If you have consumed messages via a message consumer and then roll back, the
same session will receive the same stream of messages.
This behaviour is as specified in the JMS spec. (1.1, sectons 4.4.7 and 4.4.11)
If you have the same message consumer(s) open on that session, then it will
rlucente wrote : I read the JMS spec but I didn't really see the description
of a session/message affinity at rollback.
|
4.4.7:
... If a transaction rollback is done, its produced messages
are destroyed and its consumed messages are automatically recovered. For more
information on
Hello all-
We've started up a new public IRC channel for JBoss Mesaging related chat.
It's here:
#jbossmessaging at irc.freenode.net.
See you there :)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4140259#4140259
Reply to the post :
kgreiner wrote : I
|
| Should SimpleMessageReference directly reference the message or a key into
the SimpleMessageStore?
|
|
Yes, it should reference it directy
[quote}
Should I be setting FullSize and/or DownCacheSize? Documentation for either is
rather lacking right now.
View
subrata_jboss wrote : Thanks it works.
|
| if several client using several queue , restarting all the queue will cause
| some problem.
The unit of redeployment is the file. So if you want to redeploy different sets
of queues separately you can put them in different files.
BTW this is no
In that version a database is required for persisting queue/topic information
as well as message data.
If you're not persisting message data you could just use a simple database like
HSQL for persisting your queue/topic information.
In the next 1.4 release there will be a null persistence
test
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4139450#4139450
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4139450
___
jboss-user mailing list
jboss-user@lists.jboss.org
test2
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4139498#4139498
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4139498
___
jboss-user mailing list
jboss-user@lists.jboss.org
Can you post the configuration for the datasource you are using?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4138869#4138869
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4138869
What version of JBM are you using?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4138870#4138870
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4138870
___
jboss-user mailing list
I can see you're using an XA datasource.
JBM needs a non XA datasource to function.
You can find an MSSQL non xa datasource example in docs/examples/jca of your
app server distribution.
There have been a few other threads about this on this forum before, it's
probably worth a search
View the
How many nodes did you start with, and how many did you failover?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4138911#4138911
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4138911
One more question:
How many connections and sessions do you have attached to each node when
failover occurs?
Do you see the same problem if you failover with no jms connections using the
nodes?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4138915#4138915
Can i confirm you have no MDBs or any other consumers on the nodes?
Also can you confirm which version of JBoss remoting you are using?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4138943#4138943
Reply to the post :
Ok, I think I know what is going on here. I should have it sorted by the end of
the week.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4139051#4139051
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4139051
http://jira.jboss.org/jira/browse/JBMESSAGING-1266
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4139052#4139052
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4139052
___
[Moved from JBoss Messaging user forum]
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4138668#4138668
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4138668
___
jboss-user mailing
jeuk wrote :
| Any ideas?
You didn't start the connection:
| connection.start();
|
java.sun.com provides a good JMS tutorial which goes through the basics, I
suggest trying it out. :)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4137472#4137472
See the log4j site for how to configure log4j.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4137502#4137502
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4137502
___
jboss-user
I have added this task for someone to investigate whether this is a real issue
or not:
http://jira.jboss.org/jira/browse/JBMESSAGING-1249
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4136532#4136532
Reply to the post :
[Moved thread from design forum]
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4136542#4136542
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4136542
___
jboss-user mailing list
Dave, take a look at http://jira.jboss.org/jira/browse/JBMESSAGING-1245, maybe
it explains your issue?
Regarding batching, have a look at how the JBoss Messaging bridge does it. It
uses onMessage(), and you can configure batches to have a maximum number of
messages and/or a maximum time.
View
If you use a connection factory with enableFailover set to true, then when an
exception occurs it will automatically try and reconnect to another server, so
you won't get the exception unless it can't reconnect.
See user guide
If you don't want automatic failover then set to false and you will
Hello Dave-
Can you provide instructions on how to replicate the issue and we'll make sure
someone investigates it further?
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4135580#4135580
Reply to the post :
One thing that strikes me: You say you're using consumer.receive(1000) to
receive messages from the queue.
Are you saying you are polling in a loop? Any reason you don't use a
MessageListener?
What happens if the call to receive(1000) returns with null - this is perfectly
possible even if
That code doesn't look valid to me.
The call to receive(1000) could legitimately return null even thought there are
messages in the queue. This would cause it to break out of the loop and process
the batch.
Is this what you want?
You could just do the same code in a message listener surely?
Looking at http://jira.jboss.org/jira/browse/JBMESSAGING-1245, I believe I can
see a potential race condition which might give the behaviour observed.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4135600#4135600
Reply to the post :
Wickus:
I have inspected the code and I believe I can see potential for a race
condition, more here http://jira.jboss.org/jira/browse/JBMESSAGING-1245
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4135599#4135599
Reply to the post :
Due to the non deterministic nature of thread scheduling this is hard to
replicate since it requires, the call to changeRate to come in at that specific
point, AFAICT this will only happen after the consumer is first created, so the
condition is far more likely to occur if you are creating and
czar_iv wrote : PeterJ,
|
| What version of JBoss messaging are you using
| I am using 1.4.0.SP2.
That's strange.
JBoss AS 5.0 beta 4 comes *pre-installed* with JBoss Messaging 1.4.1.beta1 (see
http://anonsvn.jboss.org/repos/jbossas/tags/JBoss_5_0_0_Beta4/build/build-thirdparty.xml).
czar_iv wrote : ok, I am obviously new to JBoss and JBoss Messaging; I was
trying the examples from JBoss Messaging 1.4.0 SP1. I'll download JBoss
Messaging 1.4.1 beta 1 and try those examples. Thanks!
You don't need to download anything apart from the app server.
If you are using JBoss 5,
rexer wrote : So can anybody see any obvious problems with my experimental
code I posed in my original question?
|
| Sounds like most of you have tried annotations instead of using XML. Are
those generally more reliable?
|
| I'll try to find the examples you folks are referring to.
mpr_prabhu wrote :
| However would consider this as a defect in JBM as I expect it to handle it
more gracefully and clean up expired messages or ensure these do not affect new
messages
|
The JMS spec only requires that expired messages are never received by a
consumer. It does not
There's no such release as JBoss Messaging 1.4.1.SP1.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4134139#4134139
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4134139
___
Wickus -
Can you clarify what value of prefetchSize and slowConsumers you were using
when you saw the problem?
Just to be clear- you're saying that the with the default values its ok, but
when you change them to your values you get the problem?
View the original post :
Sorry, I'm a bit confused.
So, you're saying you saw the problem with the default, out of the box values,
with no changes?
What values do you need for your system - do you need to change the
prefetchSize or slowconsumers?
View the original post :
I want to try and replicate this on this end.
Can you give me more information on your setup? Size of messages, number of
messages, number of consumers etc etc. so we can replicate something similar?
And what I should do to replicate?
Looking at the code the only time consumecount gets
Does the same problem also occur with 1.4.0.SP3?
Can you also ensure you are using JBoss Remoting 2.2.2.SP4?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4134471#4134471
Reply to the post :
http://jira.jboss.org/jira/browse/JBMESSAGING-1245
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4134474#4134474
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4134474
___
Did you manage to successfully run the examples, including the clustering
examples?
(See user guide)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4133820#4133820
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4133820
Sounds like your installation failed.
Did you follow the installation instructions in the user guide exactly?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4134023#4134023
Reply to the post :
There was another thread on this forum recently which explained what libraries
you need to use for JBoss 5, please have a search.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4134021#4134021
Reply to the post :
There have been several other threads about receiveNoWait semantics on this
forum.
Please have a search.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4134024#4134024
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4134024
Yes, I believe this has been fixed since the version you are using.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4134053#4134053
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4134053
navjeetc wrote :
| How about my other question about JMS provider jndi url setup?
|
There is a wiki page on how to set up bridge for remote providers:
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4134067#4134067
Reply to the post :
Hello Wickus-
Can you ensure that you upgraded to remoting 2.2.2.SP4 on both client and
server side?
We had a few issues reported that sounded like this when remoting wasn't
upgraded to 2.2.2SP4 everywhere in the system. Remoting 2.2.2.SP4 is not
compatible with earlier versions.
View the
I would check if you are creating a lot of sessions somewhere and not closing
them.
Common causes would be creating a connection, session, sending a message etc
from inside an ejb, but not using the JCA managed connection factory at
java:/JmsXA
View the original post :
It means you're trying to send a message on a closed session which is illegal.
Try and find where in your code the session is being closed. A common
possibility would be you have an exception listener which closes the connection
(which closes the session).
View the original post :
I have started a new messaging blog here http://jbossfox.blogspot.com :)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4133487#4133487
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4133487
Personally I wouldn't bother with the installer, but install using the
instructions in the user guide.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4132868#4132868
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4132868
sams wrote :
| Evidently when JBoss creates the MDB, it create's the MDB's Message
Listener from a Session that was created from a standard ConnectionFactory
instead of the ClusteredConnectionFactory. I have not seen a setting in any of
the config files so far to change this, so it may be
For those of you who couldn't make it to JBoss World last week, the
presentations are now online:
http://www.jbossworld.com/downloads/presentations/
Be sure to check out the JBoss Messaging presentation - it mainly goes into
what's new in JBM 2.0
View the original post :
Well.. topics don't hold on to messages, so it wouldn't make sense to browse
them.
You can create multiple subscriptions on a particular topic, and it might make
sense to browse them but JMS doesn't provide any such functionality.
However with JBM you can use the JMX management interface to
There should be documentation on the stompconnect site about this.
I haven't actually tried this myself
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4131548#4131548
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4131548
wow that's an old version :)
Have a look through JIRA. It's more than likely that was solved in a later
version.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4131546#4131546
Reply to the post :
501 - 600 of 1586 matches
Mail list logo
