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.
Related
I stop my server update when it was creating DDL statments and restart the server. Now my server is stuck at below line. I did ant clean all and again tried to start the server but still same issue.
How to resolve this?
log4j:WARN No such property [maxFileSize] in org.apache.log4j.DailyRollingFileAppender.
Feb 07, 2020 2:28:29 PM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://www.springframework.org/security/tags is already defined
log4j:WARN No appenders could be found for logger (de.hybris.platform.servicelayer.web.XSSFilter).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Feb 07, 2020 2:28:29 PM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Feb 07, 2020 2:28:30 PM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Run the following SQL request to check if the system is locked.
select process,locked from systeminit ;
if locked = 1, update it to 0.
I'm getting a ClassCastException when Liferay 7.1 starts:
INFO [main][ModuleFrameworkImpl:1636] Starting dynamic bundles
ERROR [Start Level: Equinox Container: 08ae8322-2575-4260-9c68-db4761a17500][org_apache_felix_scr:97] bundle org.apache.felix.scr:2.1.14 (34)Error while loading components of bundle com.liferay.portal.remote.soap.extender.impl:2.0.5 (555)
java.lang.ClassCastException: org.eclipse.osgi.internal.loader.FragmentLoader cannot be cast to org.eclipse.osgi.internal.loader.BundleLoader
Any help would be appreciated
Thanks
Seems this is a bug in equinox framework that is already fixed. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=423728 . You can try to update eclipse to version 3.10.0.
I'm using JSF2.1 Mojarra on Weblogic 12c with Servlet 3.0. jsf-api and jsf-impl are NOT in /WEB-INF/lib after build/deploy. I've tried checking for classpath pollution, but don't see anything. This is the error:
java.lang.IllegalStateException: Could not find backup for factory
javax.faces.context.FacesContextFactory.
at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:1010)
at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:342)
at javax.faces.webapp.FacesServlet.init(FacesServlet.java:302)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction
.run(StubSecurityHelper.java:337)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction
.run(StubSecurityHelper.java:288)
Truncated. see log file for complete stacktrace
Here's what I found in my classpath that relates to JSF:
com.oracle.adf.library:JSF:pom:12.1.2-0-0
com.sun.faces:jsf-api:jar:2.1.7-01
com.sun.faces:jsf-impl:jar:2.1.7-01
Here's everything in my classpath:
com.bea.core.antlr:runtime:jar:1.0.0.0_3-2
com.oracle.adf.library:Contexts-and-Dependency-Injection:pom:12.1.2-0-0
com.oracle.adf.library:Java-EE:pom:12.1.2-0-0
com.oracle.adf.library:JSF:pom:12.1.2-0-0
com.oracle.adf.library:JSP-Runtime:pom:12.1.2-0-0
com.oracle.adf.library:JSTL:pom:12.1.2-0-0
com.oracle.adf.library:TopLink:pom:12.1.2-0-0
com.oracle.adf:eclipselink:jar:12.1.2-0-0
com.sun.faces:jsf-api:jar:2.1.7-01
com.sun.faces:jsf-impl:jar:2.1.7-01
com.sun.mail:javax.mail:jar:1.4.4
glassfish:el:jar:1.1.0.0_2-2
glassfish:jstl:jar:1.2.2.0
javax.enterprise:deploy:jar:1.3
javax.enterprise:inject:jar:1.1
javax.management:j2ee:jar:1.1.0.0
javax.security:jacc:jar:1.1.0.0_1-1
javax.servlet:jstl:jar:1.2
javax.servlet:servlet-api:jar:2.5
javax.xml:registry:jar:1.1.0.0_1-0-4
javax.xml:rpc:jar:1.2.3
javax.xml:stream:jar:1.1.1.0
javax.xml:ws:jar:2.3.0
javax:ejb:jar:3.2.0
javax:inject:jar:1.1
javax:interceptor:jar:1.2
javax:jms:jar:1.1.3
javax:jsp:jar:3.0.0.0_2-2
javax:resource:jar:1.6.1
javax:servlet:jar:2.1.0.0_3-0
javax:transaction:jar:2.1.0.0_1-1
javax:validation:jar:1.1.0
junit:junit:jar:4.4:test
log4j:log4j:jar:1.2.16
org.eclipse.persistence:javax.persistence:jar:2.0.5-SNAPSHOT
org.eclipse.persistence:nosql:jar:2.4.2.v20130514-5956486
org.eclipse.persistence:org.eclipse.persistence.oracle.nosql:jar:2.4.2-SNAPSHOT
org.glassfish:javax.annotation:jar:3.0.1
I found the issue. In WEB-INF/faces-config.xml, I had a navigation-handler that was pointing to a class that didn't exist. Correcting this resolved the issue.
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"
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)