Liferay Error Occurred While Converting Date

English » 1. Installation / Deployment / Setup Recent Posts Statistics RSS (Opens New Window) Answer (Unmark) Mark as an Answer Threads [ Previous | Next ] Exceptions when starting Liferay-Tomcat! Phương Minh Nguyễn January 10, 2011 6:07 PM RE: Exceptions when starting Liferay-Tomcat! Jason Reast-Jones January 20, 2010 1:28 AM RE: Exceptions when starting Liferay-Tomcat! Phương Minh Nguyễn January 20, 2010 6:30 PM RE: Exceptions when starting Liferay-Tomcat! Jason Reast-Jones January 21, 2010 3:25 AM RE: Exceptions when starting Liferay-Tomcat! KC Koh June 3, 2010 10:52 PM RE: Exceptions when starting Liferay-Tomcat! NIRVAN V. JAIN January 5, 2011 3:18 AM Exceptions when starting Liferay-Tomcat! January 10, 2011 6:07 PM Answer Phương Minh Nguyễn Rank: New Member Posts: 21 Join Date: July 7, 2009 Recent Posts Hi everyone!I built my Liferay Portal from source code version 5.2.3. My Tomcat version is 6.0.20. I built my Liferay follow the instruction in the book "Liferay Portal 5.2 Systems Development" by Jonas X. Yuan. Everytime I start Liferay-Tomcat, I get the following exceptions in the Console Window of Eclipse:12SEVERE: Error starting static Resources3java.lang.IllegalArgumentException: Document base D:\Liferay-Portal-5.2.3\apache-tomcat-6.0.20\webapps\host-manager does not exist or is not a readable directory4 at org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.java:142)5 at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4048)6 at org.apache.catalina.core.StandardContext.start(StandardContext.java:4217)7 at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)8 at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)9 at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)10 at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:630)11 at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:556)12 at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:491)13 at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1206)14 at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:314)15 at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more https://web.liferay.com/community/forums/-/message_boards/view_message/4450255 about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping http://stackoverflow.com/questions/7620886/log4jerror-error-occured-while-converting-date each other. Join them; it only takes a minute: Sign up log4j:ERROR Error occured while converting date up vote 5 down vote favorite 1 I found this exception in my logs: log4j:ERROR Error occured while converting date. java.lang.NullPointerException at java.lang.System.arraycopy(Native Method) at java.lang.AbstractStringBuilder.getChars(AbstractStringBuilder.java:328) at java.lang.StringBuffer.getChars(StringBuffer.java:201) at org.apache.log4j.helpers.ISO8601DateFormat.format(ISO8601DateFormat.java:130) at java.text.DateFormat.format(DateFormat.java:316) at org.apache.log4j.helpers.PatternParser$DatePatternConverter.convert(PatternParser.java:443) at org.apache.log4j.helpers.PatternConverter.format(PatternConverter.java:65) at org.apache.log4j.PatternLayout.format(PatternLayout.java:506) at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:310) at org.apache.log4j.WriterAppender.append(WriterAppender.java:162) at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:251) at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:66) at org.apache.log4j.Category.callAppenders(Category.java:206) at org.apache.log4j.Category.forcedLog(Category.java:391) at org.apache.log4j.Category.info(Category.java:666) at org.obliquid.db.ConnectionManager.releaseConnection(ConnectionManager.java:313) at org.obliquid.db.ConnectionManager.finalize(ConnectionManager.java:331) at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method) at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83) at java.lang.ref.Finalizer.access$100(Finalizer.java:14) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160) I think it could be caused by my log4j.properties file, in particular by ConversionPattern. Any idea on how to fix? #Updated at Wed Sep 14 21:57:51 CEST 2011 #Wed Sep 14 21:

