Re: BrokerXmlConfig property in resource element of tomee.xml file is not honoured.

[Romain Manni-Bucau]

Hi

maybe check what is used throught JMS and try an absolute path, depending
how it is started you can use a wrong relative path I think

also did you add all the needed jars (spring etc)?


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.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>

2016-11-26 11:24 GMT+01:00 Dignesh :

> HI,
>
> I am using 7.0.1 Version of TomEE plus.
>
> Below is my configuration defined in tomee.xml file.
>
> 
> DataSource test/datasource
> BrokerXmlConfig =  xbean:file:../conf/activemq.xml
> 
> 
>   ResourceAdapter = resAdapter
> 
>
> I have few destinations defined in tomee.xml file.
>
> 
> 
> 
> 
>
> And I have defined destination policies and redeliverables in activemq.xml
> file.
>
> I dont see the configuartions defined in the file are being respected by
> TomEE plus. I have attached the activemq.xml file for reference.
> activemq.xml
> <http://tomee-openejb.979440.n4.nabble.com/file/n4680645/activemq.xml>
>
> Can any one of you please help me on this .Is it a configuration where I am
> doing wrong ? Please guide me on this.
>
> Thank you very much in Advance.
>
>
>
>
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/BrokerXmlConfig-property-in-resource-element-
> of-tomee-xml-file-is-not-honoured-tp4680645.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: tomee git commit: why this got upgraded? error?

[Romain Manni-Bucau]

no more since 17 days
https://github.com/apache/tomee/commit/e88ea2fee158936f9f7230c388fb3706dd91a784
;)


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.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>

2016-11-23 22:05 GMT+01:00 Thiago Veronezi :

> That was a branch new clone. It was using the snapshot.
> https://github.com/apache/tomee/commit/0075fb5b5f235c16e5cbeb45a3d9ea
> 3532fa9081
> Well, all good now.
>
> On 23 November 2016 at 16:02, Romain Manni-Bucau 
> wrote:
>
> > Oh I see, so you were not up to date with master probably. 7.0-1 is good.
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://blog-rmannibucau.rhcloud.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>
> >
> > 2016-11-23 21:58 GMT+01:00 Thiago Veronezi :
> >
> > > Because this is a dev branch and it was using an old version of another
> > > snapshot.  Previously using 7.0-1-SNAPSHOT, breaking it im my machine.
> > I'm
> > > fine either way. Just answering the previous question.
> > >
> > > On 23 November 2016 at 15:54, Romain Manni-Bucau <
> rmannibu...@gmail.com>
> > > wrote:
> > >
> > > > Sorry Thiago, not understanding what you mean. javaee-api and tomee
> are
> > > not
> > > > aligned and there was not a single commit on javaee-api since 7.0-1
> so
> > > why
> > > > using a snapshot?
> > > >
> > > >
> > > > Romain Manni-Bucau
> > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > > <https://blog-rmannibucau.rhcloud.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>
> > > >
> > > > 2016-11-23 21:53 GMT+01:00 Thiago Veronezi :
> > > >
> > > > > Because it was using old version.
> > > > >
> > > > > https://git1-us-west.apache.org/repos/asf?p=tomee.git;a=
> > > > > commitdiff;h=0075fb5b
> > > > >
> > > > > On 23 November 2016 at 15:30,  wrote:
> > > > >
> > > > > > Repository: tomee
> > > > > > Updated Branches:
> > > > > >   refs/heads/master 0075fb5b5 -> dc475ca49
> > > > > >
> > > > > >
> > > > > > why this got upgraded? error?
> > > > > >
> > > > > >
> > > > > > Project: http://git-wip-us.apache.org/repos/asf/tomee/repo
> > > > > > Commit: http://git-wip-us.apache.org/repos/asf/tomee/commit/
> > dc475ca4
> > > > > > Tree: http://git-wip-us.apache.org/repos/asf/tomee/tree/dc475ca4
> > > > > > Diff: http://git-wip-us.apache.org/repos/asf/tomee/diff/dc475ca4
> > > > > >
> > > > > > Branch: refs/heads/master
> > > > > > Commit: dc475ca49582c5d25eac2bd82d64aebb20929e32
> > > > > > Parents: 0075fb5
> > > > > > Author: rmannibucau 
> > > > > > Authored: Wed Nov 23 21:30:30 2016 +0100
> > > > > > Committer: rmannibucau 
> > > > > > Committed: Wed Nov 23 21:30:30 2016 +0100
> > > > > >
> > > > > > 
> > > --
> > > > > >  pom.xml | 2 +-
> > > > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > > > > 
> > > --
> > > > > >
> > > > > >
> > > > > > http://git-wip-us.apache.org/repos/asf/tomee/blob/dc475ca4/
> pom.xml
> > > > > > 
> > > --
> > > > > > diff --git a/pom.xml b/pom.xml
> > > > > > index ecfef94..34274d1 100644
> > > > > > --- a/pom.xml
> > > > > > +++ b/pom.xml
> > > > > > @@ -94,7 +94,7 @@
> > > > > >  ${project.version}
> > > > > >
> > > > > >  
> > > > > > -7.0-2-SNAPSHOT
> > > > > > +7.0-1
> > > > > >
> > > > > >  2.4.1
> > > > > >  1.7.0 > > > > > openwebbeans.version>
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: tomee git commit: why this got upgraded? error?

[Romain Manni-Bucau]

Oh I see, so you were not up to date with master probably. 7.0-1 is good.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.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>

2016-11-23 21:58 GMT+01:00 Thiago Veronezi :

> Because this is a dev branch and it was using an old version of another
> snapshot.  Previously using 7.0-1-SNAPSHOT, breaking it im my machine. I'm
> fine either way. Just answering the previous question.
>
> On 23 November 2016 at 15:54, Romain Manni-Bucau 
> wrote:
>
> > Sorry Thiago, not understanding what you mean. javaee-api and tomee are
> not
> > aligned and there was not a single commit on javaee-api since 7.0-1 so
> why
> > using a snapshot?
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://blog-rmannibucau.rhcloud.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>
> >
> > 2016-11-23 21:53 GMT+01:00 Thiago Veronezi :
> >
> > > Because it was using old version.
> > >
> > > https://git1-us-west.apache.org/repos/asf?p=tomee.git;a=
> > > commitdiff;h=0075fb5b
> > >
> > > On 23 November 2016 at 15:30,  wrote:
> > >
> > > > Repository: tomee
> > > > Updated Branches:
> > > >   refs/heads/master 0075fb5b5 -> dc475ca49
> > > >
> > > >
> > > > why this got upgraded? error?
> > > >
> > > >
> > > > Project: http://git-wip-us.apache.org/repos/asf/tomee/repo
> > > > Commit: http://git-wip-us.apache.org/repos/asf/tomee/commit/dc475ca4
> > > > Tree: http://git-wip-us.apache.org/repos/asf/tomee/tree/dc475ca4
> > > > Diff: http://git-wip-us.apache.org/repos/asf/tomee/diff/dc475ca4
> > > >
> > > > Branch: refs/heads/master
> > > > Commit: dc475ca49582c5d25eac2bd82d64aebb20929e32
> > > > Parents: 0075fb5
> > > > Author: rmannibucau 
> > > > Authored: Wed Nov 23 21:30:30 2016 +0100
> > > > Committer: rmannibucau 
> > > > Committed: Wed Nov 23 21:30:30 2016 +0100
> > > >
> > > > 
> --
> > > >  pom.xml | 2 +-
> > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > > 
> --
> > > >
> > > >
> > > > http://git-wip-us.apache.org/repos/asf/tomee/blob/dc475ca4/pom.xml
> > > > 
> --
> > > > diff --git a/pom.xml b/pom.xml
> > > > index ecfef94..34274d1 100644
> > > > --- a/pom.xml
> > > > +++ b/pom.xml
> > > > @@ -94,7 +94,7 @@
> > > >  ${project.version}
> > > >
> > > >  
> > > > -7.0-2-SNAPSHOT
> > > > +7.0-1
> > > >
> > > >  2.4.1
> > > >  1.7.0 > > > openwebbeans.version>
> > > >
> > > >
> > >
> >
>

Re: tomee git commit: why this got upgraded? error?

[Romain Manni-Bucau]

Sorry Thiago, not understanding what you mean. javaee-api and tomee are not
aligned and there was not a single commit on javaee-api since 7.0-1 so why
using a snapshot?


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.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>

2016-11-23 21:53 GMT+01:00 Thiago Veronezi :

> Because it was using old version.
>
> https://git1-us-west.apache.org/repos/asf?p=tomee.git;a=
> commitdiff;h=0075fb5b
>
> On 23 November 2016 at 15:30,  wrote:
>
> > Repository: tomee
> > Updated Branches:
> >   refs/heads/master 0075fb5b5 -> dc475ca49
> >
> >
> > why this got upgraded? error?
> >
> >
> > Project: http://git-wip-us.apache.org/repos/asf/tomee/repo
> > Commit: http://git-wip-us.apache.org/repos/asf/tomee/commit/dc475ca4
> > Tree: http://git-wip-us.apache.org/repos/asf/tomee/tree/dc475ca4
> > Diff: http://git-wip-us.apache.org/repos/asf/tomee/diff/dc475ca4
> >
> > Branch: refs/heads/master
> > Commit: dc475ca49582c5d25eac2bd82d64aebb20929e32
> > Parents: 0075fb5
> > Author: rmannibucau 
> > Authored: Wed Nov 23 21:30:30 2016 +0100
> > Committer: rmannibucau 
> > Committed: Wed Nov 23 21:30:30 2016 +0100
> >
> > --
> >  pom.xml | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > --
> >
> >
> > http://git-wip-us.apache.org/repos/asf/tomee/blob/dc475ca4/pom.xml
> > --
> > diff --git a/pom.xml b/pom.xml
> > index ecfef94..34274d1 100644
> > --- a/pom.xml
> > +++ b/pom.xml
> > @@ -94,7 +94,7 @@
> >  ${project.version}
> >
> >  
> > -7.0-2-SNAPSHOT
> > +7.0-1
> >
> >  2.4.1
> >  1.7.0 > openwebbeans.version>
> >
> >
>

Re: TomEE servers are getting stopped in the middle of the day and is throwing "Caused by: org.apache.openjpa.persistence.Persisten

[Romain Manni-Bucau]

2016-11-18 18:34 GMT+01:00 lreddy :

> Here is the version number:Server number:  7.0.55.0
>
>
Looks like an old one, we got several fixes which can be related. Here the
tests I would recommand:

1. move to dbcp pooling (DataSourceCreator = dbcp)
2. ensure you evict the pool properly (check TestWhileIdle/ValidationQuery
properties)

If it happens again check the pool properties through JMX and get a thread
dump.


> We didn't put any of the properties with respect to eviction. Do you
> recommend any properties that I have to configure with respect to eviction?
>
>
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/TomEE-servers-are-getting-stopped-in-the-
> middle-of-the-day-and-is-throwing-Caused-by-openjpa-2-
> 4-0-n-tp4680592p4680594.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: TomEE servers are getting stopped in the middle of the day and is throwing "Caused by: org.apache.openjpa.persistence.Persisten

[Romain Manni-Bucau]

Hi

does it happen on 7.0.2? Did you configure eviction on the database (no
link with the stateless pool)?


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.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>

2016-11-18 16:27 GMT+01:00 lreddy :

> one of our applicaiton is deployed in TomEE and I am not sure what causing
> but JVM is getting stopped in the middle of the business day and eventually
> someone has to go in and manually restart the server.
>
> when we checked the logs, it is throwing this error
>
> Caused by:  error> org.apache.openjpa.persistence.PersistenceException: Pool wait
> interrupted.
> at org.apache.openjpa.jdbc.sql.DBDictionary.narrow(
> DBDictionary.java:4998)
> at
> org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(
> DBDictionary.java:4958)
> at
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:134)
> at
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:108)
> at
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:60)
> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.
> connect(JDBCStoreManager.java:968)
> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.getConnection(
> JDBCStoreManager.java:242)
> at
> org.apache.openjpa.jdbc.kernel.PreparedSQLStoreQuery$PreparedSQLExecutor.
> executeQuery(PreparedSQLStoreQuery.java:104)
> at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.
> java:1005)
> at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:863)
> at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:794)
> at
> org.apache.openjpa.kernel.DelegatingQuery.execute(
> DelegatingQuery.java:542)
> at org.apache.openjpa.persistence.QueryImpl.execute(
> QueryImpl.java:275)
> at
> org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:291)
> at
> org.apache.openejb.core.cmp.jpa.JpaCmpEngine.executeSelectQuery(
> JpaCmpEngine.java:280)
> at
> org.apache.openejb.core.cmp.jpa.JpaCmpEngine.queryBeans(
> JpaCmpEngine.java:234)
> at
> org.apache.openejb.core.cmp.CmpContainer.findEJBObject(
> CmpContainer.java:702)
> at org.apache.openejb.core.cmp.CmpContainer.invoke(
> CmpContainer.java:271)
> at
> org.apache.openejb.core.entity.EntityEjbHomeHandler.
> findX(EntityEjbHomeHandler.java:65)
> at
> org.apache.openejb.core.ivm.EjbHomeProxyHandler._invoke(
> EjbHomeProxyHandler.java:202)
> ... 52 more
> Caused by: java.sql.SQLException: Pool wait interrupted.
> at
> org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(
> ConnectionPool.java:655)
> at
> org.apache.tomcat.jdbc.pool.ConnectionPool.getConnection(
> ConnectionPool.java:188)
> at
> org.apache.tomcat.jdbc.pool.DataSourceProxy.getConnection(
> DataSourceProxy.java:128)
> at
> org.apache.openjpa.lib.jdbc.DelegatingDataSource.getConnection(
> DelegatingDataSource.java:110)
> at
> org.apache.openjpa.lib.jdbc.DecoratingDataSource.getConnection(
> DecoratingDataSource.java:87)
> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connectInternal(
> JDBCStoreManager.java:979)
> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.
> connect(JDBCStoreManager.java:964)
> ... 66 more
> Caused by: java.lang.InterruptedException
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.
> doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1038)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.
> tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1326)
> at java.util.concurrent.CountDownLatch.await(
> CountDownLatch.java:282)
> at
> org.apache.tomcat.jdbc.pool.FairBlockingQueue.poll(
> FairBlockingQueue.java:151)
> at
> org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(
> ConnectionPool.java:650)
> ... 72 more
>
> Here are some of the properties for our applicaiton
>
> myStatelessContainer = new://Container?type=STATELESS
> myStatelessContainer.accessTimeout = 30 seconds
> myStatelessContainer.callbackThreads = 5
> myStatelessContainer.closeTimeout = 5 minutes
> myStatelessContainer.garbageCollection = false
> myStatelessContainer.idleTimeout = 0 minutes
> myStatelessContainer.maxAge = 0 hours
> myStatelessContainer.maxAgeOffset = -1
> myStateless

Re: MaxTotal vs MaxActive in Tomcat/DBCP db pools in TomEE 7

[Romain Manni-Bucau]

2016-11-17 14:25 GMT+01:00 Jonathan Gallimore 
:

> Thanks for the reply, and clarifying the design choice. I'll hold off
> changing anything, unless this discussion changes direction.
>
> I did update the documentation on the website which will hopefully help
> anyone else who might run into this issue. Hope that is ok with everyone.
>
>
You rock man!

Note on that: dbcp seems to have removed dbcp1 doc (tomee 1), not sure
where we can find it anymore.


> Regards
>
> Jon
>
>
>
> On Thu, Nov 17, 2016 at 1:21 PM, Romain Manni-Bucau  >
> wrote:
>
> > Hi Jon,
> >
> > when migrating and for 7.x the choice was to get rid of most of our
> > defaults and just ensure we map to the defaults of the underlying pool -
> > think I sent a mail months (years?) ago. Goal was really have the pool
> you
> > use config and not something vaguely defined or require the user which
> can
> > know the pool for other application to learn another way to use this pool
> > with tomee.
> >
> > Hope it makes sense.
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://blog-rmannibucau.rhcloud.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>
> >
> > 2016-11-17 14:15 GMT+01:00 Jonathan Gallimore <
> > jonathan.gallim...@gmail.com>
> > :
> >
> > > Hi
> > >
> > > I discovered that in TomEE 7, when using DBCP as my data source
> creator,
> > I
> > > needed to use the "MaxTotal" property as opposed to the "MaxActive"
> > > property, which the Tomcat creator would use.
> > >
> > > Does it make sense for us to "map" MaxActive to MaxTotal so these are
> > > consistent and save any confusion? If so, I'd like to make the change -
> > > just wanted to gather some opinion before going ahead.
> > >
> > > Many thanks
> > >
> > > Jon
> > >
> >
>

Re: MaxTotal vs MaxActive in Tomcat/DBCP db pools in TomEE 7

[Romain Manni-Bucau]

Hi Jon,

when migrating and for 7.x the choice was to get rid of most of our
defaults and just ensure we map to the defaults of the underlying pool -
think I sent a mail months (years?) ago. Goal was really have the pool you
use config and not something vaguely defined or require the user which can
know the pool for other application to learn another way to use this pool
with tomee.

Hope it makes sense.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.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>

2016-11-17 14:15 GMT+01:00 Jonathan Gallimore 
:

> Hi
>
> I discovered that in TomEE 7, when using DBCP as my data source creator, I
> needed to use the "MaxTotal" property as opposed to the "MaxActive"
> property, which the Tomcat creator would use.
>
> Does it make sense for us to "map" MaxActive to MaxTotal so these are
> consistent and save any confusion? If so, I'd like to make the change -
> just wanted to gather some opinion before going ahead.
>
> Many thanks
>
> Jon
>

Re: [RESULT][VOTE] Apache TomEE 7.0.2

[Romain Manni-Bucau]

should be done now


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.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>

2016-11-17 12:34 GMT+01:00 Jonathan Gallimore 
:

> Hey Romain
>
> Thanks for this. Are you able to push the 7.0.2 tag? I'm not seeing it
> here: https://git-wip-us.apache.org/repos/asf?p=tomee.git
>
> Thanks in advance.
>
> Jon
>
> On Fri, Nov 11, 2016 at 6:45 PM, Romain Manni-Bucau  >
> wrote:
>
> > Which makes 5 +1 (3 bindings with Mark, JL and mine) and no other votes
> so
> > it passes :). Will continue with release steps.
> >
> > Thanks to all people having answered!
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://blog-rmannibucau.rhcloud.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>
> >
> > 2016-11-11 19:41 GMT+01:00 Jean-Louis Monteiro  >:
> >
> > > thanks Romain.
> > >
> > > here is my +1
> > >
> > > Le 11 nov. 2016 19:40, "Felipe Jaekel"  a écrit :
> > >
> > > > I had some classes that were incorrectly implementing Serializable
> > > >
> > > > It is working fine now
> > > >
> > > > Thanks
> > > >
> > > > 2016-11-07 10:33 GMT-02:00 Romain Manni-Bucau  >:
> > > >
> > > > > PS: should be working for 7.0.3 (
> > > > > https://issues.apache.org/jira/browse/TOMEE-1965) but maybe also
> > check
> > > > why
> > > > > you serialize an entity manager (this never sounds safe since it
> > breaks
> > > > > several parts of JPA with most providers)
> > > > >
> > > > >
> > > > > Romain Manni-Bucau
> > > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > > > <https://blog-rmannibucau.rhcloud.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>
> > > > >
> > > > > 2016-11-07 13:23 GMT+01:00 Romain Manni-Bucau <
> rmannibu...@gmail.com
> > >:
> > > > >
> > > > > > think it can be solved setting tomee.jpa.cdi=false
> > > > > >
> > > > > >
> > > > > > Romain Manni-Bucau
> > > > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > > > > <https://blog-rmannibucau.rhcloud.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>
> > > > > >
> > > > > > 2016-11-07 13:16 GMT+01:00 Felipe Jaekel :
> > > > > >
> > > > > >> Hi,
> > > > > >>
> > > > > >> +1 as I've been using apache-tomee-7.0.2-20160726.
> 041804-27-plus
> > on
> > > > > >> production without problems.
> > > > > >>
> > > > > >> One detail is that with version 7.0.2-20161107.040545-131 I'm
> > > getting
> > > > a
> > > > > >> *java.io.NotSerializableException* when I run arquillian tests
> on
> > > > > >> Jenkins.
> > > > > >> It started some weeks ago. Sorry to mention it only now. I
> didn't
> > > had
> > > > > time
> > > > > >> to report it on the user list when I first saw the problem, so I
> > > just
> > > > > >> changed the maven dependency to 7.0.1 and ended up forgetting
> > about
> > > > > it...
> > > > > >>
> > > > > >> Local

[RESULT][VOTE] Apache TomEE 7.0.2

[Romain Manni-Bucau]

Which makes 5 +1 (3 bindings with Mark, JL and mine) and no other votes so
it passes :). Will continue with release steps.

Thanks to all people having answered!


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.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>

2016-11-11 19:41 GMT+01:00 Jean-Louis Monteiro :

