Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
Liferay 6.1 Jboss 7 Alessandro Sebastiano March 28, 2012 1:26 AM
RE: Liferay 6.1 Jboss 7 David H Nebinger March 28, 2012 6:00 AM
RE: Liferay 6.1 Jboss 7 Alessandro Sebastiano March 28, 2012 7:12 AM
RE: Liferay 6.1 Jboss 7 Alessandro Sebastiano March 28, 2012 7:15 AM
RE: Liferay 6.1 Jboss 7 Alessandro Sebastiano March 28, 2012 8:10 AM
RE: Liferay 6.1 Jboss 7 David H Nebinger March 28, 2012 8:17 AM
RE: Liferay 6.1 Jboss 7 Alessandro Sebastiano March 28, 2012 8:21 AM
RE: Liferay 6.1 Jboss 7 David H Nebinger March 28, 2012 8:46 AM
RE: Liferay 6.1 Jboss 7 Hitoshi Ozawa March 28, 2012 2:42 PM
RE: Liferay 6.1 Jboss 7 Brian Ko April 3, 2012 1:25 PM
RE: Liferay 6.1 Jboss 7 Everest Liu April 3, 2012 1:51 PM
RE: Liferay 6.1 Jboss 7 Hitoshi Ozawa April 3, 2012 5:03 PM
RE: Liferay 6.1 Jboss 7 Everest Liu April 4, 2012 11:29 AM
RE: Liferay 6.1 Jboss 7 Everest Liu April 4, 2012 2:54 PM
RE: Liferay 6.1 Jboss 7 Brian Ko April 5, 2012 9:40 AM
RE: Liferay 6.1 Jboss 7 Everest Liu April 5, 2012 10:24 AM
RE: Liferay 6.1 Jboss 7 Brian Ko April 5, 2012 2:02 PM
RE: Liferay 6.1 Jboss 7 Everest Liu April 5, 2012 3:11 PM
RE: Liferay 6.1 Jboss 7 Everest Liu April 5, 2012 5:06 PM
RE: Liferay 6.1 Jboss 7 Brian Ko April 6, 2012 8:44 AM
RE: Liferay 6.1 Jboss 7 Everest Liu April 6, 2012 9:21 AM
RE: Liferay 6.1 Jboss 7 Oliver T. January 10, 2014 5:52 AM
RE: Liferay 6.1 Jboss 7 Hitoshi Ozawa April 22, 2012 7:16 AM
RE: Liferay 6.1 Jboss 7 Trenton Perceval May 8, 2012 2:44 AM
RE: Liferay 6.1 Jboss 7 Hitoshi Ozawa May 8, 2012 5:26 AM
RE: Liferay 6.1 Jboss 7 devaraj s July 2, 2012 9:07 PM
RE: Liferay 6.1 Jboss 7 Adrian Chia March 29, 2012 2:18 PM
RE: Liferay 6.1 Jboss 7 Jack Chung April 20, 2012 7:43 AM
RE: Liferay 6.1 Jboss 7 Hitoshi Ozawa March 28, 2012 7:05 AM
RE: Liferay 6.1 Jboss 7 Hitoshi Ozawa March 28, 2012 7:10 AM
Alessandro Sebastiano
Liferay 6.1 Jboss 7
March 28, 2012 1:26 AM
Answer

Alessandro Sebastiano

Rank: New Member

Posts: 13

Join Date: March 9, 2012

Recent Posts

Hi,
I have installed Jboss AS 7.1.1 and deploy Liferay 6.1.10 with war file.
When I start Jboss in the server.log there're some error:


10:15:24,353 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry vecmath-1.3.2.jar in "/usr/local/jboss-as-7.1.1/standalone/deployments/ROOT.war/WEB-INF/lib/gt-metadata.jar" does not point to a valid jar for a Class-Path reference.
10:15:24,354 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry geoapi-2.3-M1.jar in "/usr/local/jboss-as-7.1.1/standalone/deployments/ROOT.war/WEB-INF/lib/gt-metadata.jar" does not point to a valid jar for a Class-Path reference.
10:15:24,355 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry jsr-275-1.0-beta-2.jar in "/usr/local/jboss-as-7.1.1/standalone/deployments/ROOT.war/WEB-INF/lib/gt-metadata.jar" does not point to a valid jar for a Class-Path reference.
10:15:24,355 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry geoapi-pending-2.3-M1.jar in "/usr/local/jboss-as-7.1.1/standalone/deployments/ROOT.war/WEB-INF/lib/gt-metadata.jar" does not point to a valid jar for a Class-Path reference.
10:15:24,356 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry commons-cli.jar in "/usr/local/jboss-as-7.1.1/standalone/deployments/ROOT.war/WEB-INF/lib/xuggle-xuggler.jar" does not point to a valid jar for a Class-Path reference.
10:15:24,357 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry logback-classic.jar in "/usr/local/jboss-as-7.1.1/standalone/deployments/ROOT.war/WEB-INF/lib/xuggle-xuggler.jar" does not point to a valid jar for a Class-Path reference.
10:15:24,358 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry logback-core.jar in "/usr/local/jboss-as-7.1.1/standalone/deployments/ROOT.war/WEB-INF/lib/xuggle-xuggler.jar" does not point to a valid jar for a Class-Path reference.


....

Please, could you help me?
Thanks a lot
Alessandro
David H Nebinger
RE: Liferay 6.1 Jboss 7
March 28, 2012 6:00 AM
Answer

David H Nebinger

Rank: Liferay Legend

Posts: 7080

Join Date: September 1, 2006

Recent Posts

You will get these when there is a dependency reference in the manifest that is not satisfied in the class path.

Looks like these two jars list dependencies to the missing jars, thus generating the warnings.

As long as you don't use the code from the listed jars, you can ignore the warning.
Hitoshi Ozawa
RE: Liferay 6.1 Jboss 7
March 28, 2012 7:05 AM
Answer

Hitoshi Ozawa

Rank: Liferay Legend

Posts: 7990

Join Date: March 23, 2010

Recent Posts

Alessandro, would appreciate if you stop posting the same question in the forum.

http://www.liferay.com/community/forums/-/message_boards/message/13203067
Hitoshi Ozawa
RE: Liferay 6.1 Jboss 7
March 28, 2012 7:10 AM
Answer

Hitoshi Ozawa

Rank: Liferay Legend

Posts: 7990

Join Date: March 23, 2010

Recent Posts

JBoss 7.1.1 was released after Liferay 6.1 was released. So, it wasn't tested. May be better to stick with the bundled version or use Tomcat.
Alessandro Sebastiano
RE: Liferay 6.1 Jboss 7
March 28, 2012 7:12 AM
Answer

Alessandro Sebastiano

Rank: New Member

Posts: 13

Join Date: March 9, 2012

Recent Posts

ok but the deploy fails with error and liferay not works.


