weblogic 10.3不能启动报数组越界

今天一个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>

intermittently Servers in Cluster Fail with java.lang.IndexOutOfBoundsException:
Index: 0, Size: 0 (文档 ID 1680266.1)		 转到底部

In this Document

Symptoms
  Cause
  Solution
  References

APPLIES TO:

Oracle WebLogic Server - Version 10.3.6 to 12.1.2.0.0

Information in this document applies to any platform.

SYMPTOMS

Intermittently, the servers in the cluster fail with java.lang.IndexOutOfBoundsException:

Index: 0, Size: 0 ####<30-Oct-2013 13:16:50 o‘clock GMT> <Critical> <WebLogicServer>

<vrtstwls101.iggroup.local> <p01> <main> <<WLS Kernel>> <> <> <1383139010950>

<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:90)

at weblogic.rmi.cluster.ClusterableRemoteRef.getPrimaryRef(ClusterableRemoteRef.j ava:155)

at weblogic.rmi.cluster.ClusterableRemoteRef.add(ClusterableRemoteRef.java:474)

at weblogic.rmi.cluster.ClusterableRemoteObject.onBind(ClusterableRemoteObject.java:193)

at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:373)

at weblogic.jndi.internal.ServerNamingNode.bindHere(ServerNamingNode.java:140)

at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:319)

at weblogic.jndi.internal.WLEventContextImpl.bind(WLEventContextImpl.java:277)

at weblogic.cluster.BasicServiceOffer.install(BasicServiceOffer.java:101)

at weblogic.cluster.NodeInfo.install(NodeInfo.java:63)

at weblogic.cluster.TreeManager.install(TreeManager.java:59)

at weblogic.cluster.MemberServices.processOffer(MemberServices.java:64)

at weblogic.cluster.RemoteMemberInfo.processStateDump(RemoteMemberInfo.java:339)

at weblogic.cluster.AnnouncementManager$2.run(AnnouncementManager.java:242)

at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject. java:321)

at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)

at weblogic.cluster.AnnouncementManager.receiveStateDump(AnnouncementManager.java:233)

at weblogic.cluster.MemberManager.getJNDIStateDump(MemberManager.java:268)

at weblogic.cluster.MemberManager.waitForSync(MemberManager.java:222)

at weblogic.cluster.MemberManager.waitToSyncWithCurrentMembers(MemberManager.java :182)

at weblogic.cluster.InboundService.start(InboundService.java:37)

at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)

at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)

at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

>

CAUSE

This issue is caused by starting a clustered Managed Server when there is an IOException on the clients invoking Idempotent remote/EJB methods.This issue has been addressed by Bug
17721032

SOLUTION

Patches are available for Bug 17721032:

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

Fixed in: 12.1.4

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

文档详细信息
 

 
  类型:
  状态:
  上次主更新:
  上次更新:

 
  PROBLEM
  PUBLISHED
  2015-3-27
  2015-3-27

     

 

相关产品
 
     
 

信息中心
 
   

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]
&quot;java.lang.IndexOutOfBoundsException:
Index: 0, Size: 0&quot; 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]

显示更多

     

java.lang.IndexOutOfBoundsException Assertion Error When Getting ReplicaList (文档 ID 1644003.1) 转到底部

In this Document

Symptoms
  Cause
  Solution
  References

APPLIES TO:

Oracle WebLogic Server - Version 9.2.3 to 10.3.5

Oracle WebLogic Server - Version 10.3.6 to 10.3.6

Information in this document applies to any platform.

SYMPTOMS

In WebLogic Server, intermittently the below exception occurs and application won‘t process the request properly. To recover, one needs to restart the whole domain.

<Error> <Kernel> <BEA-000802> <ExecuteRequest failed java.lang.IndexOutOfBoundsException: Index: 0, Size: 0.

java.lang.IndexOutOfBoundsException: Index: 0, Size: 0

at java.util.ArrayList.RangeCheck(ArrayList.java:546)

at java.util.ArrayList.get(ArrayList.java:321)

at weblogic.rmi.cluster.BasicReplicaList.getPrimary(BasicReplicaList.java:91)

at weblogic.rmi.cluster.ClusterableRemoteRef.getPrimaryRef(ClusterableRemoteRef.java:146)

at weblogic.rmi.cluster.ClusterableRemoteRef.add(ClusterableRemoteRef.java:462)