> thanks Romain.
>
> here is my +1
>
> Le 11 nov. 2016 19:40, "Felipe Jaekel"  a écrit :
>
> > I had some classes that were incorrectly implementing Serializable
> >
> > It is working fine now
> >
> > Thanks
> >
> > 2016-11-07 10:33 GMT-02:00 Romain Manni-Bucau :
> >
> > > PS: should be working for 7.0.3 (
> > > https://issues.apache.org/jira/browse/TOMEE-1965) but maybe also check
> > why
> > > you serialize an entity manager (this never sounds safe since it breaks
> > > several parts of JPA with most providers)
> > >
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > <https://blog-rmannibucau.rhcloud.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>
> > >
> > > 2016-11-07 13:23 GMT+01:00 Romain Manni-Bucau :
> > >
> > > > think it can be solved setting tomee.jpa.cdi=false
> > > >
> > > >
> > > > Romain Manni-Bucau
> > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > > <https://blog-rmannibucau.rhcloud.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>
> > > >
> > > > 2016-11-07 13:16 GMT+01:00 Felipe Jaekel :
> > > >
> > > >> Hi,
> > > >>
> > > >> +1 as I've been using apache-tomee-7.0.2-20160726.041804-27-plus on
> > > >> production without problems.
> > > >>
> > > >> One detail is that with version 7.0.2-20161107.040545-131 I'm
> getting
> > a
> > > >> *java.io.NotSerializableException* when I run arquillian tests on
> > > >> Jenkins.
> > > >> It started some weeks ago. Sorry to mention it only now. I didn't
> had
> > > time
> > > >> to report it on the user list when I first saw the problem, so I
> just
> > > >> changed the maven dependency to 7.0.1 and ended up forgetting about
> > > it...
> > > >>
> > > >> Locally I can run the tests. This is my arquillian deployment code:
> > > >>
> > > >> @ArquillianSuiteDeployment
> > > >> public class ClienteIT extends AbstractIT
> > > >> {
> > > >> @Deployment(testable = false)
> > > >> public static WebArchive createDeployment()
> > > >> {
> > > >> if(ServerUtil.isJenkins())
> > > >> {
> > > >> return ShrinkWrap.createFromZipFile(WebArchive.class, new
> > > >> File("target/cliente.war"));
> > > >> }
> > > >> else
> > > >> {
> > > >> return ShrinkWrap.create(MavenImporter.class, "cliente.war")//
> > > >> .offline()//
> > > >> .loadPomFromFile("pom.xml")//
> > > >> .importBuildOutput()//
> > > >> .as(WebArchive.class);
> > > >> }
> > > >> }
> > > >>
> > > >>
> > > >> *Jenkins output:*
> > > >> Mensagem de erro
> > > >>
> > > >> Unable to deploy
> > > >>
> > > >> Pilha
> > > >>
> > > >> org.jboss.arquillian.container.spi.client.
> > > container.DeploymentException:
> > > >> Unable to deploy
> > > >> Caused by: javax.ejb.EJBException:
> > > >> Unknown Container Exception: java.rmi.RemoteException: Cannot read
> the
> > > >> respon

Re: [VOTE] Apache TomEE 7.0.2

[Romain Manni-Bucau]

my own +1, validated the expected JAX-RS 2 fix works well, yeah!


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.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>

2016-11-07 13:33 GMT+01:00 Romain Manni-Bucau :

> PS: should be working for 7.0.3 (https://issues.apache.org/
> jira/browse/TOMEE-1965) but maybe also check why you serialize an entity
> manager (this never sounds safe since it breaks several parts of JPA with
> most providers)
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://blog-rmannibucau.rhcloud.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>
>
> 2016-11-07 13:23 GMT+01:00 Romain Manni-Bucau :
>
>> think it can be solved setting tomee.jpa.cdi=false
>>
>>
>> Romain Manni-Bucau
>> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
>> <https://blog-rmannibucau.rhcloud.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>
>>
>> 2016-11-07 13:16 GMT+01:00 Felipe Jaekel :
>>
>>> Hi,
>>>
>>> +1 as I've been using apache-tomee-7.0.2-20160726.041804-27-plus on
>>> production without problems.
>>>
>>> One detail is that with version 7.0.2-20161107.040545-131 I'm getting a
>>> *java.io.NotSerializableException* when I run arquillian tests on
>>> Jenkins.
>>> It started some weeks ago. Sorry to mention it only now. I didn't had
>>> time
>>> to report it on the user list when I first saw the problem, so I just
>>> changed the maven dependency to 7.0.1 and ended up forgetting about it...
>>>
>>> Locally I can run the tests. This is my arquillian deployment code:
>>>
>>> @ArquillianSuiteDeployment
>>> public class ClienteIT extends AbstractIT
>>> {
>>> @Deployment(testable = false)
>>> public static WebArchive createDeployment()
>>> {
>>> if(ServerUtil.isJenkins())
>>> {
>>> return ShrinkWrap.createFromZipFile(WebArchive.class, new
>>> File("target/cliente.war"));
>>> }
>>> else
>>> {
>>> return ShrinkWrap.create(MavenImporter.class, "cliente.war")//
>>> .offline()//
>>> .loadPomFromFile("pom.xml")//
>>> .importBuildOutput()//
>>> .as(WebArchive.class);
>>> }
>>> }
>>>
>>>
>>> *Jenkins output:*
>>> Mensagem de erro
>>>
>>> Unable to deploy
>>>
>>> Pilha
>>>
>>> org.jboss.arquillian.container.spi.client.container.DeploymentException:
>>> Unable to deploy
>>> Caused by: javax.ejb.EJBException:
>>> Unknown Container Exception: java.rmi.RemoteException: Cannot read the
>>> response from the server (OEJP/4.6) : Cannot read the response from
>>> the server (OEJP/4.6) : writing aborted;
>>> java.io.NotSerializableException:
>>> org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1;
>>> nested exception is:
>>> java.io.IOException: Cannot read the response from the server
>>> (OEJP/4.6) : writing aborted; java.io.NotSerializableException:
>>> org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1
>>> Caused by: java.io.IOException: Cannot read the response from the
>>> server (OEJP/4.6) : writing aborted; java.io.NotSerializableException:
>>> org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1
>>> Caused by: java.io.WriteAbortedException: writing aborted;
>>> java.io.NotSerializableException:
>>> org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1
>>> Caused by: java.io.NotSerializableException:
>>> org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1
>>>
>>> Saída de erro padrão
>>>
>>> Nov 07, 2016 8:40:23 AM org.reflections.Reflections scan
>>> INFO: Reflections took 269 ms to scan 2 urls, producing 41 keys and 130
>>> 

Re: [VOTE] Apache TomEE 7.0.2

[Romain Manni-Bucau]

PS: should be working for 7.0.3 (
https://issues.apache.org/jira/browse/TOMEE-1965) but maybe also check why
you serialize an entity manager (this never sounds safe since it breaks
several parts of JPA with most providers)


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.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>

2016-11-07 13:23 GMT+01:00 Romain Manni-Bucau :

> think it can be solved setting tomee.jpa.cdi=false
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://blog-rmannibucau.rhcloud.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>
>
> 2016-11-07 13:16 GMT+01:00 Felipe Jaekel :
>
>> Hi,
>>
>> +1 as I've been using apache-tomee-7.0.2-20160726.041804-27-plus on
>> production without problems.
>>
>> One detail is that with version 7.0.2-20161107.040545-131 I'm getting a
>> *java.io.NotSerializableException* when I run arquillian tests on
>> Jenkins.
>> It started some weeks ago. Sorry to mention it only now. I didn't had time
>> to report it on the user list when I first saw the problem, so I just
>> changed the maven dependency to 7.0.1 and ended up forgetting about it...
>>
>> Locally I can run the tests. This is my arquillian deployment code:
>>
>> @ArquillianSuiteDeployment
>> public class ClienteIT extends AbstractIT
>> {
>> @Deployment(testable = false)
>> public static WebArchive createDeployment()
>> {
>> if(ServerUtil.isJenkins())
>> {
>> return ShrinkWrap.createFromZipFile(WebArchive.class, new
>> File("target/cliente.war"));
>> }
>> else
>> {
>> return ShrinkWrap.create(MavenImporter.class, "cliente.war")//
>> .offline()//
>> .loadPomFromFile("pom.xml")//
>> .importBuildOutput()//
>> .as(WebArchive.class);
>> }
>> }
>>
>>
>> *Jenkins output:*
>> Mensagem de erro
>>
>> Unable to deploy
>>
>> Pilha
>>
>> org.jboss.arquillian.container.spi.client.container.DeploymentException:
>> Unable to deploy
>> Caused by: javax.ejb.EJBException:
>> Unknown Container Exception: java.rmi.RemoteException: Cannot read the
>> response from the server (OEJP/4.6) : Cannot read the response from
>> the server (OEJP/4.6) : writing aborted;
>> java.io.NotSerializableException:
>> org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1;
>> nested exception is:
>> java.io.IOException: Cannot read the response from the server
>> (OEJP/4.6) : writing aborted; java.io.NotSerializableException:
>> org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1
>> Caused by: java.io.IOException: Cannot read the response from the
>> server (OEJP/4.6) : writing aborted; java.io.NotSerializableException:
>> org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1
>> Caused by: java.io.WriteAbortedException: writing aborted;
>> java.io.NotSerializableException:
>> org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1
>> Caused by: java.io.NotSerializableException:
>> org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1
>>
>> Saída de erro padrão
>>
>> Nov 07, 2016 8:40:23 AM org.reflections.Reflections scan
>> INFO: Reflections took 269 ms to scan 2 urls, producing 41 keys and 130
>> values
>> Nov 07, 2016 8:40:23 AM
>> org.jboss.arquillian.drone.webdriver.factory.remote.reusable
>> .ReusedSessionPermanentFileStorage
>> readStore
>> INFO: Reused session store is not available at
>> /var/lib/jenkins/.drone-webdriver-session-store, a new one will be
>> created.
>> Nov 07, 2016 8:40:24 AM org.apache.openejb.arquillian.common.Setup
>> findHome
>> INFO: Unable to find home in: /tmp/arquillian-apache-tomee
>> Nov 07, 2016 8:40:24 AM
>> org.apache.openejb.arquillian.common.MavenCache getArtifact
>> INFO: Downloading
>> org.apache.tomee:apache-tomee:7.0.2-SNAPSHOT:zip:plus please wait...
>> Nov 07, 2016 8:40:24 AM org.apache.openejb.arquillian.common.Zips unzip
>> INFO: Extracting
>> '/var/lib/jenkins/.m2/repository/org/apache/tomee/apache-
>> tomee/7.0.2-

Re: [VOTE] Apache TomEE 7.0.2

[Romain Manni-Bucau]

think it can be solved setting tomee.jpa.cdi=false


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.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>

2016-11-07 13:16 GMT+01:00 Felipe Jaekel :

> Hi,
>
> +1 as I've been using apache-tomee-7.0.2-20160726.041804-27-plus on
> production without problems.
>
> One detail is that with version 7.0.2-20161107.040545-131 I'm getting a
> *java.io.NotSerializableException* when I run arquillian tests on Jenkins.
> It started some weeks ago. Sorry to mention it only now. I didn't had time
> to report it on the user list when I first saw the problem, so I just
> changed the maven dependency to 7.0.1 and ended up forgetting about it...
>
> Locally I can run the tests. This is my arquillian deployment code:
>
> @ArquillianSuiteDeployment
> public class ClienteIT extends AbstractIT
> {
> @Deployment(testable = false)
> public static WebArchive createDeployment()
> {
> if(ServerUtil.isJenkins())
> {
> return ShrinkWrap.createFromZipFile(WebArchive.class, new
> File("target/cliente.war"));
> }
> else
> {
> return ShrinkWrap.create(MavenImporter.class, "cliente.war")//
> .offline()//
> .loadPomFromFile("pom.xml")//
> .importBuildOutput()//
> .as(WebArchive.class);
> }
> }
>
>
> *Jenkins output:*
> Mensagem de erro
>
> Unable to deploy
>
> Pilha
>
> org.jboss.arquillian.container.spi.client.container.DeploymentException:
> Unable to deploy
> Caused by: javax.ejb.EJBException:
> Unknown Container Exception: java.rmi.RemoteException: Cannot read the
> response from the server (OEJP/4.6) : Cannot read the response from
> the server (OEJP/4.6) : writing aborted;
> java.io.NotSerializableException:
> org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1;
> nested exception is:
> java.io.IOException: Cannot read the response from the server
> (OEJP/4.6) : writing aborted; java.io.NotSerializableException:
> org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1
> Caused by: java.io.IOException: Cannot read the response from the
> server (OEJP/4.6) : writing aborted; java.io.NotSerializableException:
> org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1
> Caused by: java.io.WriteAbortedException: writing aborted;
> java.io.NotSerializableException:
> org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1
> Caused by: java.io.NotSerializableException:
> org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1
>
> Saída de erro padrão
>
> Nov 07, 2016 8:40:23 AM org.reflections.Reflections scan
> INFO: Reflections took 269 ms to scan 2 urls, producing 41 keys and 130
> values
> Nov 07, 2016 8:40:23 AM
> org.jboss.arquillian.drone.webdriver.factory.remote.reusable.
> ReusedSessionPermanentFileStorage
> readStore
> INFO: Reused session store is not available at
> /var/lib/jenkins/.drone-webdriver-session-store, a new one will be
> created.
> Nov 07, 2016 8:40:24 AM org.apache.openejb.arquillian.common.Setup
> findHome
> INFO: Unable to find home in: /tmp/arquillian-apache-tomee
> Nov 07, 2016 8:40:24 AM
> org.apache.openejb.arquillian.common.MavenCache getArtifact
> INFO: Downloading
> org.apache.tomee:apache-tomee:7.0.2-SNAPSHOT:zip:plus please wait...
> Nov 07, 2016 8:40:24 AM org.apache.openejb.arquillian.common.Zips unzip
> INFO: Extracting
> '/var/lib/jenkins/.m2/repository/org/apache/tomee/
> apache-tomee/7.0.2-SNAPSHOT/apache-tomee-7.0.2-SNAPSHOT-plus.zip'
> to '/tmp/arquillian-apache-tomee'
> Nov 07, 2016 8:40:24 AM
> org.apache.tomee.arquillian.remote.RemoteTomEEContainer configure
> INFO: Downloaded container to:
> /tmp/arquillian-apache-tomee/apache-tomee-plus-7.0.2-SNAPSHOT
> Nov 07, 2016 8:40:33 AM org.apache.openejb.client.EventLogger log
> INFO: RemoteInitialContextCreated{providerUri=http://localhost:
> 38057/tomee/ejb}
> Nov 07, 2016 8:41:03 AM org.apache.openejb.client.EventLogger log
> WARNING: RequestFailed{server=http://localhost:38057/tomee/ejb}
> EJBRequest{deploymentId='openejb/Deployer',
> type=EJB_OBJECT_BUSINESS_METHOD,
> Body{ejb=SINGLETON:openejb/Deployer:org.apache.openejb.assembler.Deployer,
> orb=null, methodInstance=public abstract
> org.apache.openejb.assembler.classic.AppInfo
> org.apache.openejb.assembler.Deployer.deploy(java.lang.String) throws
> org.apache.openejb.OpenEJBException, interfaceClass=interface
> org.apache.openejb.assembler.Depl

[VOTE] Apache TomEE 7.0.2

[Romain Manni-Bucau]

Hi

As mentionned on the dev@ list few weeks ago here is the 7.0.2 vote.

Main change is upgrading CXF and Tomcat. It shouldn't break any application
but fix the ones with JAX-RS 2 @Suspended.

There are, as usual, tons of bugfixes and small enhancements in particular
in gradle integration and tomee embedded areas.

- Release notes:
https://issues.apache.org/jira/browse/TOMEE-1964?jql=project%20%3D%20TOMEE%20and%20fixVersion%20%3D%207.0.2%20and%20resolution%20%3D%20Fixed
- Keys file: https://www.apache.org/dist/tomee/KEYS
- Tag on github: https://github.com/rmannibucau/tomee/tree/tomee-7.0.2
- Staging repository:
https://repository.apache.org/content/repositories/orgapachetomee-1102
- Dev dist: https://dist.apache.org/repos/dist/dev/tomee/7.0.2/

Vote will be open for 72h or until we get 3 +1 bindings. Binding or not
everyone is very welcomed to test and vote.


Please vote:
[ ] +1 of course!
[ ] +0 just to say hi
[ ] -1 no, ${blocker} is blocking because ${cause}

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.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>

Re: 7.0.2 around the corner?

[Romain Manni-Bucau]

quick update: jcs vote should end ~these days and bval is ready to release
so will let them end of the week and target next week for tomee (kind of
last chance to be onboard since we reached the mandatory dependency
upgrades ;))


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-09-15 19:03 GMT+02:00 Romain Manni-Bucau :

> Tomcat and cxf which are planned end of the month more or less
>
> Le 15 sept. 2016 15:38, "Adam Cornett"  a écrit :
>
>> It looks like MyFaces 2.1.11 is going to pass the release vote (currently
>> in progress: http://markmail.org/thread/jlnpnc6knt4kzkgz).
>>
>> With Tomcat and OWB both recently released is there anything else needed
>> for TomEE 7.0.2?
>>
>> On Fri, Sep 2, 2016 at 10:43 AM, Romain Manni-Bucau <
>> rmannibu...@gmail.com>
>> wrote:
>>
>> > ok, will ping myfaces then
>> >
>> >
>> > Romain Manni-Bucau
>> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
>> > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
>> > <http://rmannibucau.wordpress.com> | Github <https://github.com/
>> > rmannibucau> |
>> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
>> > <http://www.tomitribe.com> | JavaEE Factory
>> > <https://javaeefactory-rmannibucau.rhcloud.com>
>> >
>> > 2016-09-02 16:39 GMT+02:00 Adam Cornett :
>> >
>> > > I just tested using TomEE 7.0.2-SNAPSHOT, OWB 1.7.0-SNAPSHOT and
>> MyFaces
>> > > 2.2.10 with tomcat clustering setup.  When I access a page with a
>> > > ViewScoped JSF bean I get a "java.io.NotSerializableException:
>> > > org.apache.webbeans.container.BeanManagerImpl" exception on the
>> primary
>> > > server.  This exception does not happen when I swap in  MyFaces
>> > > 2.2.11-SNAPSHOT.
>> > >
>> > > On Fri, Sep 2, 2016 at 10:14 AM, Romain Manni-Bucau <
>> > rmannibu...@gmail.com
>> > > >
>> > > wrote:
>> > >
>> > > > think it was the id generation issue which was causing this one but
>> if
>> > > you
>> > > > can test feedback would be very welcomed
>> > > >
>> > > >
>> > > > Romain Manni-Bucau
>> > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
>> > > > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
>> > > > <http://rmannibucau.wordpress.com> | Github <https://github.com/
>> > > > rmannibucau> |
>> > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
>> > > > <http://www.tomitribe.com> | JavaEE Factory
>> > > > <https://javaeefactory-rmannibucau.rhcloud.com>
>> > > >
>> > > > 2016-09-02 16:12 GMT+02:00 Adam Cornett :
>> > > >
>> > > > > It was my understanding that the change in MyFaces is part of the
>> fix
>> > > > > (making the BeanManager reference transient to prevent it being
>> > > > serialized
>> > > > > to begin with.)  I can use 2.2.10 and see if the issue returns and
>> > > report
>> > > > > back.
>> > > > >
>> > > > > On Fri, Sep 2, 2016 at 10:07 AM, Romain Manni-Bucau <
>> > > > rmannibu...@gmail.com
>> > > > > >
>> > > > > wrote:
>> > > > >
>> > > > > > @Adam: isnt it fixed in OWB 1.7.0?
>> > > > > >
>> > > > > >
>> > > > > > Romain Manni-Bucau
>> > > > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
>> > > > > > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
>> > > > > > <http://rmannibucau.wordpress.com> | Github <
>> https://github.com/
>> > > > > > rmannibucau> |
>> > > > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
>> > > > > > <http://www.tomitribe.com> | JavaEE Factory
>> > > >

Re: TOMEE-1962 - Deprecate LocalInitialContextFactory

[Romain Manni-Bucau]

Ok,

putting aside the name - just wanted to keep the old one to not break that
usage which is still numerous due to openejb 3 upgrades, and not speaking
of our codebase.

- The factory is complicated - reflection - probably due to old support
(maybe OSGi) or very legacy stuff which is useless today so we can get rid
of it
- The factory contains init logic we should get rid of for a context
factory (separation of concerns + leads to the fact to put in the factory
logic related to boot which is no more accurate)
- The context has this global security config which shouldn't be used at
runtime but is used in tests and embedded scenarii (legacy)
- The context has all this boot/shutdown logic of the container
- The context has this "inject" and @LocalClient hacks which is today no
more accurate thanks to CDI
- The OpenEJBInitialContextFactory supports local EJB but also resources
lookup which is the main valid usage today of specifying explicitly a local
factory (unmanaged/controlled environment + lookup of resources: typically
JPA provider DataSource lookup)

Happy to move the old factory in openejb-core-legacy (same fqn) and release
it once and remove it after, just as a compatibility module.

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-10-24 1:23 GMT+02:00 David Blevins :

> Let’s discuss this one a bit.
>
> Aside from the ClientSecurity aspect, what’s wrong with this class?
>
> And to be clear I’m more in favor of deprecating specific functionality
> rather than the name itself.  Keeping things symmetrical with
> RemoteInitialContextFactory and LocalInitialContextFactory is quite nice.
>
> The second thing is we tend to always copy code, leave the old code
> broken, port some of the features and then we have 5 80% functional
> versions of the same thing.  So in the sake of learning a better way, I
> think it’d be great to have a discussion on what it is we’re trying to fix
> or deprecate.
>
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
>
>

Re: tomee example request

[Romain Manni-Bucau]

Not dure i can parse your request. How did you configure the provider?

Le 19 oct. 2016 12:34, "Chris Graves"  a écrit :

> Rest service using JSON Schema not xsd.  I can't seem to get the
> JSONProvider to work correctly.  It works fine if I have an xsd.
>
>
> Thanks
>
> Chris
>

Re: getResourceAsStream() for a folder

[Romain Manni-Bucau]

@Svetlin: thanks to catch it, was intended for dev@tomcat (thanks gmail to
have completion ;))

dev@tomcat: can you check please the original question (in short:
getResourceAsStream("/some/folder")
returns a stream)


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-10-13 13:59 GMT+02:00 Svetlin Zarev :

> Hi,
>
> IMO this is a bug introduced with [1][2]. Although the root cause is in the
> bad impl. of FileResource [3] that ignores the IOException and despite the
> error, still returns a byte[] as if nothing bad happened.
>
>
> [1] https://bz.apache.org/bugzilla/show_bug.cgi?id=60146
> [2]
> https://github.com/apache/tomcat85/blob/5768426dd27422747f2b9b4da5a092
> 7ee3328ffb/java/org/apache/catalina/webresources/CachedResource.java#L267
> [3]
> https://github.com/apache/tomcat85/blob/5768426dd27422747f2b9b4da5a092
> 7ee3328ffb/java/org/apache/catalina/webresources/FileResource.java#L203
>
> PS: Maybe this should be forwarded to the tomcat dev list ?
>
> Kind regards,
> Svetlin
>
> 2016-10-13 12:06 GMT+03:00 Romain Manni-Bucau :
>
> > Hi guys,
> >
> > upgrading tomee to tomcat 8.5.6 I noticed request.getServletContext().
> > getResourceAsStream(path) now returns an empty stream for / (or an
> existing
> > folder probably). Not sure it is expected or unintended.
> >
> > Reading the spec it is not that clear to me since the folder is an
> existing
> > resource but not really a webresource so not it should be considered as a
> > resource and therefore having a stream (which doesn't mean much for a
> > folder).
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > <http://www.tomitribe.com> | JavaEE Factory
> > <https://javaeefactory-rmannibucau.rhcloud.com>
> >
>

getResourceAsStream() for a folder

[Romain Manni-Bucau]

Hi guys,

upgrading tomee to tomcat 8.5.6 I noticed request.getServletContext().
getResourceAsStream(path) now returns an empty stream for / (or an existing
folder probably). Not sure it is expected or unintended.

Reading the spec it is not that clear to me since the folder is an existing
resource but not really a webresource so not it should be considered as a
resource and therefore having a stream (which doesn't mean much for a
folder).

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

Re: Tomee Drop-in War -security mode

[Romain Manni-Bucau]

Please dont multicast the same question over and over. You got the answer
on jira afaik.

Le 12 oct. 2016 14:32, "Moorthy, Magesh"  a
écrit :

> Hi,
>
>We are using tomee drop in war (version 7.0.0-M1) in our tomcat
> server(8.0.36) to deploy our web applications which uses EJBs. When we
> start the server in -security mode tomee war is getting deployed only if we
> give the below mentioned permission. Please confirm whether tomee drop-in
> war will get deployed only  if we provide permission
> java.security.AllPermission.
>
> grant codeBase "file:${catalina.base}/webapps/tomee/-" {
> permission java.security.AllPermission;
> };
>
>
> Thanks & Regards,
> Magesh M
>
>
> This e-mail message is being sent solely for use by the intended
> recipient(s) and may contain confidential information.  Any unauthorized
> review, use, disclosure or distribution is prohibited.  If you are not the
> intended recipient, please contact the sender by phone or reply by e-mail,
> delete the original message and destroy all copies. Thank you.

Re: 7.0.1 TomEE plus shutdown fails intermetantly

[Romain Manni-Bucau]

2016-10-06 12:03 GMT+02:00 Dignesh :

> Hi Romain,
>
> Just curious to know ..how you found it is thread-42 from screenshot ?
>
>
First WARNING ;)


>
> Attached are the thread dump and latest screen shot of shutdown getting
> blocked. ThreadDump.txt
> 
> issue.jpg
> 
>
>
The issue comes from this thread:



"pool-18-thread-1" prio=6 tid=0x12917000 nid=0xfdc waiting on
condition [0x14e1f000]
   java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <0x00071563d248> (a
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at 
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2082)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1090)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:807)
at 
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)


(found with this command

grep '^"' /tmp/ThreadDump.txt  | grep -v daemon | grep -v main | grep
-v GC | grep -v VM
"pool-18-thread-1" prio=6 tid=0x12917000 nid=0xfdc waiting on
condition [0x14e1f000]

)


But I'm not sure who is created the pool. One easy way is to debug in
ThreadPoolExecutor constructor to know ho creates this pool.

Thank you,
> Dignesh,
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/7-0-1-TomEE-plus-shutdown-fails-intermetantly-
> tp4680299p4680301.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: 7.0.1 TomEE plus shutdown fails intermetantly

[Romain Manni-Bucau]

Hi Dignesh,

this is due to not daemon threads not stopped at shutdown.

This Thread-42 is very suspicious

To know what happens just take a thread dump (jps -> identify Bootstrap
process pid then jstack )


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-10-06 6:12 GMT+02:00 Dignesh :

> Hi,
>
> When I invoke shutdown.bat , TomEE server doesnot stop. It is getting
> struck
> at some point. I need to kill the java process manually everytime.
> Can anyone please help me why I am seeing this issue.Attached the screen
> shot of the log where it is getting struck
> TestLog.jpg
> <http://tomee-openejb.979440.n4.nabble.com/file/n4680299/TestLog.jpg>
>
> Thank you,
> Dignesh
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/7-0-1-TomEE-plus-shutdown-fails-intermetantly-tp4680299.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Fwd: tomee git commit: TOMEE-1951 making JPA CDI aware

[Romain Manni-Bucau]

Hi guys,

a quick note on that commit (and if you have a better idea it would be very
very welcomed).

Issue is JPA needs to know the BeanManager reference now.

First idea was to start CDI before JPA (yes it breaks the class
transformation lifecycle but let's assume it doesn't). Issue is then if CDI
uses a startup event then JPA can be missing and the app will not boot.

So we need to start JPA before CDI but hibernate for instance uses CDI when
the EMF is created to lookup the listeners in CDI context...which fails
cause CDI is not yet booted.

I don't see a good solution to that so I basically made a proxy to the bean
manager available to JPA and added a property to support the lazy creation
of the EMF (see https://issues.apache.org/jira/browse/TOMEE-1951).

It seems it works - I expect some test to break but will keep an eye on
that - but it can break some tomee 7.0.[0|1] applications relying on
hibernate (maybe eclipselink, didnt check yet but build will say us) and
I'm not very happy of that state even if it is the best I found.

Wanted to avoid to do some kind of reactive implementation popping up
threads "on demand" which would make the application quite uncontrolled
compared to what we do today which is quite predictable.

Happy to get help on that topic if you see a small hole we can use to make
it smoother.

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

-- Forwarded message --
From: 
Date: 2016-10-03 11:03 GMT+02:00
Subject: tomee git commit: TOMEE-1951 making JPA CDI aware
To: comm...@tomee.apache.org


Repository: tomee
Updated Branches:
  refs/heads/master 63792008e -> 0737513ae


TOMEE-1951 making JPA CDI aware


Project: http://git-wip-us.apache.org/repos/asf/tomee/repo
Commit: http://git-wip-us.apache.org/repos/asf/tomee/commit/0737513a
Tree: http://git-wip-us.apache.org/repos/asf/tomee/tree/0737513a
Diff: http://git-wip-us.apache.org/repos/asf/tomee/diff/0737513a

Branch: refs/heads/master
Commit: 0737513ae6e4755ac94699b3b8b09ee2371ece09
Parents: 6379200
Author: rmannibucau 
Authored: Mon Oct 3 11:02:59 2016 +0200
Committer: rmannibucau 
Committed: Mon Oct 3 11:02:59 2016 +0200

--
 .../openejb/assembler/classic/Assembler.java|   6 +-
 .../classic/EntityManagerFactoryCallable.java   |  53 +++-
 .../assembler/classic/PersistenceBuilder.java   |   9 +-
 .../classic/ReloadableEntityManagerFactory.java |  47 ---
 .../openejb/persistence/JtaEntityManager.java   |   9 +-
 .../openejb/jpa/JPAHasBeanManagerTest.java  | 121 +++
 6 files changed, 216 insertions(+), 29 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/tomee/blob/0737513a/
container/openejb-core/src/main/java/org/apache/openejb/
assembler/classic/Assembler.java
--
diff --git a/container/openejb-core/src/main/java/org/apache/openejb/
assembler/classic/Assembler.java b/container/openejb-core/src/
main/java/org/apache/openejb/assembler/classic/Assembler.java
index ae52f14..08eb1a3 100644
--- a/container/openejb-core/src/main/java/org/apache/openejb/
assembler/classic/Assembler.java
+++ b/container/openejb-core/src/main/java/org/apache/openejb/
assembler/classic/Assembler.java
@@ -765,6 +765,8 @@ public class Assembler extends AssemblerTool implements
org.apache.openejb.spi.A
 final Map appBindings =
appBuilder.buildBindings(JndiEncBuilder.JndiScope.app);
 final Context appJndiContext = appBuilder.build(appBindings);

+final boolean cdiActive = shouldStartCdi(appInfo);
+
 try {
 // Generate the cmp2/cmp1 concrete subclasses
 final CmpJarBuilder cmpJarBuilder = new
CmpJarBuilder(appInfo, classLoader);
@@ -861,7 +863,7 @@ public class Assembler extends AssemblerTool implements
org.apache.openejb.spi.A
 for (final PersistenceUnitInfo info :
appInfo.persistenceUnits) {
 final ReloadableEntityManagerFactory factory;
 try {
-factory = persistenceBuilder.
createEntityManagerFactory(info, classLoader, validatorFactoriesByConfig);
+factory = persistenceBuilder.
createEntityManagerFactory(info, classLoader, validatorFactoriesByConfig,
cdiActive);
 containerSystem.getJNDIContext().bind(
PERSISTENCE_UNIT_NAMING_CONTEXT + info.id, factory);
 units.put(info.name, PERS

Re: OpenEJB/TomEE static code analysis

[Romain Manni-Bucau]

merged 2 PRs Svetlin, build will run on
https://ci.apache.org/builders/tomee-trunk-ubuntu soon


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-09-16 9:21 GMT+02:00 Svetlin Zarev :

> I've cleaned up the PR to make it more readable. I'll be grateful for any
> comments.
>
> Svetlin
>
> 2016-09-14 16:15 GMT+03:00 Svetlin Zarev  >:
>
> > Hi,
> >
> > I think I've fixed[1]  all stream leaks to files or streams opened by
> > classLoader.getResoureAsStream(). I intentionally ignored all streams
> > opened bu UrlConnection, because the issue with the connection pooling
> has
> > to be researched. I also reopened [2] because the patch is only for
> > slurp(File) and not for slurp(URL) or slurp(InputStream) which should not
> > close the stream.
> >
> > [1] https://github.com/apache/tomee/pull/44
> > [2] https://github.com/apache/tomee/pull/40
> >
> > Svetlin
> >
> > 2016-09-14 10:58 GMT+03:00 Romain Manni-Bucau :
> >
> >> Tomee is java 7 for 7.x by spec do java 8 is not an option
> >>
> >> On the fixes: ensure to unit test each non trivial fix but you can put
> all
> >> the "same" category ones in the same pr. Like "ensure streams are
> closed".
> >> Side note on this particular one: since we pool connections sometimes
> >> closing the stream would break it at runtime so unit testing is
> mandatory.
> >>
> >> Thanks to have a look to that
> >>
> >> Le 14 sept. 2016 09:48, "Mitia Alexandrov" 
> a
> >> écrit :
> >>
> >> > Hello,
> >> > I've made several such runs from Idea but mainly for Java 8fy reasons.
> >> > There are also several thousand places where the code may be rewritten
> >> with
> >> > java 8 constructions.
> >> >
> >> > Regards,
> >> >
> >> > Mitia
> >> >
> >> > 2016-09-14 10:35 GMT+03:00 Svetlin Zarev
>  >> om
> >> > >:
> >> >
> >> > > Dear TomEE developers,
> >> > >
> >> > > I've been running static code analysis (fortify) against TomEE 7 and
> >> as a
> >> > > result I have a list of more than 8000 potential issues (I hope most
> >> of
> >> > > them are false positives). Unfortunately I'm not allowed to share
> the
> >> > list
> >> > > itself.
> >> > >
> >> > > Either way I'll have to go through that list and review every single
> >> > > report, but it's impractical to open a bug report for every single
> >> issue.
> >> > >
> >> > > So here are my questions:
> >> > > * What would be the best way to handle the situation ?
> >> > > * What's the minimum severity level that's worth reporting ?
> >> > > * Should I open jira tickets for the minot/trivial/bad-practices
> >> issues ?
> >> > > * Should I provide PullRequests for the low priority issues or just
> >> for
> >> > the
> >> > > higher priority ones?
> >> > >
> >> > >
> >> > > Kind regards,
> >> > > Svetlin
> >> > >
> >> >
> >>
> >
> >
>

Re: String equality checks in JAXB classes

[Romain Manni-Bucau]

Le 16 sept. 2016 09:27, "Svetlin Zarev"  a
écrit :
>
> Hi,
>
> The static code analysis revealed that in all JAXB classes strings are
> being compared using == and !=. Obviously TomEE works, so this is not such
> a big issue, but I cannot explain to myself why it works :) I know that
the
> string literals are interned by default, but how do you guarantee that the
> various XML parsers will return the interned instances and not different
> instances ?

We heavily test it in our build for the provided parsers

>  Is the performance boost that big to make that hack worth it ?

No

> Are you interested in converting all !=/== to using equals() ?
>

Dont think so

> Kind regards,
> Svetlin

Re: 7.0.2 around the corner?

[Romain Manni-Bucau]

Tomcat and cxf which are planned end of the month more or less

Le 15 sept. 2016 15:38, "Adam Cornett"  a écrit :

> It looks like MyFaces 2.1.11 is going to pass the release vote (currently
> in progress: http://markmail.org/thread/jlnpnc6knt4kzkgz).
>
> With Tomcat and OWB both recently released is there anything else needed
> for TomEE 7.0.2?
>
> On Fri, Sep 2, 2016 at 10:43 AM, Romain Manni-Bucau  >
> wrote:
>
> > ok, will ping myfaces then
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > <http://www.tomitribe.com> | JavaEE Factory
> > <https://javaeefactory-rmannibucau.rhcloud.com>
> >
> > 2016-09-02 16:39 GMT+02:00 Adam Cornett :
> >
> > > I just tested using TomEE 7.0.2-SNAPSHOT, OWB 1.7.0-SNAPSHOT and
> MyFaces
> > > 2.2.10 with tomcat clustering setup.  When I access a page with a
> > > ViewScoped JSF bean I get a "java.io.NotSerializableException:
> > > org.apache.webbeans.container.BeanManagerImpl" exception on the
> primary
> > > server.  This exception does not happen when I swap in  MyFaces
> > > 2.2.11-SNAPSHOT.
> > >
> > > On Fri, Sep 2, 2016 at 10:14 AM, Romain Manni-Bucau <
> > rmannibu...@gmail.com
> > > >
> > > wrote:
> > >
> > > > think it was the id generation issue which was causing this one but
> if
> > > you
> > > > can test feedback would be very welcomed
> > > >
> > > >
> > > > Romain Manni-Bucau
> > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> > > > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > > > rmannibucau> |
> > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > > > <http://www.tomitribe.com> | JavaEE Factory
> > > > <https://javaeefactory-rmannibucau.rhcloud.com>
> > > >
> > > > 2016-09-02 16:12 GMT+02:00 Adam Cornett :
> > > >
> > > > > It was my understanding that the change in MyFaces is part of the
> fix
> > > > > (making the BeanManager reference transient to prevent it being
> > > > serialized
> > > > > to begin with.)  I can use 2.2.10 and see if the issue returns and
> > > report
> > > > > back.
> > > > >
> > > > > On Fri, Sep 2, 2016 at 10:07 AM, Romain Manni-Bucau <
> > > > rmannibu...@gmail.com
> > > > > >
> > > > > wrote:
> > > > >
> > > > > > @Adam: isnt it fixed in OWB 1.7.0?
> > > > > >
> > > > > >
> > > > > > Romain Manni-Bucau
> > > > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > > > > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> > > > > > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > > > > > rmannibucau> |
> > > > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > > > > > <http://www.tomitribe.com> | JavaEE Factory
> > > > > > <https://javaeefactory-rmannibucau.rhcloud.com>
> > > > > >
> > > > > > 2016-09-02 16:06 GMT+02:00 Adam Cornett  >:
> > > > > >
> > > > > > > Has MyFaces said anything about releasing 2.2.11? I know there
> > is a
> > > > > fix (
> > > > > > > https://issues.apache.org/jira/browse/MYFACES-4057) for an
> issue
> > > > I've
> > > > > > > encountered in testing.  If not I can keep pulling in a
> snapshot
> > of
> > > > it
> > > > > > for
> > > > > > > now so as to not delay the release of everything else that
> would
> > be
> > > > > > > included in 7.0.2
> > > > > > >
> > > > > > > - Adam
> > > > > > >
> > > > > > > On Fri, Sep 2, 2016 at 7:27 AM, Romain Manni-Buca

Re: OpenEJB/TomEE static code analysis

[Romain Manni-Bucau]

Tomee is java 7 for 7.x by spec do java 8 is not an option

On the fixes: ensure to unit test each non trivial fix but you can put all
the "same" category ones in the same pr. Like "ensure streams are closed".
Side note on this particular one: since we pool connections sometimes
closing the stream would break it at runtime so unit testing is mandatory.

Thanks to have a look to that

Le 14 sept. 2016 09:48, "Mitia Alexandrov"  a
écrit :

> Hello,
> I've made several such runs from Idea but mainly for Java 8fy reasons.
> There are also several thousand places where the code may be rewritten with
> java 8 constructions.
>
> Regards,
>
> Mitia
>
> 2016-09-14 10:35 GMT+03:00 Svetlin Zarev  >:
>
> > Dear TomEE developers,
> >
> > I've been running static code analysis (fortify) against TomEE 7 and as a
> > result I have a list of more than 8000 potential issues (I hope most of
> > them are false positives). Unfortunately I'm not allowed to share the
> list
> > itself.
> >
> > Either way I'll have to go through that list and review every single
> > report, but it's impractical to open a bug report for every single issue.
> >
> > So here are my questions:
> > * What would be the best way to handle the situation ?
> > * What's the minimum severity level that's worth reporting ?
> > * Should I open jira tickets for the minot/trivial/bad-practices issues ?
> > * Should I provide PullRequests for the low priority issues or just for
> the
> > higher priority ones?
> >
> >
> > Kind regards,
> > Svetlin
> >
>

Re: NameNotFoundException during ejb lookups

[Romain Manni-Bucau]

Hi

each EJB has its own JNDI tree and webapp has one too which can also be
different from beans one (each of them are configurable etc) so that's not
surprising you can't do that (keep in mind you bind a string whatever name
it has and binding in global is not defined, only global EJB names are
defined).


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-09-08 15:05 GMT+02:00 Dignesh :

> Hi,
>
> I have 2 beans. A and B. I am binding a object to dignesh namespace in "A".
> And I am doing the lookup in another bean B, and it is failing with
> namenotfoundexception. Am I doing something wrong here.Can anyone please
> help me on this
>
> A.bean: -
>
> Context ctx = new InitialContext();
> ctx.rebind("java:global/server/Dignesh", "false");
>
>
> B.Bean :-
>
> InitialContext initContext = new InitialContext();
> initContext.lookup("java:global/server/Dignesh"));
>
>
> Thank you,
>
>
>
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.n4.nabble.com/
> NameNotFoundException-during-ejb-lookups-tp4680063.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: PoolExhaustedException in logs

[Romain Manni-Bucau]

don't pass user/password to hibernate

hibernate needs to use datasource.getConnection() and not
datasource.getConnection(user, pwd)


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-09-07 10:57 GMT+02:00 Dignesh :

> Hi Romain,
>
> I have added the property in the resource. I am seeing a different issue
> now. Below is the stack trace what I am seeing in logs. Is there something
> I
> need to do additionally to switch to dbcp ?
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:494)
> Caused by: java.lang.UnsupportedOperationException: Not supported by
> BasicDataSource
> at
> org.apache.commons.dbcp2.BasicDataSource.getConnection(
> BasicDataSource.java:1552)
> at
> org.hibernate.service.jdbc.connections.internal.
> DatasourceConnectionProviderImpl.getConnection(
> DatasourceConnectionProviderImpl.java:141)
> at
> org.hibernate.internal.AbstractSessionImpl$NonContextualJdbcConnectionAcc
> ess.obtainConnection(AbstractSessionImpl.java:301)
> at
> org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.obtainConnection(
> LogicalConnectionImpl.java:214)
> at
> org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.getConnection(
> LogicalConnectionImpl.java:157)
> at
> org.hibernate.engine.jdbc.internal.StatementPreparerImpl.connection(
> StatementPreparerImpl.java:56)
> at
> org.hibernate.engine.jdbc.internal.StatementPreparerImpl$5.doPrepare(
> StatementPreparerImpl.java:159)
> at
> org.hibernate.engine.jdbc.internal.StatementPreparerImpl$
> StatementPreparationTemplate.prepareStatement(StatementPreparerImpl.java:
> 183)
> at
> org.hibernate.engine.jdbc.internal.StatementPreparerImpl.
> prepareQueryStatement(StatementPreparerImpl.java:157)
> at org.hibernate.loader.Loader.prepareQueryStatement(Loader.
> java:1881)
> at org.hibernate.loader.Loader.executeQueryStatement(Loader.
> java:1858)
> at org.hibernate.loader.Loader.executeQueryStatement(Loader.
> java:1838)
> at org.hibernate.loader.Loader.doQuery(Loader.java:906)
> at
> org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCol
> lections(Loader.java:348)
> at org.hibernate.loader.Loader.doList(Loader.java:2550)
> at org.hibernate.loader.Loader.doList(Loader.java:2536)
> at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.
> java:2366)
> at org.hibernate.loader.Loader.list(Loader.java:2361)
> at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:495)
> at
> org.hibernate.hql.internal.ast.QueryTranslatorImpl.list(
> QueryTranslatorImpl.java:357)
> at
> org.hibernate.engine.query.spi.HQLQueryPlan.performList(
> HQLQueryPlan.java:198)
> at org.hibernate.internal.SessionImpl.list(SessionImpl.java:1194)
> at org.hibernate.internal.QueryImpl.list(QueryImpl.java:101)
>
> Thank you,
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.n4.nabble.com/
> PoolExhaustedException-in-logs-tp4680034p4680041.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: PoolExhaustedException in logs

[Romain Manni-Bucau]

datasource properties = properties of the datasource = in  block


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-09-06 15:44 GMT+02:00 Dignesh :

> I dont see any property file with that name in tomee.
> Should I create one? and I should place in which location ?
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.n4.nabble.com/
> PoolExhaustedException-in-logs-tp4680034p4680038.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: PoolExhaustedException in logs

[Romain Manni-Bucau]

only that line in datasource properties

(side note: should be fixed on master/next release)


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-09-06 15:40 GMT+02:00 Dignesh :

> Hi Romain,
>
> Is that something configurable in tomee.xml.
> "DataSourceCreator = dbcp."
> OR are there any additional changes need to be done to switch to dbcp ?
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.n4.nabble.com/
> PoolExhaustedException-in-logs-tp4680034p4680036.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: PoolExhaustedException in logs

[Romain Manni-Bucau]

Hi

we identified few cases where we can leak connection with this mode (JTA +
tomcat-jdbc), maybe try to switch to dbcp setting DataSourceCreator = dbcp.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-09-06 15:34 GMT+02:00 Dignesh :

> Hi,
>
> My application is deployed on TomEE. It works fine for sometime, but after
> few hours I see these below exceptions in the log. Is the pool size is
> configurable in tomee.xml file.I do see few properties that can be
> specified
> for a resource in documentation, I am not sure which one is applicable for
> the below issue?Can some one please help me on this.
>
> Caused by: org.hibernate.exception.GenericJDBCException: could not prepare
> statement
> at
> org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(
> StandardSQLExceptionConverter.java:54)
> at
> org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(
> SqlExceptionHelper.java:124)
> at
> org.hibernate.engine.jdbc.internal.StatementPreparerImpl$
> StatementPreparationTemplate.prepareStatement(StatementPreparerImpl.java:
> 193)
> at
> org.hibernate.engine.jdbc.internal.StatementPreparerImpl.
> prepareQueryStatement(StatementPreparerImpl.java:157)
> at org.hibernate.loader.Loader.prepareQueryStatement(Loader.
> java:1881)
> at org.hibernate.loader.Loader.executeQueryStatement(Loader.
> java:1858)
> at org.hibernate.loader.Loader.executeQueryStatement(Loader.
> java:1838)
> at org.hibernate.loader.Loader.doQuery(Loader.java:906)
> at
> org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCol
> lections(Loader.java:348)
> at org.hibernate.loader.Loader.doList(Loader.java:2550)
> at org.hibernate.loader.Loader.doList(Loader.java:2536)
> at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.
> java:2366)
> at org.hibernate.loader.Loader.list(Loader.java:2361)
> at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:495)
> at
> org.hibernate.hql.internal.ast.QueryTranslatorImpl.list(
> QueryTranslatorImpl.java:357)
> at
> org.hibernate.engine.query.spi.HQLQueryPlan.performList(
> HQLQueryPlan.java:198)
> at org.hibernate.internal.SessionImpl.list(SessionImpl.java:1194)
> at org.hibernate.internal.QueryImpl.list(QueryImpl.java:101)
> at
> com.artesia.server.user.entity.UserStorageManager.retrieveTeamsUser(
> UserStorageManager.java:1700)
> ... 33 more
> Caused by: org.apache.tomcat.jdbc.pool.PoolExhaustedException: [Default
> JMS
> Resource Adapter-worker- - 68] Timeout: Pool empty. Unable to fetch a
> connection in 30 seconds, none available[size:100; busy:100; idle:0;
> lastwait:3].
> at
> org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(
> ConnectionPool.java:688)
> at
> org.apache.tomcat.jdbc.pool.ConnectionPool.getConnection(
> ConnectionPool.java:187)
> at
> org.apache.tomcat.jdbc.pool.DataSourceProxy.getConnection(
> DataSourceProxy.java:132)
> at
> org.apache.tomcat.jdbc.pool.DataSourceProxy.getConnection(
> DataSourceProxy.java:90)
> at
> org.apache.openejb.resource.jdbc.managed.local.ManagedConnection.
> newConnection(ManagedConnection.java:180)
> at
> org.apache.openejb.resource.jdbc.managed.local.ManagedConnection.invoke(
> ManagedConnection.java:126)
> at com.sun.proxy.$Proxy101.prepareStatement(Unknown Source)
> at
> org.hibernate.engine.jdbc.internal.StatementPreparerImpl$5.doPrepare(
> StatementPreparerImpl.java:159)
> at
> org.hibernate.engine.jdbc.internal.StatementPreparerImpl$
> StatementPreparationTemplate.prepareStatement(StatementPreparerImpl.java:
> 183)
> ... 49 more
>
> Thank you
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.n4.nabble.com/
> PoolExhaustedException-in-logs-tp4680034.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: reworking the website?

[Romain Manni-Bucau]

Le 5 sept. 2016 21:20, "David Blevins"  a écrit :
>
> Looking great!
>
> I’d definitely be “pro” grouping.

Was thinking to a convention on sample names for that (split on -?)

>
> Note on the Wall of fame, I think it’d be great to list everyone.  Maybe
two sections “Most Recent” and “All time”.
>

First impl used github a bit like example page but data were not that
accurate and rendering suffered from it so used a manual list thinking
comitters and contributors can PR themself ( see
https://github.com/rmannibucau/site-tomee-ng/blob/master/src/main/jbake/content/community/contributors.adoc
)

> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
>
> > On Sep 2, 2016, at 10:18 AM, Romain Manni-Bucau 
wrote:
> >
> > added a basic example section:
> > http://tomee.apache.org/ng/examples/index.html
> >
> > feel free to hack anything you want there like tagging or whatever but
> > basic feature is there; Idea was to provide a search box instead of
> > organizing the example to let them be browsable more efficiently.
Doesn't
> > prevent to organize them later but we need to find a convention then
(page
> > is generated)
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> > <http://rmannibucau.wordpress.com> | Github <
https://github.com/rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > <http://www.tomitribe.com> | JavaEE Factory
> > <https://javaeefactory-rmannibucau.rhcloud.com>
> >
> > 2016-04-12 7:47 GMT+02:00 Romain Manni-Bucau :
> >
> >> Hi Chris
> >>
> >> Le 12 avr. 2016 02:33, "Chris Owens"  a
> >> écrit :
> >>>
> >>> Speaking as a reasonably-well-informed user of TomEE, who has been
into
> >> the
> >>> code, but who is still very much an outsider, I would say that
> >> documentation
> >>> is probably the biggest obstacle to wider uptake. It's a project I
would
> >> be
> >>> happy to work on. I'm willing to put the work in to do some serious
> >> writing.
> >>>
> >>> Before we talk about documentation workflow, git vs other models,
CMSes,
> >>> etc., I think there are some much more basic questions to address:
> >>>
> >>> -- Who is the intended audience for each major portion of the
> >> documentation?
> >>>
> >>
> >> I d say people not able to go to code and in that category 2
> >> subcategories: admin and dev.
> >>
> >>> -- For TomEE Components that are not owned by this project (e.g.,
Tomcat,
> >>> cxf, JMS, etc.), how shall our documentation interact with that
> >> component's
> >>> "native" documentation? By reference? By duplication? Other?
> >>>
> >>
> >> Reference + enrichment when needed. Really against duplication.
> >>
> >>> -- What are the major reference topics that need to be covered? (For
> >>> example, Contexts, Classloaders, Configuration, Testing, Embedded,
etc)?
> >>>
> >>
> >> Idea was to start with some basics and add info depending the list
> >> questions.
> >>
> >>> -- What are the major tutorial or "how-to" threads that need to be
> >> covered?
> >>>
> >>>
> >>
> >> Same there. Should also probably consider rework very hard examples to
> >> make them useful and more explicit (arquillian website is a great
example
> >> there).
> >>
> >>>
> >>>
> >>>
> >>> --
> >>> View this message in context: http://tomee-openejb.979440.
> >> n4.nabble.com/reworking-the-website-tp4677918p4678116.html
> >>> Sent from the TomEE Dev mailing list archive at Nabble.com.
> >>
>

Re: 7.0.2 around the corner?

[Romain Manni-Bucau]

ok, will ping myfaces then


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-09-02 16:39 GMT+02:00 Adam Cornett :

> I just tested using TomEE 7.0.2-SNAPSHOT, OWB 1.7.0-SNAPSHOT and MyFaces
> 2.2.10 with tomcat clustering setup.  When I access a page with a
> ViewScoped JSF bean I get a "java.io.NotSerializableException:
> org.apache.webbeans.container.BeanManagerImpl" exception on the primary
> server.  This exception does not happen when I swap in  MyFaces
> 2.2.11-SNAPSHOT.
>
> On Fri, Sep 2, 2016 at 10:14 AM, Romain Manni-Bucau  >
> wrote:
>
> > think it was the id generation issue which was causing this one but if
> you
> > can test feedback would be very welcomed
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > <http://www.tomitribe.com> | JavaEE Factory
> > <https://javaeefactory-rmannibucau.rhcloud.com>
> >
> > 2016-09-02 16:12 GMT+02:00 Adam Cornett :
> >
> > > It was my understanding that the change in MyFaces is part of the fix
> > > (making the BeanManager reference transient to prevent it being
> > serialized
> > > to begin with.)  I can use 2.2.10 and see if the issue returns and
> report
> > > back.
> > >
> > > On Fri, Sep 2, 2016 at 10:07 AM, Romain Manni-Bucau <
> > rmannibu...@gmail.com
> > > >
> > > wrote:
> > >
> > > > @Adam: isnt it fixed in OWB 1.7.0?
> > > >
> > > >
> > > > Romain Manni-Bucau
> > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> > > > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > > > rmannibucau> |
> > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > > > <http://www.tomitribe.com> | JavaEE Factory
> > > > <https://javaeefactory-rmannibucau.rhcloud.com>
> > > >
> > > > 2016-09-02 16:06 GMT+02:00 Adam Cornett :
> > > >
> > > > > Has MyFaces said anything about releasing 2.2.11? I know there is a
> > > fix (
> > > > > https://issues.apache.org/jira/browse/MYFACES-4057) for an issue
> > I've
> > > > > encountered in testing.  If not I can keep pulling in a snapshot of
> > it
> > > > for
> > > > > now so as to not delay the release of everything else that would be
> > > > > included in 7.0.2
> > > > >
> > > > > - Adam
> > > > >
> > > > > On Fri, Sep 2, 2016 at 7:27 AM, Romain Manni-Bucau <
> > > > rmannibu...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Hi guys,
> > > > > >
> > > > > > Marks sent the vote for OWB and Tomcat so sounds like we should
> > > release
> > > > > in
> > > > > > not a too long future.
> > > > > >
> > > > > > I know Mark (struberg) also wants to release BatchEE so we can
> > maybe
> > > > wait
> > > > > > for it as well and then move forward. I'll be quite off for 1
> week
> > on
> > > > the
> > > > > > 16th so depending the schedule of these releases I can work on
> that
> > > > next
> > > > > > week if it we have them all or end of the month.
> > > > > >
> > > > > > Wdyt? Anything you'd like to get in?
> > > > > >
> > > > > > Romain Manni-Bucau
> > > > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > > > > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> > > > > > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > > > > > rmannibucau> |
> > > > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > > > > > <http://www.tomitribe.com> | JavaEE Factory
> > > > > > <https://javaeefactory-rmannibucau.rhcloud.com>
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Adam Cornett
> > > > > adam.corn...@gmail.com
> > > > > (678) 296-1150
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Adam Cornett
> > > adam.corn...@gmail.com
> > > (678) 296-1150
> > >
> >
>
>
>
> --
> Adam Cornett
> adam.corn...@gmail.com
> (678) 296-1150
>

Re: 7.0.2 around the corner?

[Romain Manni-Bucau]

think it was the id generation issue which was causing this one but if you
can test feedback would be very welcomed


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-09-02 16:12 GMT+02:00 Adam Cornett :

> It was my understanding that the change in MyFaces is part of the fix
> (making the BeanManager reference transient to prevent it being serialized
> to begin with.)  I can use 2.2.10 and see if the issue returns and report
> back.
>
> On Fri, Sep 2, 2016 at 10:07 AM, Romain Manni-Bucau  >
> wrote:
>
> > @Adam: isnt it fixed in OWB 1.7.0?
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > <http://www.tomitribe.com> | JavaEE Factory
> > <https://javaeefactory-rmannibucau.rhcloud.com>
> >
> > 2016-09-02 16:06 GMT+02:00 Adam Cornett :
> >
> > > Has MyFaces said anything about releasing 2.2.11? I know there is a
> fix (
> > > https://issues.apache.org/jira/browse/MYFACES-4057) for an issue I've
> > > encountered in testing.  If not I can keep pulling in a snapshot of it
> > for
> > > now so as to not delay the release of everything else that would be
> > > included in 7.0.2
> > >
> > > - Adam
> > >
> > > On Fri, Sep 2, 2016 at 7:27 AM, Romain Manni-Bucau <
> > rmannibu...@gmail.com>
> > > wrote:
> > >
> > > > Hi guys,
> > > >
> > > > Marks sent the vote for OWB and Tomcat so sounds like we should
> release
> > > in
> > > > not a too long future.
> > > >
> > > > I know Mark (struberg) also wants to release BatchEE so we can maybe
> > wait
> > > > for it as well and then move forward. I'll be quite off for 1 week on
> > the
> > > > 16th so depending the schedule of these releases I can work on that
> > next
> > > > week if it we have them all or end of the month.
> > > >
> > > > Wdyt? Anything you'd like to get in?
> > > >
> > > > Romain Manni-Bucau
> > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> > > > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > > > rmannibucau> |
> > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > > > <http://www.tomitribe.com> | JavaEE Factory
> > > > <https://javaeefactory-rmannibucau.rhcloud.com>
> > > >
> > >
> > >
> > >
> > > --
> > > Adam Cornett
> > > adam.corn...@gmail.com
> > > (678) 296-1150
> > >
> >
>
>
>
> --
> Adam Cornett
> adam.corn...@gmail.com
> (678) 296-1150
>

Re: 7.0.2 around the corner?

[Romain Manni-Bucau]

@Adam: isnt it fixed in OWB 1.7.0?


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-09-02 16:06 GMT+02:00 Adam Cornett :

> Has MyFaces said anything about releasing 2.2.11? I know there is a fix (
> https://issues.apache.org/jira/browse/MYFACES-4057) for an issue I've
> encountered in testing.  If not I can keep pulling in a snapshot of it for
> now so as to not delay the release of everything else that would be
> included in 7.0.2
>
> - Adam
>
> On Fri, Sep 2, 2016 at 7:27 AM, Romain Manni-Bucau 
> wrote:
>
> > Hi guys,
> >
> > Marks sent the vote for OWB and Tomcat so sounds like we should release
> in
> > not a too long future.
> >
> > I know Mark (struberg) also wants to release BatchEE so we can maybe wait
> > for it as well and then move forward. I'll be quite off for 1 week on the
> > 16th so depending the schedule of these releases I can work on that next
> > week if it we have them all or end of the month.
> >
> > Wdyt? Anything you'd like to get in?
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > <http://www.tomitribe.com> | JavaEE Factory
> > <https://javaeefactory-rmannibucau.rhcloud.com>
> >
>
>
>
> --
> Adam Cornett
> adam.corn...@gmail.com
> (678) 296-1150
>

7.0.2 around the corner?

[Romain Manni-Bucau]

Hi guys,

Marks sent the vote for OWB and Tomcat so sounds like we should release in
not a too long future.

I know Mark (struberg) also wants to release BatchEE so we can maybe wait
for it as well and then move forward. I'll be quite off for 1 week on the
16th so depending the schedule of these releases I can work on that next
week if it we have them all or end of the month.

Wdyt? Anything you'd like to get in?

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

Re: reworking the website?

[Romain Manni-Bucau]

added a basic example section:
http://tomee.apache.org/ng/examples/index.html

feel free to hack anything you want there like tagging or whatever but
basic feature is there; Idea was to provide a search box instead of
organizing the example to let them be browsable more efficiently. Doesn't
prevent to organize them later but we need to find a convention then (page
is generated)


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-04-12 7:47 GMT+02:00 Romain Manni-Bucau :

> Hi Chris
>
> Le 12 avr. 2016 02:33, "Chris Owens"  a
> écrit :
> >
> > Speaking as a reasonably-well-informed user of TomEE, who has been into
> the
> > code, but who is still very much an outsider, I would say that
> documentation
> > is probably the biggest obstacle to wider uptake. It's a project I would
> be
> > happy to work on. I'm willing to put the work in to do some serious
> writing.
> >
> > Before we talk about documentation workflow, git vs other models, CMSes,
> > etc., I think there are some much more basic questions to address:
> >
> > -- Who is the intended audience for each major portion of the
> documentation?
> >
>
> I d say people not able to go to code and in that category 2
> subcategories: admin and dev.
>
> > -- For TomEE Components that are not owned by this project (e.g., Tomcat,
> > cxf, JMS, etc.), how shall our documentation interact with that
> component's
> > "native" documentation? By reference? By duplication? Other?
> >
>
> Reference + enrichment when needed. Really against duplication.
>
> > -- What are the major reference topics that need to be covered? (For
> > example, Contexts, Classloaders, Configuration, Testing, Embedded, etc)?
> >
>
> Idea was to start with some basics and add info depending the list
> questions.
>
> > -- What are the major tutorial or "how-to" threads that need to be
> covered?
> >
> >
>
> Same there. Should also probably consider rework very hard examples to
> make them useful and more explicit (arquillian website is a great example
> there).
>
> >
> >
> >
> > --
> > View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/reworking-the-website-tp4677918p4678116.html
> > Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Issue in starting TomEE as window Service

[Romain Manni-Bucau]

ok, then only issue i can think about is a previous tom* (tomcat or tomee)
service you didnt deinstall before installing this one


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-09-01 16:23 GMT+02:00 Dignesh :

> Hi Romain,
>
> Thank you very much for quick reply.
>
> Yes I have disabled the UAC and also I created the service as
> administrator.
> Attached the screenshot for reference.
>
> UAC.jpg <http://tomee-openejb.979440.n4.nabble.com/file/n4679998/UAC.jpg>
>
>
>
>
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Issue-in-starting-TomEE-as-window-
> Service-tp4679996p4679998.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Issue in starting TomEE as window Service

[Romain Manni-Bucau]

Hi

did you install it as an admin? see
http://tomcat.apache.org/tomcat-8.5-doc/windows-service-howto.html doc
(search for UAC string)


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-09-01 14:17 GMT+02:00 Dignesh :

> Hi,
>
> I am trying to create TomEE as window Service.
> What I did was modified the service.bat file shipped in %TOMEE_HOME%\bin
> directory.
>
> Service is getting created successfully. But when I start the service it is
> not getting started.
>
> Below is the error I see in log file. I have attached the modified bat file
> for reference.
>
> Can everyone please help me in finding where I am going wrong.
>
> Thank you very much in advance.
>
> [2016-09-01 17:48:38] [info]  [14108] Commons Daemon procrun (1.0.14.0
> 64-bit) started
> [2016-09-01 17:48:38] [info]  [14108] Running 'Apache' Service...
> [2016-09-01 17:48:39] [info]  [10736] Starting service...
> [2016-09-01 17:48:39] [error] [10736] Missing service ImageFile
> [2016-09-01 17:48:39] [error] [10736] ServiceStart returned 1
> [2016-09-01 17:48:39] [info]  [14108] Run service finished.
> [2016-09-01 17:48:39] [info]  [14108] Commons Daemon procrun finished
>
>
> service.bat
> <http://tomee-openejb.979440.n4.nabble.com/file/n4679996/service.bat>
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Issue-in-starting-TomEE-as-window-Service-tp4679996.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: tomee git commit: useless code since done in the connection close

[Romain Manni-Bucau]

+1, doesnt make sense to do both to me, in particular with our pooling
abstraction

Le 29 août 2016 21:42, "Jonathan Gallimore"  a
écrit :

> Indeed it is, and I think your change to do that in connection.close() is
> actually a better fix (thanks!), but we still have an issue, and that is
> the order in Client.java:
>
>if (null != in) {
> try {
> in.close();
> } catch (final Throwable e) {
> //Ignore
> }
> }
>
> if (null != conn) {
> try {
> conn.close();
> } catch (final Throwable t) {
> logger.log(Level.WARNING, "Error closing connection
> with server: " + t.getMessage(), t);
> }
> }
>
> The inputstream will be closed before conn.close() - effectively closing
> the stream while under certain circumstances there is still more to read.
> This specifically happens when the response from the server uses
> Transfer-encoding: chunked, and the client is connecting over https. The
> effect in this case
> is that HttpsUrlConnection won't reuse the connection (effectively there is
> no keep-alive) and the SSL handshake has to happen all over again on the
> next call.
>
> As I mentioned, I prefer your solution - feels neater. The question is, how
> to solve this small ordering issue - how about moving the in.close() /
> out.close() logic
> to each of the implementations of Connection? (HttpConnection,
> SocketConnection and an anonymous class in MockConnectionFactory)
>
> Thoughts?
>
> Jon
>
>
> On Mon, Aug 29, 2016 at 10:23 AM,  wrote:
>
> > Repository: tomee
> > Updated Branches:
> >   refs/heads/master a26d99040 -> 8514d47c5
> >
> >
> > useless code since done in the connection close
> >
> >
> > Project: http://git-wip-us.apache.org/repos/asf/tomee/repo
> > Commit: http://git-wip-us.apache.org/repos/asf/tomee/commit/8514d47c
> > Tree: http://git-wip-us.apache.org/repos/asf/tomee/tree/8514d47c
> > Diff: http://git-wip-us.apache.org/repos/asf/tomee/diff/8514d47c
> >
> > Branch: refs/heads/master
> > Commit: 8514d47c58b60e8288ccffa28a1bc3f33b4cbdfd
> > Parents: a26d990
> > Author: Romain manni-Bucau 
> > Authored: Mon Aug 29 11:22:51 2016 +0200
> > Committer: Romain manni-Bucau 
> > Committed: Mon Aug 29 11:22:51 2016 +0200
> >
> > --
> >  .../java/org/apache/openejb/client/Client.java | 17
> -
> >  1 file changed, 17 deletions(-)
> > --
> >
> >
> > http://git-wip-us.apache.org/repos/asf/tomee/blob/8514d47c/
> > server/openejb-client/src/main/java/org/apache/openejb/
> client/Client.java
> > --
> > diff --git a/server/openejb-client/src/main/java/org/apache/openejb/
> client/Client.java
> > b/server/openejb-client/src/main/java/org/apache/openejb/
> > client/Client.java
> > index d017e7f..837a2ea 100644
> > --- a/server/openejb-client/src/main/java/org/apache/openejb/
> > client/Client.java
> > +++ b/server/openejb-client/src/main/java/org/apache/openejb/
> > client/Client.java
> > @@ -405,23 +405,6 @@ public class Client {
> >  }
> >
> >  if (null != in) {
> > -
> > -// consume anything left in the buffer if we're running
> > in http(s) mode
> > -if (HttpConnectionFactory.HttpConnection.class.
> isInstance(conn))
> > {
> > -final HttpConnectionFactory.HttpConnection
> > httpConnection = HttpConnectionFactory.HttpConnection.class.cast(conn);
> > -if ("https".equalsIgnoreCase(
> httpConnection.getURI().getScheme()))
> > {
> > -
> > -try {
> > -int read = 0;
> > -while (read > -1) {
> > -read = in.read();
> > -}
> > -} catch (Throwable e) {
> > -// ignore
> > -}
> > -}
> > -}
> > -
> >  try {
> >  in.close();
> >  } catch (final Throwable e) {
> >
> >
>
>
> --
> Jonathan Gallimore
> http://twitter.com/jongallimore
> http://www.tomitribe.com
>

WebBeansContext.currentInstance() change

[Romain Manni-Bucau]

Hi guys,

a quick heads up to say I changed the way we look up CDI context
(WebBeansContext to be concrete).

Before we had some fallback logic to find it if all known ones failed. This
was acceptable maybe in flat (1 webapp or 1 ejbjar *only*) embedded mode
but was quite broken in other modes leading to really annoying conflicts
(see TOMEE-1913 for one of the cases).

the build
https://ci.apache.org/builders/tomee-trunk-ubuntu/builds/495/steps/test/logs/stdio
is back to stable (the only failing module is removed in next commit cause
it was legacy already).

Just want to point out that now currentInstance() will throw an
IllegalStateException if the webapp hasn't CDI (there is a spec ticket to
ensure it is what we want but seems it will atm)

Happy to help you investigate some cases if you have doubts.

PS: a nice side effect is we now don't create a fake WebBeansContext
anymore when CDI is not active and leak it which was the case before if you
deploy another webapp with CDI activated in embedded mode.

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

Re: How to configure DLQs and Redelivery policies (default and queue specific) in tomee.xml

[Romain Manni-Bucau]

Hi Dignesh,

it depends your setup, the BrokerUrl support is maybe not enough depending
what you want to do (see current supported syntax:
https://issues.apache.org/jira/browse/TOMEE-1550 and
org.apache.activemq.broker.util.RedeliveryPlugin and
org.apache.activemq.plugin.DiscardingDLQBrokerPlugin). If so you need to
configure the broker using xbean-spring setup which would lead to
configuring exactly like it is documented on activemq website once you
added the few needed jars.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-08-24 15:04 GMT+02:00 Dignesh :

> Hi,
>
> I am using apache-tomee-plus-7.0.1. I need to configure DLQ's and
> Redelivery
> policies for Resources present in tomee.xml file. I don't find any thing
> specific way to configure this in tomee.xml file.
> Can anyone please help me on how to acheive this ?
>
> Thanks in advance.
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/How-to-configure-DLQs-and-Redelivery-
> policies-default-and-queue-specific-in-tomee-xml-tp4679862.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: ClassNotFoundException: com.sun.el.ExpressionFactoryImpl in embedded Arquillian container

[Romain Manni-Bucau]

You leak cdi 1.0 api somewhere (through the bom?). Advice would be to not
share arquillian deps too much. Transitivity hurts when stack is not
homogeneous.

Le 24 août 2016 00:47, "Ivan St. Ivanov"  a
écrit :

> Hey, Soro! :)
>
> That's what I actually have: profile for each container. And when I add
> TomEE's javaee-api dependency to TomEE's profile, I get the above
> exception. Which I don't get if the dependency is outside the profile. But
> then WildFly doesn't work :(
>
> On Wed, Aug 24, 2016 at 1:35 AM, Daniel Cunha 
> wrote:
>
> > profile can fix it.
> > So, you can create a widfly profile and a tomee profile. :)
> >
> > On Tue, Aug 23, 2016 at 7:23 PM, Ivan St. Ivanov <
> ivan.st.iva...@gmail.com
> > >
> > wrote:
> >
> > > Ah, now I understand, thanks for the clarification, Romain!
> > >
> > > So, if I add TomEE's javaee-api dependency to my POM, the TomEE
> Embedded
> > > tests pass. But as you might guess, the WildFly container ones fail.
> > That's
> > > why I decided to put each one container's javaee-api dependency in its
> > own
> > > profile. That's how TomEE's profile's dependencies looked like the
> > > following:
> > >
> > > 
> > > 
> > > org.apache.tomee
> > > javaee-api
> > > provided
> > > 
> > > 
> > > org.apache.tomee
> > > arquillian-tomee-embedded
> > > 7.0.1
> > > test
> > > 
> > >
> > > Now the test failed again, this time with different exception:
> > >
> > > java.lang.IncompatibleClassChangeError: Class
> > > org.apache.webbeans.conversation.ConversationStorageBean does not
> > > implement
> > > the requested interface javax.enterprise.inject.spi.BeanAttributes
> > > at
> > > org.apache.webbeans.component.BeanAttributesImpl.(
> > > BeanAttributesImpl.java:59)
> > > at
> > > org.apache.webbeans.component.third.ThirdpartyBeanImpl.<
> > > init>(ThirdpartyBeanImpl.java:41)
> > > at
> > > org.apache.webbeans.component.third.PassivationCapableThirdpartyBe
> > > anImpl.(PassivationCapableThirdpartyBeanImpl.java:32)
> > > at
> > > org.apache.webbeans.container.BeanManagerImpl.addInternalBean(
> > > BeanManagerImpl.java:373)
> > > at
> > > org.apache.webbeans.conversation.ConversationManager.(
> > > ConversationManager.java:69)
> > > at
> > > org.apache.webbeans.config.WebBeansContext.(
> > > WebBeansContext.java:158)
> > > at
> > > org.apache.webbeans.config.WebBeansContext.(
> > > WebBeansContext.java:116)
> > >
> > > I read elsewhere that this might be caused by different versions of CDI
> > on
> > > the server and in the webapp. But what did I do to make this violation?
> > > While the dependency was outside of the profile, it used to work.
> > >
> > > Cheers,
> > > Ivan
> > >
> > > P.S. I am trying to make this project follow the microprofile
> > requirements,
> > > so making the Arquillian tests runnable on all runtimes is a must :)
> > >
> > >
> > > On Wed, Aug 24, 2016 at 12:31 AM, Romain Manni-Bucau <
> > > rmannibu...@gmail.com>
> > > wrote:
> > >
> > > > Yes, not using tomcat el api - shaded in tomee javaee-api - you get
> > > > glassfish defaults.
> > > >
> > > > Ensure to use org.apache.tomee:javaee-api
> > > >
> > > > Le 23 août 2016 23:28, "John D. Ament"  a
> > écrit :
> > > >
> > > > > Don't forget, TomEe will ship Geronimo jars.  If you reference
> > Javax.el
> > > > > you'll get duplicates
> > > > >
> > > > > On Aug 23, 2016 17:25, "Alex Soto"  wrote:
> > > > >
> > > > > > Then now I have no idea, it seems emedded instance does not
> contain
> > > the
> > > > > > javax.el interpreter. Can you try using remote artifacts?
> > > > > >
> > > > > > El 23 ago. 2016 11:19 p. m., "Ivan St. Ivanov" <
> > > > ivan.st.iva...@gmail.com
> > > > > >
> > > > > > escribió:
> > > > > >
> > > > > > > Hey Alex :)
> > >

Re: ClassNotFoundException: com.sun.el.ExpressionFactoryImpl in embedded Arquillian container

[Romain Manni-Bucau]

Yes, not using tomcat el api - shaded in tomee javaee-api - you get
glassfish defaults.

Ensure to use org.apache.tomee:javaee-api

Le 23 août 2016 23:28, "John D. Ament"  a écrit :

> Don't forget, TomEe will ship Geronimo jars.  If you reference Javax.el
> you'll get duplicates
>
> On Aug 23, 2016 17:25, "Alex Soto"  wrote:
>
> > Then now I have no idea, it seems emedded instance does not contain the
> > javax.el interpreter. Can you try using remote artifacts?
> >
> > El 23 ago. 2016 11:19 p. m., "Ivan St. Ivanov"  >
> > escribió:
> >
> > > Hey Alex :)
> > >
> > > I'm using the Arquillian Universe BOM Alpha 3. Downgraded to Alpha 2,
> but
> > > getting the same exception.
> > >
> > > Cheers,
> > > Ivan
> > >
> > > On Wed, Aug 24, 2016 at 12:15 AM, Alex Soto  wrote:
> > >
> > > > Are you using arquillian 1.1.11, if so try with .10
> > > >
> > > > El 23 ago. 2016 10:47 p. m., "Ivan St. Ivanov" <
> > ivan.st.iva...@gmail.com
> > > >
> > > > escribió:
> > > >
> > > > > Hi folks,
> > > > >
> > > > > I have an issue when I run Arquillian test in the TomEE embedded
> > > > > container, version 7.0.1. Originally I wanted to run a test as
> client
> > > > > (@RunAsClient) that checks a RESTful web service's response [1].
> > > However,
> > > > > during the deployment of the ShrinkWrap archive I get the following
> > > > > exception:
> > > > >
> > > > > javax.el.ELException: Provider com.sun.el.ExpressionFactoryImpl
> not
> > > > found
> > > > > at javax.el.FactoryFinder.newInstance(FactoryFinder.java:101)
> > > > > at javax.el.FactoryFinder.find(FactoryFinder.java:197)
> > > > > at javax.el.ExpressionFactory.newInstance(ExpressionFactory.
> > java:197)
> > > > > at javax.el.ExpressionFactory.newInstance(ExpressionFactory.
> > java:168)
> > > > > at org.apache.jasper.runtime.JspApplicationContextImpl.(
> > > > > JspApplicationContextImpl.java:46)
> > > > > at org.apache.jasper.runtime.JspApplicationContextImpl.
> getInstance(
> > > > > JspApplicationContextImpl.java:76)
> > > > > at org.apache.jasper.runtime.JspFactoryImpl.
> > getJspApplicationContext(
> > > > > JspFactoryImpl.java:217)
> > > > > at org.apache.openejb.cdi.OpenEJBLifecycle.setJspELFactory(
> > > > > OpenEJBLifecycle.java:416)
> > > > > at org.apache.openejb.cdi.OpenEJBLifecycle.
> initializeServletContext(
> > > > > OpenEJBLifecycle.java:387)
> > > > > at org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(
> > > > > TomcatWebAppBuilder.java:1423)
> > > > >
> > > > > The whole exception trace is attached to this emal.
> > > > >
> > > > > I wondered what the problem is, so I added a dummy resource [2]
> that
> > > > > doesn't involve CDI. And then ran a test [3] as client and it went
> > > fine.
> > > > > Then I added a test that doesn't run as client and involves a class
> > > that
> > > > > uses CDI [4]. And I got the same exception as above.
> > > > >
> > > > > Do you know what is the reason for the failure? The same tests run
> > > > > successfully on the WildFly 10 managed container. And they keep
> > failing
> > > > on
> > > > > TomEE embedded even with an empty beans.xml added to the ShrinkWrap
> > web
> > > > > archive.
> > > > >
> > > > > The app under test is runnable under TomEE 7 Plume as well as via
> the
> > > > > Maven plugin.
> > > > >
> > > > > Thank you,
> > > > > Ivan
> > > > >
> > > > > [1] https://github.com/ivannov/javaee-actuator/blob/
> > > > > arquillian/javaee-actuator/src/test/java/io/github/
> > > > > ivannov/actuator/resources/MetricsResourceTest.java
> > > > > [2] https://github.com/ivannov/javaee-actuator/blob/
> > > > > arquillian/javaee-actuator/src/main/java/io/github/
> > > > > ivannov/actuator/resources/HelloResource.java
> > > > > [3] https://github.com/ivannov/javaee-actuator/blob/
> > > > > arquillian/javaee-actuator/src/test/java/io/github/
> > > > > ivannov/actuator/resources/HelloResourceTest.java
> > > > > [4] https://github.com/ivannov/javaee-actuator/blob/
> > > > > arquillian/javaee-actuator/src/test/java/io/github/
> > > > > ivannov/actuator/resources/BeansResourceTest.java
> > > > >
> > > >
> > >
> >
>

Re: Migration of Spring bean web application

[Romain Manni-Bucau]

tempted to say it is a spring question (so not the right forum)

that said spring uses by default applicationContext.xml name but you likely
configured beans.xml in web.xml or somewhere else


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-08-22 16:38 GMT+02:00 Aruna Kalagnanam :

> After removing the WEB-INF/beans.xml, I get a
> java.io.FileNotFoundException: Could not open ServletContext resource
> [/WEB-INF/beans.xml].
> If the beans.xml isnt present, how would Spring figure out the
> configuration.
> Sorry if I'm being dumb about this, I'm missing something basic here.
>
> Thanks,
> Aruna.
>
>
> On Mon, Aug 22, 2016 at 6:27 PM, Romain Manni-Bucau  >
> wrote:
>
> > 2016-08-22 14:51 GMT+02:00 Aruna Kalagnanam :
> >
> > > Hi Romain
> > >
> > > If I understood properly, you are saying that an empty beans.xml should
> > be
> > > present.
> >
> >
> > Think I said the opposite: don't create a spring beans.xml in WEB-INF. I
> > know it is a common practise but this file is a CDI file with a standard
> > namespace which of course - wouldn't be fun otherwise ;) - doesn't match
> > spring one.
> >
> >
> > > Do I need to include any other configuration ? Will openejb-core
> > > take care of integration between EE and Spring.
> > >
> > >
> > The opposite: spring is the one taking care of the EE integration and not
> > EE taking care of spring integration.
> >
> >
> > > Thanks,
> > > Aruna.
> > >
> > > On Thu, Aug 11, 2016 at 7:37 PM, Romain Manni-Bucau <
> > rmannibu...@gmail.com
> > > >
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > If i get it right you want to use spring in tomee? if so you need to
> > NOT
> > > > use WEB-INF/beans.xml cause it is a EE descriptor which needs to
> > respect
> > > EE
> > > > namespace (obviously not the case of spring application contexts ;)).
> > > >
> > > >
> > > > Romain Manni-Bucau
> > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> > > > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > > > rmannibucau> |
> > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > > > <http://www.tomitribe.com> | JavaEE Factory
> > > > <https://javaeefactory-rmannibucau.rhcloud.com>
> > > >
> > > > 2016-08-11 16:01 GMT+02:00 Aruna Kalagnanam :
> > > >
> > > > > Hi All,
> > > > >
> > > > > I'm trying to migrate a Spring bean web application to run on
> > TomEE+. I
> > > > > want to continue to use Spring beans, without introducing JavaEE
> > beans.
> > > > >
> > > > > I tried the following steps :
> > > > >
> > > > > 1) Copied the war as-is into the webapps folder of TomEE+. Startup
> > > error
> > > > > due to "javax.xml.bind.UnmarshalException: unexpected element
> (uri:"
> > > > > http://java.sun.com/xml/ns/javaee";, local:"import")."
> > > > >
> > > > > 2) Copied openejb-core.jar into WEB-INF/lib; same startup error.
> > > > >
> > > > > 3) Modified beans.xml to include javaee namespace; same startup
> > error.
> > > > >
> > > > > Can you point me to documentation references that cover porting a
> > > spring
> > > > > bean application to TomEE+  or help me with some pointers.
> > > > >
> > > > > Thanks,
> > > > > Aruna.
> > > > >
> > > >
> > >
> >
>