16:08:36,968 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.module.service."deployment.ROOT.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.ROOT.war".main: Failed to load module: deployment.ROOT.war:main
at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
Caused by: org.jboss.modules.ModuleNotFoundException: Module system:main is not found in local module loader @3d9360e2 (roots: /usr/local/jboss-as-7.1.1.Final/modules)
at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:126)
at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275)
at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222)
at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94)
at org.jboss.modules.ModuleLoader.preloadExportedModule(ModuleLoader.java:233)
at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:246)
at org.jboss.as.server.moduleservice.ServiceModuleLoader.preloadModule(ServiceModuleLoader.java:160) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.modules.Module.addPaths(Module.java:841)
at org.jboss.modules.Module.link(Module.java:1181)
at org.jboss.modules.Module.relinkIfNecessary(Module.java:1207)
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:208)
at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:70) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 5 more


thanks a lot
alessandro
Alessandro Sebastiano
RE: Liferay 6.1 Jboss 7
March 28, 2012 7:15 AM
Answer

Alessandro Sebastiano

Rank: New Member

Posts: 13

Join Date: March 9, 2012

Recent Posts

What Do you think if I install Jboss 7.0 Web Profile Only (Java EE6 Certified)???

What's the right version of Jboss to download?

Thanks a lot
Alessandro
Alessandro Sebastiano
RE: Liferay 6.1 Jboss 7
March 28, 2012 8:10 AM
Answer

Alessandro Sebastiano

Rank: New Member

Posts: 13

Join Date: March 9, 2012

Recent Posts

Now I have installed Jboss 7.0 Web Profile Only (Java EE6 Certified) and deployed Liferay but not work.

this is the error:


14:57:45,496 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/]] (MSC service thread 1-5) Exception sending context initialized event to listener instance of class com.liferay.portal.spring.context.PortalContextLoaderListener: org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [com.liferay.portal.kernel.format.PhoneNumberFormatUtil] for bean with name 'com.liferay.portal.kernel.format.PhoneNumberFormatUtil' defined in class path resource [META-INF/util-spring.xml]; nested exception is java.lang.ClassNotFoundException: com.liferay.portal.kernel.format.PhoneNumberFormatUtil from [Module "deployment.ROOT.war:main" from Service Module Loader]
at org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1261) [spring-beans.jar:]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.predictBeanType(AbstractAutowireCapableBeanFactory.java:576) [spring-beans.jar:]
at org.springframework.beans.factory.support.AbstractBeanFactory.isFactoryBean(AbstractBeanFactory.java:1330) [spring-beans.jar:]
at org.springframework.beans.factory.support.AbstractBeanFactory.isFactoryBean(AbstractBeanFactory.java:896) [spring-beans.jar:]
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:566) [spring-beans.jar:]
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895) [spring-context.jar:]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425) [spring-context.jar:]
at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:282) [spring-web.jar:]
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:204) [spring-web.jar:]
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47) [spring-web.jar:]
at com.liferay.portal.spring.context.PortalContextLoaderListener.contextInitialized(PortalContextLoaderListener.java:159) [portal-impl.jar:]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3368) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3821) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:70) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_30]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_30]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_30]


Please, help me
Alessandro
David H Nebinger
RE: Liferay 6.1 Jboss 7
March 28, 2012 8:17 AM
Answer

David H Nebinger

Rank: Liferay Legend

Posts: 7080

Join Date: September 1, 2006

Recent Posts

Deploying Liferay to an existing Jboss server is not a matter of downloading and dropping in the Liferay war file.

This is all covered in the documentation related to installing to an existing application server.

Basically you're missing the portal-service.jar file which is usually found in the global class path.

Either start from a bundle (which is good to go) or read the documentation.
Alessandro Sebastiano
RE: Liferay 6.1 Jboss 7
March 28, 2012 8:21 AM
Answer

Alessandro Sebastiano

Rank: New Member

Posts: 13

Join Date: March 9, 2012

Recent Posts

I have installed liferay following the online documentation.

What I have to check, please?
thanks a lot
Alessandro
David H Nebinger
RE: Liferay 6.1 Jboss 7
March 28, 2012 8:46 AM
Answer

David H Nebinger

Rank: Liferay Legend

Posts: 7080

Join Date: September 1, 2006

Recent Posts

Usually you can identify differences from the jboss bundle vs a clean jboss by downloading the bundle and the corresponding clean jboss version, then use a comparison tool to identify the changes that were made.

Using this list as a template, you can then make similar changes to the target jboss version that you want to run on.

But these are all things you would do when you're ready to deploy to a production system. If you're just new to Liferay or just trying to give it a spin, stick with the bundled version. It's working, it's stable, and it's easy to get started with.
Hitoshi Ozawa
RE: Liferay 6.1 Jboss 7
March 28, 2012 2:42 PM
Answer

Hitoshi Ozawa

Rank: Liferay Legend

Posts: 7990

Join Date: March 23, 2010

Recent Posts

David, there's an issue with Liferay 6.1 and JBoss using the bundle version or not. It's been reported several times in the forum before and it's still not resolved.
I'll have to check the svn trunk if Liferay.com has fixed something to resolve this.
Adrian Chia
RE: Liferay 6.1 Jboss 7
March 29, 2012 2:18 PM
Answer

Adrian Chia

Rank: New Member

Posts: 1

Join Date: March 29, 2012

Recent Posts

Alessandro Sebastiano:
Now I have installed Jboss 7.0 Web Profile Only (Java EE6 Certified) and deployed Liferay but not work.

this is the error:


14:57:45,496 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/]] (MSC service thread 1-5) Exception sending context initialized event to listener instance of class com.liferay.portal.spring.context.PortalContextLoaderListener: org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [com.liferay.portal.kernel.format.PhoneNumberFormatUtil] for bean with name 'com.liferay.portal.kernel.format.PhoneNumberFormatUtil' defined in class path resource [META-INF/util-spring.xml]; nested exception is java.lang.ClassNotFoundException: com.liferay.portal.kernel.format.PhoneNumberFormatUtil from [Module "deployment.ROOT.war:main" from Service Module Loader]
at org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1261) [spring-beans.jar:]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.predictBeanType(AbstractAutowireCapableBeanFactory.java:576) [spring-beans.jar:]
at org.springframework.beans.factory.support.AbstractBeanFactory.isFactoryBean(AbstractBeanFactory.java:1330) [spring-beans.jar:]
at org.springframework.beans.factory.support.AbstractBeanFactory.isFactoryBean(AbstractBeanFactory.java:896) [spring-beans.jar:]
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:566) [spring-beans.jar:]
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895) [spring-context.jar:]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425) [spring-context.jar:]
at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:282) [spring-web.jar:]
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:204) [spring-web.jar:]
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47) [spring-web.jar:]
at com.liferay.portal.spring.context.PortalContextLoaderListener.contextInitialized(PortalContextLoaderListener.java:159) [portal-impl.jar:]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3368) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3821) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:70) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_30]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_30]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_30]


