Forum

Accueil » Liferay Portal » English » 3. Development

Vue combinée Vue Plate Arborescence
Sujets [ Précédent | Suivant ]
toggle
Hitesh Methani
Regarding cache not alive issue
28 décembre 2011 02:45
Réponse

Hitesh Methani

Rang: Regular Member

Publications: 163

Date d'inscription: 24 juin 2010

Publications Récentes

Hi Folks,

I am using liferay-portal-jboss-6.0, and facing cache not alive issue when using service builder.

Cache of certain custom entity defined in service.xml expires and the cache not alive issue is seen anytime I deploy any portlet containing service.xml.
Root cause and steps for the reproducing issue are not definite.

If portlet A contains certain entity, say entity E, and it's cache expires due to some reason, then even if I deploy portlet B containing service.xml and not containing entity E,
I face cache not alive issue for entity E when I deploy portlet B or portlet A.

Issue gets resolved when I restart the server. I have defined expirtation-cache to be 0 in all the portlets.

Following is the exception trace for the same.

  1
  201:13:03,072 INFO  [AutoDeployDir:167] Processing StoreFrontManager-portlet-6.0.12.1.war
  301:13:03,077 INFO  [PortletAutoDeployListener:71] Copying portlets for /home/jboss/liferay-portal-6.0-ee-sp2/deploy/StoreFrontManager-portlet-6.0.12.1.war
  4   Expanding:
  5/home/jboss/liferay-portal-6.0-ee-sp2/deploy/StoreFrontManager-portlet-6.0.12.1.war
  6into /tmp/20111228011303085
  7   Copying 1 file to /tmp/20111228011303085/WEB-INF
  8   Copying 1 file to /tmp/20111228011303085/WEB-INF/classes
  9   Copying 1 file to /tmp/20111228011303085/WEB-INF/classes
 10   Copying 1 file to /tmp/20111228011303085/WEB-INF/jsp
 11   Copying 18 files to
 12/home/jboss/liferay-portal-6.0-ee-sp2/jboss-5.1.0/server/default/deploy/StoreFrontManager-portlet.war
 13   Copying 1 file to
 14/home/jboss/liferay-portal-6.0-ee-sp2/jboss-5.1.0/server/default/deploy/StoreFrontManager-portlet.war
 15   Deleting directory /tmp/20111228011303085
 1601:13:03,856 INFO  [PortletAutoDeployListener:81] Portlets for /home/jboss/liferay-portal-6.0-ee-sp2/deploy/StoreFrontManager-portlet-6.0.12.1.war
 17copied successfully. Deployment will start in a few seconds.
 1801:13:12,421 INFO  [TomcatDeployment] undeploy, ctxPath=/StoreFrontManager-portlet
 1901:13:12,431 INFO  [PluginPackageUtil:1077] Reading plugin package for StoreFrontManager-portlet 01:13:12,440 ERROR [HotDeployUtil:205]
 20com.liferay.portal.kernel.deploy.hot.HotDeployException: Error unregistering plugins for StoreFrontManager-portlet
 21com.liferay.portal.kernel.deploy.hot.HotDeployException: Error unregistering plugins for StoreFrontManager-portlet
 22     at
 23com.liferay.portal.kernel.deploy.hot.BaseHotDeployListener.throwHotDeployException(BaseHotDeployListener.java:46)
 24     at
 25com.liferay.portal.deploy.hot.PluginPackageHotDeployListener.invokeUndeploy(PluginPackageHotDeployListener.java:63)
 26     at
 27com.liferay.portal.kernel.deploy.hot.HotDeployUtil._fireUndeployEvent(HotDeployUtil.java:202)
 28     at
 29com.liferay.portal.kernel.deploy.hot.HotDeployUtil.fireUndeployEvent(HotDeployUtil.java:44)
 30     at
 31com.liferay.portal.kernel.servlet.PortletContextListener.doPortalDestroy(PortletContextListener.java:60)
 32     at
 33com.liferay.portal.kernel.util.BasePortalLifecycle.portalDestroy(BasePortalLifecycle.java:30)
 34     at
 35com.liferay.portal.kernel.servlet.PortletContextListener.contextDestroyed(PortletContextListener.java:45)
 36     at
 37org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:3949)
 38     at
 39org.apache.catalina.core.StandardContext.stop(StandardContext.java:4615)
 40     at
 41org.apache.catalina.core.ContainerBase.destroy(ContainerBase.java:1175)
 42     at
 43org.apache.catalina.core.StandardContext.destroy(StandardContext.java:4705)
 44     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 45     at
 46sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 47     at
 48sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 49     at java.lang.reflect.Method.invoke(Method.java:597)
 50     at
 51org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297)
 52     at
 53org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
 54     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
 55     at
 56org.jboss.web.tomcat.service.deployers.TomcatDeployment.performUndeployInternal(TomcatDeployment.java:596)
 57     at
 58org.jboss.web.tomcat.service.deployers.TomcatDeployment.performUndeploy(TomcatDeployment.java:570)
 59     at
 60org.jboss.web.deployers.AbstractWarDeployment.stop(AbstractWarDeployment.java:480)
 61     at org.jboss.web.deployers.WebModule.stopModule(WebModule.java:133)
 62     at org.jboss.web.deployers.WebModule.stop(WebModule.java:102)
 63     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 64     at
 65sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 66     at
 67sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 68     at java.lang.reflect.Method.invoke(Method.java:597)
 69     at
 70org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
 71     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
 72     at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
 73     at
 74org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
 75     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
 76     at
 77org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206)
 78     at $Proxy38.stop(Unknown Source)
 79     at
 80org.jboss.system.microcontainer.StartStopLifecycleAction.uninstallAction(StartStopLifecycleAction.java:56)
 81     at
 82org.jboss.system.microcontainer.StartStopLifecycleAction.uninstallAction(StartStopLifecycleAction.java:37)
 83     at
 84org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleUninstallAction(SimpleControllerContextAction.java:79)
 85     at
 86org.jboss.dependency.plugins.action.AccessControllerContextAction.uninstall(AccessControllerContextAction.java:131)
 87     at
 88org.jboss.dependency.plugins.AbstractControllerContextActions.uninstall(AbstractControllerContextActions.java:58)
 89     at
 90org.jboss.dependency.plugins.AbstractControllerContext.uninstall(AbstractControllerContext.java:354)
 91     at
 92org.jboss.dependency.plugins.AbstractController.uninstall(AbstractController.java:1664)
 93     at
 94org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:1275)
 95     at
 96org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:827)
 97     at
 98org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
 99     at
