dubbo2.5.5 . I will write it down when I have time in the future.
Friends who do not know how to search online also have a lot.
Dangdang: dubbox extends dubbo and adds rest-style interface access. The serialization block also uses kryo. Serialization is faster.
The company's project environment is built using dubbox2.8.4. I used the native dubbo2.5.5.
2.5.5 environment to build it up. Engineering projects are also accessed. dubbo-admin is no problem.
The only problem is that the Charts and Statistics in the monitoring project don't come out.
Monitored Qps are important to the project. You can know the daily traffic of the service interface and the daily traffic of client calls. This provides real-time visibility into how the project is performing. When is the project's peak period of operation. Usually the interface we develop, the most lack is this piece of monitoring.
Project engineering dubbox2.8.4, service environment dubbo2.5.5
problems:
expected map/object at java.lang.String (Lcom/alibaba/dubbo/common/URL;), dubbo version: 2.5.5, current host: 192.168.42.25 com.alibaba.com.caucho.hessian.io.HessianProtocolException: expected map/object at java.lang.String (Lcom/alibaba/dubbo/common/URL;) at com.alibaba.com.caucho.hessian.io.AbstractDeserializer.error(AbstractDeserializer.java:101) at com.alibaba.com.caucho.hessian.io.AbstractMapDeserializer.readObject(AbstractMapDeserializer.java:68) at com.alibaba.com.caucho.hessian.io.Hessian2Input.readObject(Hessian2Input.java:2224) at com.alibaba.dubbo.common.serialize.support.hessian.Hessian2ObjectInput.readObject(Hessian2ObjectInput.java:82) at com.alibaba.dubbo.rpc.protocol.dubbo.DecodeableRpcInvocation.decode(DecodeableRpcInvocation.java:119) at com.alibaba.dubbo.rpc.protocol.dubbo.DecodeableRpcInvocation.decode(DecodeableRpcInvocation.java:71) at com.alibaba.dubbo.rpc.protocol.dubbo.DubboCodec.decodeBody(DubboCodec.java:130) at com.alibaba.dubbo.remoting.exchange.codec.ExchangeCodec.decode(ExchangeCodec.java:118) at com.alibaba.dubbo.remoting.exchange.codec.ExchangeCodec.decode(ExchangeCodec.java:79)
The error reported by the monitoring terminal The
error is reported by the hession.
It is enough to adjust the version of the service environment and the version of the engineering project.
How to make monitoring pictures come out[ /b]
[b]1 Monitoring items need to change the configuration
dubbo.jetty.directory=/home/xx/dubbomitor/dubbo-monitor-simple-2.5.5/monitor
dubbo.charts.directory=${dubbo.jetty.directory}/charts
dubbo.statistics.directory=/home/xxx/dubbomitor/dubbo-monitor-simple-2.5.5/monitor/statistics
The monitor folder needs to be created by yourself. Statistics, charts folders, monitoring items will be created automatically.
2 The project server and client add
the server corresponding to the configuration statistics.
Add <dubbo:monitor protocol="registry"/> charts to the configuration file.
The client
<dubbo:monitor protocol= "registry"/> corresponding to the charts
did not know dubbo-monitor-simple-2.5.5-assembly during the project construction process. How does the .tar.gz compressed package use maven to form it.
Build the dubbo-monitor-simple project with maven locally. What comes out is the jar file. Anyone who knows can reply.
1 Does it have to be built in a linux environment? There is a problem with the
article , please correct me