Re: Migration of Spring bean web application

[Romain Manni-Bucau]

2016-08-22 14:51 GMT+02:00 Aruna Kalagnanam :

> Hi Romain
>
> If I understood properly, you are saying that an empty beans.xml should be
> present.


Think I said the opposite: don't create a spring beans.xml in WEB-INF. I
know it is a common practise but this file is a CDI file with a standard
namespace which of course - wouldn't be fun otherwise ;) - doesn't match
spring one.


> Do I need to include any other configuration ? Will openejb-core
> take care of integration between EE and Spring.
>
>
The opposite: spring is the one taking care of the EE integration and not
EE taking care of spring integration.


> Thanks,
> Aruna.
>
> On Thu, Aug 11, 2016 at 7:37 PM, Romain Manni-Bucau  >
> wrote:
>
> > Hi,
> >
> > If i get it right you want to use spring in tomee? if so you need to NOT
> > use WEB-INF/beans.xml cause it is a EE descriptor which needs to respect
> EE
> > namespace (obviously not the case of spring application contexts ;)).
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > <http://www.tomitribe.com> | JavaEE Factory
> > <https://javaeefactory-rmannibucau.rhcloud.com>
> >
> > 2016-08-11 16:01 GMT+02:00 Aruna Kalagnanam :
> >
> > > Hi All,
> > >
> > > I'm trying to migrate a Spring bean web application to run on TomEE+. I
> > > want to continue to use Spring beans, without introducing JavaEE beans.
> > >
> > > I tried the following steps :
> > >
> > > 1) Copied the war as-is into the webapps folder of TomEE+. Startup
> error
> > > due to "javax.xml.bind.UnmarshalException: unexpected element (uri:"
> > > http://java.sun.com/xml/ns/javaee";, local:"import")."
> > >
> > > 2) Copied openejb-core.jar into WEB-INF/lib; same startup error.
> > >
> > > 3) Modified beans.xml to include javaee namespace; same startup error.
> > >
> > > Can you point me to documentation references that cover porting a
> spring
> > > bean application to TomEE+  or help me with some pointers.
> > >
> > > Thanks,
> > > Aruna.
> > >
> >
>

