websphere服务自动重启

[莫忘]

前台通过Ajax访问Spring Mvc，中间执行HbasePool.getTable操作

public void init() {
		Configuration conf = new Configuration();
		conf.set("hbase.zookeeper.quorum", systemConfigService.getSystemParamValue("ZK_QUORUM"));//"10.45.47.152"
		conf.set("hbase.zookeeper.property.clientPort", "2181");
		hbaseConf = HBaseConfiguration.create(conf);
		pool = new HTablePool(hbaseConf, Integer.MAX_VALUE);
	}
if(pool == null){
			init() ;
}
HTableInterface table = pool.getTable(tableName.getBytes());

当代码走到这一步

HTableInterface table = pool.getTable(tableName.getBytes());

，应用就自行重启了
下面是日志信息

7/2/14 11:30:15:892 CST] 00000020 NativeCodeLoa W org.apache.hadoop.util.NativeCodeLoader <clinit> Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
[7/2/14 11:30:15:965 CST] 00000020 SystemOut     O 2014-07-02 11:30:15 [ WebContainer : 0:333659 ] - [ INFO ] Initiating client connection, connectString=136.6.204.48:2181,136.6.204.15:2181,136.6.204.50:2181 sessionTimeout=180000 watcher=hconnection
[7/2/14 11:30:15:985 CST] 00000020 RecoverableZo I org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper <init> The identifier of this process is 8260@crmqdcx01
[7/2/14 11:30:15:992 CST] 00000023 SystemOut     O 2014-07-02 11:30:15 [ WebContainer : 0-SendThread(master5:2181):333685 ] - [ WARN ] SASL configuration failed: javax.security.auth.login.LoginException: No JAAS configuration section named 'Client' was found in specified JAAS configuration file: '/websphere/IBM/AppServer/profiles/AppSrv01/properties/wsjaas.conf'. Will continue connection to Zookeeper server without SASL authentication, if Zookeeper server allows it.
[7/2/14 11:30:15:992 CST] 00000023 SystemOut     O 2014-07-02 11:30:15 [ WebContainer : 0-SendThread(master5:2181):333686 ] - [ INFO ] Opening socket connection to server master5/136.6.204.15:2181
[7/2/14 11:30:15:996 CST] 00000023 SystemOut     O 2014-07-02 11:30:15 [ WebContainer : 0-SendThread(master5:2181):333690 ] - [ INFO ] Socket connection established to master5/136.6.204.15:2181, initiating session
[7/2/14 11:30:15:996 CST] 00000023 SystemOut     O 2014-07-02 11:30:15 [ WebContainer : 0-SendThread(master5:2181):333690 ] - [ DEBUG ] Session establishment request sent on master5/136.6.204.15:2181
[7/2/14 11:30:16:001 CST] 00000023 SystemOut     O 2014-07-02 11:30:16 [ WebContainer : 0-SendThread(master5:2181):333695 ] - [ INFO ] Session establishment complete on server master5/136.6.204.15:2181, sessionid = 0x246d7352a1838be, negotiated timeout = 120000
[7/2/14 11:30:16:004 CST] 00000023 SystemOut     O 2014-07-02 11:30:16 [ WebContainer : 0-SendThread(master5:2181):333698 ] - [ DEBUG ] Reading reply sessionid:0x246d7352a1838be, packet:: clientPath:null serverPath:null finished:false header:: 1,3  replyHeader:: 1,38654890489,0  request:: '/hbase/hbaseid,F  response:: s{8589935416,34359738589,1401970703773,1403769891314,6,0,0,0,53,0,8589935416} 
[7/2/14 11:30:16:006 CST] 00000023 SystemOut     O 2014-07-02 11:30:16 [ WebContainer : 0-SendThread(master5:2181):333700 ] - [ DEBUG ] Reading reply sessionid:0x246d7352a1838be, packet:: clientPath:null serverPath:null finished:false header:: 2,4  replyHeader:: 2,38654890489,0  request:: '/hbase/hbaseid,F  response:: #ffffffff000c38323433406d61737465723537643363383463352d656161382d343331342d616162622d356166613161653133653666,s{8589935416,34359738589,1401970703773,1403769891314,6,0,0,0,53,0,8589935416} 
[7/2/14 11:30:16:012 CST] 00000023 SystemOut     O 2014-07-02 11:30:16 [ WebContainer : 0-SendThread(master5:2181):333706 ] - [ DEBUG ] Reading reply sessionid:0x246d7352a1838be, packet:: clientPath:null serverPath:null finished:false header:: 3,3  replyHeader:: 3,38654890489,0  request:: '/hbase/master,T  response:: s{34359738587,34359738587,1403769889303,1403769889303,0,0,0,164055034847297542,46,0,34359738587} 
[7/2/14 11:30:16:015 CST] 00000023 SystemOut     O 2014-07-02 11:30:16 [ WebContainer : 0-SendThread(master5:2181):333709 ] - [ DEBUG ] Reading reply sessionid:0x246d7352a1838be, packet:: clientPath:null serverPath:null finished:false header:: 4,4  replyHeader:: 4,38654890489,0  request:: '/hbase/master,T  response:: #ffffffff000c38323433406d617374657235006d6173746572352c36303030302c31343033373639383737383336,s{34359738587,34359738587,1403769889303,1403769889303,0,0,0,164055034847297542,46,0,34359738587} 
[7/2/14 11:30:16:018 CST] 00000023 SystemOut     O 2014-07-02 11:30:16 [ WebContainer : 0-SendThread(master5:2181):333712 ] - [ DEBUG ] Reading reply sessionid:0x246d7352a1838be, packet:: clientPath:null serverPath:null finished:false header:: 5,3  replyHeader:: 5,38654890489,0  request:: '/hbase/root-region-server,T  response:: s{34359739060,34359739060,1403769896570,1403769896570,0,0,0,0,46,0,34359739060} 
[7/2/14 11:30:16:020 CST] 00000023 SystemOut     O 2014-07-02 11:30:16 [ WebContainer : 0-SendThread(master5:2181):333714 ] - [ DEBUG ] Reading reply sessionid:0x246d7352a1838be, packet:: clientPath:null serverPath:null finished:false header:: 6,4  replyHeader:: 6,38654890489,0  request:: '/hbase/root-region-server,T  response:: #ffffffff000d35353439406861646f6f7033316861646f6f7033312c36303032302c31343033373639383635363233,s{34359739060,34359739060,1403769896570,1403769896570,0,0,0,0,46,0,34359739060} 
[7/2/14 11:30:16:064 CST] 00000023 SystemOut     O 2014-07-02 11:30:16 [ WebContainer : 0-SendThread(master5:2181):333758 ] - [ DEBUG ] Reading reply sessionid:0x246d7352a1838be, packet:: clientPath:null serverPath:null finished:false header:: 7,3  replyHeader:: 7,38654890489,0  request:: '/hbase,F  response:: s{4294968882,4294968882,1401964961182,1401964961182,0,83,0,0,0,13,34359739060} 
[7/2/14 11:30:16:066 CST] 00000023 SystemOut     O 2014-07-02 11:30:16 [ WebContainer : 0-SendThread(master5:2181):333760 ] - [ DEBUG ] Reading reply sessionid:0x246d7352a1838be, packet:: clientPath:null serverPath:null finished:false header:: 8,4  replyHeader:: 8,38654890489,0  request:: '/hbase/root-region-server,T  response:: #ffffffff000d35353439406861646f6f7033316861646f6f7033312c36303032302c31343033373639383635363233,s{34359739060,34359739060,1403769896570,1403769896570,0,0,0,0,46,0,34359739060} 

