Is modcluster-1.3.0 compatible with AS-7.2.0?

[marcodanti]

Hi all, I noticed that modcluster-1.3.0.Final claims to solve https://issues.jboss.org/browse/MODCLUSTER-359, which I really need to solve.

I am not sure however, if the jump from 1.2.x to 1.3.0 introduces compatibility issues with AS-7.2.0....

Thanks,

Marco

[jfclere]

The protocol didn't change so that will work. BTW you should use 1.3.1.

[marcodanti]

I see no 1.3.1 release available, so I tried to build mod_cluster-master, but my mvn -P dist package fails as follows:

[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/softeco/src/mod_cluster-master/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 for org.jboss.maven.plugins:maven-jdocbook-plugin:jar:2.1.2 (): 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/jbossorg-docbook-xslt-1.1.0.pom , ReasonPhrase:Forbidden. -> [Help 2]

[ERROR]     Unknown packaging: jdocbook @ org.jboss:User-Guide-${translation}:1.3.1.Final-SNAPSHOT, /home/softeco/src/mod_cluster-master/docs/userguide/pom.xml, line 11, column 14

I used to be able to build it without problems up to modcluster-.2.6.

[rhusar]

[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 for org.jboss.maven.plugins:maven-jdocbook-plugin:jar:2.1.2 (): 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/jbossorg-docbook-xslt-1.1.0.pom , ReasonPhrase:Forbidden. -> [Help 2]

Try again, works now, so maybe you hit a small outage.

[marcodanti]

Uhm..strange, it doesn't work for me. I can open http://repository.jboss.org in the browser, but there is no maven2 tree in the directory listing

[rhusar]

It's probably mapped, try to open http://repository.jboss.org/maven2/org/jboss/jbossorg-docbook-xslt/1.1.0/jbossorg-docbook-xslt-1.1.0.pom in your browser.

[marcodanti]

Forbidden

You don't have permission to access /maven2/org/jboss/jbossorg-docbook-xslt/1.1.0/jbossorg-docbook-xslt-1.1.0.pom on this server.

[rhusar]

Odd, I am out of clues, could you please shoot an email to [e-mail] with your IP, etc.?

[marcodanti]

FWIW, I downloaded also 1.2.8 and I can actually build it without errors. Does this suggest anything?

[rhusar]

Strange, the docbook version used hasn't changed in those versions.

What does your ~/.m2/settings.xml say -- do you have the jboss developer profile there (jboss-public-repository) ?

[marcodanti]

I did not have any settings.xml anywhere; setting one up actually got me past the error above, and the build completes almost without problems; it still fails to create the user guide with

[INFO] --- maven-jdocbook-plugin:2.1.2:generate (default-generate) @ User-Guide-en ---

Mar 28, 2014 2:18:30 PM org.apache.fop.hyphenation.Hyphenator getHyphenationTree

SEVERE: Couldn't find hyphenation pattern en

(...followed by a few hundreds of WARNING lines)

but I guess I can live without that, and  I'm not sure I want to know why or how I could get along from 1.2.4 to 1.2.8 with no need for a settings.xml.

Unfortunately now, after installing the new jars under modules/system/layers/base/org/jboss/as/modcluster/main and updating module.xml, I can't start JBoss any longer because the server boot aborts with:

14:28:22,315 INFO  [org.jboss.as] (MSC service thread 1-1) JBAS015950: JBoss AS 7.2.0.Final "Janus" stopped in 11ms

14:28:22,300 ERROR [org.jboss.as.controller] (Controller Boot Thread) JBAS014601: Error booting the container: java.lang.NoClassDefFoundError: org/jboss/modcluster/load/metric/impl/SystemMemoryUsageLoadMetric

...

I found a reference to SystemMemoryUsageLoadMetric being dropped in MODCLUSTER-288. Am I missing some action to dissuade the server from trying to load it?

[rhusar]

Yes, I see the problem. Let me add to what JFC said:

The protocol didn't change so that will work. BTW you should use 1.3.1.

I think JFC was referring to the native part.  The native part -- httpd modules -- are very well backwards compatible. You can use those with AS 7.2.

Unfortunately, just sticking in new version of mod_cluster jar will not work, due to some changes, like the dropping of that class. Which is unfortunate. You can do to workaround:

$ git checkout upstream/master

$ git revert 4b953743c60694d9ff339791a3483be1a064f8b9

...and build. That could work.

[rhusar]

Regarding the user docs, I can build them fine in the end, just disregard the warnings -- probably needs some cleaning up.

I have created [MODCLUSTER-396] Clean up docs build - JBoss Issue Tracker open for volunteers.

[marcodanti]

Oh, wait  a minute... could it be that the fix for MODCLUSTER-359 affects only the native part?

Because if that were the case, I could just get away with updating the httpd modules.

I am hoping so, because I am not familiar with Jboss builds from source, up to now I just used to rebuild modcluster alone from the command line and replace the jars and the native modules.

[rhusar]

marcodanti wrote:

Oh, wait  a minute... could it be that the fix for MODCLUSTER-359 affects only the native part?

Because if that were the case, I could just get away with updating the httpd modules.

I am hoping so, because I am not familiar with Jboss builds from source, up to now I just used to rebuild modcluster alone from the command line and replace the jars and the native modules.

Yes, that's correct. The fix is only in native/mod_proxy_cluster/mod_proxy_cluster.c for which you can just replace the native part. No need to change the container implementation side.