Re: Minimal components in TomEE Embedded Server

[Romain Manni-Bucau]

Let us know if you need any help on particular topics not yet opened on
another thread


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-08-16 15:41 GMT+02:00 Sathwik :

> Hi Romain,
>
> I have the initial setup ready. I have done some initial work and got the
> package ready. Though there are some more things that needs to be attended
> like testing the packaged server.
>
> Jira: https://issues.apache.org/jira/browse/ODE-1060
> Source Git branch: ODE-1060 (On apache's git and github as well
> github.com/apache/ode)
> Sub modules within ODE source: tomee, tomee-server
> Jenkins: ODE-1060-experimental
>
> Embedded server named ode-tomee-server-1.3.7-SNAPSHOT.zip is packaged
> within
> https://builds.apache.org/me/my-views/view/All/job/ODE-1060-experimental/
> lastSuccessfulBuild/artifact/distro/target/apache-ode-war-
> 1.3.7-SNAPSHOT.zip
>
> I have posted few question on the user list.
>
> regards,
> sathwik
>
> On 2016-07-05 17:45 (+0530), Romain Manni-Bucau 
> wrote:
> > 2016-07-05 14:13 GMT+02:00 Sathwik :
> >
> > > Hi Romain,
> > >
> > > Thanks for the quick reply,
> > >
> > > We use Ruby & Rake for the builds, moved out of maven a very long time
> > > ago. We have a docker image and use it to build on Jenkins. It works
> for
> > > local builds as well.
> > >
> > > So, we will need to enhance the current ruby based build script to
> have an
> > > embedded ODE server, which I will do.
> > >
> > > I had encountered some issues with OpenJPA 2.4 when integrating ODE
> with
> > > TomEE and hence I had to downgrade . Will see if I have noted the
> problems.
> > >
> > > Thanks for the pointers and I have just started to look into the TomEE
> > > code.
> > >
> > > I will raise a JIRA issue explaining the goal of embedded ODE server
> and
> > > share it here.
> > >
> > > ODE is available on Git repo. What do you suggest for the working
> branch
> > > to help us?
> > >
> > >
> > Anything public, even a github repo is fine, just needs to be on a
> trusted
> > server (asf or github for instance). If ODE has PR integration it can
> also
> > be an option.
> >
> >
> > > regards,
> > > sathwik
> > >
> > > On 2016-07-05 15:47 (+0530), Romain Manni-Bucau  >
> > > wrote:
> > > > Hello
> > > >
> > > > few questions before answering more specifically: can you use mvn to
> > > build
> > > > this server - I know ODE has a pom but not sure if it is to make
> jenkins
> > > > happy or if it is really used. If so tomee-maven-plugin allows to do
> what
> > > > you do in your script more or less in a "standard" fashion, only
> trick
> > > > would be to have an axis and a EE war but this is very doable with
> > > > mvn-war-plugin.
> > > >
> > > >
> > > > Now more specifically about your use case:
> > > > 1. the downgrade of JPA is normally useless (JPA 2 supports JPA 1)
> > > > 2. Configuration of tomee embedded or standalone is the same (either
> > > > tomee.xml or - recommanded for embedded - through system
> > > > properties/system.properties)
> > > >
> > > >
> > > > About how to bootstrap/configure tomee-embedded here is the doc:
> > > > http://tomee.apache.org/ng/advanced/tomee-embedded/, let me know if
> > > > anything is unclear.
> > > >
> > > > If you want to do a fatjar of ode you can get started with this page
> as
> > > > well http://tomee.apache.org/ng/advanced/shading/index.html
> > > >
> > > > If you push a working branch somewhere I'm happy to help if I have
> enough
> > > > guidance on the goal.
> > > >
> > > >
> > > >
> > > > Romain Manni-Bucau
> > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> > > > <http://rmannibucau.wordpress.com> | Github <
> > > https://github.com/rmannibucau> |
> > > &g

