April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBAS-2861) HttpSession sharing between WAR modules

by Todd Gould (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2861?page=comments#action_12358625 ] Todd Gould commented on JBAS-2861: ---------------------------------- What are the latest plans for this in terms of planned releases and timeframes? THis issue is of very high importance to our efforts. TIA! > HttpSession sharing between WAR modules > --------------------------------------- > > Key: JBAS-2861 > URL: http://jira.jboss.com/jira/browse/JBAS-2861 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service, Clustering > Affects Versions: JBossAS-3.2.7 Final, JBossAS-3.2.6 Final > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.1.CR1 > > > Creating a redacted version of JBAS-1909, which was opened as a non-public JIRA issue by a customer. > Our J2EE application is composed of several modules, each one addressing one facet of our business process, and currently this application has one web module (WAR) and several JAR modules (EJB). > We need to divide this web module into several smaller web modules. > In order to separate our unique WAR file into several WARs we must guarantee HttpSession sharing. This is due to the fact that we have a lot of session attributes that are used throughout the entire application and we cannot afford to refactor the application, in fact, that's impossible. > The security aspects for this requirement are completely addressed by the JBoss/Tomcat Single Sign-On mechanism but the session sharing requirements are not. > The ideal scenario is to keep the same HttpSession (same object in the heap, same session ID) when authenticating into one application (HttpSession created) and then forwarding to another application. > The current SSO mechanism allows the user to access the second application without reauthentication, as you know, but it creates a new HttpSession object. Also, if the two WARs have different session timeouts, if you access application A, migrates to application B, stays there until session in application A expires and then returns to application A from application B, a new HttpSession is also created in application A. > The ideal solution is to have one unique, monolithic session to all web applications configured to share a common session. IBM WebSphere and BEA WebLogic do have this configuration and feature. Please check the links below in case you want more information: > WebSphere Application Server V5: Sharing Session Context - http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/tips0215.ht... > BEA Weblogic - Enabling Web applications to share the same session - http://e-docs.bea.com/wls/docs90/webapp/sessions.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-460) Message bundler doesn't handle small messages (100 bytes) correctly

by Bela Ban (JIRA)

Message bundler doesn't handle small messages (100 bytes) correctly ------------------------------------------------------------------- Key: JGRP-460 URL: http://jira.jboss.com/jira/browse/JGRP-460 Project: JGroups Issue Type: Bug Affects Versions: 2.4.1 SP1 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 Attachments: config.txt, sfc.xml When using 2 nodes in perf.Test and the attached config.txt plus sfc.xml, we get the following exception below. Trace is: at java.net.PlainDatagramSocketImpl.send(Native Method) at java.net.DatagramSocket.send(DatagramSocket.java:612) at org.jgroups.protocols.UDP._send(UDP.java:319) at org.jgroups.protocols.UDP.sendToAllMembers(UDP.java:289) at org.jgroups.protocols.TP.doSend(TP.java:1194) at org.jgroups.protocols.TP.access$3300(TP.java:49) at org.jgroups.protocols.TP$Bundler.sendBundledMessages(TP.java:1768) at org.jgroups.protocols.TP$Bundler.send(TP.java:1689) at org.jgroups.protocols.TP$Bundler.access$100(TP.java:1657) at org.jgroups.protocols.TP.send(TP.java:1173) at org.jgroups.protocols.TP.down(TP.java:957) at org.jgroups.protocols.Discovery.down(Discovery.java:325) at org.jgroups.protocols.MERGE2.down(MERGE2.java:184) at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:406) at org.jgroups.protocols.FD.down(FD.java:363) at org.jgroups.stack.Protocol.down(Protocol.java:270) at org.jgroups.protocols.BARRIER.down(BARRIER.java:94) at org.jgroups.protocols.pbcast.NAKACK.send(NAKACK.java:641) at org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:435) at org.jgroups.protocols.UNICAST.down(UNICAST.java:398) at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:312) at org.jgroups.protocols.VIEW_SYNC.down(VIEW_SYNC.java:172) at org.jgroups.protocols.pbcast.GMS.down(GMS.java:777) at org.jgroups.protocols.SFC.down(SFC.java:257) at org.jgroups.protocols.FRAG2.down(FRAG2.java:167) at org.jgroups.protocols.pbcast.STATE_TRANSFER.down(STATE_TRANSFER.java:212) at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:340) at org.jgroups.JChannel.down(JChannel.java:1194) at org.jgroups.JChannel.send(JChannel.java:575) at org.jgroups.tests.perf.transports.JGroupsTransport.send(JGroupsTransport.java:85) at org.jgroups.tests.perf.Test.sendMessages(Test.java:451) at org.jgroups.tests.perf.Test.main(Test.java:808) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBTM-210) ServerTopLevelAction ignores ABORT_ONLY state in rollback

by Kevin Conner (JIRA)

ServerTopLevelAction ignores ABORT_ONLY state in rollback --------------------------------------------------------- Key: JBTM-210 URL: http://jira.jboss.com/jira/browse/JBTM-210 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.2 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.3 When executing a rollback, ServerTopLevelAction will execute the rollback if the transaction is in state RUNNING. This ignores the ABORT_ONLY state which should also result in execution of the rollback. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (GPD-66) Support configuring decision handler from decision's context menu

by John Ruud (JIRA)

Support configuring decision handler from decision's context menu ----------------------------------------------------------------- Key: GPD-66 URL: http://jira.jboss.com/jira/browse/GPD-66 Project: JBoss jBPM GPD Issue Type: Feature Request Reporter: John Ruud Assigned To: Koen Aers Priority: Minor It's currently possible to configure a node's action handler from a node's context menu (by choosing 'properties'). It would be very useful to be able to configure a decision's decision handler in a similar fashion. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3856) Update JBossRemoting to version 2.2.0

by Dimitris Andreadis (JIRA)

Update JBossRemoting to version 2.2.0 ------------------------------------- Key: JBAS-3856 URL: http://jira.jboss.com/jira/browse/JBAS-3856 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Remoting Reporter: Dimitris Andreadis Assigned To: Tom Elrod Fix For: JBossAS-5.0.0.Beta2 JBAS-3273 brought JBossAS Beta1 to remoting 2.2.0.Alpha2. This task is to track the upgrade to a stable 2.2.0 release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-849) PojoCache jmx test case failure

by Ben Wang (JIRA)

PojoCache jmx test case failure ------------------------------- Key: JBCACHE-849 URL: http://jira.jboss.com/jira/browse/JBCACHE-849 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Brian Stansberry Fix For: 2.0.0.GA Current pojo.jmx test is failing so I have commented them out. But we need to fix them before GA. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-4054) AOP integration

by Scott M Stark (JIRA)

AOP integration --------------- Key: JBAS-4054 URL: http://jira.jboss.com/jira/browse/JBAS-4054 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Scott M Stark Track the aop integration issues that prevent aspects from being applied -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

2
1
0 / 0

[JBoss JIRA] Updated: (JBAS-3170) ProfileService Bootstrapping of the MC

by Scott M Stark (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3170?page=all ] Scott M Stark updated JBAS-3170: -------------------------------- Fix Version/s: JBossAS-5.0.0.Beta3 (was: JBossAS-5.0.0.Beta2) Delayed the full completion to Beta3. > ProfileService Bootstrapping of the MC > -------------------------------------- > > Key: JBAS-3170 > URL: http://jira.jboss.com/jira/browse/JBAS-3170 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: MicroContainer bus > Reporter: Scott M Stark > Assigned To: Scott M Stark > Priority: Blocker > Fix For: JBossAS-5.0.0.Beta3 > > > Tasks for bootstrapping the mc using the profile service. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4112) Document the Beta2 profileservice architecture

by Scott M Stark (JIRA)

Document the Beta2 profileservice architecture ---------------------------------------------- Key: JBAS-4112 URL: http://jira.jboss.com/jira/browse/JBAS-4112 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-907) Action component: getVariable

by David Lloyd (JIRA)

Action component: getVariable ----------------------------- Key: JBPM-907 URL: http://jira.jboss.com/jira/browse/JBPM-907 Project: JBoss jBPM Issue Type: Sub-task Reporter: David Lloyd Assigned To: David Lloyd -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2007