Wonder if someone knows some sort of design pattern for security in a system where
Tomcat and Jboss are on different hosts (JVMs). My story is:
We setup Tomcat and Jboss on different hosts. Associated with the web content, we have
certain roles/permissions setup. The dynamic part of those Web co
Scott,
You are right about my assumption and that's also my fear. So, I'll back to the
hard-coded way.
As for JINI security model, I do not have one in particular. In our case, we just use
standard JAAS as
- get a LoginContext
- login
- get subject
- call Subject.doAs...(...)
Thanks,
JD
View
Will this work?:
1. Configure the EJB (let's call it SBean) which access remote server thru RMI with
security checking.
2. Configure all other EJBs which access the SBean with a security-identity/run-as
role-name
3. Setup a special security domain for the specified role
The main assumption is
Our EJB application need to access another server thru RMI call (JINI in exact) by
using standard JAAS (we're using certificate). Seems I have a couple options, can
someone please tell me which one is feasible and how,
1) Hard-code JAAS login and acquire Subject, then put all RMI call in privile
Or, the most part of 400M are messages, then processing logic kick in which begins to
comsume the heap left.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3830987#3830987
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3
Thanks for providing "definite" answers.
For question 3, we are using MySQL as persistence manager, and water marks are set
properly (350/400) I think for Xmx1024.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3830981#3830981
Reply to the post :
http://www
Browsing all kind of forums and official JBoss document, we still cannot find answes
for certain questions. Please help.
1. jms-ds.xml
The JMS provider is configured as
DefaultJMSProvider
org.jboss.jms.jndi.JBossMQProvider
java:/XAConnectionFactory
java:/XAConnec
Start the Jboss 3.2.3 from fresh installation, everything is fine (and I can open
jmx-console).
I then deployed one of my web application, sample.war
restart the jboss, when I try to open the jmx-console, I got the following error.
Any idea on why this is happening? (I do not have this problem
>From Sun J2EE API, it's seemingly saying that you do not need to close a QueueSession
>if you are closing a QueueConnection.
Is this true in JBoss? Seems someone is saying I have to close those QueueSession
before closing QueueConnection.
BTW, I am investigating two issues related to JMS in JB
Can someone please tell us where I can find the change note (or release note) between
3.2.1 and 3.2.3.
We are interested in what kind of bugs are fixed.
Especially the bugs related to the following exceptions:
1)
java.sql.SQLException: The database is shutdown in statement [DISCONN
ECT]
10 matches
Mail list logo