tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roberto Cortez <>
Subject Re: Connector Resource Adapter Issues
Date Thu, 02 Jun 2016 20:05:37 GMT
Hi guys,
Another issue that I've found:

When validating Resource Adapters connections with ValidatingGenericConnectionManager, there
is a case that just hands over the pool object directly to the validate method, which may
cause multiple Timer threads to change the connections Set and cause a java.util.ConcurrentModificationException.

This time, I've also submitted a patch :)
      From: Roberto Cortez <>
 To: Romain Manni-Bucau <>; "" <>

 Sent: Friday, May 20, 2016 9:43 AM
 Subject: Re: Connector Resource Adapter Issues
Thank you Romain!
Next time, let me submit the patch myself :)
      From: Romain Manni-Bucau <>
 To: "" <>; Roberto Cortez <>

 Sent: Friday, May 20, 2016 12:01 AM
 Subject: Re: Connector Resource Adapter Issues
Hi Roberto,
Made first one not failling as a tolerance (since properties are considered as config properties
you can then say you should just put a getter).
Second one was already fixed.

Romain Manni-Bucau
@rmannibucau |  Blog | Github | LinkedIn | Tomitriber | JavaEE Factory
2016-05-20 2:14 GMT+02:00 Roberto Cortez <>:

And the issues:

      From: Roberto Cortez <>
 To: "" <>
 Sent: Thursday, May 19, 2016 4:50 PM
 Subject: Connector Resource Adapter Issues

I have been implementing a Connector Resource Adapter and run into some issues:
  -  If I add a property getter into a resourceadapter-class or into a managedconnectionfactory-class,
when deploying I get a NPE, since it expects the setter to be there. The deployed classes
are available, but configuration might not be loaded properly since the configuration load
is interrupted by the NPE. I had a look into the spec, and yes for config properties you are
required to have a getter / setter, but I couldn't find anything telling you that you can't
have a regular property with just a getter (it's just not configurable).

  - When using the configuration "validationInterval" to provide connection validation, the
connector just fails to deploy with a java.lang.NoSuchFieldException: pool

Did anyone else run into these issue?
In the meanwhile, I'm creating JIRA issue, plus tests. I would also like to fix these myself
if they confirm to be problems.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message