weblogic部署web项目出现错误

1、错误描写叙述

<2015-3-15 下午02时13分01秒 CST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<2015-3-15 下午02时13分02秒 CST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<2015-3-15 下午02时13分04秒 CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 24.65-b04 from Oracle Corporation>
<2015-3-15 下午02时13分06秒 CST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.6.0  Tue Nov 15 08:52:36 PST 2011 1441050 >
<2015-3-15 下午02时13分09秒 CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<2015-3-15 下午02时13分09秒 CST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<2015-3-15 下午02时13分10秒 CST> <Notice> <Log Management> <BEA-170019> <The server log file C:\Oracle\Middleware\user_projects\domains\base_domain\servers\AdminServer\logs\AdminServer.log is opened. All server side log events will be written to this file.>
<2015-3-15 下午02时13分12秒 CST> <Error> <Socket> <BEA-000438> <Unable to load performance pack. Using Java I/O instead. Please ensure that wlntio.dll is in: ‘D:\Java\jdk1.7.0_67\bin;C:\Oracle\Middleware\wlserver_10.3\bin;C:\Oracle\Middleware\wlserver_10.3\server\bin‘
>
<2015-3-15 下午02时13分18秒 CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<2015-3-15 下午02时13分20秒 CST> <Warning> <Store> <BEA-280109> <Unable to load the native wlfileio library for the persistent file store "_WLS_AdminServer". The store will use buffered I/O. The store is still operating in a transactionally safe synchronous mode. See store open log messages for the requested and final write policies.>
<2015-3-15 下午02时13分30秒 CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<2015-3-15 下午02时13分30秒 CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<2015-3-15 下午02时13分43秒 CST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<2015-3-15 下午02时13分43秒 CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<2015-3-15 下午02时13分43秒 CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<2015-3-15 下午02时13分44秒 CST> <Notice> <Security> <BEA-090171> <Loading the identity certificate and private key stored under the alias DemoIdentity from the jks keystore file C:\Oracle\Middleware\wlserver_10.3\server\lib\DemoIdentity.jks.>
<2015-3-15 下午02时13分44秒 CST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\Oracle\Middleware\wlserver_10.3\server\lib\DemoTrust.jks.>
<2015-3-15 下午02时13分44秒 CST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file D:\Java\jdk1.7.0_67\jre\lib\security\cacerts.>
<2015-3-15 下午02时13分44秒 CST> <Alert> <Security> <BEA-090152> <Demo trusted CA certificate is being used in production mode: [
[
  Version: V3
  Subject: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
  Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4

  Key:  Sun RSA public key, 512 bits
  modulus: 9550192877869244258838480703390456015046425375252278279190673063544122510925482179963329236052146047356415957587628011282484772458983977898996276815440753
  public exponent: 65537
  Validity: [From: Fri Mar 22 04:12:27 CST 2002,
               To: Wed Mar 23 04:12:27 CST 2022]
  Issuer: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
  SerialNumber: [    33f10648 fcde0deb 4199921f d64537f4]

Certificate Extensions: 1
[1]: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
  Key_CertSign
]

]
  Algorithm: [MD5withRSA]
  Signature:
0000: 9D 26 4C 29 C8 91 C3 A7   06 C3 24 6F AE B4 F8 82  .&L)......$o....
0010: 80 4D AA CB 7C 79 46 84   81 C4 66 95 F4 1E D8 C4  .M...yF...f.....
0020: E9 B7 D9 7C E2 23 33 A4   B7 21 E0 AA 54 2B 4A FF  .....#3..!..T+J.
0030: CB 21 20 88 81 21 DB AC   90 54 D8 7D 79 63 23 3C  .! ..!...T..yc#<

] The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.>
<2015-3-15 下午02时13分44秒 CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<2015-3-15 下午02时13分44秒 CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<2015-3-15 下午02时13分44秒 CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G2,OU=(c) 2007 thawte\, Inc. - For authorized use only,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.10045.4.3.3.>
<2015-3-15 下午02时13分44秒 CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Buypass Class 3 Root CA,O=Buypass AS-983163327,C=NO". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<2015-3-15 下午02时13分44秒 CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Buypass Class 2 Root CA,O=Buypass AS-983163327,C=NO". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<2015-3-15 下午02时13分44秒 CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<2015-3-15 下午02时13分44秒 CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<2015-3-15 下午02时13分44秒 CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Class 3 Public Primary Certification Authority - G4,OU=(c) 2007 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.10045.4.3.3.>
<2015-3-15 下午02时13分44秒 CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<2015-3-15 下午02时13分44秒 CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<2015-3-15 下午02时13分44秒 CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=AffirmTrust Commercial,O=AffirmTrust,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<2015-3-15 下午02时13分44秒 CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<2015-3-15 下午02时13分44秒 CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=AffirmTrust Premium ECC,O=AffirmTrust,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.10045.4.3.3.>
<2015-3-15 下午02时13分44秒 CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<2015-3-15 下午02时13分44秒 CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<2015-3-15 下午02时13分44秒 CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G2,OU=(c) 2007 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.10045.4.3.3.>
<2015-3-15 下午02时13分44秒 CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=AffirmTrust Premium,O=AffirmTrust,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.12.>
<2015-3-15 下午02时13分45秒 CST> <Warning> <Server> <BEA-002611> <Hostname "2014-0831-1223", maps to multiple IP addresses: 192.168.1.101, fe80:0:0:0:f9a8:f561:a1a9:decf%13>
<2015-3-15 下午02时13分45秒 CST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on 192.168.1.101:7002 for protocols iiops, t3s, ldaps, https.>
<2015-3-15 下午02时13分45秒 CST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.1.101:7001 for protocols iiop, t3, ldap, snmp, http.>
<2015-3-15 下午02时13分45秒 CST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[6]" is now listening on 127.0.0.1:7002 for protocols iiops, t3s, ldaps, https.>
<2015-3-15 下午02时13分45秒 CST> <Notice> <Server> <BEA-002613> <Channel "Default[4]" is now listening on fe80:0:0:0:0:100:7f:fffe:7001 for protocols iiop, t3, ldap, snmp, http.>
<2015-3-15 下午02时13分45秒 CST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[2]" is now listening on fe80:0:0:0:f9a8:f561:a1a9:decf:7002 for protocols iiops, t3s, ldaps, https.>
<2015-3-15 下午02时13分45秒 CST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[4]" is now listening on fe80:0:0:0:0:100:7f:fffe:7002 for protocols iiops, t3s, ldaps, https.>
<2015-3-15 下午02时13分45秒 CST> <Notice> <Server> <BEA-002613> <Channel "Default[6]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
<2015-3-15 下午02时13分45秒 CST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on fe80:0:0:0:258c:5c5:3ef4:278d:7001 for protocols iiop, t3, ldap, snmp, http.>
<2015-3-15 下午02时13分45秒 CST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[3]" is now listening on fe80:0:0:0:ac34:62eb:b0cb:ccf1:7002 for protocols iiops, t3s, ldaps, https.>
<2015-3-15 下午02时13分45秒 CST> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on fe80:0:0:0:f9a8:f561:a1a9:decf:7001 for protocols iiop, t3, ldap, snmp, http.>
<2015-3-15 下午02时13分45秒 CST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[5]" is now listening on 0:0:0:0:0:0:0:1:7002 for protocols iiops, t3s, ldaps, https.>
<2015-3-15 下午02时13分45秒 CST> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on fe80:0:0:0:ac34:62eb:b0cb:ccf1:7001 for protocols iiop, t3, ldap, snmp, http.>
<2015-3-15 下午02时13分45秒 CST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[1]" is now listening on fe80:0:0:0:258c:5c5:3ef4:278d:7002 for protocols iiops, t3s, ldaps, https.>
<2015-3-15 下午02时13分45秒 CST> <Notice> <Server> <BEA-002613> <Channel "Default[5]" is now listening on 0:0:0:0:0:0:0:1:7001 for protocols iiop, t3, ldap, snmp, http.>
<2015-3-15 下午02时13分45秒 CST> <Notice> <WebLogicServer> <BEA-000329> <Started WebLogic Admin Server "AdminServer" for domain "base_domain" running in Production Mode>
<2015-3-15 下午02时13分45秒 CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<2015-3-15 下午02时13分45秒 CST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<2015-3-15 下午02时28分02秒 CST> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 0:0:0:0:0:0:0:1:49,696 during the configured idle timeout of 5 secs>
<2015-3-15 下午02时31分17秒 CST> <Warning> <Security> <BEA-090475> <Plaintext data for protocol HTTP was received from peer 0:0:0:0:0:0:0:1 - 0:0:0:0:0:0:0:1 instead of an SSL handshake.>
<2015-3-15 下午02时31分19秒 CST> <Warning> <Security> <BEA-090475> <Plaintext data for protocol HTTP was received from peer 0:0:0:0:0:0:0:1 - 0:0:0:0:0:0:0:1 instead of an SSL handshake.>
<2015-3-15 下午02时31分32秒 CST> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 0:0:0:0:0:0:0:1:55,716 during the configured idle timeout of 5 secs>
Error 404--Not Found

From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:

10.4.5 404 Not Found

The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.

2、错误原因

3、解决的方法

时间: 2024-12-18 15:11:59

weblogic部署web项目出现错误的相关文章

Linux Weblogic部署web项目(war包)

