weblogic 10.3不能启动报数组越界

最新推荐文章于 2023-05-10 15:32:31 发布
最新推荐文章于 2023-05-10 15:32:31 发布
阅读量4.2k 收藏
点赞数
分类专栏： weblogic
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/stevendbaguo/article/details/45098535
版权

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

转到底部转到底部

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



单击此项可添加到收藏夹转到底部转到底部

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 -

单击此项可添加到收藏夹转到底部转到底部

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 -
深圳gg
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
Weblogic 10.3.0.0 win32位
01-26
公司需要，非得让安装个这么老版本的，全网找遍了找不到。没办法找客户要了一个。
Weblogic10.3.6.0补丁包（含补丁安装说明）.zip
08-19
Weblogic 10.3.6 2019年7月16日集成补丁包（p29633432_1036_Generic_20190716.zip），补丁名称：MXLE，下载文件中包含补丁安装说明和方法（自用详细步骤）。服务器打补丁前请注意做好备份，若与旧的补丁冲突，需卸载...
linux启动weblogic数组越界,weblogic 10.3不能启动报数组越界
weixin_29332623的博客
05-16 210
In this DocumentAPPLIES TO: Oracle WebLogic Server - Version 10.3.6 to 12.1.2.0.0Information in this document applies to any platform.SYMPTOMSIntermittently, the servers in the cluster fail with java....
linux启动weblogic数组越界,weblogic启动后，抛出大量的java.lang.ArrayIndexOutOfBoundsException异常...
weixin_39566387的博客
05-16 502
在weblogic 12c添加一个server成功后，在将server删除。重新启动AndminServer时抛出大量的 java.lang.ArrayIndexOutOfBoundsException的错误，日志报错如下代码： at com.octetstring.vde.Entry.checkEntryFieldLength(Entry.java:785)at com.octetstrin...
weblogic启动后，抛出大量的java.lang.ArrayIndexOutOfBoundsException异常
p15097962069的博客
07-11 413
weblogic启动后，抛出大量的java.lang.ArrayIndexOutOfBoundsException异常
weblogic 启动报错bea 000386解决方案
gaofenghaha2的博客
06-26 5430
weblogic 启动报错bea 000386 原因：weblogic 用户名/密码验证认证失败 解决方法：第一步：删除server 下对应节点服务boot.properties 文件 目录：/weblogic/Oracle/Middleware/user_projects/domains/base_domain/servers/Server2(对应你的节...
Weblogic10.3优化设置
05-26
Weblogic10.3 优化设置, 在生产环境中优化weblogic,使得服务器性能更佳，减少服务器宕机等引起的风险。
weblogic10.3.6.0 补丁包-编码21Y4
最新发布
04-03
- 重新启动WebLogic Server，使补丁生效。 4. **补丁管理** 对于企业环境中运行的多个WebLogic Server实例，补丁管理至关重要。需要跟踪每个实例的补丁状态，确保所有服务器都打上了必要的补丁，并定期检查Oracle...
Weblogic10.3.0.0 linux32位安装包
01-26
公司需要，非得让安装个这么老版本的，全网找遍了找不到。没办法找客户要了一个。
java.lang.OutOfMemoryError: GC overhead limit exceeded
weixin_34275734的博客
03-10 186
     今天现场weblogic报java.lang.OutOfMemoryError: GC overhead limit exceeded，在metalink查了下，有明白解释，要设置一个JVM參数。只是因为当前weblogic内存设置为4G，所以设置參数的做法事实上并非解决这个问题之道。还是要分析weblogic 内存溢出文件，得出是哪个功能有问题： APPLIES TO...
java.lang.StringIndexOutOfBoundsException: String index out of range: -2147483648 成功解决
笑看风云路的博客
05-10 1291
最近一个小伙伴出现一个从未见过的一个异常，不知道如何解决，于是找我帮忙，看到问题我也是有点懵，怎么会出现这个问题呢，于是找他要了sql脚本，开始找问题的原因。。。
Weblogic 漏洞复现
Knsec
06-03 2634
Weblogic 漏洞复现
java.util.concurrent.CompletionException: java.lang.ArrayIndexOutOfBoundsException异常的原因分析及解决方
zhulj625的博客
12-03 8379
java.util.concurrent.CompletionException: java.lang.ArrayIndexOutOfBoundsException异常的原因分析及解决方案 1.错误日志 java.util.concurrent.CompletionException: java.lang.ArrayIndexOutOfBoundsException at java.util.concurrent.CompletableFuture.encodeThrowable(Compl.
weblogic11g无法启动，报Security:090399
寒江的专栏
09-15 7225
weblogic11g无法启动，报Security:090399 weblogic11g无法启动，报Security:090399 分类： 中间件     安装了oracle的weblogic11g for windows准备研究研究，创建一个domain后
启动weblogic域时报错BEA-000365的解决方法
热门推荐
你爸爸的博客
02-27 1万+
通过生产模式并且选择自己安装的jdk创建了一个域，然后启动这个域时报错，不能进入weblogic控制台解决方法：    1.找到这个域的目录，打开servers目录下的AdminServer，如果没有security文件夹就创建一个。    2.创建一个properties文件，命名为boot，在里面添加以下内容：        username=xxxxx        password=xxx...
WebLogicServer BEA-000386 Weblogic启动报错
Derek_J的博客
04-20 2316
启动weblogic时报错 <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.NumberFormatException: null java.lang.NumberFormatException: null at java.lang....
Weblogic10.3集群配置指南
"Weblogic10.3集群配置手册" 在WebLogic Server中，集群是一种能够提高可用性和可伸缩性的技术。集群允许你将多个服务器实例组合在一起，以作为一个单一的逻辑单元工作，从而实现故障转移、负载均衡和资源共享。本...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值