facing exception while deploying liferay on weblogic - weblogic

I've deployed liferay 5.2 sp2 on weblogic 10.3 and in deployment part the status of application is Active.
Now when i pass the URL in browser "nakulpatel:7001" it display "500--Internal Server Error".
java.lang.NoClassDefFoundError: com/yahoo/platform/yui/compressor/JavaScriptCompressor
at com.liferay.portal.util.MinifierUtil._minifyJavaScript(MinifierUtil.java:80)
at com.liferay.portal.util.MinifierUtil.minifyJavaScript(MinifierUtil.java:52)
at com.liferay.portal.servlet.filters.strip.StripFilter.strip(StripFilter.java:251)
at com.liferay.portal.servlet.filters.strip.StripFilter.processFilter(StripFilter.java:159)
at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:91)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:154)...
Please guide me how to fix this problem.
I've not used maven at all.Simply deployed .war file of liferay 5.2 and not able to start portal.

The reason you got it is because Liferay uses YUI compressor to do Javascript/CSS minification. Minification can be done in two ways -- runtime vs build time. It looks like liferay implements the former through servlet filter.
I checked my Liferay 6.0.x installation. There is a liferay-yuicompressor.jar under the \liferay-portal-6.0.6\tomcat-6.0.29\webapps\ROOT\WEB-INF. Lfieray 5.2 should have a similar directory structure. Make sure this jar file is included in your WEB-INF/lib when deploying to WebLogic 10.3

Related

Can we deploy a directory application on WebLogic?

We have an old application running on a WebLogic 8.1.5.0.
In this version, we can see that the application has been configured as a directory (which has classes, css, images, htmls), but No WAR, JAR or EAR found for this app.
PFB the extract from config.xml
Application Name="abc" Path="/wls_domains/flret/admin/applications" StagingMode="nostage" TwoPhase="true">
<WebAppComponent Name="abc" Targets="admin" URI="abc"/>
Now, we need to migrate this application to WebLogic 10.3.6.0.
New Weblogic is not allowing us to deploy an application other than WAR, EAR or JAR.
Also, config.xml structure is completely different for new weblogic.
<name>XYZ</name>
<target>XYZ_cluster</target>
<module-type>war</module-type>
<source-path>servers/admin/upload/XYZ.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
Is it something related to weblogic versions and feature available to deploy a directory?
Can someone plz suggest can I complete this deployment or any other way to do this.
Thanks in advance.
Looks like you have an 'Exploded Archive' app, which modern versions of weblogic do not support. You need to upgrade to a modern format, or put it directly on the filesystem of the app server.
(see: How can I deploy an exploded web app through WebLogic 11g administrative console?)

Undeploy a failed Mule app

We have a Live mule server (Community edition ) 3.3.0 running on a Windows 2008 server.
We have several apps running on it.
We tried to hotdeploy a new app in it. It failed saying some port was already in use/bind - this was a JMX port. However we were unable to undeploy it. It didn't create any anchor file as it had failed deployment so we couldn't do the clean undeploy. When we tried to delete the exploded folder it didn't allow as it said the jars in the lib were in use.
We tried to re-deploy the same file with fix again but it had no effect.
Question is irrespective of what caused out application to fail - how can one undeploy or take out a Mule app (failed) completely? It doesn't have anchor file and trying to delete says jar in use. Only way we could do was to stop mule and then delete the folder and restart Mule - totally unacceptable in production environment.
Any clues?
This is a known bug on 3.3.0 that was fixed on 3.3.1.

Can we deploy web application as a folder instead of war file in JBoss AS 7

I am having two queries
1. Can I deploy web application as a folder instead of war file in JBoss AS 7?
2. If not ,how to update the JSP or html or js files with out building/deploying the war file again?
JBoss supports the ability to deploy an archive file or as an exploded directory. To explode a Java EE archive, unzip the archive to a directory that is named the same as the archive file. As long as the directory name has the correct extension (.war, .ear, etc.) JBoss will deploy the directory normally. So if your war file has name HelloWorld.war, your exploded directory name should be HelloWorld.war too.
Please also note that it is recommended to edit your deployment-scanner in the standalone.xml configuration file and changing auto-deploy-exploded property back to false for exploded deployment. Quote from JBoss 7.1 Documentation:
Manual deploy mode is strongly recommended for exploded content, as
exploded content is inherently vulnerable to the scanner trying to
auto-deploy partially copied content.
Edit:
Please see link https://community.jboss.org/thread/200114. Looks like this is a confirmed bug in JBoss 7.1.1 that JBoss ignores the configuration in jsp-configuration and does not reload modified jsp. It is fixed in 7.1.2. You need to build 7.1.2 nightly build yourself. Or talk to JBoss Support if you have Enterprise support.

Glassfish 3.1.2 and Eclipse

I just downloaded the Glassfish version 3.1.2, this is not yet an official release.
I need this version because my web application is using websockets.
The problem I have now is with the Glassfish plugin for eclipse, he is not recognizing the new Glassfish Version.
With the Glassfish Version 3.1.1 in Eclipse everything works fine.
I am using Oracle Glassfish Server Tools (Eclipse plugin ) version 2.0.0.20111104904 from Oracle(last version I could download).
If I try to add a new Server Runtime Environment in Eclipse for the Glassfish 3.1.2 I get the error:
There is no valid GlassFish installation in the specified directory...
I need everything to be able to debug my web application in Eclipse.
Anyone know what the plugin is checking ?
There is any change to trick the plugin so will run with Glashfish 3.1.2 too ?
Use the plugin from here (for Indigo): http://dlc.sun.com.edgesuite.net/glassfish/eclipse/indigo/
The plugin for Helios does not support 3.1.2.
If you have to live with the bits the are blessed by Oracle or keep using Helios, then you can try the following trick:
create a couple files....
${glassfish.rootdirectory}/modules/jsf-impl.jar and
${glassfish.rootdirectory}/modules/jstl-impl.jar
These files were renamed between 3.1.1 and 3.1.2...
You may be able to get the 3.1.2 to mascarade as 3.1.1 by just
creating empty files with the above names. If that doesn't do it,
make copies of the following files should do it.
The new name for jstl-impl.jar is
gf312/glassfish/modules/javax.servlet.jsp.jstl.jar
The new name for jsf-impl.jar is
gf312/glassfish/modules/javax.faces.jar.
If you are on Helios, you can try the following:
uninstall the Glassfish 3.1.1 plugin (and all associated runtimes and servers).
go to "Install new software" and type in (for the URL): http://download.java.net/glassfish/eclipse/indigo
Though the plugin says indigo, it is also working for me in Helios. And it gives options for both Glassfish 3.1.1 and 3.1.2 servers (pre and post name changes).
Note that it downloads Glassfish itself, and installs an internal server. You can delete that one, and install your own server ("New server...") if you have an existing server you want to work with (as I did).
HTH.

Manually edit Glassfish Server Path settings

I added several JARs to my GlassFish server path and now the GlassFish Admin Console won't come up. It says "HTTP Status 404 - Servlet FacesServlet is not available". I think something I added is causing a JAR conflict with the admin tool. I would like to remove the stuff I added to the path, but I can't use the GlassFish admin tool to do it.
Can someone tell me how to manually edit the GlassFish server path values? Are they stored in a XML file somewhere? I looked around a little and couldn't find them.
I found the problem JAR (xercesImpl.jar). If I simply rename that JAR, then the GlassFish Admin Console comes up with no problem. Apparently GlassFish uses a different version and there was a conflict.