Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
Luis Losada
Problem deployment Liferay 6.1.1
May 31, 2013 2:38 AM
Answer

Luis Losada

Rank: New Member

Posts: 9

Join Date: May 20, 2013

Recent Posts

I trying deploy Liferay in GlassFish 2.1.1. When I deploy the war I always obtain the next error:

Loading file:/C:/Herramientas/GlassFishESBv22/glassfish/domains/lif6/generated/jsp/j2ee-modules/liferay-portal-6.1.1-ce-ga2-20120731132656558/loader/portal.properties
PWC1412: WebModule[] ServletContext.log():Initializing Spring root WebApplicationContext
10:26:57,876 INFO [Timer-8][DialectDetector:71] Determine dialect for HSQL Database Engine 2
10:26:57,876 WARN [Timer-8][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.
10:26:57,939 INFO [Timer-8][DialectDetector:136] Found dialect org.hibernate.dialect.HSQLDialect
WebModule[]StandardWrapper.Throwable
java.lang.NoSuchMethodError: org.objectweb.asm.ClassReader.accept(Lorg/objectweb/asm/ClassVisitor;I)V
at jodd.paramo.Paramo.resolveParameters(Paramo.java:61)
at com.liferay.portal.util.MethodParametersResolverImpl.resolveMethodParameters(MethodParametersResolverImpl.java:46)
at com.liferay.portal.kernel.util.MethodParametersResolverUtil.resolveMethodParameters(MethodParametersResolverUtil.java:34)
at com.liferay.portal.jsonwebservice.JSONWebServiceActionConfig.<init>(JSONWebServiceActionConfig.java:43)
at com.liferay.portal.jsonwebservice.JSONWebServiceActionsManagerImpl.registerJSONWebServiceAction(JSONWebServiceActionsManagerImpl.java:214)
at com.liferay.portal.kernel.jsonwebservice.JSONWebServiceActionsManagerUtil.registerJSONWebServiceAction(JSONWebServiceActionsManagerUtil.java:73)
at com.liferay.portal.jsonwebservice.JSONWebServiceConfigurator._registerJSONWebServiceAction(JSONWebServiceConfigurator.java:396)
at com.liferay.portal.jsonwebservice.JSONWebServiceConfigurator._onJSONWebServiceClass(JSONWebServiceConfigurator.java:367)
at com.liferay.portal.jsonwebservice.JSONWebServiceConfigurator.onEntry(JSONWebServiceConfigurator.java:209)
at jodd.io.findfile.ClassFinder.scanEntry(ClassFinder.java:376)
at jodd.io.findfile.ClassFinder.scanJarFile(ClassFinder.java:269)
at jodd.io.findfile.ClassFinder.scanPath(ClassFinder.java:238)
at jodd.io.findfile.ClassFinder.scanPaths(ClassFinder.java:179)
at com.liferay.portal.jsonwebservice.JSONWebServiceConfigurator._configure(JSONWebServiceConfigurator.java:225)
at com.liferay.portal.jsonwebservice.JSONWebServiceConfigurator.configure(JSONWebServiceConfigurator.java:168)
at com.liferay.portal.jsonwebservice.JSONWebServiceServiceAction.<init>(JSONWebServiceServiceAction.java:51)
at com.liferay.portal.jsonwebservice.JSONWebServiceServlet.getJSONAction(JSONWebServiceServlet.java:169)
at com.liferay.portal.servlet.JSONServlet.init(JSONServlet.java:52)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1100)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1023)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4969)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:5376)
at com.sun.enterprise.web.WebModule.start(WebModule.java:345)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:986)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:970)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:704)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1649)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1254)
at com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:182)
at com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:278)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1005)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:992)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)
at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:231)
at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:966)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:280)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:298)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:584)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:390)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:373)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:477)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:170)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:583)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployJavaEEArchive(AutoDeployer.java:564)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deploy(AutoDeployer.java:495)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:270)
at com.sun.enterprise.deployment.autodeploy.AutoDeployControllerImpl$AutoDeployTask.run(AutoDeployControllerImpl.java:374)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
WebModule[]PWC1396: Servlet threw load() exception
java.lang.NoSuchMethodError: org.objectweb.asm.ClassReader.accept(Lorg/objectweb/asm/ClassVisitor;I)V
at jodd.paramo.Paramo.resolveParameters(Paramo.java:61)
at com.liferay.portal.util.MethodParametersResolverImpl.resolveMethodParameters(MethodParametersResolverImpl.java:46)
at com.liferay.portal.kernel.util.MethodParametersResolverUtil.resolveMethodParameters(MethodParametersResolverUtil.java:34)
at com.liferay.portal.jsonwebservice.JSONWebServiceActionConfig.<init>(JSONWebServiceActionConfig.java:43)
at com.liferay.portal.jsonwebservice.JSONWebServiceActionsManagerImpl.registerJSONWebServiceAction(JSONWebServiceActionsManagerImpl.java:214)
at com.liferay.portal.kernel.jsonwebservice.JSONWebServiceActionsManagerUtil.registerJSONWebServiceAction(JSONWebServiceActionsManagerUtil.java:73)
at com.liferay.portal.jsonwebservice.JSONWebServiceConfigurator._registerJSONWebServiceAction(JSONWebServiceConfigurator.java:396)
at com.liferay.portal.jsonwebservice.JSONWebServiceConfigurator._onJSONWebServiceClass(JSONWebServiceConfigurator.java:367)
at com.liferay.portal.jsonwebservice.JSONWebServiceConfigurator.onEntry(JSONWebServiceConfigurator.java:209)
at jodd.io.findfile.ClassFinder.scanEntry(ClassFinder.java:376)
at jodd.io.findfile.ClassFinder.scanJarFile(ClassFinder.java:269)
at jodd.io.findfile.ClassFinder.scanPath(ClassFinder.java:238)
at jodd.io.findfile.ClassFinder.scanPaths(ClassFinder.java:179)
at com.liferay.portal.jsonwebservice.JSONWebServiceConfigurator._configure(JSONWebServiceConfigurator.java:225)
at com.liferay.portal.jsonwebservice.JSONWebServiceConfigurator.configure(JSONWebServiceConfigurator.java:168)
at com.liferay.portal.jsonwebservice.JSONWebServiceServiceAction.<init>(JSONWebServiceServiceAction.java:51)
at com.liferay.portal.jsonwebservice.JSONWebServiceServlet.getJSONAction(JSONWebServiceServlet.java:169)
at com.liferay.portal.servlet.JSONServlet.init(JSONServlet.java:52)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1100)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1023)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4969)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:5376)
at com.sun.enterprise.web.WebModule.start(WebModule.java:345)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:986)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:970)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:704)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1649)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1254)
at com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:182)
at com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:278)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1005)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:992)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)
at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:231)
at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:966)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:280)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:298)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:584)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:390)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:373)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:477)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:170)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:583)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployJavaEEArchive(AutoDeployer.java:564)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deploy(AutoDeployer.java:495)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:270)
at com.sun.enterprise.deployment.autodeploy.AutoDeployControllerImpl$AutoDeployTask.run(AutoDeployControllerImpl.java:374)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
ContainerBase.addChild: start:
LifecycleException: java.lang.NoSuchMethodError: org.objectweb.asm.ClassReader.accept(Lorg/objectweb/asm/ClassVisitor;I)V
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4979)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:5376)
at com.sun.enterprise.web.WebModule.start(WebModule.java:345)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:986)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:970)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:704)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1649)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1254)
at com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:182)
at com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:278)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1005)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:992)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)
at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:231)
at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:966)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:280)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:298)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:584)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:390)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:373)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:477)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:170)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:583)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployJavaEEArchive(AutoDeployer.java:564)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deploy(AutoDeployer.java:495)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:270)
at com.sun.enterprise.deployment.autodeploy.AutoDeployControllerImpl$AutoDeployTask.run(AutoDeployControllerImpl.java:374)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
PWC1412: WebModule[] ServletContext.log():Closing Spring root WebApplicationContext
chirag @ India
RE: Problem deployment Liferay 6.1.1
May 31, 2013 4:13 AM
Answer

