Im struggling a long time now with the following problem: I generate a very basic (or complex) example portlet with xmlportletfactory. Deploy it to Liferay, add it on a page and try to use it. I can not add a new entry (error message in view) and the server log sais:
ERROR [http-bio-8080-exec-1][PortletBeanLocatorUtil:42] BeanLocator is null for servlet context coursesExample
Environment is:
liferay-portal-6.1.2-ce-ga3
liferay-plugins-sdk-6.1.1
XMLPortletFactory_6.x-v2.2
Tomcat/7.0.40
Postgres 9.2
Java 1.6.0_45
I searched the whole web and find a lot of similiar problems on the liferay forums, but nothing helped me. I posted it also to xmlportletfactory forums http://www.xmlportletfactory.org/forum/-/message_boards/message/145826, but still no answer yet.
What can I do?
In my case, for some reason I changed the project's name, and I started having the same "BeanLocator is null for servlet context..." problem.
A couple of days later, I renamed my eclipse project to the same name I initially used, and everything went back to normal.
Could that be something related to your project's name as well?
Related
I'm revisiting an XPages application that was last touched a number of months ago. It was previously built and running fine. In Designer (9.0.1 FP9) I'm now seeing the following errors when the project is cleaned and built.
This application also uses the org.openntf.Utils class. When looking at Java code the following error, along with a couple of others is displayed (although not listed on the Problems tab)
I recently had to delete the workspace folder in the Notes Data directory, so not sure if I've lost config or preference changes that are required. Any pointers much appreciated.
It's likely to be the same root cause as this question, not picking up the right JVM folder Xpages can't load, Error 500; java.util cannot be resolved
I'm having a strange issue with my (i admit) very old liferay. Sometime yesterday morning my system broke down and doesn't start up again. I have no idea why it broke down.
Now when I restart my liferay again according to the logfile it starts fine. But when I try to acces the page via browser all I get is inifite loading. No log messages, no exceptions, no timeout, nothing. This all was Liferay 6.0.5 and JBoss 5.
I then downloaded a Liferay 6.0.6 bundle with Tomcat 6 and connected it to my oracle db. Same behavior. Next thing I did was not using an oracle connection so liferay used its built-in memory DB. And voila, startup worked immediatly. reconnecting to oracle results in failure again. I tried this liferay-tomcat bundle with all needed themes and portlets.
Then I undeployed all custom webapps and startet again and suddenly my log showed this message: No theme found for specified theme id <MY_CUSTOM_THEME>. Returning the default theme.
So the request must reach liferay somehow. Sadly the browser still doesn't show anything.
I'm short on ideas so I'm grateful for any help. Btw: I'm planning to relaunch with liferay 6.2 and an other db schema in couple of weeks, so a dirty workaround would totaly be enough for me.
Thinking out of the box: Is it possible to export all data from my database as sql inserts, etc and import them into liferays memory db? I know the memory db is not build for production use, but since it's only a couple of weeks I might give it a shot.
EDIT: I switched back to my jboss 5 and liferay 6.0 setting. I just noticed another strange thing. When I type a non-existent like liferays default community url (not configured in my particular portal instance) I see this message in my log Current URL /de/web/guest/home generates exception: null
. So apparently the illigal requests are recognized but legal requests are not served.
Thanks guys and regards. Sebastian
I am working with a brand new instance of IIS on Windows Server 2012 and I am having trouble getting my CFWheels app to work. The issue it seems to be with ISAPI filters and isapi_redirect.dll because it's trying to find the file in the wrong folder. I tried adding a filter myself which I named jakarta and pointed it to the correct folder of the dll but now I am not getting anything but a blank screen and no error of any sort (before I was getting an error 500)
Anyone with a recommendation of what I need to do!?
I recreated the site under C:\inetpub\wwwroot\ instead of having it on my second HDD and the issue went away.... I would love to know why though so if anyone ever comes across this question please feel free to post
I've just upgraded from Liferay CE to EE 6.2, and have successfully deployed the WAR on my weblogic 12c appserver. However, I am getting this error while trying to access my portal:
An unexpected system error occurred.
Unable to process template _SERVLET_CONTEXT_/html/themes/classic/templates/portal_normal.vm
I've read that this might be a cache issue, and I've deleted all temporary files and restarted my server but am still getting this error.
Any ideas as to why this occurs?
I've seen it before, but can't remember the exact circumstances. AFAIK it's been a temporary issue and I'm puzzled that restarting the server doesn't help..
However I've found LPS-12683, an issue that is marked as fixed, but maybe you find some circumstances in the description that haven't been fixed. Also this forum entry contains a nice hint to check
You need to import the init.ftl file from your parent theme and fix occurrences of:
stringUtil.equals(x, y)
in
x == y
I modified settings for a Community Site inside Liferay.
Trying to poke and play with Liferay's CMS.
Added this setting= Staging: Remote Live
And now I get this error:
javax.servlet.jsp.JspException:
org.apache.velocity.exception.MethodInvocationException: Invocation of
method 'runtime' in class com.liferay.taglib.util.VelocityTaglib threw
exception org.apache.jasper.JasperException:
javax.servlet.ServletException: javax.servlet.jsp.JspException:
ServletException in '/html/portlet/staging_bar/view.jsp':
com.liferay.portal.NoSuchLayoutSetBranchException: No LayoutSetBranch
exists with the key {groupId=13309, privateLayout=false, master=true}
at VM_liferay.vm[line 91, column 24]
Can anyone help with what can I change programmatically to be able to get into the app again? I cannot even get to localhost:8080, it gives me this error.
I'm still using the default HSQL database.
think it might be related to this: http://issues.liferay.com/browse/LPS-18606
It looks like the one we had some time ago.
Site crashed after modifying it's settings in Control Panel. After some investigation we've found up that a setting branchingPublic=true affected that.
First of all, find out which site (community) have You modified. For example it is "community1".
In database find the row of this site:
SELECT * FROM group_ WHERE friendlyurl like '%community1%'
And check there what settings it has in column: "typesettings". I recommend copy them to have a backup.
We have changed branchingPublic=true to branchingPublic=false. And restarted the Liferay Portal.
It helped to start running again.
Although Liferay Support didn't reproduce this, I believe it may help You or someone else.
If that doesn't help, try playing with other settings, maybe some other affects the crash. At last you can try remove them all. Just an idea for You!
Kind Regards!