OK I have found a solution!
The deadlocking seems to be caused by this bug:
https://jira.jboss.org/jira/browse/JBAS-5801
As JBoss AS 4.2.4.GA is not available yet, I manually backported the fixes from
the 4.2.4.GA branch into my JBoss 4.2.3.GA sources (building and updating the
jms-ra.rar and
Hello.
We are getting an intermittent exception when our system processes a large
number of JBossMQ messages in parallel. Whenever we get this exception, one of
our Message Driven Beans becomes deadlocked, and never processes any more
messages.
Our scenario is as follows (JBoss 4.2.3.GA,
We have observed a JMS message leak using Seam Remoting to subscribe to a JMS
topic, whereby the list of undelivered topic messages grows indefinitely until
the server ultimately runs out of memory and crashes.
The cause of this seems to be that Seam Remoting requires the web client to
New JIRA issue created:
http://jira.jboss.com/jira/browse/JBSEAM-1250
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4040841#4040841
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4040841
I have upgraded to Seam 1.2.1.GA and still get this exception, however I have
discovered that it appears to only happens when running the server on Windows
XP.
For some reason, running the same application with JBoss on Linux does NOT give
this socket write error exception.
Could this perhaps
I am having exactly the same problems in that I am porting a Seam application
that was working with JAAS FORM authentication to use the new Seam security
code:
anonymous wrote : Seam Security only uses JAAS for authentication, not for
authorization. I'm guessing that your action is protected
I have recently migrated from JBossAS 4.0.4.GA/Seam 1.0.1.GA to JBossAS
4.2.0.CR1/Seam 1.2.0.PATCH1 and am getting a new exception.
My web interface uses Seam.Remoting.subscribe() to asynchronously subscribe to
JMS messages. This functionality is working correctly, however if I navigate
away
Hello.
I am upgrading from JBossAS 4.0.4.GA/Seam 1.0.1.GA to JBossAS 4.2.0.CR1/Seam
1.2.0.PATCH1 and am having an intermittent failure deploying my application.
I am getting the following exception:
| 2007-03-15 16:31:36,968 223172 INFO [org.jboss.ejb3.EJBContainer] (main:)
STARTED EJB:
anonymous wrote :
| Does the problem go away if you eliminate
|
| | preload//preload
| |
| in the CacheLoaderConfiguration section?
|
Yes that seems to have fixed it. I have booted 12+ times now and it has worked
every time.
Thanks!
View the original post :
No worries glad I could help. Thanks for the quick response too btw!
With regard to the JIRA:
anonymous wrote :
| An open question is why there are nodes to be preloaded.
StatefulTreeCache.stop() should be causing them to be deleted, and starting the
cache shouldn't be bringing over any
OK there is DEFINITELY a problem with 4.0.5.GA EJB3 RC9 and
stateful-session-beans!
Anyone can test this -
1. Build the clustering tutorial example that ships with the EJB3-RC9-FD
distribution (jboss-EJB-3.0_RC9-FD\docs\tutorial\clustering) and deploy on
4.0.4.GA in the 'all' configuration -
I am still seeing this NoSuchFieldError: eviction_policy_provider error
deploying @Clustered SFSBs in 4.0.5.GA using both the JEMS installer and by
manually patching an unzipped installation of JBossAS with EJB3 RC9.
However I just noticed this message during the startup log:
anonymous wrote :
I could be wrong, but it seems to me that the EJB 3.0 security annotations are
missing the ability to force an EJB to run using more than one security role.
The @RunAs annotation assigns a SINGLE role to the methods called by a bean,
but what do we do when we want to give a bean MULTIPLE
I am in the process of upgrading from JBossAS 4.0.4.GA (with EJB3 RC8) to
4.0.5.GA (EJB3 RC9).
The problem is that I now get a deployment exception in all Seam SFSBs what use
the @Clustered annotation. These all previously deployed and worked fine fine:
anonymous wrote :
| 2006-11-07
Will do, thanks.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3983637#3983637
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3983637
___
jboss-user mailing list
I am in the process of upgrading from JBossAS 4.0.4.GA (with EJB3 RC8) to
4.0.5.GA (EJB3 RC9).
The problem is that I now get a deployment exception in all Seam SFSBs that use
the @Clustered annotation. These all previously deployed and worked fine fine:
anonymous wrote :
| 2006-11-07
Hello.
Since upgrading from EJB3 RC8 to RC9 on JBossAS4.0.4.GA, I am getting a new
exception with jBPM in code that was previously working fine (using both jBPM
3.1.1 and jBPM 3.1.2).
The exception I am getting is unusual (full exception trace shown at the end of
this post):
anonymous wrote
17 matches
Mail list logo