Built-ins for date/time/date-time values Page Contents date, time, datetime (when used with a date/time/date-time value)date_if_unknown, time_if_unknown, datetime_if_unknowniso_...string (when used with a date/time/date-time value) date, time, datetime (when used with a date/time/date-time value) These built-ins can be used to specify which parts of the date-like variable are in use: date: Date http://freemarker.org/docs/ref_builtins_date.html only, no time of the day. time: Only the time of the https://docs.oracle.com/cd/E13222_01/wls/docs61/notes/bugfixes2.html day, no date part datetime: Both date and time Ideally, you do not need to use these built-ins. Unfortunately, because of the technical limitations of the Java platform, FreeMarker sometimes can't find out which parts of a date-like value is a date, a time or a date-time; ask the programmers which variables liferay error has this problem. If FreeMarker has to execute an operation where this information is needed -- such as displaying the value as text -- but it does not know which parts are in use, it will stop with error. This is when you have to use these built-ins. For example, assume openingTime is a such problematic variable: <#assign x = openingTime> <#-- no problem can liferay error occurred occur here --> ${openingTime?time} <#-- without ?time it would fail --> <#-- For the sake of better understanding, consider this: --> <#assign openingTime = openingTime?time> ${openingTime} <#-- this will work now --> These built-ins can also be used to convert date-time values to date or time. For example: Last updated: ${lastUpdated} <#-- assume that lastUpdated is a date-time value --> Last updated date: ${lastUpdated?date} Last updated time: ${lastUpdated?time} will output something like: Last updated: 04/25/2003 08:00:54 PM Last updated date: 04/25/2003 Last updated time: 08:00:54 PM If the left side of the ? is string, then these built-ins convert strings to date/time/date-time. date_if_unknown, time_if_unknown, datetime_if_unknown Note: This built-in exists since FreeMarker 2.3.21. The date_if_unknown, time_if_unknown, datetime_if_unknown built-ins mark a date-like value with some of the sub-types: date without time, time, or date-time, respectively. However, if the value already holds this information, the built-in has no effect. That is, it will never convert the sub-type of a value, it only adds the sub-type if it was unknown. iso_... Note: These built-ins are deprecated since FreeMarker 2.3.21, where the date_format, time_format and datetime_format settings understand "iso" (for ISO 8601:2004 format) and "xs" (for XML

| WebLogic Server Doc Home | Release Notes | Previous Topic | Next Topic | Contents | View as PDF Resolved Problems The following sections describe problems that have been resolved by Service Packs for WebLogic Server 6.1. Service Packs are cumulative; the current release, Service Pack 7 contains all the fixes made in earlier Service Packs released for WebLogic Server 6.1. WebLogic Server 6.1 Service Pack 7 Solutions WebLogic Server 6.1 Service Pack 6 Solutions WebLogic Server 6.1 Service Pack 5 Solutions WebLogic Server 6.1 Service Pack 4 Solutions WebLogic Server 6.1 Service Pack 3 Solutions WebLogic Server 6.1 Service Pack 2 Solutions WebLogic Server 6.1 Service Pack 1 Solutions WebLogic Server 6.1 Release Solutions WebLogic Server 6.1 Service Pack 7 Solutions The following sections describe problems that have been resolved for the release of WebLogic Server 6.1 Service Pack 7. Administration Console Classloader Cluster Core Deployment EJB Internationalization JDriver JDBC JMS JNDI JSPs and Servlets JVM Operations, Administration and Management Plug-Ins RMI-IIOP RMI Samples Security SNMP WLEC WebLogic Tuxedo Connector Administration Console CR Number Description CR172370 When the Administration Console created an Application MBean, the associated WebAppComponent MBean incorrectly inherited the Application MBean name instead of the WebAppComponent's URI name. This caused the deployer tool to incorrectly create an additional deployment repository for this application when it was updated. This defect was corrected by a code change. CR105735 Navigation through the directories did not go through action servlet, so encoding was not set properly. A change was made to set the encoding explicitly in the page, so the correct encoding is used to produce the response. CR087598 Propagation from list page to realm deletion changed the MBean class name specific to the MBean to be deleted. Because of this MBean showed only the last deleted type MBeans in the list. A attribute (original class name from list) has been introduced which will be propagated in the above described flow. This at