Please, help me
Alessandro


In JBoss AS7 you have to edit the standalone.xml (see bundled JBoss AS 7) and the war file should contain jboss-deployment-structure.xml (see bundled JBoss AS 7 again) which resolve some class loading /dependencies issues.
Brian Ko
RE: Liferay 6.1 Jboss 7
April 3, 2012 1:25 PM
Answer

Brian Ko

Rank: Junior Member

Posts: 70

Join Date: February 11, 2010

Recent Posts

I agree. There is a problem and I already posted it. http://www.liferay.com/community/forums/-/message_boards/message/12395728

What I do not understand is this. The problem is so easy to duplicate. Just unzip the file and start the Jboss and you will find it is not working. However, why Liferay does not acknowledge this problem? Why aren't there many people complaining about this problem?

When liferay uses thousands of Hudson servers to test the program, it is hard to believe that EE version is failing. Probably we have some special set up that makes it fail. However, how do we find what it is? The problem is so obvious that it is hard to troubleshoot.

Brian
Anonymous
RE: Liferay 6.1 Jboss 7
April 3, 2012 1:51 PM
Answer

Anonymous

Hi Hitoshi & Brian,

I ran fresh installs of Liferay on WinXP and Win7 with the jBoss packages, both variations of CE and EE and they are all working for me. Maybe there was an update since the time of original post. Try it again and let me know your results with the newest GA release! Also, what hardware/software config are you guys doing? I can't seem to find any problems deploying Liferay with the bundled jBoss in my 6.1 builds.

Regards,
Everest
Hitoshi Ozawa
RE: Liferay 6.1 Jboss 7
April 3, 2012 5:03 PM
Answer

Hitoshi Ozawa

Rank: Liferay Legend

Posts: 7990

Join Date: March 23, 2010

Recent Posts

I've tried running the bundled GA1 on Windows XP and Ubuntu 32 bit. Both failed. Tomcat bundle works ok on both.

There's other posts about the problem. I haven't had any difficulties with 6.0.5 and 6.0.6 with JBoss bundled/unbundled.
e.g.
http://www.liferay.com/community/forums/-/message_boards/message/13267981
Anonymous
RE: Liferay 6.1 Jboss 7
April 4, 2012 11:29 AM
Answer

Anonymous

Hey Hitoshi,

I deployed the jBoss package in both CE and EE on Ubuntu 32bit with no problems at all. I'm also using GA1 for both and have had no problems. Is there any conflict with your previous deployments of jBoss? jBoss 7.0.2 (included in the package) has no problems for me.

My process:
1. open a VM of whichever OS (have tried on ubuntu 32, winxp 32, win7 32, and win7 64)
2. go to java.com to install java on the respective OS
3. download liferay CE 6.1 GA1
4. unzip to desktop
5. deploy standalone.sh / standalone.bat
6. repeat steps 3-5 with EE 6.1 GA1, deploy EE license
Success

This has been successful for me in every combination. Are you running the most up-to-date JRE? Maybe there's an issue there possibly. Let me know because I'd like to help figure out what variable may be causing the error! Let me know of any other variables that may be present.

Regards,
Everest
Anonymous
RE: Liferay 6.1 Jboss 7
April 4, 2012 2:54 PM
Answer

Anonymous

Brian Ko:
The problem is so easy to duplicate. Just unzip the file and start the Jboss and you will find it is not working.

  • I've had 10 variations of this and was never able to duplicate the problem, many OS in both 32 and 64 bits, both CE and EE. I've asked many others to try it too and they can't replicate the problem either with the jboss package.

Brian Ko:
However, why Liferay does not acknowledge this problem?

  • We can't find any problem, we've tried but it always works. Can you post your console logs? warnings are okay, and are normal because they are just warnings. we don't get any jboss startup and deploy errors.

Brian Ko:
Why aren't there many people complaining about this problem?

  • It seems to be localized to just a few machines, possibly with custom setups. It works for almost everyone else deploying the bundle. After your jboss AS starts up, are you able to conenct to localhost manually in a browser?

Brian Ko:
When liferay uses thousands of Hudson servers to test the program, it is hard to believe that EE version is failing.

  • It's not failing for most people; the EE bundle works as expected

Brian Ko:
Probably we have some special set up that makes it fail.

  • post your console so I can take a look; it does sound like the special set up that you have may possibly be preventing it to start up, so I'd agree with you there


Hope I can help.
Brian Ko
RE: Liferay 6.1 Jboss 7
April 5, 2012 9:40 AM
Answer

Brian Ko

Rank: Junior Member

Posts: 70

Join Date: February 11, 2010

Recent Posts

Hi Everest,

I appreciate your reply and glad to hear it is my problem. Here is the console output. It is kind of lengthy. FYI, it was done on Windows XP, service pack 2. For this, I downloaded the clean zip file and unzip it and run standalone.bat from C:\java\liferay-portal-6.1.10-ee-ga1\jboss-7.0.2\bin directory.

Brian

C:\java\liferay-portal-6.1.10-ee-ga1\jboss-7.0.2\bin>standalone.bat
Calling C:\java\liferay-portal-6.1.10-ee-ga1\jboss-7.0.2\bin\standalone.conf.bat

===============================================================================

JBoss Bootstrap Environment

JBOSS_HOME: C:\java\liferay-portal-6.1.10-ee-ga1\jboss-7.0.2

JAVA: C:\Program Files\Java\jdk1.6.0_06\bin\java

JAVA_OPTS: -Dprogram.name=standalone.bat -Dsun.rmi.dgc.client.gcInterval=3600
000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dorg.jboss.resolver.warning=true -D
jboss.modules.system.pkgs=org.jboss.byteman -Dfile.encoding=UTF-8 -Djava.net.pre
ferIPv4Stack=true -Duser.timezone=GMT -Xmx1024m -XX:MaxPermSize=256m -server

===============================================================================

