美文网首页
后台一些记录

后台一些记录

作者: 仕明同学 | 来源:发表于2018-10-31 20:16 被阅读63次
    • 欢迎关注我的公众号
      公众号
    • Redis tks
    • 缓存就是在内存中存储的数据备份,当数据没有发生本质变化的时候,我们避免数据的查询操作直接连接数据库,而是去 内容中读取数据,这样就大大降低了数据库的读写次数,而且从内存中读数据的速度要比从数据库查询要快很多。
    image.png image.png
    image.png image.png
    已连接。
    新零售-39.108.108.242 :0>set key value
    "OK"
    新零售-39.108.108.242 :0>set retail:logistics:real_time_location:deliveryman_id_1 lishiming
    "OK"
    新零售-39.108.108.242 :0>get "{\"latitude\":22.5,\"gettingDataTime\":\"2018-10-17 17:28:00\",\"longitude\":23.1}"
    null
    新零售-39.108.108.242 :0>get  retail:logistics:real_time_location:deliveryman_id_1
    "lishiming"
    新零售-39.108.108.242 :0>set retail:logistics:real_time_location:deliveryman_id_1 "{\"latitude\":22.5,\"gettingDataTime\":\"2018-10-17 17:28:00\",\"longitude\":23.1}" 
    "OK"
    新零售-39.108.108.242 :0>set  shiming "{\"latitude\":22.5,\"gettingDataTime\":\"2018-10-17 17:28:00\",\"longitude\":23.1}"
    "OK"
    新零售-39.108.108.242 :0>get shiming
    "{"latitude":22.5,"gettingDataTime":"2018-10-17 17:28:00","longitude":23.1}"
    新零售-39.108.108.242 :0>del shiming
    "1"
    新零售-39.108.108.242 :0>del shiming
    "0"
    新零售-39.108.108.242 :0>get shiming
    null
    新零售-39.108.108.242 :0>type "{\"latitude\":22.5,\"gettingDataTime\":\"2018-10-17 17:28:00\",\"longitude\":23.1}"
    "none"
    新零售-39.108.108.242 :0>type retail:logistics:real_time_location:deliveryman_id_1
    "string"
    新零售-39.108.108.242 :0>
    
    image.png
    新零售-39.108.108.242 :0>exists "{\"latitude\":22.5,\"gettingDataTime\":\"2018-10-17 17:28:00\",\"longitude\":23.1}"
    "0"
    新零售-39.108.108.242 :0>exists retail:logistics:real_time_location:deliveryman_id_1
    "1"
    新零售-39.108.108.242 :0>
    
    image.png image.png
    新零售-39.108.108.242 :0>incr num
    "1"
    新零售-39.108.108.242 :0>incr num
    "2"
    新零售-39.108.108.242 :0>get num
    "2"
    
    image.png
    新零售-39.108.108.242 :0>incrby shiming 3
    "3"
    新零售-39.108.108.242 :0>incrby shiming 40
    "43"
    新零售-39.108.108.242 :0>get shiming
    "43"
    
    image.png
    新零售-39.108.108.242 :0>decr shiming
    "42"
    新零售-39.108.108.242 :0>decr shiming
    "41"
    新零售-39.108.108.242 :0>
    
    image.png
    新零售-39.108.108.242 :0>incrbyfloat shiming 102.54
    "143.54000000000000001"
    新零售-39.108.108.242 :0>
    
    image.png
    新零售-39.108.108.242 :0>append shiming " woaini "
    "29"
    新零售-39.108.108.242 :0>get shiming
    "143.54000000000000001 woaini "
    新零售-39.108.108.242 :0>
    
    image.png
    • 同时获得设置多个键值
    新零售-39.108.108.242 :0>mset shiming1 1 shiming2 2
    "OK"
    新零售-39.108.108.242 :0>get shiming2
    "2"
    新零售-39.108.108.242 :0>mget shiming  shiming1
     1)  "143.54000000000000001 woaini "
     2)  "1"
    新零售-39.108.108.242 :0>
    
    image.png
    新零售-39.108.108.242 :0>set key 你好
    "ERR syntax error"
    新零售-39.108.108.242 :0>SET  key  你好
    "ERR syntax error"
    新零售-39.108.108.242 :0>set key "你好"
    "OK"
    新零售-39.108.108.242 :0>get key
    "你好"
    新零售-39.108.108.242 :0>strlen key
    "6"
    新零售-39.108.108.242 :0>
    
    image.png image.png image.png image.png image.png image.png image.png image.png

    只读事务(@Transactional(readOnly = true))的一些概念 :https://blog.csdn.net/andyzhaojianhui/article/details/51984157

     /**
         * 对于只读查询,可以指定事务类型为readonly,即只读事务。
         * 由于只读事务不存在数据的修改,因此数据库将会为只读事务提供一些优化手段
         * @param orderCode
         * @return
         */
        @Override
        @Transactional(readOnly = true)
        public DeliveryOrder receiveDeliveryOrder(Long orderCode) {
            return deliveryOrderService.getByOrderCode(orderCode);
        }
    
    • https://blog.csdn.net/nextyu/article/details/78669997

    • 事务管理是应用系统开发中必不可少的一部分。Spring 为事务管理提供了丰富的功能支持。Spring 事务管理分为编程式和声明式的两种方式。编程式事务指的是通过编码方式实现事务;声明式事务基于 AOP,将具体业务逻辑与事务处理解耦。声明式事务管理使业务代码逻辑不受污染, 因此在实际使用中声明式事务用的比较多。声明式事务有两种方式,一种是在配置文件(xml)中做相关的事务规则声明,另一种是基于 @Transactional 注解的方式。本文将着重介绍基于 @Transactional 注解的事务管理。

    • Spring Boot 中使用 @Transactional 注解配置事务管理

    • 简单的使用方法

    • 只需在方法加上 @Transactional 注解就可以了。
      如下有一个保存用户的方法,加入 @Transactional 注解,使用默认配置,抛出异常之后,事务会自动回滚,数据不会插入到数据库。

    @Transactional
    @Override
    public void save() {
        User user = new User("服部半藏");
        userMapper.insertSelective(user);
    
        if (true) {
            throw new RuntimeException("save 抛异常了");
        }
    }
    

    Propagation.REQUIRED

    如果当前存在事务,则加入该事务,如果当前不存在事务,则创建一个新的事务。

    Propagation.SUPPORTS

    如果当前存在事务,则加入该事务;如果当前不存在事务,则以非事务的方式继续运行。

    Propagation.MANDATORY

    如果当前存在事务,则加入该事务;如果当前不存在事务,则抛出异常。

    Propagation.REQUIRES_NEW

    重新创建一个新的事务,如果当前存在事务,暂停当前的事务。

    Propagation.NOT_SUPPORTED

    以非事务的方式运行,如果当前存在事务,暂停当前的事务。

    Propagation.NEVER

    以非事务的方式运行,如果当前存在事务,则抛出异常。

    Propagation.NESTED

    和 Propagation.REQUIRED 效果一样。

    • isolation 属性
      事务的隔离级别,默认值为 Isolation.DEFAULT。
      可选的值有:
      Isolation.DEFAULT
      使用底层数据库默认的隔离级别。
      Isolation.READ_UNCOMMITTED
      Isolation.READ_COMMITTED
      Isolation.REPEATABLE_READ
      Isolation.SERIALIZABLE

    • rollbackFor 属性
      用于指定能够触发事务回滚的异常类型,可以指定多个异常类型。

    查询服务器liux系统

      1. 什么是linux?
    • Linux是一套免费使用和自由传播的类Unix操作系统,是一个多用户、多任务、支持多线程和多CPU的操作系统。它能运行主要的UNIX工具软件、应用程序和网络协议。它支持32位和64位硬件。Linux继承了Unix以网络为核心的设计思想,是一个性能稳定的多用户网络操作系统。
      1. Linux系统的特点?
    • 稳定的系统 :打个比方,安装Linux的主机连续运行一年以上不曾宕机、不必关机是很平常的事,我的windows系统今早打开时是黑屏,强行关机之后才恢复,原因不明

    • 安全性和漏洞的快速修补 :Linux有众多电脑高手在使用,所以维护者众多,更新维护很快,而windows则是所有人都会用,且不开源
      多任务,多用户 :你可以在一个Linux主机上规划出不同等级的用户,而且每个用户登录系统时工作环境可以不同,此外你还可以允许不同用户在同一时间登陆主机以使用主机的资源

    • 用户和用户组的规划 :在linux的机器上,文件可分为可读可写可执行三类(windows上也可以设置这些属性,在命令行里,会在以后的windows博客里写出来)此外,这些属性还可以分为三类:分别是文件拥有者、文件所属用户组、其他非拥有着与用户组者,这对于项目或者其他项目开发者具有良好的保密性
      相对较少的系统资源占用 :这是最吸引眼球的地方,目前市面上任何一款个人计算机都可以达到使用Linux搭建一个服务上百人以上的主机
      可定制裁剪,移植到嵌入式平台(如安卓设备)
      可选择的多种图形用户界面(如GNOME,KDE)

    • 1.模块化程度高

    • Linux的内核设计非常精巧,分成进程调度、内存管理、进程间通信、虚拟文件系统和网络接口五大部分;其独特的模块机制可根据用户的需要,实时地将某些模块插入或从内核中移走,使得Linux系统内核可以裁剪得非常小巧,很适合于嵌入式系统的需要。

    • 2.源码公开
    • 由于Linux系统的开发从一开始就与GNU项目紧密地结合起来,所以它的大多数组成部分都直接来自GNU项目。任何人、任何组织只要遵守GPL条 款,就可以自由使用Linux 源代码,为用户提供了最大限度的自由度。这一点也正投嵌入式系统所好,因为嵌入式系统应用千差万别,设计者往往需要针对具体的应用对源码进行修改和优化, 所以是否能获得源代码 对于嵌入式系统的开发是至关重要的。加之Linux的软件资源十分丰富,每种通用程序在Linux上几乎都可以找到,并且数量还在不断增加。这一切就使设 计者在其基础之上进行二次开发变得非常容易。另外,由于Linux源代码公开,也使用户不用担心有“后闸”等安全隐患。
      同时,源码开放给各教育机构提供极大的方便,从而也促进了Linux的学习、推广和应用。
    • 3.广泛的硬件支持
    • Linux能支持x86、ARM、MIPS、ALPHA和PowerPC等多种体系结构的微处理器。目前已成功地移植到数十种硬件平台,几乎能运行在所有流行的处理器上。
      由于世界范围内有众多开发者在为Linux的扩充贡献力量,所以Linux有着异常丰富的驱动程序资源,支持各种主流硬件设各和最新的硬件技术,甚至可在没有存储管理单元MMU 的处理器上运行,这些都进一步促进了Linux在嵌入式系统中的应用。
    • 4.安全性及可靠性好
    • 内核高效稳定。Linux内核的高效和稳定已在各个领域内得到了大量事实的验证。
      Linux中大量网络管理、网络服务等方面的功能,可使用户很方便地建立高效稳定的防火墙、路由器、工作站、服务器等。为提高安全性,它还提供了大量的网络管理软件、网络分析软件和网络安全软件等。
    • 5.具有优秀的开发工具
    • 开发嵌入式系统的关键是需要有一套完善的开发和调试工具。传统的嵌入式开发调试工具是在线仿真器(In Circuit Emulator,ICE),它通过取代目标板的微处理器,给目标程序提供一个完整的仿真环境,从而使开发者能非常清楚地了解到程序在目标板上的工作状 态,便于监视和调试程序。在线仿真器的价格非常高,而且只适合做非常底层的调试。如果使用的是嵌人式Linux,一旦软硬件能支持正常的串口功能,即使不 用在线仿真器,也可以很好地进行开发和调试工作,从而节省了一笔不小的开发费用。嵌入式Linux为开发者提供了一套完整的工具链(Tool Chain),能够很方便地实现从操作系统到应用软件各个级别的调试。
    • 6.有很好的网络支持利文件系统支持
    • Linux从诞生之日起就与Internet密不可分,支持各种标准的Internet网络协议,并且很容易移植到嵌入式系统当中。目前,Linux几乎支持所有主流的网络硬件、网络协议和文件系统,因此它是NFS的一个很好的平台。
      另一方面,由于Linux有很好的文件系统支持(例如,它支持Ext2、FAT32、romfs等文件系统),是数据各份、同步和复制的良好平台,这些都为开发嵌入式系统应用打下了坚实的基础。
    • 7.与UNIX完全兼容

    • 目前,在Linux中所包含的工具和实用程序,可以完成UNIX的所有主要功能。
      但由于Linux不是为实时而设计的,因而这就成了Linux在实时系统中应用的最大遗憾。不过,目前有众多的自由软件爱好者正在为此进行不懈的努力,也取得了诸多成果

      1. win系统的特点
    • 直观、高效的面向对象的图形用户界面,易学易用,Windows用户界面和开发环境都是面向对象的,这种操作方式模拟了现实世界的行为,易于理解、学习和使用。

      1. Linux与win的区别
    • windows平台:数量和质量的优势,不过大部分为收费软件;由微软官方提供重要支持和服务

    • linux平台:大都为开源自由软件,用户可以修改定制和再发布,由于基本免费没有资金支持,部分软件质量和体验欠缺;有全球所有的Linux开发者和自由软件社区提供支持

    • 是按Tab键,左上角ESC的下面两个,如果你当前目录只有一项,只需要直接Tab,如果有多项,输入前面不同的部分再Tab,一般输入3个字母就可以,如果按一下没效果,按两下会列出所有项,然后再输入一点自己再Tab就行

    cd / ,即进入根目录。

    pwd 命令pwd——查看当前路径

    ls 列出文件

    tab补全

    cd opt/

    cd data/

    ps -ef|grep logistics ps命令将某个进程显示出来 grep命令是查找中间的|是管道命令 是指ps命令与grep同时执行

    less retail-logistics.log less 工具也是对文件或其它输出进行分页显示的工具,应该说是linux正统查看文件内容的工具,功能极其强大。less 的用法比起 more 更加的有弹性。 在 more 的时候,我们并没有办法向前面翻, 只能往后面看,但若使用了 less 时,就可以使用 [pageup] [pagedown] 等按 键的功能来往前往后翻看文件,更容易用来查看一个文件的内容!除此之外,在 less 里头可以拥有更多的搜索功能,不止可以向下搜,也可以向上搜。

    tailf retail-logistics.log 动态跟踪日志文件logfile,最初的时候打印文件的最后10行内容。

    
    [dev@dev-lhn1d-retail-api1 ~]$ 
    [dev@dev-lhn1d-retail-api1 ~]$ ls
    logs  nohup.out
    [dev@dev-lhn1d-retail-api1 ~]$ cd /data
    -bash: cd: /data: No such file or directory
    [dev@dev-lhn1d-retail-api1 ~]$ ls
    logs  nohup.out
    [dev@dev-lhn1d-retail-api1 ~]$ cd /
    [dev@dev-lhn1d-retail-api1 /]$ ls
    bin  boot  dev  etc  home  lib  lib64  lost+found  media  mnt  nohup.out  opt  proc  root  run  sbin  srv  sys  tmp  usr  var
    [dev@dev-lhn1d-retail-api1 /]$ cd opt/
    [dev@dev-lhn1d-retail-api1 opt]$ ls
    apache-maven-3.5.4-bin.tar.gz  jdk-8u181-linux-x64.tar.gz  newretail_services  sh
    [dev@dev-lhn1d-retail-api1 opt]$ cd newretail_services/
    [dev@dev-lhn1d-retail-api1 newretail_services]$ ls
    blissmall-eureka  blissmall-gateway  retail-activity  retail-baseinfo  retail-logistics  retail-product  retail-shop
    [dev@dev-lhn1d-retail-api1 newretail_services]$ cd retail-logistics/
    [dev@dev-lhn1d-retail-api1 retail-logistics]$ ls
    logs  nohup.log  retail-logistics.jar
    [dev@dev-lhn1d-retail-api1 retail-logistics]$ pwd
    /opt/newretail_services/retail-logistics
    [dev@dev-lhn1d-retail-api1 retail-logistics]$ ps -ef|grep logistics
    ops      28125     1  1 14:31 ?        00:01:42 java -jar /opt/newretail_services/retail-logistics/retail-logistics.jar
    dev      31284 31247  0 17:04 pts/2    00:00:00 grep --color=auto logistics
    [dev@dev-lhn1d-retail-api1 retail-logistics]$ 
    [dev@dev-lhn1d-retail-api1 retail-logistics]$ ls
    logs  nohup.log  retail-logistics.jar
    [dev@dev-lhn1d-retail-api1 retail-logistics]$ cd logs/
    [dev@dev-lhn1d-retail-api1 logs]$ ls
    retail-logistics.log
    [dev@dev-lhn1d-retail-api1 logs]$ tailf retail-logistics.log 
    2018-10-31 16:20:00.006  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 16:25:00.008  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 16:30:00.008  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 16:35:00.007  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 16:40:00.008  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 16:45:00.008  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 16:50:00.009  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 16:55:00.008  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 17:00:00.006  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 17:05:00.006  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    ^C
    [dev@dev-lhn1d-retail-api1 logs]$ less retail-logistics.log 
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    2018-10-31 14:31:18.628  INFO [retail-logistics,,,] 28125 --- [main] n.b.retail.logistics.Application         : The following profiles are active: env
    2018-10-31 14:31:21.523  WARN [retail-logistics,,,] 28125 --- [main] c.c.f.f.i.p.DefaultServerProvider        : Environment is set to null. Because it is not available in either (1) JVM system property 'env_meta', (2) OS env variable 'ENV_META' nor (3) property 'env_meta' from the properties InputStream.
    2018-10-31 14:31:21.682  WARN [retail-logistics,,,] 28125 --- [main] o.s.c.a.ConfigurationClassPostProcessor  : Cannot enhance @Configuration bean definition 'com.ctrip.framework.apollo.spring.boot.ApolloAutoConfiguration' since its singleton instance has been created too early. The typical cause is a non-static @Bean method with a BeanDefinitionRegistryPostProcessor return type: Consider declaring such methods as 'static'.
    2018-10-31 14:31:22.292  WARN [retail-logistics,,,] 28125 --- [main] o.s.b.c.p.PropertySourcesDeducer         : Multiple PropertySourcesPlaceholderConfigurer beans registered [propertySourcesPlaceholderConfigurer, org.springframework.context.support.PropertySourcesPlaceholderConfigurer], falling back to Environment
    2018-10-31 14:31:24.947  WARN [retail-logistics,,,] 28125 --- [localhost-startStop-1] c.n.c.sources.URLConfigurationSource     : No URLs will be polled as dynamic configuration sources.
    2018-10-31 14:31:34.405  WARN [retail-logistics,,,] 28125 --- [main] c.n.c.sources.URLConfigurationSource     : No URLs will be polled as dynamic configuration sources.
    2018-10-31 14:31:40.317  INFO [retail-logistics,,,] 28125 --- [main] n.b.b.c.m.c.AbstractRocketmqConsumer     : 订阅消息topic:topic_logistics,tags:*
    2018-10-31 14:31:40.320  INFO [retail-logistics,,,] 28125 --- [main] n.b.b.c.m.c.AbstractRocketmqConsumer     : 启动消费组retail-logistics-consumer
    2018-10-31 14:31:40.355  INFO [retail-logistics,,,] 28125 --- [main] n.b.b.c.m.c.AbstractRocketmqConsumer     : 启动消费组retail-logistics-consumer-broadcast
    2018-10-31 14:31:40.371  INFO [retail-logistics,,,] 28125 --- [main] n.b.b.c.m.c.AbstractRocketmqConsumer     : 启动消费组retail-logistics-consumer-orderly
    2018-10-31 14:31:40.451  INFO [retail-logistics,,,] 28125 --- [main] n.b.retail.logistics.Application         : Started Application in 23.724 seconds (JVM running for 24.85)
    2018-10-31 14:35:00.063  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 14:40:00.008  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 14:45:00.012  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 14:50:00.009  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 14:55:00.007  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 15:00:00.010  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 15:05:00.013  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 15:10:00.010  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 15:15:00.007  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 15:20:00.007  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 15:25:00.006  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 15:30:00.014  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 15:35:00.009  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 15:40:00.011  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 15:45:00.007  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 15:50:00.011  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 15:55:00.008  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 16:00:00.009  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 16:05:00.020  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 16:10:00.008  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 16:15:00.009  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 16:20:00.006  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 16:25:00.008  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 16:30:00.008  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 16:35:00.007  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 16:40:00.008  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 16:45:00.008  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 16:50:00.009  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 16:55:00.008  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 17:00:00.006  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    2018-10-31 17:05:00.006  INFO [retail-logistics,,,] 28125 --- [simpleLogisticsJob_Worker-1] n.b.r.logistics.job.SimpleLogisticsJob   : execute simpleLogisticsJob
    (END)
    
    
    

    PowerDesigner连接MySQL数据库 : PowerDesigner连接MySQL数据库

    PowerDesigner逆向导入MYSQL数据库并显示中文注释:PowerDesigner逆向导入MYSQL数据库并显示中文注释

    Eureka

    问题记录一:

    • Failed to configure a DataSource: 'url' attribute is not specified and no embedded datasource could be configured.
    • Spring Boot 虽然做了很多默认的配置,但是它没办法知道你用什么数据库,数据库名称、用户名、密码是什么啊。


      image.png
    • 解决方式


      image.png

    相关文章

      网友评论

          本文标题:后台一些记录

          本文链接:https://www.haomeiwen.com/subject/rgfyzftx.html