Skip to end of metadata
Go to start of metadata


Home  ||  Download  ||  User Guide  ||  Developer Guide  ||  Administrator Guide  ||  Training  ||  FAQ  ||  Release Notes  ||  Roadmap  ||  Community

English | 中文

Overview

(+) (#)

Serving 2,000+ services with 3,000,000,000+ invocations everyday, Dubbo becomes the key part of Alibaba's SOA solution and has been deployed to the whole alibaba.com family:

For more, see: Known Users

So, What is Dubbo?

Dubbo [] is a distributed service framework empowers applications with service import/export capability with high performance RPC.

It's composed of three kernel parts:

  • Remoting: a network communication framework provides sync-over-async and request-response messaging.
  • Clustering: a remote procedure call abstraction with load-balancing/failover/clustering capabilities.
  • Registry: a service directory framework for service registration and service event publish/subscription

Dubbo can:

  • Integrate different types of RPC solutions(RMI/Hessian...) with unified behavior by the abstraction layer of RPC
  • Support out-of-box, plug-able load balancing and fault tolerance strategies.
  • Achieve graceful service upgrade/downgrade with service registry.

Quick Start

(+) (#)

Dubbo also support usage WITHOUT spring, 
but it's more painful and not recommended. Please refer to: API Config (+)

Service Provider

(#)

Define the service interface:

DemoService.java

Provide the service implementation

DemoServiceImpl.java

Setup the spring configuration

provider.xml

Kick it off with following java code

Provider.java

Congrats! The DemoService now is exported by dubbo and waiting for incoming requests at port 20880.

Service Consumer

(#)

Setup the spring XML

consumer.xml

Client side java code.

Consumer.java

For more, please click here for a complete user guide~~

Support


Mailing List:

QQ Group: 222162989

Follow Us: @dubbo

Blog Article

Issue Tracking (Register Account)

Continuous Integration

Code Review

More...

News


This version only hot fix bugs

Dubbo 2.4.10 Download:

Download#2.4.10 (2013-03-17)

Dubbo 2.4.10 Release Notes:

Release Notes#2.4.10 (2013-03-17)

Dubbo 2.4.9 released on 2012-11-07

This version only hot fix bugs

Dubbo 2.4.9 Download:

Download#2.4.9 (2012-11-07)

Dubbo 2.4.9 Release Notes:

Release Notes#2.4.9 (2012-11-07)

Dubbo 2.5.3 released on 2012-10-24

This version only hot fix bugs。

该版本重点增强了 codec,避免了 encode/decode 时不必要的数据复制。

Dubbo 2.5.3 Download:

Download#2.5.3 (2012-10-24)

Dubbo 2.5.3 Release Notes:

Release Notes#2.5.3 (2012-10-24)

More...

Changes


Recently Updated

More...

Comments


Recently Updated

Add Comment

Labels:
dubbo dubbo Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. 一月 19, 2012

    Anonymous

    how to support other language?

    1. 一月 25, 2012

      The C++ version is under development.

      1. 二月 23, 2012

        Anonymous

        if we have distributed transaction requirement,how to solve it?

      2. 十二月 27, 2013

        请问一下,我想用dubbo集成一个服务,多个web项目做client,集中调用这个service服务;有个问题不太明白,做完后service服务是打包启动就可以了,但在开始过程中怎么在不打包的情况下debug程序呢?

  2. 二月 11, 2012

    Anonymous

    看到在服务注册的时候,唯一标识用了interface的名字。 java这样做还好,其它语言不一定适用,是否可以替换成可定义的名字做标识,每种实现可以用不同的接口命名方式来做适应?

    1. 二月 15, 2012

      多谢你的建议,我们会在后续版本考虑加上独立的标识,现在用interface做标识是为了简化配置。

      1. 二月 20, 2012

        Anonymous

        thrift协议啥时候能支持呢? 如果我自己实现, 如何贡献代码?

        1. 二月 20, 2012

          Thrift已经做了集成,正在测试验证,如果你想贡献代码,可以将实现代码发邮件到Dubbo的邮件列表,谢谢你的支持。

          1. 二月 24, 2012

            Anonymous

            Thrift生成的接口属于内部类,在加载类的时候需要 $Iface ,但是$在AbstractConfig.checkPathName这个方法内被过滤掉了

            1. 二月 28, 2012

              已发布2.0.13版本,使path支持$符。

  3. 三月 09, 2012

    Anonymous

    That's a smart way of thniking about it.

    1. 十一月 14, 2012

      Anonymous

      This posting koncked my socks off

    2. 十一月 15, 2012

      Anonymous

      b9WUH4 <a href="http://jjoirtdmzime.com/">jjoirtdmzime</a>

  4. 三月 15, 2012

    Anonymous

    2.1.0和2.1.1在使用zookeeper(3.4.3)作为注册中心时,在不断重复运行示例中的Consumer情况下还是偶尔会出现订阅异常错误。

    1. 三月 21, 2012

      能不能把异常栈信息给到邮件列表。

      1. 六月 15, 2012

        Anonymous

        我也遇到这种情况,在多线程情况下会出现下面的异常:

        1. 三月 24, 2012

          感谢你的发现,已在2.1.2版本解决,JIRA记录:DUBBO-305

  5. 三月 21, 2012

    Anonymous

    RegistryDirectory类出现过并发异常吗?你的并发处理有些问题。

    1. 三月 21, 2012

      能不能说详细一点。RegistryDirectory中的集合属性变化时,都是先创建一个新集合,然后替换引用,没有并发remove或add行为,相当于copy-on-write,Java内存模型是确保替换引用是原子的。

      1. 三月 22, 2012

        Anonymous

        看到你的notify方法加了synchronized关键字,也就是说这个方法会被并发的执行,这样就有可能导致后触发的更新事件先被执行,从而导致本地缓存的数据并不是最新的。
        非公平锁更容易导致这个问题。
        zookeeper的callback是串行化的,就是为了解决这个问题。

        "Java内存模型是确保替换引用是原子的",其实你的被并发访问的map都加了volatile关键字..

        1. 三月 23, 2012

          事件的顺序是由触发方保证的,也就是注册中心实现需保证通知的顺序,比如:单线程通知,或用队列串行化,或者带版本号对比丢弃旧数据,这是契约的一部分。
          加synchronized只是为了防御,万一哪个注册中心实现的有BUG,也不至于因并发创建或销毁Invoker连接而导致出错,最坏也只是看到旧数据。
          理论上不应让synchronized起作用,如果synchronized起作用,确实会有非公平锁引起的顺序问题,因为先等待锁的不一定先拿到锁。
          加volatile是为了保证可见性,通知的数据更新后,其它线程能立即看到,避免多核下CPU缓存以及线程栈和堆引用同步等引起的可见性问题。

          1. 三月 23, 2012

            Anonymous

            既然已经用了synchronized关键字,又为什么要用ConcurrentHashMap?

            “加volatile是为了保证可见性,通知的数据更新后,其它线程能立即看到,避免多核下CPU缓存以及线程栈和堆引用同步等引起的可见性问题。”那“Java内存模型是确保替换引用是原子的”还成立吗?

            看了你们的代码,我还真不敢随便用这个框架!你们的负载均衡策略也相当简陋!希望你们能更加深入,更加专业!

            1. 三月 25, 2012

              多谢你细致的发现,线程栈内的ConcurrentHashMap改成HashMap,会尽快处理掉。
              框架一直在演进,这么多人在开发,加代码,总会有些细节没注意到,如果压测下不是热点,可能就被忽视了。

              原子性和可见性并不冲突:
              原子性是指不会看到脏数据,在32位机上,long或double类型,写完高位,低位还没写入,中间就可能被用户读取了,
              所以对long或double类型的变量赋值就不是原子性的,需要同步保证原子性,而对象地址的操作是原子性的。参见:JLS 17.7
              可见性是指CPU不会在L1,L2进行缓存,总是同步到主存,volatile在JIT编译后在x86处理器下实际汇编指令为lock,如:0x04b5ce32: lock addl $0x0,(%esp);

              负载均衡策略,是一个正交分解后的扩展点,它只关心选择方式,至于其它的像容错,降级,路由等,都由其它扩展点实现,这样就可以进行组合使用,也能保持接口的职责单一,越复杂越容易出错,以最简单的实现达到目的,也是我们一贯的做法,坚持KISS法则。

            2. 三月 24, 2012

              已在2.1.2版本改为HashMap,参见:RegistryDirectory-2.1.2.java

  6. 三月 23, 2012

    Anonymous

    其实加synchronized关键字,从应用角度来说并无伤大雅。
    但是ConcurrentHashMap建议尽早改成HashMap吧,并发读取性能能提高一倍,而这每次方法调用都会跑的代码!

    1. 三月 23, 2012

      嗯,我们会尽快处理,但这种提升在一次RPC调用中微乎其微,几乎可以忽略。

  7. 三月 29, 2012

    Anonymous

    你好,不知是不是我使用的问题,在已经启动tomcat的情况下,我修改代码,因为tomcat的自动重编译,导致了dubbo的重新发布。而在发布时因为端口被占用,导致了项目down掉。

    1. 三月 29, 2012

      Anonymous

      额,找到原因了,是tomcat的设置问题,server.xml里有个reloadable="true",一旦设置了在使用dubbo的时候同时编写代码就有问题,设为false才可以。

  8. 四月 03, 2012

    Anonymous

    遇到个问题,是关于服务治理方面的,准确的说应该是:服务依赖关系的管理

    举例:场景一,如图

    1. 有两台service服务器server1、server2
    2. 有4个team分别开发维护A、B、C、D四个系统(或组件)
    3. 其中A中的consumer需要依赖于C提供的service,D中的consumer需要依赖于B提供的service(或者是其他的依赖关系)
    4. 使用zookeeper注册中心

    问题一: consumer向zookeeper注册订阅URL时,是要依赖provider的URL的, 由于这种强依赖性, 同时启动server1和server2上的系统,系统是无法启动的
    问题二:即使可以所有的系统(应用)可以分别启动,但是对于我们来说几十个应用,几百个服务,这样的维护成本太高了,包括团队或组员之间的协调、沟通成本更高。

    看到你们网站上的关于服务治理方面的资料处于--整理中的状态, 不知道你们在实际的开发、生产环境中,是如何管理服务的(你们的1000+的服务)?

    谢谢

    1. 四月 05, 2012

      如果有双向或循环依赖,可以关闭启动时检查,这样当服务提供者不存在时也能启动,参见:Check On Startup
      依赖关系的展示,是可以通过服务订阅数据分析出来的,开源的simple-monitor也能以文本树的方式展示一部分依赖关系。
      等我们将公司内部的服务治理中心,进行整理剥离后,会考虑将其开源,预计在第二季度内完成。

      1. 四月 05, 2012

        Anonymous

        非常感谢您的回复,不好意思,指南看的不仔细,期待你们的服务治理中心--开源

  9. 四月 17, 2012

    Anonymous

    Hi,梁飞,zookeeper注册中心不太稳定啊!
    这么多注册中心,还不如集中搞定一个可以稳定使用的。
    我们使用中遇到以下问题:
    1.在修改服务端,重新启动服务端,注册订阅信息,提示该订阅信息已经存在了
    2.服务端修改没有及时更新到客户端

    1. 五月 17, 2012

      2.2.0版本zookeeper的集成已改为使用zkclient,健状性上有所提升,你可以试用。
      https://github.com/sgroschupf/zkclient

  10. 五月 04, 2012

    Anonymous

    可以支持纯粹的socket吗,或者要怎么去扩展他,因为我的客户端是c语言写的系统。

    1. 九月 07, 2012

      Anonymous

      你的纯socket通信通过dubbo实现了吗?

  11. 六月 15, 2012

    Anonymous

    试用redis做为注册中心,本地注册服务正常,远程注册的服务可以注册成功,客户端调用的时候就会抛异常

    1. 五月 14, 2012

      Anonymous

      补充下,windows可以,linux抛上面的异常

      1. 十一月 15, 2012

        Anonymous

        Great article, thank you again for witirng.

      2. 十一月 16, 2012

        Anonymous

        tTqEFy <a href="http://ishzfgcwrlrw.com/">ishzfgcwrlrw</a>

      3. 十一月 17, 2012

        Anonymous

        km2OuF <a href="http://sqmhjoainnkd.com/">sqmhjoainnkd</a>

      4. 十一月 18, 2012

        Anonymous

        UZyHSU , [url=http://iycntonvtnuo.com/]iycntonvtnuo[/url], [link=http://nqnzfqebhazg.com/]nqnzfqebhazg[/link], http://gfymvomqoxmo.com/

  12. 六月 15, 2012

    Anonymous

    consumer引用远程对象报出来的,consumer端首先是连接9090注册中心没问题,接着连接20880服务就报上没错误。请大家帮忙看看是怎么回事

    1. 五月 20, 2012

      原因:

      这个异常信息的含义是在“接收消息”的“IO线程”上又发起了“发送信息”的请求。因为“发送信息”本身需要IO线程,而IO线程正在“接收消息”的途中等待发送完成。因netty有在await之前检测对比当前线程,所以只是报异常,并不会真正发生死锁。

      排查:

      用的Dubbo哪个版本?有没有设置过<dubbo:protocol dispatcher="" />?如果有设置,可能引发此问题。参见:http://code.alibabatech.com/wiki/display/dubbo/User+Guide#UserGuide-ThreadModel

      比如:将dispatcher设置为连接事件不派发到线程池,而是直接在IO线程上执行,那么在ChannelHandler的connected()和disconnected()事件中不能再直接发起send操作,否则死锁,必须另启线程执行send操作。

      已记录,我们会跟进排查:http://code.alibabatech.com/jira/browse/DUBBO-404

  13. 五月 21, 2012

    Anonymous

    非常感谢,问题已经解决。
    加dispatcher用线程池就好了。

  14. 五月 30, 2012

    Anonymous

    请问dubbo的运行环境是不是必须最低java 1.6?
    因为看里面的一些代码特性,都是java6的,包括最近的zkClient,也是java6实现,但我看说明,是说环境要求 jdk 1.5+?

    1. 五月 30, 2012

      部分功能是需要1.6支持的,比如:script路由,grizzly传输,zookeeper注册中心等,但dubbo本身是用jdk1.5编译的,只要不用到这些功能,就可以用jdk1.5。

  15. 六月 15, 2012

    Anonymous

    dubbo 2.1.8 simply-registry+自己的服务,开发过程经常registry报OOM,请问需要什么优化么?我用的是自带的start.bat
    java -Xms64m -Xmx512m -Xss256k -XX:MaxPermSize=128M -classpath ..\conf;%LIB_JARS% com.alibaba.dubbo.container.Main

    1. 五月 30, 2012

      simply-registry 有BUG,没有去修复,请不要使用。

      1. 五月 30, 2012

        Anonymous

        那如果环境为java 1.5话,是不是只能是redis作为registry的方案了?

        1. 五月 31, 2012

          你可以考虑自己拿zkclient的源代码用jdk1.5重新编译一次,在自己的仓库重发一份。

          1. 六月 01, 2012

            Anonymous

            请问alibaba内部使用的registry是?

            1. 六月 12, 2012

              alibaba内部使用的是一个基于mysql实现的配置中心,dubbo将其适配为registry。

    2. 七月 03, 2012

      SimpleRegistry的BUG已在2.3.2版本修复。

  16. 六月 15, 2012

    Anonymous

    To 梁飞:

    在:
    ExtensionLoader.getExtensionLoader(ExtensionFactory.class).getAdaptiveExtension()报错了
    ExtensionFactory接口中没有Adaptive注解方法。
    容器必须怎么启动呢?

    1. 六月 03, 2012

      Anonymous

      程序版本是2.20
      Main.java
      private static final ExtensionLoader<Container> loader = ExtensionLoader.getExtensionLoader(Container.class);

    2. 六月 12, 2012

      你有没有改变dubbo的jar包的内容?不能改变dubbo的jar包内的META-INF下的配置文件,否则扩展点的加载会问题。

  17. 六月 15, 2012

    Anonymous

    咨询2个问题:
    1、测试期间发现这个问题,不理解情况是怎么发生的,测试的压力不大,就是普通的web系统点点,是否需要进行一些调优配置?

    1. 六月 12, 2012

      问题一:
      Thread pool is EXHAUSTED! 表示线程池的线程全部被占用,如果每次请求都把线程卡住,比如全堵在数据库连接上,就算你只有一个并发,也能把线程池耗光,不管线程池设多大也没用。
      你可以用:jstack PID > jstack.log,把线程栈dump下来,看所有线程都阻在哪个方法上,这个方法就是有问题的地方,比如阻个oracle-driver的某个方法上,就检测一下oracle的连接数限制,最大执行语句限制等。

      问题二:
      可能是注册中心连接已关闭,又有新的unregister请求发起,导致unregister失败,但此问题不会影响运行。

  18. 六月 10, 2012

    Anonymous

    你好:

    我用dubbo 2.2遇到了一个问题,就是用2台电脑进行调用接口的时候就是连接不上注册中心。在同一台电脑上就可以调用接口。

    我想知道用multicast 注册中心,2台电脑该如何设置?

    后来我采用了Zookeeper 3.3.3 注册中心。在一台电脑上有用,当用2台电脑调用接口(就是一台电脑做服务提供者,一台电脑做消费者),消费者就是连接不上另一台电脑的注册中心。请问是什么原因?

    1. 六月 10, 2012

      Anonymous

      用了Zookeeper 3.3.3消费者连接上了注册中心 可DemoService demoService = (DemoService)context.getBean("demoService"); 这句获得不了。

      1. 六月 11, 2012

        Anonymous

        可以尝试先在消费者机器上telnet 提供者机器ip:zookeeper端口,看看是否有通,
        ->没通的话,检查看看是否提供者机器有防火墙之类的东西,
        ->有通的话,则看看提供者和消费者dubbo配置的registry端口是否有错误,如果都对,我看你需要贴上异常日志
        ->第3个情况,就是提供者是否有多个ip,假设提供者有192.168.0.1和10.2.3.1两个ip,而消费者机器ip是192.168.0.2,而dubbo服务的监听ip是10.2.3.1的话(看看dubbo export url的ip端口信息),这样消费者机器是连不到提供者的

        1. 六月 12, 2012

          这位已经回答的很清楚。

    2. 六月 12, 2012

      如果你的网络支持广播包,使用multicast注册中心,在机器上不需要做任何设置,
      也不用搭建任何中间节点,只要两个人填的multicast地址一样,就能互相发现,
      广播地址段:224.0.0.0 - 239.255.255.255,在这个段内任选一个IP都可以。

  19. 六月 15, 2012

    Anonymous

    这个问题很是郁闷,spring对rpc远程对象进行代理时报错。proxy1是有构造函数的,但是spring选择用cglib代理时。cglib找不到或者参数传递有问题。
    首先proxy1本身就是一个代理对象。
    spring源码Cglib2AopProxy中setConstructorArguments方法没有被调用过。

    始终是执行else里面的分支。这样就会报Superclass has no null constructors but no arguments were given
    各位请帮助看看。。!!!

  20. 六月 15, 2012

    Anonymous

    关于dubbo-monitor-simple-2.3.0使用问题
    修改了dubbo.properties配置如下

    provider接口都有调用过多次,但是在网页上Services->显示Statistics (0) Charts (0),没有出现报表图,是不是还需要注意什么配置

    1. 六月 16, 2012

      Anonymous

      我这么配置也没出现报表图。。。。

    2. 六月 18, 2012

      Statistics是1分钟汇报一次,Charts是5分钟生成一次,要等一会。

    3. 九月 10, 2012

      Anonymous

      你在provider和consumer的配置文件里配置了monitor节点没?

  21. 六月 28, 2012

    Anonymous

    1. 六月 23, 2012

      Anonymous

      用的dubbo最新版本2.30

    2. 六月 24, 2012

      上面已经答过一次,simply-registry 有BUG,没有去修复,请不要使用。

    3. 七月 03, 2012

      SimpleRegistry的BUG已在2.3.2版本修复。

  22. 六月 26, 2012

    Anonymous

    最新的版本的 dubbo是否支持RESTful服务,若不支持,用 dubbo的 spi能扩展么

  23. 六月 26, 2012

    Anonymous

    http://code.alibabatech.com/wiki/display/dubbo/User+Guide#UserGuide-RouterRule
    condition://0.0.0.0/com.foo.BarService?category=routers&dynamic=false&rule=

    “0.0.0.0
    表示对所有IP地址生效,如果只想对某个IP的生效,请填入具体IP,必填。”

    其中的 对所有IP地址生效指的是 的所有是指 所有提供者么?

    1. 六月 28, 2012

      路由规则只对消费者生效。

  24. 七月 24, 2012

    Anonymous

    用loadrunner并发的时候会报注册失败,请问下这个新版本有没有考虑解决?目前我只一次测试达到了50并发。

    1. 七月 30, 2012

      请给出完整的异常信息栈。

  25. 九月 26, 2012

    Anonymous

    请问这个No such extension com.alibaba.dubbo.common.threadpool.ThreadPool by name limited是什么意思

    1. 八月 02, 2012

      2.4.0把线程池的缺省类型从fixed改成了limited,参见:Thread Model
      这个limited线程池是打包在dubbo的jar内的,理论上不会出现找不到,请问你使用的dubbo版本是?

      1. 九月 26, 2012

        Anonymous

        我使用的是2.4.2,也出现了同样的问题。程序代码非常简单,配置文件如下:

        程序代码如下:

        错误堆栈信息如下:

      2. 八月 03, 2012

        Anonymous

        刚刚把dubbo版本切换成2.3.7,问题就解决了。
        看来升级到2.4.0以上版本,还是得搞清楚情况,弄对配置后再说。

        1. 九月 26, 2012

          Maven中央仓库中的2.4.2版本有问题,因为maven中央仓库不允许替换,所以没有改掉,阿里仓库内的2.4.2版本可用,但建议用2.4.6版本。

  26. 八月 03, 2012

    Anonymous

    2.4.2版本的,你们的例子能不能搞个完整的工程出来,你们讲的例子还真不好学习

    1. 九月 26, 2012

      可以看下:Administrator Guide-zh,里面打包好的工程可以直接运行,另外,源代码根目录下的README文件,有详细描述如何从源码运行。

      1. 十一月 20, 2012

        Anonymous

        梁飞,你好,示例运行完成正常,而且按照示例自行实现也可以正常执行

        问题出现一个:使用Eclipse的export功能生成的jar中如果把配置文件一起归档,系统无法识别,使用ant脚本可以正常识别,想必是解析的地方有部分兼容问题.

        从示例看,实现的是dubbo协议的,如果改成别的使用接口实现的协议,例如hessian等,都相近,容易处理

        如果我们使用HTTP协议的servlet呢?

        按照说明配置了服务提供者,并配置了ZooKeeper作为注册中心,启动Web服务,发现ZooKeeper的终端没有反应,我的理解是服务提供者并未注册到ZooKeeper上

        其次即使服务提供者注册成功,服务消费者也不可能使用像使用其他协议那样获取一个Interface来实现,想必需要HttpClient等方式实现,这时HTTP请求的URL等如何操作就不是很清楚了

        总体感觉HTTP协议和其他协议差异相对较大,是否可以提供HTTP协议的简单示例或者操作手册,以便更好地学习.

  27. 九月 26, 2012

    Anonymous

    在客户程序连接服务程序时报了如下错误

    1. 九月 26, 2012

      javassist的版本冲突,NoClassDefFoundError: javassist/ClassPath,
      请使用3.15.0-GA以上版本,或配置成jdk字节码生成:

  28. 八月 21, 2012

    Anonymous

    在控制台和 service xml文件中都配置了 XXXService 的属性A,但是 两种方式配置的 属性A的值是不同的 比如 A=executes属性。
    之后重启 包含XXXService的provider,问题来了:

    第一种情况:XXXService服务中的 A配置值会覆盖控制台中配置的值么?
    第二种情况:重启 注册中心,之前在 控制台中配置的值会失效么

    1. 八月 24, 2012

      1. 控制台配置的值优先。
      2. 配置的值是持久存储的,不会失效。

  29. 九月 26, 2012

    Anonymous

    问题如下:
    注意3@@@@
    《1》使用.getBean("userService")的结果

    我在仔细研究下吧,dubbo的proxy中不包含方法参数名,是不是合理呢?(期待您的回复:cnsdl@126.com/17830095)

    1. 九月 26, 2012

      proxy在生在字节码时,会判断该方法有没有重载,如果没有,就只生成对比方法名的条件字节码,否则增加生成对比参数类型的字节码。

      1. 十月 19, 2012

        Anonymous

        其实很希望在编译为 class时除了参数类型外,还能记住 方法的参数名称;很悲剧,一个class 编译时把方法的参数名记下了,不过放到了 类似注释之类的地方,所以韩能拿到;interface就无能为力了,其实 java 6 查点支持编译参数名称,发布之前取消了。java7 也没有,之后的版本也够呛,有个开源的工具曾游说过 sun,但是没被采纳。

        1. 十月 19, 2012

          Anonymous

          Paranamer

  30. 九月 06, 2012

    Anonymous

    未来考不考虑支持 .NET 平台呢?

    1. 九月 18, 2012

      阿里几乎不使用.NET,没有考虑支持 .NET 平台的计划。

  31. 十月 19, 2012

    Anonymous

    梁 飞、李 鼎,您们好!
    我现在需要在dubbo 服务提供者提供安全,就是说 服务消费者调用服务提供者端的 某个分布式方法,在服务提供者端要验证用户的身份。
    我知道dubbo提供了 黑白名单的支持,但是只有黑白名单的 IP限制是不够的。我们需要确定调用者的身份,(一个服务只允许若干人可访问,当然一个人可以访问不同的多个服务)

    我现在计划把 Spring Security和dubbo做集成来实现我的想法,我可以在为服务提供者制定一个安全的数据映射(服务和认证主体(比如一个人)),让Spring 的AOP处理服务调用时拦截,进入安全处理流程(MethodSecurityInterceptor),可以拿到 当前 服务方法允许那些人访问,但是拿不到当前的用户?若有当前的用户以及当前服务需要的用户列表便可以做出判断。

    1、建议是不是dubbo能提供API ,在消费者端调用时设置 一些自定义属性(比如我需要的用户的身份),另一个API是在服务提供者端能提取设置的属性,(缺点:这样consumer 和provider有少许耦合)
    2、若第1点不合理,请给我点建议,我就想在服务提供者那里拿到 调用者的身份, 我该怎么做
    3、关于dubbo的安全 有什么好的建议请多多指点。

    万分感激!!!
    Best Regards!

    cnsdl sohosdl@gmail.com|cnsdl@126.com

    1. 十月 22, 2012

      Anonymous

      请问下哪里可以配置黑白名单?我用的Redis 注册中心,得到了如下错误:

      Exception in thread "main" com.alibaba.dubbo.rpc.RpcException: Forbid consumer 10.129.248.66 access service com.services.SignupPlayerService from registry 10.129.248.156:6379 use dubbo version 2.4.5, Please check registry access list (whitelist/blacklist)

      1. 十月 26, 2012

        Anonymous

        在dubbo的管理控制台程序(War) 中设置黑白名单,我们用的 Zookeeper

      2. 十一月 14, 2012

        Anonymous

        It's great to find an expert who can explian things so well

      3. 十一月 15, 2012

        Anonymous

        mjAgNQ <a href="http://yfxsjvrxkiqe.com/">yfxsjvrxkiqe</a>

      4. 十一月 16, 2012

        Anonymous

        Urs1Uz <a href="http://nbllptfopxjt.com/">nbllptfopxjt</a>

  32. 十一月 14, 2012

    Anonymous

    请问有计划针对.net平台发布版本吗?

  33. 十一月 15, 2012

    Anonymous

    请教一个问题,如果dubbo:service 没有设置超时时间,而在使用的客户端dubbo:reference中设置了超时时间为10秒,那么在真正使用中对于客户端来说超时时间是多少呢?多谢!

  34. 十一月 16, 2012

    Anonymous

    请问有dubbo和spring3注解的例子或者说明吗?注解一直引用不成功。。期待回答~~

    1. 十二月 12, 2013

      Anonymous

      修改一下源码吧!

      1. 十二月 13, 2013

        Anonymous

        给大家dubbo2.5.3+spring3.0.5的配置:

        <beans xmlns="http://www.springframework.org/schema/beans"
            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
            xmlns:dubbo="http://code.alibabatech.com/schema/dubbo"
            xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
            http://code.alibabatech.com/schema/dubbo http://code.alibabatech.com/schema/dubbo/dubbo.xsd">
            <dubbo:application name="$

        Unknown macro: {dubbo.application.name}

        "  />
            <!-- registry address, used for consumer to discover services -->
            <dubbo:registry protocol="zookeeper" address="$

        Unknown macro: {dubbo.registry}

        " />
            <dubbo:reference id="demoService" interface="com.alibaba.dubbo.demo.DemoService" />
        </beans>

        ..................

        web.xml

        <display-name>Dubbo Agent WebSite</display-name>
            <context-param>
                <param-name>contextConfigLocation</param-name>
                <param-value>classpath:/META-INF/spring/*.xml</param-value>
            </context-param>

        另外,将dubbo2.5.3源码对spring2.5的依赖改成对spring3.0.5的依赖(版本自己定),重新编译!

  35. 十二月 12, 2012

    Anonymous

    Exception in thread "main" java.lang.NoClassDefFoundError: org/I0Itec/zkclient/exception/ZkNoNodeException
    at com.alibaba.dubbo.registry.zookeeper.ZookeeperRegistryFactory.createRegistry(ZookeeperRegistryFactory.java:37)
    at com.alibaba.dubbo.registry.support.AbstractRegistryFactory.getRegistry(AbstractRegistryFactory.java:94)
    at com.alibaba.dubbo.registry.RegistryFactory$Adpative.getRegistry(RegistryFactory$Adpative.java)
    at com.alibaba.dubbo.registry.integration.RegistryProtocol.getRegistry(RegistryProtocol.java:190)
    at com.alibaba.dubbo.registry.integration.RegistryProtocol.export(RegistryProtocol.java:109)
    at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper.export(ProtocolFilterWrapper.java:53)
    at com.alibaba.dubbo.rpc.protocol.ProtocolListenerWrapper.export(ProtocolListenerWrapper.java:54)
    at com.alibaba.dubbo.rpc.Protocol$Adpative.export(Protocol$Adpative.java)
    at com.alibaba.dubbo.config.ServiceConfig.doExportUrlsFor1Protocol(ServiceConfig.java:485)
    at com.alibaba.dubbo.config.ServiceConfig.doExportUrls(ServiceConfig.java:281)
    at com.alibaba.dubbo.config.ServiceConfig.doExport(ServiceConfig.java:242)
    at com.alibaba.dubbo.config.ServiceConfig.export(ServiceConfig.java:143)
    at com.alibaba.dubbo.config.spring.ServiceBean.onApplicationEvent(ServiceBean.java:109)
    at org.springframework.context.event.SimpleApplicationEventMulticaster$1.run(SimpleApplicationEventMulticaster.java:78)
    at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49)
    at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:76)
    at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:260)
    at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:743)
    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:372)
    at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:122)
    at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:76)
    at com.lenovo.api.test.Provider.main(Provider.java:7)
    Caused by: java.lang.ClassNotFoundException: org.I0Itec.zkclient.exception.ZkNoNodeException
    at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
    ... 22 more
    这个错误是什么问题,怎么解决

  36. 四月 18, 2013

    Anonymous

    问题状况:管理控制台对指定消费者ip进行容错或屏蔽,向注册中心发布了override://xxxx.xxx.xx.x/mock=force或fail的url;结果是消费方没有被屏蔽或容错,仍能正常访问。
    如果消费方与registry注册中心相同ip的条件下,能正常进行屏蔽或容错。
    code trace:
    (MockClusterInvoker) 69 —>是否进行mock
    String value = directory.getUrl().getMethodParameter(invocation.getMethodName(), Constants.MOCK_KEY, Boolean.FALSE.toString()).trim();
    (RegistryDirectory) 610 —>directory.getUrl()
    public URL getUrl()

    Unknown macro: { return this.overrideDirectoryUrl; }

    (RegistryDirectory) 191 —>合并override参数
    this.overrideDirectoryUrl = directoryUrl;//directoryUrl为注册中心的url,host为注册中心
    for (Configurator configurator : localConfigurators)

    Unknown macro: { this.overrideDirectoryUrl = configurator.configure(overrideDirectoryUrl);//合并override参数时,如果overrideUrl的host与注册中心Url的host不相同就无法合并参数。 }

    疑问:上述问题是否描述正确,该问题的是否是一处bug,还是我使用该功能时遗漏了某个细节.

    1. 四月 19, 2013

      Anonymous

      另外一个bug
      消费方如果是generic方式将无法进行动态路由。
      methodName是routerUrl设置的条件之一,消费方必须要求有methods parameter才能在某router上路由
      generic类型的消费方mehtods parameter 返回为空,就可以逃避路由设置。

  37. 四月 27, 2013

    Anonymous

    咨询一个问题,帮忙排查排查:

    dubbo的客户端和服务端同时部署在本地的时候,服务端返回的对象,在客户端接收不到,但是如果服务端和客户端部署在不同的服务器上,就不会有这个问题。异常信息如下:

    com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method isLogin in the service com.tianque.dubboService.SessionService. Tried 3 times of the providers [192.168.1.175:32568] (1/1) from the registry 224.55.61.75:1230 on the consumer 192.168.1.175 using the dubbo version 2.5.3. Last error is: Invoke remote method timeout. method: isLogin, provider: dubbo://192.168.1.175:32568/com.tianque.dubboService.SessionService?anyhost=true&application=consumer-of-gis&check=false&dubbo=2.5.3&interface=com.tianque.dubboService.SessionService&methods=isLogin,findSessionBySessionId,deleteSessionsWhenTimeOut&pid=4988&revision=3.0.0&side=consumer&timeout=5000&timestamp=1367053464528&version=3.0.0, cause: Waiting server-side response timeout. start time: 2013-04-27 17:10:32.448, end time: 2013-04-27 17:10:37.450, client elapsed: 0 ms, server elapsed: 5002 ms, timeout: 5000 ms, request: Request [id=42, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=isLogin, parameterTypes=[class java.lang.String, class java.lang.String, class java.lang.String], arguments=[ab928fb4-3183-4268-9a6a-a37e83168394, /gis/twoDimensionMapStatisticCommonManage/countIndexGridLayerInfoByOrgId.action, 127.0.0.1], attachments=

    Unknown macro: {path=com.tianque.dubboService.SessionService, interface=com.tianque.dubboService.SessionService, timeout=5000, version=3.0.0}

    ]], channel: /192.168.1.175:64890 -> /192.168.1.175:32568 at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:101) at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:227) at com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:72) at com.alibaba.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:52) at com.alibaba.dubbo.common.bytecode.proxy3.isLogin(proxy3.java) at com.tianque.component.SessionManagerImpl.isLogin(SessionManagerImpl.java:67) at com.tianque.component.SessionManagerImpl$$FastClassByCGLIB$$6d197164.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:700) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:635) at com.tianque.component.SessionManagerImpl$$EnhancerByCGLIB$$50fafaeb.isLogin(<generated>) at com.tianque.web.filter.LoginValidateFilter.doFilter(LoginValidateFilter.java:68) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:96) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at com.tianque.web.filter.ParametersTrimFilter.doFilter(ParametersTrimFilter.java:30) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at com.tianque.web.filter.ClearThreadVariable.doFilter(ClearThreadVariable.java:25) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:78) at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:131) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
    Caused by: com.alibaba.dubbo.remoting.TimeoutException: Waiting server-side response timeout. start time: 2013-04-27 17:10:32.448, end time: 2013-04-27 17:10:37.450, client elapsed: 0 ms, server elapsed: 5002 ms, timeout: 5000 ms, request: Request [id=42, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=isLogin, parameterTypes=[class java.lang.String, class java.lang.String, class java.lang.String], arguments=[ab928fb4-3183-4268-9a6a-a37e83168394, /gis/twoDimensionMapStatisticCommonManage/countIndexGridLayerInfoByOrgId.action, 127.0.0.1], attachments=

    ]], channel: /192.168.1.175:64890 -> /192.168.1.175:32568 at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:107) at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:84) at com.alibaba.dubbo.rpc.protocol.dubbo.DubboInvoker.doInvoke(DubboInvoker.java:96) at com.alibaba.dubbo.rpc.protocol.AbstractInvoker.invoke(AbstractInvoker.java:144) at com.alibaba.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.java:75) at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91) at com.alibaba.dubbo.rpc.protocol.dubbo.filter.FutureFilter.invoke(FutureFilter.java:53) at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91) at com.alibaba.dubbo.rpc.filter.ConsumerContextFilter.invoke(ConsumerContextFilter.java:48) at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91) at com.alibaba.dubbo.rpc.listener.ListenerInvokerWrapper.invoke(ListenerInvokerWrapper.java:74) at com.alibaba.dubbo.rpc.protocol.InvokerWrapper.invoke(InvokerWrapper.java:53) at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:77) ... 41 more
    2013-04-27 17:10:37 com.atomikos.diagnostics.Slf4jConsole.println(Slf4jConsole.java:110)-[INFO] rollback() done of transaction 192.168.1.175.tm0002600005 -(:110)
    2013-04-27 17:10:37 org.mortbay.log.Slf4jLog.warn(Slf4jLog.java:87)-[ERROR] /resource/openLayersMap/images/openhand.cur -(:87)
    com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method isLogin in the service com.tianque.dubboService.SessionService. Tried 3 times of the providers [192.168.1.175:32568] (1/1) from the registry 224.55.61.75:1230 on the consumer 192.168.1.175 using the dubbo version 2.5.3. Last error is: Invoke remote method timeout. method: isLogin, provider: dubbo://192.168.1.175:32568/com.tianque.dubboService.SessionService?anyhost=true&application=consumer-of-gis&check=false&dubbo=2.5.3&interface=com.tianque.dubboService.SessionService&methods=isLogin,findSessionBySessionId,deleteSessionsWhenTimeOut&pid=4988&revision=3.0.0&side=consumer&timeout=5000&timestamp=1367053464528&version=3.0.0, cause: Waiting server-side response timeout. start time: 2013-04-27 17:10:32.460, end time: 2013-04-27 17:10:37.462, client elapsed: 0 ms, server elapsed: 5002 ms, timeout: 5000 ms, request: Request [id=43, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=isLogin, parameterTypes=[class java.lang.String, class java.lang.String, class java.lang.String], arguments=[ab928fb4-3183-4268-9a6a-a37e83168394, /resource/openLayersMap/images/openhand.cur, 127.0.0.1], attachments=

    Unknown macro: {path=com.tianque.dubboService.SessionService, interface=com.tianque.dubboService.SessionService, timeout=5000, version=3.0.0}

    ]], channel: /192.168.1.175:64890 -> /192.168.1.175:32568 at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:101) at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:227) at com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:72) at com.alibaba.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:52) at com.alibaba.dubbo.common.bytecode.proxy3.isLogin(proxy3.java) at com.tianque.component.SessionManagerImpl.isLogin(SessionManagerImpl.java:67) at com.tianque.component.SessionManagerImpl$$FastClassByCGLIB$$6d197164.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:700) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:635) at com.tianque.component.SessionManagerImpl$$EnhancerByCGLIB$$50fafaeb.isLogin(<generated>) at com.tianque.web.filter.LoginValidateFilter.doFilter(LoginValidateFilter.java:68) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:96) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at com.tianque.web.filter.ParametersTrimFilter.doFilter(ParametersTrimFilter.java:30) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at com.tianque.web.filter.ClearThreadVariable.doFilter(ClearThreadVariable.java:25) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
    Caused by: com.alibaba.dubbo.remoting.TimeoutException: Waiting server-side response timeout. start time: 2013-04-27 17:10:32.460, end time: 2013-04-27 17:10:37.462, client elapsed: 0 ms, server elapsed: 5002 ms, timeout: 5000 ms, request: Request [id=43, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=isLogin, parameterTypes=[class java.lang.String, class java.lang.String, class java.lang.String], arguments=[ab928fb4-3183-4268-9a6a-a37e83168394, /resource/openLayersMap/images/openhand.cur, 127.0.0.1], attachments=

    ]], channel: /192.168.1.175:64890 -> /192.168.1.175:32568 at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:107) at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:84) at com.alibaba.dubbo.rpc.protocol.dubbo.DubboInvoker.doInvoke(DubboInvoker.java:96) at com.alibaba.dubbo.rpc.protocol.AbstractInvoker.invoke(AbstractInvoker.java:144) at com.alibaba.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.java:75) at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91) at com.alibaba.dubbo.rpc.protocol.dubbo.filter.FutureFilter.invoke(FutureFilter.java:53) at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91) at com.alibaba.dubbo.rpc.filter.ConsumerContextFilter.invoke(ConsumerContextFilter.java:48) at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91) at com.alibaba.dubbo.rpc.listener.ListenerInvokerWrapper.invoke(ListenerInvokerWrapper.java:74) at com.alibaba.dubbo.rpc.protocol.InvokerWrapper.invoke(InvokerWrapper.java:53) at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:77) ... 38 more
    2013-04-27 17:10:37 com.atomikos.diagnostics.Slf4jConsole.println(Slf4jConsole.java:110)-[INFO] rollback() done of transaction 192.168.1.175.tm0002700005 -(:110)
    2013-04-27 17:10:37 org.mortbay.log.Slf4jLog.warn(Slf4jLog.java:87)-[ERROR] /openLayersMap/mapView.jsp -(:87)
    com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method isLogin in the service com.tianque.dubboService.SessionService. Tried 3 times of the providers [192.168.1.175:32568] (1/1) from the registry 224.55.61.75:1230 on the consumer 192.168.1.175 using the dubbo version 2.5.3. Last error is: Invoke remote method timeout. method: isLogin, provider: dubbo://192.168.1.175:32568/com.tianque.dubboService.SessionService?anyhost=true&application=consumer-of-gis&check=false&dubbo=2.5.3&interface=com.tianque.dubboService.SessionService&methods=isLogin,findSessionBySessionId,deleteSessionsWhenTimeOut&pid=4988&revision=3.0.0&side=consumer&timeout=5000&timestamp=1367053464528&version=3.0.0, cause: Waiting server-side response timeout. start time: 2013-04-27 17:10:32.471, end time: 2013-04-27 17:10:37.473, client elapsed: 0 ms, server elapsed: 5002 ms, timeout: 5000 ms, request: Request [id=44, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=isLogin, parameterTypes=[class java.lang.String, class java.lang.String, class java.lang.String], arguments=[ab928fb4-3183-4268-9a6a-a37e83168394, /openLayersMap/mapView.jsp, 127.0.0.1], attachments=

    Unknown macro: {path=com.tianque.dubboService.SessionService, interface=com.tianque.dubboService.SessionService, timeout=5000, version=3.0.0}

    ]], channel: /192.168.1.175:64890 -> /192.168.1.175:32568 at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:101) at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:227) at com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:72) at com.alibaba.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:52) at com.alibaba.dubbo.common.bytecode.proxy3.isLogin(proxy3.java) at com.tianque.component.SessionManagerImpl.isLogin(SessionManagerImpl.java:67) at com.tianque.component.SessionManagerImpl$$FastClassByCGLIB$$6d197164.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:700) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:635) at com.tianque.component.SessionManagerImpl$$EnhancerByCGLIB$$50fafaeb.isLogin(<generated>) at com.tianque.web.filter.LoginValidateFilter.doFilter(LoginValidateFilter.java:68) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:96) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at com.tianque.web.filter.ParametersTrimFilter.doFilter(ParametersTrimFilter.java:30) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at com.tianque.web.filter.ClearThreadVariable.doFilter(ClearThreadVariable.java:25) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:78) at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:131) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
    Caused by: com.alibaba.dubbo.remoting.TimeoutException: Waiting server-side response timeout. start time: 2013-04-27 17:10:32.471, end time: 2013-04-27 17:10:37.473, client elapsed: 0 ms, server elapsed: 5002 ms, timeout: 5000 ms, request: Request [id=44, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=isLogin, parameterTypes=[class java.lang.String, class java.lang.String, class java.lang.String], arguments=[ab928fb4-3183-4268-9a6a-a37e83168394, /openLayersMap/mapView.jsp, 127.0.0.1], attachments=

    ]], channel: /192.168.1.175:64890 -> /192.168.1.175:32568 at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:107) at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:84) at com.alibaba.dubbo.rpc.protocol.dubbo.DubboInvoker.doInvoke(DubboInvoker.java:96) at com.alibaba.dubbo.rpc.protocol.AbstractInvoker.invoke(AbstractInvoker.java:144) at com.alibaba.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.java:75) at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91) at com.alibaba.dubbo.rpc.protocol.dubbo.filter.FutureFilter.invoke(FutureFilter.java:53) at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91) at com.alibaba.dubbo.rpc.filter.ConsumerContextFilter.invoke(ConsumerContextFilter.java:48) at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91) at com.alibaba.dubbo.rpc.listener.ListenerInvokerWrapper.invoke(ListenerInvokerWrapper.java:74) at com.alibaba.dubbo.rpc.protocol.InvokerWrapper.invoke(InvokerWrapper.java:53) at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:77) ... 41 more
    2013-04-27 17:10:38 com.atomikos.diagnostics.Slf4jConsole.println(Slf4jConsole.java:110)-[INFO] rollback() done of transaction 192.168.1.175.tm0002800005 -(:110)
    2013-04-27 17:10:38 org.mortbay.log.Slf4jLog.warn(Slf4jLog.java:87)-[ERROR] /sysadmin/orgManage/findOrganizationsByParent.action -(:87)
    com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method isLogin in the service com.tianque.dubboService.SessionService. Tried 3 times of the providers [192.168.1.175:32568] (1/1) from the registry 224.55.61.75:1230 on the consumer 192.168.1.175 using the dubbo version 2.5.3. Last error is: Invoke remote method timeout. method: isLogin, provider: dubbo://192.168.1.175:32568/com.tianque.dubboService.SessionService?anyhost=true&application=consumer-of-gis&check=false&dubbo=2.5.3&interface=com.tianque.dubboService.SessionService&methods=isLogin,findSessionBySessionId,deleteSessionsWhenTimeOut&pid=4988&revision=3.0.0&side=consumer&timeout=5000&timestamp=1367053464528&version=3.0.0, cause: Waiting server-side response timeout. start time: 2013-04-27 17:10:33.439, end time: 2013-04-27 17:10:38.441, client elapsed: 1 ms, server elapsed: 5001 ms, timeout: 5000 ms, request: Request [id=45, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=isLogin, parameterTypes=[class java.lang.String, class java.lang.String, class java.lang.String], arguments=[ab928fb4-3183-4268-9a6a-a37e83168394, /sysadmin/orgManage/findOrganizationsByParent.action, 127.0.0.1], attachments=

    Unknown macro: {path=com.tianque.dubboService.SessionService, interface=com.tianque.dubboService.SessionService, timeout=5000, version=3.0.0}

    ]], channel: /192.168.1.175:64890 -> /192.168.1.175:32568 at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:101) at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:227) at com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:72) at com.alibaba.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:52) at com.alibaba.dubbo.common.bytecode.proxy3.isLogin(proxy3.java) at com.tianque.component.SessionManagerImpl.isLogin(SessionManagerImpl.java:67) at com.tianque.component.SessionManagerImpl$$FastClassByCGLIB$$6d197164.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:700) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:635) at com.tianque.component.SessionManagerImpl$$EnhancerByCGLIB$$50fafaeb.isLogin(<generated>) at com.tianque.web.filter.LoginValidateFilter.doFilter(LoginValidateFilter.java:68) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:96) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at com.tianque.web.filter.ParametersTrimFilter.doFilter(ParametersTrimFilter.java:30) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at com.tianque.web.filter.ClearThreadVariable.doFilter(ClearThreadVariable.java:25) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:78) at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:131) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
    Caused by: com.alibaba.dubbo.remoting.TimeoutException: Waiting server-side response timeout. start time: 2013-04-27 17:10:33.439, end time: 2013-04-27 17:10:38.441, client elapsed: 1 ms, server elapsed: 5001 ms, timeout: 5000 ms, request: Request [id=45, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=isLogin, parameterTypes=[class java.lang.String, class java.lang.String, class java.lang.String], arguments=[ab928fb4-3183-4268-9a6a-a37e83168394, /sysadmin/orgManage/findOrganizationsByParent.action, 127.0.0.1], attachments=

    ]], channel: /192.168.1.175:64890 -> /192.168.1.175:32568 at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:107) at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:84) at com.alibaba.dubbo.rpc.protocol.dubbo.DubboInvoker.doInvoke(DubboInvoker.java:96) at com.alibaba.dubbo.rpc.protocol.AbstractInvoker.invoke(AbstractInvoker.java:144) at com.alibaba.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.java:75) at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91) at com.alibaba.dubbo.rpc.protocol.dubbo.filter.FutureFilter.invoke(FutureFilter.java:53) at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91) at com.alibaba.dubbo.rpc.filter.ConsumerContextFilter.invoke(ConsumerContextFilter.java:48) at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91) at com.alibaba.dubbo.rpc.listener.ListenerInvokerWrapper.invoke(ListenerInvokerWrapper.java:74) at com.alibaba.dubbo.rpc.protocol.InvokerWrapper.invoke(InvokerWrapper.java:53) at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:77) ... 41 more
    2013-04-27 17:10:38 com.atomikos.diagnostics.Slf4jConsole.println(Slf4jConsole.java:110)-[INFO] createCompositeTransaction ( 300000 ): created new ROOT transaction with id 192.168.1.175.tm0002900005 -(:110)
    2013-04-27 17:10:38 com.atomikos.diagnostics.Slf4jConsole.println(Slf4jConsole.java:110)-[INFO] createCompositeTransaction ( 300000 ): created new ROOT transaction with id 192.168.1.175.tm0003000005 -(:110)
    2013-04-27 17:10:53 com.atomikos.diagnostics.Slf4jConsole.println(Slf4jConsole.java:110)-[INFO] rollback() done of transaction 192.168.1.175.tm0002900005 -(:110)
    2013-04-27 17:10:53 org.mortbay.log.Slf4jLog.warn(Slf4jLog.java:87)-[ERROR] /sysadmin/orgManage/orgSelectComponent.action -(:87)
    com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method isLogin in the service com.tianque.dubboService.SessionService. Tried 3 times of the providers [192.168.1.175:32568] (1/1) from the registry 224.55.61.75:1230 on the consumer 192.168.1.175 using the dubbo version 2.5.3. Last error is: Invoke remote method timeout. method: isLogin, provider: dubbo://192.168.1.175:32568/com.tianque.dubboService.SessionService?anyhost=true&application=consumer-of-gis&check=false&dubbo=2.5.3&interface=com.tianque.dubboService.SessionService&methods=isLogin,findSessionBySessionId,deleteSessionsWhenTimeOut&pid=4988&revision=3.0.0&side=consumer&timeout=5000&timestamp=1367053464528&version=3.0.0, cause: Waiting server-side response timeout. start time: 2013-04-27 17:10:48.522, end time: 2013-04-27 17:10:53.523, client elapsed: 0 ms, server elapsed: 5001 ms, timeout: 5000 ms, request: Request [id=50, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=isLogin, parameterTypes=[class java.lang.String, class java.lang.String, class java.lang.String], arguments=[ab928fb4-3183-4268-9a6a-a37e83168394, /sysadmin/orgManage/orgSelectComponent.action, 127.0.0.1], attachments=

    Unknown macro: {path=com.tianque.dubboService.SessionService, interface=com.tianque.dubboService.SessionService, timeout=5000, version=3.0.0}

    ]], channel: /192.168.1.175:64890 -> /192.168.1.175:32568 at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:101) at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:227) at com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:72) at com.alibaba.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:52) at com.alibaba.dubbo.common.bytecode.proxy3.isLogin(proxy3.java) at com.tianque.component.SessionManagerImpl.isLogin(SessionManagerImpl.java:67) at com.tianque.component.SessionManagerImpl$$FastClassByCGLIB$$6d197164.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:700) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:635) at com.tianque.component.SessionManagerImpl$$EnhancerByCGLIB$$50fafaeb.isLogin(<generated>) at com.tianque.web.filter.LoginValidateFilter.doFilter(LoginValidateFilter.java:68) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:96) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at com.tianque.web.filter.ParametersTrimFilter.doFilter(ParametersTrimFilter.java:30) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at com.tianque.web.filter.ClearThreadVariable.doFilter(ClearThreadVariable.java:25) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:78) at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:131) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
    Caused by: com.alibaba.dubbo.remoting.TimeoutException: Waiting server-side response timeout. start time: 2013-04-27 17:10:48.522, end time: 2013-04-27 17:10:53.523, client elapsed: 0 ms, server elapsed: 5001 ms, timeout: 5000 ms, request: Request [id=50, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=isLogin, parameterTypes=[class java.lang.String, class java.lang.String, class java.lang.String], arguments=[ab928fb4-3183-4268-9a6a-a37e83168394, /sysadmin/orgManage/orgSelectComponent.action, 127.0.0.1], attachments=

    ]], channel: /192.168.1.175:64890 -> /192.168.1.175:32568 at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:107) at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:84) at com.alibaba.dubbo.rpc.protocol.dubbo.DubboInvoker.doInvoke(DubboInvoker.java:96) at com.alibaba.dubbo.rpc.protocol.AbstractInvoker.invoke(AbstractInvoker.java:144) at com.alibaba.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.java:75) at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91) at com.alibaba.dubbo.rpc.protocol.dubbo.filter.FutureFilter.invoke(FutureFilter.java:53) at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91) at com.alibaba.dubbo.rpc.filter.ConsumerContextFilter.invoke(ConsumerContextFilter.java:48) at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91) at com.alibaba.dubbo.rpc.listener.ListenerInvokerWrapper.invoke(ListenerInvokerWrapper.java:74) at com.alibaba.dubbo.rpc.protocol.InvokerWrapper.invoke(InvokerWrapper.java:53) at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:77) ... 41 more
    2013-04-27 17:10:53 com.atomikos.diagnostics.Slf4jConsole.println(Slf4jConsole.java:110)-[INFO] rollback() done of transaction 192.168.1.175.tm0003000005 -(:110)
    2013-04-27 17:10:53 org.mortbay.log.Slf4jLog.warn(Slf4jLog.java:87)-[ERROR] /sysadmin/orgManage/orgSelectComponent.action -(:87)
    com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method isLogin in the service com.tianque.dubboService.SessionService. Tried 3 times of the providers [192.168.1.175:32568] (1/1) from the registry 224.55.61.75:1230 on the consumer 192.168.1.175 using the dubbo version 2.5.3. Last error is: Invoke remote method timeout. method: isLogin, provider: dubbo://192.168.1.175:32568/com.tianque.dubboService.SessionService?anyhost=true&application=consumer-of-gis&check=false&dubbo=2.5.3&interface=com.tianque.dubboService.SessionService&methods=isLogin,findSessionBySessionId,deleteSessionsWhenTimeOut&pid=4988&revision=3.0.0&side=consumer&timeout=5000&timestamp=1367053464528&version=3.0.0, cause: Waiting server-side response timeout. start time: 2013-04-27 17:10:48.534, end time: 2013-04-27 17:10:53.535, client elapsed: 0 ms, server elapsed: 5001 ms, timeout: 5000 ms, request: Request [id=51, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=isLogin, parameterTypes=[class java.lang.String, class java.lang.String, class java.lang.String], arguments=[ab928fb4-3183-4268-9a6a-a37e83168394, /sysadmin/orgManage/orgSelectComponent.action, 127.0.0.1], attachments=

    Unknown macro: {path=com.tianque.dubboService.SessionService, interface=com.tianque.dubboService.SessionService, timeout=5000, version=3.0.0}

    ]], channel: /192.168.1.175:64890 -> /192.168.1.175:32568 at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:101) at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:227) at com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:72) at com.alibaba.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:52) at com.alibaba.dubbo.common.bytecode.proxy3.isLogin(proxy3.java) at com.tianque.component.SessionManagerImpl.isLogin(SessionManagerImpl.java:67) at com.tianque.component.SessionManagerImpl$$FastClassByCGLIB$$6d197164.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:700) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:635) at com.tianque.component.SessionManagerImpl$$EnhancerByCGLIB$$50fafaeb.isLogin(<generated>) at com.tianque.web.filter.LoginValidateFilter.doFilter(LoginValidateFilter.java:68) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:96) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at com.tianque.web.filter.ParametersTrimFilter.doFilter(ParametersTrimFilter.java:30) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at com.tianque.web.filter.ClearThreadVariable.doFilter(ClearThreadVariable.java:25) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:78) at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:131) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
    Caused by: com.alibaba.dubbo.remoting.TimeoutException: Waiting server-side response timeout. start time: 2013-04-27 17:10:48.534, end time: 2013-04-27 17:10:53.535, client elapsed: 0 ms, server elapsed: 5001 ms, timeout: 5000 ms, request: Request [id=51, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=isLogin, parameterTypes=[class java.lang.String, class java.lang.String, class java.lang.String], arguments=[ab928fb4-3183-4268-9a6a-a37e83168394, /sysadmin/orgManage/orgSelectComponent.action, 127.0.0.1], attachments=

    ]], channel: /192.168.1.175:64890 -> /192.168.1.175:32568 at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:107) at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:84) at com.alibaba.dubbo.rpc.protocol.dubbo.DubboInvoker.doInvoke(DubboInvoker.java:96) at com.alibaba.dubbo.rpc.protocol.AbstractInvoker.invoke(AbstractInvoker.java:144) at com.alibaba.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.java:75) at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91) at com.alibaba.dubbo.rpc.protocol.dubbo.filter.FutureFilter.invoke(FutureFilter.java:53) at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91) at com.alibaba.dubbo.rpc.filter.ConsumerContextFilter.invoke(ConsumerContextFilter.java:48) at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91) at com.alibaba.dubbo.rpc.listener.ListenerInvokerWrapper.invoke(ListenerInvokerWrapper.java:74) at com.alibaba.dubbo.rpc.protocol.InvokerWrapper.invoke(InvokerWrapper.java:53) at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:77) ... 41 more
    com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method isLogin in the service com.tianque.dubboService.SessionService. Tried 3 times of the providers [192.168.1.175:32568] (1/1) from the registry 224.55.61.75:1230 on the consumer 192.168.1.175 using the dubbo version 2.5.3. Last error is: Invoke remote method timeout. method: isLogin, provider: dubbo://192.168.1.175:32568/com.tianque.dubboService.SessionService?anyhost=true&application=consumer-of-gis&check=false&dubbo=2.5.3&interface=com.tianque.dubboService.SessionService&methods=isLogin,findSessionBySessionId,deleteSessionsWhenTimeOut&pid=4988&revision=3.0.0&side=consumer&timeout=5000&timestamp=1367053464528&version=3.0.0, cause: Waiting server-side response timeout. start time: 2013-04-27 17:10:32.448, end time: 2013-04-27 17:10:37.450, client elapsed: 0 ms, server elapsed: 5002 ms, timeout: 5000 ms, request: Request [id=42, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=isLogin, parameterTypes=[class java.lang.String, class java.lang.String, class java.lang.String], arguments=[ab928fb4-3183-4268-9a6a-a37e83168394, /gis/twoDimensionMapStatisticCommonManage/countIndexGridLayerInfoByOrgId.action, 127.0.0.1], attachments=

    Unknown macro: {path=com.tianque.dubboService.SessionService, interface=com.tianque.dubboService.SessionService, timeout=5000, version=3.0.0}

    ]], channel: /192.168.1.175:64890 -> /192.168.1.175:32568

    at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:101)

    at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:227)

    at com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:72)

    at com.alibaba.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:52)

    at com.alibaba.dubbo.common.bytecode.proxy3.isLogin(proxy3.java)

    at com.tianque.component.SessionManagerImpl.isLogin(SessionManagerImpl.java:67)

    at com.tianque.component.SessionManagerImpl$$FastClassByCGLIB$$6d197164.invoke(<generated>)

    at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)

    at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:700)

    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)

    at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)

    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)

    at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:635)

    at com.tianque.component.SessionManagerImpl$$EnhancerByCGLIB$$50fafaeb.isLogin(<generated>)

    at com.tianque.web.filter.LoginValidateFilter.doFilter(LoginValidateFilter.java:68)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:96)

    at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at com.tianque.web.filter.ParametersTrimFilter.doFilter(ParametersTrimFilter.java:30)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at com.tianque.web.filter.ClearThreadVariable.doFilter(ClearThreadVariable.java:25)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:78)

    at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:131)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)

    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)

    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)

    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)

    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)

    at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)

    at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)

    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)

    at org.mortbay.jetty.Server.handle(Server.java:326)

    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)

    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)

    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)

    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)

    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)

    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)

    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)

    Caused by: com.alibaba.dubbo.remoting.TimeoutException: Waiting server-side response timeout. start time: 2013-04-27 17:10:32.448, end time: 2013-04-27 17:10:37.450, client elapsed: 0 ms, server elapsed: 5002 ms, timeout: 5000 ms, request: Request [id=42, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=isLogin, parameterTypes=[class java.lang.String, class java.lang.String, class java.lang.String], arguments=[ab928fb4-3183-4268-9a6a-a37e83168394, /gis/twoDimensionMapStatisticCommonManage/countIndexGridLayerInfoByOrgId.action, 127.0.0.1], attachments=

    ]], channel: /192.168.1.175:64890 -> /192.168.1.175:32568

    at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:107)

    at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:84)

    at com.alibaba.dubbo.rpc.protocol.dubbo.DubboInvoker.doInvoke(DubboInvoker.java:96)

    at com.alibaba.dubbo.rpc.protocol.AbstractInvoker.invoke(AbstractInvoker.java:144)

    at com.alibaba.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.java:75)

    at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)

    at com.alibaba.dubbo.rpc.protocol.dubbo.filter.FutureFilter.invoke(FutureFilter.java:53)

    at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)

    at com.alibaba.dubbo.rpc.filter.ConsumerContextFilter.invoke(ConsumerContextFilter.java:48)

    at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)

    at com.alibaba.dubbo.rpc.listener.ListenerInvokerWrapper.invoke(ListenerInvokerWrapper.java:74)

    at com.alibaba.dubbo.rpc.protocol.InvokerWrapper.invoke(InvokerWrapper.java:53)

    at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:77)

    ... 41 more

    2013-04-27 17:10:37 com.atomikos.diagnostics.Slf4jConsole.println(Slf4jConsole.java:110)-[INFO] rollback() done of transaction 192.168.1.175.tm0002600005 -(:110)

    2013-04-27 17:10:37 org.mortbay.log.Slf4jLog.warn(Slf4jLog.java:87)-[ERROR] /resource/openLayersMap/images/openhand.cur -(:87)

    com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method isLogin in the service com.tianque.dubboService.SessionService. Tried 3 times of the providers [192.168.1.175:32568] (1/1) from the registry 224.55.61.75:1230 on the consumer 192.168.1.175 using the dubbo version 2.5.3. Last error is: Invoke remote method timeout. method: isLogin, provider: dubbo://192.168.1.175:32568/com.tianque.dubboService.SessionService?anyhost=true&application=consumer-of-gis&check=false&dubbo=2.5.3&interface=com.tianque.dubboService.SessionService&methods=isLogin,findSessionBySessionId,deleteSessionsWhenTimeOut&pid=4988&revision=3.0.0&side=consumer&timeout=5000&timestamp=1367053464528&version=3.0.0, cause: Waiting server-side response timeout. start time: 2013-04-27 17:10:32.460, end time: 2013-04-27 17:10:37.462, client elapsed: 0 ms, server elapsed: 5002 ms, timeout: 5000 ms, request: Request [id=43, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=isLogin, parameterTypes=[class java.lang.String, class java.lang.String, class java.lang.String], arguments=[ab928fb4-3183-4268-9a6a-a37e83168394, /resource/openLayersMap/images/openhand.cur, 127.0.0.1], attachments=

    Unknown macro: {path=com.tianque.dubboService.SessionService, interface=com.tianque.dubboService.SessionService, timeout=5000, version=3.0.0}

    ]], channel: /192.168.1.175:64890 -> /192.168.1.175:32568

    at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:101)

    at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:227)

    at com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:72)

    at com.alibaba.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:52)

    at com.alibaba.dubbo.common.bytecode.proxy3.isLogin(proxy3.java)

    at com.tianque.component.SessionManagerImpl.isLogin(SessionManagerImpl.java:67)

    at com.tianque.component.SessionManagerImpl$$FastClassByCGLIB$$6d197164.invoke(<generated>)

    at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)

    at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:700)

    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)

    at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)

    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)

    at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:635)

    at com.tianque.component.SessionManagerImpl$$EnhancerByCGLIB$$50fafaeb.isLogin(<generated>)

    at com.tianque.web.filter.LoginValidateFilter.doFilter(LoginValidateFilter.java:68)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:96)

    at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at com.tianque.web.filter.ParametersTrimFilter.doFilter(ParametersTrimFilter.java:30)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at com.tianque.web.filter.ClearThreadVariable.doFilter(ClearThreadVariable.java:25)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)

    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)

    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)

    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)

    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)

    at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)

    at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)

    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)

    at org.mortbay.jetty.Server.handle(Server.java:326)

    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)

    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)

    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)

    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)

    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)

    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)

    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)

    Caused by: com.alibaba.dubbo.remoting.TimeoutException: Waiting server-side response timeout. start time: 2013-04-27 17:10:32.460, end time: 2013-04-27 17:10:37.462, client elapsed: 0 ms, server elapsed: 5002 ms, timeout: 5000 ms, request: Request [id=43, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=isLogin, parameterTypes=[class java.lang.String, class java.lang.String, class java.lang.String], arguments=[ab928fb4-3183-4268-9a6a-a37e83168394, /resource/openLayersMap/images/openhand.cur, 127.0.0.1], attachments=

    ]], channel: /192.168.1.175:64890 -> /192.168.1.175:32568

    at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:107)

    at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:84)

    at com.alibaba.dubbo.rpc.protocol.dubbo.DubboInvoker.doInvoke(DubboInvoker.java:96)

    at com.alibaba.dubbo.rpc.protocol.AbstractInvoker.invoke(AbstractInvoker.java:144)

    at com.alibaba.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.java:75)

    at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)

    at com.alibaba.dubbo.rpc.protocol.dubbo.filter.FutureFilter.invoke(FutureFilter.java:53)

    at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)

    at com.alibaba.dubbo.rpc.filter.ConsumerContextFilter.invoke(ConsumerContextFilter.java:48)

    at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)

    at com.alibaba.dubbo.rpc.listener.ListenerInvokerWrapper.invoke(ListenerInvokerWrapper.java:74)

    at com.alibaba.dubbo.rpc.protocol.InvokerWrapper.invoke(InvokerWrapper.java:53)

    at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:77)

    ... 38 more

    2013-04-27 17:10:37 com.atomikos.diagnostics.Slf4jConsole.println(Slf4jConsole.java:110)-[INFO] rollback() done of transaction 192.168.1.175.tm0002700005 -(:110)

    2013-04-27 17:10:37 org.mortbay.log.Slf4jLog.warn(Slf4jLog.java:87)-[ERROR] /openLayersMap/mapView.jsp -(:87)

    com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method isLogin in the service com.tianque.dubboService.SessionService. Tried 3 times of the providers [192.168.1.175:32568] (1/1) from the registry 224.55.61.75:1230 on the consumer 192.168.1.175 using the dubbo version 2.5.3. Last error is: Invoke remote method timeout. method: isLogin, provider: dubbo://192.168.1.175:32568/com.tianque.dubboService.SessionService?anyhost=true&application=consumer-of-gis&check=false&dubbo=2.5.3&interface=com.tianque.dubboService.SessionService&methods=isLogin,findSessionBySessionId,deleteSessionsWhenTimeOut&pid=4988&revision=3.0.0&side=consumer&timeout=5000&timestamp=1367053464528&version=3.0.0, cause: Waiting server-side response timeout. start time: 2013-04-27 17:10:32.471, end time: 2013-04-27 17:10:37.473, client elapsed: 0 ms, server elapsed: 5002 ms, timeout: 5000 ms, request: Request [id=44, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=isLogin, parameterTypes=[class java.lang.String, class java.lang.String, class java.lang.String], arguments=[ab928fb4-3183-4268-9a6a-a37e83168394, /openLayersMap/mapView.jsp, 127.0.0.1], attachments=

    Unknown macro: {path=com.tianque.dubboService.SessionService, interface=com.tianque.dubboService.SessionService, timeout=5000, version=3.0.0}

    ]], channel: /192.168.1.175:64890 -> /192.168.1.175:32568

    at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:101)

    at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:227)

    at com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:72)

    at com.alibaba.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:52)

    at com.alibaba.dubbo.common.bytecode.proxy3.isLogin(proxy3.java)

    at com.tianque.component.SessionManagerImpl.isLogin(SessionManagerImpl.java:67)

    at com.tianque.component.SessionManagerImpl$$FastClassByCGLIB$$6d197164.invoke(<generated>)

    at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)

    at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:700)

    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)

    at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)

    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)

    at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:635)

    at com.tianque.component.SessionManagerImpl$$EnhancerByCGLIB$$50fafaeb.isLogin(<generated>)

    at com.tianque.web.filter.LoginValidateFilter.doFilter(LoginValidateFilter.java:68)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:96)

    at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at com.tianque.web.filter.ParametersTrimFilter.doFilter(ParametersTrimFilter.java:30)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at com.tianque.web.filter.ClearThreadVariable.doFilter(ClearThreadVariable.java:25)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:78)

    at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:131)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)

    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)

    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)

    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)

    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)

    at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)

    at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)

    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)

    at org.mortbay.jetty.Server.handle(Server.java:326)

    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)

    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)

    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)

    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)

    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)

    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)

    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)

    Caused by: com.alibaba.dubbo.remoting.TimeoutException: Waiting server-side response timeout. start time: 2013-04-27 17:10:32.471, end time: 2013-04-27 17:10:37.473, client elapsed: 0 ms, server elapsed: 5002 ms, timeout: 5000 ms, request: Request [id=44, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=isLogin, parameterTypes=[class java.lang.String, class java.lang.String, class java.lang.String], arguments=[ab928fb4-3183-4268-9a6a-a37e83168394, /openLayersMap/mapView.jsp, 127.0.0.1], attachments=

    ]], channel: /192.168.1.175:64890 -> /192.168.1.175:32568

    at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:107)

    at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:84)

    at com.alibaba.dubbo.rpc.protocol.dubbo.DubboInvoker.doInvoke(DubboInvoker.java:96)

    at com.alibaba.dubbo.rpc.protocol.AbstractInvoker.invoke(AbstractInvoker.java:144)

    at com.alibaba.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.java:75)

    at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)

    at com.alibaba.dubbo.rpc.protocol.dubbo.filter.FutureFilter.invoke(FutureFilter.java:53)

    at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)

    at com.alibaba.dubbo.rpc.filter.ConsumerContextFilter.invoke(ConsumerContextFilter.java:48)

    at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)

    at com.alibaba.dubbo.rpc.listener.ListenerInvokerWrapper.invoke(ListenerInvokerWrapper.java:74)

    at com.alibaba.dubbo.rpc.protocol.InvokerWrapper.invoke(InvokerWrapper.java:53)

    at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:77)

    ... 41 more

    2013-04-27 17:10:38 com.atomikos.diagnostics.Slf4jConsole.println(Slf4jConsole.java:110)-[INFO] rollback() done of transaction 192.168.1.175.tm0002800005 -(:110)

    2013-04-27 17:10:38 org.mortbay.log.Slf4jLog.warn(Slf4jLog.java:87)-[ERROR] /sysadmin/orgManage/findOrganizationsByParent.action -(:87)

    com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method isLogin in the service com.tianque.dubboService.SessionService. Tried 3 times of the providers [192.168.1.175:32568] (1/1) from the registry 224.55.61.75:1230 on the consumer 192.168.1.175 using the dubbo version 2.5.3. Last error is: Invoke remote method timeout. method: isLogin, provider: dubbo://192.168.1.175:32568/com.tianque.dubboService.SessionService?anyhost=true&application=consumer-of-gis&check=false&dubbo=2.5.3&interface=com.tianque.dubboService.SessionService&methods=isLogin,findSessionBySessionId,deleteSessionsWhenTimeOut&pid=4988&revision=3.0.0&side=consumer&timeout=5000&timestamp=1367053464528&version=3.0.0, cause: Waiting server-side response timeout. start time: 2013-04-27 17:10:33.439, end time: 2013-04-27 17:10:38.441, client elapsed: 1 ms, server elapsed: 5001 ms, timeout: 5000 ms, request: Request [id=45, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=isLogin, parameterTypes=[class java.lang.String, class java.lang.String, class java.lang.String], arguments=[ab928fb4-3183-4268-9a6a-a37e83168394, /sysadmin/orgManage/findOrganizationsByParent.action, 127.0.0.1], attachments=

    Unknown macro: {path=com.tianque.dubboService.SessionService, interface=com.tianque.dubboService.SessionService, timeout=5000, version=3.0.0}

    ]], channel: /192.168.1.175:64890 -> /192.168.1.175:32568

    at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:101)

    at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:227)

    at com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:72)

    at com.alibaba.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:52)

    at com.alibaba.dubbo.common.bytecode.proxy3.isLogin(proxy3.java)

    at com.tianque.component.SessionManagerImpl.isLogin(SessionManagerImpl.java:67)

    at com.tianque.component.SessionManagerImpl$$FastClassByCGLIB$$6d197164.invoke(<generated>)

    at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)

    at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:700)

    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)

    at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)

    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)

    at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:635)

    at com.tianque.component.SessionManagerImpl$$EnhancerByCGLIB$$50fafaeb.isLogin(<generated>)

    at com.tianque.web.filter.LoginValidateFilter.doFilter(LoginValidateFilter.java:68)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:96)

    at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at com.tianque.web.filter.ParametersTrimFilter.doFilter(ParametersTrimFilter.java:30)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at com.tianque.web.filter.ClearThreadVariable.doFilter(ClearThreadVariable.java:25)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:78)

    at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:131)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)

    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)

    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)

    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)

    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)

    at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)

    at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)

    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)

    at org.mortbay.jetty.Server.handle(Server.java:326)

    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)

    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)

    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)

    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)

    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)

    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)

    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)

    Caused by: com.alibaba.dubbo.remoting.TimeoutException: Waiting server-side response timeout. start time: 2013-04-27 17:10:33.439, end time: 2013-04-27 17:10:38.441, client elapsed: 1 ms, server elapsed: 5001 ms, timeout: 5000 ms, request: Request [id=45, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=isLogin, parameterTypes=[class java.lang.String, class java.lang.String, class java.lang.String], arguments=[ab928fb4-3183-4268-9a6a-a37e83168394, /sysadmin/orgManage/findOrganizationsByParent.action, 127.0.0.1], attachments=

    ]], channel: /192.168.1.175:64890 -> /192.168.1.175:32568

    at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:107)

    at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:84)

    at com.alibaba.dubbo.rpc.protocol.dubbo.DubboInvoker.doInvoke(DubboInvoker.java:96)

    at com.alibaba.dubbo.rpc.protocol.AbstractInvoker.invoke(AbstractInvoker.java:144)

    at com.alibaba.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.java:75)

    at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)

    at com.alibaba.dubbo.rpc.protocol.dubbo.filter.FutureFilter.invoke(FutureFilter.java:53)

    at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)

    at com.alibaba.dubbo.rpc.filter.ConsumerContextFilter.invoke(ConsumerContextFilter.java:48)

    at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)

    at com.alibaba.dubbo.rpc.listener.ListenerInvokerWrapper.invoke(ListenerInvokerWrapper.java:74)

    at com.alibaba.dubbo.rpc.protocol.InvokerWrapper.invoke(InvokerWrapper.java:53)

    at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:77)

    ... 41 more

    2013-04-27 17:10:38 com.atomikos.diagnostics.Slf4jConsole.println(Slf4jConsole.java:110)-[INFO] createCompositeTransaction ( 300000 ): created new ROOT transaction with id 192.168.1.175.tm0002900005 -(:110)

    2013-04-27 17:10:38 com.atomikos.diagnostics.Slf4jConsole.println(Slf4jConsole.java:110)-[INFO] createCompositeTransaction ( 300000 ): created new ROOT transaction with id 192.168.1.175.tm0003000005 -(:110)

    2013-04-27 17:10:53 com.atomikos.diagnostics.Slf4jConsole.println(Slf4jConsole.java:110)-[INFO] rollback() done of transaction 192.168.1.175.tm0002900005 -(:110)

    2013-04-27 17:10:53 org.mortbay.log.Slf4jLog.warn(Slf4jLog.java:87)-[ERROR] /sysadmin/orgManage/orgSelectComponent.action -(:87)

    com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method isLogin in the service com.tianque.dubboService.SessionService. Tried 3 times of the providers [192.168.1.175:32568] (1/1) from the registry 224.55.61.75:1230 on the consumer 192.168.1.175 using the dubbo version 2.5.3. Last error is: Invoke remote method timeout. method: isLogin, provider: dubbo://192.168.1.175:32568/com.tianque.dubboService.SessionService?anyhost=true&application=consumer-of-gis&check=false&dubbo=2.5.3&interface=com.tianque.dubboService.SessionService&methods=isLogin,findSessionBySessionId,deleteSessionsWhenTimeOut&pid=4988&revision=3.0.0&side=consumer&timeout=5000&timestamp=1367053464528&version=3.0.0, cause: Waiting server-side response timeout. start time: 2013-04-27 17:10:48.522, end time: 2013-04-27 17:10:53.523, client elapsed: 0 ms, server elapsed: 5001 ms, timeout: 5000 ms, request: Request [id=50, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=isLogin, parameterTypes=[class java.lang.String, class java.lang.String, class java.lang.String], arguments=[ab928fb4-3183-4268-9a6a-a37e83168394, /sysadmin/orgManage/orgSelectComponent.action, 127.0.0.1], attachments=

    Unknown macro: {path=com.tianque.dubboService.SessionService, interface=com.tianque.dubboService.SessionService, timeout=5000, version=3.0.0}

    ]], channel: /192.168.1.175:64890 -> /192.168.1.175:32568

    at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:101)

    at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:227)

    at com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:72)

    at com.alibaba.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:52)

    at com.alibaba.dubbo.common.bytecode.proxy3.isLogin(proxy3.java)

    at com.tianque.component.SessionManagerImpl.isLogin(SessionManagerImpl.java:67)

    at com.tianque.component.SessionManagerImpl$$FastClassByCGLIB$$6d197164.invoke(<generated>)

    at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)

    at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:700)

    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)

    at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)

    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)

    at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:635)

    at com.tianque.component.SessionManagerImpl$$EnhancerByCGLIB$$50fafaeb.isLogin(<generated>)

    at com.tianque.web.filter.LoginValidateFilter.doFilter(LoginValidateFilter.java:68)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:96)

    at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at com.tianque.web.filter.ParametersTrimFilter.doFilter(ParametersTrimFilter.java:30)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at com.tianque.web.filter.ClearThreadVariable.doFilter(ClearThreadVariable.java:25)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:78)

    at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:131)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)

    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)

    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)

    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)

    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)

    at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)

    at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)

    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)

    at org.mortbay.jetty.Server.handle(Server.java:326)

    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)

    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)

    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)

    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)

    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)

    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)

    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)

    Caused by: com.alibaba.dubbo.remoting.TimeoutException: Waiting server-side response timeout. start time: 2013-04-27 17:10:48.522, end time: 2013-04-27 17:10:53.523, client elapsed: 0 ms, server elapsed: 5001 ms, timeout: 5000 ms, request: Request [id=50, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=isLogin, parameterTypes=[class java.lang.String, class java.lang.String, class java.lang.String], arguments=[ab928fb4-3183-4268-9a6a-a37e83168394, /sysadmin/orgManage/orgSelectComponent.action, 127.0.0.1], attachments=

    ]], channel: /192.168.1.175:64890 -> /192.168.1.175:32568

    at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:107)

    at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:84)

    at com.alibaba.dubbo.rpc.protocol.dubbo.DubboInvoker.doInvoke(DubboInvoker.java:96)

    at com.alibaba.dubbo.rpc.protocol.AbstractInvoker.invoke(AbstractInvoker.java:144)

    at com.alibaba.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.java:75)

    at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)

    at com.alibaba.dubbo.rpc.protocol.dubbo.filter.FutureFilter.invoke(FutureFilter.java:53)

    at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)

    at com.alibaba.dubbo.rpc.filter.ConsumerContextFilter.invoke(ConsumerContextFilter.java:48)

    at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)

    at com.alibaba.dubbo.rpc.listener.ListenerInvokerWrapper.invoke(ListenerInvokerWrapper.java:74)

    at com.alibaba.dubbo.rpc.protocol.InvokerWrapper.invoke(InvokerWrapper.java:53)

    at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:77)

    ... 41 more

    2013-04-27 17:10:53 com.atomikos.diagnostics.Slf4jConsole.println(Slf4jConsole.java:110)-[INFO] rollback() done of transaction 192.168.1.175.tm0003000005 -(:110)

    2013-04-27 17:10:53 org.mortbay.log.Slf4jLog.warn(Slf4jLog.java:87)-[ERROR] /sysadmin/orgManage/orgSelectComponent.action -(:87)

    com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method isLogin in the service com.tianque.dubboService.SessionService. Tried 3 times of the providers [192.168.1.175:32568] (1/1) from the registry 224.55.61.75:1230 on the consumer 192.168.1.175 using the dubbo version 2.5.3. Last error is: Invoke remote method timeout. method: isLogin, provider: dubbo://192.168.1.175:32568/com.tianque.dubboService.SessionService?anyhost=true&application=consumer-of-gis&check=false&dubbo=2.5.3&interface=com.tianque.dubboService.SessionService&methods=isLogin,findSessionBySessionId,deleteSessionsWhenTimeOut&pid=4988&revision=3.0.0&side=consumer&timeout=5000&timestamp=1367053464528&version=3.0.0, cause: Waiting server-side response timeout. start time: 2013-04-27 17:10:48.534, end time: 2013-04-27 17:10:53.535, client elapsed: 0 ms, server elapsed: 5001 ms, timeout: 5000 ms, request: Request [id=51, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=isLogin, parameterTypes=[class java.lang.String, class java.lang.String, class java.lang.String], arguments=[ab928fb4-3183-4268-9a6a-a37e83168394, /sysadmin/orgManage/orgSelectComponent.action, 127.0.0.1], attachments=

    Unknown macro: {path=com.tianque.dubboService.SessionService, interface=com.tianque.dubboService.SessionService, timeout=5000, version=3.0.0}

    ]], channel: /192.168.1.175:64890 -> /192.168.1.175:32568

    at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:101)

    at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:227)

    at com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:72)

    at com.alibaba.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:52)

    at com.alibaba.dubbo.common.bytecode.proxy3.isLogin(proxy3.java)

    at com.tianque.component.SessionManagerImpl.isLogin(SessionManagerImpl.java:67)

    at com.tianque.component.SessionManagerImpl$$FastClassByCGLIB$$6d197164.invoke(<generated>)

    at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)

    at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:700)

    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)

    at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)

    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)

    at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:635)

    at com.tianque.component.SessionManagerImpl$$EnhancerByCGLIB$$50fafaeb.isLogin(<generated>)

    at com.tianque.web.filter.LoginValidateFilter.doFilter(LoginValidateFilter.java:68)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:96)

    at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at com.tianque.web.filter.ParametersTrimFilter.doFilter(ParametersTrimFilter.java:30)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at com.tianque.web.filter.ClearThreadVariable.doFilter(ClearThreadVariable.java:25)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:78)

    at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:131)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)

    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)

    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)

    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)

    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)

    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)

    at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)

    at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)

    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)

    at org.mortbay.jetty.Server.handle(Server.java:326)

    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)

    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)

    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)

    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)

    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)

    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)

    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)

    Caused by: com.alibaba.dubbo.remoting.TimeoutException: Waiting server-side response timeout. start time: 2013-04-27 17:10:48.534, end time: 2013-04-27 17:10:53.535, client elapsed: 0 ms, server elapsed: 5001 ms, timeout: 5000 ms, request: Request [id=51, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=isLogin, parameterTypes=[class java.lang.String, class java.lang.String, class java.lang.String], arguments=[ab928fb4-3183-4268-9a6a-a37e83168394, /sysadmin/orgManage/orgSelectComponent.action, 127.0.0.1], attachments=

    ]], channel: /192.168.1.175:64890 -> /192.168.1.175:32568

    at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:107)

    at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:84)

    at com.alibaba.dubbo.rpc.protocol.dubbo.DubboInvoker.doInvoke(DubboInvoker.java:96)

    at com.alibaba.dubbo.rpc.protocol.AbstractInvoker.invoke(AbstractInvoker.java:144)

    at com.alibaba.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.java:75)

    at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)

    at com.alibaba.dubbo.rpc.protocol.dubbo.filter.FutureFilter.invoke(FutureFilter.java:53)

    at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)

    at com.alibaba.dubbo.rpc.filter.ConsumerContextFilter.invoke(ConsumerContextFilter.java:48)

    at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)

    at com.alibaba.dubbo.rpc.listener.ListenerInvokerWrapper.invoke(ListenerInvokerWrapper.java:74)

    at com.alibaba.dubbo.rpc.protocol.InvokerWrapper.invoke(InvokerWrapper.java:53)

    at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:77)

    ... 41 more

  38. 六月 12, 2013

    Anonymous

    Hi
    为什么总数会碰到无法定位登录位置的问题啊?
    每次触发调用的时候就会出现,调用的过程看起来都正确,都成功获取返回,但是console里面老出现这样的提示。

    2013-06-12 12:52:29,271 [DEBUG] [ZooKeeperSaslClient.java] : 519 – Could not retrieve login configuration: java.lang.SecurityException: 无法定位登录配置
    2013-06-12 12:52:29,271 [DEBUG] [ZooKeeperSaslClient.java] : 519 – Could not retrieve login configuration: java.lang.SecurityException: 无法定位登录配置
    2013-06-12 12:52:29,274 [DEBUG] [ZooKeeperSaslClient.java] : 519 – Could not retrieve login configuration: java.lang.SecurityException: 无法定位登录配置
    2013-06-12 12:52:29,274 [DEBUG] [ZooKeeperSaslClient.java] : 519 – Could not retrieve login configuration: java.lang.SecurityException: 无法定位登录配置
    2013-06-12 12:52:29,274 [DEBUG] [ZooKeeperSaslClient.java] : 519 – Could not retrieve login configuration: java.lang.SecurityException: 无法定位登录配置
    2013-06-12 12:52:29,274 [DEBUG] [ClientCnxn.java] : 815 – Reading reply sessionid:0x13f36777ce8000c, packet:: clientPath:null serverPath:null finished:false header:: 101,-11 replyHeader:: 101,1073,0 request:: null response:: null
    2013-06-12 12:52:29,274 [DEBUG] [ClientCnxn.java] : 1257 – Disconnecting client for session: 0x13f36777ce8000c
    2013-06-12 12:52:29,274 [DEBUG] [ZooKeeperSaslClient.java] : 519 – Could not retrieve login configuration: java.lang.SecurityException: 无法定位登录配置
    2013-06-12 12:52:29,276 [INFO] [ZooKeeper.java] : 684 – Session: 0x13f36777ce8000c closed

    1. 六月 12, 2013

      Anonymous

      应该是我多启动了同样的监听端口导致。

  39. 六月 27, 2013

    Anonymous

    DubboAdmin里面配置路由规则和负载均衡这些都做了持久化存储的吧?具体是如何实现方式呢

    我们现在也在做一个监控治理中心,想复用这些配置功能

  40. 七月 12, 2013

    Anonymous

    }
    }, dubbo version: 2.5.0, current host: 127.0.0.1
    INFO - [DUBBO] Start NettyServer bind /0.0.0.0:20880, export /10.0.20.136:20880, dubbo version: 2.5.0, current host: 127.0.0.1
    Exception in thread "main" java.lang.IllegalArgumentException: Invalid multicast address 127.0.0.1, scope: 224.0.0.0 - 239.255.255.255
    at com.alibaba.dubbo.registry.multicast.MulticastRegistry.<init>(MulticastRegistry.java:83)
    at com.alibaba.dubbo.registry.multicast.MulticastRegistryFactory.createRegistry(MulticastRegistryFactory.java:30)
    at com.alibaba.dubbo.registry.support.AbstractRegistryFactory.getRegistry(AbstractRegistryFactory.java:94)
    at com.alibaba.dubbo.registry.RegistryFactory$Adpative.getRegistry(RegistryFactory$Adpative.java)
    at com.alibaba.dubbo.registry.integration.RegistryProtocol.getRegistry(RegistryProtocol.java:190)
    at com.alibaba.dubbo.registry.integration.RegistryProtocol.export(RegistryProtocol.java:109)
    at com.alibaba.dubbo.rpc.protocol.ProtocolListenerWrapper.export(ProtocolListenerWrapper.java:54)
    at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper.export(ProtocolFilterWrapper.java:53)
    at com.alibaba.dubbo.rpc.Protocol$Adpative.export(Protocol$Adpative.java)
    at com.alibaba.dubbo.config.ServiceConfig.doExportUrls(ServiceConfig.java:466)
    at com.alibaba.dubbo.config.ServiceConfig.doExport(ServiceConfig.java:242)
    at com.alibaba.dubbo.config.ServiceConfig.export(ServiceConfig.java:143)
    at com.alibaba.dubbo.config.spring.ServiceBean.onApplicationEvent(ServiceBean.java:109)
    at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:97)
    at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:334)
    at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:948)
    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482)
    at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:139)
    at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:93)
    at com.yougou.dobbo.provider.Provider.main(Provider.java:19)
    INFO - [DUBBO] Run shutdown hook now., dubbo version: 2.5.0, current host: 127.0.0.1
    INFO - [DUBBO] Close all registries [], dubbo version: 2.5.0, current host: 127.0.0.1
    INFO - [DUBBO] Unexport service: dubbo://10.0.20.136:20880/com.yougou.dobbo.provider.IDemoService?anyhost=true&application=hello-world-app&dubbo=2.5.0&interface=com.yougou.dobbo.provider.IDemoService&methods=sayHello&pid=3436&side=provider&timestamp=1373616082822, dubbo version: 2.5.0, current host: 127.0.0.1
    INFO - [DUBBO] Close dubbo server: /10.0.20.136:20880, dubbo version: 2.5.0, current host: 127.0.0.1
    INFO - [DUBBO] Close NettyServer bind /0.0.0.0:20880, export /10.0.20.136:20880, dubbo version: 2.5.0, current host: 127.0.0.1
    INFO - [DUBBO] Unexport service: injvm://127.0.0.1/com.yougou.dobbo.provider.IDemoService?anyhost=true&application=hello-world-app&dubbo=2.5.0&interface=com.yougou.dobbo.provider.IDemoService&methods=sayHello&pid=3436&side=provider&timestamp=1373616082822, dubbo version: 2.5.0, current host: 127.0.0.1

    帮忙看下 ,按照您的例子,启动的时候报这个错,

    MulticastRegistry.java 里面这里

    public MulticastRegistry(URL url) {
    super(url);
    if (url.isAnyHost())

    Unknown macro: { throw new IllegalStateException("registry address == null"); }

    if (! isMulticastAddress(url.getHost()))

    Unknown macro: { throw new IllegalArgumentException("Invalid multicast address " + url.getHost() + ", scope}

    try {
    mutilcastAddress = InetAddress.getByName(url.getHost());
    mutilcastPort = url.getPort() <= 0 ? DEFAULT_MULTICAST_PORT : url.getPort();
    mutilcastSocket = new MulticastSocket(mutilcastPort);
    mutilcastSocket.setLoopbackMode(false);
    mutilcastSocket.joinGroup(mutilcastAddress);
    Thread thread = new Thread(new Runnable() {

    断点跟踪
    url :multicast://127.0.0.1:1234/com.alibaba.dubbo.registry.RegistryService?
    application=hello-world-app&
    dubbo=2.5.0&
    interface=com.alibaba.dubbo.registry.RegistryService&pid=3156&
    timestamp=1373614497504

    为什么会这样。。

    <!-- 提供方应用信息,用于计算依赖关系 -->
    <dubbo:application name="hello-world-app" />

    <!-- 使用multicast广播注册中心暴露服务地址 -->
    <dubbo:registry address="multicast://224.5.6.7:1234" />

    <bean id="demoService" class="com.yougou.dobbo.provider.DemoServiceImpl" />
    <!-- 用dubbo协议在20880端口暴露服务 -->
    <dubbo:protocol name="dubbo" port="20888" dispather="all" threadpool="cached" threads="5000"/>
    <!-- 声明需要暴露的服务接口 -->
    <dubbo:service interface="com.yougou.dobbo.provider.IDemoService" ref="demoService" />

    <!-- 和本地bean一样实现服务 -->

    我明明配置的不是127.0.0.1 。。。头大了。

  41. 九月 17, 2013

    Anonymous

    您好!
    请问下,我如何才能实现路由规则啊?具体的代码例子,消费者需要通过路由访问指定的提供者。

    1. 九月 24, 2013

      Anonymous

      已解决。

  42. 九月 17, 2013

    Anonymous

    我使用管理控制台进行操作的时候,为什么老是出现找不到的页面啊,这是什么原因?

  43. 十月 11, 2013

    Anonymous

    <!-- 使用redis发现服务地址 -->
    <dubbo:registry address="redis://172.16.10.224:6379" timeout="1000" />

    当消费程序关闭后,在redis注册中心,为什么我还能看到打开的到消费程序所在的连接??

  44. 一月 03, 2014

    Anonymous

    您好:
    环境:spring3 + hessian 4.0.7 +dubbo2.5.3 使用hessian协议时 客户端报异常,请问可能的原因是什么?代码配置都是根据用户手册中配置的 搞了2天了 还是报错,谢谢
    com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method upload in the se
    rvice com.chinamoney.dubbo.FileUploadServiceInf. Tried 3 times of the providers
    [192.168.120.181:7001] (1/1) from the registry 127.0.0.1:2181 on the consumer 19
    2.168.120.181 using the dubbo version 2.5.3. Last error is: Failed to invoke rem
    ote service: interface com.chinamoney.dubbo.FileUploadServiceInf, method: upload
    , cause: 500: java.net.SocketTimeoutException: Read timed out
    at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke
    (FailoverClusterInvoker.java:101)
    at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(A
    bstractClusterInvoker.java:227)
    at com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invo
    ke(MockClusterInvoker.java:72)
    at com.alibaba.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerIn
    vocationHandler.java:52)
    at com.alibaba.dubbo.common.bytecode.proxy1.upload(proxy1.java)
    at com.chinamoney.dubbo.consumer.ConsumerAction.uploadFile(ConsumerActio
    n.java:53)
    at com.chinamoney.dubbo.execute.Consumer.main(Consumer.java:20)
    Caused by: com.caucho.hessian.client.HessianConnectionException: 500: java.net.S
    ocketTimeoutException: Read timed out
    at com.caucho.hessian.client.HessianURLConnection.sendRequest(HessianURL
    Connection.java:142)
    at com.caucho.hessian.client.HessianProxy.sendRequest(HessianProxy.java:
    289)
    at com.caucho.hessian.client.HessianProxy.invoke(HessianProxy.java:170)
    at $Proxy8.upload(Unknown Source)
    at com.alibaba.dubbo.common.bytecode.Wrapper1.invokeMethod(Wrapper1.java
    )
    at com.alibaba.dubbo.rpc.proxy.javassist.JavassistProxyFactory$1.doInvok
    e(JavassistProxyFactory.java:46)
    at com.alibaba.dubbo.rpc.proxy.AbstractProxyInvoker.invoke(AbstractProxy
    Invoker.java:72)
    at com.alibaba.dubbo.rpc.protocol.AbstractProxyProtocol$2.doInvoke(Abstr
    actProxyProtocol.java:93)
    at com.alibaba.dubbo.rpc.protocol.AbstractInvoker.invoke(AbstractInvoker
    .java:144)
    at com.alibaba.dubbo.rpc.listener.ListenerInvokerWrapper.invoke(Listener
    InvokerWrapper.java:74)
    at com.alibaba.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.
    java:75)
    at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(Protoco
    lFilterWrapper.java:91)
    at com.alibaba.dubbo.rpc.protocol.dubbo.filter.FutureFilter.invoke(Futur
    eFilter.java:53)
    at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(Protoco
    lFilterWrapper.java:91)
    at com.alibaba.dubbo.rpc.filter.ConsumerContextFilter.invoke(ConsumerCon
    textFilter.java:48)
    at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(Protoco
    lFilterWrapper.java:91)
    at com.alibaba.dubbo.rpc.protocol.InvokerWrapper.invoke(InvokerWrapper.j
    ava:53)
    at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke
    (FailoverClusterInvoker.java:77)
    ... 6 more
    Caused by: java.net.SocketTimeoutException: Read timed out
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
    orAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
    onstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
    at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.j
    ava:1298)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpU
    RLConnection.java:1292)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon
    nection.java:946)
    at com.caucho.hessian.client.HessianURLConnection.sendRequest(HessianURL
    Connection.java:122)
    ... 23 more
    Caused by: java.net.SocketTimeoutException: Read timed out
    at java.net.SocketInputStream.socketRead0(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:129)
    at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
    at java.io.BufferedInputStream.read1(BufferedInputStream.java:258)
    at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
    at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:687)
    at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:632)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon
    nection.java:1002)
    at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:373
    )
    at com.caucho.hessian.client.HessianURLConnection.sendRequest(HessianURL
    Connection.java:109)
    ... 23 more

    1. 一月 03, 2014

      Anonymous

      容器使用的是weblogic12 容器启动完后 客户端第一次调用就会报这个异常 之后调用就不会有异常了。。。。。

Add Comment