16:28:46,245 INFO [org.jboss.modules] JBoss Modules version 1.0.2.GA
16:28:46,869 INFO [org.jboss.msc] JBoss MSC version 1.0.1.GA
16:28:46,947 INFO [org.jboss.as] JBoss AS 7.0.2.Final "Arc" starting
16:28:48,927 WARN [org.jboss.as] No security realm defined for native managemen
t service, all access will be unrestricted.
16:28:48,927 INFO [org.jboss.as] creating http management service using network
interface (management) port (9990)
16:28:49,114 WARN [org.jboss.as] No security realm defined for http management
service, all access will be unrestricted.
16:28:49,130 INFO [org.jboss.as.logging] Removing bootstrap log handlers
16:28:49,161 INFO [org.jboss.as.connector.subsystems.datasources] (Controller B
oot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)
16:28:49,177 INFO [org.jboss.as.clustering.infinispan.subsystem] (Controller Bo
ot Thread) Activating Infinispan subsystem.
16:28:49,348 INFO [org.jboss.as.naming] (Controller Boot Thread) JBAS011800: Ac
tivating Naming Subsystem
16:28:49,395 INFO [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: St
arting Naming Service
16:28:49,411 INFO [org.jboss.as.osgi] (Controller Boot Thread) JBAS011910: Acti
vating OSGi Subsystem
16:28:49,442 INFO [org.jboss.as.security] (Controller Boot Thread) Activating S
ecurity Subsystem
16:28:49,473 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting
version 3.2.0.Beta2
16:28:49,489 INFO [org.xnio] (MSC service thread 1-4) XNIO Version 3.0.0.Beta3
16:28:49,504 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementati
on Version 3.0.0.Beta3
16:28:50,097 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subs
ystem
16:28:50,128 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service
thread 1-4) The Apache Tomcat Native library which allows optimal performance in
production environments was not found on the java.library.path: C:\Program File
s\Java\jdk1.6.0_06\bin;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;
C:\Program Files\CollabNet Subversion Client;C:\WINDOWS\system32;C:\WINDOWS;C:\W
INDOWS\System32\Wbem;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Pro
gram Files\Java\jdk1.6.0_06\bin;C:\java\apache-ant-1.8.2\bin;C:\java\apache-mave
n-2.2.1\bin;C:\Program Files\Common Files\Compuware;C:\PROGRA~1\IBM\SQLLIB\BIN;C
:\PROGRA~1\IBM\SQLLIB\FUNCTION;C:\PROGRA~1\IBM\SQLLIB\SAMPLES\REPL;c:\cvs;C:\jav
a\eclipse-jee-europa-win32\eclipse;C:\Program Files\Common Files\Lenovo;C:\Progr
am Files\TortoiseSVN\bin;C:\Program Files\IBM\IBM DATA SERVER DRIVER\bin;C:\wamp
\bin\php\php5.3.5;C:\Program Files\IDM Computer Solutions\UltraEdit\;C:\Program
Files\MySQL\MySQL Server 5.0\bin\;
16:28:50,175 INFO [org.jboss.as.remoting] (MSC service thread 1-2) Listening on
/127.0.0.1:9999
16:28:50,175 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-
2) Starting remote JMX connector
16:28:50,471 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread
1-1) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
16:28:50,486 INFO [org.jboss.as.connector] (MSC service thread 1-3) Starting JC
A Subsystem (JBoss IronJacamar 1.0.3.Final)
16:28:50,580 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service
thread 1-4) Bound data source [java:jboss/datasources/ExampleDS]
16:28:51,266 INFO [org.jboss.as.deployment] (MSC service thread 1-4) Started Fi
leSystemDeploymentService for directory C:\java\liferay-portal-6.1.10-ee-ga1\jbo
ss-7.0.2\standalone\deployments
16:28:51,297 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.2.Final
"Arc" started in 5426ms - Started 93 of 148 services (55 services are passive or
on-demand)
16:28:52,950 INFO [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Fou
nd ROOT.war in deployment directory. To trigger deployment create a file called
ROOT.war.dodeploy
16:28:52,981 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) Sta
rting deployment of "ROOT.war"
16:30:30,550 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry asm-3.3.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2/
standalone/deployments/ROOT.war/WEB-INF/lib/asm-xml.jar" does not point to a va
lid jar for a Class-Path reference.
16:30:30,550 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry asm-util-3.3.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7
.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/asm-xml.jar" does not point to
a valid jar for a Class-Path reference.
16:30:30,550 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry asm-attrs-3.3.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-
7.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/asm-xml.jar" does not point t
o a valid jar for a Class-Path reference.
16:30:30,550 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry gt-api-2.6.1.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7
.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/gt-coverage.jar" does not poin
t to a valid jar for a Class-Path reference.
16:30:30,550 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry jts-1.10.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2
/standalone/deployments/ROOT.war/WEB-INF/lib/gt-coverage.jar" does not point to
a valid jar for a Class-Path reference.
16:30:30,550 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry gt-referencing-2.6.1.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1
/jboss-7.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/gt-coverage.jar" does
not point to a valid jar for a Class-Path reference.
16:30:30,550 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry vecmath-1.3.2.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-
7.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/gt-coverage.jar" does not poi
nt to a valid jar for a Class-Path reference.
16:30:30,550 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry commons-pool-1.5.3.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/j
boss-7.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/gt-coverage.jar" does no
t point to a valid jar for a Class-Path reference.
16:30:30,550 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry gt-metadata-2.6.1.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jb
oss-7.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/gt-coverage.jar" does not
point to a valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry geoapi-2.3-M1.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-
7.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/gt-coverage.jar" does not poi
nt to a valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry jsr-275-1.0-beta-2.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/j
boss-7.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/gt-coverage.jar" does no
t point to a valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry geoapi-pending-2.3-M1.jar in "/C:/java/liferay-portal-6.1.10-ee-ga
1/jboss-7.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/gt-coverage.jar" does
not point to a valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry gt-main-2.6.1.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-
7.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/gt-coverage.jar" does not poi
nt to a valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry jdom-1.0.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2
/standalone/deployments/ROOT.war/WEB-INF/lib/gt-coverage.jar" does not point to
a valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry commons-beanutils-1.7.0.jar in "/C:/java/liferay-portal-6.1.10-ee-
ga1/jboss-7.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/gt-coverage.jar" do
es not point to a valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry commons-logging-1.1.1.jar in "/C:/java/liferay-portal-6.1.10-ee-ga
1/jboss-7.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/gt-coverage.jar" does
not point to a valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry vecmath-1.3.2.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-
7.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/gt-metadata.jar" does not poi
nt to a valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry geoapi-2.3-M1.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-
7.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/gt-metadata.jar" does not poi
nt to a valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry jsr-275-1.0-beta-2.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/j
boss-7.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/gt-metadata.jar" does no
t point to a valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry geoapi-pending-2.3-M1.jar in "/C:/java/liferay-portal-6.1.10-ee-ga
1/jboss-7.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/gt-metadata.jar" does
not point to a valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry jaxb-api.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2
/standalone/deployments/ROOT.war/WEB-INF/lib/jaxb-impl.jar" does not point to a
valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry activation.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0
.2/standalone/deployments/ROOT.war/WEB-INF/lib/jaxb-impl.jar" does not point to
a valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry jsr173_1.0_api.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss
-7.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/jaxb-impl.jar" does not poin
t to a valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry jaxb1-impl.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0
.2/standalone/deployments/ROOT.war/WEB-INF/lib/jaxb-impl.jar" does not point to
a valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry jaxws-api.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.
2/standalone/deployments/ROOT.war/WEB-INF/lib/jaxws-rt.jar" does not point to a
valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry jsr181-api.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0
.2/standalone/deployments/ROOT.war/WEB-INF/lib/jaxws-rt.jar" does not point to
a valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry jsr250-api.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0
.2/standalone/deployments/ROOT.war/WEB-INF/lib/jaxws-rt.jar" does not point to
a valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry saaj-api.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2
/standalone/deployments/ROOT.war/WEB-INF/lib/jaxws-rt.jar" does not point to a
valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry saaj-impl.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.
2/standalone/deployments/ROOT.war/WEB-INF/lib/jaxws-rt.jar" does not point to a
valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry jsr173_api.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0
.2/standalone/deployments/ROOT.war/WEB-INF/lib/jaxws-rt.jar" does not point to
a valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry sjsxp.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2/st
andalone/deployments/ROOT.war/WEB-INF/lib/jaxws-rt.jar" does not point to a val
id jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry woodstox.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2
/standalone/deployments/ROOT.war/WEB-INF/lib/jaxws-rt.jar" does not point to a
valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry resolver.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2
/standalone/deployments/ROOT.war/WEB-INF/lib/jaxws-rt.jar" does not point to a
valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry jaxb-api.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2
/standalone/deployments/ROOT.war/WEB-INF/lib/jaxws-rt.jar" does not point to a
valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry jaxb-impl.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.
2/standalone/deployments/ROOT.war/WEB-INF/lib/jaxws-rt.jar" does not point to a
valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry activation.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0
.2/standalone/deployments/ROOT.war/WEB-INF/lib/jaxws-rt.jar" does not point to
a valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry stax-ex.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2/
standalone/deployments/ROOT.war/WEB-INF/lib/jaxws-rt.jar" does not point to a v
alid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry streambuffer.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7
.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/jaxws-rt.jar" does not point t
o a valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry stax-utils.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0
.2/standalone/deployments/ROOT.war/WEB-INF/lib/jaxws-rt.jar" does not point to
a valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry ridl.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2/sta
ndalone/deployments/ROOT.war/WEB-INF/lib/juh.jar" does not point to a valid jar
for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry jurt.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2/sta
ndalone/deployments/ROOT.war/WEB-INF/lib/juh.jar" does not point to a valid jar
for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry ridl.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2/sta
ndalone/deployments/ROOT.war/WEB-INF/lib/jurt.jar" does not point to a valid ja
r for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry unoloader.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.
2/standalone/deployments/ROOT.war/WEB-INF/lib/jurt.jar" does not point to a val
id jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry ../../lib/ in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2/s
tandalone/deployments/ROOT.war/WEB-INF/lib/jurt.jar" does not point to a valid
jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry ../bin/ in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2/stan
dalone/deployments/ROOT.war/WEB-INF/lib/jurt.jar" does not point to a valid jar
for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry xbean.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2/st
andalone/deployments/ROOT.war/WEB-INF/lib/liferay-rhino.jar" does not point to
a valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry jaxp-api.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2
/standalone/deployments/ROOT.war/WEB-INF/lib/saaj-api.jar" does not point to a
valid jar for a Class-Path reference.
16:30:30,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry jax-qname.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.
2/standalone/deployments/ROOT.war/WEB-INF/lib/saaj-api.jar" does not point to a
valid jar for a Class-Path reference.
16:30:30,581 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry activation.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0
.2/standalone/deployments/ROOT.war/WEB-INF/lib/saaj-api.jar" does not point to
a valid jar for a Class-Path reference.
16:30:30,581 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry servlet.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2/
standalone/deployments/ROOT.war/WEB-INF/lib/saaj-api.jar" does not point to a v
alid jar for a Class-Path reference.
16:30:30,581 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry saaj-api.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2
/standalone/deployments/ROOT.war/WEB-INF/lib/saaj-impl.jar" does not point to a
valid jar for a Class-Path reference.
16:30:30,581 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry activation.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0
.2/standalone/deployments/ROOT.war/WEB-INF/lib/saaj-impl.jar" does not point to
a valid jar for a Class-Path reference.
16:30:30,581 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry xml-apis.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2
/standalone/deployments/ROOT.war/WEB-INF/lib/serializer.jar" does not point to
a valid jar for a Class-Path reference.
16:30:30,581 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry lib/ant.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2/
standalone/deployments/ROOT.war/WEB-INF/lib/truezip.jar" does not point to a va
lid jar for a Class-Path reference.
16:30:30,581 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry lib/lcrypto-jdk14-135.jar in "/C:/java/liferay-portal-6.1.10-ee-ga
1/jboss-7.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/truezip.jar" does not
point to a valid jar for a Class-Path reference.
16:30:30,581 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry xercesImpl.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0
.2/standalone/deployments/ROOT.war/WEB-INF/lib/xalan.jar" does not point to a v
alid jar for a Class-Path reference.
16:30:30,581 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry xml-apis.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2
/standalone/deployments/ROOT.war/WEB-INF/lib/xalan.jar" does not point to a val
id jar for a Class-Path reference.
16:30:30,581 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry serializer.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0
.2/standalone/deployments/ROOT.war/WEB-INF/lib/xalan.jar" does not point to a v
alid jar for a Class-Path reference.
16:30:30,581 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry commons-cli.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.
0.2/standalone/deployments/ROOT.war/WEB-INF/lib/xuggle-xuggler.jar" does not po
int to a valid jar for a Class-Path reference.
16:30:30,581 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry logback-classic.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jbos
s-7.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/xuggle-xuggler.jar" does no
t point to a valid jar for a Class-Path reference.
16:30:30,581 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry logback-core.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7
.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/xuggle-xuggler.jar" does not p
oint to a valid jar for a Class-Path reference.
16:30:30,581 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Cla
ss Path entry slf4j-api.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.
2/standalone/deployments/ROOT.war/WEB-INF/lib/xuggle-xuggler.jar" does not poin
t to a valid jar for a Class-Path reference.
16:30:33,093 WARN [org.jboss.as.server.deployment.service-loader] (MSC service
thread 1-2) Encountered invalid class name "DRIVER=TRUE" for service type "de.sc
hlichtherle.io.registry.properties"
16:30:33,109 WARN [org.jboss.as.server.deployment.service-loader] (MSC service
thread 1-2) Encountered invalid class name "DEFAULT=ear|jar|war|zip" for service
type "de.schlichtherle.io.registry.properties"
16:30:33,109 WARN [org.jboss.as.server.deployment.service-loader] (MSC service
thread 1-2) Encountered invalid class name "zip=de.schlichtherle.io.archive.zip.
ZipDriver" for service type "de.schlichtherle.io.registry.properties"
16:30:33,109 WARN [org.jboss.as.server.deployment.service-loader] (MSC service
thread 1-2) Encountered invalid class name "ear|jar|war=de.schlichtherle.io.arch
ive.zip.JarDriver" for service type "de.schlichtherle.io.registry.properties"
16:30:33,109 WARN [org.jboss.as.server.deployment.service-loader] (MSC service
thread 1-2) Encountered invalid class name "odg|odp|ods|odt=de.schlichtherle.io.
archive.zip.OdfDriver" for service type "de.schlichtherle.io.registry.properties
"
16:30:33,109 WARN [org.jboss.as.server.deployment.service-loader] (MSC service
thread 1-2) Encountered invalid class name "otg|otp|ots|ott=de.schlichtherle.io.
archive.zip.OdfDriver" for service type "de.schlichtherle.io.registry.properties
"
16:30:33,109 WARN [org.jboss.as.server.deployment.service-loader] (MSC service
thread 1-2) Encountered invalid class name "odb|odf|odm|oth=de.schlichtherle.io.
archive.zip.OdfDriver" for service type "de.schlichtherle.io.registry.properties
"
16:30:33,109 WARN [org.jboss.as.server.deployment.service-loader] (MSC service
thread 1-2) Encountered invalid class name "exe=de.schlichtherle.io.archive.zip.
ReadOnlySfxDriver" for service type "de.schlichtherle.io.registry.properties"
16:30:33,109 WARN [org.jboss.as.server.deployment.service-loader] (MSC service
thread 1-2) Encountered invalid class name "tzp|zip.rae|zip.raes=de.schlichtherl
e.io.archive.zip.raes.SafeZipRaesDriver" for service type "de.schlichtherle.io.r
egistry.properties"
16:30:33,109 WARN [org.jboss.as.server.deployment.service-loader] (MSC service
thread 1-2) Encountered invalid class name "tar=de.schlichtherle.io.archive.tar.
TarDriver" for service type "de.schlichtherle.io.registry.properties"
16:30:33,109 WARN [org.jboss.as.server.deployment.service-loader] (MSC service
thread 1-2) Encountered invalid class name "tgz|tar.gz=de.schlichtherle.io.archi
ve.tar.TarGZipDriver" for service type "de.schlichtherle.io.registry.properties"

