Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Michael Musgrove
    @mmusgrov
    That's a good suggestion. Although it's been quiet since we finished v1 of the spec, I'd imagine we'll get some questions as the implementations become available.
    Michael Musgrove
    @mmusgrov
    The microprofile spec groups also hang out on gitter so if anyone has interest in the other specs then they could join those too. For example the narayana team are contributors to the https://gitter.im/eclipse/microprofile-concurrency group.
    Moulali
    @moulalis
    Hi All
    there are many places in coordinator.java where logger in not consistent
    does it require to change for all?
    Michael Musgrove
    @mmusgrov
    I think so
    Moulali
    @moulalis
    there is also appending "e.getMessage()" that needs to be removed then, as it is not present in LraI18nLogger
    Michael Musgrove
    @mmusgrov
    Note that the exception messages should be taken directly from the logger as I suggested in one of my comments ( https://github.com/jbosstm/narayana/pull/1859#issuecomment-866185240). But don't change any of the logger messages since those are fixed.
    I'm not sure, do you have an example?
    Moulali
    @moulalis
    String errorMsg = lraId + ": Illegal LRA id format " + e1.getMessage();
    LRALogger.i18nLogger.error_invalidStringFormatOfUrl(lraId, e1);
    String errorMsg = lraId + ": Illegal LRA id format " + e1.getMessage();
    Michael Musgrove
    @mmusgrov
    where is that from. The error message can inlcude more info that
    than the log message
    Moulali
    @moulalis
    ok
    understood
    Michael Musgrove
    @mmusgrov
    You may need to change the syntax of some of the methods in LraI18nLogger to return Strings that you can then use in the body of the exception. But don't change the actual text that gets logged.
    Moulali
    @moulalis
    sure
    Michael Musgrove
    @mmusgrov
    If that means you will loose some useful message content then just append the extra text to the exception body.
    Let me find an example of where we do that ...
    Moulali
    @moulalis
    it will be good have
    Michael Musgrove
    @mmusgrov
    We don't have many examples where we add extra message text.
    There is warn_LRAStatusInDoubt and the one I included in my PR comment. But those two should give you some ideas.
    In fact those are the only two examples in the LRA portion of the codebase. There may be examples in other modules but the two I just reference will give you some hints.
    Michael Musgrove
    @mmusgrov
    So, following up on your example, I would do something like the following:
                    String logMsg = LRALogger.i18nLogger.error_invalidStringFormatOfUrl(lraId, e1);
                    LRALogger.logger.error(logMsg); // make sure that the original logging is not changed
                    String errorMsg = String.format("%s (%s)", logMsg, e1.getMessage()); // add extra text
    
                    throw new WebApplicationException(errorMsg, e1,
                            Response.status(BAD_REQUEST).entity(errorMsg).build());
    Michael Musgrove
    @mmusgrov
    I like to avoid being too verbose (since that can make text more difficult to parse, especially when code is maintained by people from multiple nationalities), hence the minimal additional text.
    But the key addition is the log message id, with that the user can navigate directly to the place where the message was generated from - reading the source is the most accurate way to understand the meaning of a log message.
    Moulali
    @moulalis
    This is perfect. Thanks
    Moulali
    @moulalis
    @mmusgrov could you please review jbosstm/narayana#1859
    Michael Musgrove
    @mmusgrov
    Thanks @moulalis I had a few changes requests but otherwise it is a good PR.
    jerypvincent
    @jerypvincent
    02:51:33.037 [Camel (camel-1) thread #3 - JmsConsumer[XXXXX.QUEUE]] DEBUG o.a.c.c.j.DefaultJmsMessageListenerContainer - Setup of JMS message listener invoker failed - already recovered by other invoker
    java.lang.ExceptionInInitializerError: null
    at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.begin(BaseTransaction.java:94)
    getting this error, any idea why its coming
    chalda
    @ochaloup
    @jerypvincent do I understand right that you're running Narayana under Camel? Is there other runtime running aside?
    What version of Narayana do you use?
    jmfinelli
    @jmfinelli
    vabgandhi
    @vabgandhi:matrix.org
    [m]
    hi, i am new to narayana. On narayana https://narayana.io/ site it is mentioned to have binding for c++
    we have c++ applications which need to use XA transactions.. could someone please point how to use narayana as transaction coordinator for c++ applications?
    jmfinelli
    @jmfinelli
    @vabgandhi:matrix.org if you want to use Narayana in a C++ application, you should consider OTS/CORBA. Have a look at the Narayana documentation. There is also a quick start project to help you getting started with OTS/JTS
    Also, you could start writing a C++ version of JTSDockerContainerTest to play with the integration
    jmfinelli
    @jmfinelli
    We are aware http://narayana.io is down and our team is working to restore it. We can be contacted on our other channels:
    Follow up -> temporary, Narayana's website is reachable at https://jbosstm.github.io
    testeradam
    @testeradam

    Hi, I implemented a Proof of concept application using Narayana Transaction Manager with Spring boot and Apache Camel framework, Active MQ as one of the
    XA resoucrce, While testing the application I noticed occasionally consumer count being increased abnormally ( Ex: 20,000+ consumers) with below error in Logs

    warn arjuna.ats.jta arjuna016061: transactionimple.enlistresource - xaresource.start returned: xaexception.xaer_proto for < formatid=131077, gtrid_length=29
    warn component.jms.defaultjmsmessagelistenercontainer setup of jms message listener invoker failed for destination 'test_queue' - trying to recover. cause: jta transaction unexpectedly rolled back (maybe due to a timeout);
    Restarting the app is bringing the consumer count to normal state.

    Apologize if I missed something, Can anyone suggest what might have caused the issue.

    I Am using the properties file as is located here

    jmfinelli
    @jmfinelli
    Hi @testeradam, thanks for reaching out to ask for help :-) If you could share your code (e.g. the git repository you are using to develop your PoC), maybe we can figure this out together
    jmfinelli
    @jmfinelli
    it would be very helpful if you could also tell us how to reproduce your scenario
    testeradam
    @testeradam
    Hi @jmfinelli , I have uploaded my repository here - https://github.com/testeradam/SpringbootNarayana2PCPOC
    I am trying to achieve distributed transactions interfacing with oracle DB and ActiveMQ broker as two resources using spring boot framework.
    Thanks in advance!
    jmfinelli
    @jmfinelli
    I will take a look ASAP :-) Thanks for sharing @testeradam
    Tom Jenkinson
    @tom_jenkinson_twitter
    Please can we talk about "testing threads"
    1 reply
    Testing threads 2
    17 replies
    Michael Musgrove
    @mmusgrov
    replying in thread
    2 replies
    Tom Jenkinson
    @tom_jenkinson_twitter
    I didn't find a way to link to single messages but I seemed to find a way to link to messages sent at a particular minute. To get a timestamp (the the minute) based link you can right click on the time of a message, for example https://gitter.im/jbosstm/community?at=6268fe9441f4560c6f72cf6e highlights both Please can we talk about "testing threads" and Testing threads 2 (both at 09:28)
    jmfinelli
    @jmfinelli
    Moving to Zulip
    11 replies
    jmfinelli
    @jmfinelli
    Great news! We have completed the configuration of our new Zulip organisation and I am happy to communicate that we are up and running at this address! Join us and start contributing to our open conversations :-)