Delivery Status Notification (Failure)
by postmaster@lists.jboss.org
This is an automatically generated Delivery Status Notification.
Unable to deliver message to the following recipients, because the message was forwarded more than the maximum allowed times. This could indicate a mail loop.
contactyuriy.khanyuriy.khan(a)technodom.kz
18 years, 2 months
[JBoss jBPM] - Re: Substitution arrangement for impeded actors
by holly77
Yes, of course...
But this way I'd have to do the reassignment each time manually.
What I'm searching for is a more flexible, powerful solution for this problem.
So what you definetly need is a database, rule engine, etc. you can get a or a list of proxy actors from for the currently assigned actor.
These the task would then be assigned to, when the task is not being processed for a certain period of time, or whatsoever reason.
For sure this can be done in jBPM using actions, timers, etc.
But as it is a common problem, I thought there would be a generic solution, I could adapt and use, not having to reinvent the wheel...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151354#4151354
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151354
18 years, 2 months
[Microcontainer] - Re: Get at Kernel from Unmanaged Object
by ALRubinger
"alesj" wrote : Couldn't you just make this JNP server MC aware, some wrapper, and then with the help of some interface push that handle further.
| Naming should be configurable, I remember having naming -service.xml somewhere.
Let's shelve my one concrete example, for now I have several. :)
What, in your view, is more friendly?
1) Decorator Pattern for anything wishing to leverage MC
2) Kernel is transparent, but available, to anything in the process
Security concerns aside for the moment, I'm asking that a Kernel be able to be looked up from a POJO. Is that contrary to the aims of the MicroContainer project? How powerful a feature it'd be.
S,
ALR
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151353#4151353
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151353
18 years, 2 months
[Security & JAAS/JBoss] - 'sufficient' loginmodules combined with ClientLoginModule
by pieter.kuijpers@gmail.com
I have the following requirements for my web application running on JBoss 4.2.1:
- Users should be authenticated against an LDAP directory
- In LDAP, a user is registered in one of two locations, say ou=A or ou=B. So, the DN for a user might be uid=X,ou=A or uid=X,ou=B
- I need to perform programmatic web authentication
The solution I have come up with is to use two LdapLoginModules: one for each location. Both login-modules are set to 'sufficient'.
| <login-module code="org.jboss.security.auth.spi.LdapLoginModule" flag="sufficient">
| <!-- regular options omitted -->
| <module-option name="principalDNPrefix">uid=</module-option>
| <module-option name="principalDNSuffix">,ou=A</module-option>
| </login-module>
| <login-module code="org.jboss.security.auth.spi.LdapLoginModule" flag="sufficient">
| <!-- regular options omitted -->
| <module-option name="principalDNPrefix">uid=</module-option>
| <module-option name="principalDNSuffix">,ou=B</module-option>
| </login-module>
|
This works as expected: authentication succeeds if the can be authenticated against one of the two LDAP locations.
To propagate the authentication info to the container, I use the ClientLoginModule as mentioned in the SecurityFAQ. This is added as the third loginmodule in my configuration:
| <login-module code="org.jboss.security.ClientLoginModule" flag="required">
| <module-option name="restore-login-identity">true</module-option>
| <module-option name="multi-threaded">true</module-option>
| <module-option name="password-stacking">useFirstPass</module-option>
| </login-module>
|
What I want is that authentication fails when both Ldap loginmodules fail. In reality, authentication succeeds in that case, because the ClientLoginModule always succeeds. Thus, I have the two 'sufficient' ldap loginmodules fail, and the 'required' clientloginmodule succeed, resulting in a successful login.
Is there a way to enforce that (at least) one of the ldap loginmodules succeed, and that the clientloginmodule is still invoked for a successful login?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151352#4151352
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151352
18 years, 2 months
[Installation, Configuration & DEPLOYMENT] - Life cycle of sessions .ser files in tmp in JBoss-4.2.1.GA
by korlam
Hi,
My understanding on .ser files in tmp/sessions folders goes like this:
1. When the beans are created at first instance, the folders are created in sessions folder of tmp (jboss-4.2.1.GA\server\default\tmp).
2. When passivated they are written as .ser files
3. When activated these .ser files were read
4. When the server is shutdown (or the ear is re-deployed) then the sessions folder is cleaned and gets deleted
Please correct me (or point me towards docs) if my understanding is wrong.
Now, my issue is:
We have a performance tracker (KEYNOTE) on production server for our application. With this tool enabled, found that .ser files keep increasing in the respective bean folders and taking away the full disk space in matter of couple of days.
NOTE - Without this tracker, things are fine. Every JSP page in our application invokes and removes the beans.
Can anyone please explain about the sessions folder - when do the folder(s) with bean name are created with .ser files, when they are updated and deleted.
Thanks & Regards.
Korlam.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151348#4151348
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151348
18 years, 2 months