16:30:33,109 WARN [org.jboss.as.server.deployment.service-loader] (MSC service
thread 1-2) Encountered invalid class name "tbz2|tar.bz2=de.schlichtherle.io.arc
hive.tar.TarBZip2Driver" for service type "de.schlichtherle.io.registry.properti
es"
16:30:33,124 WARN [org.jboss.as.server.deployment.service-loader] (MSC service
thread 1-2) Encountered invalid class name "org.xmlpull.mxp1.MXParser,org.xmlpul
l.mxp1_serializer.MXSerializer" for service type "org.xmlpull.v1.XmlPullParserFa
ctory"
16:30:33,327 INFO [org.jboss.as.jpa] (MSC service thread 1-2) added javax.persi
stence.api, javaee.api, org.jboss.as.jpa, org.javassist dependencies to ROOT.war

16:30:37,085 INFO [org.jboss.as.jpa] (MSC service thread 1-1) Deployment has it
s own Persistence Provider class org.hibernate.ejb.HibernatePersistence
16:30:39,330 INFO [com.liferay.portal.kernel.deploy.hot.HotDeployUtil] (MSC ser
vice thread 1-1) Initializing hot deploy manager 18086647
16:30:39,346 INFO (MSC service thread 1-1) Loading vfs:/C:/java/lifera
y-portal-6.1.10-ee-ga1/jboss-7.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/p
ortal-impl.jar/system.properties
16:30:39,440 INFO [com.liferay.portal.kernel.util.ServerDetector] (MSC service
thread 1-1) Detected server jboss
16:30:39,455 INFO [com.liferay.portal.util.PropsUtil] (MSC service thread 1-1)
Global lib directory C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2/modules/co
m/liferay/portal/main/
16:30:39,455 INFO [com.liferay.portal.util.PropsUtil] (MSC service thread 1-1)
Portal lib directory /C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2/standalon
e/deployments/ROOT.war/WEB-INF/lib/
16:30:39,580 INFO (MSC service thread 1-1) 16:30:39,580 INFO [EasyCon
f:122] Refreshed the configuration of all components
16:30:39,970 INFO (MSC service thread 1-1) 16:30:39,970 INFO [Configu
rationLoader:56] Properties for vfs:/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-
7.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/portal-impl.jar/portal loaded
from [vfs:/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2/standalone/deploymen
ts/ROOT.war/WEB-INF/lib/portal-impl.jar/portal.properties]
16:30:39,970 INFO (MSC service thread 1-1) Loading vfs:/C:/java/lifera
y-portal-6.1.10-ee-ga1/jboss-7.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/p
ortal-impl.jar/portal.properties
16:30:40,438 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-
host].[/]] (MSC service thread 1-1) Initializing Spring root WebApplicationConte
xt
16:30:48,234 INFO (MSC service thread 1-1) 16:30:48,234 INFO [Dialect
Detector:80] Determine dialect for HSQL Database Engine 2
16:30:48,250 INFO (MSC service thread 1-1) 16:30:48,250 WARN [Dialect
Detector:95] Liferay is configured to use Hypersonic as its database. Do NOT use
Hypersonic in production. Hypersonic is an embedded database useful for develop
ment and demo'ing purposes. The database settings can be changed in portal-ext.p
roperties.
16:30:48,281 INFO (MSC service thread 1-1) 16:30:48,281 INFO [Dialect
Detector:145] Found dialect org.hibernate.dialect.HSQLDialect
16:30:54,175 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Did
not receive a response to the deployment operation within the allowed timeout p
eriod [120 seconds]. Check the server configurationfile and the server logs to f
ind more about the status of the deployment.
16:30:54,175 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads -
2) Deployment of "ROOT.war" was rolled back with failure message Operation canc
elled
16:31:20,061 INFO (MSC service thread 1-1) Starting Liferay Portal Ent
erprise Edition 6.1 EE GA1 (Paton / Build 6110 / February 15, 2012)
16:31:20,918 INFO (MSC service thread 1-1) 16:31:20,903 INFO [BaseDB:
406] Database supports case sensitive queries
16:31:21,667 INFO (MSC service thread 1-1) 16:31:21,667 INFO [VerifyP
rocess:76] Verifying com.liferay.portal.verify.VerifyProcessSuite
16:31:21,667 INFO (MSC service thread 1-1) 16:31:21,667 INFO [VerifyP
rocess:76] Verifying com.liferay.portal.verify.VerifyProperties
16:31:21,682 INFO (MSC service thread 1-1) 16:31:21,682 INFO [VerifyP
rocess:76] Verifying com.liferay.portal.verify.VerifyMySQL
16:31:21,698 INFO (MSC service thread 1-1) 16:31:21,698 INFO [VerifyP
rocess:76] Verifying com.liferay.portal.verify.VerifySQLServer
16:31:21,714 INFO (MSC service thread 1-1) 16:31:21,714 INFO [VerifyP
rocess:76] Verifying com.liferay.portal.verify.VerifyCounter
16:31:21,729 INFO (MSC service thread 1-1) 16:31:21,729 INFO [VerifyP
rocess:76] Verifying com.liferay.portal.verify.VerifyUUID
16:31:21,760 INFO (MSC service thread 1-1) 16:31:21,760 INFO [VerifyP
rocess:76] Verifying com.liferay.portal.verify.VerifyPermission
16:31:24,068 INFO (MSC service thread 1-1) 16:31:24,068 INFO [VerifyP
rocess:76] Verifying com.liferay.portal.verify.VerifyRole
16:31:24,505 INFO (MSC service thread 1-1) 16:31:24,505 INFO [VerifyP
rocess:76] Verifying com.liferay.portal.verify.VerifyAsset
16:31:24,505 INFO (MSC service thread 1-1) 16:31:24,505 INFO [Upgrade
Process:207] Upgrading com.liferay.portal.upgrade.util.UpgradeAssetPublisherManu
alEntries
16:31:24,520 INFO (MSC service thread 1-1) 16:31:24,520 INFO [VerifyP
rocess:76] Verifying com.liferay.portal.verify.VerifyBlogs
16:31:24,520 INFO (MSC service thread 1-1) 16:31:24,520 INFO [VerifyP
rocess:76] Verifying com.liferay.portal.verify.VerifyBookmarks
16:31:24,536 INFO (MSC service thread 1-1) 16:31:24,536 INFO [VerifyP
rocess:76] Verifying com.liferay.portal.verify.VerifyCalendar
16:31:24,552 INFO (MSC service thread 1-1) 16:31:24,552 INFO [VerifyP
rocess:76] Verifying com.liferay.portal.verify.VerifyDocumentLibrary
16:31:24,567 INFO (MSC service thread 1-1) 16:31:24,567 INFO [VerifyP
rocess:76] Verifying com.liferay.portal.verify.VerifyGroup
16:31:24,754 INFO (MSC service thread 1-1) 16:31:24,754 INFO [VerifyP
rocess:76] Verifying com.liferay.portal.verify.VerifyJournal
16:31:24,770 INFO (MSC service thread 1-1) 16:31:24,770 INFO [VerifyP
rocess:76] Verifying com.liferay.portal.verify.VerifyLayout
16:31:24,786 INFO (MSC service thread 1-1) 16:31:24,786 INFO [VerifyP
rocess:76] Verifying com.liferay.portal.verify.VerifyMessageBoards
16:31:24,817 INFO (MSC service thread 1-1) 16:31:24,817 INFO [VerifyP
rocess:76] Verifying com.liferay.portal.verify.VerifyOrganization
16:31:24,863 INFO (MSC service thread 1-1) 16:31:24,863 INFO [VerifyP
rocess:76] Verifying com.liferay.portal.verify.VerifyResourcePermissions
16:31:26,626 INFO (MSC service thread 1-1) 16:31:26,626 INFO [VerifyR
esourcePermissions:147] Processed 100 resource permissions for com.liferay.porta
l.model.User
16:31:27,826 INFO (MSC service thread 1-1) 16:31:27,826 INFO [VerifyP
rocess:76] Verifying com.liferay.portal.verify.VerifySocial
16:31:27,826 INFO (MSC service thread 1-1) 16:31:27,826 INFO [VerifyP
rocess:76] Verifying com.liferay.portal.verify.VerifyUser
16:31:27,857 INFO (MSC service thread 1-1) 16:31:27,857 INFO [VerifyP
rocess:76] Verifying com.liferay.portal.verify.VerifyWiki
16:31:27,873 INFO (MSC service thread 1-1) 16:31:27,873 INFO [License
Manager:?] Failed to find directory C:\java\liferay-portal-6.1.10-ee-ga1\data\li
cense
16:31:27,873 INFO (MSC service thread 1-1) 16:31:27,873 ERROR [License
Manager:?] No binary licenses found
16:31:27,889 INFO (MSC service thread 1-1) 16:31:27,889 INFO [PluginP
ackageUtil:1023] Reading plugin package for the root context
16:31:51,934 INFO (MSC service thread 1-1) 16:31:51,934 INFO [AutoDep
loyDir:84] Creating missing directory C:\java\liferay-portal-6.1.10-ee-ga1\deplo
y
16:31:51,934 INFO (MSC service thread 1-1) 16:31:51,934 INFO [AutoDep
loyDir:105] Auto deploy scanner started for C:\java\liferay-portal-6.1.10-ee-ga1
\deploy
16:32:05,469 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-
host].[/]] (MSC service thread 1-1) Initializing Spring FrameworkServlet 'Remoti
ng Servlet'
16:32:09,742 INFO [org.jboss.web] (MSC service thread 1-1) registering web cont
ext:
16:32:09,804 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-
host].[/]] (MSC service thread 1-3) Destroying Spring FrameworkServlet 'Remoting
Servlet'
16:32:10,381 INFO [hsqldb.db.HSQLDB35ACF0BD51.ENGINE] (MSC service thread 1-3)
Database closed
16:32:10,521 INFO [org.quartz.core.QuartzScheduler] (MSC service thread 1-3) Sc
heduler PersistedQuartzSchedulerEngineInstance_$_NON_CLUSTERED shutting down.
16:32:10,521 INFO [org.quartz.core.QuartzScheduler] (MSC service thread 1-3) Sc
heduler PersistedQuartzSchedulerEngineInstance_$_NON_CLUSTERED paused.
16:32:10,521 INFO [org.quartz.core.QuartzScheduler] (MSC service thread 1-3) Sc
heduler PersistedQuartzSchedulerEngineInstance_$_NON_CLUSTERED shutdown complete
.
16:32:10,521 INFO [org.quartz.core.QuartzScheduler] (MSC service thread 1-3) Sc
heduler MemoryQuartzSchedulerEngineInstance_$_NON_CLUSTERED shutting down.
16:32:10,521 INFO [org.quartz.core.QuartzScheduler] (MSC service thread 1-3) Sc
heduler MemoryQuartzSchedulerEngineInstance_$_NON_CLUSTERED paused.
16:32:10,537 INFO [org.quartz.core.QuartzScheduler] (MSC service thread 1-3) Sc
heduler MemoryQuartzSchedulerEngineInstance_$_NON_CLUSTERED shutdown complete.
16:32:11,816 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-
host].[/]] (MSC service thread 1-3) Closing Spring root WebApplicationContext
16:32:11,893 INFO [com.liferay.portal.kernel.messaging.BaseAsyncDestination] (M
SC service thread 1-3) The following 0 tasks were not executed due to shutown: [
]
16:32:11,909 INFO [com.liferay.portal.kernel.messaging.BaseAsyncDestination] (M
SC service thread 1-3) The following 0 tasks were not executed due to shutown: [
]
16:32:11,971 WARNING [com.liferay.portal.kernel.cluster.ClusterExecutorUtil] (MS
C service thread 1-3) ClusterExecutorUtil has not been initialized
16:32:12,252 INFO [org.hibernate.impl.SessionFactoryImpl] (MSC service thread 1
-3) closing
16:32:12,252 INFO [org.hibernate.impl.SessionFactoryImpl] (MSC service thread 1
-3) closing
16:32:13,562 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) Sto
pped deployment ROOT.war in 79547ms
Anonymous
RE: Liferay 6.1 Jboss 7
April 5, 2012 10:24 AM
Answer