at weblogic.rmi.cluster.ClusterableRemoteObject.onBind(ClusterableRemoteObject.java:193)

at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:371)

at weblogic.jndi.internal.ServerNamingNode.bindHere(ServerNamingNode.java:136)

at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:317)

at weblogic.jndi.internal.WLEventContextImpl.bind(WLEventContextImpl.java:292)

at weblogic.cluster.BasicServiceOffer.install(BasicServiceOffer.java:93)

at weblogic.cluster.NodeInfo.install(NodeInfo.java:63)

at weblogic.cluster.TreeManager.install(TreeManager.java:59)

at weblogic.cluster.MemberServices.processOffer(MemberServices.java:64)

at weblogic.cluster.RemoteMemberInfo.processStateDump(RemoteMemberInfo.java:305)

at weblogic.cluster.AnnouncementManager$2.run(AnnouncementManager.java:242)

at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)

at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)

at weblogic.cluster.AnnouncementManager.receiveStateDump(AnnouncementManager.java:233)

at weblogic.cluster.StateDumpMessage.execute(StateDumpMessage.java:36)

at weblogic.cluster.HTTPExecuteRequest$1.run(HTTPExecuteRequest.java:95)

at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)

at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)

at weblogic.cluster.HTTPExecuteRequest.run(HTTPExecuteRequest.java:92)

at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)

at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

CAUSE

It happens only when global-transactions-protocol for the DataSource is EmulateTwoPhaseCommit. Issue has been fixed via Bug
11796397 - <BEA-000802> <EXECUTEREQUEST FAILED JAVA.LANG.INDEXOUTOFBOUNDSEXCEPTION: INDEX

SOLUTION

Patches are available for Bug 11796397:

PATCH INFORMATION
WLS Version Patch Number
9.2.3 Patch 11796397
9.2.4 Patch 11796397
10.3.3 Patch 11796397
10.3.4 Patch 11796397

Fixed in: 12.1.1 , 10.3.6

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.

REFERENCES

BUG:11796397 -

java.lang.IndexOutOfBoundsException Assertion Error When Getting ReplicaList (文档 ID 1644003.1) 转到底部

In this Document

Symptoms
  Cause
  Solution
  References

APPLIES TO:

Oracle WebLogic Server - Version 9.2.3 to 10.3.5

Oracle WebLogic Server - Version 10.3.6 to 10.3.6

Information in this document applies to any platform.

SYMPTOMS

In WebLogic Server, intermittently the below exception occurs and application won‘t process the request properly. To recover, one needs to restart the whole domain.

<Error> <Kernel> <BEA-000802> <ExecuteRequest failed java.lang.IndexOutOfBoundsException: Index: 0, Size: 0.

java.lang.IndexOutOfBoundsException: Index: 0, Size: 0

at java.util.ArrayList.RangeCheck(ArrayList.java:546)

at java.util.ArrayList.get(ArrayList.java:321)

at weblogic.rmi.cluster.BasicReplicaList.getPrimary(BasicReplicaList.java:91)

at weblogic.rmi.cluster.ClusterableRemoteRef.getPrimaryRef(ClusterableRemoteRef.java:146)

at weblogic.rmi.cluster.ClusterableRemoteRef.add(ClusterableRemoteRef.java:462)

at weblogic.rmi.cluster.ClusterableRemoteObject.onBind(ClusterableRemoteObject.java:193)

at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:371)

at weblogic.jndi.internal.ServerNamingNode.bindHere(ServerNamingNode.java:136)

at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:317)

at weblogic.jndi.internal.WLEventContextImpl.bind(WLEventContextImpl.java:292)

at weblogic.cluster.BasicServiceOffer.install(BasicServiceOffer.java:93)

at weblogic.cluster.NodeInfo.install(NodeInfo.java:63)

at weblogic.cluster.TreeManager.install(TreeManager.java:59)

at weblogic.cluster.MemberServices.processOffer(MemberServices.java:64)

at weblogic.cluster.RemoteMemberInfo.processStateDump(RemoteMemberInfo.java:305)

at weblogic.cluster.AnnouncementManager$2.run(AnnouncementManager.java:242)

at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)

at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)

at weblogic.cluster.AnnouncementManager.receiveStateDump(AnnouncementManager.java:233)

at weblogic.cluster.StateDumpMessage.execute(StateDumpMessage.java:36)

at weblogic.cluster.HTTPExecuteRequest$1.run(HTTPExecuteRequest.java:95)

