正好公司想要做一个门户网站系统,因此查询了一些开源项目,找到了GateIn。先不说项目好坏,本文主要记录一下GateIn配置在Tomcat下启动时抛出的错误及解决的方法。
先说一下运行环境,OS: Windows XP SP3, JDK:1.6.0, Tomcat为GateIn应用程序自带,应该为6.0.28。在启动GateIn应用的过程中需要通过命令行的方式运行 gatein.bat,这个需要注意一下。在console内输入"gatein.bat run"(不包括冒号),即可启动Tomcat。在启动的过程中抛出如下错误:
严重: Cannot create the portal container 'portal' . ServletContext: org.apache.catalina.core.ApplicationContextFacade@150f0a7
java.lang.RuntimeException: Cannot instantiate component key=org.exoplatform.services.organization.idm.PicketLinkIDMService type=org.exoplatform.services.organization.idm.PicketLinkIDMServiceImpl found at jndi:/localhost/portal/WEB-INF/conf/organization/idm-configuration.xml
at org.exoplatform.container.jmx.MX4JComponentAdapter.getComponentInstance(MX4JComponentAdapter.java:124)
at org.exoplatform.container.management.ManageableComponentAdapter.getComponentInstance(ManageableComponentAdapter.java:68)
at org.exoplatform.container.ConcurrentPicoContainer.getInstance(ConcurrentPicoContainer.java:400)
at org.exoplatform.container.ConcurrentPicoContainer.getComponentInstancesOfType(ConcurrentPicoContainer.java:350)
at org.exoplatform.container.CachingContainer.getComponentInstancesOfType(CachingContainer.java:111)
at org.picocontainer.defaults.LifecycleVisitor.visitContainer(LifecycleVisitor.java:97)
at org.exoplatform.container.ConcurrentPicoContainer.accept(ConcurrentPicoContainer.java:506)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.picocontainer.defaults.AbstractPicoVisitor.traverse(AbstractPicoVisitor.java:32)
at org.picocontainer.defaults.LifecycleVisitor.traverse(LifecycleVisitor.java:63)
at org.picocontainer.defaults.LifecycleVisitor.start(LifecycleVisitor.java:113)
at org.exoplatform.container.ConcurrentPicoContainer.start(ConcurrentPicoContainer.java:453)
at org.exoplatform.container.ExoContainer.start(ExoContainer.java:186)
at org.exoplatform.container.PortalContainer.start(PortalContainer.java:595)
at org.exoplatform.container.ExoContainer.start(ExoContainer.java:180)
at org.exoplatform.container.RootContainer.createPortalContainer(RootContainer.java:338)
at org.exoplatform.container.RootContainer.registerPortalContainer(RootContainer.java:212)
at org.exoplatform.portal.application.PortalController.afterInit(PortalController.java:114)
at org.exoplatform.container.web.AbstractHttpServlet.init(AbstractHttpServlet.java:72)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1173)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:993)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4149)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4458)
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:526)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:630)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:556)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:491)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1206)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:314)
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:722)
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:516)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:583)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.exoplatform.container.ExoContainer.createComponent(ExoContainer.java:321)
at org.exoplatform.container.jmx.MX4JComponentAdapter.getComponentInstance(MX4JComponentAdapter.java:94)
... 47 more
Caused by: java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/E:/GateIn/lib/jaxb-impl-2.1.7.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
at com.sun.xml.bind.v2.model.impl.ModelBuilder.<clinit>(ModelBuilder.java:173)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:422)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:286)
at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139)
at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:117)
at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:188)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:132)
at javax.xml.bind.ContextFinder.find(ContextFinder.java:286)
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:372)
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:337)
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:244)
at org.picketlink.idm.impl.configuration.jaxb2.JAXB2IdentityConfiguration.createConfigurationMetaData(JAXB2IdentityConfiguration.java:129)
at org.exoplatform.services.organization.idm.PicketLinkIDMServiceImpl.<init>(PicketLinkIDMServiceImpl.java:117)
... 53 more
2011-2-14 15:22:02 org.apache.catalina.startup.HostConfig deployDescriptor
------------------------------------------------------分割线--------------------------------------------------------------
异常的原因可以看到:
Caused by: java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/E:/GateIn/lib/jaxb-impl-2.1.7.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
解释一下,错误提示说的是“链接错误”,原因是启动类加载器预先加载了 JAXB 2.0 API。但是当前应用的RI(jaxb-impl-2.1.7.jar)需要的是JAXB 2.1 API。可以使用endorsed目录机制替换掉JAXB 2.0,使JAXB 2.1加载到类加载器重。笔者随后到GateIn的lib文件夹下面找到了jaxb-api-2.1.jar和jaxb-impl-2.1.7.jar。错误提示说impl包没有找到2.1版本的jar包,但2.1.jar的确存在lib文件夹下,为什么没有加载呢?或者说新版本的jar包为什么没有替换掉旧版本的jar包?
在以下的链接中看到了一些提示,http://jaxb.java.net/guide/Migrating_JAXB_2_0_applications_to_JavaSE_6.html 。JavaSE 6 update 4之前,rt.jar包中集成了jaxb-api-2.0.jar。update4之后,JavaSE 6全部集成jaxb-api-2.1.jar。并提示了update4之前的解决方法。试了第一种,也就是在$JRE_HOME/lib/下面建立endorsed文件夹,然后拷贝jaxb-api-2.1.jar文件以替换旧版本文件。这种方法没有实质效果。在queue19的博客中找到了原因,http://queue19.iteye.com/blog/418748。如果是Tomcat 5.5,则新建文件路径为“Tomcat 5.5\common\endorsed”,如果是Tomcat 6.0,则新建路径为“Tomcat 6.0\endorsed”。(此处引用queue19文章内容,非本人撰写)
还有一种方法就是将JDK 6版本升级,升级到updat4版本之后。本人选择的此种方法,问题顺利解决掉。
分享到:
相关推荐
tomcat-juli.jar 用于在tomcat启动报错时除错
eclipse 部署tomcat 服务时出现问题
Tomcat无法正常启动的解决办法 教你如何解决Tomcat无法正常启动 欢迎下载
tomcat启动报错,启动超时,找不到类文件四渡赤水打成不是的
主要介绍了解决IDEA配置tomcat启动报错问题,本文给大家介绍的非常详细,对大家的学习或工作具有一定的参考借鉴价值,需要的朋友可以参考下
解决dubbo-admin在jdk1.8下启动报错问题,需要下载dubbo源码修改问题重新编译打包发布,这里已经和重新编译。
Tomcat报错,如: Can't load IA 32-bit .dll on a AMD 64-bit platform Can't load IA 64-bit .dll on a AMD 64-bit platform 都应该用x64里面的dll文件 不同的硬件平台需要与之对应的dll即可
后面我把原先tomcat启动环境用的jdk1.7改为了本机安装的jdk1.8就不在报错。 具体过程: 在myeclipse中点击window→preference→在搜索框中输入Tomcat→选择安装的tomcat版本,我这里是选择Tomcat 7.x→点击JDK→在...
tomcat7启动或运行报错 亲测解决的方法
主要给大家介绍了关于tomcat启动报:java.util.zip.ZipException错误的解决方法,文中通过示例代码介绍的非常详细,同样遇到这个问题的朋友可以参考借鉴,下面随着小编来一起学习学习吧
JSP中常见的Tomcat报错错误解析JSP中常见的Tomcat报错错误解析JSP中常见的Tomcat报错错误解析JSP中常见的Tomcat报错错误解析
tomcat启动不了问题处理 解决tomcat启动不了问题
tomcat报错 原因JDK没有安装好!这里提供了报错信息
tomcat下webapps防止刷新报错的静态文件
然后我运行Eclipse后server报错:端口8082被占用 ;如图 之后我检查进程,发现8082端口被一个java程序占用 我把进程杀死后tomcat就变成这样了: 重启tomcat后又好了: 然后再次查询8082端口后又有一个java程序...
NULL 博文链接:https://lionelxx777.iteye.com/blog/358193
tomcat 开机启动,dos窗口去掉,tomcat 开机启动,dos窗口去掉
tcnative-1.dll解决windows 7 64下 tomcat启动报错-附件资源
从几个方面讨论tomcat报错Service Temporarily Unavailable tomcat解决方式
NULL 博文链接:https://luihuilang.iteye.com/blog/396488