Using jboss-messaging 1.0.1CR3 on jboss 4.0.4GA with ejb3 mdb I got the
following Exception:
13:38:20,920 ERROR [ServerConnectionEndpoint] Exception occured
java.util.ConcurrentModificationException
at
java.util.AbstractList$Itr.checkForComodification(AbstractList.java:449)
at
Tim,
basically it's my jms test case (version 2+ ;-)
on a server with 4 CPUs (which I believe is important!)
Unfortunately it happened only once and I was not able to reproduce it so far.
Regards,
Martin
View the original post :
Sounds great. Thanks!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3952584#3952584
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3952584
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully
Tim,
the memory leak becomes visible very quickly with my testcase, it will eat 1-2
MB every minute.
BUT: I didn't try your configuration yet, I can reproduce this reliably on
jboss 4.0.4.GA-patch1 with ejb3 config and jboss-messaging 1.0.1CR2. I will try
with EJB3-RC8 this afternoon and keep
anonymous wrote : Martin - which version of EJB3 are you running?
the one that comes with jboss 4.0.4.GA-patch1. Rumors say it could be RC6...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3952345#3952345
Reply to the post :
anonymous wrote : in PlexMDB, when the message is received it sends 4 more
messages to the topic:
Yes, that is all on purpose: this is where the selectors enter the game!
If you look at the client, it creates consumers (using the selctor) for targets
10 or 20
But the MDB sends one message
Yes, you are absolutely right! Shame on me.
The bad news is, that it seems like I did not 'extract' the testcase
sucessfully or it takes longer for the leak to appear...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3952371#3952371
Reply to the post :
I'am sorry I didn't put a readme in the zip-file, but it's very easy to
reproduce the leak with my testcase, just take a jboss messaging configuration
based on ejb3. Adjust the settings at the beginning of my build.xml to your
needs and run ant (without parameters). The leak will be obvious
Clebert,
did you try my testcase? Can you reproduce the problem?
Best regards,
Martin
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3949276#3949276
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3949276
I have a testcase that replicates it. The cause seems to be a topic selector
whith an OR operator.
I will send the exmaple by email to you, it needs a messaging config based on
ejb3.
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3948095#3948095
Yes, exactly! The OR makes the difference.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3948179#3948179
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3948179
---
All
timfox wrote:
anonymous wrote :
| The most likely cause here is you are sending messages fasting than you are
consuming them, consequently they will build up on the queue or subscription,
until the system runs out of storage for them.
|
Oops, jboss-messaging just let the VM run out of
Yes, it happens with CR2, too!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3947294#3947294
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3947294
---
All the
Both files (messaging-users.properties and messaging-roles.properties) are
there and readable.
The point is: this happens after several thousands of messages have been
sucessfully delivered and suddenly its broken. There is no special event in our
application and jboss is not running out of
Yes. With CR2 it happens always after about 30 minutes.
As I mentioned earlier, the traffic is at about 200 messages per second, there
are topics, queues and ejb3 mdb involved, but no clustering. OS is Linux and
java is Bea jrockit.
View the original post :
It seems to be a memory leak. When we try it with sun jdk 1.5.0_06 instead of
bea jrockit, jboss runs clearly out of memory.
Our applications uses lots of ObjectMessages in both queues and topics.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3947389#3947389
The throughput is about 200 msgs/s (please don't nail me down on this ;-)
On every queue sits an ejb3 mdb, so the messages should get consumed.
Furthermore we don't detect any lost messages.
The size of the messages is several KB.
They are all non-persistent.
DB is mysql.
View the original
Yes, sychronizing fixes the problem!
Thanks a lot!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3946757#3946757
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3946757
After 15 or 20 minutes processing messages without any complaints, our
application suddenly starts throwing jms security exceptions. There is no
visible 'change' in the types of messages that could trigger this, but we have
an avarage traffic of about 200 messages per second.
The effect is on
I get this exception sometimes when the same instance of an ObjectMessage is
delivered to the second or third topic subscriber and tries msg.getObject(). I
am using messaging 1.0.1CR1 on jboss 4.0.4GA-Patch1 with ejb3 profile.
Is there a workaround?
Here is the stacktrace:
anonymous wrote :
Not sure if I can 'extract' the test case from our application...
Can it be a concurrency issue? The consumers are all servlets, to which the
messages are delivered almost 'at the same time'.
In other words, would it help to synchronize on the message?
Thanks!
View the original post :
Ovidiu,
while waiting for jboss-messaging-1.0.1, could you post a ejb3 mdb example for
jboss-messaging here?
Or should my old jboss-mq pojo mdb work right out of the box with
jboss-messaging? What would be the recommended jbossas-version?
Thank you very much!
View the original post :
In RC4/5 there is no more access attribute of the @Entity annotation:
@Entity(access=AccessType.FIELD)
is no longer possible, while it still seems to be in the EJB3-SPEC-PFD??
How can I specify field access??
best regards,
Martin
View the original post :
Hello,
Why is the partition name part of the ejb-clustering annotation?
Suppose there are three clusters: one for integration, one for test, one for
production and each has a distinct partition name. It would not be possible to
'move' the application from integration to test without changing
Can I use jboss somehow with the latest edition of sun's jwsdp (which is 1.6)?
What is the trick? Or does jboss have a 'wscompile' on its own?
thanx,
Martin
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3887892#3887892
Reply to the post :
Thanks for your reply, how do you deploy your webservice? I get exceptions of
missing classes? Have you done any jboss configuration?
Martin
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3887916#3887916
Reply to the post :
26 matches
Mail list logo
