October 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBBOOT-109) Port Embedded API and Core to Bootstrap Components

by Andrew Lee Rubinger (JIRA)

Port Embedded API and Core to Bootstrap Components -------------------------------------------------- Key: JBBOOT-109 URL: https://jira.jboss.org/jira/browse/JBBOOT-109 Project: JBoss Bootstrap Issue Type: Task Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger The following components: org.jboss.embedded:jboss-embedded-api org.jboss.embedded:jboss-embedded-core Are ready to graduate from the Embedded groupId. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7148) Archived war deployment with jars in WEB-INF/lib leads to exploding the jars in tmp folder

by jaikiran pai (JIRA)

Archived war deployment with jars in WEB-INF/lib leads to exploding the jars in tmp folder ------------------------------------------------------------------------------------------ Key: JBAS-7148 URL: https://jira.jboss.org/jira/browse/JBAS-7148 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Environment: Branch_5_x and AS trunk Reporter: jaikiran pai Assignee: Andrew Lee Rubinger Deploying an archived war file in Branch_5_x and trunk, which contains jar files in the WEB-INF/lib folder of the war leads to these jars being exploded to tmp folder too. This results in deployment errors when some tomcat code expects the libraries to be zipped jars. See the reference forum thread for complete details. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

3
3
0 / 0

[JBoss JIRA] Resolved: (JBAS-7100) Exploding vfsmemory:// contents is empty for web deployments

by Andrew Lee Rubinger (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-7100?page=com.atlassian.jira.plug... ] Andrew Lee Rubinger resolved JBAS-7100. --------------------------------------- Resolution: Done Reverted > Exploding vfsmemory:// contents is empty for web deployments > ------------------------------------------------------------ > > Key: JBAS-7100 > URL: https://jira.jboss.org/jira/browse/JBAS-7100 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Reporter: Andrew Lee Rubinger > Assignee: Andrew Lee Rubinger > Fix For: JBossAS-5.2.0.Beta1, JBossAS-6.0.0.Alpha1 > > > The following patch addresses this: > [alrubinger@localhost Branch_5_x]$ svn di server/ > When using an in-memory archive backed by VFS, we're using an "unjar"; this leaves out any RAM-backed resources. Instead explode the contents, regardless of what's behind the virtual abstraction: > Index: server/src/main/org/jboss/web/deployers/AbstractWarDeployer.java > =================================================================== > --- server/src/main/org/jboss/web/deployers/AbstractWarDeployer.java (revision 91204) > +++ server/src/main/org/jboss/web/deployers/AbstractWarDeployer.java (working copy) > -357,7 +357,7 @@ > > VFSDeploymentUnit vfsUnit = (VFSDeploymentUnit)unit; > VirtualFile root = vfsUnit.getRoot(); > - VirtualFile unjared = VFSUtils.unjar(root); > + VirtualFile unjared = VFSUtils.explode(root); > // file was not unjared yet > if (root != unjared) > { > This was exposed by prototyping in EMB-32. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-6910) Eliminate use of JGroups IpAddress class in cluster module

by Brian Stansberry (JIRA)

Eliminate use of JGroups IpAddress class in cluster module ---------------------------------------------------------- Key: JBAS-6910 URL: https://jira.jboss.org/jira/browse/JBAS-6910 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-6.0.0.Alpha1 With JGroups 2.8 the type of the address is likely to be different. Biggest source of it is ClusterNodeImpl which takes IpAddress as a constructor param and then returns it as the type of getOriginalJGAddress(). The getOriginalJGAddress() method is not part of the ClusterNode interface and is only used in ClusterPartition, the class which creates the ClusterNodeImpl. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6295) reference to farm service

by John Davison (JIRA)

reference to farm service ------------------------- Key: JBAS-6295 URL: https://jira.jboss.org/jira/browse/JBAS-6295 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Docs/Clustering Guide Affects Versions: JBossAS-5.0.0.GA, JBossAS-5.0.0.CR2, JBossAS-5.0.0.CR1, JBossAS-5.0.0.Beta4, JBossAS-5.0.0.Beta3 Reporter: John Davison Section 4.3 references the Farming deployment method that is no longer supported in AS 5. It should be modified to reflect as such. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-7250) Upgrade JBoss Cache to 3.2.1.GA