chirag @ India

Rank: Regular Member

Posts: 129

Join Date: December 20, 2011

Recent Posts

hi Luis Losada ,

You should use other(MY-Sql) db software instead of Hypersonic. You can not used in-build database it is for demo purpose.

Go TO tomcat-7.0.35\webapps\ROOT\WEB-INF\classes in that you will find portal-ext.properties file then configure for db.

For more detail check this wiki

HTH
Chirag @ india
Manish Yadav
RE: Problem deployment Liferay 6.1.1
May 31, 2013 5:47 AM
Answer

Manish Yadav

Rank: Expert

Posts: 385

Join Date: May 26, 2012

Recent Posts

Hi Luis Losada,
How you unzipped your liferayBundle,Sometime winzip is not able to unzip files properly.Try to unzip folder with 7z and then start if error still persist then use someother db as Chirag mention in his post.


Thanks & Regards
Manish Banwari lal Yadav
Email:- manishyadav1103@gmail.com
Juan Gonzalez
RE: Problem deployment Liferay 6.1.1
May 31, 2013 8:32 AM
Answer

Juan Gonzalez

LIFERAY STAFF

Rank: Liferay Legend

Posts: 2137

Join Date: October 28, 2008

Recent Posts

What steps did you follow to deploy in Glassfish 2.1.1?
Luis Losada
RE: Problem deployment Liferay 6.1.1
June 2, 2013 3:03 AM
Answer

