September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBAS-3641) Updated bin/jboss_init_hpux.sh script

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3641?page=comments#action_12343308 ] Dimitris Andreadis commented on JBAS-3641: ------------------------------------------ Thanks John. I'll commit this to all brances, but can you please verify it works with the latest jboss-4.0.5.CR1 ? > Updated bin/jboss_init_hpux.sh script > ------------------------------------- > > Key: JBAS-3641 > URL: http://jira.jboss.com/jira/browse/JBAS-3641 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Other > Environment: HP-UX > Reporter: john mendonca > Assigned To: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-5.0.0.Beta, JBossAS-3.2.8.SP2, JBossAS-4.0.5.GA > > Attachments: jboss_init_hpux.sh > > > Entered at the request of Luc Texier: > <HP request from the Customer support Portal> > Please replace the <jbosshome>/bin/jboss_init_hpux.sh script with the attached updated version in your next release cycle: > - handles multiple jboss as instances > - updated comments (including installation instructions) > - more robust code -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3641) Updated bin/jboss_init_hpux.sh script

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3641?page=all ] Dimitris Andreadis updated JBAS-3641: ------------------------------------- Fix Version/s: JBossAS-5.0.0.Beta JBossAS-3.2.8.SP2 > Updated bin/jboss_init_hpux.sh script > ------------------------------------- > > Key: JBAS-3641 > URL: http://jira.jboss.com/jira/browse/JBAS-3641 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Other > Environment: HP-UX > Reporter: john mendonca > Assigned To: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-5.0.0.Beta, JBossAS-3.2.8.SP2, JBossAS-4.0.5.GA > > Attachments: jboss_init_hpux.sh > > > Entered at the request of Luc Texier: > <HP request from the Customer support Portal> > Please replace the <jbosshome>/bin/jboss_init_hpux.sh script with the attached updated version in your next release cycle: > - handles multiple jboss as instances > - updated comments (including installation instructions) > - more robust code -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-407) XARecovery integration of JBossMessaging with JBossTS