by Brian Stansberry (JIRA)

Upgrade JBoss Cache to 3.2.1.GA ------------------------------- Key: JBAS-7250 URL: https://jira.jboss.org/jira/browse/JBAS-7250 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-6.0.0.Alpha1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-7118) Update JGroups to 2.6.11

by Brian Stansberry (JIRA)

Update JGroups to 2.6.11 ------------------------ Key: JBAS-7118 URL: https://jira.jboss.org/jira/browse/JBAS-7118 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-5.2.0.Beta1 Latest bug fix release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
7
0 / 0

[JBoss JIRA] Created: (JBAS-7199) Upgrade JBoss Cache to 3.2.0.GA

by Brian Stansberry (JIRA)

Upgrade JBoss Cache to 3.2.0.GA ------------------------------- Key: JBAS-7199 URL: https://jira.jboss.org/jira/browse/JBAS-7199 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-5.2.0.Beta1, JBossAS-6.0.0.Alpha1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (JGRP-1067) ConnectionTable: eagerly verify TCP connection upon lookup

by Vladimir Blagojevic (JIRA)

ConnectionTable: eagerly verify TCP connection upon lookup ---------------------------------------------------------- Key: JGRP-1067 URL: https://jira.jboss.org/jira/browse/JGRP-1067 Project: JGroups Issue Type: Bug Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 2.8 Whenever node A sends a message to a node B it looks up a connection from a connection table. In cases connection to B is present in A's table - it is returned to a caller, otherwise a new connection is created. However, the above mentioned connection to B might be closed and not yet removed from A's table (think of a case when B closes connection from its end of the pipe). Therefore, the caller who asked for a connection to B might end up with a stale connection that is guaranteed to throw an exception when A attempts to send a message to B. Of course, JGroups will eventually detect that the message is missing and retransmission will kick in but this situation can be remedied by verifying connection status before returning it to a caller. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
2
0 / 0

[JBoss JIRA] Commented: (JBAS-7100) Exploding vfsmemory:// contents is empty for web deployments

by Andrew Lee Rubinger (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-7100?page=com.atlassian.jira.plug... ] Andrew Lee Rubinger commented on JBAS-7100: ------------------------------------------- Yes; was planning on doing so after this next big patch I'm working on it complete. If needed sooner ping me and I'll do it in a new workspace. > Exploding vfsmemory:// contents is empty for web deployments > ------------------------------------------------------------ > > Key: JBAS-7100 > URL: https://jira.jboss.org/jira/browse/JBAS-7100 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Reporter: Andrew Lee Rubinger > Assignee: Andrew Lee Rubinger > Fix For: JBossAS-5.2.0.Beta1, JBossAS-6.0.0.Alpha1 > > > The following patch addresses this: > [alrubinger@localhost Branch_5_x]$ svn di server/ > When using an in-memory archive backed by VFS, we're using an "unjar"; this leaves out any RAM-backed resources. Instead explode the contents, regardless of what's behind the virtual abstraction: > Index: server/src/main/org/jboss/web/deployers/AbstractWarDeployer.java > =================================================================== > --- server/src/main/org/jboss/web/deployers/AbstractWarDeployer.java (revision 91204) > +++ server/src/main/org/jboss/web/deployers/AbstractWarDeployer.java (working copy) > -357,7 +357,7 @@ > > VFSDeploymentUnit vfsUnit = (VFSDeploymentUnit)unit; > VirtualFile root = vfsUnit.getRoot(); > - VirtualFile unjared = VFSUtils.unjar(root); > + VirtualFile unjared = VFSUtils.explode(root); > // file was not unjared yet > if (root != unjared) > { > This was exposed by prototyping in EMB-32. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
0
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 October 2009