at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)

at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)

at weblogic.cluster.HTTPExecuteRequest.run(HTTPExecuteRequest.java:92)

at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)

at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

CAUSE

It happens only when global-transactions-protocol for the DataSource is EmulateTwoPhaseCommit. Issue has been fixed via Bug
11796397 - <BEA-000802> <EXECUTEREQUEST FAILED JAVA.LANG.INDEXOUTOFBOUNDSEXCEPTION: INDEX

SOLUTION

Patches are available for Bug 11796397:

PATCH INFORMATION
WLS Version Patch Number
9.2.3 Patch 11796397
9.2.4 Patch 11796397
10.3.3 Patch 11796397
10.3.4 Patch 11796397

Fixed in: 12.1.1 , 10.3.6

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.

REFERENCES

BUG:11796397 -

时间： 2024-10-28 05:15:32

weblogic 10.3不能启动报数组越界的相关文章

XCode6报数组越界错误的问题

今天碰到一个很奇葩的问题, 调试了半天: 错误:"index 0 beyond bounds for empty array",  意思就是说数据源数组为nil, 所以你调用直接取值自然就报错. 我叙述下我的场景: 1. 在UITaleView中创建cell, 数据源dataArray是存在并且数量为10, 然后我是[dataArray objectAtIndexindexPath.row]来取值作为cell的数据, 当然numberOfRowsAtIndexPath里面是返回data

ScriptEngine执行复杂js报数组越界

import javax.script.Invocable; import javax.script.ScriptEngine; import javax.script.ScriptEngineManager; import javax.script.ScriptException; /** * @Author: SimonHu * @Date: 2019/2/12 11:13 * @Description: */ public class Test { public static void m

listview添加头部view问题，数组越界问题

发现在开发中如果用下面的函数,在开发中会遇到一些问题,一个自选基金的管理界面是个listview,点击修改进入下一个界面,然后返回再去点击删除对应行,就会报数组越界, 应该是返回后listview发生了变化,可能和header有关系,换成一个参数的就没有了问题. lv.addHeaderView(headerView, , ); 版权声明:本文为博主原创文章,未经博主允许不得转载.

qRCodeEncoder.Encode 数组越界

从网上下载ThoughtWorks.QRCode.dll解压发现有很多版本,果断选择最新版 生成二维码的代码 private Bitmap GetCode(string code) { QRCodeEncoder qRCodeEncoder = new QRCodeEncoder(); //设置二维码编码格式 qRCodeEncoder.QRCodeEncodeMode = QRCodeEncoder.ENCODE_MODE.BYTE; //设置编码测量度 qRCodeEncoder.QRCod

weblogic启动报错

重启了一次linux服务器后,weblogic启动莫名报错,查看日志发现说部署的项目有个bean类无法加载, 1.然后手动删除 已经部署的项目,先在 domais/servers/AdminServer/upload 删除上传的项目:启动报错 <Jul 13, 2016 10:01:47 AM CST> <Error> <Deployer> <BEA-149605> <Failed to create App/Comp mbeans for AppDe

AIX weblogic 启动报There is not enough buffer space

AIX weblogic 启动报There is not enough buffer space for the requested socket operation 错误 <Sep 19, 2014 10:27:09 AM GMT+08:00> <Error> <Coherence> <BEA-000000> <Oracle Coherence 3.6.0.4 (member=n/a): Error while starting cluster: (

Weblogic 启动报错：java.lang.NoClassDefFoundError

Weblogic 启动报错:java.lang.NoClassDefFoundError  ####<2015-6-17 下午03时30分47秒 CST> <Error> <HTTP> <HDQSDOCMTAPP4> <zonyappserver> <[ACTIVE] ExecuteThread: '15' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS

谨防数组越界！

今天第一次对数组越界问题有了深切的感受,数组越界如果在Release版本中运行也不会报错,如果是Debug版本的话,若直接通过常量数值引用数组下标会被检测到数组越界,若通过变量引用数组下标也是不会被检测到的!!! 测试下面的代码, 1 #include <stdio.h> 2 3 int main(void) 4 { 5 int arr[1][1] = {20}, brr[1] = {1}, y = 5; 6 7 //printf("%d\n", arr[5][0] ==

linux上weblogic 12c域无法启动

域启动报错,解决方法:vi /etc/hosts  本机ip 本机hostname. <2015-4-30 上午10时03分10秒 CST> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: java.lang.ExceptionIn