Re: JTA Transcation Manager configuration in Tomee

[Romain Manni-Bucau]

2016-08-16 7:36 GMT+02:00 sureshshine :

> Thanks for you reply ..
>
> I tried to   type="java:comp/TransactionManager"> and I got the below exception
>
>
Type is the...type so as written in the error message "TransactionManager".
There is a way to hack it there but the easiest solution is the one I
mentionned:


  
  


then just use this bean from spring context to get the txMgr.

Side note: of course you can do the same without spring or with spring but
still programmatically.


>  org.apache.openejb.config.NoSuchProviderException: Cannot determine a
> provider for TransactionManager(id=transactionManager,
> type=java:comp/TransactionManager, provider=null).
>
> Possible valid configurations might be:
>   
> at
> org.apache.openejb.config.ConfigurationFactory.getServiceProvider(
> ConfigurationFactory.java:1324)
> at
> org.apache.openejb.config.ConfigurationFactory.configureService(
> ConfigurationFactory.java:1179)
> at
> org.apache.openejb.config.ConfigurationFactory.getOpenEjbConfiguration(
> ConfigurationFactory.java:514)
> at
> org.apache.openejb.config.ConfigurationFactory.getOpenEjbConfiguration(
> ConfigurationFactory.java:629)
> at
> org.apache.openejb.assembler.classic.Assembler.getOpenEjbConfiguration(
> Assembler.java:503)
> at org.apache.openejb.assembler.classic.Assembler.build(
> Assembler.java:482)
> at org.apache.openejb.OpenEJB$Instance.(OpenEJB.java:150)
> at org.apache.openejb.OpenEJB.init(OpenEJB.java:307)
> at org.apache.tomee.catalina.TomcatLoader.initialize(
> TomcatLoader.java:247)
> at
> org.apache.tomee.catalina.ServerListener.lifecycleEvent(
> ServerListener.java:168)
> at
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(
> LifecycleBase.java:94)
> at
> org.apache.catalina.util.LifecycleBase.setStateInternal(
> LifecycleBase.java:401)
> at org.apache.catalina.util.LifecycleBase.init(
> LifecycleBase.java:115)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:606)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:629)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:311)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:494)
>
> Spring Context file as below
>
>  class="org.springframework.transaction.jta.JtaTransactionManager"/>
>
> Please help me to proceed further.
>
> Thanks much
>
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/JTA-Transcation-Manager-configuration-in-
> Tomee-tp4679716p4679753.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: JTA Transcation Manager configuration in Tomee

[Romain Manni-Bucau]

Use java:comp/TransactionManager or openejb:Resource/{resource or txmgr id
in tomee.xml}

In spring you can also use
org.apache.openejb.OpenEJB.getTransactionManager() returned value - it is a
static method so configurable in appctx.xml

Le 13 août 2016 14:43, "sureshshine"  a écrit :

