by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    u6f6o
    @u6f6o
    on which version was your system running the day before?
    weichao
    @iamwwc
    wait a while, I will try
    Arnaud Esteve
    @aesteve
    1/ try with milestone 3, there is a chance your code will still be compatible, and this version shouldn't have changed lately
    2 replies
    2/ try to declare a dependency to fasterxml explicitely in your pom
    weichao
    @iamwwc
    it works when I use master branch now
    I have move bug codes into addlogin branch
    Frank Lemanschik
    @frank-dspeed
    then write down the current commit it
    of the master branch
    its always clever to know the last working version
    weichao
    @iamwwc
    but my addlogin branch only use a auth0-jwt
    image.png
    Frank Lemanschik
    @frank-dspeed
    ava.lang.NoSuchMethodError: com.fasterxml.jackson.core.JsonGenerator.writeStartArray(Ljava/lang/Object;I)V
    weichao
    @iamwwc
    auth0 jwt use jackson, but it's almost latest version
    Frank Lemanschik
    @frank-dspeed
    the json generator is the problem
    weichao
    @iamwwc
    did you mean is auth0-jwt cause this bug?
    10 replies
    Frank Lemanschik
    @frank-dspeed
    maybe the method got deprecated
    NoSuchMethod is a relativ clear error
    it says that JsonGenerator has not this function
    maybe it got renamed
    weichao
    @iamwwc
    image.png
    I found it, vertx core have version conflict
    with java-jwt
    but how to fix it? can vertx update jackson version to latest?
    21 replies
    weichao
    @iamwwc
    Hi, everyone, I have a question. Did milestone4 is a snapshot version?
    which mean its code maybe changed after I reimport it in some day when though i use milestone4.0.0 version of vert.x core
    Stephan H. Wissel
    @Stwissel
    Testing question: I have a verticle that launches a set of eventBus listeners. Works like a charm. I'd like to test if the addresses are working. So I sent a bunch of messages and it looks good. Then I added in the test a non-existing address, but it still looks good. So I'm missing something:
    
      @Test
      void testVerticleMessages(final Vertx vertx, VertxTestContext testContext) {
       final EventBus eb = vertx.eventBus();      
          eb.send(EVENTBUS_LOADKEEPCONFIG_DB, this.message);
          eb.send(EVENTBUS_LOADKEEPCONFIG_APP, this.message);
          eb.send(EVENTBUS_LOADKEEPCONFIG_DXL, this.message);
          // I would expect an error here      
        eb.send("This does not exist", this.message);
          testContext.completeNow();
      }
    Arnaud Esteve
    @aesteve
    You can send messages to non-existing addresses
    in fact, there's no such thing as "non-existing adress" I'd say
    You'd like to have an indication of failure when sending a message to an address that has no consumer subscribed ? if I understand correctly
    Stephan H. Wissel
    @Stwissel
    It only fails when one "request" instead of "send" isn't it?
    Sohini Pattanayak
    @TheSohini_twitter
    Hi, all, for this piece of code -
    import io.vertx.core.AbstractVerticle;
    public class HelloMicroservice extends AbstractVerticle {
        @Override
        public void start() {
                Router router = Router.router(vertx);
                router.get("/").handler(rc -> rc.response().end("Hi"));
                router.get("/:name").handler(rc -> rc.response()
                .end("Hi"+ rc.pathParam("name")));
    
                vertx.createHttpServer()
                    .requestHandler(router::accept)
                    .listen(8080);
        }
    }
    why do i get this error [ERROR] symbol: class Router
    [ERROR] symbol: variable Router
    Arnaud Esteve
    @aesteve
    @Stwissel I have never used this request API actually, so I can't confirm. But since the 3rd parameter is a "reply handler" and no consumer is listening to the address, I guess we can by reading the docs assume the handler will either:
    • never be called at all
    • fail, mentioning that no consumer is registered on this address
      Only your test can confirm this :)
    Stephan H. Wissel
    @Stwissel
    it will fail, rather fast
    Arnaud Esteve
    @aesteve
    Ok, good to know!
    carbotaniuman
    @carbotaniuman
    Is there a way to duplicate a ReadStream, such that I can say write two files at once from a single WebClient request?
    carbotaniuman
    @carbotaniuman
    A WriteStream that redirects to two others, or one that redirects but also buffers internally would also be acceptable.
    Marco Collovati
    @mcollovati
    Hi all,
    I need help with vertx-maven-plugin, but I don't know if this is the right place to ask for;
    anyway, does someone know if there's a way to "block" vertx:start mojo until then verticle is fully deployed?
    I'm using vertx:start bound to pre-integration-test phase, but integration tests fails because verticle in not yet deployed (it takes a couple of second to be up and running).
    Arnaud Esteve
    @aesteve
    Not sure you can :s
    In the meantime, waiting for someone with good knowledge about the maven plugin to answer, maybe you could start your app in a @BeforeEach section of a vertx-junit5 test ?
    1 reply
    That's what I'm usually doing for integration-tests
    Is this a valid workaround to consider?
    4 replies
    Petr Koňárek
    @PetrosW
    hello, is there way to use https://vertx.io/docs/vertx-mysql-client/java/ without pool and with await ? something like MySQLConnection.connectAwait(vertx, connectOptions) ?
    Petr Koňárek
    @PetrosW
    good, i have solution
    for other, its that import io.vertx.kotlin.mysqlclient.* and import io.vertx.mysqlclient.MySQLConnection import same class MySQLConnection and because of that compiler didnt see MySQLConnection.connectAwait
    YangJieRong
    @Yangjierong
    we are using vertx-redis-client-3.9.0, no matter what maxPoolSize we set, we can only get 4 connections from redis pool
            int maxPoolSize = appProperties.getIntProperty("Redis.maxPoolSize");
            int maxPoolWaiting = appProperties.getIntProperty("Redis.maxPoolWaiting");
            int poolCleanerInterval = appProperties.getIntProperty("Redis.poolCleanerInterval");
            int poolRecycleTimeout = appProperties.getIntProperty("Redis.poolRecycleTimeout");
    
            RedisOptions config = new RedisOptions().setConnectionString(connectionString).setMaxPoolSize(maxPoolSize)
                    .setMaxPoolWaiting(maxPoolWaiting).setPoolCleanerInterval(poolCleanerInterval)
                    .setPoolRecycleTimeout(poolRecycleTimeout);
    
            Redis redis = Redis.createClient(App.vertx, config);
    YangJieRong
    @Yangjierong
    and vertx-mysql-client-3.9.0 has this issue:
    io.vertx.mysqlclient.MySQLException: Unknown prepared statement handler (3) given to mysqld_stmt_execute
            at io.vertx.mysqlclient.impl.codec.CommandCodec.handleErrorPacketPayload(CommandCodec.java:133)
            at io.vertx.mysqlclient.impl.codec.ExtendedQueryCommandBaseCodec.handleInitPacket(ExtendedQueryCommandBaseCodec.java:28)
            at io.vertx.mysqlclient.impl.codec.QueryCommandBaseCodec.decodePayload(QueryCommandBaseCodec.java:58)
            at io.vertx.mysqlclient.impl.codec.ExtendedQueryCommandCodec.decodePayload(ExtendedQueryCommandCodec.java:100)
            at io.vertx.mysqlclient.impl.codec.MySQLDecoder.decodePayload(MySQLDecoder.java:62)
            at io.vertx.mysqlclient.impl.codec.MySQLDecoder.decode(MySQLDecoder.java:51)
            at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:498)
            at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:437)
            at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:276)
            at io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:251)
            at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
            at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
            at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
            at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
            at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
            at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
            at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
            at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163)
            at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:714)
            at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650)
            at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576)
            at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
            at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
            at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
            at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
            at java.base/java.lang.Thread.run(Unknown Source)
    Paulo Lopes
    @pmlopes
    @Yangjierong that issue was reported on master and fixed. Can you open a issue to try to backport it to 3.9
    I was referring to redis