100org.jboss.system.ServiceController.doChange(ServiceController.java:688)
101     at org.jboss.system.ServiceController.stop(ServiceController.java:510)
102     at
103org.jboss.system.deployers.ServiceDeployer.stop(ServiceDeployer.java:170)
104     at
105org.jboss.system.deployers.ServiceDeployer.undeploy(ServiceDeployer.java:150)
106     at
107org.jboss.system.deployers.ServiceDeployer.undeploy(ServiceDeployer.java:46)
108     at
109org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalUndeploy(AbstractSimpleRealDeployer.java:69)
110     at
111org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.undeploy(AbstractRealDeployer.java:112)
112     at
113org.jboss.deployers.plugins.deployers.DeployerWrapper.undeploy(DeployerWrapper.java:196)
114     at
115org.jboss.deployers.plugins.deployers.DeployersImpl.doUndeploy(DeployersImpl.java:1469)
116     at
117org.jboss.deployers.plugins.deployers.DeployersImpl.doUninstallParentLast(DeployersImpl.java:1376)
118     at
119org.jboss.deployers.plugins.deployers.DeployersImpl.doUninstallParentLast(DeployersImpl.java:1369)
120     at
121org.jboss.deployers.plugins.deployers.DeployersImpl.uninstall(DeployersImpl.java:1331)
122     at
123org.jboss.dependency.plugins.AbstractControllerContext.uninstall(AbstractControllerContext.java:354)
124     at
125org.jboss.dependency.plugins.AbstractController.uninstall(AbstractController.java:1664)
126     at
127org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:1275)
128     at
129org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:827)
130     at
131org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
132     at
133org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:694)
134     at
135org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679)
136     at
137org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
138     at
139org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:362)
140     at
141org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
142     at
143java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
144     at
145java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
146     at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
147     at
148java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
149     at
150java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
151     at
152java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
153     at
154java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
155     at
156java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
157     at java.lang.Thread.run(Thread.java:662)
158Caused by: com.liferay.portal.kernel.exception.SystemException:
159org.hibernate.cache.CacheException: java.lang.IllegalStateException: The com.hungama.gdp.webservice.model.impl.OfferPlanImpl Cache is not alive.
160     at
161com.liferay.portal.service.impl.ServiceComponentLocalServiceImpl.destroyServiceComponent(ServiceComponentLocalServiceImpl.java:65)
162     at sun.reflect.GeneratedMethodAccessor4947.invoke(Unknown Source)
163     at
164sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
165     at java.lang.reflect.Method.invoke(Method.java:597)
166     at
167com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:115)
168     at
169com.liferay.portal.spring.transaction.TransactionInterceptor.invoke(TransactionInterceptor.java:86)
170     at
171com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:60)
172     at
173com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:60)
174     at
175com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:60)
176     at
177com.liferay.portal.spring.aop.ServiceBeanAopProxy.invoke(ServiceBeanAopProxy.java:93)
178     at $Proxy481.destroyServiceComponent(Unknown Source)
179     at
180com.liferay.portal.service.ServiceComponentLocalServiceUtil.destroyServiceComponent(ServiceComponentLocalServiceUtil.java:262)
181     at
182com.liferay.portal.deploy.hot.PluginPackageHotDeployListener.destroyServiceComponent(PluginPackageHotDeployListener.java:72)
183     at
184com.liferay.portal.deploy.hot.PluginPackageHotDeployListener.doInvokeUndeploy(PluginPackageHotDeployListener.java:146)
185     at
186com.liferay.portal.deploy.hot.PluginPackageHotDeployListener.invokeUndeploy(PluginPackageHotDeployListener.java:60)
187     ... 73 more
188Caused by: org.hibernate.cache.CacheException:
189java.lang.IllegalStateException: The
190com.hungama.gdp.webservice.model.impl.OfferPlanImpl Cache is not alive.
191     at net.sf.ehcache.hibernate.EhCache.clear(EhCache.java:178)
192     at
193com.liferay.portal.dao.orm.hibernate.CacheWrapper.invalidate(CacheWrapper.java:130)
194     at
195com.liferay.portal.cache.CacheRegistryImpl.clear(CacheRegistryImpl.java:41)
196     at
197com.liferay.portal.kernel.cache.CacheRegistryUtil.clear(CacheRegistryUtil.java:23)
198     at
199com.liferay.portal.service.impl.ServiceComponentLocalServiceImpl.clearCacheRegistry(ServiceComponentLocalServiceImpl.java:274)
200     at
201com.liferay.portal.service.impl.ServiceComponentLocalServiceImpl.destroyServiceComponent(ServiceComponentLocalServiceImpl.java:62)
202     ... 87 more
203Caused by: java.lang.IllegalStateException: The com.hungama.gdp.webservice.model.impl.OfferPlanImpl Cache is not alive.
204     at net.sf.ehcache.Cache.checkStatus(Cache.java:2191)
205     at net.sf.ehcache.Cache.removeAll(Cache.java:1978)
206     at net.sf.ehcache.Cache.removeAll(Cache.java:1964)
207     at net.sf.ehcache.hibernate.EhCache.clear(EhCache.java:176)
208     ... 92 more
20901:13:12,441 INFO  [PortletHotDeployListener:445] Unregistering portlets for StoreFrontManager-portlet
21001:13:12,442 INFO  [PortletHotDeployListener:477] 1 portlet for StoreFrontManager-portlet was unregistered
21101:13:12,444 INFO  [[/StoreFrontManager-portlet]] Closing Spring root WebApplicationContext 01:13:13,400 INFO  [TomcatDeployment] deploy, ctxPath=/StoreFrontManager-portlet
21201:13:13,535 INFO  [[/StoreFrontManager-portlet]] Initializing Spring root WebApplicationContext Loading vfsfile:/home/jboss/liferay-portal-6.0-ee-sp2/jboss-5.1.0/server/default/deploy/StoreFrontManager-portlet.war/WEB-INF/classes/service.properties
213Loading
214vfsfile:/home/jboss/liferay-portal-6.0-ee-sp2/jboss-5.1.0/server/default/deploy/StoreFrontManager-portlet.war/WEB-INF/classes/service.properties
21501:13:18,218 INFO  [PluginPackageUtil:1077] Reading plugin package for StoreFrontManager-portlet Loading vfsfile:/home/jboss/liferay-portal-6.0-ee-sp2/jboss-5.1.0/server/default/deploy/StoreFrontManager-portlet.war/WEB-INF/classes/service.properties
216Loading
217vfsfile:/home/jboss/liferay-portal-6.0-ee-sp2/jboss-5.1.0/server/default/deploy/StoreFrontManager-portlet.war/WEB-INF/classes/portlet.properties
218Loading
219vfsfile:/home/jboss/liferay-portal-6.0-ee-sp2/jboss-5.1.0/server/default/deploy/StoreFrontManager-portlet.war/WEB-INF/classes/portlet.properties
22001:13:18,575 INFO  [PortletHotDeployListener:251] Registering portlets for StoreFrontManager-portlet Loading vfsfile:/home/jboss/liferay-portal-6.0-ee-sp2/jboss-5.1.0/server/default/deploy/StoreFrontManager-portlet.war/WEB-INF/classes/portlet.properties
22101:13:18,621 INFO  [PortletHotDeployListener:410] 1 portlet for StoreFrontManager-portlet is available for use


