To answer my own question, it seems that removing the second login-module
eliminated this issue.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3880704#3880704
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3880704
---
Cheers Scott. You are of course correct. My misunderstanding about Form Based
Authentication (RTFM!).
Interestingly once I got past this, the first call to any secured EJB would
generate an insufficient permissions for principal [mikeh] error to occur. A
second call to the EJB container and
I hate to type this, but I?m having issues with JAAS caller principal
propagation.
For what it?s worth, I am running 3.2.6 with a DatabaseLoginModule configured.
I added the ClientLoginModule bit after reading some of the other posts here.
Needless to say, I've tried removing and relocating
You are proably caching a shared resource as an instance variable. Try making
your instance variables transient
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862329#3862329
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply
Shouldn't you be looking up as jnp://se.rv.er.ip:1099
?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3828841#3828841
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3828841
-
Jboss 3.2.4 rc1
JDK 1.4.2
I have 2 beans:
The first (BeanA) contains a Collection of data and is an Entity Bean
The second (BeanB also an EntityBean) is an aggregator of the Collections obtained
from one or more BeanA's located by findByPrimaryKey
Both beans have the "Supports" Transaction Attr
