Liferay 6.2 install on JBoss 6.2 EAP Server

[Subhasis Roy, modifié il y a 9 années.]

Hi,

I am facing an issue while installing Liferay 6.2 ee SP9 on JBoss 6.2 EAP server.
I have followed the steps for the ref url -

Liferay installation on JBoss

Please find the error log below -

need some help to fix the issue.

Error Log:

09:47:29,069 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'org.kxml2.io.KXmlParser,org.kxml2.io.KXmlSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'
09:47:29,085 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'DRIVER=TRUE' for service type 'de.schlichtherle.io.registry.properties'
09:47:29,085 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'DEFAULT=ear|jar|war|zip' for service type 'de.schlichtherle.io.registry.properties'
09:47:29,085 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'zip=de.schlichtherle.io.archive.zip.ZipDriver' for service type 'de.schlichtherle.io.registry.properties'
09:47:29,085 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'ear|jar|war=de.schlichtherle.io.archive.zip.JarDriver' for service type 'de.schlichtherle.io.registry.properties'
09:47:29,085 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'odg|odp|ods|odt=de.schlichtherle.io.archive.zip.OdfDriver' for service type 'de.schlichtherle.io.registry.properties'
09:47:29,101 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'otg|otp|ots|ott=de.schlichtherle.io.archive.zip.OdfDriver' for service type 'de.schlichtherle.io.registry.properties'
09:47:29,101 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'odb|odf|odm|oth=de.schlichtherle.io.archive.zip.OdfDriver' for service type 'de.schlichtherle.io.registry.properties'
09:47:29,116 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'exe=de.schlichtherle.io.archive.zip.ReadOnlySfxDriver' for service type 'de.schlichtherle.io.registry.properties'
09:47:29,116 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'tzp|zip.rae|zip.raes=de.schlichtherle.io.archive.zip.raes.SafeZipRaesDriver' for service type 'de.schlichtherle.io.registry.properties'
09:47:29,116 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'tar=de.schlichtherle.io.archive.tar.TarDriver' for service type 'de.schlichtherle.io.registry.properties'
09:47:29,132 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'tgz|tar.gz=de.schlichtherle.io.archive.tar.TarGZipDriver' for service type 'de.schlichtherle.io.registry.properties'
09:47:29,132 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'tbz2|tar.bz2=de.schlichtherle.io.archive.tar.TarBZip2Driver' for service type 'de.schlichtherle.io.registry.properties'
09:47:29,132 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'
09:47:31,505 INFO [org.jboss.web] (ServerService Thread Pool -- 115) JBAS018210: Register web context:
09:47:32,807 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/]] (ServerService Thread Pool -- 115) Initializing Spring root WebApplicationContext
09:47:58,628 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS]
09:47:58,644 INFO [org.apache.coyote.http11] (MSC service thread 1-7) JBWEB003075: Coyote HTTP/1.1 pausing on: http-/127.0.0.1:8080
09:48:51,247 INFO [org.apache.coyote.http11] (MSC service thread 1-7) JBWEB003077: Coyote HTTP/1.1 stopping on : http-/127.0.0.1:8080


thanks,
subhasis

[David H Nebinger, modifié il y a 9 années.]

error log missing from post.

