[JBoss JIRA] (MODCLUSTER-511) run-demo.sh script fails in most cases
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-511?page=com.atlassian.jira.pl... ]
Radoslav Husar updated MODCLUSTER-511:
--------------------------------------
Fix Version/s: 1.4.0.Alpha1
> run-demo.sh script fails in most cases
> --------------------------------------
>
> Key: MODCLUSTER-511
> URL: https://issues.jboss.org/browse/MODCLUSTER-511
> Project: mod_cluster
> Issue Type: Bug
> Components: Documentation & Demos
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 1.4.0.Alpha1, 2.0.0.Alpha1
>
>
> on a system with smaller ulimit -s
> {noformat}
> [rhusar@syrah client]$ sh run-demo.sh
> run-demo.sh: line 19: 48696 Bus error: 10 java -cp $CP $OPTS org.jboss.modcluster.demo.client.ModClusterDemo
> {noformat}
> onJDK8:
> {noformat}
> [rhusar@x220 client]$ sh run-demo.sh
> MaxTenuringThreshold of 31 is invalid; must be between 0 and 15
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (MODCLUSTER-528) Re-think catalina/tomcat dependencies so as it is possible to build without tomcat7 API
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-528?page=com.atlassian.jira.pl... ]
Radoslav Husar updated MODCLUSTER-528:
--------------------------------------
Fix Version/s: 2.0.0.Alpha1
> Re-think catalina/tomcat dependencies so as it is possible to build without tomcat7 API
> ---------------------------------------------------------------------------------------
>
> Key: MODCLUSTER-528
> URL: https://issues.jboss.org/browse/MODCLUSTER-528
> Project: mod_cluster
> Issue Type: Enhancement
> Affects Versions: 1.3.3.Final
> Reporter: Michal Karm Babacek
> Assignee: Radoslav Husar
> Fix For: 2.0.0.Alpha1
>
>
> It is not possible (or I'm doing something wrong) to build mod_cluster Tomcat libs with Tomcat 8-only API.
> I hit this problem with RPM build on Fedora where I cannot download random stuff from maven central and I need to specify dependencies beforehand.
> h3. Description
> * container/catalina contains calls to API that is deprecated in Tomcat 7 and missing in Tomcat 8, so I have to apply this patch: [MODCLUSTER-528-CatalinaContext.java.patch|https://github.com/Karm/mod_clu...] before build
> * profiles and test dependencies and Servlet API dependencies needs hacks to build without Tomcat 7 too: see other patches in [mod_cluster-fedora-packages/|https://github.com/Karm/mod_cluster-fedora-p...]
> h3. Suggestion
> * architecture dependencies so as it is possible to build mod_cluster with Tomcat 8 API only (and Tomcat 7 API only)
> * drop Tomcat 6 and JBossWeb from 1.3.x as they are not used in 1.3.x anyway (last use of Tomcat 6 and JBossWeb is 1.2.x)
> h3. Fedora 24 offers only Tomcat 8
> ...so does it even make sense to offer users Tomcat 7 libs RPM? At the moment, I have it disabled. Note: Former mod_cluster RPM (1.2.6) hasn't been distributing any usable tomcat integration; it has been AS7/JBossWeb one.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (MODCLUSTER-485) Move CI to Travis
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-485?page=com.atlassian.jira.pl... ]
Radoslav Husar resolved MODCLUSTER-485.
---------------------------------------
Resolution: Done
> Move CI to Travis
> -----------------
>
> Key: MODCLUSTER-485
> URL: https://issues.jboss.org/browse/MODCLUSTER-485
> Project: mod_cluster
> Issue Type: Task
> Components: Core & Container Integration (Java)
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Labels: CI
> Fix For: 2.0.0.Alpha1, 1.4.0.Alpha1, 1.3.4.Final
>
>
> -I ran into this while adding support for Tomcat 9.-
> -What the CI should be testing, give the number of JDKs and different container versions that we support, we should build with respective jdks and versions:-
> -jdk6 + mvn verify -PTC6-
> -jdk7 + mvn verify -PTC7-
> -jdk7 + mvn verify -PAS7-
> -jdk8 + mvn verify -PTC8-
> -jdk7/8 + mvn verify-
> The situation has changed since original proposal fixing CI with proper dependencies for tomcat versions. Taking into account support for legacy containers has been dropped in master, so now we have desired combinations:
> * jdk7 + jdk8 and default profile (excludes Tomcat 9) -> 3 combos on travis
> * jdk 8 + Tomcat 9 profile -> 1 combo on travis
> See http://tomcat.apache.org/whichversion.html
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months