Anonymous

The two lines that caught my eye is:

16:30:54,175 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Did
not receive a response to the deployment operation within the allowed timeout p
eriod [120 seconds]. Check the server configurationfile and the server logs to f
ind more about the status of the deployment.
16:30:54,175 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads -
2) Deployment of "ROOT.war" was rolled back with failure message Operation canc
elled

did you check your standalone.xml config file to see if it matches your custom system settings? I'll try to replicate your set up and compare my logs
Brian Ko
RE: Liferay 6.1 Jboss 7
April 5, 2012 2:02 PM
Answer

Brian Ko

Rank: Junior Member

Posts: 70

Join Date: February 11, 2010

Recent Posts

I did not change anything. I just unzip the file and started the jboss. Is there any procedures I need to follow after unzipping and before starting jboss?
Anonymous
RE: Liferay 6.1 Jboss 7
April 5, 2012 3:11 PM
Answer

Anonymous

I talked to Jerry and he recommends maybe trying to deploy it on a fresh VM to see if you get problems there. That way we can at least rule out a few variables. When I was deploying it in a new WinXP VM, the only thing I had to do was install java first, then double click on standalone.bat and it started and deployed with no issues at all. Let me try again with installing JDK6 instead of the JRE and see if I can reproduce your errors.

One thing to also mention is possibly updating your JDK to the latest 1.6 release, 31 (and not JDK 1.7). Your present configuration is on 1.6u6, which is also out of date. I don't think that's the problem, but it's worth a shot. Let me know!
Anonymous
RE: Liferay 6.1 Jboss 7
April 5, 2012 5:06 PM
Answer