> Hi All,
>
> I tired to configure JTA transaction manager in tomee plume and below is my
> configuration
>
> tomee.xml
>
> 
> adler32Checksum = true
> bufferSizeKb = 32
> checksumEnabled = true
> defaultTransactionTimeout = 10 minutes
> flushSleepTime = 50 Milliseconds
> logFileDir = txlog
> logFileExt = log
> logFileName = howl
> maxBlocksPerFile = -1
> maxBuffers = 0
> maxLogFiles = 2
> minBuffers = 4
> threadsWaitingForceThreshold = -1
> txRecovery = false
> 
>
> Spring Configuration File
>
>  class="org.springframework.transaction.jta.JtaTransactionManager">
>  ref="transactionManager">
>
> I know the configuration is wrong but I am not sure how to configured the
> JTA based transaction in Tomee Plume.
>
> Thanks in Advance.
>
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/JTA-Transcation-Manager-configuration-in-
> Tomee-tp4679716.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Migration of Spring bean web application

[Romain Manni-Bucau]

Hi,

If i get it right you want to use spring in tomee? if so you need to NOT
use WEB-INF/beans.xml cause it is a EE descriptor which needs to respect EE
namespace (obviously not the case of spring application contexts ;)).


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-08-11 16:01 GMT+02:00 Aruna Kalagnanam :

> Hi All,
>
> I'm trying to migrate a Spring bean web application to run on TomEE+. I
> want to continue to use Spring beans, without introducing JavaEE beans.
>
> I tried the following steps :
>
> 1) Copied the war as-is into the webapps folder of TomEE+. Startup error
> due to "javax.xml.bind.UnmarshalException: unexpected element (uri:"
> http://java.sun.com/xml/ns/javaee";, local:"import")."
>
> 2) Copied openejb-core.jar into WEB-INF/lib; same startup error.
>
> 3) Modified beans.xml to include javaee namespace; same startup error.
>
> Can you point me to documentation references that cover porting a spring
> bean application to TomEE+  or help me with some pointers.
>
> Thanks,
> Aruna.
>

Re: TomEE 7.0.1 with Windows

[Romain Manni-Bucau]

2016-08-01 15:43 GMT+02:00 Joerg Jans :

> Romain Manni-Bucau wrote
> > Ok, was just to ensure it was not a more serious issue.
> >
> > Do you want to work on a patch?
>
> Do you need more than the batches I attached in the original post?
>
>
>
best is to attach a diff on a jira created on project
https://issues.apache.org/jira/browse/TOMEE

Typically batches are not plain files in the sources (excepted tomee.bat)
so either you need to modify the changes we do at
https://github.com/apache/tomee/blob/master/tomee/tomee-common/src/main/java/org/apache/tomee/installer/Installer.java#L489
or it is a tomcat issues (in term of source code responsability) and you
need to open an issue for tomcat (see
http://tomcat.apache.org/bugreport.html)

Feel free to ask for help if anything is unclear or if you need some
guidance on how to build and test tomee.


>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-7-0-1-with-Windows-tp4679320p4679560.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Problem with Manager GUI

[Romain Manni-Bucau]

@Eduardo: is the behavior you see different from a plain tomcat 8.5?
Normally we fully rely on it.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-07-29 17:21 GMT+02:00 Eduardo Rotundo :

> Hi.
>
> I downloaded the last version of Apache TomEE Plus but when i click the
> Manager App to enter site to view, the system don’t ask to me for the user
> and password to enter. Previously configured Tomcat-users.xml and enable a
> user to enter to the system.
>
> I make a downgrade to versión 1.7.4 and the problem not exist
>
> Best regards
>
> Eduardo Rotundo
>
> Enviado desde Correo<https://go.microsoft.com/fwlink/?LinkId=550986> para
> Windows 10
>
>

Re: TomEE 7.0.1 with Windows

[Romain Manni-Bucau]

Ok, was just to ensure it was not a more serious issue.

Do you want to work on a patch?

Le 28 juil. 2016 09:06, "Joerg Jans"  a écrit :

> That works without any adaptions.
>
> Unfortunately the MS guys love whitespaces and there are environments where
> I'm forced to use the standard folders of Windows.
>
>
> Romain Manni-Bucau wrote
> > c:\pathwithoutspace\tomee should work AFAIK
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau>; |  Blog
> > <https://blog-rmannibucau.rhcloud.com>; | Old Wordpress Blog
> > <http://rmannibucau.wordpress.com>; | Github
> > <https://github.com/rmannibucau>; |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau>; | Tomitriber
> > <http://www.tomitribe.com>; | JavaEE Factory
> > <https://javaeefactory-rmannibucau.rhcloud.com>;
>
>
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-7-0-1-with-Windows-tp4679320p4679524.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Tomme+ and JMS with JNDI configuration

[Romain Manni-Bucau]

https://github.com/rmannibucau/lookup-from-spring-in-tomee uses that,
lookup works and is done with first solution:
https://github.com/rmannibucau/lookup-from-spring-in-tomee/blob/master/src/main/webapp/WEB-INF/applicationContext.xml#L13


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-07-22 14:44 GMT+02:00 sureshshine :

> Thanks .. It's not working, Still i am getting null exception for
> connectionFactory. I changed the spring configuration as you suggested ( I
> tried both )
>
>  jndi-name="openejb:Resource/jms/ConnectionFactory"
> lookup-on-startup="false"
> proxy-interface="javax.jms.ConnectionFactory"/>
>
> and
>
>  jndi-name="java:openejb/Resource/ConnectionFactory"
> lookup-on-startup="false" proxy-interface="javax.jms.ConnectionFactory"/>
>
> Please help me to get it resolved.
>
> Thanks much.
>
>
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Tomme-and-JMS-with-JNDI-configuration-tp4679415p4679459.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Tomme+ and JMS with JNDI configuration

[Romain Manni-Bucau]

Add prefix openejb:Resource/ or java:openejb/Resource/ to id value for
spring lookup

Le 22 juil. 2016 12:19, "sureshshine"  a écrit :

> Thanks much for your reply.
>
> I need one more clarification and added a jndi resource in tomee.xml as
> follows,
>
> 
> BrokerXmlConfig = xbean:file:/conf/activemq.xml
> ServerUrl = tcp://localhost:61616
> 
>
>   
> connectionMaxIdleTime = 15 Minutes
> connectionMaxWaitTime = 5 seconds
> poolMaxSize = 10
> poolMinSize = 0
> resourceAdapter = MyJmsResourceAdapter
> transactionSupport = xa
>   
>
> I am able to see the resource id "jms/ConnectionFactory" in tomee+ catalina
> log. I tried to get that instance in my application context file as
> follows,
> but instance (connectionFactory) was null.
>
>  lookup-on-startup="false" proxy-interface="javax.jms.ConnectionFactory"/>
>
> private ConnectionFactory connectionFactory;
>
> Also added the following configuration in tomee+ web.xml and context.xml
> and
> tried , but i am unable to get that instance (
> connectionFactory)
>
> resource-ref>
> JMS JNDI Connection
> jms/ConnectionFactory
> javax.jms.ConnectionFactory
> Container
> 
>
> Please let me know what's needs to be done to get the connectionFactory
> instance in my application.
>
> Thanks
>
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Tomme-and-JMS-with-JNDI-configuration-tp4679415p4679454.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Tomme+ and JMS with JNDI configuration

[Romain Manni-Bucau]

Hi

not sure if this jndi.properties is expected to work but tomee
configuration is intended to go in tomee.xml:
- http://tomee.apache.org/jms-resources-and-mdb-container.html
- http://tomee.apache.org/jmsconnectionfactory-config.html
- http://tomee.apache.org/ng/admin/configuration/resources.html


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-07-21 10:42 GMT+02:00 sureshshine :

> Hi All,
>
> I integrated ActiveMQ with Tomee+ and I tried to configure JMS connection
> by
> using jndi but it was not working.
>
> I created jndi.properties and placed that in webapps\activemq\WEB-INF\ ,
> ActiveMQ console war which is running in the tomee+
>
>
> java.naming.factory.initial =
> org.apache.activemq.jndi.ActiveMQInitialContextFactory
>
> # use the following property to configure the default connector
> #java.naming.provider.url = vm://localhost
> java.naming.provider.url = tcp://localhost:61616
>
> # use the following property to specify the JNDI name the connection
> factory
> # should appear as.
> connectionFactoryNames = connectionFactory, queueConnectionFactory,
> topicConnectionFactry
>
> # register some queues in JNDI using the form
> # queue.[jndiName] = [physicalName]
> queue.MyQueue = MyDestQueue
>
>
> # register some topics in JNDI using the form
> # topic.[jndiName] = [physicalName]
> #topic.MyTopic = example.MyTopic
>
> # END SNIPPET: jndi
>
> Please let know the where i need to add these configuration , in tomee+ or
> activemq war
>
> Thanks in Advance
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Tomme-and-JMS-with-JNDI-configuration-tp4679415.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Example request

[Romain Manni-Bucau]

2016-07-19 16:07 GMT+02:00 Roxanne El Baff :

> Hello,
>
>
Hello


> I have a maven ear project with:
>
>- war maven module
>   - No openEjb or openJPA is used here! Only front end stuff
>   - EJBD module
>   - Main communication with POSTGRES DB by using EJB and JPA.
>   - *Here I should use openEjb and openJPA instead of the regular
> ones?*
>   - What are the required dependencies to use openEJB, openJPA on tomEE
>   to generate entities and JPAControllers by connecting to a
> PostGres 9.5 DB?
>

TomEE provides openejb and openjpa so just add in common.loader (tomee/lib)
postgres jdbc driver jar.


>   - Should I use an older version of POSTGRES 9.5 ?
>
>
Likely depends your database version


> Thank you for your time and help !
>
> Regards,
>
> --
> *Roxanne El Baff*
> Software Developer
> Computer Science Masters Student
> Bauhaus-Universität, Weimar, Germany
>
> +49 (0) 1523 / 9516877
> LinkedIn Profile 
>

Re: TomEE 7.0.1 with Windows

[Romain Manni-Bucau]

c:\pathwithoutspace\tomee should work AFAIK


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-07-18 13:50 GMT+02:00 Joerg Jans :

> Hi Romain,
>
> I installed TomEE to "C:\Program Files\TomEE". Due to the known write
> protection issues I granted "Full Access" to the group Users.
>
> Here is the log from TomEE:
> Using CATALINA_BASE:   "C:\Program Files\TomEE"
> Der Befehl "127.0.0.1" ist entweder falsch geschrieben oder konnte nicht
> gefunden werden.
> Using CATALINA_HOME:   "C:\Program Files\TomEE"
> Using CATALINA_TMPDIR: "C:\Program Files\TomEE\temp"
> Using JRE_HOME:"C:\Program Files\Java\jdk1.8.0_92"
> Using CLASSPATH:   "C:\Program Files\TomEE\bin\bootstrap.jar;C:\Program
> Files\TomEE\bin\tomcat-juli.jar"
>
> The problem is caused by superfluous and missing quotes in the batch files.
>
> Regards,
> Jörg
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-7-0-1-with-Windows-tp4679320p4679372.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Exposing RESTful web services from WEB-INF/lib

[Romain Manni-Bucau]

You can redefine it in conf (conf/exclusions.list), in WEB-INF or we have
include/exclude system property for it.

It is on the refcard https://tomee.apache.org/refcard/refcard.html

Le 16 juil. 2016 16:56, "Daniel Cunha"  a écrit :

> Romain,
>
> has an option to override the excluded jars? :)
>
> On Sat, Jul 16, 2016 at 11:52 AM, Ivan St. Ivanov <
> ivan.st.iva...@gmail.com>
> wrote:
>
> > Hi folks,
> >
> > Thanks everybody for quick responses!
> >
> > @Romain: you were right. After I renamed the jar to just actuator.jar, it
> > worked! Awesome!
> >
> > Cheers,
> > Ivan
> >
> > On Sat, Jul 16, 2016 at 5:41 PM, Romain Manni-Bucau <
> rmannibu...@gmail.com
> > >
> > wrote:
> >
> > > Should clearly but not if called javaee-actuator.jar cause javaee*.jar
> > are
> > > excluded by default.
> > >
> > > Le 16 juil. 2016 16:39, "John D. Ament"  a
> écrit
> > :
> > >
> > > > Looks like he has a master branch where that works properly.
> > > >
> > > > John
> > > >
> > > > On Sat, Jul 16, 2016 at 10:35 AM Alex Soto 
> wrote:
> > > >
> > > > > At mobile now but have you tried adding classes in war project and
> > see
> > > if
> > > > > they work and then extract to jar?
> > > > >
> > > > > El 16 jul. 2016 4:34 p. m., "Ivan St. Ivanov" <
> > > ivan.st.iva...@gmail.com>
> > > > > escribió:
> > > > >
> > > > > > Hi folks,
> > > > > >
> > > > > > I have the following case. I am developing a simple web
> > application,
> > > > > which
> > > > > > is empty for the moment, but contains a jar that exposes RESTful
> > web
> > > > > > services via JAX-RS. Here is the structure:
> > > > > >
> > > > > > - actuator.jar: contains class extending
> > javax.ws.rs.core.Application
> > > > as
> > > > > > well as a class annotated with @Path and containing a method
> > > annotated
> > > > > with
> > > > > > @GET
> > > > > > - actuator.war packages actuator.jar in WEB-INF/lib and apart
> from
> > > that
> > > > > is
> > > > > > empty
> > > > > >
> > > > > > The source code is here:
> > > > > > https://github.com/ivannov/javaee-actuator/tree/split
> > > > > >
> > > > > > I deployed this into TomEE 7.0.1 Plume and when I tried to access
> > my
> > > > > > RESTful resource, I got 404. I don't see anything in the catalina
> > > log.
> > > > > And
> > > > > > these are the application deployment messages form the console:
> > > > > >
> > > > > > INFO - Enterprise application
> > > > > > "/opt/apache-tomee-plume-7.0.1/webapps/actuator" loaded.
> > > > > > INFO - Assembling app:
> > /opt/apache-tomee-plume-7.0.1/webapps/actuator
> > > > > > INFO - Deployed
> > > > > > Application(path=/opt/apache-tomee-plume-7.0.1/webapps/actuator)
> > > > > > INFO - At least one JAR was scanned for TLDs yet contained no
> TLDs.
> > > > > Enable
> > > > > > debug logging for this logger for a complete list of JARs that
> were
> > > > > scanned
> > > > > > but no TLDs were found in them. Skipping unneeded JARs during
> > > scanning
> > > > > can
> > > > > > improve startup time and JSP compilation time.
> > > > > > INFO - Deployment of web application archive
> > > > > > /opt/apache-tomee-plume-7.0.1/webapps/actuator.war has finished
> in
> > > > 1,808
> > > > > ms
> > > > > >
> > > > > > The same works fine in Wildfly 10. It works OK on TomEE as well
> > when
> > > > > > actuator.jar is actually a war and deploy it directly.
> > > > > >
> > > > > > Do I have to do anything special in order to make resources
> > packaged
> > > in
> > > > > > WEB-INF/lib discoverable in TomEE?
> > > > > >
> > > > > > Thanks,
> > > > > > Ivan
> > > > > >
> > > > >
> > > >
> > >
> >
>
>
>
> --
> Daniel Cunha
> https://twitter.com/dvlc_
> http://www.tomitribe.com
> http://www.tomitribe.io
>

Re: Exposing RESTful web services from WEB-INF/lib

[Romain Manni-Bucau]

Should clearly but not if called javaee-actuator.jar cause javaee*.jar are
excluded by default.

Le 16 juil. 2016 16:39, "John D. Ament"  a écrit :

> Looks like he has a master branch where that works properly.
>
> John
>
> On Sat, Jul 16, 2016 at 10:35 AM Alex Soto  wrote:
>
> > At mobile now but have you tried adding classes in war project and see if
> > they work and then extract to jar?
> >
> > El 16 jul. 2016 4:34 p. m., "Ivan St. Ivanov" 
> > escribió:
> >
> > > Hi folks,
> > >
> > > I have the following case. I am developing a simple web application,
> > which
> > > is empty for the moment, but contains a jar that exposes RESTful web
> > > services via JAX-RS. Here is the structure:
> > >
> > > - actuator.jar: contains class extending javax.ws.rs.core.Application
> as
> > > well as a class annotated with @Path and containing a method annotated
> > with
> > > @GET
> > > - actuator.war packages actuator.jar in WEB-INF/lib and apart from that
> > is
> > > empty
> > >
> > > The source code is here:
> > > https://github.com/ivannov/javaee-actuator/tree/split
> > >
> > > I deployed this into TomEE 7.0.1 Plume and when I tried to access my
> > > RESTful resource, I got 404. I don't see anything in the catalina log.
> > And
> > > these are the application deployment messages form the console:
> > >
> > > INFO - Enterprise application
> > > "/opt/apache-tomee-plume-7.0.1/webapps/actuator" loaded.
> > > INFO - Assembling app: /opt/apache-tomee-plume-7.0.1/webapps/actuator
> > > INFO - Deployed
> > > Application(path=/opt/apache-tomee-plume-7.0.1/webapps/actuator)
> > > INFO - At least one JAR was scanned for TLDs yet contained no TLDs.
> > Enable
> > > debug logging for this logger for a complete list of JARs that were
> > scanned
> > > but no TLDs were found in them. Skipping unneeded JARs during scanning
> > can
> > > improve startup time and JSP compilation time.
> > > INFO - Deployment of web application archive
> > > /opt/apache-tomee-plume-7.0.1/webapps/actuator.war has finished in
> 1,808
> > ms
> > >
> > > The same works fine in Wildfly 10. It works OK on TomEE as well when
> > > actuator.jar is actually a war and deploy it directly.
> > >
> > > Do I have to do anything special in order to make resources packaged in
> > > WEB-INF/lib discoverable in TomEE?
> > >
> > > Thanks,
> > > Ivan
> > >
> >
>

Re: TomEE 7.0.1 with Windows

[Romain Manni-Bucau]

Hi

what is the install path?
what is the error?


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-07-15 8:26 GMT+02:00 Joerg Jans :

> After configuring the newest TomEE in NetBeans 8.1 I got an error starting
> the server.
> I did some digging and found an StackOverlow article adressing the problem:
>
> http://stackoverflow.com/questions/26485487/error-starting-tomcat-from-netbeans-127-0-0-1-is-not-recognized-as-an-inter
>
> Afterwards I checked the batches and modified them to run under windows
>
> I hope someone could either address this issue with tomcat or modify the
> batches used in TomEE
>
> batches.zip
> <http://tomee-openejb.979440.n4.nabble.com/file/n4679320/batches.zip>
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-7-0-1-with-Windows-tp4679320.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Web service Example+request

[Romain Manni-Bucau]

Hi

tomee+ includes CXF so nothing to add.

To configure a pojo webservice just define the webservice as a servlet in
web.xml to map it like in
https://github.com/apache/tomee/blob/master/examples/pojo-webservice/src/main/webapp/WEB-INF/web.xml


To get the wsld just add ?wsdl to the URL logged at startup


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-07-11 20:47 GMT+02:00 Morris Ang :

> Hi,
>
> I’m currently learning web services. I have a question about
> simple_webservice example. I’ve downloaded Tomee+ so that it includes
> JAX-WS. Why is there a need to use a stateless EJB for web services to work
> in Tomee+? Is it necessary to use EJB as web service for Tomee? I’ve tried
> running it without @Stateless and even tried to create my own simple class
> without it but I keep getting the following:
>
> SEVERE - Error deploying CXF webservice for servlet
> com.service.MyService
> javax.xml.ws.WebServiceException: Service resource injection failed
>
> I’ve tried with Wildfly and all I have to do is annotate my POJO with
> @Webservice.
>
> I’m also confused as to how to generate WSDL or the java source. I’m using
> IntelliJ and I can’t add a CXF engine. I thought Tomee+ already includes
> CXF? Do I need to download CXF separately along with Tomee+ for web service
> support?
>
>

Re: Define common runtimes for web apps

[Romain Manni-Bucau]

the one I pasted for a folder, a file path, mvn coordinates
(mvn:group:artifact:version), http path or any custom registered resolver
on 7.x


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-07-07 13:26 GMT+02:00 lakshman udayakantha :

