I installed weblogic Server 10.3.Created a new domain.Downloaded liferay dependencies and additional war files.i copied the dependencies into lib folder and war into deploy folder and started server.But i am getting an error.
<Mar 7, 2014 2:35:20 PM IST> <Warning> <HTTP> <BEA-101342> <_appsdir_liferay-por
tal-6.1.1-ce-ga2-20120731132656558_war: Error(s) encountered while pre-compiling
jsp jspURI
configuration.jsp:17:18: Error in "init.jsp" at line 249: The code of method _j
spService(HttpServletRequest, HttpServletResponse) is exceeding the 65535 bytes
limit
<%# include file="/html/portlet/asset_publisher/init.jsp" %>
^--------------------------------------^
You seem to be running into LPS-27841. AFAIK a fix is available in EE, or you can search for the relevant commit(s) on github and apply them to your environment.
Note that Weblogic 10 is neither in the "certified" nor in the "supported" list of application servers for 6.2 (EE). E.g. it's untested and you might run into other issues. Weblogic 12 is "certified", 11 is "supported"
Related
We are trying to deploy our application's .war file in Weblogic 12.1.3 but we get the following error messages:
Task 156 initiated: [Deployer:149026]deploy application sarp on sarp.
Task 156 failed: [Deployer:149026]deploy application sarp on sarp.
Target state: deploy failed on Server sarp
java.lang.IllegalArgumentException
java.lang.IllegalArgumentException
at com.bea.objectweb.asm.ClassReader.<init>(Unknown Source)
at com.bea.objectweb.asm.ClassReader.<init>(Unknown Source)
at weblogic.application.utils.annotation.ClassInfoImpl.<init>(ClassInfoImpl.java:41)
at weblogic.application.utils.annotation.ClassfinderClassInfos.polulateOneClassInfo(ClassfinderClassInfos.java:240)
at weblogic.application.utils.annotation.ClassfinderClassInfos.populateClassInfos(ClassfinderClassInfos.java:193)
at weblogic.application.utils.annotation.ClassfinderClassInfos.<init>(ClassfinderClassInfos.java:44)
at weblogic.servlet.internal.War.initializeClassInfosIfNecessary(War.java:446)
at weblogic.servlet.internal.War.getAnnotatedClasses(War.java:376)
at weblogic.servlet.internal.WebBaseModuleExtensionContext.getAnnotatedClasses(WebBaseModuleExtensionContext.java:63)
at weblogic.j2ee.managedbean.ManagedBeanModuleExtensionFactory.create(ManagedBeanModuleExtensionFactory.java:65)
at weblogic.application.internal.ExtensibleModuleWrapper.createModuleExtensions(ExtensibleModuleWrapper.java:264)
at weblogic.application.internal.ExtensibleModuleWrapper.initDrivenObjectArray(ExtensibleModuleWrapper.java:232)
at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:107)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:100)
at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:175)
at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:170)
at weblogic.application.utils.StateMachineDriver$ParallelChange.run(StateMachineDriver.java:80)
at weblogic.work.ContextWrap.run(ContextWrap.java:40)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:548)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)
Why are we getting this error? Any Suggestions?
Regards.
This error is because the version of JDK from your WLS is lower than bytecode is being deployed in your war file.
please check JDK of your WebLogic and your war file.
Weblogic 12.1.3 can use 7 or 8.
EDIT1: log4j2 is an example that has bundled bytecode of Java9 that, when is deployed in WebLogic 12.1.3 an exception is thrown (com.bea.objectweb.asm.ClassReader.<init>). The newest version (without modification) that can be deployed directly in WLS 12.1.3 is log4j 2.8.2.
I have a strange behaviour on Webshphere 8.5.5.13 on Linux.
I have extended a large Enterprise application (IBM Maximo Enterprise Asset Management 7.6.0.9) and added some classes and a JSP file.
These changes work fine on Webshere on Windows (and Weblogic) for months for a lot of customers.
Now we have a customer who has deployed this Enterprise Application on Linux and here are unexpected problems.
When accessing my simple JSP on Linux I get the following error message in the SystemOut.log of the application server:
[8/28/18 16:16:06:336 CEST] 00000633 FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /opt/IBM/WebSphere/AppServer/profiles/ctgAppSrv01/logs/ffdc/MXServer_79a40fc5_18.08.28_16.16.06.3072776788115294465046.txt com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.translateJsp 259
[8/28/18 16:16:06:337 CEST] 00000633 webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[/webclient/common/eamdmtrequesthandler.jsp]: com.ibm.ws.jsp.JspCoreException: JSPG0049E: /webclient/common/eamdmtrequesthandler.jsp failed to compile :
JSPG0091E: An error occurred at line: 3 in the file: /webclient/common/eamdmtrequesthandler.jsp
JSPG0093E: Generated servlet error from file: /webclient/common/eamdmtrequesthandler.jsp
/opt/IBM/WebSphere/AppServer/profiles/ctgAppSrv01/temp/ctgNode01/MXServer/MAXIMO/maximouiweb.war/webclient/common/_eamdmtrequesthandler.java : 7 : The import de cannot be resolved
JSPG0091E: An error occurred at line: 8 in the file: /webclient/common/eamdmtrequesthandler.jsp
JSPG0093E: Generated servlet error from file: /webclient/common/eamdmtrequesthandler.jsp
/opt/IBM/WebSphere/AppServer/profiles/ctgAppSrv01/temp/ctgNode01/MXServer/MAXIMO/maximouiweb.war/webclient/common/_eamdmtrequesthandler.java : 87 : ExportXLS cannot be resolved to a type
JSPG0091E: An error occurred at line: 8 in the file: /webclient/common/eamdmtrequesthandler.jsp
JSPG0093E: Generated servlet error from file: /webclient/common/eamdmtrequesthandler.jsp
/opt/IBM/WebSphere/AppServer/profiles/ctgAppSrv01/temp/ctgNode01/MXServer/MAXIMO/maximouiweb.war/webclient/common/_eamdmtrequesthandler.java : 87 : ExportXLS cannot be resolved to a type
at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.translateJsp(AbstractJSPExtensionServletWrapper.java:616)
at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper._checkForTranslation(AbstractJSPExtensionServletWrapper.java:477)
at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.checkForTranslation(AbstractJSPExtensionServletWrapper.java:298)
at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.handleRequest(AbstractJSPExtensionServletWrapper.java:167)
Facts:
All required classes are available in their correct folder. I have checked the EAR file and the installedApps folder in Websphere.
All files are readable and accessible. No permission issues. Websphere is running as root, SELinux is disabled
The same EAR file, which has this error on Linux, does not have this problem if deployed under Windows.
I get the same error message when I try to compile the JSP with the JspBatchCompiler.sh command from the commandline.
I have moved my classes from de.eam.webclient.servlet to psdi.webclient.servlet (an already existing package which is part of Maximo) and then the JSP works as expected.
I have checked the log file MXServer_79a40fc5_18.08.28_16.16.06.3072776788115294465046.txt and I have also verified, that the classpath contains my classes in my folder.
What can be the reason for Websphere not finding my top level package directory "de" and not finding the classes even if they are in the classpath and are found on Windows.
What can I do to track this down? Is this a bug in Websphere on Linux?
The JSP File:
<%# page language="java"
%><%# page contentType="text/html; charset=utf-8"
%><%# page import="de.eam.webclient.servlet.ExportXLS"
%><%
request.setCharacterEncoding("UTF-8");
response.setCharacterEncoding("UTF-8");
ExportXLS servlet = new ExportXLS();
servlet.handleRequest(request, response);
%>
I am not able to start application it gives below exception :
Java.lang.IllegalArgumentException
At com.bea.objectweb.asm.ClassReader.(Unknownsource)com.bea.objectweb.asm.ClassReader.(Unknown source)
Application got started after replacing below jars
Log4j-1.2-api-2.9.1.jar
Log4j-api-2.9.1.jar
Log4j-core-2.9.1.jar
Log4j-slf4j-impl-2.10.0.jar
With
Log4j-1.2-api-2.8.2.jar
Log4j-api-2.8.2jar
Log4j-core-2.8.2.jar
Log4j-slf4j-impl-2.8.2.jar
Since version 2.9.0 there are classes compiled in java 9.
One workaround is to remove them from log4j-api-2.x.y.jar
I'm using Tapestry 5.3 framework in my Java 1.7 web-app, and run in under Tomcat 7.x.
Suddenly today I've found in startup logs of my app these lines:
jul 31, 2014 12:12:46 PM com.sun.faces.config.ConfigureListener contextInitialized
INFO: Initializing Mojarra 2.2.7 ( 20140610-1547 https://svn.java.net/svn/mojarra~svn/tags/2.2.7#13362) for context '/XXX'
jul 31, 2014 12:12:46 PM com.sun.faces.spi.InjectionProviderFactory createInstance
INFO: JSF1048: PostConstruct/PreDestroy annotations present. ManagedBeans methods marked with these annotations will have said annotations processed.
I have never seen these log-lines before in my app. Furthermore, "Initializing Mojarra" process takes some appreciable time.
So I should think, that somebody among our project developers have added special libraries - but there aren't any JSF or Faces libraries in the build.
I have no ideas what have changed and how I can cut out Mojarra from my project? Any help would be appreciated.
The problem was in jsf-*.jar libraries placed mistakenly in /lib folder of Tomcat. They were initialized due to tomcat startup. Removing them solved the problem.
I am trying to run Titan with embedded cassandra and rexster. Downloaded Titan distribution titan-all-0.3.2 and unpacked on a linux box. After unpacking this is what i ran the command
$ ./bin/titan.sh config/titan-server-rexster.xml config/titan-server-cassandra.properties
This is what i see in the logs
After starting RexPro services its unable to deploy and start grizzly. Has anyone had this issue?
Exception stack trace:
13/10/18 14:51:31 INFO server.RexProRexsterServer: RexPro serving on port: [8184]
Oct 18, 2013 2:51:31 PM org.glassfish.grizzly.servlet.WebappContext deploy
INFO: Starting application [jersey] ...
Oct 18, 2013 2:51:31 PM org.glassfish.grizzly.servlet.WebappContext deploy
SEVERE: [jersey] Exception deploying application. See stack trace for details.
java.lang.RuntimeException: com.sun.jersey.api.container.ContainerException: No WebApplication provider is present
at org.glassfish.grizzly.servlet.WebappContext.initServlets(WebappContext.java:1479)
at org.glassfish.grizzly.servlet.WebappContext.deploy(WebappContext.java:265)
There were some packaging problems in some of the 0.3.2 zip files. You basically need to replace a jar file or two around Jersey to get it to work (or I think use the titan-cassandra distribution instead of titan-all).
You can read more about the issue here and its solution (also reported here), but the answer is:
You should be able to patch 0.3.2 by replacing this jar file in the
Titan lib directory:
jersey-core-1.8.jar
with:
jersey-core-1.17
(http://repo1.maven.org/maven2/com/sun/jersey/jersey-core/1.17/jersey-core-1.17.jar)