August 2014 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-424) Broken Links on JBoss.org

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-424?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-424: ------------------------------------------- The Jira link also needs updating (ssl, host changed, etc) so it should be "https://issues.jboss.org/browse/MODCLUSTER". > Broken Links on JBoss.org > ------------------------- > > Key: MODCLUSTER-424 > URL: https://issues.jboss.org/browse/MODCLUSTER-424 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Daniel Coughlin > Assignee: Radoslav Husar > > The following broken link is currently listed against this project on www.jboss.org/projects. > https://community.jboss.org/en/mod_cluster/dev - Dev Forum > http://hudson.qa.jboss.com/hudson/view/mod_cluster/view/mod_cluster - Build/Jenkins > If you maintain a project.properties file that you have told the jboss.org team about, then you just need to fix it in there and the change will be reflected on the site. Otherwise, you need to update the data on this project's Magnolia page. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-424) Broken Links on JBoss.org

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-424?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-424: ------------------------------------------- I have created a view in public jenkins instance (the one used by the build publisher plugin), it is here: https://hudson.jboss.org/hudson/view/mod_cluster/ > Broken Links on JBoss.org > ------------------------- > > Key: MODCLUSTER-424 > URL: https://issues.jboss.org/browse/MODCLUSTER-424 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Daniel Coughlin > Assignee: Radoslav Husar > > The following broken link is currently listed against this project on www.jboss.org/projects. > https://community.jboss.org/en/mod_cluster/dev - Dev Forum > http://hudson.qa.jboss.com/hudson/view/mod_cluster/view/mod_cluster - Build/Jenkins > If you maintain a project.properties file that you have told the jboss.org team about, then you just need to fix it in there and the change will be reflected on the site. Otherwise, you need to update the data on this project's Magnolia page. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-424) Broken Links on JBoss.org

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-424?page=com.atlassian.jira.pl... ] Radoslav Husar edited comment on MODCLUSTER-424 at 8/15/14 8:09 AM: -------------------------------------------------------------------- hudson.qa.jboss.com is not accessible from the outside world, only from VPN. Maybe needs some sort of publishing of the view? Not sure if its not only applicable for jobs. {quote}Unable to determine IP address from host name hudson.qa.jboss.com{quote} was (Author: rhusar): hudson.qa.jboss.com is not accessible from the outside world, only from VPN. Maybe needs some sort of publishing of the view? Not sure if its not only applicable for buids. {quote}Unable to determine IP address from host name hudson.qa.jboss.com{quote} > Broken Links on JBoss.org > ------------------------- > > Key: MODCLUSTER-424 > URL: https://issues.jboss.org/browse/MODCLUSTER-424 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Daniel Coughlin > Assignee: Radoslav Husar > > The following broken link is currently listed against this project on www.jboss.org/projects. > https://community.jboss.org/en/mod_cluster/dev - Dev Forum > http://hudson.qa.jboss.com/hudson/view/mod_cluster/view/mod_cluster - Build/Jenkins > If you maintain a project.properties file that you have told the jboss.org team about, then you just need to fix it in there and the change will be reflected on the site. Otherwise, you need to update the data on this project's Magnolia page. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-424) Broken Links on JBoss.org

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-424?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-424: ------------------------------------------- I checked our publishing plugin in jenkins, wecan only publish *jobs* not views, so that link never worked for the community. I am thinking we could create a page with links to the published jobs. > Broken Links on JBoss.org > ------------------------- > > Key: MODCLUSTER-424 > URL: https://issues.jboss.org/browse/MODCLUSTER-424 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Daniel Coughlin > Assignee: Radoslav Husar > > The following broken link is currently listed against this project on www.jboss.org/projects. > https://community.jboss.org/en/mod_cluster/dev - Dev Forum > http://hudson.qa.jboss.com/hudson/view/mod_cluster/view/mod_cluster - Build/Jenkins > If you maintain a project.properties file that you have told the jboss.org team about, then you just need to fix it in there and the change will be reflected on the site. Otherwise, you need to update the data on this project's Magnolia page. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-424) Broken Links on JBoss.org

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-424?page=com.atlassian.jira.pl... ] Work on MODCLUSTER-424 started by Radoslav Husar. > Broken Links on JBoss.org > ------------------------- > > Key: MODCLUSTER-424 > URL: https://issues.jboss.org/browse/MODCLUSTER-424 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Daniel Coughlin > Assignee: Radoslav Husar > > The following broken link is currently listed against this project on www.jboss.org/projects. > https://community.jboss.org/en/mod_cluster/dev - Dev Forum > http://hudson.qa.jboss.com/hudson/view/mod_cluster/view/mod_cluster - Build/Jenkins > If you maintain a project.properties file that you have told the jboss.org team about, then you just need to fix it in there and the change will be reflected on the site. Otherwise, you need to update the data on this project's Magnolia page. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-424) Broken Links on JBoss.org

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-424?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-424: ------------------------------------------- hudson.qa.jboss.com is not accessible from the outside world, only from VPN. Maybe needs some sort of publishing of the view? Not sure if its not only applicable for buids. {quote}Unable to determine IP address from host name hudson.qa.jboss.com{quote} > Broken Links on JBoss.org > ------------------------- > > Key: MODCLUSTER-424 > URL: https://issues.jboss.org/browse/MODCLUSTER-424 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Daniel Coughlin > Assignee: Radoslav Husar > > The following broken link is currently listed against this project on www.jboss.org/projects. > https://community.jboss.org/en/mod_cluster/dev - Dev Forum > http://hudson.qa.jboss.com/hudson/view/mod_cluster/view/mod_cluster - Build/Jenkins > If you maintain a project.properties file that you have told the jboss.org team about, then you just need to fix it in there and the change will be reflected on the site. Otherwise, you need to update the data on this project's Magnolia page. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-424) Broken Links on JBoss.org

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-424?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-424: ------------------------------------------- OK, also fixed on the project matrix. > Broken Links on JBoss.org > ------------------------- > > Key: MODCLUSTER-424 > URL: https://issues.jboss.org/browse/MODCLUSTER-424 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Daniel Coughlin > Assignee: Radoslav Husar > > The following broken link is currently listed against this project on www.jboss.org/projects. > https://community.jboss.org/en/mod_cluster/dev - Dev Forum > http://hudson.qa.jboss.com/hudson/view/mod_cluster/view/mod_cluster - Build/Jenkins > If you maintain a project.properties file that you have told the jboss.org team about, then you just need to fix it in there and the change will be reflected on the site. Otherwise, you need to update the data on this project's Magnolia page. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-418) Upgrade maven repositories to jboss developer from the deprecated repositories

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-418?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-418: -------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Merged. > Upgrade maven repositories to jboss developer from the deprecated repositories > ------------------------------------------------------------------------------ > > Key: MODCLUSTER-418 > URL: https://issues.jboss.org/browse/MODCLUSTER-418 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation & Demos > Affects Versions: 1.3.0.Final, 1.2.9.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Fix For: 1.3.1.Final > > > The problem is we are using old repositories, and thus not all artefacts can be fetched from outside of red hat internal VPN. Nevertheless, all these are available in the right repositories. > There is also a note: > Note: This Maven repository is deprecated. The JBoss.org Maven repository is now managed by Nexus located at https://repository.jboss.org/nexus/. You should update your Maven builds to use the new repository url since it will contain all current project releases. > If you want to use JBoss artifacts in your project builds, you should use the repository found at http://repository.jboss.org/nexus/content/groups/public-jboss/. More information is available on the wiki page MavenGettingStarted-Users > If you are developing software for the JBoss community, please refer to MavenGettingStarted-Developers > Original report: > arun-gupta commented 18 days ago > pi@raspberrypi ~/mod_cluster/mod_cluster $ ~/apache-maven-3.2.1/bin/mvn -P dist package > [INFO] Scanning for projects... > Downloading: http://repository.jboss.org/maven2/org/jboss/jbossorg-docbook-xslt/1.1.0/... > Downloading: http://repository.jboss.org/maven2/org/jboss/jbossorg-jdocbook-style/1.1.... > Downloading: http://repository.jboss.org/maven2/net/sf/docbook/docbook/1.72.0/docbook-... > Downloading: http://repository.jboss.org/maven2/javax/media/jai-core/1.1.3/jai-core-1.... > Downloading: http://repository.jboss.org/maven2/com/sun/media/jai-codec/1.1.3/jai-code... > [ERROR] The build could not read 1 project -> [Help 1] > [ERROR] > [ERROR] The project org.jboss:User-Guide-en:1.3.1.Final-SNAPSHOT (/home/pi/mod_cluster/mod_cluster/docs/userguide/pom.xml) has 2 errors > [ERROR] Unresolveable build extension: Plugin org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.2 or one of its dependencies could not be resolved: Failed to collect dependencies at org.jboss.maven.plugins:maven-jdocbook-plugin:jar:2.1.2 -> org.jboss:jbossorg-docbook-xslt:jar:1.1.0: Failed to read artifact descriptor for org.jboss:jbossorg-docbook-xslt:jar:1.1.0: Could not transfer artifact org.jboss:jbossorg-docbook-xslt:pom:1.1.0 from/to old jboss.org (http://repository.jboss.org/maven2): Access denied to: http://repository.jboss.org/maven2/org/jboss/jbossorg-docbook-xslt/1.1.0/... , ReasonPhrase:Forbidden. -> [Help 2] > [ERROR] Unknown packaging: jdocbook @ org.jboss:User-Guide-${translation}:1.3.1.Final-SNAPSHOT, /home/pi/mod_cluster/mod_cluster/docs/userguide/pom.xml, line 11, column 14 > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException > [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-413) Log superfluous stack traces onto DEBUG instead of ERROR level

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-413?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-413: -------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Merged. > Log superfluous stack traces onto DEBUG instead of ERROR level > -------------------------------------------------------------- > > Key: MODCLUSTER-413 > URL: https://issues.jboss.org/browse/MODCLUSTER-413 > Project: mod_cluster > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core & Container Integration (Java) > Affects Versions: 1.3.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.3.1.Final > > > (18:17:45) rhusar: pferraro: i would like to refactor this: when modcluster fails certain calls on the proxy, the whole stack trace is logged > (18:17:59) rhusar: pferraro: and i think its really useless to log Connection failed stack trace > (18:18:07) rhusar: pferraro: some projects solve this by > (18:18:08) rhusar: pferraro: ContextLogger.LOG.unableToClearBeanStore(getBeanStore()); > (18:18:08) rhusar: ContextLogger.LOG.catchingDebug(e); > (18:18:18) rhusar: pferraro: would you be in favor of such change? > (18:19:27) rhusar: pferraro: so you can still access the stack traces if you switch to debug. otherwise things like restarting the proxy doesnt print a horrific stack trace > (18:19:31) rhusar: pferraro: just an error. > (18:20:15) pferraro: rhusar: that makes sense > (18:20:40) rhusar: pferraro: ie get rid of https://gist.githubusercontent.com/rhusar/6ddc5b3b0ce51d4f6f67/raw/137d12... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-180) ping and nodeTimeout interact.

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-180?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-180. ------------------------------------- Closing. Clean-up. At least one of the following applies: * the issue has been thoroughly tested as a part of one of the current releases or * it hasn't occurred in ~2 years or * it's utterly harmless > ping and nodeTimeout interact. > ------------------------------- > > Key: MODCLUSTER-180 > URL: https://issues.jboss.org/browse/MODCLUSTER-180 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.3.GA > Reporter: Samuel Mendenhall > Assignee: Jean-Frederic Clere > Fix For: 1.0.4.GA > > > mod_cluster times out after ping instead nodeTimeout -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues August 2014