掲示板

Issue deploying liferay-6.1- ee-ga2 on jboss EAP-6.0

11年前 に vv nagesh によって更新されました。

Issue deploying liferay-6.1- ee-ga2 on jboss EAP-6.0

New Member 投稿: 1 参加年月日: 11/12/08 最新の投稿
Hi All ,

I have an issue while deploying liferay-6.1- ee-ga2 on jboss EAP-6.0. I have followed all the steps mentioned in http://www.liferay.com/documentation/liferay-portal/6.1/user-guide/-/ai/lp-6-1-ugen11-installing-liferay-on-jboss-7-0 except that am using hsql database.

ROOT.war is successfully deployed. Issue details are

1> Deploy directory is not being created.
2> Tables are created but the reference data is not inserted in any of the tables.

Logs from EAP-6.0.0

19:22:32,404 WARN [org.jboss.as.server.deployment] (MSC service thread 1-27) JBAS015893: Encountered invalid class name 'DEFAULT=ear|jar|war|zip' for service type 'de.schlichtherle.io.registry.properties'
19:22:32,404 WARN [org.jboss.as.server.deployment] (MSC service thread 1-27) JBAS015893: Encountered invalid class name 'zip=de.schlichtherle.io.archive.zip.ZipDriver' for service type 'de.schlichtherle.io.registry.properties'
19:22:32,404 WARN [org.jboss.as.server.deployment] (MSC service thread 1-27) JBAS015893: Encountered invalid class name 'ear|jar|war=de.schlichtherle.io.archive.zip.JarDriver' for service type 'de.schlichtherle.io.registry.properties'
19:22:32,404 WARN [org.jboss.as.server.deployment] (MSC service thread 1-27) JBAS015893: Encountered invalid class name 'odg|odp|ods|odt=de.schlichtherle.io.archive.zip.OdfDriver' for service type 'de.schlichtherle.io.registry.properties'
19:22:32,405 WARN [org.jboss.as.server.deployment] (MSC service thread 1-27) JBAS015893: Encountered invalid class name 'otg|otp|ots|ott=de.schlichtherle.io.archive.zip.OdfDriver' for service type 'de.schlichtherle.io.registry.properties'
19:22:32,405 WARN [org.jboss.as.server.deployment] (MSC service thread 1-27) JBAS015893: Encountered invalid class name 'odb|odf|odm|oth=de.schlichtherle.io.archive.zip.OdfDriver' for service type 'de.schlichtherle.io.registry.properties'
19:22:32,405 WARN [org.jboss.as.server.deployment] (MSC service thread 1-27) JBAS015893: Encountered invalid class name 'exe=de.schlichtherle.io.archive.zip.ReadOnlySfxDriver' for service type 'de.schlichtherle.io.registry.properties'
19:22:32,405 WARN [org.jboss.as.server.deployment] (MSC service thread 1-27) 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'
19:22:32,406 WARN [org.jboss.as.server.deployment] (MSC service thread 1-27) JBAS015893: Encountered invalid class name 'tar=de.schlichtherle.io.archive.tar.TarDriver' for service type 'de.schlichtherle.io.registry.properties'
19:22:32,406 WARN [org.jboss.as.server.deployment] (MSC service thread 1-27) JBAS015893: Encountered invalid class name 'tgz|tar.gz=de.schlichtherle.io.archive.tar.TarGZipDriver' for service type 'de.schlichtherle.io.registry.properties'
19:22:32,406 WARN [org.jboss.as.server.deployment] (MSC service thread 1-27) JBAS015893: Encountered invalid class name 'tbz2|tar.bz2=de.schlichtherle.io.archive.tar.TarBZip2Driver' for service type 'de.schlichtherle.io.registry.properties'
19:22:34,405 INFO [org.jboss.as.osgi] (MSC service thread 1-21) JBAS011907: Register module: Module "deployment.ROOT.war:main" from Service Module Loader
19:22:34,652 INFO [stdout] (MSC service thread 1-34) Loading vfs:/home/appuser/jboss-eap-6.0.0/jboss-eap-6.0/standalone/deployments/ROOT.war/WEB-INF/lib/portal-impl.jar/system.properties
19:22:35,059 INFO [stdout] (MSC service thread 1-34) Loading vfs:/home/appuser/jboss-eap-6.0.0/jboss-eap-6.0/standalone/deployments/ROOT.war/WEB-INF/lib/portal-impl.jar/portal.properties
19:22:40,514 INFO [stdout] (MSC service thread 1-34) 19:22:40,512 INFO [MSC service thread 1-34][DialectDetector:71] Determine dialect for HSQL Database Engine 2
19:22:40,515 INFO [stdout] (MSC service thread 1-34) 19:22:40,515 WARN [MSC service thread 1-34][DialectDetector:86] Liferay is configured to use Hypersonic as its database. Do NOT use Hypersonic in production. Hypersonic is an embedded database useful for development and demo'ing purposes. The database settings can be changed in portal-ext.properties.
19:22:40,534 INFO [stdout] (MSC service thread 1-34) 19:22:40,533 INFO [MSC service thread 1-34][DialectDetector:136] Found dialect org.hibernate.dialect.HSQLDialect
19:22:53,741 INFO [stdout] (MSC service thread 1-34) Starting Liferay Portal Enterprise Edition 6.1.20 EE (Paton / Build 6120 / July 31, 2012)
19:22:54,083 INFO [stdout] (MSC service thread 1-34) 19:22:54,083 INFO [MSC service thread 1-34][BaseDB:452] Database supports case sensitive queries
19:22:54,327 INFO [stdout] (MSC service thread 1-34) 19:22:54,327 INFO [MSC service thread 1-34][LicenseManager:?] Failed to find directory /home/appuser/jboss-eap-6.0.0/data/license
19:22:54,328 INFO [stdout] (MSC service thread 1-34) 19:22:54,328 ERROR [MSC service thread 1-34][LicenseManager:?] No binary licenses found
19:22:54,329 INFO [stdout] (MSC service thread 1-34) 19:22:54,329 INFO [MSC service thread 1-34][ServerDetector:157] Server does not support hot deploy
19:22:54,334 INFO [stdout] (MSC service thread 1-34) 19:22:54,334 INFO [MSC service thread 1-34][PluginPackageUtil:1030] Reading plugin package for the root context
19:22:58,265 INFO [org.jboss.web] (MSC service thread 1-34) JBAS018210: Registering web context:
19:22:58,327 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "ROOT.war"


Any help on this issue would be really useful.
thumbnail
11年前 に Hitoshi Ozawa によって更新されました。

RE: Issue deploying liferay-6.1- ee-ga2 on jboss EAP-6.0

Liferay Legend 投稿: 7942 参加年月日: 10/03/24 最新の投稿
You're following instructions to setup liferay 6.1 on JBoss 7.
Unfortunately, I don't think there's an instruction to setup liferay 6.1 on JBoss 6.
Either use previous version of liferay or use newer version of JBoss.
thumbnail
11年前 に Peter Svehla によって更新されました。

RE: Issue deploying liferay-6.1- ee-ga2 on jboss EAP-6.0

New Member 投稿: 4 参加年月日: 12/03/19 最新の投稿
JBoss EAP 6.0 includes 7.1.1 AS inside, so EAP 6 equates to JBoss 7.