weblogic 10.3不能启动报数组越界
2015-04-17 16:21
976 查看
今天一个weblogic服务启动到一半报错，这个错误一看就是weblogic内部的错误：
<BEA-000386> <Server subsystem failed. Reason: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.RangeCheck(ArrayList.java:547)
at java.util.ArrayList.get(ArrayList.java:322)
at weblogic.rmi.cluster.BasicReplicaList.getPrimary(BasicReplicaList.java:91)
at weblogic.rmi.cluster.ClusterableRemoteRef.getPrimaryRef(ClusterableRemoteRef.java:153)
at weblogic.rmi.cluster.ClusterableRemoteRef.add(ClusterableRemoteRef.java:472)
Truncated. see log file for complete stacktrace
>
<2015-4-17 上午11时04分19秒 CST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<BEA-000386> <Server subsystem failed. Reason: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.RangeCheck(ArrayList.java:547)
at java.util.ArrayList.get(ArrayList.java:322)
at weblogic.rmi.cluster.BasicReplicaList.getPrimary(BasicReplicaList.java:91)
at weblogic.rmi.cluster.ClusterableRemoteRef.getPrimaryRef(ClusterableRemoteRef.java:153)
at weblogic.rmi.cluster.ClusterableRemoteRef.add(ClusterableRemoteRef.java:472)
Truncated. see log file for complete stacktrace
>
<2015-4-17 上午11时04分19秒 CST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
| intermittently Servers in Cluster Fail with java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 (文档 ID 1680266.1) |  转到底部 | |
In this Document
Oracle WebLogic Server - Version 10.3.6 to 12.1.2.0.0 |
| PATCH INFORMATION | |
|---|---|
| WLS Version | Patch Number |
| 10.3.5 | Patch 17721032 |
| 10.3.6.0.7 Overlay | Patch 17721032 |
| 10.3.6.0.8 Overlay | Patch 17721032 |
| 10.3.6.0.9 Overlay | Patch 17721032 |
To apply one of these patches, click on the link for your WLS version and download the appropriate patch from My Oracle Support. You can also search in My Oracle Support for the patch number for your WLS version: for detailed instructions, please see Master
Note: How to Locate and Download Patches for WebLogic Server Using My Oracle Support Note 1302053.1. If you
are using WLS 12.1.1 or earlier (including Fusion Middleware 11g/WLS 10.3.x), please use Smart Update to apply the patches. For instructions, please see How to Apply WebLogic Server (WLS) Patches Using Smart Update Note
876004.1. Smart Update is no longer applicable for WLS 12.1.2 and higher. On these versions, please use the OPatch tool to apply the patches. For instructions, please see the documentation atPatching
with OPatch. Coverage of all patching and maintenance issues is available at the Information Center at Note
1573509.2.
Patches are specifically tied to a particular release and maintenance pack of WebLogic Server (WLS). A patch for WLS 12.1.1, for example, would not work on WLS 12.1.2. In a few cases, patches are also specific to particular operating systems. If you think
you are experiencing the problem outlined in this note, and you are running a WLS version which is eligible for error correction (see Note
950131.1 for more about the Oracle Error Correction Policy), but your WLS version is not included in the list of patches provided here, please contact support and ask for a version of the patch appropriate for you. Please reference this note as well as
this bug number to help speed our service for you.
NOTE: Patches are applied per WLS installation and not per domain. That is, if you apply this patch on one WLS installation, then all of the servers from all the domains in that installation will have this patch. On the other hand, if you have
a managed server in another machine in a domain (that is, set up with its own WLS installation), you need to install this patch on that other machine as well. Generally, patches can only be applied while the server is not running because WLS locks the needed
files while it is running. If, however, you are able to apply a patch while WLS is running, you must restart WLS before the patch will take effect.
REFERENCES
NOTE:883024.1 - IndexOutOfBoundsException When Booting Managed Servers into Cluster in WebLogic Server (WLS)BUG:17721032 - JAVA.LANG.INDEXOUTOFBOUNDSEXCEPTION: INDEX: 0, SIZE: 0
|
|
|
|
|
|
| Information Center: Oracle WebLogic Server [1298857.2] Information Center: WebLogic Server Java Message Service (JMS) [1373135.2] Information Center: WebLogic Server SSL and Security [1376143.2] |
|
| IndexOutOfBoundsException When Booting Managed Servers into Cluster in WebLogic Server (WLS) [883024.1] |
|
| intermittently Servers in Cluster Fail with java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 [1680266.1] | |
| ||
| "java.lang.IndexOutOfBoundsException: Index: 0, Size: 0" Error Message When Completing a Horizontal Scale Out in OBIEE 11g [1906153.1] | |
| ||
| Stuck Thread observerd at sun.nio.ch.DevPollArrayWrapper.poll0(Native Method) On WebLogic Server 12.1.3.0.0 [1986468.1] | |
| ||
| WLS 12.1.2 Managed Servers take a Long Time to Start on Solaris 11 when Admin Server Listens on localhost [1627400.1] | |
| ||
| WebLogic Server (WLS) Application - High CPU with STUCK Threads at HashMap Methods [1315750.1] | |
|
To apply one of these patches, click on the link for your WLS version and download the appropriate patch from My Oracle Support. You can also search in My Oracle Support for the patch number for your WLS version: for detailed instructions, please see Master Note: How to Locate and Download Patches for WebLogic Server Using My Oracle Support Note 1302053.1. If you are using WLS 12.1.1 or earlier (including Fusion Middleware 11g/WLS 10.3.x), please use Smart Update to apply the patches. For instructions, please see How to Apply WebLogic Server (WLS) Patches Using Smart Update Note 876004.1. Smart Update is no longer applicable for WLS 12.1.2 and higher. On these versions, please use the OPatch tool to apply the patches. For instructions, please see the documentation at Patching with OPatch. Coverage of all patching and maintenance issues is available at the Information Center at Note 1573509.2. Patches are specifically tied to a particular release and maintenance pack of WebLogic Server (WLS). A patch for WLS 12.1.1, for example, would not work on WLS 12.1.2. In a few cases, patches are also specific to particular operating systems. If you think you are experiencing the problem outlined in this note, and you are running a WLS version which is eligible for error correction (see Note 950131.1 for more about the Oracle Error Correction Policy), but your WLS version is not included in the list of patches provided here, please contact support and ask for a version of the patch appropriate for you. Please reference this note as well as this bug number to help speed our service for you. NOTE: Patches are applied per WLS installation and not per domain. That is, if you apply this patch on one WLS installation, then all of the servers from all the domains in that installation will have this patch. On the other hand, if you have a managed server in another machine in a domain (that is, set up with its own WLS installation), you need to install this patch on that other machine as well. Generally, patches can only be applied while the server is not running because WLS locks the needed files while it is running. If, however, you are able to apply a patch while WLS is running, you must restart WLS before the patch will take effect.
BUG:11796397 - |
To apply one of these patches, click on the link for your WLS version and download the appropriate patch from My Oracle Support. You can also search in My Oracle Support for the patch number for your WLS version: for detailed instructions, please see Master Note: How to Locate and Download Patches for WebLogic Server Using My Oracle Support Note 1302053.1. If you are using WLS 12.1.1 or earlier (including Fusion Middleware 11g/WLS 10.3.x), please use Smart Update to apply the patches. For instructions, please see How to Apply WebLogic Server (WLS) Patches Using Smart Update Note 876004.1. Smart Update is no longer applicable for WLS 12.1.2 and higher. On these versions, please use the OPatch tool to apply the patches. For instructions, please see the documentation at Patching with OPatch. Coverage of all patching and maintenance issues is available at the Information Center at Note 1573509.2. Patches are specifically tied to a particular release and maintenance pack of WebLogic Server (WLS). A patch for WLS 12.1.1, for example, would not work on WLS 12.1.2. In a few cases, patches are also specific to particular operating systems. If you think you are experiencing the problem outlined in this note, and you are running a WLS version which is eligible for error correction (see Note 950131.1 for more about the Oracle Error Correction Policy), but your WLS version is not included in the list of patches provided here, please contact support and ask for a version of the patch appropriate for you. Please reference this note as well as this bug number to help speed our service for you. NOTE: Patches are applied per WLS installation and not per domain. That is, if you apply this patch on one WLS installation, then all of the servers from all the domains in that installation will have this patch. On the other hand, if you have a managed server in another machine in a domain (that is, set up with its own WLS installation), you need to install this patch on that other machine as well. Generally, patches can only be applied while the server is not running because WLS locks the needed files while it is running. If, however, you are able to apply a patch while WLS is running, you must restart WLS before the patch will take effect.
BUG:11796397 - |
内容来自用户分享和网络整理，不保证内容的准确性，如有侵权内容，可联系管理员处理 
相关文章推荐
- weblogic 进程不能启动
- 修改weblogic(10.3)域的启动JDK
- 解决weblogic10.3启动后，报 Hibernate 中解析HQL的类 找不到的错误
- weblogic10.3 启动报错 Unrecognized option: -jrockit Error: Could not create the Java Virtual Machine
- weblogic域管理员密码的修改后，服务不能启动了，这样办？
- weblogic 不能启动
- 在Linux/ubuntu环境下Weblogic10.3启动超慢原因分析
- 百炼+日期转换+注意数组不能越界，免得re
- Weblogic92, Weblogic10.3在Linux上启动慢的问题
- 修改weblogic(10.3)域的启动JDK
- Weblogic管理员密码修改后，服务不能启动的解决方法
- weblogic域管理员密码的修改后，服务不能启动了
- 修改Weblogic的JDK路径以解决其不能正常启动的问题
- weblogic启动时提示不能访问JRE
- weblogic启动不能锁定AdminServer.lok的故障处理
- 【转】weblogic域管理员密码的修改后，服务不能启动了，咋办？
- weblogic启动不能锁定AdminServer.lok的故障处理
- weblogic停止不正确导致不能启动
- WebLogic的Admin Server能启动，但Managed Server不能启动
- 修改weblogic(10.3)域的启动JDK