[FeelTouch Labs]

单纯从代码和日志上都没看出什么问题，执行到 HTableInterface table = pool.getTable(tableName.getBytes()); 引起服务重启的一种可能是内存不足导致应用无法访问，服务重启；另外检查下WAS脚本的配置

[FeelTouch Labs]

引用 3 楼 cycao313 的回复:

[quote=引用 1 楼 FENGQIYUNRAN 的回复:] 单纯从代码和日志上都没看出什么问题，执行到 HTableInterface table = pool.getTable(tableName.getBytes()); 引起服务重启的一种可能是内存不足导致应用无法访问，服务重启；另外检查下WAS脚本的配置

单独写了Hbase连接操作的代码打成Jar包放到Was的应用服务器上运行，是可以操作成功了。问题应该是出在Was上，具体也不知道怎么检查[/quote] 嗯，从内部工作的机制着手去分析问题，再去总结，这是成长的过程

[莫忘]

引用 1 楼 FENGQIYUNRAN 的回复:

单纯从代码和日志上都没看出什么问题，执行到 HTableInterface table = pool.getTable(tableName.getBytes()); 引起服务重启的一种可能是内存不足导致应用无法访问，服务重启；另外检查下WAS脚本的配置

请问是检查Was的什么脚本？服务内存已经加到1024-2048M了

[莫忘]

引用 1 楼 FENGQIYUNRAN 的回复:

单纯从代码和日志上都没看出什么问题，执行到 HTableInterface table = pool.getTable(tableName.getBytes()); 引起服务重启的一种可能是内存不足导致应用无法访问，服务重启；另外检查下WAS脚本的配置

单独写了Hbase连接操作的代码打成Jar包放到Was的应用服务器上运行，是可以操作成功了。问题应该是出在Was上，具体也不知道怎么检查

[莫忘]

引用 4 楼 FENGQIYUNRAN 的回复:

[quote=引用 3 楼 cycao313 的回复:] [quote=引用 1 楼 FENGQIYUNRAN 的回复:] 单纯从代码和日志上都没看出什么问题，执行到 HTableInterface table = pool.getTable(tableName.getBytes()); 引起服务重启的一种可能是内存不足导致应用无法访问，服务重启；另外检查下WAS脚本的配置

单独写了Hbase连接操作的代码打成Jar包放到Was的应用服务器上运行，是可以操作成功了。问题应该是出在Was上，具体也不知道怎么检查[/quote] 嗯，从内部工作的机制着手去分析问题，再去总结，这是成长的过程[/quote] 没人回答，结贴了