> Hi Romain,
>
> Thanks for the quick reply. In what format I should mention jar in jars.txt
> file?
>
> Thanks
>
> On Thu, Jul 7, 2016 at 3:53 PM, Romain Manni-Bucau 
> wrote:
>
> > Hi
> >
> > can you add a WEB-INF/jars.txt in the wars needing this behavior? If so
> in
> > this file you can put /opt/tomee/libs/*.jar and all apps will inherit
> from
> > it.
> >
> > Otherwise we have a ClassLoaderEnricher API which is intended for that
> > purpose but it is a bit lower level so can be harder to use (
> > tomee.classloader.configurer.clazz=my.company.ClassLoaderConfigurerImpl).
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> > <http://rmannibucau.wordpress.com> | Github <
> > https://github.com/rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > <http://www.tomitribe.com> | JavaEE Factory
> > <https://javaeefactory-rmannibucau.rhcloud.com>
> >
> > 2016-07-07 12:19 GMT+02:00 lakshman udayakantha :
> >
> > > Hi folks,
> > >
> > > My requirement is to define common runtimes (several class paths) so
> that
> > > several apps can use that by mentioning which class paths are using in
> > web
> > > app level. I suppose to do this  by defining a runtime name with
> > directory
> > > path in an XML. I found by digging TomEE code that TempClassLoader is
> > > responsible for loading classes and holding class loader definition.
> Hope
> > > to override the behaviour of this class to achieve this requirement.
> Am I
> > > in the right path? or any other better way to achieve this?
> > >
> > > Thanks
> > > Lakshman
> > >
> >
>

Re: Define common runtimes for web apps

[Romain Manni-Bucau]

Hi

can you add a WEB-INF/jars.txt in the wars needing this behavior? If so in
this file you can put /opt/tomee/libs/*.jar and all apps will inherit from
it.

Otherwise we have a ClassLoaderEnricher API which is intended for that
purpose but it is a bit lower level so can be harder to use (
tomee.classloader.configurer.clazz=my.company.ClassLoaderConfigurerImpl).


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-07-07 12:19 GMT+02:00 lakshman udayakantha :

> Hi folks,
>
> My requirement is to define common runtimes (several class paths) so that
> several apps can use that by mentioning which class paths are using in web
> app level. I suppose to do this  by defining a runtime name with directory
> path in an XML. I found by digging TomEE code that TempClassLoader is
> responsible for loading classes and holding class loader definition. Hope
> to override the behaviour of this class to achieve this requirement. Am I
> in the right path? or any other better way to achieve this?
>
> Thanks
> Lakshman
>

Re: Remote JNDI look up to ConnectionFactories is failing

[Romain Manni-Bucau]

Ok so then compare the instances you used and the one you get with the
config you set up. There is probably a difference there.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-07-06 15:22 GMT+02:00 Dignesh :

> Yes I am able to send messages successfully by doing "new"
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Remote-JNDI-look-up-to-ConnectionFactories-is-failing-tp4679228p4679242.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Remote JNDI look up to ConnectionFactories is failing

[Romain Manni-Bucau]

you can activate org.apache.activemq debug logs.

Do you manage to send a message doing the "new" yourself like mentionned in
previous message?


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-07-06 14:59 GMT+02:00 Dignesh :

> I have verified url and Listener, both of them are valid.But still I dont
> see
> listener receiving any messages.
> Is there any way possibly via logs etc.. to determine why the messages are
> not sent.
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Remote-JNDI-look-up-to-ConnectionFactories-is-failing-tp4679228p4679239.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Remote JNDI look up to ConnectionFactories is failing

[Romain Manni-Bucau]

Hello

answered inline

2016-07-06 13:30 GMT+02:00 Dignesh :

> Hi Romain,
>
> Just few questions on configuring the resources in client.
>
> System.setProperty("aConnectionFactory",
>
> "connectionfactory:org.apache.activemq.ActiveMQConnectionFactory:tcp://localhost:11616");
>
> So in the above property.What should be the value of the port - Is it
> something the serverURL we specify for resource in tomee.xml file.
>
>
Yes, the network connector url of the broker


> System.setProperty("aQueue",
> "queue:org.apache.activemq.command.ActiveMQQueue:LISTENER");
>
> If I need to configure a topic in the client - Should I add the property in
> the below format ?
>
> System.setProperty("xyz",
> "topic:org.apache.activemq.command.ActiveMQTopic:LISTENER");
>
>
yes


>
> Currently my client program contains below 2 system properties. And I dont
> see any issues with look ups.But Messages I send are not received by the
> listener. So is there any other configuration where I am going wrong.
> System.setProperty("digneshConnection",
>
> "connectionfactory:org.apache.activemq.ActiveMQConnectionFactory:tcp://localhost:61616");
> System.setProperty("xyz",
> "topic:org.apache.activemq.command.ActiveMQTopic:LISTENER");
>
>
>
will just do a new ActiveMQConnectionFactory("tcp://localhost:61616"); and
new ActiveMQTopic("LISTENER");

If these settings (url and topic name) are not valid then you will not hit
your server.


>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Remote-JNDI-look-up-to-ConnectionFactories-is-failing-tp4679228p4679237.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Remote JNDI look up to ConnectionFactories is failing

[Romain Manni-Bucau]

1. that's the way
2. no for the mentionned reasons. The way to solve it would likely be to
write a remote EJB acting as a proxy and getting injected the factory and
queue or equivalent.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-07-05 15:03 GMT+02:00 Dignesh :

> Thank you Romain.
>
> 1.I am using ejbd:// for JNDI look up to ejb's - The ejb's are deployed in
> tomee. I have activated it by adding
> openejb.service.manager.class =
> org.apache.openejb.server.SimpleServiceManager
> in system.properties file -  No issues with this configuration. Please let
> me know I am doing some thing wrong here.
>
> 2.Is there any other alternative apart from configuring connection
> factories
> in client as system property.
> In short i dont want to have below two statements in my client program
>   System.setProperty("aConnectionFactory",
>
> "connectionfactory:org.apache.activemq.ActiveMQConnectionFactory:tcp://localhost:11616");
> System.setProperty("aQueue",
> "queue:org.apache.activemq.command.ActiveMQQueue:LISTENER");
>
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Remote-JNDI-look-up-to-ConnectionFactories-is-failing-tp4679228p4679232.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: TomEE Server not getting started

[Romain Manni-Bucau]

Then that's another jar. if you have bash you can run:

user@machine $  for i in lib/*.jar; do if [ "$(jar tf $i | grep
MANIFEST.MF)" == "" ]; then echo $i; fi done


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-07-05 14:48 GMT+02:00 Dignesh :

> it does contain META-INF/MANIFEST.MF in jar.
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Server-not-getting-started-tp4679116p4679229.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Remote JNDI look up to ConnectionFactories is failing

[Romain Manni-Bucau]

Hello

several things:

- ejbd:// is only used if you set it up in tomee, default is deactivated
- default ejbd transport for tomee is http (http://xxx/tomee/ejb) but
it needs to be activated too, see tomee.remote.support on
http://tomee.apache.org/properties-listing.html
- connection factories client needs to be configured in the client, there
is a sample there
https://github.com/apache/tomee/blob/master/examples/client-resource-lookup-preview/src/test/java/org/superbiz/client/SenderTest.java#L34
(making the why short: otherwise the server would provide either a remote
proxy which would be slow or a shared client config which would likely be
inaccurate)




Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-07-05 14:45 GMT+02:00 Dignesh :

> Hi ,
>
> I am using 7.0.1 version of TomEE. I am doing remote jndi look up to
> connection factory from my local client program.I am not sure is there
> something which I am missing. Can anyone please help me out in finding what
> is the issue here.
> I have attached my client program for reference.
> clientProgram.txt
> <http://tomee-openejb.979440.n4.nabble.com/file/n4679228/clientProgram.txt
> >
>
> Below is stack trace
>
> Jul 05, 2016 6:46:42 PM org.apache.openejb.client.EventLogger log
> INFO: RemoteInitialContextCreated{providerUri=ejbd://localhost:4201}
> Jul 05, 2016 6:46:42 PM org.apache.openejb.client.EventLogger log
> INFO: ConnectionOpened{uri=ejbd://localhost:4201}
> Exception in thread "main" javax.naming.NamingException: Unknown JNDI name
> prefix 'openejb/remote/openejb:'
> at
> org.apache.openejb.core.ivm.naming.IvmContext.lookup(IvmContext.java:130)
> at
>
> org.apache.openejb.server.ejbd.JndiRequestHandler.doLookup(JndiRequestHandler.java:261)
> at
>
> org.apache.openejb.server.ejbd.JndiRequestHandler.processResponse(JndiRequestHandler.java:174)
> at
>
> org.apache.openejb.server.ejbd.EjbDaemon.processJndiResponse(EjbDaemon.java:370)
> at
> org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:275)
> at
> org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:104)
> at
>
> org.apache.openejb.server.ejbd.KeepAliveServer$Session.service(KeepAliveServer.java:277)
> at
>
> org.apache.openejb.server.ejbd.KeepAliveServer$Session.access$1000(KeepAliveServer.java:196)
> at
>
> org.apache.openejb.server.ejbd.KeepAliveServer.service(KeepAliveServer.java:331)
> at
> org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:90)
> at
>
> org.apache.openejb.server.ServerServiceFilter.service(ServerServiceFilter.java:65)
> at
>
> org.apache.openejb.server.ServerServiceFilter.service(ServerServiceFilter.java:65)
> at
> org.apache.openejb.server.ServiceStats.service(ServiceStats.java:54)
> at
>
> org.apache.openejb.server.ServerServiceFilter.service(ServerServiceFilter.java:65)
> at
> org.apache.openejb.server.ServiceLogger.service(ServiceLogger.java:93)
> at
>
> org.apache.openejb.server.ServerServiceFilter.service(ServerServiceFilter.java:65)
> at
> org.apache.openejb.server.ServicePool.access$201(ServicePool.java:39)
> at
> org.apache.openejb.server.ServicePool$3.run(ServicePool.java:208)
> at
>
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
>
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Remote-JNDI-look-up-to-ConnectionFactories-is-failing-tp4679228.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: TomEE Server not getting started

[Romain Manni-Bucau]

so ojdbc jar doesn't have a META-INF/MANIFEST.MF which can likely be the
case. try adding ojdbc in conf/exclusions.list (don't forget to add
"default-list" in the file as well if it doesn't exist)


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-07-05 14:37 GMT+02:00 Dignesh :

> Hi Romain ,
>
> Moving to latest version 7.0.1 of TomEE plus has resolved the issue.
> But one thing I noticed is, the issue is observed when I use Oracle as
> Database.The issue is not seen when I use sqlserver and PostGres as
> database.
>
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Server-not-getting-started-tp4679116p4679226.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Minimal components in TomEE Embedded Server

[Romain Manni-Bucau]

2016-07-05 14:13 GMT+02:00 Sathwik :

> Hi Romain,
>
> Thanks for the quick reply,
>
> We use Ruby & Rake for the builds, moved out of maven a very long time
> ago. We have a docker image and use it to build on Jenkins. It works for
> local builds as well.
>
> So, we will need to enhance the current ruby based build script to have an
> embedded ODE server, which I will do.
>
> I had encountered some issues with OpenJPA 2.4 when integrating ODE with
> TomEE and hence I had to downgrade . Will see if I have noted the problems.
>
> Thanks for the pointers and I have just started to look into the TomEE
> code.
>
> I will raise a JIRA issue explaining the goal of embedded ODE server and
> share it here.
>
> ODE is available on Git repo. What do you suggest for the working branch
> to help us?
>
>
Anything public, even a github repo is fine, just needs to be on a trusted
server (asf or github for instance). If ODE has PR integration it can also
be an option.


> regards,
> sathwik
>
> On 2016-07-05 15:47 (+0530), Romain Manni-Bucau 
> wrote:
> > Hello
> >
> > few questions before answering more specifically: can you use mvn to
> build
> > this server - I know ODE has a pom but not sure if it is to make jenkins
> > happy or if it is really used. If so tomee-maven-plugin allows to do what
> > you do in your script more or less in a "standard" fashion, only trick
> > would be to have an axis and a EE war but this is very doable with
> > mvn-war-plugin.
> >
> >
> > Now more specifically about your use case:
> > 1. the downgrade of JPA is normally useless (JPA 2 supports JPA 1)
> > 2. Configuration of tomee embedded or standalone is the same (either
> > tomee.xml or - recommanded for embedded - through system
> > properties/system.properties)
> >
> >
> > About how to bootstrap/configure tomee-embedded here is the doc:
> > http://tomee.apache.org/ng/advanced/tomee-embedded/, let me know if
> > anything is unclear.
> >
> > If you want to do a fatjar of ode you can get started with this page as
> > well http://tomee.apache.org/ng/advanced/shading/index.html
> >
> > If you push a working branch somewhere I'm happy to help if I have enough
> > guidance on the goal.
> >
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> > <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > <http://www.tomitribe.com> | JavaEE Factory
> > <https://javaeefactory-rmannibucau.rhcloud.com>
> >
> > 2016-07-05 10:09 GMT+02:00 Sathwik :
> >
> > > Hi Devs,
> > >
> > > I am from the Apache ODE team. We are in the process of distributing
> > > production ready ODE as a standalone server, henceforth looking towards
> > > TomEE Embedded server. ODE has been in distribution till now as a web
> > > application.
> > >
> > > We have tried deploying ODE on a full blown Tomee Webprofile server
> 1.7.2
> > >
> > >
> https://github.com/sathwik/apache-ode-tomcat-bundle/blob/master/buildfile-tomee
> > > We had to downgrade TomEE from JPA2 to JPA1 as ODE is still on JPA 1.0.
> > >
> > > We are looking for a minimal configuration of TomEE Embedded Server
> > > preferably (Tomcat + JTA + JMS (optional)) to start with. Can you guys
> help
> > > us out.
> > >
> > > regards,
> > > sathwik
> > > ODE-PMC
> > >
> > >
> >
>

Re: Minimal components in TomEE Embedded Server

[Romain Manni-Bucau]

Hello

few questions before answering more specifically: can you use mvn to build
this server - I know ODE has a pom but not sure if it is to make jenkins
happy or if it is really used. If so tomee-maven-plugin allows to do what
you do in your script more or less in a "standard" fashion, only trick
would be to have an axis and a EE war but this is very doable with
mvn-war-plugin.


Now more specifically about your use case:
1. the downgrade of JPA is normally useless (JPA 2 supports JPA 1)
2. Configuration of tomee embedded or standalone is the same (either
tomee.xml or - recommanded for embedded - through system
properties/system.properties)


About how to bootstrap/configure tomee-embedded here is the doc:
http://tomee.apache.org/ng/advanced/tomee-embedded/, let me know if
anything is unclear.

If you want to do a fatjar of ode you can get started with this page as
well http://tomee.apache.org/ng/advanced/shading/index.html

If you push a working branch somewhere I'm happy to help if I have enough
guidance on the goal.



Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-07-05 10:09 GMT+02:00 Sathwik :

> Hi Devs,
>
> I am from the Apache ODE team. We are in the process of distributing
> production ready ODE as a standalone server, henceforth looking towards
> TomEE Embedded server. ODE has been in distribution till now as a web
> application.
>
> We have tried deploying ODE on a full blown Tomee Webprofile server 1.7.2
>
> https://github.com/sathwik/apache-ode-tomcat-bundle/blob/master/buildfile-tomee
> We had to downgrade TomEE from JPA2 to JPA1 as ODE is still on JPA 1.0.
>
> We are looking for a minimal configuration of TomEE Embedded Server
> preferably (Tomcat + JTA + JMS (optional)) to start with. Can you guys help
> us out.
>
> regards,
> sathwik
> ODE-PMC
>
>

Re: TomEE Server not getting started

[Romain Manni-Bucau]

your jars and container classpath if you changed it? This is the error for
sure.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-06-29 16:47 GMT+02:00 Dignesh :

> Hi ,
>
> I have double checked it again.I dont find any jars which doesnot contain
> metainf/manifest file.
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Server-not-getting-started-tp4679116p4679122.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: TomEE Server not getting started

[Romain Manni-Bucau]

2016-06-29 16:08 GMT+02:00 Dignesh :

> Hi,
>  I haven't understood the answer.
>
> 1.Does it mean every jar should have META-INF/MANIFEST.MF ?
>

yes was a (now fixed) bug in tomcat


> 2.How to exclude the jar from the scanning - Any configuration available ?
>

easiest is to add the jar prefix (for foo-1.2.3.jar add "foo-") in
conf/exclusions.list

file should look like:

default-list
foo-
bar-
#...


> 3.What will be the impact if I exclude the jar from scanning?
>
>
If it contains EE components (EJB, CDI beans, @WebXXX...) it will be
ignored. The container will be able to load the classes when needed but
will ignore them at processing time.

If it is your jar just fix your build tool to generate this file (mvn,
gradle, ant should do it by default), if not your jar and just a utility
jar exclude it.

Last note: as mentionned upgrading is an alternative now since 7.0.1 is
released


>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Server-not-getting-started-tp4679116p4679119.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: TomEE Server not getting started

[Romain Manni-Bucau]

PS: should be fixed on tomee 7.0.1


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-06-29 16:31 GMT+02:00 Romain Manni-Bucau :

> Hi
>
> think it has been treated multiple times on the list but it means a jar
> misses a META-INF/MANIFEST.MF
>
> Just exclude this jar from the scanning and this exception will disappear.
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> <http://rmannibucau.wordpress.com> | Github
> <https://github.com/rmannibucau> | LinkedIn
> <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> <http://www.tomitribe.com> | JavaEE Factory
> <https://javaeefactory-rmannibucau.rhcloud.com>
>
> 2016-06-29 15:36 GMT+02:00 Dignesh :
>
>> Hi,
>> I am seeing the below the exception during the server start up.And server
>> is
>> terminated automatically.
>> I dont see any other exception other than below stack trace. Can any one
>> please help me in understanding what is causing the issue.
>>
>> 29-Jun-2016 19:36:00.103 SEVERE [Catalina-startStop-1]
>> sun.reflect.NativeMethodAccessorImpl.invoke A child container failed
>> during
>> start
>>  java.util.concurrent.ExecutionException:
>> org.apache.catalina.LifecycleException: Failed to start component
>>
>> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/content]]
>> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
>> at java.util.concurrent.FutureTask.get(FutureTask.java:188)
>> at
>>
>> org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:913)
>> at
>> org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:890)
>> at
>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:152)
>> at
>>
>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1405)
>> at
>>
>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1395)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>> at
>>
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> at
>>
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> at java.lang.Thread.run(Thread.java:744)
>> Caused by: org.apache.catalina.LifecycleException: Failed to start
>> component
>>
>> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/content]]
>> at
>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:158)
>> ... 6 more
>> Caused by: java.lang.NullPointerException
>> at
>>
>> org.apache.tomcat.util.scan.StandardJarScanner.processManifest(StandardJarScanner.java:373)
>> at
>>
>> org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner.java:328)
>> at
>>
>> org.apache.tomcat.util.scan.StandardJarScanner.scan(StandardJarScanner.java:277)
>> at
>> org.apache.tomee.loader.TomEEJarScanner.scan(TomEEJarScanner.java:59)
>> at
>>
>> org.apache.catalina.startup.ContextConfig.processJarsForWebFragments(ContextConfig.java:1887)
>> at
>>
>> org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1122)
>> at
>>
>> org.apache.catalina.startup.OpenEJBContextConfig.webConfig(OpenEJBContextConfig.java:402)
>> at
>>
>> org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:771)
>> at
>>
>> org.apache.catalina.startup.OpenEJBContextConfig.configureStart(OpenEJBContextConfig.java:123)
>> at
>>
>> org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:298)
>> at
>>
>> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94)
>> at
>>
>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5093)
>> at
>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:152)
>> ... 6 more
>>
>>
>>
>> --
>> View this message in context:
>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Server-not-getting-started-tp4679116.html
>> Sent from the TomEE Dev mailing list archive at Nabble.com.
>>
>
>

Re: TomEE Server not getting started

[Romain Manni-Bucau]

Hi

think it has been treated multiple times on the list but it means a jar
misses a META-INF/MANIFEST.MF

Just exclude this jar from the scanning and this exception will disappear.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-06-29 15:36 GMT+02:00 Dignesh :

> Hi,
> I am seeing the below the exception during the server start up.And server
> is
> terminated automatically.
> I dont see any other exception other than below stack trace. Can any one
> please help me in understanding what is causing the issue.
>
> 29-Jun-2016 19:36:00.103 SEVERE [Catalina-startStop-1]
> sun.reflect.NativeMethodAccessorImpl.invoke A child container failed during
> start
>  java.util.concurrent.ExecutionException:
> org.apache.catalina.LifecycleException: Failed to start component
>
> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/content]]
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:188)
> at
>
> org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:913)
> at
> org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:890)
> at
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:152)
> at
>
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1405)
> at
>
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1395)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
>
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
> Caused by: org.apache.catalina.LifecycleException: Failed to start
> component
>
> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/content]]
> at
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:158)
> ... 6 more
> Caused by: java.lang.NullPointerException
> at
>
> org.apache.tomcat.util.scan.StandardJarScanner.processManifest(StandardJarScanner.java:373)
> at
>
> org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner.java:328)
> at
>
> org.apache.tomcat.util.scan.StandardJarScanner.scan(StandardJarScanner.java:277)
> at
> org.apache.tomee.loader.TomEEJarScanner.scan(TomEEJarScanner.java:59)
> at
>
> org.apache.catalina.startup.ContextConfig.processJarsForWebFragments(ContextConfig.java:1887)
> at
>
> org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1122)
> at
>
> org.apache.catalina.startup.OpenEJBContextConfig.webConfig(OpenEJBContextConfig.java:402)
> at
>
> org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:771)
> at
>
> org.apache.catalina.startup.OpenEJBContextConfig.configureStart(OpenEJBContextConfig.java:123)
> at
>
> org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:298)
> at
>
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94)
> at
>
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5093)
> at
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:152)
> ... 6 more
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Server-not-getting-started-tp4679116.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: New contributor

[Romain Manni-Bucau]

Awesome news Diego!

Welcome onboard ;).

Let us know if you need any help to get started or anything


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-06-28 21:01 GMT+02:00 Diego Urenia :

> Hello everybody!
>
> My name is Diego and I've just joined the mailing list to, hopefully, be
> able to contribute with the project.
>
> For a long time I thought about contributing to an opensource project, but
> I was always a silent member in the mailing list and never brave enough to
> do it (yes, the "be brave" section really inspired me). Well, that's going
> to change now.
>
> Best regards,
> Diego Urenia
>

[ANNOUNCE] Apache TomEE 7.0.1

[Romain Manni-Bucau]

The Apache Team Team is pleased to announce the availability of Apache TomEE
 7.0.1

When downloading, please verify signatures using the KEYS file available at:
http://www.apache.org/dist/tomee

Maven artifacts are already available in the central Maven repository.


The Apache TomEE Team

Re: ApplicationComposer and overriding default jndi naming strategy

[Romain Manni-Bucau]

Hi

if you set my-ear as name to the Application or ApplicationModule and
my-ejb to the EjbJar or EjbModule then you will end up with this naming.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-06-27 12:04 GMT+02:00 Gregory Orciuch :

> Hi,
>
> in my app some of it's legacy parts are using static InitialContext.lookup
> on hardcoded jboss's pattern jndi paths, like:
>
> java:global/my-ear/my-ejb/FooService .
>
> How can I achieve the same with OpenEJB and ApplicationComposer, while it's
> quite different naming strategy : "java:comp/env/
>
>
> Actually having trouble to locate a good way passing the property
> of openejb.jndiname.format
> to tests run by:
> @RunWith(ApplicationComposer.class)
>
> Any idea ?
>
> BR,
> Gregory
>

[RESULT][VOTE] Apache TomEE 7.0.1

[Romain Manni-Bucau]

And with my +1 this vote pass with 3 +1 bindings (Mark, JL and me) and 4 +1
(Gregory, Daniel, Felipe, Jeff)

I'll continue with the release steps

thanks too all people having answered!


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-06-27 11:22 GMT+02:00 Jean-Louis Monteiro :

> Sorry, meant +1 of course
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
> On Mon, Jun 27, 2016 at 11:22 AM, Jean-Louis Monteiro <
> jlmonte...@tomitribe.com> wrote:
>
> > Thanks Romain.
> > Looks good.
> >
> > Jean-Louis
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> > On Sun, Jun 26, 2016 at 8:46 PM, Mark Struberg  >
> > wrote:
> >
> >> Tested with my app, License file checked, RAT passed, signature ok.
> >>
> >> +1
> >>
> >> txs and LieGrue,
> >> strub
> >>
> >>
> >> > Am 23.06.2016 um 08:44 schrieb Romain Manni-Bucau <
> >> rmannibu...@gmail.com>:
> >> >
> >> > Hi
> >> >
> >> > As mentionned on the dev@ list here is the 7.0.1 vote.
> >> >
> >> > There is not much but mainly tomcat upgrade to 8.5.3 in there.
> >> >
> >> > Release notes:
> >> >
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320&version=12335762
> >> > Keys file: https://www.apache.org/dist/tomee/KEYS
> >> > Tag on github: https://github.com/rmannibucau/tomee/tree/tomee-7.0.1
> >> > Staging repository:
> >> >
> https://repository.apache.org/content/repositories/orgapachetomee-1099
> >> > Dev dist: https://dist.apache.org/repos/dist/dev/tomee/7.0.1/
> >> >
> >> > Vote will be open for 72h or until we get 3 +1 bindings. Binding or
> not
> >> > everyone is very welcomed to test and vote.
> >> >
> >> >
> >> > Please vote:
> >> > [ ] +1 of course!
> >> > [ ] +0 just to say hi
> >> > [ ] -1 no cause ${blocker}
> >> >
> >> > Romain Manni-Bucau
> >> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> >> > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> >> > <http://rmannibucau.wordpress.com> | Github <
> >> https://github.com/rmannibucau> |
> >> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> >> > <http://www.tomitribe.com> | JavaEE Factory
> >> > <https://javaeefactory-rmannibucau.rhcloud.com>
> >>
> >>
> >
>

Re: Classloading issues integrating Jersey 2.16 and apache-tomee-plus-7.0.0

[Romain Manni-Bucau]

FYI https://issues.apache.org/jira/browse/TOMEE-1851


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-06-24 7:57 GMT+02:00 rvinjamu :

> I am done with making Jersey work with Tomee with my application REST
> resources bundled in my REST Webapp/web-inf/lib instead of in EAR/lib. But
> I
> have another problem to solve now - that of classes being loaded from
> EAR/lib first. I tried to leverage the tomee.webapp-first=true attribute.
> But still I see that classes from EAR/lib are loaded first. Attached is a
> EAR that demonstrates this behavior. This ear has a library placed in the
> EAR/lib as well as in WEB-INF/lib of the constituent web module. The web
> page in the web module invokes a method of this library class and prints
> the
> return value on the page. The method just returns the classloader name that
> loaded the class. To check, deploy the ear in Tomee and then access the
> following URL:
>
> http://localhost:8080/TomeeClassLoaderIssue-war/index.jsp
>
> For me it just prints "I have been loaded by class
> org.apache.openejb.util.classloader.URLClassLoaderFirst"
>
> However when I remove the library from EAR/lib, it loads from WEB-INF/lib.
>
> I have checked with the option tomee.webapp-first=true in system.properties
> - but without any change in behavior. The sample EAR has been attached
> here.
>
> TomeeClassLoaderIssue.ear
> <
> http://tomee-openejb.979440.n4.nabble.com/file/n4679042/TomeeClassLoaderIssue.ear
> >
>
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Classloading-issues-integrating-Jersey-2-16-and-apache-tomee-plus-7-0-0-tp4678794p4679042.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

[VOTE] Apache TomEE 7.0.1

[Romain Manni-Bucau]

Hi

As mentionned on the dev@ list here is the 7.0.1 vote.

There is not much but mainly tomcat upgrade to 8.5.3 in there.

Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320&version=12335762
Keys file: https://www.apache.org/dist/tomee/KEYS
Tag on github: https://github.com/rmannibucau/tomee/tree/tomee-7.0.1
Staging repository:
https://repository.apache.org/content/repositories/orgapachetomee-1099
Dev dist: https://dist.apache.org/repos/dist/dev/tomee/7.0.1/

Vote will be open for 72h or until we get 3 +1 bindings. Binding or not
everyone is very welcomed to test and vote.


Please vote:
[ ] +1 of course!
[ ] +0 just to say hi
[ ] -1 no cause ${blocker}

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

7.0.1?

[Romain Manni-Bucau]

Hi guys,

know plans for 7.0.1 were to get OWB and johnzon but due to the
[fileupload] CVE tomcat reported I'd like to get it out if possible with
current state and do the upgrade later.

Any objection please shout.

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

Re: Classloading issues integrating Jersey 2.16 and apache-tomee-plus-7.0.0

[Romain Manni-Bucau]

2016-06-22 5:28 GMT+02:00 rvinjamu :

> I am not able to get things working with Jersey unless I place all my
> Jersey
> Libraries in EAR/lib - and to my discomfiture even the REST resources jar
> of
> my WebApp to EAR/lib.  For now I have decided to adopt an alternate
> approach
> - I have created an extension of LazyStopLoader and as a Classloader
> delegate using a custom extension of TomEEWebappClassLoader that just
> overrides the getResources method the way Jersey expects it (In-fact I too
> feel that way - the resource URI as returned by the classloader should not
> have a trailing '/' - the / does not make it a precise URI - though Jersey
> could have handled it as a robust measure). I now set this custom loader in
> context.xml of Tomcat ( right now I am setting it at server level - but I
> would move it to the Webapp level). This works fine for me. Jersey is now
> able to identify all resources - The REST app works fine without me having
> to bundle Jersey libraries or the REST resources jar in EAR/lib.
>
> Two points in my opinion favor making the modification in
> TomEEWebappClassLoader.
>
> 1. The TomEE TempClassLoader which loads the classes in EAR/lib behaves
> just
> fine - returns the resource URIs without any trailing '/'. Then why not
> TomEEWebappClassLoader
> 2. A resource URI should be precise. In my opinion, the trailing '/' does
> not make it precise.
>
>
Well this is actually a standard handling on windows by the JVM

We can surely have a flag to activate your workaround if too specific - if
you want to share it - but there is a simpler altenative: don't use
scanning from jersey there (either providing classes in
Application#getClasses() or generating this class at build time) and it
should work fine.


>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Classloading-issues-integrating-Jersey-2-16-and-apache-tomee-plus-7-0-0-tp4678794p4678993.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Issue with Messaging destination (topic) deployments.

[Romain Manni-Bucau]

2016-06-20 15:47 GMT+02:00 Dignesh :

>
> So does it mean TomEE will create a destination with default convention for
> each of those destinations defined in activemq.xml file.
>
>
No, it means that tomee needs a destination by default injection (@Resource
Topic topic;) MDB

Names can be set in activation config properties for the MDB or name method
of @Resource for injections. If not set it is deduced from the MDB name or
injection name - should be logged anyway in the deployment output.


> And if Yes, what will be the id for the destination created.
> And if No, Is it mandatory to define the destinations in TomEE.xml file
> instead of ActiveMq.xml
>
>
It is if you rely on implicit resources - I think you do - and it is not if
you fully wire the names everywhere.


>
>
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Issue-with-Messaging-destination-topic-deployments-tp4678975p4678979.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Issue with Messaging destination (topic) deployments.

[Romain Manni-Bucau]

2016-06-20 15:16 GMT+02:00 Dignesh :

> Hello Romain . Thank you very much for quick reply
>
> I am not clear of your answer
>
> 1.What does it mean tomee is not aware of these destination maybe it
> doesn't
> use it and rely on
> default names ? - what are default names ?
>
>
the amq.xml usage will set the destination on the broker but tomee doesn't
know it exists - compared to one defined in tomee.xml which is known bu
tomee runtime.

So when tomee needs to resolve a topic it will not use the ones of the
broker but the ones of tomee.xml. If noone is defined there it will create
one with a default convention.


>
> 2. I am not clear of this question - Would it make sense for your app?
>
>
>

Wonder if your issue can be tomee creates a topic with another name in your
case.


>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Issue-with-Messaging-destination-topic-deployments-tp4678975p4678977.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Issue with Messaging destination (topic) deployments.

[Romain Manni-Bucau]

Hi

Think it is deployed (you can check it putting a breakpoint
in org.apache.activemq.broker.BrokerService#startDestinations) but since
tomee is not aware of these destination maybe it doesn't use it and rely on
default names. Would it make sense for your app?


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-06-20 14:59 GMT+02:00 Dignesh :

> Hello,
>
> I am facing a weird issue.
>
> I have defined the destinations in the activemq.xml and I have linked that
> to the BrokerxmlConfig in tomee.xml.
>
> The consumer for that topic is webapp listener.
>
> The issue what I am seeing is the destination(topic) which is defined in
> activemq.xml is not getting deployed. - Is there any other configuration
> which I am missing here ?
>
> So when I add the below is data in tomee.xml file, it is getting deployed.
>
> 
>
> Please help me on this to point where I am going wrong.
>
> activemq.xml
> <http://tomee-openejb.979440.n4.nabble.com/file/n4678975/activemq.xml>
> tomee.xml
> <http://tomee-openejb.979440.n4.nabble.com/file/n4678975/tomee.xml>  I
> have
> attached tomee.xml and activemq.xml file for reference.
>
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Issue-with-Messaging-destination-topic-deployments-tp4678975.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Classloading issues integrating Jersey 2.16 and apache-tomee-plus-7.0.0

[Romain Manni-Bucau]

openejb.validation.skip=true

will remove the first call IIRC


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-06-20 10:17 GMT+02:00 rvinjamu :

>
> Stack Trace 1: Registration of resources by Open EJB Container
>
> at
>
> org.glassfish.jersey.server.internal.scanning.PackageNamesScanner.addResourceFinder(PackageNamesScanner.java:278)
> at
>
> org.glassfish.jersey.server.internal.scanning.PackageNamesScanner.init(PackageNamesScanner.java:196)
> at
>
> org.glassfish.jersey.server.internal.scanning.PackageNamesScanner.(PackageNamesScanner.java:153)
> at
>
> org.glassfish.jersey.server.internal.scanning.PackageNamesScanner.(PackageNamesScanner.java:110)
> at
>
> org.glassfish.jersey.server.ResourceConfig.packages(ResourceConfig.java:669)
> at
>
> org.glassfish.jersey.server.ResourceConfig.packages(ResourceConfig.java:652)
> at
>
> com.opentext.mediamanager.restapi.core.OTMMRestAPIApplication.(OTMMRestAPIApplication.java:23)
> at
>
> sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java)
> at
>
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
>
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at java.lang.Class.newInstance(Class.java:374)
> at
>
> org.apache.openejb.config.rules.CheckRestMethodArePublic.validate(CheckRestMethodArePublic.java:73)
> at
> org.apache.openejb.config.AppValidator.validate(AppValidator.java:102)
> at
> org.apache.openejb.config.ValidateModules.deploy(ValidateModules.java:38)
> at
>
> org.apache.openejb.config.ConfigurationFactory$Chain.deploy(ConfigurationFactory.java:417)
> at
>
> org.apache.openejb.config.ConfigurationFactory.configureApplication(ConfigurationFactory.java:1023)
> at
>
> org.apache.openejb.config.ConfigurationFactory.configureApplication(ConfigurationFactory.java:842)
> at
>
> org.apache.openejb.config.ConfigurationFactory.getOpenEjbConfiguration(ConfigurationFactory.java:540)
> at
>
> org.apache.openejb.config.ConfigurationFactory.getOpenEjbConfiguration(ConfigurationFactory.java:627)
> at
>
> org.apache.openejb.assembler.classic.Assembler.getOpenEjbConfiguration(Assembler.java:500)
> at
> org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:479)
> at org.apache.openejb.OpenEJB$Instance.(OpenEJB.java:150)
> at org.apache.openejb.OpenEJB.init(OpenEJB.java:307)
> at
> org.apache.tomee.catalina.TomcatLoader.initialize(TomcatLoader.java:266)
> at
>
> org.apache.tomee.catalina.ServerListener.lifecycleEvent(ServerListener.java:168)
> at
>
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94)
> at
>
> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:401)
> at
> org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:115)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:606)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:629)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java)
> at
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:311)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:494)
>
>
> Stack Trace 1: Registration of resources from Jersey Servlet
>
> "localhost-startStop-1"
> at
>
> org.glassfish.jersey.server.internal.scanning.PackageNamesScanner.addResourceFinder(PackageNamesScanner.java:280)
> at
>
> org.glassfish.jersey.server.internal.scanning.PackageNamesScanner.init(PackageNamesScanner.java:196)
> at
>
> org.glassfish.jersey.server.internal.scanning.PackageNamesScanner.(PackageNames

Re: Classloading issues integrating Jersey 2.16 and apache-tomee-plus-7.0.0

[Romain Manni-Bucau]

Well scanning has a lighter classloader and TomEEWebappClassLoader has some
workaround for ears scanning dont use which can explain why you have this
behavior. About the trainling slash I guess jersey should fix it - we
should just reuse tomcat one there.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-06-20 10:05 GMT+02:00 rvinjamu :

> While i work on creating a sample application that shows the PARENT FIRST
> class-loading of TomEE Plus, I was able to figure out some extent as to why
> Jersey does not work with TomEE when packaged in
> EAR/WAR-MODULE/WEB-INF/lib.
> I removed all the Jar conflicts and ensured that Jersey libraries are only
> available from EAR-module/war-module/web-inf/lib.  My observations are as
> here under:
>
> I notice that my REST Application and resources are examined twice. Once by
> OpenEJB container and once by the Jersey Container Servlet. So the first
> time when resource uris are figured out, the classloader used is
> org.apache.openejb.core.TempClassLoader and (strangely !) it is able to
> locate resources from
> WEB-INF/lib of my REST Web module. The getResources(String name) method
> fired on this classloader returns Jar URLs - each Jar URL having URI like
> this:
>
> file:/C:/installations/otmm-tomee/apache-tomee-plus-7.0.0/apps/myear/restapi/WEB-INF/lib/myrestresources.jar!/com/xyz/pqr/restapi.
> I see that all my REST resources are properly identified. One point to
> notice is that the URI has no trailing slash.
>
> However, the REST application is invoked second time from Jersey Servlet.
> While figuring out resources, the classloader used is an instance of
> "org.apache.tomee.catalina.TomEEWebappClassLoader"
> and it returns each URI with a trailing slash as follows.
>
>
> "jar:file:/C:/installations/otmm-tomee/apache-tomee-plus-7.0.0/apps/artesia/restapi/WEB-INF/lib/otmm-rest-representations.jar!/com/opentext/mediamanager/restapi/"
> - Notice the trailing slash. This was not there when TempClassLoader is
> used. Jersey does some substring stuff and the trailing slash upsets
> Jersey's processing and it fails to identify the REST resources. Not sure
> whether there is anything there in java.lang.ClassLoader contract that
> getResource(String name) can/should n't list resource URIs with trailing
> slash. Therefore cannot say whether the getResource implementation of
> TomEEWebappClassLoader is right or wrong. But this is the reason as to why
> Jersey fails to identify REST resources.
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Classloading-issues-integrating-Jersey-2-16-and-apache-tomee-plus-7-0-0-tp4678794p4678970.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Classloading issues integrating Jersey 2.16 and apache-tomee-plus-7.0.0

[Romain Manni-Bucau]

Hi

it can be for ears.

Do you care sharing a maven project reproducing it? Would like to ensure I
test against the same packaging - just remove the business logic to keep a
single hello world endpoint please.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-06-20 5:50 GMT+02:00 rvinjamu :

> Looks like this is a class loading issue. I have a library with some Jersey
> classes in EAR/lib and this is being picked up first and the classes in
> this
> are naturally not able to pick up classes in the other jar packaged in
> EAR/WARmodule/web-inf/lib. Looks like TomEE is following a PARENT-FIRST
> approach to class loading. I see some other posts on the same issue. What
> is
> the solution to force TomEE follow the regular J2EE model - of loading the
> WEB-INF/lib jars first?
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Classloading-issues-integrating-Jersey-2-16-and-apache-tomee-plus-7-0-0-tp4678794p4678962.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: JNDI look up fails in user spwaned thread.

[Romain Manni-Bucau]

same excepted there the spec forbids explicitly it (tomee tolerates it to
keep common code working but some server just fail when doing that).


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-06-13 14:21 GMT+02:00 Dignesh :

> So how about the forking a new thread in message driven bean.I am seeing
> the
> same issue there as well ?
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/JNDI-look-up-fails-in-user-spwaned-thread-tp4678861p4678867.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: JNDI look up fails in user spwaned thread.

[Romain Manni-Bucau]

Hi

it is expected or more explicitly unspecified. EJB as web env (servlet)
have their own jndi tree (you can configure some parts in ejb-jar.xml or
web.xml) so if you are not in this context then it is up to you to make it
work or not.

Easy workaround is to wrap the lookup in a known context
(ejb.doInContext(() -> return lookup()); for instance)


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-06-13 10:10 GMT+02:00 Dignesh :

> Hi,
>
> JNDI look up to EJB's fail if the look up is done from user spawned thread.
>
> I am forking a new thread in my servlet and doing a JNDI look up to EJB,
> and
> it is failing. Is it is a bug or it is expected behaviour.
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/JNDI-look-up-fails-in-user-spwaned-thread-tp4678861.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Need help on setting up log4j.xml

[Romain Manni-Bucau]

it just loads it as a log4j.properties file so using log4j properties
syntax it works.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-06-06 15:46 GMT+02:00 Dignesh :

> so you mean I can use the logging.properties for log4j configuration. -I
> assume that we need to add log4j.xml content in to logging.properties to
> achieve this ?
>
> Or
>
> Can you please provide me example of logging.properties which uses
> log4j.xml.
>
>
>
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Need-help-on-setting-up-log4j-xml-tp4678735p4678778.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Dynamic Resources

[Romain Manni-Bucau]

Hi

this error means you didn't set up the provider, ie this file:
https://github.com/apache/tomee/blob/042d4d9fc647c32ee31c4c7455a4769817564340/examples/dynamic-datasource-routing/src/main/resources/META-INF/org.router/service-jar.xml

Note that it is no more required and can be replaced in resources.xml by:


 # config


Also note that for a war descriptors (resources.xml there) should be in
WEB-INF and not META-INF - guess it is your issue.




Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com/> | Old Blog
<http://rmannibucau.wordpress.com/> | Github
<https://github.com/rmannibucau> | LinkedIn
<https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-06-06 13:21 GMT+02:00 Rafael Reynoud :

>
> Good afternoom
>  we are using the server tomee, we need create several Resouce, but we did
> not get make work.
>
> we use example
> https://github.com/apache/tomee/tree/042d4d9fc647c32ee31c4c7455a4769817564340/examples/dynamic-datasource-routing,
> In this example I can do the test successfully , but we try the same
> project on our server (tomee, files .ear or .war), we have difficulties,
> example message:  org.apache.openejb.OpenEJBException: Can't find resource
> for class org.superbiz.dynamicdatasourcerouting.RoutedPersister#router. (No
> provider available for resource-ref id with type
> 'org.superbiz.dynamicdatasourcerouting.DeterminedRouter' for
> 'BoostrapUtility'.).
>
> We look at various examples and tutorials including some developed by
> tomitribe employees, but in no case could the success.
>
> we are using java 8 and apache-tomee-webprofile-1.7.4.
>
> Attached, we send the same example that we downloaded from github and
> tomee.xml
>
> we look forward for a positive response, thank you!
>
> and congratulations for the work yours.!
>
>

Re: Need help on setting up log4j.xml

[Romain Manni-Bucau]

2016-06-06 10:35 GMT+02:00 Dignesh :

> Thank you very much..It is working now.
>
> Is there any way we can eliminate adding the log4j.jar and log4j.xml in
> tomee lib directory and generate logging.Because the way now it is working
> is, we need them to be added in tomee lib directory.
> Is there any other way we can do by modifying the logging.properties file
> present in conf folder.
>
>
Should be the default (ie external property set to false)


> The reason why I need this is we dont want any log4j.jar,log4j.xml files
> that needs to be added in TomEE lib directory.
>
>
Strictly speaking it needs to be in the classloader of the logger. If you
want tomee to use log4j you need to put it in tomee classloader ie
common.loader of tomcat (you can create other folders if you prefer). If
that's just for the app but not tomee then putting them all in the webapp
works.


> Please advise further.
>
>
> Thanks
>
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Need-help-on-setting-up-log4j-xml-tp4678735p4678768.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Need help on setting up log4j.xml

[Romain Manni-Bucau]

1. system.properties:

openejb.log.factory = log4j
openejb.logger.external = true
log4j.debug=true

2.lib/log4j.xml:




http://jakarta.apache.org/log4j/"; >










































conf/jars.txt (was too lazy to download log4j.jar):

mvn:log4j:log4j:1.2.17


Then I get openejb logs on log4j (openejb appender). I don't get apps logs
but not sure you expect it




Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-06-03 19:13 GMT+02:00 Dignesh :

> artesia.ear
> <http://tomee-openejb.979440.n4.nabble.com/file/n4678751/artesia.ear>
> system.properties
> <http://tomee-openejb.979440.n4.nabble.com/file/n4678751/system.properties
> >
> log4j.xml
> <http://tomee-openejb.979440.n4.nabble.com/file/n4678751/log4j.xml>
> tomee.xml
> <http://tomee-openejb.979440.n4.nabble.com/file/n4678751/tomee.xml>
>
> Attached ear ,conf/system.properties,conf/log4j.xml,tomee.xml
> Version of tomee plus  1.7 M3
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Need-help-on-setting-up-log4j-xml-tp4678735p4678751.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Need help on setting up log4j.xml

[Romain Manni-Bucau]

Maybe try to take the time to setup your installation with
tomee-maven-plugin to reproduce it and share us something we can inspect
(src/main/tomee/conf for conf folder, src/main/tomee/libfor lib folder and
log4j:log4j:1.2.17 to add log4j to libs. Finally
mvn tomee:run to start)


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-06-03 19:02 GMT+02:00 Dignesh :

> Still the same issue
>
> Attached system.properties file system.properties
> <http://tomee-openejb.979440.n4.nabble.com/file/n4678749/system.properties
> >
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Need-help-on-setting-up-log4j-xml-tp4678735p4678749.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Need help on setting up log4j.xml

[Romain Manni-Bucau]

Add in conf/system.properties:

openejb.logger.external=true

Otherwise we historically read some particular files not very intuitively.
Le 3 juin 2016 19:30, "Dignesh"  a écrit :

> Hi,
>
> Below are my configurations
>
> 1.added log4j.xml in conf folder
> 2.Added openejb.log.factory = log4j property in system.property file
> 3.Added commons-logging and log4j.jars in lib directory
>
> I am seeing the below warn messages in log. Is there any other
> configuration
> which i am missing .If not how can i turn on the log4j.debug to drill down
> the issue further.
>
>
> log4j:WARN No appenders could be found for logger
> (dignesh.tomee.learning.TestCl
> ass1).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
> more in
> fo.
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Need-help-on-setting-up-log4j-xml-tp4678735p4678747.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>