Anonymous

after analyzing your console log with one of my colleagues, it seems the situation may be this:
16:28:52,981 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) Starting deployment of "ROOT.war"
16:30:30,550 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry asm-3.3.jar in "/C:/java/liferay-portal-6.1.10-ee-ga1/jboss-7.0.2/standalone/deployments/ROOT.war/WEB-INF/lib/asm-xml.jar" does not point to a valid jar for a Class-Path reference.
there's almost two minutes between those messages

what my console log says:
23:05:54,056 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "ROOT.war"
23:06:13,174 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry asm-3.3.jar in "/C:/........
so it doesn't time out because my computer has the system resources to process it within the 120 seconds.

from my colleague:
the warn message is interesting. looks like JBoss is doing something to validate all the JARs
if you open up asm-xml.jar and look in the MANIFEST.MF file in the META-INF folder, you'll see why it's looking for asm-3.3.jar

solution:
open your standalone.xml (or whatever config you are using) and look for deployment-scanner subsystem and modify to add deployment-timeout
for instance:
<deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" deployment-timeout="900"/>
will set timeout to 900 seconds instead of the 120 that you currently have.

This may be the fix to your issue. We understand the hardware limitations can be a bottleneck, and so if possible, it may be about time to upgrade the hardware or to switch to the Tomcat server. Let me know, Brian. Thx!
Brian Ko
RE: Liferay 6.1 Jboss 7
April 6, 2012 8:44 AM
Answer

