August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Resolved: (JBPORTAL-936) Update IPC sample and docs

by Roy Russo (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-936?page=all ] Roy Russo resolved JBPORTAL-936. -------------------------------- Fix Version/s: 2.4.1 Final Resolution: Done > Update IPC sample and docs > -------------------------- > > Key: JBPORTAL-936 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-936 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation > Affects Versions: 2.4 Final > Reporter: Roy Russo > Assigned To: Roy Russo > Fix For: 2.4.1 Final > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3358) Work directory shouldn't be deleted on Context Destroy

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3358?page=all ] Dimitris Andreadis updated JBAS-3358: ------------------------------------- Fix Version/s: JBossAS-4.0.5.CR1 (was: JBossAS-4.0.5.GA) Affects: [Compatibility/Configuration] > Work directory shouldn't be deleted on Context Destroy > ------------------------------------------------------ > > Key: JBAS-3358 > URL: http://jira.jboss.com/jira/browse/JBAS-3358 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Affects Versions: JBossAS-4.0.4.GA > Reporter: Javid Jamae > Assigned To: Anil Saldhana > Fix For: JBossAS-4.0.5.CR1 > > > I tried enabling HTTP session persistence, but found out that the default directory that it writes to is the work directory. Working with JBoss support, I discovered that the work directory is deleted when the server shuts down. > Either the work directory should not be deleted, or the default directory where the persistent HTTP sessions are serialized to a file should be changed to be in a directory other than work (since it is being deleted). -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3358) Work directory shouldn't be deleted on Context Destroy

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3358?page=comments#action_12341496 ] Dimitris Andreadis commented on JBAS-3358: ------------------------------------------ Shouldn't the correct fix version be 4.0.5.CR1? > Work directory shouldn't be deleted on Context Destroy > ------------------------------------------------------ > > Key: JBAS-3358 > URL: http://jira.jboss.com/jira/browse/JBAS-3358 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Affects Versions: JBossAS-4.0.4.GA > Reporter: Javid Jamae > Assigned To: Anil Saldhana > Fix For: JBossAS-4.0.5.GA > > > I tried enabling HTTP session persistence, but found out that the default directory that it writes to is the work directory. Working with JBoss support, I discovered that the work directory is deleted when the server shuts down. > Either the work directory should not be deleted, or the default directory where the persistent HTTP sessions are serialized to a file should be changed to be in a directory other than work (since it is being deleted). -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-289) Make service container configurable wrt datasource and persistence manager config

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-289?page=all ] Tim Fox updated JBMESSAGING-289: -------------------------------- Fix Version/s: 1.0.1.CR5 (was: 1.0.1.CR1) > Make service container configurable wrt datasource and persistence manager config > --------------------------------------------------------------------------------- > > Key: JBMESSAGING-289 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-289 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Ovidiu Feodorov > Priority: Blocker > Fix For: 1.0.1.CR5 > > > Must be made configurable so test suite can be run against different databases with different pm configs -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-289) Make service container configurable wrt datasource and persistence manager config

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-289?page=all ] Tim Fox reopened JBMESSAGING-289: --------------------------------- The current solution for this only allows the persistence manager to be configured for the JMS tests. The core tests will continue to use the default HSQL persistence manager config, irrespective of which database has been configured. > Make service container configurable wrt datasource and persistence manager config > --------------------------------------------------------------------------------- > > Key: JBMESSAGING-289 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-289 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Ovidiu Feodorov > Priority: Blocker > Fix For: 1.0.1.CR1 > > > Must be made configurable so test suite can be run against different databases with different pm configs -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3501) JBoss ignores exploded modules inside an unexploded EAR

by Gregory Nolle (JIRA)

JBoss ignores exploded modules inside an unexploded EAR ------------------------------------------------------- Key: JBAS-3501 URL: http://jira.jboss.com/jira/browse/JBAS-3501 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-4.0.4.GA Reporter: Gregory Nolle Assigned To: Dimitris Andreadis Attachments: EARDeployer.diff The EARDeployer ignores modules that are exploded inside an unexploded EAR and then throws an error saying that it couldn't find said modules. If the EAR is exploded as well then it's not a problem. I've attached a patch for the EARDeployer class that fixes the problem. I personally think it's an inelegant solution but I don't have the time to do the refactoring necessary to improve it. Nonetheless, it seems to work for me. I've basically copied a bunch of code out of the JarUtils class to work out the URL to the exploded JAR's directory in the tempDeployDir and then added that to the extractedJars map, without using JarUtils.extractNestedJar(...). -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-276) Print version number on startup

by Bela Ban (JIRA)

Print version number on startup ------------------------------- Key: JGRP-276 URL: http://jira.jboss.com/jira/browse/JGRP-276 Project: JGroups Issue Type: Feature Request Affects Versions: 2.3 SP1 Reporter: Bela Ban Assigned To: Bela Ban Priority: Trivial Fix For: 2.4 Useful for support -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-275) unsafe check for MBeanServer defaultdomain

by Ivan Martinez (JIRA)

unsafe check for MBeanServer defaultdomain ------------------------------------------ Key: JGRP-275 URL: http://jira.jboss.com/jira/browse/JGRP-275 Project: JGroups Issue Type: Bug Affects Versions: 2.4 Environment: testing jmx and jgroups under jboss 4.0.2 Reporter: Ivan Martinez Assigned To: Bela Ban Attachments: jgroups_jmx_util_getmbeanserver.patch when a mbeanserver exists with null domain before a jboss server the Util.getMBeanServer throws NPE -- 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, 11 months

2
3
0 / 0

Pensó en tener un Servidor propio?

by Hostex.cl

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-490) update license headers

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-490?page=all ] Alejandro Guizar resolved JBPM-490. ----------------------------------- Resolution: Done Added the header for the jbpm-bpel license from thirdparty/licences/license-info.xml. > update license headers > ---------------------- > > Key: JBPM-490 > URL: http://jira.jboss.com/jira/browse/JBPM-490 > Project: JBoss jBPM > Issue Type: Task > Components: BPEL > Reporter: Tom Baeyens > Assigned To: Alejandro Guizar > Attachments: jbpm-bpel.license.txt > > > The header is necessary in terms of having the FSF agree that a project is conforming with the LGPL terms. > The org.jboss.tools.license.ValidateLicenseHeaders java program (attached) from the jbossas/varia module is what I use. It will add the default header to files without one when -addheader is specified. It relies on the thirdparty/licenses/license-info.xml file being under the cvs directory of the source tree to determine what headers are valid. You can get this from the jboss-4.0/jboss-head cvs after thirdparty has been built, or from the thirdparty repository: -- 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, 11 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 August 2006