Hi,
I have created the JIRA ticket, I will do the patch this weekend.
https://issues.apache.org/jira/browse/TOMEE-2744
--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
Hi,
Just for curiosity, I tried tomee with jdk14 (upgrading xbean). I found that
the java.security.acl package is removed from jdk14
(https://bugs.openjdk.java.net/browse/JDK-8191138 ) and
java.security.acl.Group is referenced in AbstractSecurityService (I don't
know if it is used somewhere
Hi,
We have a significant part of the project written in kotlin and I can notice
that tomee spends a lot of startup time in CdiScanner.tryToMakeItFail ,
loading kotlin generated classes like MyClass$Companion,
MyClass$WhenMappings, etc.
Is there any way I can exclude them out of the cdi scan?
Ok, please allow me this weekend to see what I can come up with
--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
Hi,
Just in case somebody needs it I wrote Junit-jupiter extensions for
ApplicationComposer and SingleApplicationComposer. They are very simple
since all the work is already done, but they may save somebody's 10 minutes.
public class ApplicationComposerExtension implements BeforeEachCallback,
I haven't found how to set org.apache.cxf.endpoint.private to an existing
endpoint, but anyway, I have split the web services into several and just
hide private wadls with a web filter.
@ApplicationPath("private-resources")
public class InternalApiRestServer extends Application {
...
}
Hi,
I just created https://issues.apache.org/jira/browse/OPENJPA-2758 . Feel
free to close it if it's not the right place. I'd be glad to help, but I'm
not using openjpa and my knowledge about it is very limited.
--
Sent from:
Shouldn't it be aligned since openjpa is now 2.2 compliant?
--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
Hi,
Using the javaee-api 8.0 library I get the following errors:
AttributeOverride is not a repeatable annotation type
NamedQuery is not a repeatable annotation type
Is the JPA spec updated to the latest 2.2?
Best regards,
Vicente.
--
Sent from:
Sorry, I made a mistake (I made the interceptor without parameters and didn't
read the tomee warnings)
It works with an ejb-jar.xml
http://xmlns.jcp.org/xml/ns/javaee;
version="3.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
Hi,
Is there any way to apply a CDI interceptor to existing @Schedule without
explicitly usign @Interceptors in all methods? I haven't found anything in
the spec.
Or is there any easy way to create my own @Schedule CDI interceptor?
Thanks in advance.
--
Sent from:
https://github.com/apache/tomee/pull/164
--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
Hi,
I noticed in latest tomee 8 an incompatibility between versions used in
wss4j and xmlsec (2.0.6)
The stacktrace is:
java.lang.NoSuchMethodError:
org.apache.xml.security.utils.XMLUtils.encodeToString([B)Ljava/lang/String;
at
Great news!
Looking forward for a tomee 8 release, we have been using it for a couple of
months now (building from source and private releases), and I can confirm
that it works fine with java 10
--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
Romain, one question. You said that if I was using it outside a transaction I
should clear myself the entityManager.
But looking at the JtaEntityManager it does nothing in that case:
public void clear() {
if (!extended && !isTransactionActive()) {
return;
}
Thx Chongma, but one question.
Let's say I also want to use that MyRepo1 from a @Stateless @Scheduled (so
no request context). How can I produce that same entityManager?
--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
Hi,
Calling entityManager.clear() seems the best approach since most of the
queries are not executed inside a transaction. But I have no idea on where I
should use it or what would be a good implementation pattern.
I mean, let's say I have a @ViewScoped with a couple of injected
My xmx is 11g right now, I need it this way or production environment will
end up doing full gc. The heapdump is taken after a GC.
I think the problem comes from eclipselink. We have some caches. Those
caches are storing some entities which are in fact storing lazy relations.
In case of a
Hi,
We are having some memory problems in our applications. We are using tomee
7.0.4 with eclipselink, no second cache level. Most of the application are
@ApplicationScoped.
Transaction is managed by container (JTA), no extended transactions at all,
everything we do with persistence is through
Hi,
One question about future TomEE 8. Would it be compatible with java 9? (I
mean project compiled to java 9, I can run tomee 7 with java 9 runtime but I
have to compile to java 8).
--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
The error is a problem with hibernate and lazy collections. Try returning
just a mocked object, not from database.
Jackson works in tomee, to get it working you need a @Producer
@Provider
@Consumes(MediaType.APPLICATION_JSON)
@Produces(MediaType.APPLICATION_JSON)
public class
Hi,
I'm thinking of migrating to gradle, we build, start and stop our tomee with
the maven plugin, so I was wondering if there are plans to implement the
tomee plugin for gradle.
It won't be very hard to have a dedicated pom for that and call it from
gradle, but it's not the ideal situation.
Just define the datasource with the javamelody JdbcDriver. Mine is defined in
resources.xml
DriverClassName net.bull.javamelody.JdbcDriver
ConnectionProperties driver=org.mariadb.jdbc.Driver;
JdbcDriver org.mariadb.jdbc.Driver
InitialSize 5
MaxActive
Ok, thanks
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/7-0-3-release-tp4681145p4681149.html
Sent from the TomEE Users mailing list archive at Nabble.com.
Hi,
I would like to request, if possible, a 7.0.3 release. I read in other posts
that there is nothing really pending for a (minor) new release.
There are some bug fixes (most notable the CUTask one) that we have patched
into our server, it's a minor inconvenience for us to work on snapshots,
Sure, I'll do it. I can also try to see if I can arrange a pull request for
this case... I haven't looked into it but it doesn't sound too difficult (I
think)
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/openejb-jpa-auto-scan-error-tp4680980p4680983.html
Sent from
Hi,
I just tried the openejb.jpa.auto-scan switch to avoid an additional
scanning, which is a very good idea. However I get an error because the
provider doesn't recognise converters... maybe they should be added to the
scanned classes? (I'm using eclipselink).
The error says:
The converter
Hi,
I wish we could use 1 minute timeout... travel industry is not the most
advanced tecnologically some bookings take as long as 2 minutes and
timeouts are very frequent. Some providers even use screen scrapping, so
they are not very reliable.
We use different timeouts depending on the
)
>> private ManagedExecutorService executor;
>>
>>
>>
>>
>> Romain Manni-Bucau
>> @rmannibucau <https://twitter.com/rmannibucau> | Blog
>> <https://blog-rmannibucau.rhcloud.com> | Old Blog
>> <http://rmannibucau.wordpress.com> |
| Old Blog
> <http://rmannibucau.wordpress.com> | Github <https://github.com/
> rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> <https://javaeefactory-rmannibucau.rhcloud.com>
>
> 2017-01-29 13:48 GMT+01:00 cocorossel
I made an ApplicationComposer test (AsyncInterceptorIT) in that github
project (with latest SNAPSHOT)
https://github.com/cocorossello/tomee-example
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/MDC-and-Asynchronous-tp4680927p4680971.html
Sent from the TomEE Users mailing list a
Tested, it is faster now.
Thank you!
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/Tomee-7-0-2-performance-tp4680954p4680970.html
Sent from the TomEE Users mailing list archive at Nabble.com.
No, I already tried setting that in system.properties with no luck. Regarding
the security manager, I have no clue on how to do that so I guess not.
I think the problem is in
org.apache.openejb.assembler.classic.EntityManagerFactoryCallable.getProvider
() 0.0 ms (0%) 6,583 ms (0.7%)
The problem has to be in JTAEntityManager.isJPA21, now is much slower.
org.apache.openejb.persistence.JtaEntityManager. (String,
org.apache.openejb.persistence.JtaEntityManagerRegistry,
javax.persistence.EntityManagerFactory, java.util.Map, boolean, String) 91.7
ms (0.3%) 10,206 ms (1%)
Hi,
I can see that the big difference is in
org.apache.openejb.persistence.JtaEntityManager. (String,
org.apache.openejb.persistence.JtaEntityManagerRegistry,
javax.persistence.EntityManagerFactory, java.util.Map, boolean, String)
75.6ms in 7.0.1 and 9631 in 7.0.2 (no other change involved at
Hi,
Since I upgraded to tomee 7.0.2, from 7.0.1 I can see a signficant
performance degradation, not a stopper, but I'm wondering if this has been
identified.
I can see that the startup time increases from 27 seconds to 35. And our end
to end test suite (about 60 parallel phantomjs tests) takes
Thank you!
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/MDC-and-Asynchronous-tp4680927p4680946.html
Sent from the TomEE Users mailing list archive at Nabble.com.
I couldn't get the attachment to work , I made a github project
https://github.com/cocorossello/tomee-example
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/MDC-and-Asynchronous-tp4680927p4680943.html
Sent from the TomEE Users mailing list archive at Nabble.com.
Hi,
I think it is something related with tomee. I made a very simple webapp
showing the error, just the interceptor and 1 async method.
Can you please try it?
mvn clean install tomee:start
and go to http://localhost:8080/index.xhtml and reload 2 or 3 times, the
error should happen
Sorry, I
I'm not using EjbContext at all. It isn't MDC problem as well, I don't really
know what's going on, the inerceptor is fairly simple.
@AroundInvoke
public Object submitAsync(InvocationContext ctx) throws Exception {
if (executor == null) {
executor =
Tomee 7.0.1 BTW , we didn't upgrade to 7.0.2
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/MDC-and-Asynchronous-tp4680927p4680938.html
Sent from the TomEE Users mailing list archive at Nabble.com.
Since I deployed the interceptor I can see some random errors happening in
different points:
java.util.ConcurrentModificationException: null
at java.util.HashMap$HashIterator.nextNode(HashMap.java:1437)
at java.util.HashMap$EntryIterator.next(HashMap.java:1471)
at
I finally went without the managedTask, simpler (I couldn't get the resource
inyection, I don't know why, with priority and declaring it in beans.xml)
@InterceptorBinding
@Target({TYPE, METHOD})
@Retention(RUNTIME)
@Inherited
public @interface Async {
}
@Async
@Interceptor
public class
;https://github.com/
> rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> <https://javaeefactory-rmannibucau.rhcloud.com>
>
> 2017-01-25 13:24 GMT+01:00 cocorossello <[hidden email]
> <http:///user/SendEmail.jtp?type=node=46809
I got it, this is the code just in case anyone needs it.
@InterceptorBinding
@Target({TYPE, METHOD})
@Retention(RUNTIME)
@Inherited
public @interface Async {
}
@Async
@Interceptor
public class AsyncInterceptor implements Serializable {
@Resource(name = "TravelcAsynchronousPool")
No, the class not found was my issue because I disabled scanning, sorry.
The point is that the apache EL implementation is being used instead of the
glassfish one, it shouldn't be this way.
Let me see if I can get an example.
--
View this message in context:
Hi,
Just a quick question about upcoming 7.0.2 release.
We are using glassfish EL implementation:
org.apache.myfaces.EXPRESSION_FACTORY
com.sun.el.ExpressionFactoryImpl
It is working fine in 7.0.1 with myfaces 2.2.11, but with tomee 7.0.2 I can
see that the apache one
Thanks Romain
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/Throttle-Asynchronous-calls-tp4680188p4680190.html
Sent from the TomEE Users mailing list archive at Nabble.com.
I have an application that calls multiple external web services and each one
of them has specific limits, so I would like to throttle concurrent calls
based on a just plain number (at least for now).
I was about to implement a custom interceptor for this, something like:
@Throttle(max=5)
Hi,
I think there is an error in tomee-maven-plugin documentation. Doc says
there is keepServerXmlAsthisattribute but it's not in the source code. In
tomee-embedded-plugin the docs say that the attribute name is
keepServerXmlAsThis (uppercase T). That attribute does exist in the
embedded
Hi,
If I switch on session serialization I get an error:
Cannot serialize session attribute openWebBeansSessionContext for session
90BB07C251DC2CDEF5BFFFD4FAF87335.D0
java.io.NotSerializableException:
org.apache.webbeans.container.BeanManagerImpl
at
Hi,
I'm trying to implement an "autostop" bash (or equivalent) script for tomcat
(I want to implement an "autoscaled" cluster, although I'm a newbie on
this).
The script would check for active sessions and stop the server (and the VM)
whenever is 0, but we also need to look for active
Got it, I just had to set the system property in the maven surefire plugin
org.apache.maven.plugins
maven-surefire-plugin
Hi,
We have tomee with logback, which is great. The problem is that I'm not able
to use logback in an arquillian test with tomee-embedded. The tomee output
seems to be using log4j for some reason. Logback/slf4j dependencies are in
classpath and logback.xml is provided
Did someone solve it?
--
Hi Romain,
I don't know how to take a sample project without taking the whole entity
model, which is big now.
I'll try to share that jstack to see if it helps.
--
View this message in context:
Hi,
I can confirm that the problem still exists with bval (it performs much
better but still slow).
The screen is a typical crud screen with a data table and a form to
create/update. The list is now fast but it takes a few seconds to save the
entity. The entity has several oneToMany associations
Hi,
I would like to skip some jar files from scanning so I put them in
catalina.properties...
tomcat.util.scan.StandardJarScanFilter.jarsToSkip=\
tr2*.jar
(I excluded all the default files from the post)
Even though it's there I can see it on the logs:
DEBUG
Hi,
I don't know if I should report this or I should wait till final release.
We are hitting performance problems with primefaces datatables with
checkboxes in it listing eclipselink entities, 10 or 20 seconds to render a
page.
The problem is that a lot of exceptions (millions) are thrown
2.6.1
But the problem is not only with eclipselink, it just becomes more evident
with it.
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/Performance-problems-in-tomee-7-0-0-tp4677292p4677296.html
Sent from the TomEE Users mailing list archive at Nabble.com.
I don't know how to use the container provided validator... Is there another
validator besides bval?
Do you think it's safe to use bval 0.5?
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/Performance-problems-in-tomee-7-0-0-tp4677292p4677298.html
Sent from the
I'll just use bval snapshot downloaded from jenkins, it works fine.
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/Performance-problems-in-tomee-7-0-0-tp4677292p4677300.html
Sent from the TomEE Users mailing list archive at Nabble.com.
Just in case someone needs it, there is a "bug" in tomcat 8 EL implementation
which converts empty request parameters into empty strings (instead of
nulls)
http://stackoverflow.com/questions/4192/tomcat-8-coerce-behaviour-null-strings-are-incorrectly-set-as-empty-strings
--
View this
Hi,
I have some dependencies (omnifaces) that changed to CDI 1.1 but we are
still in tomee 1.7.2. I wonder if it's possible to switch CDI to 1.1 since
we have a nasty startup error when DeploymentLoader tries to read the
element in beans.xml file.
--
View this message in context:
We have an application which is already live but we don't have a heavy
workload right now (but it will increase in the next few months hopefully),
do you think we can try to upgrade to tomee 7.0.0 for production or should
we stick to 1.7.2 until 7.0 is released?
--
View this message in context:
Ok, I'll wait for the answer. I just tried the latest snapshot and everything
works fine so far.
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/Upgrade-to-CDI-1-1-in-tomee-1-7-2-tp4676543p4676550.html
Sent from the TomEE Users mailing list archive at Nabble.com.
Yes, there are some differences, specially in the exception handling. I'm not
in production yet so I have time to test and fix the problems.
Thanks
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/Upgrade-myfaces-version-in-Tomee-1-7-0-tp4671458p4671466.html
Sent
I have tried with tracking-mode, but still does not work. After the session
is serialized tomcat shows login page, giving me no chance to execute a
webFilter or whatever so I could just perform a request.login() with the
user and password. SessionListener won't work either as the session is not
67 matches
Mail list logo
