include error,path:/comp/nav/main?compId=nav_main-15034808049591651 cause:org.springframework.web.util.NestedServletException: Request processing failed; nested exception is com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method findFrontSubNode in the service cn.ce.ebiz.column.service.ColumnContentService. Tried 2 times of the providers [192.168.79.63:20881, 192.168.69.145:20881] (2/16) from the registry BJ-ZW-PAAS-MIDD-ZK-NODE4.online.local:2181 on the consumer 172.20.4.67 using the dubbo version 2.6.0. Last error is: Failed to invoke remote method: findFrontSubNode, provider: dubbo://192.168.79.63:20881/cn.ce.ebiz.column.service.ColumnContentService?anyhost=true&application=front&check=false&default.check=false&default.reference.filter=cecontext&default.retries=1&default.service.filter=cecontext&default.timeout=1000&dispatcher=message&dubbo=2.6.0&generic=false&interface=cn.ce.ebiz.column.service.ColumnContentService&loadbalance=roundrobin&methods=update,updatePostion,findByNav,deletebyNavId,get,deleteSingleColumn,findAll,getBreadcrumbColumnData,getCategoryTree,add,updateMove,findAsyncColumnTree,findByPagination,getMainNavColunmn,delete,findFrontSubNode,updateShowState,updateBefore,findChindren&owner=ebiz&pid=25565®ister.ip=172.20.4.67&remote.timestamp=1527586281078&revision=1.0.0-SNAPSHOT&side=consumer&timeout=1000×tamp=1527621080287, cause: com.alibaba.dubbo.remoting.ExecutionException: class com.alibaba.dubbo.remoting.transport.dispatcher.message.MessageOnlyChannelHandler error when process received event . com.alibaba.dubbo.remoting.ExecutionException: class com.alibaba.dubbo.remoting.transport.dispatcher.message.MessageOnlyChannelHandler error when process received event . at com.alibaba.dubbo.remoting.transport.dispatcher.message.MessageOnlyChannelHandler.received(MessageOnlyChannelHandler.java:44) at com.alibaba.dubbo.remoting.exchange.support.header.HeartbeatHandler.received(HeartbeatHandler.java:88) at com.alibaba.dubbo.remoting.transport.MultiMessageHandler.received(MultiMessageHandler.java:43) at com.alibaba.dubbo.remoting.transport.AbstractPeer.received(AbstractPeer.java:136) at com.alibaba.dubbo.remoting.transport.netty.NettyHandler.messageReceived(NettyHandler.java:90) at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:88) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296) at com.alibaba.dubbo.remoting.transport.netty.NettyCodecAdapter$InternalDecoder.messageReceived(NettyCodecAdapter.java:147) at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108) at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337) at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89) at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:714) at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:949) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1371) at com.alibaba.dubbo.remoting.transport.dispatcher.message.MessageOnlyChannelHandler.received(MessageOnlyChannelHandler.java:42) ... 24 more

E-mail:kehang@asiakh.com

地址:深圳市龙岗区坪地高桥龙腾路22号盛隆兴产业园研发楼7F

传真:0755-84283992(16线)

扫一扫
进入手机版网页

扫一扫
关注微信公众号

COPYRIGHT  ? 2017 深圳市科航科技发展有限公司  粤ICP备12075279号-1  技术支持:中企动力 

电话:0755-84283383      84283992(30线)

服务热线

大玩家娱乐用户登录:0755-84283383

亿万先生mr007欧洲馆:丁国其则同日起辞任集团执行董事及高级副总裁,理由是“为投入更多时间于家庭”。

全球输入设备 解决方案厂家

English

 

亿万先生mr007欧洲馆

 

International Input Devices Solution and Manufacturer

产品详情/ PRODUCTS

在线客服

产品中心

防爆鼠标

产品名称

防爆鼠标

国家防爆认证,防爆标志: Ex ib IIB T6
数量
-
+
产品描述
产品参数

      防护等级高,抗破坏性能强

 

  • SUS304不锈钢成型面板和按键,防水,防尘,防爆,适应在各种恶劣环境下使用;

  • 具有很强的电磁兼容性,抗干扰性和环境适应性,耐高低宽温, 抗振和抗冲击:

  • 3键(左中右)按键设计。

 

 

 


 

 
 
 

防爆标志: Ex ib IIB T6

 

 
 
 

IP65防水激光轨迹球, 内无金属轴承,无燥音操作

应用领域:

 

各种无人监管的机械设备或信息终端,军工控制台、煤矿设备、自动化监视、安防设备、矿井安全检测、工业PC 数控平台、仪器检测设备、自助缴费机、固定的海上平台、工业防爆设备、冶金、电力、交通等和特殊要求工控行业。

机械参数
产品尺寸:
80 X 110 mm (前面板)
按键 :
3按键(左中右键)
按键设计:
SUS304不锈钢椭圆按键
前面板:
SUS304不锈钢表面拉丝
按键行程:
2.0mm
轨迹球直径:
25MM不锈钢球
按键压力:
2-3N
按键预期寿命:
>1000万次
轨迹球预期寿命:
> 500 万次旋转
安装板:
3.0mm厚拉丝铝板,带防爆底盒
安装方式:
嵌入式固定型,后面板带安装孔。
接口
-:
蓝色专用线缆,USB 接口
电气参数
电源:
5V DC+10%,键盘接口
防护水平:
IP65 (前面板), NEMA4
电磁兼容标准 :
EN55022(B)
功率:
≤1.00W(操作时) ≤0.2W(非操作时)
按键开关技术:
碳/镀金(硅胶按键技术)
应用环境
工作温度:
-20oC~+ 70o C
储存温度:
- 30oC~+ 80oC
相对湿度:
30~90%
大气压力:
60~106Kpa.
可靠性
防水防尘级别:
IP65(表面)
防暴标准:
Ex ib IIB T6
平均故障时间:
>50000h
平均修复时间:
< 30min
兼容系统
-:
All Windows, MAC OS9/OSX, Linux/ Unix. BeOS.
包装方式
-:
1PC入内盒, 30PCS内盒入标准的外盒
暂未实现,敬请期待
暂未实现,敬请期待
上一篇
下一篇

服务热线

0755-84283383

传真:0755-84283992(16线)

E-mail:kehang@asiakh.com

地址:深圳市龙岗区坪地高桥龙腾
          路22号盛隆兴产业园研发楼7F

百度 360 搜狗