加载中…
个人资料
  • 博客等级:
  • 博客积分:
  • 博客访问:
  • 关注人气:
  • 获赠金笔:0支
  • 赠出金笔:0支
  • 荣誉徽章:
正文 字体大小:

【2008-12-12】weblogic v10.3配置nodemanager提示认证hostname错误的处理

(2011-05-23 21:33:29)
标签:

it

分类: 日常心得
按照原来成功在weblogic server v10.1配置nodemanager的方法,在v10.3上进行相应的配置,启动nodemanager之后,nodemanager和 adminserver都报hostname无法通过认证的错误提示,当然更无法通过nodemanager来启动managedserver。而且,在 console刷新servers界面的时候都会报这样的错误,有多少个加入machine的server就会报多少次错误。

adminserver报的错误信息:
<Dec 11, 2008 10:38:39 PM GMT+08:00> <Warning> <Security> <BEA-090504> <Certificate chain received from localhost - 127.0.0.1 failed hostname verification check. Certificate contained porsche but check expected localhost>

nodemanager报的错误信息:
<Dec 11, 2008 10:38:39 PM GMT+08:00> <Warning> <Security> <BEA-090482> <BAD_CERTIFICATE alert was received from localhost - 127.0.0.1. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
<Dec 11, 2008 10:38:39 PM> <Warning> <Uncaught exception in server handler: javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from localhost - 127.0.0.1. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from localhost - 127.0.0.1. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.
        at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
        at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertReceived(Unknown Source)
        at com.certicom.tls.record.alert.AlertHandler.handle(Unknown Source)
        at com.certicom.tls.record.alert.AlertHandler.handleAlertMessages(Unknown Source)
        at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
        at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
        at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
        at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
        at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
        at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
        at com.certicom.tls.record.ReadHandler.read(Unknown Source)
        at com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
        at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
        at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
        at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
        at java.io.InputStreamReader.read(InputStreamReader.java:167)
        at java.io.BufferedReader.fill(BufferedReader.java:136)
        at java.io.BufferedReader.readLine(BufferedReader.java:299)
        at java.io.BufferedReader.readLine(BufferedReader.java:362)
        at weblogic.nodemanager.server.Handler.run(Handler.java:66)
        at java.lang.Thread.run(Thread.java:619)

解决的办法:
修改adminserver的ssl默认参数Hostname Verification:None。之后不再提示上述错误。
但是,另外发现nodemanager在启动managedserver过程中始终停在输出日志后:
<Dec 12, 2008 10:03:28 AM> <Info> <WEBDEV> <proxy> <Working directory is "/webdev/domains/WEBDEV">
<Dec 12, 2008 10:03:28 AM> <Info> <WEBDEV> <proxy> <Server output log file is "/webdev/domains/WEBDEV/servers/proxy/logs/roxy.out">

BTW:另外发现不能设置adminserver的listner address,否则只能在对应地址打开,而不能同时打开localhost和外部地址的监听。

0

阅读 收藏 喜欢 打印举报/Report
  

新浪BLOG意见反馈留言板 欢迎批评指正

新浪简介 | About Sina | 广告服务 | 联系我们 | 招聘信息 | 网站律师 | SINA English | 产品答疑

新浪公司 版权所有