Brian Ko

Rank: Junior Member

Posts: 70

Join Date: February 11, 2010

Recent Posts

Everest,

Thank you! That fixed the problem. I will post this link to the thread I created.

Brian
Anonymous
RE: Liferay 6.1 Jboss 7
April 6, 2012 9:21 AM
Answer

Anonymous

Glad to hear, Brian! The difficulty does commonly come from the thousands of set up variations, but I'm glad we could enrich your experience with Liferay!
Jack Chung
RE: Liferay 6.1 Jboss 7
April 20, 2012 7:43 AM
Answer

Jack Chung

Rank: New Member

Posts: 19

Join Date: November 30, 2011

Recent Posts

For the jboss 7.1.1 error, the only way that i was able to resolve it was to modify the WEB-INF/jboss-deployment-structure.xml with the following:

- REPLACE

<module name="system" export="false">
<imports>
<include path="com/sun/jmx"/>
<exclude path="/**" />
</imports>
</module>

- WITH

<system>
<paths>
<path name="com/sun/jmx"/>
</paths>
</system>

Also, in the same file, make sure urn:jboss:deployment-structure:1.1 is "1.1", not "1.0" :

<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1">


I think i found the solution somewhere in the jboss forums unrelated to liferay, but had a similar error.
Hitoshi Ozawa
RE: Liferay 6.1 Jboss 7
April 22, 2012 7:16 AM
Answer

Hitoshi Ozawa

Rank: Liferay Legend

Posts: 7990

Join Date: March 23, 2010

Recent Posts

Yes, you'll need to make some modification to make jboss bundle work. I think the next release is coming out in few more days, probably better to wait becauase 6.1.0 GA1 contains too many bugs anyways.
Trenton Perceval
RE: Liferay 6.1 Jboss 7
May 8, 2012 2:44 AM
Answer

Trenton Perceval

Rank: New Member

Posts: 1

Join Date: May 8, 2012

Recent Posts

Hitoshi Ozawa:
Yes, you'll need to make some modification to make jboss bundle work. I think the next release is coming out in few more days, probably better to wait becauase 6.1.0 GA1 contains too many bugs anyways.
Do you have any confirmed information about forthcoming release?
Hitoshi Ozawa
RE: Liferay 6.1 Jboss 7
May 8, 2012 5:26 AM
Answer

Hitoshi Ozawa

Rank: Liferay Legend

Posts: 7990

Join Date: March 23, 2010

Recent Posts

Yes! James Falkner, who is with Liferay.com, said it was again being pushed back. This time to May 25th.
devaraj s
RE: Liferay 6.1 Jboss 7
July 2, 2012 9:07 PM
Answer

devaraj s

Rank: Regular Member

Posts: 206

Join Date: May 21, 2012

Recent Posts

Hi david,
I followed the document and installed liferay 6.1 on jboss 7.1 existing server. In server I achieved the deployment of liferay but when i try to login to portal page will not load I am not geetting what is happening. Please can any one tell me the solution.
Thanks in advance.
Oliver T.
RE: Liferay 6.1 Jboss 7
January 10, 2014 5:52 AM
Answer

Oliver T.

Rank: New Member

Posts: 17

Join Date: January 15, 2009

Recent Posts

Dear Everest,

sorry for the thread necromancy, but do you know if this is fixed permanently?

I just try to install the EE 6.1.3 / JBoss bundle which includes the JBoss 7.1. and am running into exactly the same classpath / jardependency issue :

https://www.liferay.com/community/forums/-/message_boards/message/33042965...

Regards,
Oliver