Subject stack grows infinitely in SecurityAssociation when timer is called.
Memory allocated to stack is never freed, which is a memory leak that after a
while leads to OutOfMemory condition.
I tried to run the following code in JBoss 4.2.3 GA as well as in Branch_4_2.
I can see that the objec
Because of isolated classloading problems with several applications in the same
container I have to avoid injecting EntityManager via a @PersistenceContext
annotation.
I tried to use the following code in my stateless bean:
| private EntityManager em;
|
| @PostConstruct
|
Forgot to mention that Seam version that was used in the previous test was
1.2.1 GA
Now, I have tested deploying seam-booking demo from Seam 2.0.0 CR1, and the
problem does not appear any more.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092441#4092441
R
I found out that the described effect occurs when JBoss is started with Sun's
jdk1.5.0_12 JVM. Running it with JRockit 1.5 or with Sun's jdk1.6.0_2 does not
lead to this problem.
Debugging of NameScanner have shown that the method getPackage() cannot obtain
a package info.
| protected Pa
I stepped into the same problem trying to run the Seam booking example. Then, I
followed an advice of Michael Yuan:
http://www.michaelyuan.com/blog/2007/05/29/seam-book-examples-updated-to-jboss-as-420-ga/
anonymous wrote : Note: Evidentially, the Seam security package still has some
residue depe
"saeediqbal1" wrote : Is it safe to use JRockit with Seam?Thanks.
What is "safe"?
I'm using JRockit with Seam, it works. It cannot solve memory leak problems
that exist in your application, container or libs though.
JRockit survives longer if a ClassLoader is leaking because it holds all
alloc
I experimented hot deploying jboss-seam-booking demo to the standard
installation of jems-installer-1.2.0.GA (JBoss 4.0.5)
I tried Seam 1.1.6.GA and 1.2.1.GA; in both cases I observed growing allocated
PermGen memory, a growing number of loaded classes, and finaly OutOfMemory.
View the original
"holtak" wrote : we also had PermGen problems
|
| Can confirm that JRocket helps with PermGen problems.
|
| You could try SUN JVM 1.6.0 update1 - it suspiciously works here untill now
but maybe the server wasn`t just stressed enough and there seams to be no
significant change in the SUN
When STATE_SAVING_METHOD=client, Trinidad blocks delegating calls to
saveSerializedView() in SeamStateManager, which makes that conversations
propagation does not work. Conversation context cleanup is never triggered.
I filed a bug to Trinidad's JIRA:
http://issues.apache.org/jira/browse/ADFFAC
I think I had a similar problem when I first tried to use JSCookMenu with Seam
and Facelets. The problem though appeared not to be about Seam, it was Facelets
instead. You have to explicitely declare all Tomahawk components if you use
Facelets. See MyFaces Wiki:
http://wiki.apache.org/myfaces/U
I got the thing working when I replaced the bundled Facelets version with the
latest one, which is 1.1.11. Replacing MyFaces 1.1.3 with 1.1.4 did not solve
the problem. It looks as, even if this is supposed to be a MyFaces bug,
Facelets cures it.
View the original post :
http://www.jboss.com/i
11 matches
Mail list logo
