[Design of JBoss/Tomcat Integration] - Re: Modifying session's jvmRoute when cookies are disabled
by bstansberry@jboss.com
http://labs.jboss.com/portal/jbossas/download
You don't want 4.0.4.CR2, you want 4.0.4.GA, which is the final release.
I do think you're grasping at straws though, as I can't see how my change would affect the behavior of response.encodeURL(). :(
Ahh, something coming back from buried memory... If you really want to prevent the use of cookies (as opposed to supporting users with them turned off), you want to make sure you have a context.xml file in WEB-INF that looks like this:
[url]
<!-- Session persistence is disable by default. To enable for all web
apps set the pathname to a non-empty value:
To enable session persistence for a single web app, add a
WEB-INF/context.xml
-->
<!-- Install an InstanceListener to handle the establishment of the run-as
role for servlet init/destroy events.
-->
org.jboss.web.tomcat.security.RunAsListener
[/url]
The relevant part is 'cookies="false"'; the rest are just the defaults from jbossweb-tomcat55.sar/context.xml. IIRC, if 'cookies="true"' and the browser has presented a session cookie, encodeURL() knows this and skips the unnecessary session id encoding. Perhaps this is your problem.
You could also edit the jbossweb-tomcat55.sar/context.xml file itself and turn cookies off by default for the entire server.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968996#3968996
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968996
18 years, 2 months
[Design of JBoss jBPM] - Re: to quartz or not to quartz
by tom.baeyens@jboss.com
There were 2 main reasons why i opted to improve our own implementation over Quartz :
1) a very heavy integration layer was needed between quartz and jbpm. especially making sure that quartz was using our jdbc connection for user job operations required some tricks. apart from that, there was more jdbc connection management going on in quartz which was hard to tie to our hibernate integration.
2) quartz can't acquire job-locks be means of optimistic locking. only pessimistic locking is supported and that is not supported by all databases (i.e. hsqldb). the solution that we now have worked out can acquire exclusive locks on a job by using hibernate's optimistic locking. this should even work with isolation level 0 (READ_UNCOMMITTED), which is the only level supported by hsqldb
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968946#3968946
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968946
18 years, 2 months
[Design of JBoss jBPM] - checked in new job scheduler
by tom.baeyens@jboss.com
After some investigations on how to use quartz, we ended up improving our own scheduler and messaging.
Both the messaging and scheduler service were kept. in any case, these services will produce jobs in the JBPM_JOB table (tables JBPM_TIMER and JBPM_MESSAGE were removed)
Both async messages and timers will end up as jobs in the job queue table.
There will be one JobExecutor. One job executor can have multiple threads that are all competing for jobs. There is a locking mechanism in place that should quard against duplicate executions.
Also besides the async="true", you now have an async="exclusive". this means that the job executor threads will execute all exclusive asynchronous jobs in a synchronized fashion. this might be handy when e.g. multiple concurrent paths of executions are created and in which all of these paths start with async behaviour. in that case, many jobs are offered to the job executor after one transaction. This might lead to contention since many job executor threads might start working on different jobs of the same process instance. That might lead to contention cause you'll get many optimistic locking exceptions.
There are still some exceptions with respect to messages and timers. But the bulk of the test suite is running.
But i already want to commit for backup reasons. I tried to make sure that other development is not impacted. Let me know if this is not the case and if you are experiencing problems.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968942#3968942
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968942
18 years, 2 months