by Madhusudhan Konda (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-407?page=comments#action_12... ] Madhusudhan Konda commented on JBMESSAGING-407: ----------------------------------------------- BTW, you need to add the following changes to conf/jbossjta-properties.xml: <properties depends="arjuna" name="jta"> ... <property name="com.arjuna.ats.jta.recovery.XAResourceRecoveryMessaging" value="org.jboss.jms.recovery.MessagingXAResourceRecovery;xaConnFac=XAConnectionFactory"/> <property name="com.arjuna.ats.jta.xaRecoveryNode" value="*" /> .. </properties> Note: the above properties MUST go under "jta" section (not the expected recoverymanager) And <properties depends="arjuna" name="recoverymanager"> .. <property name="com.arjuna.ats.arjuna.recovery.recoveryExtension3" value="com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule"/> ... </properties> > XARecovery integration of JBossMessaging with JBossTS > ----------------------------------------------------- > > Key: JBMESSAGING-407 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-407 > Project: JBoss Messaging > Issue Type: Patch > Components: Tests and Performance > Environment: JBoss 4.0.3SP1, JBossTs 4.2GA, JBOSS Messagig 1.0.1CR2 > Reporter: Madhusudhan Konda > Assigned To: Ovidiu Feodorov > Fix For: 1.2.0.Alpha1 > > Attachments: artifacts.zip, jms-recovery-patch-all.txt, jms.zip, JMSProviderXAResourceRecovery.java, xa.zip, xarecovery-patch.txt, XATestStandaloneRecovery.java > > Original Estimate: 1 week > Remaining Estimate: 1 week > > To make JBossMessaging XAResource as recoverable using JBossTS RecoveryManager -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBWEB-16) scratchdir fails for multi-user installs

by Luc Texier (JIRA)

[ http://jira.jboss.com/jira/browse/JBWEB-16?page=comments#action_12343306 ] Luc Texier commented on JBWEB-16: --------------------------------- I removed my last comment which was erroneous scratchdir is used only when compiling jsp pages what you might consider is the following option instead JAVA_OPTS="$JAVA_OPTS -Dcatalina.base=/tmp/catalina" the server will then created the /work directory in there > scratchdir fails for multi-user installs > ---------------------------------------- > > Key: JBWEB-16 > URL: http://jira.jboss.com/jira/browse/JBWEB-16 > Project: JBoss Web > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Module > Affects Versions: JBossWeb embedded - AS 4.0.1 > Reporter: Norman Richards > Assigned To: Remy Maucherat > > The setup was the basic multi-user scenario described in the dev environment admin training slides (module 8). Each user has his own data/tmp/deploy directory, but the conf directory is shared between all users and not writable. > This produces a a FATAL log message: > 11:37:06,717 FATAL [EmbeddedServletOptions] The scratchDir you specified: > /private/tmp/jboss-4.0.2/server/test/work/jboss.web/localhost/jmx-console is unusable. > This also causes exceptions when the server shuts down. > The jboss.web directory should probably go under the data or tmp directory so that it can exist on a per-user basis. Another option is to allow variable substitution in the server.xml file so that the scratchdir can be set based on the $[user.name} property. > See the admin module 8, slides 5-16 for the complete configuration if my description isn't clear. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWEB-16) scratchdir fails for multi-user installs

by Luc Texier (JIRA)

[ http://jira.jboss.com/jira/browse/JBWEB-16?page=all ] Luc Texier updated JBWEB-16: ---------------------------- Comment: was deleted > scratchdir fails for multi-user installs > ---------------------------------------- > > Key: JBWEB-16 > URL: http://jira.jboss.com/jira/browse/JBWEB-16 > Project: JBoss Web > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Module > Affects Versions: JBossWeb embedded - AS 4.0.1 > Reporter: Norman Richards > Assigned To: Remy Maucherat > > The setup was the basic multi-user scenario described in the dev environment admin training slides (module 8). Each user has his own data/tmp/deploy directory, but the conf directory is shared between all users and not writable. > This produces a a FATAL log message: > 11:37:06,717 FATAL [EmbeddedServletOptions] The scratchDir you specified: > /private/tmp/jboss-4.0.2/server/test/work/jboss.web/localhost/jmx-console is unusable. > This also causes exceptions when the server shuts down. > The jboss.web directory should probably go under the data or tmp directory so that it can exist on a per-user basis. Another option is to allow variable substitution in the server.xml file so that the scratchdir can be set based on the $[user.name} property. > See the admin module 8, slides 5-16 for the complete configuration if my description isn't clear. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-3641) Updated bin/jboss_init_hpux.sh script

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3641?page=all ] Dimitris Andreadis reassigned JBAS-3641: ---------------------------------------- Assignee: Dimitris Andreadis > Updated bin/jboss_init_hpux.sh script > ------------------------------------- > > Key: JBAS-3641 > URL: http://jira.jboss.com/jira/browse/JBAS-3641 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Other > Environment: HP-UX > Reporter: john mendonca > Assigned To: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-4.0.5.GA > > Attachments: jboss_init_hpux.sh > > > Entered at the request of Luc Texier: > <HP request from the Customer support Portal> > Please replace the <jbosshome>/bin/jboss_init_hpux.sh script with the attached updated version in your next release cycle: > - handles multiple jboss as instances > - updated comments (including installation instructions) > - more robust code -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3641) Updated bin/jboss_init_hpux.sh script

by Luc Texier (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3641?page=all ] Luc Texier updated JBAS-3641: ----------------------------- Security: Public (was: JBoss Partner) > Updated bin/jboss_init_hpux.sh script > ------------------------------------- > > Key: JBAS-3641 > URL: http://jira.jboss.com/jira/browse/JBAS-3641 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Other > Environment: HP-UX > Reporter: john mendonca > Priority: Minor > Fix For: JBossAS-4.0.5.GA > > Attachments: jboss_init_hpux.sh > > > Entered at the request of Luc Texier: > <HP request from the Customer support Portal> > Please replace the <jbosshome>/bin/jboss_init_hpux.sh script with the attached updated version in your next release cycle: > - handles multiple jboss as instances > - updated comments (including installation instructions) > - more robust code -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBWEB-16) scratchdir fails for multi-user installs

by Luc Texier (JIRA)

[ http://jira.jboss.com/jira/browse/JBWEB-16?page=comments#action_12343300 ] Luc Texier commented on JBWEB-16: --------------------------------- I had to investigate this problem for a customer. The issue is that the last folder at the end of the path is not created automatically. so if you want Tomcat to write to e.g. /home/myuser/jboss/work, /work must exist already Note: If a path is not specified as in the default configuration, "something" is creating the "/work" directory...what? I dunno > scratchdir fails for multi-user installs > ---------------------------------------- > > Key: JBWEB-16 > URL: http://jira.jboss.com/jira/browse/JBWEB-16 > Project: JBoss Web > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Module > Affects Versions: JBossWeb embedded - AS 4.0.1 > Reporter: Norman Richards > Assigned To: Remy Maucherat > > The setup was the basic multi-user scenario described in the dev environment admin training slides (module 8). Each user has his own data/tmp/deploy directory, but the conf directory is shared between all users and not writable. > This produces a a FATAL log message: > 11:37:06,717 FATAL [EmbeddedServletOptions] The scratchDir you specified: > /private/tmp/jboss-4.0.2/server/test/work/jboss.web/localhost/jmx-console is unusable. > This also causes exceptions when the server shuts down. > The jboss.web directory should probably go under the data or tmp directory so that it can exist on a per-user basis. Another option is to allow variable substitution in the server.xml file so that the scratchdir can be set based on the $[user.name} property. > See the admin module 8, slides 5-16 for the complete configuration if my description isn't clear. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-353) @Interceptors meta-annotation needs @Target(TYPE)

by Stephan Bublava (JIRA)

@Interceptors meta-annotation needs @Target(TYPE) ------------------------------------------------- Key: JBSEAM-353 URL: http://jira.jboss.com/jira/browse/JBSEAM-353 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Affects Versions: 1.0.1 Reporter: Stephan Bublava Priority: Minor The @Interceptors meta-annotation only works with @Target(TYPE). If you want to intercept certain methods only, two cooperating annotations are required (as demonstrated by the issue tracker example in CVS, which uses @LoggedIn and @CheckLoggedIn). Since this is not obvious (at least to me), it should be explained in the documentation (chapter 2.6. Seam interceptors). -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (BPEL-186) Write a blog entry about the beta release

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-186?page=all ] Alejandro Guizar updated BPEL-186: ---------------------------------- Summary: Write a blog entry about the beta release (was: Write a blog entry about the 1.1 release) Fix Version/s: jBPM BPEL 1.1 beta 2 (was: jBPM BPEL 1.1 beta 3) > Write a blog entry about the beta release > ----------------------------------------- > > Key: BPEL-186 > URL: http://jira.jboss.com/jira/browse/BPEL-186 > Project: JBoss jBPM BPEL > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documents > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 beta 2 > > -- 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, 10 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 September 2006