dotcms在linux下安装后运行不能,求助
按照开发文档上的步骤安装之后,运行catalina.sh run,会卡在
Using CATALINA_BASE: /root/dotcms/dotserver/tomcat
Using CATALINA_HOME: /root/dotcms/dotserver/tomcat
Using CATALINA_TMPDIR: /root/dotcms/dotserver/tomcat/temp
Using JRE_HOME: /usr/java/jdk1.7.0
Using CLASSPATH: /root/dotcms/dotserver/tomcat/bin/bootstrap.jar
Usage: catalina.sh ( commands ... )
commands:
debug Start Catalina in a debugger
debug -security Debug Catalina with a security manager
jpda start Start Catalina under JPDA debugger
run Start Catalina in the current window
run -security Start in the current window with security manager
start Start Catalina in a separate window
start -security Start in a separate window with security manager
stop Stop Catalina, waiting up to 5 seconds for the process to end
stop n Stop Catalina, waiting up to n seconds for the process to end
stop -force Stop Catalina, wait up to 5 seconds and then use kill -KILL if still running
stop n -force Stop Catalina, wait up to n seconds and then use kill -KILL if still running
version What version of tomcat are you running?
Note: Waiting for the process to end and use of the -force option require that $CATALINA_PID is defined
接着就没了下文。远程输入IP地址发现无法访问,回头查看数据库发现里面没有写入任何新东西。于是反回去查看错误日志dotcms.log,发现有如下情况
[05/12/12 01:44:20:176 UTC] INFO startup.HostConfig: Deploying web application directory ROOT
[05/12/12 01:44:20:428 UTC] ERROR loader.WebappClassLoader: A web application registered the JBDC driver [org.h2.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
[05/12/12 01:44:23:769 UTC] INFO util.Config: Initializing properties reader.
[05/12/12 01:44:23:796 UTC] INFO util.Config: Loading dotCMS Properties...
[05/12/12 01:44:23:854 UTC] INFO util.Config: Assigned default refresh interval: 5 minutes.
[05/12/12 01:44:23:854 UTC] INFO util.Config: dotCMS Properties Loaded
[05/12/12 01:44:23:854 UTC] INFO business.CacheLocator: loading cache administrator: com.dotmarketing.business.DotGuavaCacheAdministratorImpl
[05/12/12 01:44:23:890 UTC] INFO business.ESDistributedJournalFactoryImpl: Server IDs configured: [1]
[05/12/12 01:44:23:891 UTC] INFO util.ConfigUtils: Using configured hostname: 1
[05/12/12 01:44:24:310 UTC] INFO business.CacheLocator: loading cache administrator: com.dotmarketing.business.DotGuavaCacheAdministratorImpl
[05/12/12 01:44:24:311 UTC] INFO business.ESDistributedJournalFactoryImpl: Server IDs configured: [1]
[05/12/12 01:44:24:311 UTC] INFO util.ConfigUtils: Using configured hostname: 1
[05/12/12 01:44:24:316 UTC] FATAL business.CacheLocator: Unable to load Cache Admin:com.dotmarketing.business.DotGuavaCacheAdministratorImpl
[05/12/12 01:44:24:425 UTC] ERROR modeler.Registry: Null component Catalina:type=JspMonitor,name=jsp,WebModule=//localhost/,J2EEApplication=none,J2EEServer=none
[05/12/12 01:44:24:425 UTC] ERROR startup.HostConfig: Error deploying web application directory ROOT
java.lang.NoClassDefFoundError: Could not initialize class com.sun.crypto.provider.SunJCE
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
at java.lang.Class.newInstance0(Class.java:372)
at java.lang.Class.newInstance(Class.java:325)
at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:221)
at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:206)
at java.security.AccessController.doPrivileged(Native Method)
at sun.security.jca.ProviderConfig.doLoadProvider(ProviderConfig.java:206)
at sun.security.jca.ProviderConfig.getProvider(ProviderConfig.java:187)
at sun.security.jca.ProviderList.getProvider(ProviderList.java:232)
at sun.security.jca.ProviderList.getService(ProviderList.java:330)
at sun.security.jca.GetInstance.getInstance(GetInstance.java:157)
at java.security.Security.getImpl(Security.java:695)
at java.security.MessageDigest.getInstance(MessageDigest.java:159)
at org.apache.catalina.session.ManagerBase.getDigest(ManagerBase.java:324)
at org.apache.catalina.session.ManagerBase.generateSessionId(ManagerBase.java:999)
at org.apache.catalina.session.StandardManager.start(StandardManager.java:631)
at org.apache.catalina.core.ContainerBase.setManager(ContainerBase.java:438)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4396)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:546)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1041)
at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:964)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:785)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:519)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:581)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
[05/12/12 01:44:24:448 UTC] INFO http11.Http11Protocol: Starting Coyote HTTP/1.1 on http-198.98.98.250-8080
[05/12/12 01:44:24:516 UTC] INFO common.ChannelSocket: JK: ajp13 listening on /0.0.0.0:8009
[05/12/12 01:44:24:529 UTC] INFO server.JkMain: Jk running ID=0 time=0/31 config=null
[05/12/12 01:44:24:530 UTC] INFO startup.Catalina: Server startup in 10782 ms
[05/12/12 01:44:31:685 UTC] INFO http11.Http11Protocol: Pausing Coyote HTTP/1.1 on http-198.98.98.250-8080
[05/12/12 01:44:32:695 UTC] INFO core.StandardService: Stopping service Catalina
[05/12/12 01:44:32:696 UTC] WARN startup.HostConfig: Error while removing context []
java.lang.NullPointerException
at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:915)
at org.apache.catalina.startup.HostConfig.undeployApps(HostConfig.java:1319)
at org.apache.catalina.startup.HostConfig.stop(HostConfig.java:1290)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:323)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1086)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1098)
at org.apache.catalina.core.StandardEngine.stop(StandardEngine.java:448)
at org.apache.catalina.core.StandardService.stop(StandardService.java:587)
at org.apache.catalina.core.StandardServer.stop(StandardServer.java:744)
at org.apache.catalina.startup.Catalina.stop(Catalina.java:648)
at org.apache.catalina.startup.Catalina$CatalinaShutdownHook.run(Catalina.java:692)
[05/12/12 01:44:32:699 UTC] INFO http11.Http11Protocol: Stopping Coyote HTTP/1.1 on http-198.98.98.250-8080
请问一下是出了什么问题?多谢各位大牛指点!
需要的话之后我可以贴出来ROOT.xml,server.xml的配置情况
相关推荐
【Python编程】Python文档字符串与代码文档化规范
内容概要:本文全面解析Python代码文档化的技术规范与工具链,重点对比Google风格、NumPy风格、Sphinx reStructuredText在文档字符串格式上的差异。文章从PEP 257文档字符串约定出发,详解__doc__属性的运行时访问、docstring的类型提示集成、以及Sphinx autodoc的自动API文档生成机制。通过代码示例展示type hints与docstring的互补使用、mkdocs的Markdown文档站点构建、以及pydoc的内置文档浏览器,同时介绍Sphinx的交叉引用(:func:/:class:)、扩展主题(Read the Docs)配置、以及doctest的文档示例自动验证,最后给出在开源项目、内部SDK、API网关等场景下的文档驱动开发(DDD)策略与文档即代码(Docs as Code)实践。 sjbzhibo.hqjxgs.com hntxmedia.com www.honglu-cy.com seriea-live-streaming.hnxskj.com cbalive.htne.com.cn
毕业设计含文档和代码VB个人邮件处理系统(源代码+系统)
毕业设计含文档和代码VB个人邮件处理系统(源代码+系统)
证件照批量处理 - 批量证件照制作与换底色工具
一键批量导入照片,自动裁剪为标准证件照尺寸并替换红蓝白底色,支持自定义规格、名单映射与打包导出,快速完成团队证件照采集与制作。 主要功能:批量导入多张证件照原图、统一裁剪为标准证件照尺寸、一键替换红蓝白三色底色、内置一寸二寸等规格预设、按毫米自定义证件照尺寸、批量打包导出为压缩文件、按名单自动匹配人员信息、导入 CSV 花名册批量对应。 适用场景:证件照批量处理是一款面向企业人事、行政与摄影工作室的桌面端证件照制作工具。它把过去"一张张导入修图软件、手动裁剪、反复调整底色"的重复劳动,压缩为一次拖拽加一次点击:批量导入原始照片后,软件按所选规格统一裁剪、替换底色、排版并打包输出,让上百人的证件照采集在几分钟内完成。 说明:试用功能限制说明:本软件支持试用体验,批量处理按单次任务计算额度——每次批量任务最多可处理 5 个文件,并完整包含规格裁剪、底色替换、排版与打包导出等全部流程。当单次任务的文件数超过 5 个时,需先在软件内完成一次性功能授权,之后即可继续处理本次任务的全部文件;日常的单张处理与预览不受任何限制。
旋转设备激光对中偏差与允许公差判定器
【适用方向】设备工程与通信协议 【工具用途】 「旋转设备激光对中偏差与允许公差判定器」用于半导体制造过程中的工程计算与分析, 帮助工艺、设备、质量与生产工程师快速完成日常数据处理工作。 【能解决什么】 · 免去手工Excel 反复整理与公式编写,直接导入数据即可出结果 · 计算过程透明,关键参数可按现场实际调整 · 输出图表与明细报表,便于直接用于汇报与存档 【包内内容】 · 工具源码(Python,可直接运行) · 使用说明(数据格式与操作步骤) · 依赖清单与示例数据 【适用人群】 半导体 FAB / 晶圆厂:工艺、设备、质量、IE、生产工程师; 以及 MES 与智能制造方向的技术人员。 【使用说明】 解压后按说明导入数据运行即可;工具在本地处理数据,不联网。
园区如何帮助企业精准对接政策?数字化智配服务解决方案.docx
科易网基于40亿+科创知识图谱数据库,深度探索AI技术在技术转移、成果转化、技术经纪、知识产权、产业创新、科技招商等垂直领域的多样化应用场景,研究科技创新领域的AI+数智化解决方案,推动科技创新与产业创新智能化发展。


