RESTEASY003215: could not find writer for content-type text/plain type: java.lang.String
by Manuel Finelli
Hi all,
I would like to ask the community for help with an issue we are experiencing running the Long Running Action module of Narayana in WildFly. Going straight to the point, we are experiencing a funny issue when a thread from ForkJoin pool is used to manage expired LRA transactions: in the `try/catch` block at [1], the following exception is thrown:
```javax.ws.rs.ProcessingException: RESTEASY004655: Unable to invoke request: javax.ws.rs.ProcessingException: RESTEASY003215: could not find writer for content-type text/plain type: java.lang.String```
We arrive at that `try/catch` block from this async call [2]. It seems that the request from the coordinator to the participant [3] fails because there is no provider for "content-type text/plain type: java.lang.String" (which sounds strange as this should be one of the basic providers).
We see this exception when the Narayana LRA WAR is deployed to WildFly and also when the LRA coordinator is provided as a feature pack. Also, the same exception is thrown when the TransactionReaper thread (a standard Thread implementing Runnable) is employed to handle expired LRA transactions (we would prefer to use TransactionReaper since we also employ it in the JTA module to manage transaction timeouts).
We know that the best practise would be to use a managed thread pool but we want to keep Narayana LRA independent from any container.
To temporarily overcome this issue, we used a dedicated ThreadPool
```private static final BlockingQueue<Runnable> queue = new ArrayBlockingQueue<>(100);
private static final ExecutorService EXECUTOR_SERVICE = new ThreadPoolExecutor(10, 10, 0L, TimeUnit.MICROSECONDS, queue);```
in [2], i.e.
```CompletableFuture.supplyAsync(this::cancelLRA, EXECUTOR_SERVICE);```
This fixes the issue...but to us it looks more like a workaround rather than a solution. This workaround is going to be merged (again) in our current main branch (PR 1907 [4]).
Some extra info about this issue:
* Narayana uses RESTEasy 3.9.1
* I have tried to use RESTEasy 4.7.1 but with no luck
* According with James (hopefully, I have reported this well), ResteasyContext map is empty and the reason does not seem to be related to the use of a non-managed thread
[1]: https://github.com/jbosstm/narayana/blob/44cb48e1d4d93045a138f182153cce6e...
[2]: https://github.com/jbosstm/narayana/blob/44cb48e1d4d93045a138f182153cce6e...
[3]: https://github.com/jbosstm/narayana/blob/44cb48e1d4d93045a138f182153cce6e...
[4]: https://github.com/jbosstm/narayana/pull/1907
3 years, 3 months
Release Announcement: General Availability of Java 17 / JDK 17
by Rory O'Donnell
Hi David & Richard,
*Release Announcement: General Availability of Java 17 / JDK 17 *
**
* JDK 17, the reference implementation of Java 17, is now Generally
Available. [1]
* GPL-licensed OpenJDK builds from Oracle are available here:
https://jdk.java.net/17/ <https://jdk.java.net/17/>
* JDK 17 Release notes
<https://www.oracle.com/java/technologies/javase/17-relnotes.html>
* Inside Java: The Arrival of Java 17!
<https://inside.java/2021/09/14/the-arrival-of-java17/>
*JDK 17 includes the following features [2]:*
* JEP 306: Restore Always-Strict Floating-Point Semantics
<https://openjdk.java.net/jeps/306>
* JEP 356: Enhanced Pseudo-Random Number Generators
<https://openjdk.java.net/jeps/356>
* JEP 382: New macOS Rendering Pipeline
<https://openjdk.java.net/jeps/382>
* JEP 391: macOS/AArch64 Port <https://openjdk.java.net/jeps/391>
* JEP 398: Deprecate the Applet API for Removal
<https://openjdk.java.net/jeps/398>
* JEP 403: Strongly Encapsulate JDK Internals
<https://openjdk.java.net/jeps/403>
* JEP 406: Pattern Matching for switch (Preview)
<https://openjdk.java.net/jeps/406>
* JEP 407: Remove RMI Activation <https://openjdk.java.net/jeps/407>
* JEP 409: Sealed Classes <https://openjdk.java.net/jeps/409>
* JEP 410: Remove the Experimental AOT and JIT Compiler
<https://openjdk.java.net/jeps/410>
* JEP 411: Deprecate the Security Manager for Removal
<https://openjdk.java.net/jeps/411>
* JEP 412: Foreign Function & Memory API (Incubator)
<https://openjdk.java.net/jeps/412>
* JEP 414: Vector API (Second Incubator)
<https://openjdk.java.net/jeps/414>
* JEP 415: Context-Specific Deserialization Filters
<https://openjdk.java.net/jeps/415>
*JDK 17 will be a long-term-support (LTS) release* from most
vendors,including Oracle. If you’re upgrading from the previous LTS
release,JDK 11, then you have many more JEPs to look forward to,
summarized here:
https://openjdk.java.net/jdk/17/jeps-since-jdk-11
<https://openjdk.java.net/jdk/17/jeps-since-jdk-11>
Thanks to everyone who contributed to JDK 17, whether by creating
features or enhancements, logging bugs, or
downloading and testing the early-access builds.
*OpenJDK 18 Early Access build 14 is now available at
https://jdk.java.net/18/ <https://jdk.java.net/18/>
*
* These early access, open source builds are provided under the GNU
General Public License, version 2, with the Classpath Exception
<https://openjdk.java.net/legal/gplv2+ce.html>.
* JEPs targeted to JDK 18, so far:
o JEP 400: UTF-8 by Default <https://openjdk.java.net/jeps/400>
o JEP 413: Code Snippets in Java API Documentation
<https://openjdk.java.net/jeps/413>
* Release Notes are available at https://jdk.java.net/18/release-notes
<https://jdk.java.net/18/release-notes>
* Significant changes since the last availability email:
o JDK-8271745: Fix Issues With the KW and KWP Modes of SunJCE Provider
o JDK-8262186: Call X509KeyManager.chooseClientAlias once for all
key types
o JDK-8225083: Remove Google certificate that is expiring in
December 2021
o JDK-8251329: Zip File System Provider Throws ZipException when
entry name element contains "." or ".."
o JDK-8225082: Remove IdenTrust certificate that is expiring in
September 2021
o
*Project Loom Early-Access Builds*
* Build 18-loom+2-74 (2021/8/7) based on jdk-18+9
<https://github.com/openjdk/jdk/releases/tag/jdk-18%2B9> is
available - https://jdk.java.net/loom/ <https://jdk.java.net/loom/>
* These early access, open source builds are provided under the GNU
General Public License, version 2, with the Classpath Exception
<https://openjdk.java.net/legal/gplv2+ce.html>.
* Please send feedback via e-mail to loom-dev(a)openjdk.java.net
<mailto:loom-dev@openjdk.java.net>. To send e-mail to this address
you must first subscribe to the mailing list
<https://mail.openjdk.java.net/mailman/listinfo/loom-dev>.
Rgds,Rory
[1]
https://mail.openjdk.java.net/pipermail/jdk-dev/2021-September/006037.html
[2] https://openjdk.java.net/projects/jdk/17/
<https://openjdk.java.net/projects/jdk/17/>
3 years, 3 months
Re: wildfly-23 admin console error
by Harald Pehl
What exactly do you mean when adding a user interactively?
Adding a user using the command line should look something like this:
$ add-user.sh -u admin -p admin —silent
This adds a management user which is necessary for the admin console to
work.
What is strange is that the user has been disabled somehow. Could you
please try to provide more context how this possibly had happened?
Thanks
On 2. Sep 2021 at 16:44:49, Marlow, Andrew via wildfly-dev <
wildfly-dev(a)lists.jboss.org> wrote:
> Hello everyone,
>
>
>
> I am getting this error from the wildfly-23 admin console:
>
>
>
> If you changed your access control provider to *RBAC*, make sure that
> your configuration has current user mapped to one of the *RBAC roles*
>
>
>
> Any ideas?
>
>
>
> Here’s what I did:
>
>
>
> - Unpack wildfly zip
> - Copy standalone-full.xml to standalone-mine.xml
> - Run up wildfly with standalone-mine.xml
> - Run add-user to add an admin user
> - Disable security for activemq
> - Restart wildfly
>
>
>
> When I get this error I can use add-user to enable the user which has
> somehow got disabled. Then the admin console works.
>
>
>
> BTW: I noticed different results adding a user, depending on if I use the
> command line or not. With the command line adding doesn’t seem to work but
> going interactive does work. Also when interactive you can select admin or
> non-admin user but the command line does not have an option for specifying
> the user to be an admin user.
>
>
>
> *Andrew Marlow*
>
> Software Engineer Specialist, Apex
>
> 38th Floor, 25 Canada Square,
>
> Canary Wharf, London E14 5LQ
>
> *T*: 020-8081-2367 / 07966-451-521
> *E*: andrew.marlow(a)fisglobal.com
>
>
>
> *FIS | Advancing the way the world pays, banks and invests™ *
>
> <https://www.facebook.com/FIStoday> <https://twitter.com/FISGlobal>
> <https://www.linkedin.com/company/fis>
>
>
> The information contained in this message is proprietary and/or
> confidential. If you are not the intended recipient, please: (i) delete the
> message and all copies; (ii) do not disclose, distribute or use the message
> in any manner; and (iii) notify the sender immediately. In addition, please
> be aware that any message addressed to our domain is subject to archiving
> and review by persons other than the intended recipient. FIS is a trading
> name of the following companies: Advanced Portfolio Technologies Ltd (No:
> 6312142) | Alphakinetic Limited (No: 06897969) | Clear2Pay Limited (No:
> 5792457) | eFunds International Limited (No: 1930117) | Fidelity
> Information Services Limited (No: 2225203) | FIS Derivatives Utility
> Services (UK) Limited (No: 9398140) | FIS Energy Solutions Limited (No:
> 1889028) | FIS Global Execution Services Limited (No. 3127109) | FIS
> Capital Markets UK Limited (No: 982833) | Integrity Treasury Solutions
> Europe Limited (No: 3289271) | Metavante Technologies Limited (No: 2659326)
> | Virtus Partners Limited (No: 06602363) | all registered in England &
> Wales with their registered office at 25 Canada Square, London E14 5LQ |
> FIS Global Execution Services Limited is authorised and regulated by the
> Financial Conduct Authority | FIS Banking Solutions UK Limited (No:
> 3517639) and FIS Payments (UK) Limited (No: 4215488) both registered in
> England & Wales with their registered office at 1st Floor Tricorn House,
> 51-53 Hagley Road, Edgbaston, Birmingham, West Midlands, B16 8TU, United
> Kingdom | FIS Payments (UK) Limited is authorised and regulated by the
> Financial Conduct Authority; some services are covered by the Financial
> Ombudsman Service (in the UK) | Worldpay (UK) Limited (No: 07316500 / FCA
> No: 530923) | Worldpay Limited (No: 03424752 / FCA No: 504504) | Worldpay
> AP Limited (No: 05593466 / FCA No: 502597) all registered in England &
> Wales with their registered office at The Walbrook Building, 25 Walbrook,
> London EC4N 8AF and authorised by the Financial Conduct Authority under the
> Payment Service Regulations 2017 for the provision of payment services.
> Worldpay (UK) Limited is authorised and regulated by the Financial Conduct
> Authority for consumer credit activities | Worldpay B.V. has its registered
> office in Amsterdam, the Netherlands (Handelsregister KvK No: 60494344).
> WPBV holds a licence from and is included in the register kept by De
> Nederlandsche Bank, which registration can be consulted through www.dnb.nl.
> Clear2Pay Scotland Limited (No: SC157659), registered in Scotland with
> registered office at 19 Rose Street, Edinburgh, Scotland, EH2 2PR | Calls
> to and from the companies may be recorded for quality purposes. | All of
> the named companies are part of FIS (Fidelity National Information
> Services, Inc.).
> _______________________________________________
> wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
> To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org
> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
>
3 years, 3 months