OfferPlan Entity which causes the issue is not part of StoreFrontManager-portlet which is deployed.

Has anyone faced the same issue, any pointers for the same would be helpful.

Thanks and Regards,
Hitesh Methani.
Hitesh Methani
RE: Regarding cache not alive issue
6 mars 2012 22:02
Réponse

Hitesh Methani

Rang: Regular Member

Publications: 163

Date d'inscription: 24 juin 2010

Publications Récentes

Got relieved,
This error occurs due to different service.xml using same entity name with change in model column name.

Regards,
Hitesh Methani.
David García González
RE: Regarding cache not alive issue
8 mai 2012 08:01
Réponse

David García González

Rang: Regular Member

Publications: 127

Date d'inscription: 14 juillet 2009

Publications Récentes

Hitesh Methani:

Issue gets resolved when I restart the server. I have defined expirtation-cache to be 0 in all the portlets.
Hitesh Methani.

Hi, I am experiencing the same issue. How you define the expiration-cache to 0 in the portlet?

Thanks.
Hitesh Methani
RE: Regarding cache not alive issue
8 mai 2012 22:36
Réponse

Hitesh Methani

Rang: Regular Member

Publications: 163

Date d'inscription: 24 juin 2010

Publications Récentes

Hi David,

Expiration cache is 0 by default for all the portlets in portlet.xml, I am not sure it is related to this issue or not, I was just providing the detailed info if it might be related.
The actual cause of the issue in my case was change in entity column names in service.xml of different portlets. Check if your entity is not defined in service.xml of two different portlets.