第一步,启动并访问weblogic,进入登录页面 第二步,进入主页面,开始部署项目 第三步,上载项目war包 选择需要上载的本地war包 第四步,开始项目配置 继续下一步 选择红色标记的配置 第五步,完成配置 第六步,激活配置 第七步,开始配置系统环境 第八步,进入AdminServer 第九步,选择协议,然后选择HTTP 第十步,配置HTTP协议中的信息,没用红款标记的保持默认就行了 配置到此结束... 最后,再次部署项目 启动部署项目 然后就可以访问项目了  http://IP:PORT/P

Eclipse部署Web项目时常见的错误和解决方案

Tomcat部署Web项目到tomcat 在eclipse中找到Servers项,打开服务器(F3)(建议直接删除服务器,重新建立再设置比较好)1.Servers Locations 中选择Use Tomcat installation 2.Deploy path 改成 webapps这时候在eclipse上直接运行项目,就会自动部署到tomcat上,通过浏览器或者eclipse都可以访问该项目. Tomcat控制台的用户角色配置 在Tomcat的Mapper App中,默认没有提供控制台角色.

利用Tomcat部署Web项目报错

1.错误描述 usage: java org.apache.catalina.startup.Catalina [ -config {pathname} ] [ -nonaming ] { -help | start | stop } 八月 18, 2014 7:35:40 下午 org.apache.catalina.core.AprLifecycleListener init 信息: Loaded APR based Apache Tomcat Native library 1.1.24 u

Linux服务器上的tomcat中部署web项目

首先了解一下下面几个概念,讲得不太准确: 1.JVM JVM是class以及jar(实际上就是很多个class压缩在一起)的运行环境,特征就是java和javaw命令,通过这两个命令,你可以执行class和jar文件.你可以通过-classpath参数指定你需要加载的jar文件 2.JDK JDK就是JAVA的命令行开发环境,内置了JVM,特征就是javac命令,这个命令允许你将.java源文件批量或者单个编译成.class文件,从而可以通过JVM的java命令执行.在编译时你可以通过-clas

使用myeclipse tomcat插件部署web项目时报错 an internal error occurred during add deployment . java.lang.nullpointerexception

问题描述: 使用myeclipse10的tomcat插件部署web项目时,首次部署.实际部署到了tomcat/webapps目录下且tomcat启动成功,但是eclipse报错"An internal error occurred during: "Add Deployment"  : 且eclipse中看不到部署的项目.重新部署按钮也无法点击,如图: myeclipse中看不到部署的项目: myeclipse中可以看到部署的项目如下(作为看不到项目的对比): 再次试图部署项

(转)maven自动部署web项目到tomcat8(向下兼容7)

maven自动部署web项目到tomcat8(向下兼容7) 2014-08-29 10:52 网站上线以后,为了保证网站运行的连续性,有新功能更新时,不能重启Tomcat服务器去部署新增功能.因此,就研 究一下用maven的自动部署功能. 1首先要保证自己电脑上装了Tomcat服务器 进入Tomcat安装目录,打开..\conf\tomcat-users.xml,在这个配置文件中加入以下内容: <role rolename="manager-gui"/> <role

开发过程使用Tomcat Maven插件持续快捷部署Web项目

我在平时工作中部署Web项目到测试服务器上的Tomcat时用的是Hudson.Hudson本身已经跟SVN.Git.Maven集成并且支持添加各种插件.但如果使用Hudson,我需要配置两个任务:一个任务负责打包项目成WAR,另外一个任务负责部署打包好的WAR包到目标服务器的Tomcat上.虽然任务只需要配置一次,但每次修改代码提交后,都得切换到浏览器点Hudson构建任务页面上的Build Now按钮,然后还得跳转到另一个页面观察是否有报错,然后再点击执行相应的部署任务.烦不胜烦,偶然发现To

JBoss环境搭建及部署Web项目

http://blog.csdn.net/pop303/article/details/7210290 赶在年前学习了一下JBOSS,之前觉得JBOSS相关资料会有很多,不过现在发现很少,在亚马逊出也是很少,只有一个“JBoss实战:服务器配置指南 ”,不过我找到了英文版,有要的可以邮件给大家.我想从不会JBOSS开始进行,到我打包部署到JBOSS后能看到我的HELLO!网页结束的过程. 首先要进行的工作是下JBOSS.JBOSS插件.开发以eclipse为平台,都需要JEE方式. JBOSS,

6.linux下部署 web 项目

安装java 1.下载 linux 环境的jdk 2.上传该压缩包到 linux 系统中并且解压 tar -zxvf 压缩包名 3.配置环境变量并且刷新配置 export JAVA_HOME=/alidata/java/jdk1.8.0_111 export PATH=$JAVA_HOME/bin:$PATH source /etc/profile 安装tomcat 1.在官网下载好tomcat的压缩包 2.安装 tomcat 之前必须安装好java的环境 3.进入到 tomcat 中 bin