Liferay will run on jboss EAP (I know, I've done it). Be sure to use the standalone mode when deploying, though, not the managed one.

[David H Nebinger, modifié il y a 9 années.]

Subhasis Roy:

Hi,

I am facing an issue while installing Liferay 6.2 on JBoss 6.2 EAP server.
I have followed the steps for the ref url -

Liferay installation on JBoss

Please find the error log below -

need some help to fix the issue.

Error Log:

09:47:29,069 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'org.kxml2.io.KXmlParser,org.kxml2.io.KXmlSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'
09:47:29,085 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'DRIVER=TRUE' for service type 'de.schlichtherle.io.registry.properties'
09:47:29,085 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'DEFAULT=ear|jar|war|zip' for service type 'de.schlichtherle.io.registry.properties'
09:47:29,085 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'zip=de.schlichtherle.io.archive.zip.ZipDriver' for service type 'de.schlichtherle.io.registry.properties'
09:47:29,085 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'ear|jar|war=de.schlichtherle.io.archive.zip.JarDriver' for service type 'de.schlichtherle.io.registry.properties'
09:47:29,085 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'odg|odp|ods|odt=de.schlichtherle.io.archive.zip.OdfDriver' for service type 'de.schlichtherle.io.registry.properties'
09:47:29,101 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'otg|otp|ots|ott=de.schlichtherle.io.archive.zip.OdfDriver' for service type 'de.schlichtherle.io.registry.properties'
09:47:29,101 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'odb|odf|odm|oth=de.schlichtherle.io.archive.zip.OdfDriver' for service type 'de.schlichtherle.io.registry.properties'
09:47:29,116 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'exe=de.schlichtherle.io.archive.zip.ReadOnlySfxDriver' for service type 'de.schlichtherle.io.registry.properties'
09:47:29,116 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'tzp|zip.rae|zip.raes=de.schlichtherle.io.archive.zip.raes.SafeZipRaesDriver' for service type 'de.schlichtherle.io.registry.properties'
09:47:29,116 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'tar=de.schlichtherle.io.archive.tar.TarDriver' for service type 'de.schlichtherle.io.registry.properties'
09:47:29,132 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'tgz|tar.gz=de.schlichtherle.io.archive.tar.TarGZipDriver' for service type 'de.schlichtherle.io.registry.properties'
09:47:29,132 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'tbz2|tar.bz2=de.schlichtherle.io.archive.tar.TarBZip2Driver' for service type 'de.schlichtherle.io.registry.properties'
09:47:29,132 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'
09:47:31,505 INFO [org.jboss.web] (ServerService Thread Pool -- 115) JBAS018210: Register web context:
09:47:32,807 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/]] (ServerService Thread Pool -- 115) Initializing Spring root WebApplicationContext
09:47:58,628 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS]
09:47:58,644 INFO [org.apache.coyote.http11] (MSC service thread 1-7) JBWEB003075: Coyote HTTP/1.1 pausing on: http-/127.0.0.1:8080
09:48:51,247 INFO [org.apache.coyote.http11] (MSC service thread 1-7) JBWEB003077: Coyote HTTP/1.1 stopping on : http-/127.0.0.1:8080

Ah, log not missing, just someone playing around with colors and setting the text to white....

So I believe your issue is due to class loader configuration issue, not that it won't work. Just tweak your module dependencies for xmlpull and the schlichtherle thing and see how it goes.

[Subhasis Roy, modifié il y a 9 années.]

David H Nebinger:

Subhasis Roy:

Hi,
Ah, log not missing, just someone playing around with colors and setting the text to white....

So I believe your issue is due to class loader configuration issue, not that it won't work. Just tweak your module dependencies for xmlpull and the schlichtherle thing and see how it goes.

Hi David,

I am sharing my module.xml file.

<!--?xml version="1.0"?-->

<module xmlns="urn:jboss:module:1.0" name="com.liferay.portal">
    <resources>
        <resource-root path="hsql.jar" />
        <resource-root path="portal-service.jar" />
        <resource-root path="portlet.jar" />
    </resources>
    <dependencies>
        <module name="javax.api" />
        <module name="javax.mail.api" />
        <module name="javax.servlet.api" />
        <module name="javax.servlet.jsp.api" />
        <module name="javax.transaction.api" />
    </dependencies>
</module>

I think your asking me to check this. I am not exactly sure what is wrong in this one.

[David H Nebinger, modifié il y a 9 années.]

I don't think there's anything wrong, but there may be some missing.

One suggestion that has always worked for me was to go to a bundle and see what, exactly, it is using. If you can start and use the jboss bundle, then it's module.xml file might be a good reference for what needs to be in yours.

[Subhasis Roy, modifié il y a 9 années.]

Hi,

I am now getting the following error-