Thanks and Regards,
Hitesh Methani.
David García González
RE: Regarding cache not alive issue
9 mai 2012 04:00
Réponse

David García González

Rang: Regular Member

Publications: 127

Date d'inscription: 14 juillet 2009

Publications Récentes

Hitesh Methani:
Check if your entity is not defined in service.xml of two different portlets.

Hitesh Methani.


Hi. This entity is only placed in one service.xml, but there is 2 different things to take in account:

1.- In one portlet I have 2 service.xml.
2.- The jar xxx-portlet-service.jar is placed in another war and in the global lib directory because I have to use its methods from one hook plugin.

Could this error be happening due to one of these things??

Thank you very much!
Hitesh Methani
RE: Regarding cache not alive issue
9 mai 2012 04:21
Réponse

Hitesh Methani

Rang: Regular Member

Publications: 163

Date d'inscription: 24 juin 2010

Publications Récentes

Hello David,


2.- The jar xxx-portlet-service.jar is placed in another war and in the global lib directory because I have to use its methods from one hook plugin.

Point number 2 you mentioned seems to be creating the problem causing duplication, xxx-portlet-service.jar if placed in global lib, it should be removed from libs of any other wars.

Thanks and Regards,
Hitesh Methani
David García González
RE: Regarding cache not alive issue
9 mai 2012 04:30
Réponse

David García González

Rang: Regular Member

Publications: 127

Date d'inscription: 14 juillet 2009

Publications Récentes

Thanks!!!

The thing is that I wanted to remove the xxx-service.jar from the global lib, but I need it to call the services from the jsp /journal_content/view.jsp that is placed within a hook.

Example:
1List<Socialmedia> list = SocialmediaLocalServiceUtil.findByCompanyId(themeDisplay.getCompanyId());


Is it possible to call these services from a hook and having the services jar only inside the portlet war?
Hitesh Methani
RE: Regarding cache not alive issue
9 mai 2012 04:35
Réponse

Hitesh Methani

Rang: Regular Member

Publications: 163

Date d'inscription: 24 juin 2010