Luis Losada

Rank: New Member

Posts: 9

Join Date: May 20, 2013

Recent Posts

1º Create a new domain

2º Add the libraries to ...\domain\lib\

3º Add to domain.xml:
<jvm-options>-Dfile.encoding=UTF8</jvm-options>
<jvm-options>-Djava.net.preferIPv4Stack=true</jvm-options>
<jvm-options>-Dorg.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES=false</jvm-options>
<jvm-options>-Duser.timezone=GMT</jvm-options>
<jvm-options>-Xmx1024m</jvm-options>

4º Copy liferay-portal.war

5º Start domain
Luis Losada
RE: Problem deployment Liferay 6.1.1
June 2, 2013 3:05 AM
Answer

Luis Losada

Rank: New Member

Posts: 9

Join Date: May 20, 2013

Recent Posts

The problem is with the glassfish include in OpenESB 2.2. I have a lot of program in this server. I have tried it again with the normal GlassFish 2.1 and in this case the deployment is ok.
Juan Gonzalez
RE: Problem deployment Liferay 6.1.1
June 2, 2013 10:46 AM
Answer

Juan Gonzalez

LIFERAY STAFF

Rank: Liferay Legend

Posts: 2137

Join Date: October 28, 2008

Recent Posts

So what libraries reside in domain/lib ?

Guess there are some jars that are used by both OpenESB and Liferay...
Luis Losada
RE: Problem deployment Liferay 6.1.1
June 3, 2013 2:47 AM
Answer

Luis Losada

Rank: New Member

Posts: 9

Join Date: May 20, 2013

Recent Posts

Install liferray in GlassFish 2.1.1 (not openESemoticon is ok for me. I have the EJBs in openESB but I use the normal GlassFish for my portlets.

Now I have a diferent problem. When I start the server I obtain the next error:

[#|2013-06-03T08:17:39.296+0000|INFO|sun-appserver2.1|javax.enterprise.system.stream.out|_ThreadID=15;_ThreadName=pool-1-thread-7;|08:17:39,296 ERROR [pool-1-thread-7][ServerCapabilitiesUtil:58] Unable to determine server capabilities
java.lang.NoSuchFieldException: dasConfig
at java.lang.Class.getDeclaredField(Class.java:1882)
at com.liferay.portal.server.capabilities.GlassfishServerCapabilities.determineSupportsHotDeploy(GlassfishServerCapabilities.java:95)
at com.liferay.portal.server.capabilities.GlassfishServerCapabilities.determine(GlassfishServerCapabilities.java:32)
at com.liferay.portal.server.capabilities.ServerCapabilitiesUtil.determineServerCapabilities(ServerCapabilitiesUtil.java:55)
at com.liferay.portal.servlet.MainServlet.initServerDetector(MainServlet.java:994)
at com.liferay.portal.servlet.MainServlet.init(MainServlet.java:230)
at javax.servlet.GenericServlet.init(GenericServlet.java:270)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1100)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1023)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4969)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:5376)
at com.sun.enterprise.web.WebModule.start(WebModule.java:345)
at com.sun.enterprise.web.LifecycleStarter.doRun(LifecycleStarter.java:58)
at com.sun.appserv.management.util.misc.RunnableBase.runSync(RunnableBase.java:304)
at com.sun.appserv.management.util.misc.RunnableBase.run(RunnableBase.java:341)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
|#]

