[Design of JBoss jBPM] - jBPM design patterns question
by rwallis
Hi I new to the forum but have been using jBPM for a bit now (and loving it). I have a couple "design pattern" questions to ask.
1) Should jBPM be used as a "fancy" server side batch processor/scheduler where the token recurses from one processing node to a decision node and then, based on the decision, back to the processing node using a timer thats set at some interval like 1 minute? Will this cause stack overflow problems eventually? Will this cause the log file to get ridiculously large?
2) What is the practical limit of child token hierarchy levels? In other works if a fork is used to send a token back to the node it came from and parallel another token to a different node (resend algorithm), what limit should be put on the resend (or should this algorithm simply not be used), before the child tokens get to be too many and stack over flow occurs?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227269#4227269
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227269
16 years, 11 months
[Design of POJO Server] - Re: Caching of classes in BaseClassLoaderDomain
by bstansberry@jboss.com
Dominik is running the EJB3 perf tests and while it's early, he reports that "but the app is running, and it's running much much faster :)"
The "but" above is because there are CNFE problems at server start; look to be due to webapps being unable to load classes from the domain. Key server.log snippet:
| 2009-04-28 10:43:38,715 DEBUG [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) injectionContainer enabled and processing beginning
| 2009-04-28 10:43:38,716 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/admin-console]] (main) Error configuring application listener of class org.jboss.web.tomcat.security.SecurityFlushSessionListener
| java.lang.ClassNotFoundException: org.jboss.web.tomcat.security.SecurityFlushSessionListener
| at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
| at java.security.AccessController.doPrivileged(Native Method)
| at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
| at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
| at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
| at org.jboss.web.tomcat.service.TomcatInjectionContainer.newInstance(TomcatInjectionContainer.java:262)
| at org.jboss.web.tomcat.service.TomcatInjectionContainer.newInstance(TomcatInjectionContainer.java:256)
| at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3859)
| at org.apache.catalina.core.StandardContext.start(StandardContext.java:4393)
| at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:310)
| at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:142)
| at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461)
| at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118)
| at org.jboss.web.deployers.WebModule.start(WebModule.java:97)
The SecurityFlushSessionListener class is located in server/all/deploy/jboss-web.sar/jboss-web-service.jar.
Above is immediately followed by same thing 3 more times for other classes:
java.lang.ClassNotFoundException: org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
java.lang.ClassNotFoundException: com.sun.faces.application.WebappLifecycleListener
java.lang.ClassNotFoundException: com.sun.faces.config.ConfigureListener
Same thing happens on ROOT.war and jmx-console.war.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227267#4227267
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227267
16 years, 11 months
[QA of JBoss Portal] - Problem with Tomcat SSO valve while being in 'Admin' role bu
by mposolda@redhat.com
I have a question about Tomcat SSO Valve. I have a JBoss-4.2.3.GA with JBoss Portal 2.7.2 from branch and I did this scenario:
1) I changed the security settings of default portal, so only admin can see it. ('View recursive' and 'Personalize recursive' permission to Administrators). So the access to http://localhost:8080/portal needs authentication and needs to be authorized as admin.
2) I enabled the Tomcat SSO valve in $JBOSS_HOME/server/default/deploy/jboss-web.deployer/server.xml in same way, which is described in reference guide.
3) I enabled the authentication for jmx-console in same way, which is described in reference guide:
$JBOSS_HOME/server/default/deploy/jmx-console.war/WEB-INF/web.xml:
<security-constraint>
<web-resource-collection>
<web-resource-name>HtmlAdaptor</web-resource-name>
An example security config that only allows users with the
role JBossAdmin to access the HTML JMX console web application
<url-pattern>/*</url-pattern>
<http-method>GET</http-method>
<http-method>POST</http-method>
</web-resource-collection>
<auth-constraint>
<role-name>Admin</role-name>
</auth-constraint>
</security-constraint>
<login-config>
<auth-method>BASIC</auth-method>
<realm-name>JBoss JMX Console</realm-name>
</login-config>
<security-role>
<role-name>Admin</role-name>
</security-role>
$JBOSS_HOME/server/default/deploy/jmx-console.war/WEB-INF/jboss-web.xml:
<jboss-web>
<security-domain>java:/jaas/jmx-console</security-domain>
</jboss-web>
$JBOSS_HOME/server/default/conf/props/jmx-console-roles.properties:
admin=Admin,HttpInvoker
4) I went to http://localhost:8080/jmx-console and authenticate to jmx-console as admin.
5) Then I went to http://localhost:8080/portal and I see the normal default page of default portal with information about Admin is logged in (Sign 'logged in as: admin' in the right up corner and link to Admin portal)
6) After click to any link on portal, I felt into 403 forbidden error. This is caused, because any click redirects me to URL like: http://localhost:8080/portal/auth/dashboard and I need to be in 'Authenticated' role to access this URL. But I am only in 'Admin' role but not in 'Authenticated' role (Authentication is done by jmx-console and 'Authenticated' role is not specified in jmx-console-roles.properties).
My question is, if this behaviour is correct. I think not. If I am not authorized to see the default portal, while is possible then I can see http://localhost:8080/portal after logging to jmx-console? If I am authorized to see the portal, while I have the '403' error while clicking to any link from default portal page? This looks like conflict from my point of view.
mposolda(a)redhat.com
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227254#4227254
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227254
16 years, 11 months