Publications Récentes

Hi David,

In your case I would suggest you to bundle hook and porltet in a single war, which would remove the dependency problem,
You can refer the link hook an d portlet in single war.

Best Regards,
Hitesh
Hitoshi Ozawa
RE: Regarding cache not alive issue
9 mai 2012 04:42
Réponse

Hitoshi Ozawa

Rang: Liferay Legend

Publications: 7990

Date d'inscription: 23 mars 2010

Publications Récentes

Is it possible to call these services from a hook and having the services jar only inside the portlet war?


You only need service jar in lib\ext and not in your portlet.

That said, I agree with Hitesh. It would be easier if you just bundle everything into one war.
Akram MONCER
RE: Regarding cache not alive issue
11 janvier 2013 02:34
Réponse

Akram MONCER

Rang: Regular Member

Publications: 106

Date d'inscription: 25 septembre 2012

Publications Récentes

hi
i try the solution about packaging the hook and the portlet in the same war, the problem is if the jar generated by the service builder is in the portlet lib folder, the jsp pages from the hook can't see it because they will be deployed on other portlet, and when i remove the jar from the portlet lib and put it in the /lib/ext under tomcat folder i get cache not alive
Michael Lustenberger
RE: Regarding cache not alive issue
4 mars 2013 10:12
Réponse

Michael Lustenberger

Rang: New Member

Publications: 1

Date d'inscription: 2 octobre 2012

Publications Récentes

Hello Akram,

maybe it is not the right answer for you, but in our case I found a
quite easy solution for this error, and I hope it might possibly
help at least someone out there.

Our summarized setup:
We got some portlets (name them: 'bar'..s) all depending on one
portlet ('foo') created with service-builder. I did not want to
manually copy jars to the container or the like, so the 'foo.jar'
is put inside every 'bar.war' and the runtime context is set as
'required-deployment-contexts=foo' in liferay-plugin-package.properties..

The problem:
Now any time I redeployed the (dependent) 'bar' portlet, I got the
before mentioned Error. After a container restart, everything was
fine again (though not an option on producive systems).

An explanation (please correct me, if wrong..):
After some forum visits and playing around, I now think to understand
(or guess), this is due to the Singleton hibernate cache to be
undeployed on redeploy of 'bar'.

A solution:
So I just tried the obvious (maybe too obvious for the involved and
that is why it was not mentioned here before..): As soon as I redeploy
'foo' everything is back to normal again. So basically after each change
in 'bar' we redeploy first 'bar', than 'foo'.

Alternative (?):
Tell bar to leave cache alone??

Yours,
mic
Navaraj Neupane
Regarding cache not alive issue(liferay-portal-tomcat 6.1.1)
14 avril 2013 21:58
Réponse

Navaraj Neupane

Rang: New Member

Publications: 2

Date d'inscription: 14 avril 2013

Publications Récentes

I had replica of this error while using tomcat too. Basically error was occurred when I was using portlet with services. If I redeployed portlet and try to use it without restarting server, this error occurred. Currently I made a small change in portlet.xml and it worked fine for me.

I just replaced
1<expiration-cache>0</expiration-cache>
in portlet.xml with
1<expiration-cache>-1</expiration-cache>
. Here value '-1' represents 'cache will never expire'.

I hope this will help with tomcat.

Regards,
Navaraj Neupane
Navaraj Neupane
RE: Regarding cache not alive issue(liferay-portal-tomcat 6.1.1)
26 avril 2013 04:44
Réponse

Navaraj Neupane

Rang: New Member

Publications: 2

Date d'inscription: 14 avril 2013

Publications Récentes

One more way to resolve this issue(plz be noted it will make the system slow).

Add:
1hibernate.cache.use_query_cache=false
2hibernate.cache.use_second_level_cache=false

inside portal-ext.properties inside your liferay bundle.
Jack Bakker
RE: Regarding cache not alive issue(liferay-portal-tomcat 6.1.1)
20 septembre 2013 12:18
Réponse

Jack Bakker

Rang: Liferay Master

Publications: 515

Date d'inscription: 3 janvier 2010

Publications Récentes

Not sure if it helps, but I saw a similar issue after changing package naming from ca.clientname.server.service to ca.clientname.server.services

where to fix I had to

- delete /docroot/WEB-INF/service
- delete /docroot/WEB-INF/classes
- update /docroot/js/services.js
- clean
- rebuild services
- check dependent portlets includes