The config of the server is ok and autodeploy is enable. I have the portal-ex.properties with the correct patch:

auto.deploy.dest.dir=C\:/Herramientas/glassfish.2.1.1/domains/lf6/autodeploy
Juan Gonzalez
RE: Problem deployment Liferay 6.1.1
June 3, 2013 3:04 AM
Answer

Juan Gonzalez

LIFERAY STAFF

Rank: Liferay Legend

Posts: 2137

Join Date: October 28, 2008

Recent Posts

You can ignore that error.
Luis Losada
RE: Problem deployment Liferay 6.1.1
June 3, 2013 3:29 AM
Answer

Luis Losada

Rank: New Member

Posts: 9

Join Date: May 20, 2013

Recent Posts

I try to ignored but when I try to deploy a portlet, I obtains serverals errors. For example if I try to install the jsf2-portlet example:

10:27:18,147 INFO [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][AutoDeployDir:177] Processing jsf2-portlet-3.1.1-ga2.war
10:27:18,162 INFO [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][PortletAutoDeployListener:77] Copying portlets for C:\Herramientas\deploy\jsf2-portlet-3.1.1-ga2.war
10:27:18,162 INFO [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][BaseDeployer:763] Deploying jsf2-portlet-3.1.1-ga2.war
Expanding: C:\Herramientas\deploy\jsf2-portlet-3.1.1-ga2.war into C:\WINDOWS\20130603102718162
Copying 1 file to C:\WINDOWS\20130603102718162\WEB-INF
Copying 1 file to C:\WINDOWS\20130603102718162\WEB-INF\classes
Copying 1 file to C:\WINDOWS\20130603102718162\WEB-INF\jsp
10:27:18,772 INFO [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][BaseDeployer:2083] Modifying Servlet 2.5 C:\WINDOWS\20130603102718162\WEB-INF\web.xml
Copying 63 files to C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet
Copying 1 file to C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet
Deleting directory C:\WINDOWS\20130603102718162
10:27:20,725 INFO [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][PortletAutoDeployListener:87] Portlets for C:\Herramientas\deploy\jsf2-portlet-3.1.1-ga2.war copied successfully. Deployment will start in a few seconds.
Selecting file C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\util-java.jar for autodeployment.
Exception occures while invoking backend deployment service for file : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\util-java.jar. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\util-java.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\util-java.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB.
Autodeploy failed : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\util-java.jar.
Selecting file C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\commons-io-1.3.2.jar for autodeployment.
Exception occures while invoking backend deployment service for file : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\commons-io-1.3.2.jar. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\commons-io-1.3.2.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\commons-io-1.3.2.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB.
Autodeploy failed : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\commons-io-1.3.2.jar.
Selecting file C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\classes\com\liferay\faces\demos\bean\ApplicantModelBean.class for autodeployment.
Exception occures while invoking backend deployment service for file : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\classes\com\liferay\faces\demos\bean\ApplicantModelBean.class. -- jsf2-portlet/WEB-INF/classes/com/liferay/faces/demos/bean/ApplicantModelBean (wrong name: com/liferay/faces/demos/bean/ApplicantModelBean) -- jsf2-portlet/WEB-INF/classes/com/liferay/faces/demos/bean/ApplicantModelBean (wrong name: com/liferay/faces/demos/bean/ApplicantModelBean)
Autodeploy failed : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\classes\com\liferay\faces\demos\bean\ApplicantModelBean.class.
Selecting file C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\classes\com\liferay\faces\demos\bean\ListModelBean.class for autodeployment.
Exception occures while invoking backend deployment service for file : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\classes\com\liferay\faces\demos\bean\ListModelBean.class. -- jsf2-portlet/WEB-INF/classes/com/liferay/faces/demos/bean/ListModelBean (wrong name: com/liferay/faces/demos/bean/ListModelBean) -- jsf2-portlet/WEB-INF/classes/com/liferay/faces/demos/bean/ListModelBean (wrong name: com/liferay/faces/demos/bean/ListModelBean)
Autodeploy failed : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\classes\com\liferay\faces\demos\bean\ListModelBean.class.
Selecting file C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\classes\com\liferay\faces\demos\bean\PortletPreferencesBackingBean.class for autodeployment.
Exception occures while invoking backend deployment service for file : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\classes\com\liferay\faces\demos\bean\PortletPreferencesBackingBean.class. -- jsf2-portlet/WEB-INF/classes/com/liferay/faces/demos/bean/PortletPreferencesBackingBean (wrong name: com/liferay/faces/demos/bean/PortletPreferencesBackingBean) -- jsf2-portlet/WEB-INF/classes/com/liferay/faces/demos/bean/PortletPreferencesBackingBean (wrong name: com/liferay/faces/demos/bean/PortletPreferencesBackingBean)
Autodeploy failed : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\classes\com\liferay\faces\demos\bean\PortletPreferencesBackingBean.class.
Selecting file C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\commons-logging.jar for autodeployment.
Exception occures while invoking backend deployment service for file : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\commons-logging.jar. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\commons-logging.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\commons-logging.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB.
Autodeploy failed : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\commons-logging.jar.
Selecting file C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\liferay-faces-util-3.1.1-ga2.jar for autodeployment.
Exception occures while invoking backend deployment service for file : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\liferay-faces-util-3.1.1-ga2.jar. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\liferay-faces-util-3.1.1-ga2.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\liferay-faces-util-3.1.1-ga2.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB.
Autodeploy failed : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\liferay-faces-util-3.1.1-ga2.jar.
Selecting file C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\liferay-faces-alloy-3.1.1-ga2.jar for autodeployment.
Exception occures while invoking backend deployment service for file : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\liferay-faces-alloy-3.1.1-ga2.jar. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\liferay-faces-alloy-3.1.1-ga2.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\liferay-faces-alloy-3.1.1-ga2.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB.
Autodeploy failed : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\liferay-faces-alloy-3.1.1-ga2.jar.
Selecting file C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\classes\com\liferay\faces\demos\dto\City.class for autodeployment.
Exception occures while invoking backend deployment service for file : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\classes\com\liferay\faces\demos\dto\City.class. -- jsf2-portlet/WEB-INF/classes/com/liferay/faces/demos/dto/City (wrong name: com/liferay/faces/demos/dto/City) -- jsf2-portlet/WEB-INF/classes/com/liferay/faces/demos/dto/City (wrong name: com/liferay/faces/demos/dto/City)
Autodeploy failed : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\classes\com\liferay\faces\demos\dto\City.class.
Selecting file C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\util-taglib.jar for autodeployment.
Exception occures while invoking backend deployment service for file : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\util-taglib.jar. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\util-taglib.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\util-taglib.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB.
Autodeploy failed : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\util-taglib.jar.
Selecting file C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\classes\com\liferay\faces\demos\util\FacesMessageUtil.class for autodeployment.
Exception occures while invoking backend deployment service for file : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\classes\com\liferay\faces\demos\util\FacesMessageUtil.class. -- jsf2-portlet/WEB-INF/classes/com/liferay/faces/demos/util/FacesMessageUtil (wrong name: com/liferay/faces/demos/util/FacesMessageUtil) -- jsf2-portlet/WEB-INF/classes/com/liferay/faces/demos/util/FacesMessageUtil (wrong name: com/liferay/faces/demos/util/FacesMessageUtil)
Autodeploy failed : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\classes\com\liferay\faces\demos\util\FacesMessageUtil.class.
Selecting file C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\classes\com\liferay\faces\demos\dto\Province.class for autodeployment.
Exception occures while invoking backend deployment service for file : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\classes\com\liferay\faces\demos\dto\Province.class. -- jsf2-portlet/WEB-INF/classes/com/liferay/faces/demos/dto/Province (wrong name: com/liferay/faces/demos/dto/Province) -- jsf2-portlet/WEB-INF/classes/com/liferay/faces/demos/dto/Province (wrong name: com/liferay/faces/demos/dto/Province)
Autodeploy failed : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\classes\com\liferay\faces\demos\dto\Province.class.
Selecting file C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\jsf-impl-2.1.3-b02.jar for autodeployment.
Exception occures while invoking backend deployment service for file : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\jsf-impl-2.1.3-b02.jar. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\jsf-impl-2.1.3-b02.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\jsf-impl-2.1.3-b02.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB.
Autodeploy failed : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\jsf-impl-2.1.3-b02.jar.
Selecting file C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\commons-fileupload-1.2.2.jar for autodeployment.
Exception occures while invoking backend deployment service for file : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\commons-fileupload-1.2.2.jar. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\commons-fileupload-1.2.2.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\commons-fileupload-1.2.2.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB.
Autodeploy failed : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\commons-fileupload-1.2.2.jar.
Selecting file C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\liferay-faces-bridge-api-3.1.1-ga2.jar for autodeployment.
Exception occures while invoking backend deployment service for file : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\liferay-faces-bridge-api-3.1.1-ga2.jar. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\liferay-faces-bridge-api-3.1.1-ga2.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\liferay-faces-bridge-api-3.1.1-ga2.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB.
Autodeploy failed : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\liferay-faces-bridge-api-3.1.1-ga2.jar.
Selecting file C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\jsf-api-2.1.3-b02.jar for autodeployment.
Exception occures while invoking backend deployment service for file : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\jsf-api-2.1.3-b02.jar. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\jsf-api-2.1.3-b02.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\jsf-api-2.1.3-b02.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB.
Autodeploy failed : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\jsf-api-2.1.3-b02.jar.
Selecting file C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\classes\com\liferay\faces\demos\bean\ApplicantBackingBean.class for autodeployment.
Exception occures while invoking backend deployment service for file : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\classes\com\liferay\faces\demos\bean\ApplicantBackingBean.class. -- jsf2-portlet/WEB-INF/classes/com/liferay/faces/demos/bean/ApplicantBackingBean (wrong name: com/liferay/faces/demos/bean/ApplicantBackingBean) -- jsf2-portlet/WEB-INF/classes/com/liferay/faces/demos/bean/ApplicantBackingBean (wrong name: com/liferay/faces/demos/bean/ApplicantBackingBean)
Autodeploy failed : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\classes\com\liferay\faces\demos\bean\ApplicantBackingBean.class.
Selecting file C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\liferay-faces-bridge-impl-3.1.1-ga2.jar for autodeployment.
Exception occures while invoking backend deployment service for file : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\liferay-faces-bridge-impl-3.1.1-ga2.jar. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\liferay-faces-bridge-impl-3.1.1-ga2.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\liferay-faces-bridge-impl-3.1.1-ga2.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB.
Autodeploy failed : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\liferay-faces-bridge-impl-3.1.1-ga2.jar.
Selecting file C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\jboss-el-2.0.0.GA.jar for autodeployment.
Exception occures while invoking backend deployment service for file : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\jboss-el-2.0.0.GA.jar. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\jboss-el-2.0.0.GA.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\jboss-el-2.0.0.GA.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB.
Autodeploy failed : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\jboss-el-2.0.0.GA.jar.
Selecting file C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\util-bridges.jar for autodeployment.
Exception occures while invoking backend deployment service for file : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\util-bridges.jar. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\util-bridges.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\util-bridges.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB.
Autodeploy failed : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\util-bridges.jar.
Selecting file C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\log4j.jar for autodeployment.
Exception occures while invoking backend deployment service for file : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\log4j.jar. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\log4j.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB. -- Unrecognized module type for C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\log4j.jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB.
Autodeploy failed : C:\Herramientas\glassfish.2.1.1\domains\lf6\autodeploy\jsf2-portlet\WEB-INF\lib\log4j.jar.
Juan Gonzalez
RE: Problem deployment Liferay 6.1.1
June 3, 2013 3:35 AM
Answer

Juan Gonzalez

LIFERAY STAFF

Rank: Liferay Legend

Posts: 2137

Join Date: October 28, 2008

Recent Posts

Oh sorry,

I didn't use autodeploy feature with glassfish 2.1.1 and Liferay 6.1.1. I deployed using glassfish console and not applying the properties (so glassfish restart was necessary for every web app deployed using web console).

If you want autodeploy, guess you'd have to change to glassfish 3.1.x version.
Juan Gonzalez
RE: Problem deployment Liferay 6.1.1
June 3, 2013 3:37 AM
Answer

Juan Gonzalez

LIFERAY STAFF

Rank: Liferay Legend

Posts: 2137

Join Date: October 28, 2008

Recent Posts

BTW, what did you copy to autodeploy folder? Seems you copied expanded WAR, You should copy .WAR file