Error:
12:54:18,026 INFO [ServerService Thread Pool -- 175][BaseDB:481] Database supports case sensitive queries
12:54:18,056 ERROR [ServerService Thread Pool -- 175][MainServlet:212] java.lang.IllegalStateException: Attempting to deploy an older Liferay Portal version. Current build version is 6210 and attempting to deploy version 6202.
java.lang.IllegalStateException: Attempting to deploy an older Liferay Portal version. Current build version is 6210 and attempting to deploy version 6202.
at com.liferay.portal.tools.DBUpgrader.upgrade(DBUpgrader.java:114)
at com.liferay.portal.events.StartupAction.doRun(StartupAction.java:180)
at com.liferay.portal.ee.license.StartupAction.doRun(Unknown Source)

Its showing the version issue.

I am using the "liferay-portal-6.2-ee-sp9.war" and trying to deploy it on JBoss 6.2 EAP Server.

[David H Nebinger, modifié il y a 9 années.]

6202 would be a version number for CE, not EE sp 9.

Check the web server folders looking for a pending deployment that has not completed.

[Vilmos Papp, modifié il y a 9 années.]

Hi,

I think, your DB is generated with 6.2 EE SP9, but you try to start 6.2 CE on it. Please check that.

Regards,
Vilmos

[Subhasis Roy, modifié il y a 9 années.]

Vilmos Papp:

Hi,

I think, your DB is generated with 6.2 EE SP9, but you try to start 6.2 CE on it. Please check that.

Regards,
Vilmos

Hi Vil,

Yes, I have checked the lportal.script file and found that the it's trying to generate the 6.2, but I am not sure why it is giving that error.

Because I have downloaded the "liferay-portal-6.2-ee-sp9.war" from the liferay site and downloaded the JBoss 6.2 EAP from JBoss site separately.
So why its trying to deploy some different CE version, that's not sure.

thanks in advance.

[Vilmos Papp, modifié il y a 9 années.]

Hi Subhasis,

I think, you missed to use the corresponding portal-service.jar. Have you downloaded the one from liferay-portal-dependencies-6.2-ee-sp9.zip ?

Regards,
Vilmos

[Subhasis Roy, modifié il y a 9 années.]

Hi Vil,

Yes, I have downloaded that, and kept all those jars under "JBOSS_HOME\modules\com\liferay\portal\main" folder.

[Subhasis Roy, modifié il y a 9 années.]

Vilmos Papp:

Hi Subhasis,

I think, you missed to use the corresponding portal-service.jar. Have you downloaded the one from liferay-portal-dependencies-6.2-ee-sp9.zip ?

Regards,
Vilmos

Hi Vil,

Done it.....

Changed the portal-service.jar under "jboss-eap-6.2\modules\com\liferay\portal\main" folder with the following one and also updated the version entry in the module.xml file.

<!--?xml version="1.0"?-->

<module xmlns="urn:jboss:module:1.0" name="com.liferay.portal">
    <resources>        
        <resource-root path="portal-service-6.2.1.jar" />
		<resource-root path="hsql.jar" />
        <resource-root path="portlet.jar" />
    </resources>
    <dependencies>
		<module name="com.liferay.portal" />
        <module name="javax.api" />
        <module name="javax.mail.api" />
        <module name="javax.servlet.api" />
        <module name="javax.servlet.jsp.api" />
        <module name="javax.transaction.api" />
    </dependencies>
</module>

New portal-serice.jar file location given below -

Liferay6.2.1 Dependency_portal-service Jar

Softwares used -

1. Jboss EAP 6.2.0
2. liferay-portal-6.2-ee-sp9.war
3. portal-service-6.2.1.jar under the JBOSS_HOME/module/com/liferay/portal/main

Ref URL

Liferay6.2.x Dependency Jars_Nexus Location

i have documented my steps here..

liferay-6-2 with jboss-eap-6-2

[Vilmos Papp, modifié il y a 9 années.]

Great, I hope it will be useful for others as well.