I think that starting with JBoss 3.2.3 the CMP engine has undergone more or
less drastic changes in order to accommodate more and more performance tuning
switches. I have the _impression_ that as a side-effect JBoss does not honor
some settings in standardjbosscmp-jdbc.xml anymore.
We managed
"[EMAIL PROTECTED]" wrote : run-as sets the role of the caller, but if there is
no authenticated caller, then the security domain receiving the call has to all
unauthenticated callers. run-as is a grant of a role, not identity.
|
Yes, I figured that out. So if I mark an MDB with run-as="myrole
OK, I know this is probably a stupid question, but I need some answers before I
go on wasting my - and my employers - time.
Our applications SBs are secured using an LDAP realm with no
unauthenticatedIdentity allowed. Now I have got an MDB with the run-as
attribute set to a role with sufficient
Thanks,
I'll have a look into the docs.
Olaf
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870198#3870198
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870198
--
We would like to deploy two versions of the same Oracle jdbc driver. We are
running against an Oracle 8.0.6 and a 8.1.7 instance. In order to use blobs we
have to use a fairly recent driver for the 8.1.7 instance. Unfortunately, this
driver has issues when reading metadata from a certain table i
I was wondering why JBoss kept trying to create those JMS_* tables on startup
although I set CREATE_TABLES_ON_STARTUP to FALSE both in
oracle-jdbc2-service.xml and oracle-jdbc-state-service.xml. I had a look into
the JBoss-3.2.6 sources and found that the
org.jboss.mq.pm.jdbc2.PersistenceManage
As (nearly) always, it was my fault ;-) Just realized that the only select
statement issued after caching those attributes where those looking up the
relevant primary keys. Afterwards, no attributes are loaded, just as expected.
Cheers,
Olaf Bergner
View the original post :
http://www.jboss.o
We are working on optimizing our CMP layer, currently experimenting with commit
option A. Our data layer heavily uses attributes which may be attached to
nearly all our entities. These attributes - or rather the initial set of
attributes to choose from - are read-only and marked as such.
What p
Recently, we are observing that most finder queries take exceedingly long to
finish. Looking for the reason we have switched on cmp logging and found that
relations are loaded column by column:
| Executing SQL: SELECT id, salutation FROM PERSON WHERE (id=?) OR (id=?) OR
(id=?) OR (id=?) OR (
"triathlon98" wrote : You need to properly configure your load groups.
|
| Check out the Jboss administration docs for more details about CMP data
loading settings and implications.
|
| Joachim
Thanks for the answer. That is exactly what I have been doing all day. We
haven't declared a
I just added a - very short - FAQ to the JBossMQ WiKi.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865029#3865029
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3865029
--
OK, I found the solution. I had to add
|
|
|
to the stack of configured login modules. Judging from a quick survey via
Google, I have the impression that this is a problem plagueing many JBoss
users. So an FAQ might be in order?
Olaf
View the original post :
http://www.jboss.org/inde
I am trying to deploy an MDB which needs to access some secured SLSBs. The MDBs
'run-as' attribute is set to the name of a valid role with sufficient
permissions.
I have no problems acquiring a reference to a SLSBs local home, but each time I
try to call a method on it I get
| java.lang.Secu
Does JBossQL support the binary & operator, i.e. is something along the lines of
| SELECT OBJECT(c) from CUSTOMER c WHERE ((c.flags & 16) > 0)
|
possible? This would shrink the resultset from currently roughly 7000 - which
JBoss cannot handle - down to ca. 40.
If it's not directly expressib
14 matches
Mail list logo
