Re: RMI From TomEE to Jboss

[Howard W. Smith, Jr.]

On Tue, Jul 10, 2018 at 7:23 PM, Jonathan S. Fisher 
wrote:

>
> A better way would be to wrap your legacy EJBs with RESTful services
> so that way you're platform independent.
>

+1 I like this approach... even though I am running 2 separate TomEE's on
same machine, they communicate via RESTful services and have been working
really well; I'm sure the code I wrote helps as well.

Re: Tomcat security issues and tomee 1.7.x

[Howard W. Smith, Jr.]

Looking forward to (and have been waiting patiently for) TomEE+ 1.7.5
release, too. Thank you in advance!

Re: Recommended Java 8 settings

[Howard W. Smith, Jr.]

My responses below/inline,

On Thu, Jul 28, 2016 at 10:23 AM, Felipe Jaekel  wrote:

> I used to run TomEE 1.7.2 with java 7 and the following config:
> -Xms1G
> -Xmx3G (server has 4G)
> -XX:MaxPermSize=1G
> -XX:+UseTLAB
> -XX:+UseConcMarkSweepGC
> -XX:+CMSIncrementalMode
> -XX:+CMSClassUnloadingEnabled
>

I used the options similar to these above for years. With these settings
(and throughout the years), I have seen memory required-and-used between
500M and 4G, depending on certain database queries/operations executed
during runtime.


>
> I upgraded to Java 8 to use TomEE 7.0.x, so I decided to try different
> settings:
> -Xmx3G (server has 4G)
> -XX:+UseG1GC
> -XX:+UseStringDeduplication
>

Recently, I changed to these options above after seeing others speak about
this in ActiveMQ (or tomcat) user mail list, and I am impressed with what I
see whenever I check memory at runtime via Java Visual VM (via JMX). Now,
quite consistently, I see memory required-and-used <= 500M (sometimes 700M,
but not really over 700M).

Re: what omnifaces version use with tomee 1.7??

[Howard W. Smith, Jr.]

Hmmm,

so earlier you said,

I had problems with OmniFaces  2.x + TomEE 1.7.2

and

On Tue, Jan 5, 2016 at 5:47 AM, Felipe Jaekel  wrote:

> MyFaces 2.2.8, but the root of the problem was that OmniFaces 2.x requires
> CDI 1.1...
>

Would probably need to know more about your stack to determine why you have
issues and myself and others are not having issues with TomEE(plus) 1.7.2
and 1.7.3 and OmniFaces 2.x.

I usually unzip tomee *plus* 1.7.x ZIP file to my hard drive, including the
openwebbeans 1.2.7 JARs that are in the tomee-plus ZIP file, and replace
myfaces JARs with latest MyFaces 2.2.x JAR files, package latest OmniFaces
2.x JAR file in my WAR file, and drop WAR file in tomee/webapps folder.

This[1] says that OpenWebBeans 1.2.7 implements CDI 1.0, but internally is
already CDI 1.1, so I believe this is why OmniFaces 2.x [just] works with
TomEE-plus 1.7.x.

What version of OpenWebBeans are you using?

[1] http://openwebbeans.apache.org/download.html#owb-12x

Re: what omnifaces version use with tomee 1.7??

[Howard W. Smith, Jr.]

Interesting. I did not have any issues. I always deploy OmniFaces JAR
in/with my WAR file. Felipe, are you using MyFaces 2.2.x or 2.1.x?
On Jan 4, 2016 7:27 AM, "Felipe Jaekel"  wrote:

> I had problems with OmniFaces  2.x + TomEE 1.7.2
>
> https://issues.apache.org/jira/browse/TOMEE-1634
>
> Currently I'm using OmniFaces 1.11
>
> 2016-01-04 9:57 GMT-02:00 Howard W. Smith, Jr. :
>
> > Mauro, the latest OmniFaces showcase should work with tomee 1.7.2.
> >
> > if you look at,
> > https://github.com/omnifaces/showcase/releases
> >
> > Then you will see that there are only 2 showcase versions available, 1.2
> > and 2.0. Showcase version != OmniFaces version (1.8 or 2.0).
> > On Jan 4, 2016 4:08 AM, "mauro2java2011" 
> wrote:
> >
> > > HI Howard,
> > > i have understand to use ominfaces 1.8 with tomee 1.7.x and myfaces
> 2.1.x
> > >
> > > Now i would install the showcase of omnifaces locally for use the
> > > documentation and examples offline.
> > > But the sources are with omnifaces 2.2 that use jsf2,.2
> > >
> > > SO i you ask if i copy the sources into a web proiject with netbeans
> and
> > i
> > > use tomee 1.7.2 for compile it work with the omnifaces jar 1.8.3?
> > >
> > > Or where i can get the showcase web application of omninfaces that work
> > > with
> > > 1.8.3 of omnifaces and tomee 1.7.2?
> > >
> > >
> > >
> > >
> > > --
> > > View this message in context:
> > >
> >
> http://tomee-openejb.979440.n4.nabble.com/what-omnifaces-version-use-with-tomee-1-7-tp4677331p4677338.html
> > > Sent from the TomEE Users mailing list archive at Nabble.com.
> > >
> >
>

Re: what omnifaces version use with tomee 1.7??

[Howard W. Smith, Jr.]

Mauro, the latest OmniFaces showcase should work with tomee 1.7.2.

if you look at,
https://github.com/omnifaces/showcase/releases

Then you will see that there are only 2 showcase versions available, 1.2
and 2.0. Showcase version != OmniFaces version (1.8 or 2.0).
On Jan 4, 2016 4:08 AM, "mauro2java2011"  wrote:

> HI Howard,
> i have understand to use ominfaces 1.8 with tomee 1.7.x and myfaces 2.1.x
>
> Now i would install the showcase of omnifaces locally for use the
> documentation and examples offline.
> But the sources are with omnifaces 2.2 that use jsf2,.2
>
> SO i you ask if i copy the sources into a web proiject with netbeans and i
> use tomee 1.7.2 for compile it work with the omnifaces jar 1.8.3?
>
> Or where i can get the showcase web application of omninfaces that work
> with
> 1.8.3 of omnifaces and tomee 1.7.2?
>
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/what-omnifaces-version-use-with-tomee-1-7-tp4677331p4677338.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>

Re: what omnifaces version use with tomee 1.7??

[Howard W. Smith, Jr.]

Try OmniFaces 1.8
On Dec 31, 2015 7:02 AM, "mauro2java2011"  wrote:

> But if i not change the jsf jars from version 2.1 at 2.2 i have to use 1.8?
>
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/what-omnifaces-version-use-with-tomee-1-7-tp4677331p4677336.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>

Re: what omnifaces version use with tomee 1.7??

[Howard W. Smith, Jr.]

Mauro, I use tomee+ 1.7.x with latest version of OmniFaces 2.x, and replace
tomee/lib/myfaces JAR files with latest MyFaces 2.2.x files, always.

Re: Performance problems in tomee 7.0.0

[Howard W. Smith, Jr.]

Interesting discussion. I am eclipselink and PrimeFaces user, currently
using TomEE 1.7.3, and hope to use tomee 7.0.0 sometime in the future.
On Dec 23, 2015 9:05 AM, "Romain Manni-Bucau"  wrote:

> Yep issue is primefaces validator usage which is not compatible with bval
> caching - strictly speaking both are right even if primefaces usage is
> surprising (they use an internal validator that they create and recreate
> without any config change from the quick code i saw).
> Le 23 déc. 2015 15:00, "cocorossello"  a écrit :
>
> > 2.6.1
> >
> > But the problem is not only with eclipselink, it just becomes more
> evident
> > with it.
> >
> >
> >
> > --
> > View this message in context:
> >
> http://tomee-openejb.979440.n4.nabble.com/Performance-problems-in-tomee-7-0-0-tp4677292p4677296.html
> > Sent from the TomEE Users mailing list archive at Nabble.com.
> >
>

Re: Performance problems in tomee 7.0.0

[Howard W. Smith, Jr.]

On Dec 23, 2015 6:57 AM, "cocorossello"  wrote:
>
> We are hitting performance problems with primefaces datatables with
> checkboxes in it listing eclipselink entities, 10 or 20 seconds to render
a
> page.
>

May I ask which version of eclipselink are you using with tomee 7.0.0?

Re: Resource and UseAppClassLoader question

[Howard W. Smith, Jr.]

On Dec 3, 2015 10:01 AM, "Howard W. Smith, Jr." 
wrote:
>
>
> On Dec 3, 2015 6:18 AM, "Violeta Georgieva"  wrote:
> >
> > smithh032772 wrote
> > > On Dec 1, 2015 2:48 PM, "Violeta Georgieva" <
> >
> > > violetagg@
> >
> > > > wrote:
> > >>
> > >>
> > >> I'm testing with TomEE 1.7.3
> > >
> > > Is TomEE 1.7.3 available via tomee downloads page or somewhere else?
> >
> > I tested with the staged binaries from the mail that called for 1.7.3
voting
> >
> >
> >
>
> Will have to look for that email, thanks.

Found it.[1]

[1]
http://tomee-openejb.979440.n4.nabble.com/VOTE-staging-1071-tomee-1-7-3-td4676997.html

Re: Resource and UseAppClassLoader question

[Howard W. Smith, Jr.]

On Dec 3, 2015 6:18 AM, "Violeta Georgieva"  wrote:
>
> smithh032772 wrote
> > On Dec 1, 2015 2:48 PM, "Violeta Georgieva" <
>
> > violetagg@
>
> > > wrote:
> >>
> >>
> >> I'm testing with TomEE 1.7.3
> >
> > Is TomEE 1.7.3 available via tomee downloads page or somewhere else?
>
> I tested with the staged binaries from the mail that called for 1.7.3
voting
>
>
>

Will have to look for that email, thanks.

Re: Resource and UseAppClassLoader question

[Howard W. Smith, Jr.]

On Dec 2, 2015 4:56 PM, "Romain Manni-Bucau"  wrote:
>
> it doesnt exit yet but staging repo is there
>
https://repository.apache.org/content/repositories/orgapachetomee-1071/org/apache/openejb/apache-tomee/1.7.3/
>
>

*404 - Repository with ID="orgapachetomee-1071" not found*

Repository with ID="orgapachetomee-1071" not found

Re: Resource and UseAppClassLoader question

[Howard W. Smith, Jr.]

On Dec 1, 2015 2:48 PM, "Violeta Georgieva"  wrote:
>
>
> I'm testing with TomEE 1.7.3

Is TomEE 1.7.3 available via tomee downloads page or somewhere else?

Re: JCache using TomEE 7.0.0 example project

[Howard W. Smith, Jr.]

Thanks for sharing!

Re: Problem with Tomee on ejbPostCreate method - OutOfMemoryError

[Howard W. Smith, Jr.]

Interesting thread (discussion, findings, etc...). Thanks to all.

Re: TomEE vs commercial offering: No need?

[Howard W. Smith, Jr.]

On Oct 24, 2015 7:09 AM, "Romain Manni-Bucau"  wrote:
>
> Hi Mikael
>
> Let s try to answer even if it looks like a spam: if you ask precise
> questions instead of asking us to do your work we can refine what we
> already said you if needed.

+1 Does look like spam.

Re: singleton initializing twice? (1.6.0-stable)

[Howard W. Smith, Jr.]

My apologies, I did not see that behavior.

On Mon, Sep 28, 2015 at 4:15 PM, Howard W. Smith, Jr. <
smithh032...@gmail.com> wrote:

>
>
> On Mon, Sep 28, 2015 at 3:55 PM, Romain Manni-Bucau  > wrote:
>
>> got it but knowing 1.7.2 has the same issue helps to identify if we need
>> to
>> solve an unidentified issue or a fixed issue with potentially a
>> workwround.
>>
>>
> hmmm, i've been using tomee 1.7.2 (in production) ever since June 2015,
> and I think I saw this behavior, too, recently (once or twice). Let me
> check my log files and confirm.
>
>
What I saw was my app attempting to send multiple emails via my JavaMail
POJO, invoked by some non-JMS code and immediately after via some JMS/MDB
code, initializing twice,

Sep 23, 2015 11:02:06 PM utils.mail.JavaMail initMailSession
INFO: JavaMail.initMailSession(): initializing DEFAULT instance of
mailSession
Sep 23, 2015 11:02:06 PM utils.mail.JavaMail initMailSession
INFO: JavaMail.initMailSession(): initializing DEFAULT instance of
mailSession

and then initialized,

Sep 23, 2015 11:02:06 PM utils.mail.JavaMail initMailSession
INFO: JavaMail.initMailSession(): initialized DEFAULT instance of
mailSession
Sep 23, 2015 11:02:06 PM utils.mail.JavaMail initMailSession
INFO: JavaMail.initMailSession(): initialized DEFAULT instance of
mailSession

Re: singleton initializing twice? (1.6.0-stable)

[Howard W. Smith, Jr.]

On Mon, Sep 28, 2015 at 3:55 PM, Romain Manni-Bucau 
wrote:

> got it but knowing 1.7.2 has the same issue helps to identify if we need to
> solve an unidentified issue or a fixed issue with potentially a workwround.
>
>
hmmm, i've been using tomee 1.7.2 (in production) ever since June 2015, and
I think I saw this behavior, too, recently (once or twice). Let me check my
log files and confirm.

Re: WebServlet match on root

[Howard W. Smith, Jr.]

On Thu, Sep 3, 2015 at 12:08 PM, tonywestonuk  wrote:

>
>   Its been a good day! :-D
>

Sounds like it's been a TomEE day!  :-D

Re: JSR-107, JCache

[Howard W. Smith, Jr.]

Steve,

On Tue, Aug 18, 2015 at 10:38 AM, Steve Goldsmith  wrote:

> Are there any good examples? I'll promise to add it my test project on
> Github, so others can benefit as well.
>

I like how you share code for others to benefit, and I love TomEE (user
list) just as well!

I searched google for

jcache tutorial java

and found the following:

https://cloud.google.com/appengine/docs/java/memcache/usingjcache

https://dzone.com/articles/introduction-jcache-jsr-107

https://abhirockzz.wordpress.com/2015/02/09/sneak-peek-into-the-jcache-api-jsr-107/

hope that helps.

Re: "Getting started with Tomcat" ft TomEE

[Howard W. Smith, Jr.]

Wow, that's really nice of Alex and Romain!


On Fri, Aug 14, 2015 at 12:33 AM, Jonathan Fisher <
jonat...@springventuregroup.com> wrote:

> This is a great article over at DZone introducing some Tomcat concepts.
> They put a great plug in for our beloved Apache TomEE too :) Enjoy
>
> https://dzone.com/refcardz/getting-started-with-apache-tomcat
>
>
Getting Started With Apache TomcatLearn the Tomcat Pure Java Open-Source
Web Server

by Alex Soto  and Romain
Manni-bucau 




> *Jonathan S. Fisher*
> *VP - Information Technology*
> *Spring Venture Group*
>
> --
> Email Confidentiality Notice: The information contained in this
> transmission is confidential, proprietary or privileged and may be subject
> to protection under the law, including the Health Insurance Portability and
> Accountability Act (HIPAA). The message is intended for the sole use of the
> individual or entity to whom it is addressed. If you are not the intended
> recipient, you are notified that any use, distribution or copying of the
> message is strictly prohibited and may subject you to criminal or civil
> penalties. If you received this transmission in error, please contact the
> sender immediately by replying to this email and delete the material from
> any computer.
>

Re: No exception until attempt to use ActiveMQ on 2 separate tomee instances

[Howard W. Smith, Jr.]

Interesting, okay.


On Wed, Aug 5, 2015 at 6:58 PM, Romain Manni-Bucau 
wrote:

> Local transport  can skip serialization in some cases
> Le 5 août 2015 15:57, "Howard W. Smith, Jr."  a
> écrit :
>
> > Okay, I just recognized that after searching internet, but I still wonder
> > why the code below works when I have one tomee (activemq) instance. Prior
> > to today, GoogleCalendarEvent did not need to implement Serializable.
> >
> > public void updateGoogleCalendar(List
> eventsToAdd)
> > throws Exception {
> > Message message = session.createMessage();
> > /*
> >  *
> >
> >
> http://stackoverflow.com/questions/6904048/object-with-collection-containing-serializable-non-primitive-objects-cant-be-s
> >  */
> > message.setObjectProperty("List",
> > eventsToAdd);
> > gCalProducer.send(message);
> > }
> >
> >
> > On Wed, Aug 5, 2015 at 6:52 PM, Romain Manni-Bucau <
> rmannibu...@gmail.com>
> > wrote:
> >
> > > Surely cause not serialized
> > > Le 5 août 2015 14:40, "Howard W. Smith, Jr." 
> a
> > > écrit :
> > >
> > > > Below, is what is in my tomee.xml for tomee 2nd instance,
> > > >
> > > > On Wed, Aug 5, 2015 at 5:37 PM, Howard W. Smith, Jr. <
> > > > smithh032...@gmail.com
> > > > > wrote:
> > > >
> > > > > For tomee 2nd instance, I changed server shutdown port, connector
> > port,
> > > > > and add the following to tomee.xml:
> > > > >
> > > >
> > > > 
> > > > 
> > > >   BrokerXmlConfig =  broker:(tcp://localhost:62616)
> > > >   ServerUrl   =  tcp://localhost:62616
> > > > 
> > > >
> > > >  > type="javax.jms.ConnectionFactory">
> > > >   ResourceAdapter = MyJmsResourceAdapter
> > > > 
> > > >
> > > > 
> > > >   ResourceAdapter = MyJmsResourceAdapter
> > > > 
> > > >
> > >
> >
>

Re: No exception until attempt to use ActiveMQ on 2 separate tomee instances

[Howard W. Smith, Jr.]

Okay, I just recognized that after searching internet, but I still wonder
why the code below works when I have one tomee (activemq) instance. Prior
to today, GoogleCalendarEvent did not need to implement Serializable.

public void updateGoogleCalendar(List eventsToAdd)
throws Exception {
Message message = session.createMessage();
/*
 *
http://stackoverflow.com/questions/6904048/object-with-collection-containing-serializable-non-primitive-objects-cant-be-s
 */
message.setObjectProperty("List", eventsToAdd);
gCalProducer.send(message);
}


On Wed, Aug 5, 2015 at 6:52 PM, Romain Manni-Bucau 
wrote:

> Surely cause not serialized
> Le 5 août 2015 14:40, "Howard W. Smith, Jr."  a
> écrit :
>
> > Below, is what is in my tomee.xml for tomee 2nd instance,
> >
> > On Wed, Aug 5, 2015 at 5:37 PM, Howard W. Smith, Jr. <
> > smithh032...@gmail.com
> > > wrote:
> >
> > > For tomee 2nd instance, I changed server shutdown port, connector port,
> > > and add the following to tomee.xml:
> > >
> >
> > 
> > 
> >   BrokerXmlConfig =  broker:(tcp://localhost:62616)
> >   ServerUrl   =  tcp://localhost:62616
> > 
> >
> > 
> >   ResourceAdapter = MyJmsResourceAdapter
> > 
> >
> > 
> >   ResourceAdapter = MyJmsResourceAdapter
> > 
> >
>

Re: No exception until attempt to use ActiveMQ on 2 separate tomee instances

[Howard W. Smith, Jr.]

Below, is what is in my tomee.xml for tomee 2nd instance,

On Wed, Aug 5, 2015 at 5:37 PM, Howard W. Smith, Jr.  wrote:

> For tomee 2nd instance, I changed server shutdown port, connector port,
> and add the following to tomee.xml:
>



  BrokerXmlConfig =  broker:(tcp://localhost:62616)
  ServerUrl   =  tcp://localhost:62616



  ResourceAdapter = MyJmsResourceAdapter



  ResourceAdapter = MyJmsResourceAdapter

No exception until attempt to use ActiveMQ on 2 separate tomee instances

[Howard W. Smith, Jr.]

When I had 1 or 2 web applications on 1 tomee instance (and default tomee
ActiveMQ configuration),

app1
- has MDBs, using ActiveMQ JMS
- JAX RS (web) client to execute REST service on app2

app2
- has MDBs, using ActiveMQ JMS
- REST service running, uses MDBs to execute business logic

This works great on 1 tomee instance, but when I create a 2nd tomee
instance for app2 (above), I am getting the exception below.

For tomee 2nd instance, I changed server shutdown port, connector port, and
add the following to tomee.xml:



BrokerXmlConfig =  broker:(tcp://someHostName:61616)
ServerUrl   =  tcp://someHostName:61616



ResourceAdapter = MyJmsResourceAdapter



ResourceAdapter = MyJmsResourceAdapter



as per

Internal ActiveMQ Broker
http://tomee.apache.org/jms-resources-and-mdb-container.html

app1 on tomee 1 starts and runs well

app2 on tomee 2 starts, but has the following exception:


Aug 05, 2015 5:22:38 PM
com.mcms.googleCalendar.GoogleCalendarUpdateQueueBean
updateGoogleCalendarViaSchedule
INFO: Error occurred while adding 07/20/2018 to the Google Calendar update
queue
javax.jms.JMSException: Object is not a primitive:
com.mcms.googleCalendar.GoogleCalendarEvent@715c993d
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:72)
at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1435)
at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1345)
at org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1904)
at
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:289)
at
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:224)
at
org.apache.activemq.ActiveMQMessageProducerSupport.send(ActiveMQMessageProducerSupport.java:241)
at
com.mcms.application.ApplicationMessageBean.updateGoogleCalendar(ApplicationMessageBean.java:150)
at
com.mcms.application.ApplicationMessageBean$$OwbNormalScopeProxy0.updateGoogleCalendar(com/mcms/application/ApplicationMessageBean.java)
at
com.mcms.application.ApplicationScopeBean.sendUpdateGoogleCalendarMsg(ApplicationScopeBean.java:217)
at
com.mcms.application.ApplicationScopeBean$$OwbNormalScopeProxy0.sendUpdateGoogleCalendarMsg(com/mcms/application/ApplicationScopeBean.java)
at
com.mcms.googleCalendar.GoogleCalendarUpdateQueueBean.updateGoogleCalendarViaSchedule(GoogleCalendarUpdateQueueBean.java:425)
at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:192)
at
org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:173)
at
org.apache.openejb.monitoring.StatsInterceptor.record(StatsInterceptor.java:181)
at
org.apache.openejb.monitoring.StatsInterceptor.AroundTimeout(StatsInterceptor.java:145)
at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:192)
at
org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:173)
at
org.apache.openejb.core.interceptor.InterceptorStack.invoke(InterceptorStack.java:85)
at
org.apache.openejb.core.singleton.SingletonContainer._invoke(SingletonContainer.java:256)
at
org.apache.openejb.core.singleton.SingletonContainer.invoke(SingletonContainer.java:212)
at
org.apache.openejb.core.timer.EjbTimerServiceImpl.ejbTimeout(EjbTimerServiceImpl.java:803)
at
org.apache.openejb.core.timer.EjbTimeoutJob.execute(EjbTimeoutJob.java:39)
at org.apache.openejb.quartz.core.JobRunShell.run(JobRunShell.java:202)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: Object is not a primitive:
com.mcms.googleCalendar.GoogleCalendarEvent@715c993d
at
org.apache.activemq.util.MarshallingSupport.marshalPrimitive(MarshallingSupport.java:156)
at
org.apache.activemq.util.MarshallingSupport.marshalPrimitiveList(MarshallingSupport.java:107)
at
org.apache.activemq.util.MarshallingSupport.marshalPrimitive(MarshallingSupport.java:154)
at
org.apache.activemq.util.MarshallingSupport.marshalPrimitiveMap(MarshallingSupport.java:64)
at org.apache.activemq.command.Message.beforeMarshall(Message.java:231)
at
org.apache.activemq.openwire.v10.MessageMarshaller.tightMarshal1(MessageMarshaller.java:122)
at
org.apache.activemq.openwire.v10.ActiveMQMessageMarshaller.tightMarshal1(ActiveMQM

Re: netbeans annoyance

[Howard W. Smith, Jr.]

On Thu, Jun 11, 2015 at 10:49 AM, Howard W. Smith, Jr. <
smithh032...@gmail.com> wrote:

>
> On Tue, Jun 2, 2015 at 3:09 PM, hwaastad  wrote:
>
>> I discovered that starting tomee 1.7.2 (plus) as a server in netbeans,
>> netbeans is not too happy about the server="Apache TomEE" config on the
>> 8080
>> connector.
>> So by removing this one startup is OK again.
>>
>
> can you please clarify this? what did you do? did you rename server name
> from Apache TomEE to something else? or did you specify another port
> instead of 8080?
>
> I am experiencing this issue now, too, since I am using latest NetBeans
> and TomEE+ 1.7.2.
>
> Thanks,
> Howard
>
>
The fix[1] for me.

[1] http://stackoverflow.com/a/30788322/933054

Re: netbeans annoyance

[Howard W. Smith, Jr.]

On Tue, Jun 2, 2015 at 3:09 PM, hwaastad  wrote:

> I discovered that starting tomee 1.7.2 (plus) as a server in netbeans,
> netbeans is not too happy about the server="Apache TomEE" config on the
> 8080
> connector.
> So by removing this one startup is OK again.
>

can you please clarify this? what did you do? did you rename server name
from Apache TomEE to something else? or did you specify another port
instead of 8080?

I am experiencing this issue now, too, since I am using latest NetBeans and
TomEE+ 1.7.2.

Thanks,
Howard

Re: Stateless dead lock

[Howard W. Smith, Jr.]

On Wed, Jun 10, 2015 at 1:18 PM, Romain Manni-Bucau 
wrote:

> Hi Matej
>
> looks like a database issue for me (stateless pool is waiting for the
> stateless trying to get the db connection to be released), hasnt the DB
> connection be lost or something like that?
>
>
what is the best way for Matej to improve that? tomcat jdbc pool settings?

Re: tomee jee 7

[Howard W. Smith, Jr.]

> So I’d say TomEE is not only the best server around but almost the only
_real_ open source server on the market.

+1 I agree!

>
> LieGrue,
> strub

Re: BUG ON APACHE TOMCAT 8, 7, AND TOMEE 1.7

[Howard W. Smith, Jr.]

2015-05-29 0:31 GMT-04:00 JESUS GEIDER GUERRA HERNANDEZ <
jgguer...@misena.edu.co>:

> I create a Session Beans For Entity Classess, the message show up this:
>
> Cannot be generated for Java EE 6 sources without server with complete
>  Java EE 6 Web Profile support (at least EJB Lite support).
>

I see that message too, since/when I use NetBeans (version 7.x, 8.x) with
TomEE+.

When I used NetBeans with Glassfish 3.1.x (years ago), I did not
see/experience that error.

Re: primefaces5-1.war not work

[Howard W. Smith, Jr.]

Felipe, he is trying to run the PrimeFaces 5.1 showcase WAR file in tomee.
See below.

Caused by: org.apache.tomee.catalina.TomEERuntimeException:
org.apache.openejb.OpenEJBException: Unable to load servlet filter class:
org.primefaces.showcase.filter.CharacterEncodingFilter:
org.primefaces.showcase.filter.CharacterEncodingFilter
On Mar 23, 2015 7:51 AM, "Felipe Jaekel"  wrote:

> I pack PrimeFaces inside WEB-INF/lib, works fine with 1.7.1.
>
> 2015-03-21 7:20 GMT-03:00 mauro2java2011 :
>
> > Hi all. i have tired to use the primefaces 5.1 war into tomee
> > but it not working.
> > i ahave removed the fiels for validation 1.,1 ( already rpesent the
> > validation 1.o nto tomee).
> > But i get error.
> >
> >
> > .
> >
> > INFORMAZIONI: Manager: list: Listing contexts for virtual host
> 'localhost'
> > mar 21, 2015 11:26:10 AM org.apache.catalina.core.ApplicationContext log
> > INFORMAZIONI: Manager: list: Listing contexts for virtual host
> 'localhost'
> > mar 21, 2015 11:26:15 AM org.apache.catalina.core.ApplicationContext log
> > INFORMAZIONI: Manager: start: Starting web application '/showcase-5.1'
> > mar 21, 2015 11:26:18 AM org.apache.catalina.core.ApplicationContext log
> > GRAVE: FAIL - Application at context path /showcase-5.1 could not be
> > started
> > org.apache.catalina.LifecycleException: Failed to start component
> >
> >
> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/showcase-5.1]]
> > at
> > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
> > at
> >
> org.apache.catalina.manager.ManagerServlet.start(ManagerServlet.java:1291)
> > at
> > org.apache.catalina.manager.ManagerServlet.doGet(ManagerServlet.java:390)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> > at
> >
> >
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
> > at
> >
> >
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> > at
> > org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> > at
> >
> >
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> > at
> >
> >
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> > at
> >
> >
> org.apache.catalina.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:108)
> > at
> >
> >
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> > at
> >
> >
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> > at
> >
> >
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
> > at
> >
> >
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
> > at
> > org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:44)
> > at
> >
> >
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:610)
> > at
> >
> >
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> > at
> >
> >
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
> > at
> > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
> > at
> >
> >
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
> > at
> >
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
> > at
> >
> >
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1070)
> > at
> >
> >
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
> > at
> >
> >
> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
> > at
> >
> >
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> > at
> >
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> > at
> >
> >
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> > at java.lang.Thread.run(Thread.java:744)
> > Caused by: org.apache.tomee.catalina.TomEERuntimeException:
> > org.apache.openejb.OpenEJBException: Unable to load servlet filter class:
> > org.primefaces.showcase.filter.CharacterEncodingFilter:
> > org.primefaces.showcase.filter.CharacterEncodingFilter
> > at
> >
> >
> org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:1257)
> > at
> >
> >
> org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBuilder.java:1087)
> > at
> >
> >
> org.apache.tomee.catalina.GlobalListenerSuppo

Re: Tomee 1.7.1 compatible in Java 8

[Howard W. Smith, Jr.]

Agreed. Should not be too hard, since tomee has jodatime 1.6.2 dependency
for years now. Right?

Java 8 new Date time API = jodatime
 On Feb 19, 2015 1:24 PM, "cchacin"  wrote:

> Also we need to make some hacks to use new Date & Time API.
>
> On Thu, Feb 19, 2015, 10:13 AM Romain Manni-Bucau [via TomEE & OpenEJB] <
> ml-node+s979440n4673801...@n4.nabble.com> wrote:
>
> > OpenJPA just tolerate java 8 bytecode but doesn't support new Java 8
> > API so if you use them entity lifecycle can be broken. typically if
> > you modify a collection using stream API instead of Collection API
> > then the relationship will not get updated as exepected in the
> > database. Rarely an issue in practise but abusing of JPA as domain
> > objects with java 8 can lead to such issues.
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau
> > http://www.tomitribe.com
> > http://rmannibucau.wordpress.com
> > https://github.com/rmannibucau
> >
> >
> > 2015-02-19 19:08 GMT+01:00 Suzanne Genod <[hidden email]
> > >:
> >
> > > Hi,
> > >
> > > Would you please expand on what are TomE 1.7.1 limitations with JPA
> > > entities when running with Java 8?
> > >
> > > Thanks,
> > > Suz
> > >
> > > On Thu, Feb 19, 2015 at 5:59 PM, Romain Manni-Bucau <[hidden email]
> > >
> > > wrote:
> > >
> > >> Just a side note: it works while you don't abuse of it in JPA entities
> > >> (it is only tolerated here)
> > >>
> > >>
> > >> Romain Manni-Bucau
> > >> @rmannibucau
> > >> http://www.tomitribe.com
> > >> http://rmannibucau.wordpress.com
> > >> https://github.com/rmannibucau
> > >>
> > >>
> > >> 2015-02-19 17:54 GMT+01:00 Jean-Louis Monteiro <[hidden email]
> > >:
> > >> > Thx for the feedback Vincenzo.
> > >> >
> > >> > Very cool to see users answering questions from other users. That's
> > very
> > >> > important.
> > >> >
> > >> > and btw, you are right. All the bytecode processing has been updated
> > to
> > >> > support Java 8
> > >> >
> > >> > --
> > >> > Jean-Louis Monteiro
> > >> > http://twitter.com/jlouismonteiro
> > >> > http://www.tomitribe.com
> > >> >
> > >> > On Thu, Feb 19, 2015 at 5:40 PM, Vincenzo D'Amore <[hidden email]
> > >
> > >> > wrote:
> > >> >
> > >> >> Hi, yes, I'm actively using it with Java 8.
> > >> >>
> > >> >> On Thu, Feb 19, 2015 at 5:26 PM, [hidden email]
> >  <[hidden email]
> > 
> > >> >
> > >> >> wrote:
> > >> >>
> > >> >> > Hi all,
> > >> >> >
> > >> >> > Is Tomee 1.7.1 is compatible in Java 8?
> > >> >> >
> > >> >> > Thanks
> > >> >> > Kayal
> > >> >> >
> > >> >> >
> > >> >> >
> > >> >> > --
> > >> >> > View this message in context:
> > >> >> >
> > >> >>
> > >>
> >
> http://tomee-openejb.979440.n4.nabble.com/Tomee-1-7-1-compatible-in-Java-8-tp4673794.html
> > >> >> > Sent from the TomEE Users mailing list archive at Nabble.com.
> > >> >> >
> > >> >>
> > >> >>
> > >> >>
> > >> >> --
> > >> >> Vincenzo D'Amore
> > >> >> email: [hidden email]
> > 
> > >> >> skype: free.dev
> > >> >> mobile: +39 349 8513251
> > >> >>
> > >>
> >
> >
> > --
> >  If you reply to this email, your message will be added to the discussion
> > below:
> >
> >
> http://tomee-openejb.979440.n4.nabble.com/Tomee-1-7-1-compatible-in-Java-8-tp4673794p4673801.html
> >  To start a new topic under TomEE Users, email
> > ml-node+s979440n979441...@n4.nabble.com
> > To unsubscribe from TomEE Users, click here
> > <
> http://tomee-openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=979441&code=Y2NoYWNpbkBnbWFpbC5jb218OTc5NDQxfDE2NzcwMDYzOTY=
> >
> > .
> > NAML
> > <
> http://tomee-openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> >
> >
>
>
>
>
> -
> Carlos Chacin
> http://github.com/cchacin
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Tomee-1-7-1-compatible-in-Java-8-tp4673794p4673802.html
> Sent from the TomEE Users mailing list archive at Nabble.com.

Re: Just curious, what parts of JEE is everyone using?

[Howard W. Smith, Jr.]

i'm doing the following:

On Sun, Feb 8, 2015 at 4:41 PM, Lars-Fredrik Smedberg 
wrote:

> For us...
>
> EJB3 (Singleton, Stateless, MessageDriven mostly - Tx, @Asynchronous, EJB
> @Schedule)
>


> JMS (Active MQ bundled with TomEE++)
>


> CDI @ApplicationScoped, @RequestScoped, @SessionScoped, @ViewScoped
>


> JTA
> Bean Validation
> Servlets / Filters
>

JSF 2.2 (MyFaces)

Re: Eclipselink question

[Howard W. Smith, Jr.]

On Thu, Jan 22, 2015 at 5:59 PM, Andy Gumbrecht 
wrote:

> What do your actual db tables and entities look like? Can you supply some
> details?
>
> Andy.
>
>
> On 22/01/2015 19:10, Howard W. Smith, Jr. wrote:
>
>> Collections work well when I check isEmpty(), but I'm not using that
>> notation. I'm still using eclipselink 2.3.2.
>
>
In my app,

ORDERS has Destinations, Origins, Customer, OrderCostDetails, etc...

destinations and origins have address
address has address lines, city, state, postal code (or zip code), country

So, what I was referring to, earlier, was the following comment in my
code[1] which is referenced when generating and doing processing related to
an 'annual report' of previous year data.

/*
 * Using isEmpty() on collections, instantiates the
object; see below
 * http://stackoverflow.com/a/12100628/933054[2]
 */

EclipseLink isEmpty() showed up in jvisualvm[3] when I was doing some
performance monitoring of JSF pages in my app that is used by enduser to
develop this annual report.

[1] https://gist.github.com/8169ee34793a4babb502.git
[2] http://stackoverflow.com/a/12100628/933054
[3] http://s3.postimg.org/4vhkyquv7/20150112_perf_edit_Rolling_Stock.png

Re: Eclipselink question

[Howard W. Smith, Jr.]

Collections work well when I check isEmpty(), but I'm not using that
notation. I'm still using eclipselink 2.3.2.
On Jan 22, 2015 1:04 PM,  wrote:

> Hello! I think something is weird in eclipselink. I need to reproduce but
> if you do select item where supplier = selectedSupplier It is one select
> per item even if item only has a elementcollection with a few values...
>
> Seems any kind of collection is unusable. Thanks for your input
> Skickat från min iPhone
>
> > 22 jan 2015 kl. 14:20 skrev Andy Gumbrecht :
> >
> > Hi Karl,
> >
> > Firstly Ouch, I know it is always tempting to use things like this
> but I would not use it unless there was a really really good reason to use
> it. It is not compatible with anything other than EL.
> >
> > If your child objects start to become so many that you are thinking of
> batching the load then opt for a 'fetch = FetchType.LAZY' instead. This
> means you would need to add an additional method to your service layer to
> get the child objects. This is basically how you'd do it using JDBC too.
> >
> > final Parent p = service.getParent(long id);
> >
> > //List lc = p.getChildren(); <-- Hundreds of children, but null
> list here if lazy loaded and detached...
> >
> > List lc = service.getChildren(p);
> >
> > If you still want to batch then do it manually:
> >
> > List lc = service.getChildren(p, start, end); //Pretty easy to
> write your retrieval own loop here... eg. while !lc.isEmpty()
> >
> > Andy.
> >
> >> On 21/01/2015 18:17, karl.kil...@gmail.com wrote:
> >> Hello! Those of You who use eclipselink have been a real help before.
> How do you manage
> http://eclipse.org/eclipselink/documentation/2.4/jpa/extensions/a_batchfetch.htm
> >>
> >> You need this everywhere to get decent behavior but it cannot be
> configured globally :(
> >>
> >> Cheers
> >>
> >> Skickat från min iPhone
> >
> > --
> >  Andy Gumbrecht
> >  https://twitter.com/AndyGeeDe
> >  http://www.tomitribe.com
> >
>

Re: Tomee 1.7.2 Release Date

[Howard W. Smith, Jr.]

Also, will TomEE 1.7.2 include the latest Tomcat 7 release?

Tomcat 7.0.57 was released 2014-11-11.


On Thu, Dec 4, 2014 at 9:50 AM, ivan_nikitsenka 
wrote:

> Hello
>
> When Tomee 1.7.2 will be released?
>
> It will be great if you can provide approximate date or month
>
> Thanks,
> Ivan
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Tomee-1-7-2-Release-Date-tp4673133.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>

Re: testing with eclipselink.

[Howard W. Smith, Jr.]

On Wed, Nov 12, 2014 at 9:20 AM, Romain Manni-Bucau <
rmannibu...@tomitribe.com> wrote:

> Site note: we have an openejb-core-eclipselink replacing openejb-core
> which comes with eclipselink out of the box
>

Was openejb-core-eclipselink added for Plume (mojarra/eclipselink)? what
version of eclipselink is it?

Re: CDI container performance

[Howard W. Smith, Jr.]

On Tue, Oct 21, 2014 at 6:00 AM, Romain Manni-Bucau <
rmannibu...@tomitribe.com> wrote:

> > OWB-1.5.0 is and/or will be bundled with TomEE+ 2.x 'and' future TomEE+
> > 1.7.x releases?
> >
>
> It is in TomEE 2


Nice to hear, thanks Romain!  :)

Re: CDI container performance

[Howard W. Smith, Jr.]

Wow, very impressive. I'm glad I'm using TomEE+ 1.7.1 (for now) and looking
forward to TomEE+ 2.x.

Questions below,



   - OWB-1.5.0: 13 ms (no this is NOT a hoax, it's due to our proxy caching
   [1]...)

All with Java8.

Currently trying to run it on other boxes to rule out some misconfiguration

[1] For @ApplicationScoped beans our proxies resolve the contextual
instance only once. Thus you get the benefits of a Proxy (serializability,
interceptors, decorators, cycle prevention, shield against scope
differences) for the costs of (almost) native invocation (Creating
'underTest' via new instead of the CDI bean will run the test in 8ms).


OWB-1.5.0 is and/or will be bundled with TomEE+ 2.x 'and' future TomEE+
1.7.x releases?

@ApplicationScoped? interesting, I can remember you sending a
recommendation (to me via this list) about caching data in my app, and I
did that in my (CDI) @ApplicationScoped bean. Thanks Mark! :)



On Tue, Oct 21, 2014 at 5:37 AM, Mark Struberg  wrote:

> Hi!
>
> Yesterday I wrote a small micro benchmark to test the performance of some
> CDI containers. The outcome was pretty stunning - but best if you run it
> yourself:
>
> https://github.com/struberg/cdi-performance
>
>
>
> $> git clone https://github.com/struberg/cdi-performance.git
> $> cd cdi-performance
>
> Just look for the output:ALL THE STUFF TOOK: xxx ms
>
>
>
>
> The default profile runs with owb-1.2.6 which is currently used in
> TomEE-1.7.1:
>
> $> mvn clean install
>
> If you have OWB trunk installed you can also try the performance of
> OWB-1.5.0-SNAPSHOT:
> $> mvn clean install -POWB15
>
>
> There is also a profile -POWB11 for testing OpenWebBeans-1.1.x.
> $> mvn clean install -POWB11 -Dowb.version=1.1.8
>
>
> The numbers of the Reference Implementation (RI: Weld) can be tested via
> $> mvn clean install -PWeld
>
> but take your time and let it run - no it doesn't hang ;)
>
>
>
> The version of OWB can be defined as parameter '-Dowb.version=1.2.0' and
> similar for Weld: '-Dweld.version=2.2.5.Final' if you like to test the
> latest RI version.
>
>
> Feel free to debug into it if you don't believe our sheer crazy
> performance!
>
> As a result of this performance I was able to serve FAT applications with
> BIG pages (huge JSF datatables) within under 150ms where other EE
> containers took 2 seconds++...
>
>
>
> LieGrue,
> strub
>

Re: TomEE JavaMail problems

[Howard W. Smith, Jr.]

On Sun, Oct 19, 2014 at 7:56 AM, Romain Manni-Bucau 
wrote:

> 2014-10-19 13:51 GMT+02:00 Howard W. Smith, Jr. :
> > On Sun, Oct 19, 2014 at 7:46 AM, Romain Manni-Bucau <
> rmannibu...@gmail.com>
> > wrote:
> >
> >> 2014-10-19 13:44 GMT+02:00 Howard W. Smith, Jr.  >:
> >> > You did the right thing. For years, I have been posting to this list
> >> about
> >> > my issues with geronimo javamail (which is shipped/bundled with
> tomee+)
> >> and
> >> > the workaround is to remove-and-replace geronimo javamail JAR with
> >> (Oracle)
> >> > JavaMail JAR.
> >> >
> >>
> >> Guys please help us to resolve it, we have many users (and us as well
> >> ;)) not having issues to we need you to dig into it.
> >>
> >>
> > I think I created a bug against geronimo javamail when I started using
> > TomEE. I don't know if that bug was resolved yet or not.
> >
>
> As said the bug is linked to your environment so we can't work on it
> if you don't help :(
>
>
https://issues.apache.org/jira/browse/GERONIMO-6421

Re: TomEE JavaMail problems

[Howard W. Smith, Jr.]

On Sun, Oct 19, 2014 at 7:46 AM, Romain Manni-Bucau 
wrote:

> 2014-10-19 13:44 GMT+02:00 Howard W. Smith, Jr. :
> > You did the right thing. For years, I have been posting to this list
> about
> > my issues with geronimo javamail (which is shipped/bundled with tomee+)
> and
> > the workaround is to remove-and-replace geronimo javamail JAR with
> (Oracle)
> > JavaMail JAR.
> >
>
> Guys please help us to resolve it, we have many users (and us as well
> ;)) not having issues to we need you to dig into it.
>
>
I think I created a bug against geronimo javamail when I started using
TomEE. I don't know if that bug was resolved yet or not.


> > Now, my endusers don't like the few seconds wait/delay that it takes to
> > sendMail via (Oracle) JavaMail, so I am using MessageDrivenBean via
> Apache
> > MQ (bundled with TomEE+) to send the mail after user click Send Mail
> button
> > in webapp.
> >
>
> @Asynchronous instead of a JMS MDB looks more appropriated ;)
>
>
you tell me that all the time, thanks for the reminder. BIG :D

Re: TomEE JavaMail problems

[Howard W. Smith, Jr.]

You did the right thing. For years, I have been posting to this list about
my issues with geronimo javamail (which is shipped/bundled with tomee+) and
the workaround is to remove-and-replace geronimo javamail JAR with (Oracle)
JavaMail JAR.

Now, my endusers don't like the few seconds wait/delay that it takes to
sendMail via (Oracle) JavaMail, so I am using MessageDrivenBean via Apache
MQ (bundled with TomEE+) to send the mail after user click Send Mail button
in webapp.


On Sat, Oct 18, 2014 at 9:59 PM, iluvtr  wrote:

> I use a Tomcat 7, recently I considered to use TomEE in order to get full
> power of Java EE without all that plumbing that comes with plain Tomcat.
>
> The bad news came with email sending, because compared it was taking a
> long,
> long time compared with plain Tomcat with Oracle JavaMail.
>
> Sending email with TomEE: 116393 ms
> Sending email with Tomcat 7: 4557 ms
>
> I thought it was a bug and filed here
> https://issues.apache.org/jira/browse/TOMEE-1413, but TomEE team couldn't
> reproduce the failure and told me that maybe it was some network problem.
>
> I have disabled antivirus, firewall, everything, and tested in two
> different
> computers one in my home and other in my work, but still having that
> problem,
> This problem doesn't occur in plain Tomcat 7, I even tested the same code
> in
> Glassfish 3.1 and works pretty well there.
>
> Recently I replaced Geronimo JavaMail with Oracle JavaMail and all my
> problems went away, so I think that this problem has something to do with
> Geronimo implementation
>
> I added geronimo-osgi-locator-1.1.jar to TOMEE/lib
> I removed geronimo-javamail_1.4_mail-1.8.3.jar in TOMEE/lib
> I added mail.jar (Oracle JavaMail)
>
>
> What do you think: Is the change I made will affect badly TomEE ?
> Thank you so much
>
>
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-JavaMail-problems-tp4672429.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>

Re: Apache TomEE 1.7.0 Release

[Howard W. Smith, Jr.]

Okay, here it is, Andy/Romain. tomee 1.7.0 release stated the following;
so, I did read/remember it wrong. :)

On Fri, Aug 15, 2014 at 8:58 AM, Andy Gumbrecht 
wrote:

> Core development will now move to the TomEE 2.x EE7 binaries, but the
> 1.7.x branch will also be a active for the foreseeable future.

Re: TomEE 1.7.2 + Tomcat 7.0.56?

[Howard W. Smith, Jr.]

I thought the tomee 1.7.1 release email said that this is the last 1.7.x
release and focus is on tomee 2.x,now. I might have read that wrong though.
:-)
 On Oct 14, 2014 9:59 AM, "Andy Gumbrecht"  wrote:

> Hi Howard,
>
> What gave you the impression that there would be no more 1.7.x releases?
> Only asking in case it is/was something on the site or release notes that
> needs adjusting.
>
> Andy.
>
> On 14/10/2014 01:27, Howard W. Smith, Jr. wrote:
>
>> That's great to hear. I thought that there would be no more tomee 1.7.x
>> releases, but it's good that future tomee 1.7.x is released after tomcat
>> 7.x future releases. :)
>>
>>
>> On Mon, Oct 13, 2014 at 8:24 AM, Andy Gumbrecht  wrote:
>>
>>  For sure,
>>>
>>> It is the plan that TomEE 1.7.x always stays in line with Tomcat 7.x, and
>>> TomEE 2.x with Tomcat 8.x.
>>>
>>> Andy.
>>>
>>>
>>> On 13/10/2014 13:32, Felipe Jaekel wrote:
>>>
>>>  Hi,
>>>>
>>>> I noticed some interesting fixes in Tomcat 7.0.56 changelog.
>>>>
>>>> I'm not familiar with the TomEE versioning system, so I'd like to ask if
>>>> 1.7.2 is going to ship Tomcat 7.0.56.
>>>>
>>>> Thanks
>>>>
>>>>
>>>>
>

Re: TomEE 1.7.2 + Tomcat 7.0.56?

[Howard W. Smith, Jr.]

That's great to hear. I thought that there would be no more tomee 1.7.x
releases, but it's good that future tomee 1.7.x is released after tomcat
7.x future releases. :)


On Mon, Oct 13, 2014 at 8:24 AM, Andy Gumbrecht  wrote:

> For sure,
>
> It is the plan that TomEE 1.7.x always stays in line with Tomcat 7.x, and
> TomEE 2.x with Tomcat 8.x.
>
> Andy.
>
>
> On 13/10/2014 13:32, Felipe Jaekel wrote:
>
>> Hi,
>>
>> I noticed some interesting fixes in Tomcat 7.0.56 changelog.
>>
>> I'm not familiar with the TomEE versioning system, so I'd like to ask if
>> 1.7.2 is going to ship Tomcat 7.0.56.
>>
>> Thanks
>>
>>
>

Re: Regarding @Inject vs @EJB for EJB

[Howard W. Smith, Jr.]

Yes, I remember when I became TomEE user, I think Romain advised me that I
can use @Inject or @EJB. I decided to only use @EJB for EJBs and @Inject
for @SessionScoped, @ApplicationScoped, @RequestScoped beans.


On Fri, Oct 3, 2014 at 10:49 AM,  wrote:

> Hi,
> I am not sure about that Alex. I use @Inject only and Stateless and stuff
> is  working fine
>
> Skickat från min iPhone
>
> > 3 okt 2014 kl. 15:30 skrev Alex Soto :
> >
> > Well I don't know exactly how EJB and CDI is managed internally by TomEE.
> > But using @Inject whatever the class is will mean that the lifecycle of
> > that instance will be managed by CDI container. On the other side if you
> > use @EJB the bean will be managed by EJB container, and this means EJB
> > lifecycle, and of course that your bean wil be transactional and you will
> > be able to apply security concerns.
> >
> > Note that @Inject will make your bean be treated as POJO meanwhile @EJB
> > will mean that your bean will be treated as Enterprise Java Bean.
> >
> > As I said I am not 100% sure but I think this is how it works.
> >
> > 2014-10-03 14:19 GMT+02:00 Lars-Fredrik Smedberg :
> >
> >> Hi!
> >>
> >> I'm trying to understand how I can use @Inject to inject EJBs.
> >>
> >> 1. If I want to inject an EJB that is packaged in the WAR together with
> the
> >> code trying to inject it i assume I can use @Inject, correct?
> >> 2. As 1 but the EJB is packaged in a separate ejb-jar. I assume I can
> still
> >> use @Inject correct?
> >> 3. If the EJB is packaged in another WAR inside the same EAR or in
> another
> >> EAR I need to use @EJB correct?
> >> 4. In case 3 how do I adress the EJB? Where can I read more about the
> >> naming standard?
> >>
> >> Regards
> >> LF
> >>
> >> --
> >> Med vänlig hälsning / Best regards
> >>
> >> Lars-Fredrik Smedberg
> >>
> >> STATEMENT OF CONFIDENTIALITY:
> >> The information contained in this electronic message and any
> >> attachments to this message are intended for the exclusive use of the
> >> address(es) and may contain confidential or privileged information. If
> >> you are not the intended recipient, please notify Lars-Fredrik Smedberg
> >> immediately at itsme...@gmail.com, and destroy all copies of this
> >> message and any attachments.
> >>
> >
> >
> >
> > --
> > +--+
> >  Alex Soto Bueno - Computer Engineer
> >  www.lordofthejars.com
> > +--+
>

Re: Apache TomEE 1.7.1 Released!

[Howard W. Smith, Jr.]

Andy/Romain,

is the following still required with this TomEE 1.7.1 release (which was a
bug/regression introduced in the tomEE 1.7.0 release)?


TomEE 1.7.0 Release: xbean error caused by NoClassDefFoundError:
org/apache/geronimo/osgi/locator/ProviderLocator

On Fri, Aug 15, 2014 at 1:46 PM, Romain Manni-Bucau 
 wrote:

> Just replace geronimo javamail by
>
> http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-osgi-locator/1.1/geronimo-osgi-locator-1.1.jar
> and maybe
> http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-osgi-registry/1.1/geronimo-osgi-registry-1.1.jar
> + mail.jar you want
>




On Wed, Sep 17, 2014 at 11:29 AM, Andy Gumbrecht 
wrote:

> Hi everyone,
>
> Pushing this out on the mailing lists to make sure everyone gets the
> message. Please promote by Tweet, Google+, Facebook and any other social
> media you use. In fact, please get back to me with suggestions on any other
> promotion channels you think we should be using to reach out on?
>
> After the huge buzz getting version 1.7.0 off the press it is time to get
> back to the day to day. As promised we are committed to providing the best
> for our community, and so without further a do here is TomEE 1.7.1 - This
> is a maintenance release that fixes some minor issues and a few tweaks (We
> understand it is not so minor if you are waiting for it, so thanks for your
> patience). This version is still shipped upon Apache Tomcat 7.0.55
>
> Please note that the TomEE 1.7.1 drop in WAR file will not work on Apache
> Tomcat 8. If you are interested in a Tomcat 8.x version then please feel
> free to check out and contribute to the developer branch <
> http://tomee.apache.org/contribute.html> - We are always interested in
> any help from the community that we can get.
>
> The Apache TomEE 1.7.1 release files can be downloaded from here:
>
> http://tomee.apache.org/downloads.html
>
> Note: Issue TOMEE-1339 
> introduced a default (but configurable) check for a static /index.html/
> file when an empty JAX-RS resource URL is specified by a client. You can
> use this file to return a descriptive response to the client for example.
> Make sure that this optional file does not contain sensitive information
> when made available. Currently it is not a JSP and it is not parsed in any
> way by the Servlet container - This may change in the next version.
>
> Simply update your existing Maven JavaEE-API, OpenEJB and or TomEE pom.xml
> entries to point to the latest versions.
>
> Andy.
>
> --
>   Andy Gumbrecht
>   https://twitter.com/AndyGeeDe
>   http://www.tomitribe.com
>
>

Re: Does anyone uses atmosphere-runtime in production?

[Howard W. Smith, Jr.]

On Fri, Sep 5, 2014 at 3:05 PM, Felipe Jaekel  wrote:

> I thought so too, but it doesn't. From what I read today in the atmosphere
> group, the native runtime is only required for "old" non-standard
> websockets implementations, so I'll give atmosphere-runtime another try.
>

okay/interesting.


>
> I think the server crash happened because the PrimeFaces socket
> component doesn't validates the user browser, and I had a lot of clients
> with
> old IE. Currently I only render the socket component with the client
> browser supports websocket.
>

okay/interesting.


>
> Could you share your PrimeFaces socket component configuration?
>






userPushChannelId = sessionId (see code below)

FacesContext facesContext = FacesContext.getCurrentInstance();
HttpSession httpSession = (HttpSession)
facesContext.getExternalContext().getSession(false);
String sessionId;
if (httpSession != null) {
sessionId = user.getUserName() + httpSession.getId();
}
else {
sessionId = user.getUserName() +
new
DateTime(user.getLastLoginDt()).toString("MMddhhmmssa");
}
logger.info("sessionId = " + sessionId);


NotifyResource.java (as required by PrimeFaces 5.0 Push, and sample code
provided by PrimeFaces Push - Notify example in showcase and user guide)

package pf;

import javax.faces.application.FacesMessage;
import org.primefaces.push.annotation.OnMessage;
import org.primefaces.push.annotation.PushEndpoint;
import org.primefaces.push.annotation.Singleton;
import org.primefaces.push.impl.JSONEncoder;

@PushEndpoint("/{usernameAndSessionId}")
@Singleton
public class NotifyResource {

@OnMessage(encoders = {JSONEncoder.class})
public FacesMessage onMessage(FacesMessage message) {
return message;
}

}


again, my web.xml is as follows:



Push Servlet
org.primefaces.push.PushServlet
1


org.atmosphere.cpr.broadcasterCacheClass

org.atmosphere.cache.UUIDBroadcasterCache

true


Push Servlet
/primepush/*



FYI, my webapp only targets Google Chrome browser on Windows desktops, iPad
and Android devices.

Re: Problem with NoClassDefFoundError: CometProcessor

[Howard W. Smith, Jr.]

Felipe, can you please share why you are using tomee + atmosphere runtime
native + (tomcat7 native) comet?

does your app require comet, because some of your enduser browsers require
comet and do not support websocket?

tomee/tomcat7 + atmosphere runtime + websocket works great



On Thu, Sep 4, 2014 at 1:27 PM, Felipe Jaekel  wrote:

> Hi,
>
> I'm trying to run an existing application in TomEE plus 1.7.0. It uses
> atmosphere runtime native 2.1.8.
>
> Unless I copy atmosphere JARs to TomEE lib folder, I get
> a java.lang.NoClassDefFoundError: org/apache/catalina/CometProcessor.
>
> The same application run fine in a regular Tomcat 7.0.55 packing atmosphere
> JARs in WEB-INF/lib(compat jars pulled by maven).
>
> Any ideas?
>
> Thanks
>

Re: Does anyone uses atmosphere-runtime in production?

[Howard W. Smith, Jr.]

see my responses inline, below.


On Thu, Sep 4, 2014 at 12:59 PM, Felipe Jaekel  wrote:

> Tomcat 7 was throwing illegal state exceptions everywhere, even in the
> manager application, so it was impossible to use the server. In that case
> atmosphere-runtime.jar was packed in WEB-INF/lib, and removing the
> application with it from the server immediately solved the problem.
>

hmmm, what do you mean, when you say that it was impossible to use the
server? server == tomcat7 or tomee 1.x?

what do you mean when you say, removing the application with it from the
server immediately solved the problem?

application = WAR that includes primefaces + atmosphere-runtime JAR ?

server = tomcat7 or tomee 1.x ?


>
> With atmosphere-runtime-native I didn't have this issue, but now I want to
> migrate my applications from PrimeFaces 4 to 5 and it doesn't works with
> atmosphere-runtime-native.
>

i think you were running atmosphere-runtime-native and primefaces 4 with
tomcat7 (and not tomee 1.x), right?


>
> I remember you helped me in PrimeFaces and Atmosphere forum. Since I still
> haven't found a solution for PrimeFaces 5 + atmosphere-runtime-native, I'm
> thinking about trying atmosphere-runtime again, but as the issue I
> mentioned only happens in production, I'd like to see first if anyone else
> is using it successfully.
>

i would assume that primefaces 5 + atmosphere-runtime-native will work,
if/since primefaces 4 + atmosphere-runtime-native + your server/app config.

i have been using primefaces 4 and 5 + atmosphere-runtime JAR + tomee
1.5.1, 1.6.x, and 1.7.0. I include atmosphere-runtime JAR in my WAR file,
and I do not use atmosphere-compat JARs, and I use websocket instead of
COMET.


>
> Can you share your connector configuration from server.xml? Currently I'm
> using this:
>
> 
> compressableMimeType="text/html,text/xml,text/css,text/javascript,application/x-javascript,application/javascript"
>  compression="on"
> connectionTimeout="2"
> port="8080"
>  protocol="org.apache.coyote.http11.Http11NioProtocol"
> redirectPort="8443" />
>
>
below, is my  in server.xml,




and my web.xml has the following:



Push Servlet
org.primefaces.push.PushServlet
1


org.atmosphere.cpr.broadcasterCacheClass

org.atmosphere.cache.UUIDBroadcasterCache

true


Push Servlet
/primepush/*




> Thanks
>
>
> 2014-09-03 16:59 GMT-03:00 Howard W. Smith, Jr. :
>
> > I use it, since I am using PrimeFaces Push in my web app.
> >
> > what problems are you having? how are you deploying and/or packaging
> > atmosphere-runtime?
> >
> >
> >
> > On Wed, Sep 3, 2014 at 3:16 PM, Felipe Jaekel 
> wrote:
> >
> > > Hi,
> > >
> > > Does anyone uses atmosphere-runtime in production with TomEE plus
> 1.7.0?
> > I
> > > had some problems when I tried it in a regular Tomcat 7 some time ago.
> > >
> > > Thanks
> > >
> >
>

Re: TomEE 1.6.0 + MyFaces 2.2.0 + javax.faces.view.ViewScoped

[Howard W. Smith, Jr.]

Tomee 1.7 comes bundled with MyFaces 2.1.5 in tomee/lib. I usually replace
those jars with MyFaces 2.2 jars. Are you doing the same? Do you have
MyFaces in ear and tomee/lib?
 On Sep 4, 2014 10:31 AM, "José Luis Cetina"  wrote:

> @Romain any suggestions?
>
>
> 2014-09-03 23:59 GMT-05:00 Romain Manni-Bucau :
>
> > Surely right if mf is in the ear and not the war but not a bug neither
> > Le 3 sept. 2014 22:16, "José Luis Cetina"  a
> écrit :
> >
> > > This was the Last response from Leonardo:
> > >
> > > Hi
> > >
> > > It looks like something not directly related to MyFaces, it is like if
> > > the classpath is scanned twice, or like the bean is subscribed twice.
> > > I suppose it is a bug in OWB or in TomEE. Maybe you should report it
> > > in:
> > >
> > > https://issues.apache.org/jira/browse/TOMEE
> > >
> > > regards,
> > >
> > > Leonardo Uribe
> > >
> > > 2014/1/15 José Luis Cetina :
> > >  El 03/09/2014 15:55, "Howard W. Smith, Jr." 
> > > escribió:
> > >
> > > > Does Leonardo follow this list when people discuss MyFaces (2.2)? I
> > think
> > > > Mark Struberg monitors this list when MyFaces is discussed here.
> > > >
> > > > José, it will definitely be good to post this issue on the myfaces
> user
> > > > list.
> > > >
> > > >
> > > >
> > > >
> > > > On Wed, Sep 3, 2014 at 4:50 PM, Romain Manni-Bucau <
> > > rmannibu...@gmail.com>
> > > > wrote:
> > > >
> > > > > think so but more a MF issue this time I think
> > > > >
> > > > >
> > > > > Romain Manni-Bucau
> > > > > Twitter: @rmannibucau
> > > > > Blog: http://rmannibucau.wordpress.com/
> > > > > LinkedIn: http://fr.linkedin.com/in/rmannibucau
> > > > > Github: https://github.com/rmannibucau
> > > > >
> > > > >
> > > > > 2014-09-03 22:27 GMT+02:00 José Luis Cetina  >:
> > > > > > Hi, i was trying to use MyFaces 2.2.4 with TomEE 1.7.0 JAX-RS,
> > > > > > finally i remove all CODI sttuf from my webapp, i want to use
> > myfaces
> > > > > 2.2.4
> > > > > > because i want to use the @javax.faces.view.ViewScoped (i use the
> > > > > omnifaces
> > > > > > viewscoped) and the f:viewAction.
> > > > > >
> > > > > > But again im getting
> > > > > javax.enterprise.inject.AmbiguousResolutionException:
> > > > > > Ambiguous resolution exception that i reported a few months ago,
> > > > > apparently
> > > > > > myfaces 2.2.4 is not working with ears in tomee 1.7.0
> > > > > >
> > > > > >
> > > > > >
> > > > > > 2014-01-15 21:54 GMT-06:00 Howard W. Smith, Jr. <
> > > > smithh032...@gmail.com
> > > > > >:
> > > > > >
> > > > > >> Is it working for you, now?
> > > > > >> On Jan 15, 2014 6:00 PM, "José Luis Cetina" <
> maxtorz...@gmail.com
> > >
> > > > > wrote:
> > > > > >>
> > > > > >> > I will try right now
> > > > > >> >
> > > > > >> >
> > > > > >> > 2014/1/15 Romain Manni-Bucau 
> > > > > >> >
> > > > > >> > > Hi
> > > > > >> > >
> > > > > >> > > Fo you get it on trunk as well?
> > > > > >> > >
> > > > > >> > > Le mercredi 15 janvier 2014, José Luis Cetina <
> > > > maxtorz...@gmail.com>
> > > > > a
> > > > > >> > > écrit :
> > > > > >> > > > Hi. I use TomEE 1.6.0 Final release with myfaces 2.1.13
> and
> > > jdk
> > > > > 1.7
> > > > > >> > with
> > > > > >> > > > this i was using the org.omnifaces.cdi.ViewScoped
> annotation
> > > > with
> > > > > any
> > > > > >> > > > problem, with the new release of myfaces 2.2.0 i decide to
> > > > change
> > > > > >> > > > from org.omnifaces.cdi.ViewScoped to
> > > javax.faces.view.ViewScoped
> >

Re: TomEE 1.6.0 + MyFaces 2.2.0 + javax.faces.view.ViewScoped

[Howard W. Smith, Jr.]

Does Leonardo follow this list when people discuss MyFaces (2.2)? I think
Mark Struberg monitors this list when MyFaces is discussed here.

José, it will definitely be good to post this issue on the myfaces user
list.




On Wed, Sep 3, 2014 at 4:50 PM, Romain Manni-Bucau 
wrote:

> think so but more a MF issue this time I think
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-09-03 22:27 GMT+02:00 José Luis Cetina :
> > Hi, i was trying to use MyFaces 2.2.4 with TomEE 1.7.0 JAX-RS,
> > finally i remove all CODI sttuf from my webapp, i want to use myfaces
> 2.2.4
> > because i want to use the @javax.faces.view.ViewScoped (i use the
> omnifaces
> > viewscoped) and the f:viewAction.
> >
> > But again im getting
> javax.enterprise.inject.AmbiguousResolutionException:
> > Ambiguous resolution exception that i reported a few months ago,
> apparently
> > myfaces 2.2.4 is not working with ears in tomee 1.7.0
> >
> >
> >
> > 2014-01-15 21:54 GMT-06:00 Howard W. Smith, Jr.  >:
> >
> >> Is it working for you, now?
> >> On Jan 15, 2014 6:00 PM, "José Luis Cetina" 
> wrote:
> >>
> >> > I will try right now
> >> >
> >> >
> >> > 2014/1/15 Romain Manni-Bucau 
> >> >
> >> > > Hi
> >> > >
> >> > > Fo you get it on trunk as well?
> >> > >
> >> > > Le mercredi 15 janvier 2014, José Luis Cetina 
> a
> >> > > écrit :
> >> > > > Hi. I use TomEE 1.6.0 Final release with myfaces 2.1.13 and jdk
> 1.7
> >> > with
> >> > > > this i was using the org.omnifaces.cdi.ViewScoped annotation with
> any
> >> > > > problem, with the new release of myfaces 2.2.0 i decide to change
> >> > > > from org.omnifaces.cdi.ViewScoped to javax.faces.view.ViewScoped
> then
> >> > im
> >> > > > gettin this AmbiguousResolutionException.
> >> > > >
> >> > > >
> >> > > > This error only happend in Linux environment, if i run the same
> >> project
> >> > > in
> >> > > > Windows this error never appears.
> >> > > >
> >> > > >
> >> > > > I removed my faces 2.1.13 jars (api and imp) from tomee lib and
> add
> >> > > myfaces
> >> > > > api and impl 2.2.0
> >> > > >
> >> > > >
> >> > > > What could be wrong?
> >> > > >
> >> > > > Log:
> >> > > >
> >> > > > javax.enterprise.inject.AmbiguousResolutionException: Ambiguous
> >> > > resolution
> >> > > > found beans:
> >> > > > ViewScopeBeanHolder, Name:null, WebBeans Type:MANAGED, API
> >> > > >
> >> > >
> >> > >
> >> >
> >>
> Types:[java.io.Serializable,java.lang.Object,org.apache.myfaces.cdi.view.ViewScopeBeanHolder],
> >> > > >
> >> >
> Qualifiers:[javax.enterprise.inject.Any,javax.enterprise.inject.Default]
> >> > > > from
> >> > >
> >> > >
> >> >
> >>
> jar:file:/home/broncos/apache/tomee/apache-tomee-jaxrs-1.6.0/lib/myfaces-impl-2.2.0.jar!/org/apache/myfaces/cdi/view/ViewScopeBeanHolder.class
> >> > > > ViewScopeBeanHolder, Name:null, WebBeans Type:MANAGED, API
> >> > > >
> >> > >
> >> > >
> >> >
> >>
> Types:[java.io.Serializable,java.lang.Object,org.apache.myfaces.cdi.view.ViewScopeBeanHolder],
> >> > > >
> >> >
> Qualifiers:[javax.enterprise.inject.Any,javax.enterprise.inject.Default]
> >> > > > from
> >> > >
> >> > >
> >> >
> >>
> jar:file:/home/broncos/apache/tomee/apache-tomee-jaxrs-1.6.0/lib/myfaces-impl-2.2.0.jar!/org/apache/myfaces/cdi/view/ViewScopeBeanHolder.class
> >> > > >
> >> > >
> >> > >
> >> >
> >>
> org.apache.webbeans.util.InjectionExceptionUtil.throwAmbiguousResolutionExceptionForBeans(InjectionExceptionUtil.java:104)
> >> > > >
> >> > >
> >> > >
> >> >
> >>
> org.apache.webbeans.uti

Re: Does anyone uses atmosphere-runtime in production?

[Howard W. Smith, Jr.]

I use it, since I am using PrimeFaces Push in my web app.

what problems are you having? how are you deploying and/or packaging
atmosphere-runtime?



On Wed, Sep 3, 2014 at 3:16 PM, Felipe Jaekel  wrote:

> Hi,
>
> Does anyone uses atmosphere-runtime in production with TomEE plus 1.7.0? I
> had some problems when I tried it in a regular Tomcat 7 some time ago.
>
> Thanks
>

Re: Upgrade myfaces version in Tomee 1.7.0

[Howard W. Smith, Jr.]

Also, you may want the non-PLUME release of TomEE(+) 1.7.0, and replace
myfaces 2.1.15 JARs with myfaces 2.2.4 (api/impl) JARs.

I think TomEE PLUME release may have config + jars to make it work
specifically for Mojarra users. Of course, non-PLUME release will not have
that config + jars. :)



On Thu, Aug 28, 2014 at 5:29 PM, Felipe Jaekel  wrote:

> TomEE works fine with MyFaces 2.2, just replace the 2.1 jar with it.
>
> One observation is that in my case when I changed from Mojarra 2.1 to
> MyFaces 2.1 I had to do some adjustments in my applications, and some more
> adjustments when I changed from MyFaces 2.1 to 2.2, so I would recommend
> you to test your whole application with MyFaces before deploying it in
> production.
>
>
> 2014-08-28 17:53 GMT-03:00 cocorossello :
>
> > Hi,
> >
> > I'm moving from glassfish 4.1 to tomEE 1.7.0. I started with PLUME for an
> > easier start, but now I want to use myfaces instead of mojarra (I've seen
> > some performance problems that might be my fault, but it improves a lot
> > with
> > myfaces).
> >
> > My question is if it's safe to just upgrade myfaces to last version
> (2.2.4)
> > or if I should stick with 2.1.x
> >
> > Thank you.
> >
> >
> >
> > --
> > View this message in context:
> >
> http://tomee-openejb.979440.n4.nabble.com/Upgrade-myfaces-version-in-Tomee-1-7-0-tp4671458.html
> > Sent from the TomEE Users mailing list archive at Nabble.com.
> >
>

Re: Best way to upgrade?

[Howard W. Smith, Jr.]

-- Forwarded message --
From: Romain Manni-Bucau 
Date: Fri, Aug 15, 2014 at 1:46 PM
Subject: Re: TomEE 1.7.0 Release: xbean error caused by
NoClassDefFoundError: org/apache/geronimo/osgi/locator/ProviderLocator
To: "users@tomee.apache.org" 


Just replace geronimo javamail by
http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-osgi-locator/1.1/geronimo-osgi-locator-1.1.jar
and maybe
http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-osgi-registry/1.1/geronimo-osgi-registry-1.1.jar
+ mail.jar you want


Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau


On Wed, Aug 27, 2014 at 11:45 AM, Howard W. Smith, Jr. <
smithh032...@gmail.com> wrote:

> Can you search google for
>
> tomee 1.7 Geronimo
>
> I initiated a discussion here on this list about it. Romain provided URL
> to download a jar to fix the issue.
>  On Aug 27, 2014 10:48 AM, "Felipe Jaekel"  wrote:
>
>> Thanks, I'll do that.
>>
>> How do you remove Geronimo JavaMail? Tried it in 1.7.0 plus to solve some
>> issues and the server don't start anymore:
>>
>> GRAVE: FATAL ERROR: Unknown error in Assembler.  Please send the following
>> stack trace and this message to us...@openejb.apache.org :
>>  org.apache.xbean.recipe.ConstructionException: Error invoking
>> constructor:
>> public org.apache.tomee.catalina.TomcatSecurityService()
>> at
>>
>> org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:968)
>>  at
>> org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:276)
>> at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96)
>>  at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61)
>> at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49)
>>  at
>>
>> org.apache.openejb.assembler.classic.Assembler.createSecurityService(Assembler.java:2517)
>> at
>>
>> org.apache.openejb.assembler.classic.Assembler.buildContainerSystem(Assembler.java:498)
>>  at
>> org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:420)
>> at org.apache.openejb.OpenEJB$Instance.(OpenEJB.java:150)
>>  at org.apache.openejb.OpenEJB.init(OpenEJB.java:298)
>> at
>> org.apache.tomee.catalina.TomcatLoader.initialize(TomcatLoader.java:253)
>>  at
>> org.apache.tomee.catalina.ServerListener.install(ServerListener.java:168)
>> at
>>
>> org.apache.tomee.catalina.ServerListener.lifecycleEvent(ServerListener.java:55)
>>  at
>>
>> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
>> at
>>
>> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
>>  at
>>
>> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402)
>> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:110)
>>  at org.apache.catalina.startup.Catalina.load(Catalina.java:638)
>> at org.apache.catalina.startup.Catalina.load(Catalina.java:663)
>>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> 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:280)
>> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:454)
>> Caused by: java.lang.NoClassDefFoundError:
>> org/apache/geronimo/osgi/locator/ProviderLocator
>> at
>>
>> javax.security.jacc.PolicyConfigurationFactory$1.run(PolicyConfigurationFactory.java:89)
>>  at java.security.AccessController.doPrivileged(Native Method)
>> at
>>
>> javax.security.jacc.PolicyConfigurationFactory.getPolicyConfigurationFactory(PolicyConfigurationFactory.java:80)
>>  at
>>
>> org.apache.openejb.core.security.AbstractSecurityService.installJacc(AbstractSecurityService.java:314)
>> at
>>
>> org.apache.openejb.core.security.AbstractSecurityService.(AbstractSecurityService.java:77)
>>  at
>>
>> org.apache.openejb.core.security.AbstractSecurityService.(AbstractSecurityService.java:71)
>> at
>>
>> org.apache.tomee.catalina.TomcatSecurityService.(TomcatSecurityService.java:51)
>>  at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>> at
>>
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(Native

Re: Best way to upgrade?

[Howard W. Smith, Jr.]

Can you search google for

tomee 1.7 Geronimo

I initiated a discussion here on this list about it. Romain provided URL to
download a jar to fix the issue.
 On Aug 27, 2014 10:48 AM, "Felipe Jaekel"  wrote:

> Thanks, I'll do that.
>
> How do you remove Geronimo JavaMail? Tried it in 1.7.0 plus to solve some
> issues and the server don't start anymore:
>
> GRAVE: FATAL ERROR: Unknown error in Assembler.  Please send the following
> stack trace and this message to us...@openejb.apache.org :
>  org.apache.xbean.recipe.ConstructionException: Error invoking constructor:
> public org.apache.tomee.catalina.TomcatSecurityService()
> at
>
> org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:968)
>  at
> org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:276)
> at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96)
>  at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61)
> at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49)
>  at
>
> org.apache.openejb.assembler.classic.Assembler.createSecurityService(Assembler.java:2517)
> at
>
> org.apache.openejb.assembler.classic.Assembler.buildContainerSystem(Assembler.java:498)
>  at
> org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:420)
> at org.apache.openejb.OpenEJB$Instance.(OpenEJB.java:150)
>  at org.apache.openejb.OpenEJB.init(OpenEJB.java:298)
> at org.apache.tomee.catalina.TomcatLoader.initialize(TomcatLoader.java:253)
>  at
> org.apache.tomee.catalina.ServerListener.install(ServerListener.java:168)
> at
>
> org.apache.tomee.catalina.ServerListener.lifecycleEvent(ServerListener.java:55)
>  at
>
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
> at
>
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
>  at
>
> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402)
> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:110)
>  at org.apache.catalina.startup.Catalina.load(Catalina.java:638)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:663)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 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:280)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:454)
> Caused by: java.lang.NoClassDefFoundError:
> org/apache/geronimo/osgi/locator/ProviderLocator
> at
>
> javax.security.jacc.PolicyConfigurationFactory$1.run(PolicyConfigurationFactory.java:89)
>  at java.security.AccessController.doPrivileged(Native Method)
> at
>
> javax.security.jacc.PolicyConfigurationFactory.getPolicyConfigurationFactory(PolicyConfigurationFactory.java:80)
>  at
>
> org.apache.openejb.core.security.AbstractSecurityService.installJacc(AbstractSecurityService.java:314)
> at
>
> org.apache.openejb.core.security.AbstractSecurityService.(AbstractSecurityService.java:77)
>  at
>
> org.apache.openejb.core.security.AbstractSecurityService.(AbstractSecurityService.java:71)
> at
>
> org.apache.tomee.catalina.TomcatSecurityService.(TomcatSecurityService.java:51)
>  at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 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
>
> org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:958)
> ... 24 more
> Caused by: java.lang.ClassNotFoundException:
> org.apache.geronimo.osgi.locator.ProviderLocator
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
>  at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
>  at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
>  at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> ... 36 more
>
>
>
> 2014-08-27 11:15 GMT-03:00 Howard W. Smith, Jr. :
>
> > I would never do that. I take tomee zip file, unzip to folder, and add
> jars
> > needed by my app like JUEL, jodatime latest version, JavaMail, Derby,
> > EclipseLink, and MyFaces 2.2.x. I also add my tomee/conf files.
> >
> > 

Re: Best way to upgrade?

[Howard W. Smith, Jr.]

I would never do that. I take tomee zip file, unzip to folder, and add jars
needed by my app like JUEL, jodatime latest version, JavaMail, Derby,
EclipseLink, and MyFaces 2.2.x. I also add my tomee/conf files.

And I remove Geronimo JavaMail, jodatime 1.6.2 jars.
 On Aug 26, 2014 4:34 PM, "Felipe Jaekel"  wrote:

> Thanks, but I mean that if I copy TomEE 1.7.0 libraries to the current
> 1.6.0.2 installation, will I need to delete older versions like MyFaces
> 2.1.13 and ActiveMQ 5.9.1?
>
>
> 2014-08-22 15:00 GMT-03:00 Howard W. Smith, Jr. :
>
> > I'm the type of TomEE user that just
> >
> > - drops WAR in tomee/webapps
> > - drop a few libraries in tomee/lib
> >
> > All of the files that I drop in tomee/webapps and tomee/lib can be used
> in
> > tomee+ 1.6.0.2 and 1.7.0.
> >
> > i really think the libraries that you are currently deploying to tomee
> > 1.6.0.2 can/will work with tomee 1.7.0, too, but it may be best for you
> to
> > try it, test it, reply with stacktrace if anything occurs, and/or share
> > your library/dependencies list, and/or pom.
> >
> >
> >
> > On Fri, Aug 22, 2014 at 1:47 PM, Felipe Jaekel 
> wrote:
> >
> > > What about older versions of libraries, do I need to delete them?
> > >
> > > I still haven't tested my applications on TomEE 1.7.0. I'm trying to
> get
> > > familiar with the upgrade process first.
> > >
> > >
> > > 2014-08-22 11:40 GMT-03:00 Romain Manni-Bucau :
> > >
> > > > Hi
> > > >
> > > > tomcat tool should be enough regarding configuration syntax.
> > > >
> > > >
> > > > Romain Manni-Bucau
> > > > Twitter: @rmannibucau
> > > > Blog: http://rmannibucau.wordpress.com/
> > > > LinkedIn: http://fr.linkedin.com/in/rmannibucau
> > > > Github: https://github.com/rmannibucau
> > > >
> > > >
> > > > 2014-08-22 16:37 GMT+02:00 Felipe Jaekel :
> > > > > In Tomcat I used to check the file differences here
> > > > > <http://tomcat.apache.org/migration-7.html#Upgrading_7.0.x> and
> > > override
> > > > > the JAR files.
> > > > >
> > > > > I recently started to use TomEE Plus 1.6.0.2, and now I'd like to
> > > upgrade
> > > > > it to 1.7.0.
> > > > >
> > > > > What would be the best way to do it?
> > > > >
> > > > > Thanks
> > > >
> > >
> >
>

Re: Apache TomEE web server does not allow generation of Primefaces pages from Entity Classes

[Howard W. Smith, Jr.]

Okay, Romain. Open source. NetBeans can reuse tomee code that detects and
reports tomcat tomee version at (NetBeans) runtime, too.
 On Aug 27, 2014 7:51 AM, "Romain Manni-Bucau" 
wrote:

> @Howard: netbeans can't rely on startup since it needs available libs
> for development + we change this version at runtime.
>
> but maven metadata are reliable
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-08-27 13:42 GMT+02:00 Howard W. Smith, Jr. :
> > Kay, atmosphere library had a fix for detecting tomcat and tomee
> versions.
> > Romain may remember that discussion. Add atmosphere runtime dependency to
> > your app, start tomee and look for tomee tomcat version in a one line
> > string in atmosphere log lines in log file.
> > On Aug 27, 2014 5:06 AM, "Kay Wrobel"  wrote:
> >
> >> Thanks, Romain.
> >>
> >> Kay
> >>
> >> On 08/27/2014 04:00 AM, Romain Manni-Bucau wrote:
> >>
> >>> FYI informations are in maven properties in jars so it is surely an
> >>> easier way to support coming version.
> >>>
> >>>
> >>>
> >>>
> >>> Romain Manni-Bucau
> >>> Twitter: @rmannibucau
> >>> Blog: http://rmannibucau.wordpress.com/
> >>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> >>> Github: https://github.com/rmannibucau
> >>>
> >>>
> >>> 2014-08-27 10:53 GMT+02:00 Kay Wrobel :
> >>>
> >>>> Hi.
> >>>>
> >>>> I am the author of the PrimeFaces CRUD Generator dedicated plugin
> (a.k.a.
> >>>> nbpfcrudgen, not the one that's built into NetBeans since 8 but the
> one
> >>>> I'm
> >>>> hosting on SourceForge) and have been asked this question recently on
> >>>> Facebook. The problem is with NetBeans 8 and how it detects a proper
> >>>> TomEE
> >>>> version. Unfortunately, the team has hard-coded version strings in
> their
> >>>> source. They are looking for the tomee-common-x.x.x.jar and make a
> >>>> determination from that version. But they only test for 1.5.x and
> 1.6.x,
> >>>> not
> >>>> 1.7.x. I have filed a bug report with NetBeans here:
> >>>> https://netbeans.org/bugzilla/show_bug.cgi?id=246523
> >>>>
> >>>> As a workaround, and I know the TomEE team discourages this, you could
> >>>> rename the tomee-common-1.7.0.jar to tomee-common-1.6.0.jar and
> NetBeans
> >>>> will detect it properly. TomEE will not fail to start up in my
> >>>> experience.
> >>>> NetBeans has not yet acknowledged the bug report and no one is
> assigned
> >>>> to
> >>>> it.
> >>>>
> >>>> Try renaming that file and see what your experience is with it.
> >>>>
> >>>> Kay
> >>>>
> >>>>
> >>>> On 08/27/2014 03:43 AM, User57 wrote:
> >>>>
> >>>>> I am trying to generate PrimeFaces pages from Entity classes for a
> Java
> >>>>> EE
> >>>>> web project. My web server is Apache TomEE 1.7 and I'm using
> Netbeans 8
> >>>>> as
> >>>>> an IDE.
> >>>>>
> >>>>> When I run the wizard to generate the pages I get this error Cannot
> be
> >>>>> generated for Java EE 6 sources without server with complete  Java
> EE 6
> >>>>> Web
> >>>>> Profile support (at least EJB Lite support).
> >>>>>
> >>>>> Netbeans 8 supports TomEE and posts about this error say that it
> should
> >>>>> be
> >>>>> fixed with the release of the 8th version of Netbeans.
> >>>>>
> >>>>> What should I do to fix this problem ?
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> View this message in context:
> >>>>> http://tomee-openejb.979440.n4.nabble.com/Apache-TomEE-
> >>>>> web-server-does-not-allow-generation-of-Primefaces-
> >>>>> pages-from-Entity-Classes-tp4671397.html
> >>>>> Sent from the TomEE Users mailing list archive at Nabble.com.
> >>>>>
> >>>>
> >>>>
> >>
>

Re: Apache TomEE web server does not allow generation of Primefaces pages from Entity Classes

[Howard W. Smith, Jr.]

Kay, atmosphere library had a fix for detecting tomcat and tomee versions.
Romain may remember that discussion. Add atmosphere runtime dependency to
your app, start tomee and look for tomee tomcat version in a one line
string in atmosphere log lines in log file.
On Aug 27, 2014 5:06 AM, "Kay Wrobel"  wrote:

> Thanks, Romain.
>
> Kay
>
> On 08/27/2014 04:00 AM, Romain Manni-Bucau wrote:
>
>> FYI informations are in maven properties in jars so it is surely an
>> easier way to support coming version.
>>
>>
>>
>>
>> Romain Manni-Bucau
>> Twitter: @rmannibucau
>> Blog: http://rmannibucau.wordpress.com/
>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>> Github: https://github.com/rmannibucau
>>
>>
>> 2014-08-27 10:53 GMT+02:00 Kay Wrobel :
>>
>>> Hi.
>>>
>>> I am the author of the PrimeFaces CRUD Generator dedicated plugin (a.k.a.
>>> nbpfcrudgen, not the one that's built into NetBeans since 8 but the one
>>> I'm
>>> hosting on SourceForge) and have been asked this question recently on
>>> Facebook. The problem is with NetBeans 8 and how it detects a proper
>>> TomEE
>>> version. Unfortunately, the team has hard-coded version strings in their
>>> source. They are looking for the tomee-common-x.x.x.jar and make a
>>> determination from that version. But they only test for 1.5.x and 1.6.x,
>>> not
>>> 1.7.x. I have filed a bug report with NetBeans here:
>>> https://netbeans.org/bugzilla/show_bug.cgi?id=246523
>>>
>>> As a workaround, and I know the TomEE team discourages this, you could
>>> rename the tomee-common-1.7.0.jar to tomee-common-1.6.0.jar and NetBeans
>>> will detect it properly. TomEE will not fail to start up in my
>>> experience.
>>> NetBeans has not yet acknowledged the bug report and no one is assigned
>>> to
>>> it.
>>>
>>> Try renaming that file and see what your experience is with it.
>>>
>>> Kay
>>>
>>>
>>> On 08/27/2014 03:43 AM, User57 wrote:
>>>
 I am trying to generate PrimeFaces pages from Entity classes for a Java
 EE
 web project. My web server is Apache TomEE 1.7 and I'm using Netbeans 8
 as
 an IDE.

 When I run the wizard to generate the pages I get this error Cannot be
 generated for Java EE 6 sources without server with complete  Java EE 6
 Web
 Profile support (at least EJB Lite support).

 Netbeans 8 supports TomEE and posts about this error say that it should
 be
 fixed with the release of the 8th version of Netbeans.

 What should I do to fix this problem ?



 --
 View this message in context:
 http://tomee-openejb.979440.n4.nabble.com/Apache-TomEE-
 web-server-does-not-allow-generation-of-Primefaces-
 pages-from-Entity-Classes-tp4671397.html
 Sent from the TomEE Users mailing list archive at Nabble.com.

>>>
>>>
>

Re: Best way to upgrade?

[Howard W. Smith, Jr.]

I'm the type of TomEE user that just

- drops WAR in tomee/webapps
- drop a few libraries in tomee/lib

All of the files that I drop in tomee/webapps and tomee/lib can be used in
tomee+ 1.6.0.2 and 1.7.0.

i really think the libraries that you are currently deploying to tomee
1.6.0.2 can/will work with tomee 1.7.0, too, but it may be best for you to
try it, test it, reply with stacktrace if anything occurs, and/or share
your library/dependencies list, and/or pom.



On Fri, Aug 22, 2014 at 1:47 PM, Felipe Jaekel  wrote:

> What about older versions of libraries, do I need to delete them?
>
> I still haven't tested my applications on TomEE 1.7.0. I'm trying to get
> familiar with the upgrade process first.
>
>
> 2014-08-22 11:40 GMT-03:00 Romain Manni-Bucau :
>
> > Hi
> >
> > tomcat tool should be enough regarding configuration syntax.
> >
> >
> > Romain Manni-Bucau
> > Twitter: @rmannibucau
> > Blog: http://rmannibucau.wordpress.com/
> > LinkedIn: http://fr.linkedin.com/in/rmannibucau
> > Github: https://github.com/rmannibucau
> >
> >
> > 2014-08-22 16:37 GMT+02:00 Felipe Jaekel :
> > > In Tomcat I used to check the file differences here
> > >  and
> override
> > > the JAR files.
> > >
> > > I recently started to use TomEE Plus 1.6.0.2, and now I'd like to
> upgrade
> > > it to 1.7.0.
> > >
> > > What would be the best way to do it?
> > >
> > > Thanks
> >
>

Re: Best way to upgrade?

[Howard W. Smith, Jr.]

okay, my apologies. I think it is also good to keep an eye on the topics
posted on this mail list, because immediately after tomee+ 1.7.0 was
released, some of us posted our migration issues/concerns.



On Fri, Aug 22, 2014 at 10:50 AM, Howard W. Smith, Jr. <
smithh032...@gmail.com> wrote:

> Felipe, how often is your app(s) impacted by upgrading to latest version
> of tomcat7?
>
> if your app is never impacted by newer/newest version of tomcat7, 'and'
> since you have already migrated to TomEE+ 1.6.0.2, I don't think your app
> will be impacted when you migrate from TomEE+ 1.6.0.2 to 1.7.0.
>
>
>
> On Fri, Aug 22, 2014 at 10:37 AM, Felipe Jaekel 
> wrote:
>
>> In Tomcat I used to check the file differences here
>> <http://tomcat.apache.org/migration-7.html#Upgrading_7.0.x> and override
>> the JAR files.
>>
>> I recently started to use TomEE Plus 1.6.0.2, and now I'd like to upgrade
>> it to 1.7.0.
>>
>> What would be the best way to do it?
>>
>> Thanks
>>
>
>

Re: Best way to upgrade?

[Howard W. Smith, Jr.]

Felipe, how often is your app(s) impacted by upgrading to latest version of
tomcat7?

if your app is never impacted by newer/newest version of tomcat7, 'and'
since you have already migrated to TomEE+ 1.6.0.2, I don't think your app
will be impacted when you migrate from TomEE+ 1.6.0.2 to 1.7.0.



On Fri, Aug 22, 2014 at 10:37 AM, Felipe Jaekel  wrote:

> In Tomcat I used to check the file differences here
>  and override
> the JAR files.
>
> I recently started to use TomEE Plus 1.6.0.2, and now I'd like to upgrade
> it to 1.7.0.
>
> What would be the best way to do it?
>
> Thanks
>

Re: tomee+hibernate+java8 possible?

[Howard W. Smith, Jr.]

Good question. Tried to, but ran into some migration issues, known bugs
etc. Let's not discuss that here. Don't want to hijack this thread, and
it's not a requirement for me to upgrade yet. :-)
On Aug 21, 2014 11:58 AM, "Karl Kildén"  wrote:

> Howard, very interesting thanks. When do you plan to upgrade eclipselink?
> ;)
>
> TomEE 1.7 seems really awesome.
>
>
> On 21 August 2014 17:03, helio frota <00h...@gmail.com> wrote:
>
> > - tomee+ 1.7.0  + eclipselink 2.3.2 + apache derby 10.x + JDK8
> >
> > Awesome !
> >
> >
> >
> >
> > On Thu, Aug 21, 2014 at 11:00 AM, Howard W. Smith, Jr. <
> > smithh032...@gmail.com> wrote:
> >
> > > My response may be inappropriate but I have been using
> > >
> > > - tomee+ 1.5.1  + eclipselink 2.3.2 + apache derby 10.x + JDK7
> > >
> > > - tomee+ 1.6.x  + eclipselink 2.3.2 + apache derby 10.x + JDK7
> > >
> > > and now
> > >
> > > - tomee+ 1.7.0  + eclipselink 2.3.2 + apache derby 10.x + JDK8
> > >
> > > and the stack is working great, and I'm loving it!
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Thu, Aug 21, 2014 at 8:46 AM, Emmanuel Touzery <
> > > emmanuel.touz...@lecip-its.com> wrote:
> > >
> > > > Hello,
> > > >
> > > >  thank you. Right now we think that hibernate 4.2.x ought to work
> with
> > > > java8 so we'll try that setup first. But we'll remember this in case
> we
> > > > find out that's not the case.
> > > >
> > > >  Regards,
> > > >
> > > > Emmanuel
> > > >
> > > >
> > > > On 18/08/14 13:50, Romain Manni-Bucau wrote:
> > > >
> > > >> Hi
> > > >>
> > > >> If you add jpa 2.1 api replacing javee api jar by geronimo jar
> (javee
> > > api
> > > >> is just a shade of geronimos ones) it should work
> > > >> Le 18 août 2014 10:46, "Emmanuel Touzery" <
> > > emmanuel.touz...@lecip-its.com
> > > >> >
> > > >> a écrit :
> > > >>
> > > >>  Hello,
> > > >>>
> > > >>>  we are using tomee 1.6 with hibernate 4.2. Now that 1.7 is
> out,
> > we
> > > >>> are
> > > >>> interested to migrate to it, and start using the new java8
> features.
> > We
> > > >>> are
> > > >>> not sure which hibernate version introduced support for java8 (it
> > turns
> > > >>> out
> > > >>> extremely difficult to come to that information...), so we planned
> to
> > > >>> move
> > > >>> to the latest hibernate 4.3 version, however we found this:
> > > >>> http://stackoverflow.com/a/15771969/516188
> > > >>>
> > > >>>  There it's written /"However, Hibernate 4.3+ (JPA 2.1) is not
> > > >>> supported by TomEE, because it's Java EE 7."/. I wonder, is that
> > true?
> > > >>> That
> > > >>> we can't use hibernate 4.3+ with tomee 1.x? We definitely don't
> want
> > to
> > > >>> use
> > > >>> JEE7 features until all is ready. We are looking for a supported
> > > >>> configuration.
> > > >>>
> > > >>>  If that is true, does anyone know whether that prevents us
> from
> > > >>> using
> > > >>> tomee 1.x+hibernate+java8? Or maybe hibernate 4.2.x is enough for
> > that?
> > > >>> (yes, this last question I guess I should rather ask in a hibernate
> > > >>> forum,
> > > >>> but I can try asking here just in case someone happens to know)
> > > >>>
> > > >>>  Regards,
> > > >>>
> > > >>> Emmanuel
> > > >>>
> > > >>>
> > > >
> > >
> >
>

Re: tomee+hibernate+java8 possible?

[Howard W. Smith, Jr.]

My response may be inappropriate but I have been using

- tomee+ 1.5.1  + eclipselink 2.3.2 + apache derby 10.x + JDK7

- tomee+ 1.6.x  + eclipselink 2.3.2 + apache derby 10.x + JDK7

and now

- tomee+ 1.7.0  + eclipselink 2.3.2 + apache derby 10.x + JDK8

and the stack is working great, and I'm loving it!






On Thu, Aug 21, 2014 at 8:46 AM, Emmanuel Touzery <
emmanuel.touz...@lecip-its.com> wrote:

> Hello,
>
>  thank you. Right now we think that hibernate 4.2.x ought to work with
> java8 so we'll try that setup first. But we'll remember this in case we
> find out that's not the case.
>
>  Regards,
>
> Emmanuel
>
>
> On 18/08/14 13:50, Romain Manni-Bucau wrote:
>
>> Hi
>>
>> If you add jpa 2.1 api replacing javee api jar by geronimo jar (javee api
>> is just a shade of geronimos ones) it should work
>> Le 18 août 2014 10:46, "Emmanuel Touzery" > >
>> a écrit :
>>
>>  Hello,
>>>
>>>  we are using tomee 1.6 with hibernate 4.2. Now that 1.7 is out, we
>>> are
>>> interested to migrate to it, and start using the new java8 features. We
>>> are
>>> not sure which hibernate version introduced support for java8 (it turns
>>> out
>>> extremely difficult to come to that information...), so we planned to
>>> move
>>> to the latest hibernate 4.3 version, however we found this:
>>> http://stackoverflow.com/a/15771969/516188
>>>
>>>  There it's written /"However, Hibernate 4.3+ (JPA 2.1) is not
>>> supported by TomEE, because it's Java EE 7."/. I wonder, is that true?
>>> That
>>> we can't use hibernate 4.3+ with tomee 1.x? We definitely don't want to
>>> use
>>> JEE7 features until all is ready. We are looking for a supported
>>> configuration.
>>>
>>>  If that is true, does anyone know whether that prevents us from
>>> using
>>> tomee 1.x+hibernate+java8? Or maybe hibernate 4.2.x is enough for that?
>>> (yes, this last question I guess I should rather ask in a hibernate
>>> forum,
>>> but I can try asking here just in case someone happens to know)
>>>
>>>  Regards,
>>>
>>> Emmanuel
>>>
>>>
>

Re: Switching to Eclipselink in TomEE plus?

[Howard W. Smith, Jr.]

okay, i just confirmed that with my app and tomee+ 1.7.0. i added the
following to my java [startup] options

-Dopenejb.eclipselink.jmx=false

and i see the following in the log file:

2014-08-18 15:14:00 Commons Daemon procrun stdout initialized
[EL Info]: 2014-08-18 15:14:34.656--ServerSession(9569)--EclipseLink,
version: Eclipse Persistence Services - 2.3.2.v2025-r10461
[EL Info]: 2014-08-18
15:14:35.246--ServerSession(9569)--file:/C:/apache-tomee-plus-1.7.0/webapps/mcmsweb/WEB-INF/classes/_mcmsPU
login successful

That fixed the EclipseLink NullPointerException.



On Mon, Aug 18, 2014 at 3:01 PM, Romain Manni-Bucau 
wrote:

> it is in 1.7
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-08-18 21:00 GMT+02:00 Howard W. Smith, Jr. :
> > Is this (openejb.eclipselink.jmx=false) added as part of the fix, or
> > is openejb.eclipselink.jmx=false available in tomee 7.0 final release,
> > already?
> >
> >
> > On Mon, Aug 18, 2014 at 2:36 PM, Romain Manni-Bucau <
> rmannibu...@gmail.com>
> > wrote:
> >
> >> you can also disable it setting openejb.eclipselink.jmx=false
>

Re: Switching to Eclipselink in TomEE plus?

[Howard W. Smith, Jr.]

Is this (openejb.eclipselink.jmx=false) added as part of the fix, or
is openejb.eclipselink.jmx=false available in tomee 7.0 final release,
already?


On Mon, Aug 18, 2014 at 2:36 PM, Romain Manni-Bucau 
wrote:

> you can also disable it setting openejb.eclipselink.jmx=false

Re: Switching to Eclipselink in TomEE plus?

[Howard W. Smith, Jr.]

Romain is 'always' fast! :D

On Mon, Aug 18, 2014 at 2:33 PM, Bjorn Danielsson <
bjorn-apa...@lists.cuspycode.com> wrote:

> Wow! That was fast ;-)

Re: Primefaces Push not working for me

[Howard W. Smith, Jr.]

Below is my class annotated with @PushEndpoint,


package pf;

import javax.faces.application.FacesMessage;
import org.primefaces.push.annotation.OnMessage;
import org.primefaces.push.annotation.PushEndpoint;
import org.primefaces.push.annotation.Singleton;
import org.primefaces.push.impl.JSONEncoder;

@PushEndpoint("/{usernameAndSessionId}")
@Singleton
public class NotifyResource {

@OnMessage(encoders = {JSONEncoder.class})
public FacesMessage onMessage(FacesMessage message) {
return message;
}

}


Look for @PushEndpoint and pf.NotifyResource in my server log:

Aug 17, 2014 7:03:51 PM org.atmosphere.cpr.AtmosphereFramework
autoConfigureService
INFO: Atmosphere is using org.atmosphere.cpr.DefaultAnnotationProcessor for
processing annotation
Aug 17, 2014 7:03:51 PM org.atmosphere.cpr.DefaultAnnotationProcessor
configure
INFO: AnnotationProcessor class
org.atmosphere.cpr.DefaultAnnotationProcessor$ServletContainerInitializerAnnotationProcessor
being used
Aug 17, 2014 7:03:51 PM
org.atmosphere.cpr.DefaultAnnotationProcessor$BytecodeBasedAnnotationProcessor$1
reportTypeAnnotation
INFO: Found Annotation in pf.NotifyResource being scanned: interface
org.primefaces.push.annotation.PushEndpoint
Aug 17, 2014 7:03:51 PM org.atmosphere.cpr.AtmosphereFramework
addAtmosphereHandler
INFO: Installed AtmosphereHandler
org.primefaces.push.impl.PushEndpointHandlerProxy mapped to context-path
/{usernameAndSessionId} and Broadcaster Class
org.atmosphere.cpr.DefaultBroadcaster
Aug 17, 2014 7:03:51 PM org.atmosphere.cpr.AtmosphereFramework
addAtmosphereHandler
INFO: Installed AtmosphereInterceptor [@PushEndpoint Interceptor] mapped to
AtmosphereHandler org.primefaces.push.impl.PushEndpointHandlerProxy



On Sun, Aug 17, 2014 at 6:07 PM, Howard W. Smith, Jr. <
smithh032...@gmail.com> wrote:

> Karl, your web.xml looks okay, but my web.xml does not include the
> following:
>
>
> 
> org.atmosphere.annotation.packages
> org.primefaces.push
> 
> 
> org.atmosphere.cpr.packages
> com.kildeen.ref
>     
>
>
>
> On Sun, Aug 17, 2014 at 5:58 PM, Howard W. Smith, Jr. <
> smithh032...@gmail.com> wrote:
>
>> Karl,
>>
>> Please see PrimeFaces 5.0 user guide, page 530, section 9.5.1 Counter,
>> and then scroll down and look for,
>>
>> package org.primefaces.examples.push.counter;
>>
>> import org.primefaces.push.annotation.OnMessage;
>> import org.primefaces.push.annotation.PushEndpoint;
>> import org.primefaces.push.impl.JSONEncoder;
>>
>> @PushEndpoint("/counter")
>> public class CounterResource {
>> @OnMessage(encoders = {JSONEncoder.class})
>> public String onMessage(String count) {
>> return count;
>> }
>> }
>>
>>
>> do you have a class like this defined in your app? you should try to
>> deploy the PrimeFaces 5.0 Push - Counter example, test the example, and
>> make appropriate code changes to your PrimeFaces Push logic.
>>
>>
>>
>>
>> On Sun, Aug 17, 2014 at 1:12 PM, Karl Kildén 
>> wrote:
>>
>>> Hello,
>>>
>>> Running various versions of TomEE with Primefaces 5 all results in this
>>> problem: ERROR  org.primefaces.push.PushServlet: No Annotated class using
>>> @PushEndpoint found. Push will not work.
>>>
>>> Full boot log is here:
>>> https://gist.github.com/karlkilden/5b7c1dfe7ba5e5c2bd99
>>>
>>> I tried various configurations of Primepush and I had it working with
>>> primefaces 4. I also tried various versions of the atmosphere runtime.
>>> Anyone using this that would care to share configuration? I will try to
>>> get
>>> a minimal demo app together soon.
>>>
>>> This is what I tried most recently:
>>>
>>> 
>>> org.atmosphere
>>> atmosphere-runtime
>>> 2.1.8
>>> 
>>>
>>>
>>> 
>>>
>>> Push Servlet
>>>
>>> org.primefaces.push.PushServlet
>>> 
>>>
>>> org.atmosphere.cpr.broadcasterCacheClass
>>>
>>> org.atmosphere.cache.UUIDBroadcasterCache
>>> 
>>> 
>>> org.atmosphere.annotation.packages
>>> org.primefaces.push
>>> 
>>> 
>>> org.atmosphere.cpr.packages
>>> com.kildeen.ref
>>> 
>>> true
>>> 
>>>
>>> 
>>> Push Servlet
>>> /primepush/*
>>> 
>>>
>>>
>>>
>>> cheers
>>>
>>
>>
>

Re: Primefaces Push not working for me

[Howard W. Smith, Jr.]

Karl, your web.xml looks okay, but my web.xml does not include the
following:



org.atmosphere.annotation.packages
org.primefaces.push


org.atmosphere.cpr.packages
com.kildeen.ref




On Sun, Aug 17, 2014 at 5:58 PM, Howard W. Smith, Jr. <
smithh032...@gmail.com> wrote:

> Karl,
>
> Please see PrimeFaces 5.0 user guide, page 530, section 9.5.1 Counter, and
> then scroll down and look for,
>
> package org.primefaces.examples.push.counter;
>
> import org.primefaces.push.annotation.OnMessage;
> import org.primefaces.push.annotation.PushEndpoint;
> import org.primefaces.push.impl.JSONEncoder;
>
> @PushEndpoint("/counter")
> public class CounterResource {
> @OnMessage(encoders = {JSONEncoder.class})
> public String onMessage(String count) {
> return count;
> }
> }
>
>
> do you have a class like this defined in your app? you should try to
> deploy the PrimeFaces 5.0 Push - Counter example, test the example, and
> make appropriate code changes to your PrimeFaces Push logic.
>
>
>
>
> On Sun, Aug 17, 2014 at 1:12 PM, Karl Kildén 
> wrote:
>
>> Hello,
>>
>> Running various versions of TomEE with Primefaces 5 all results in this
>> problem: ERROR  org.primefaces.push.PushServlet: No Annotated class using
>> @PushEndpoint found. Push will not work.
>>
>> Full boot log is here:
>> https://gist.github.com/karlkilden/5b7c1dfe7ba5e5c2bd99
>>
>> I tried various configurations of Primepush and I had it working with
>> primefaces 4. I also tried various versions of the atmosphere runtime.
>> Anyone using this that would care to share configuration? I will try to
>> get
>> a minimal demo app together soon.
>>
>> This is what I tried most recently:
>>
>> 
>> org.atmosphere
>> atmosphere-runtime
>> 2.1.8
>> 
>>
>>
>> 
>>
>> Push Servlet
>>
>> org.primefaces.push.PushServlet
>> 
>>
>> org.atmosphere.cpr.broadcasterCacheClass
>>
>> org.atmosphere.cache.UUIDBroadcasterCache
>> 
>> 
>> org.atmosphere.annotation.packages
>> org.primefaces.push
>> 
>> 
>> org.atmosphere.cpr.packages
>> com.kildeen.ref
>> 
>> true
>> 
>>
>> 
>> Push Servlet
>> /primepush/*
>> 
>>
>>
>>
>> cheers
>>
>
>

Re: Primefaces Push not working for me

[Howard W. Smith, Jr.]

Karl,

Please see PrimeFaces 5.0 user guide, page 530, section 9.5.1 Counter, and
then scroll down and look for,

package org.primefaces.examples.push.counter;

import org.primefaces.push.annotation.OnMessage;
import org.primefaces.push.annotation.PushEndpoint;
import org.primefaces.push.impl.JSONEncoder;

@PushEndpoint("/counter")
public class CounterResource {
@OnMessage(encoders = {JSONEncoder.class})
public String onMessage(String count) {
return count;
}
}


do you have a class like this defined in your app? you should try to deploy
the PrimeFaces 5.0 Push - Counter example, test the example, and make
appropriate code changes to your PrimeFaces Push logic.




On Sun, Aug 17, 2014 at 1:12 PM, Karl Kildén  wrote:

> Hello,
>
> Running various versions of TomEE with Primefaces 5 all results in this
> problem: ERROR  org.primefaces.push.PushServlet: No Annotated class using
> @PushEndpoint found. Push will not work.
>
> Full boot log is here:
> https://gist.github.com/karlkilden/5b7c1dfe7ba5e5c2bd99
>
> I tried various configurations of Primepush and I had it working with
> primefaces 4. I also tried various versions of the atmosphere runtime.
> Anyone using this that would care to share configuration? I will try to get
> a minimal demo app together soon.
>
> This is what I tried most recently:
>
> 
> org.atmosphere
> atmosphere-runtime
> 2.1.8
> 
>
>
> 
>
> Push Servlet
>
> org.primefaces.push.PushServlet
> 
>
> org.atmosphere.cpr.broadcasterCacheClass
>
> org.atmosphere.cache.UUIDBroadcasterCache
> 
> 
> org.atmosphere.annotation.packages
> org.primefaces.push
> 
> 
> org.atmosphere.cpr.packages
> com.kildeen.ref
> 
> true
> 
>
> 
> Push Servlet
> /primepush/*
> 
>
>
>
> cheers
>

Re: Switching to Eclipselink in TomEE plus?

[Howard W. Smith, Jr.]

Karl, I informed the list (in another topic/thread) that I saw that
nullpointerexception too, since I have eclipselink in my project. I only
see this on my DEV server (windows 2008 server, standard edition, 64-bit,
JDK 8.0_11).

I don't see the exception onmy production server (windows 2008 server, R2,
64-bit, JDK 8.0_11).

I use eclipselink 2.3.2 and Apache Derby 10.x.



On Sun, Aug 17, 2014 at 3:14 PM, Karl Kildén  wrote:

> Seems to work fine but I do get this in the log:
>
> [EL Info]: 2014-08-17
>
> 18:57:56.333--ServerSession(2103498909)--file:/C:/raindance/mp/mp/web/target/mp-web-1.0.0-SNAPSHOT/WEB-INF/lib/mp-domain-1.0.0-SNAPSHOT.jar_ref
> login successful
> [EL Warning]: 2014-08-17 18:57:56.338--ServerSession(2103498909)--Problem
> while registering MBean: java.lang.NullPointerException
>
> You never want NPE in your boot log, anyone knows whats up?
>
>
> On 16 August 2014 21:55, Karl Kildén  wrote:
>
> > Thanks guys!
> >
> >
> > On 16 August 2014 19:57, Bjorn Danielsson <
> > bjorn-apa...@lists.cuspycode.com> wrote:
> >
> >> I've been switching back and forth between Eclipselink and OpenJPA
> >> for various reasons. All I do to enable Eclipselink is put a copy
> >> of eclipselink.jar in tomee/lib, in addition to changing the provider
> >> in my app's persistence.xml. If you don't want to use plume, just
> >> copy the eclipselink jar from that distribution.
> >>
> >> --
> >> Bjorn Danielsson
> >> Cuspy Code AB
> >>
> >>
> >> Karl Kildén  wrote:
> >> > Hello, I know this is supposed to be trivial. This shows config
> changes:
> >> >
> >> > http://tomee.apache.org/examples-trunk/jpa-eclipselink/README.html
> >> >
> >> > But what about lib changes? Anyone have good advice on what to add and
> >> > possibly remove?
> >> >
> >> > cheers
> >>
> >
> >
>

Re: TomEE 1.7.0 Release: xbean error caused by NoClassDefFoundError: org/apache/geronimo/osgi/locator/ProviderLocator

[Howard W. Smith, Jr.]

Okay, thanks Bjorn for letting me know that about Sun/Oracle javamail in
the WAR.



On Fri, Aug 15, 2014 at 3:39 PM, Bjorn Danielsson <
bjorn-apa...@lists.cuspycode.com> wrote:

> Hi Howard,
>
> Adding the Sun/Oracle javamail to the WAR works for my app in 1.7.0.
>
> I gave up trying to make Geronimo Javamail work a long time ago,
> it was clearly broken and there was no one who could fix it.
>
> --
> Bjorn Danielsson
> Cuspy Code AB
>
>
> "Howard W. Smith, Jr."  wrote:
> > okay, when i use (tomee 1.7.0) geronimo-javamail_1.4_mail-1.8.3.jar, my
> app
> > still has javamail sendmail issues. see exception below. next, I'll try
> to
> > add Sun/Oracle's javamail to my WAR. I hope that resolves the stacktrace
> > issue below and allows me to use tomee 1.7.0. otherwise, i will just have
> > to keep using tomee 1.6.0.2 and/or the next tomee release that does 'not'
> > require geronimo-javamail_1.4_mail-1.8.3.jar.
> >
> >
> > javax.mail.SendFailedException: Send failure
> > (javax.mail.MessagingException: Connection error
> > (java.net.ConnectException: Connection timed out: connect))
> > at javax.mail.Transport.send(Transport.java:163)
> > at javax.mail.Transport.send(Transport.java:48)
> > at utils.mail.JavaMail.sendMail(JavaMail.java:151)
> > at pf.ApplicationScopeBean.sendMail(ApplicationScopeBean.java:601)
> > at
> >
> pf.ApplicationScopeBean$$OwbNormalScopeProxy0.sendMail(pf/ApplicationScopeBean.java)
> > at
> >
> utils.mail.EmailOrderSentByUser.emailDriverWorksheet(EmailOrderSentByUser.java:102)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> > at
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > at java.lang.reflect.Method.invoke(Method.java:483)
> > at
> >
> org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:192)
> > at
> >
> org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:173)
> > at
> >
> org.apache.openejb.monitoring.StatsInterceptor.record(StatsInterceptor.java:181)
> > at
> >
> org.apache.openejb.monitoring.StatsInterceptor.invoke(StatsInterceptor.java:100)
> > at sun.reflect.GeneratedMethodAccessor96.invoke(Unknown Source)
> > at
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > at java.lang.reflect.Method.invoke(Method.java:483)
> > at
> >
> org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:192)
> > at
> >
> org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:173)
> > at
> >
> org.apache.openejb.core.interceptor.InterceptorStack.invoke(InterceptorStack.java:85)
> > at
> >
> org.apache.openejb.core.singleton.SingletonContainer._invoke(SingletonContainer.java:256)
> > at
> >
> org.apache.openejb.core.singleton.SingletonContainer.invoke(SingletonContainer.java:212)
> > at
> >
> org.apache.openejb.core.ivm.EjbObjectProxyHandler.synchronizedBusinessMethod(EjbObjectProxyHandler.java:308)
> > at
> >
> org.apache.openejb.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:303)
> > at
> >
> org.apache.openejb.core.ivm.EjbObjectProxyHandler._invoke(EjbObjectProxyHandler.java:92)
> > at
> >
> org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:308)
> > at
> >
> utils.mail.EmailOrderSentByUser$$LocalBeanProxy.emailDriverWorksheet(utils/mail/EmailOrderSentByUser.java)
> > at mdb.EmailMessageDrivenBean.onMessage(EmailMessageDrivenBean.java:190)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> > at
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > at java.lang.reflect.Method.invoke(Method.java:483)
> > at
> >
> org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:192)
> > at
> >
> org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:173)
> > at
> >
> org.apache.openejb.monitoring.StatsInterceptor.record(StatsInterceptor.java:181)
> &

Re: TomEE 1.7.0 Release: xbean error caused by NoClassDefFoundError: org/apache/geronimo/osgi/locator/ProviderLocator

[Howard W. Smith, Jr.]

Okay, well, I deployed TomEE+ 1.7.0 to production server as per all
discussed here, and I don't see the following exception:

Problem while registering MBean: java.lang.NullPointerException

Not using geronimo-osgi-registry-1.1.jar on production server.

I'm good, now, thanks Romain.



On Fri, Aug 15, 2014 at 2:00 PM, Romain Manni-Bucau 
wrote:

> I think it is not linked but without more info no idea to be honest.
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-08-15 19:57 GMT+02:00 Howard W. Smith, Jr. :
> > okay, see below:
> >
> > 1. added geronimo-osgi-locator/1.1/geronimo-osgi-locator-1.1.jar
> > <
> http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-osgi-locator/1.1/geronimo-osgi-locator-1.1.jar
> >
> > to
> > tomee/lib
> > 2. removed geronimo-javamail_1.4_mail-1.8.3.jar from tomee/lib
> > 3. added [Oracle] javax.mail.jar to tomee/lib
> > 4. started tomee 1.7.0, no errors
> > 5. logged into my app and saw the following exception
> >
> > [EL Warning]: 2014-08-15 13:52:45.914--ServerSession(2077670077)--Problem
> > while registering MBean: java.lang.NullPointerException
> >
> > 6. javamail sendmail works as expected :)
> >
> > should I add geronimo-osgi-registry-1.1.jar
> > <
> http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-osgi-registry/1.1/geronimo-osgi-registry-1.1.jar
> >
> > to
> > resolve the exception in #5 above?
> >
> >
> > On Fri, Aug 15, 2014 at 1:46 PM, Romain Manni-Bucau <
> rmannibu...@gmail.com>
> > wrote:
> >
> >> Just replace geronimo javamail by
> >>
> >>
> http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-osgi-locator/1.1/geronimo-osgi-locator-1.1.jar
> >> and maybe
> >>
> http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-osgi-registry/1.1/geronimo-osgi-registry-1.1.jar
> >> + mail.jar you want
> >>
> >>
> >> Romain Manni-Bucau
> >> Twitter: @rmannibucau
> >> Blog: http://rmannibucau.wordpress.com/
> >> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> >> Github: https://github.com/rmannibucau
> >>
> >>
> >> 2014-08-15 19:42 GMT+02:00 Howard W. Smith, Jr.  >:
> >> > okay, when i use (tomee 1.7.0) geronimo-javamail_1.4_mail-1.8.3.jar,
> my
> >> app
> >> > still has javamail sendmail issues. see exception below. next, I'll
> try
> >> to
> >> > add Sun/Oracle's javamail to my WAR. I hope that resolves the
> stacktrace
> >> > issue below and allows me to use tomee 1.7.0. otherwise, i will just
> have
> >> > to keep using tomee 1.6.0.2 and/or the next tomee release that does
> 'not'
> >> > require geronimo-javamail_1.4_mail-1.8.3.jar.
> >> >
> >> >
> >> > javax.mail.SendFailedException: Send failure
> >> > (javax.mail.MessagingException: Connection error
> >> > (java.net.ConnectException: Connection timed out: connect))
> >> > at javax.mail.Transport.send(Transport.java:163)
> >> > at javax.mail.Transport.send(Transport.java:48)
> >> > at utils.mail.JavaMail.sendMail(JavaMail.java:151)
> >> > at pf.ApplicationScopeBean.sendMail(ApplicationScopeBean.java:601)
> >> > at
> >> >
> >>
> pf.ApplicationScopeBean$$OwbNormalScopeProxy0.sendMail(pf/ApplicationScopeBean.java)
> >> > at
> >> >
> >>
> utils.mail.EmailOrderSentByUser.emailDriverWorksheet(EmailOrderSentByUser.java:102)
> >> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >> > at
> >> >
> >>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> >> > at
> >> >
> >>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >> > at java.lang.reflect.Method.invoke(Method.java:483)
> >> > at
> >> >
> >>
> org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:192)
> >> > at
> >> >
> >>
> org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:173)
> >> > at
> >> >
> >>
> org.apache.openejb.monitoring.StatsInterceptor.re

Re: TomEE 1.7.0 Release: xbean error caused by NoClassDefFoundError: org/apache/geronimo/osgi/locator/ProviderLocator

[Howard W. Smith, Jr.]

I added geronimo-osgi-registry-1.1.jar
<http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-osgi-registry/1.1/geronimo-osgi-registry-1.1.jar>,
but

[EL Warning]: 2014-08-15 13:52:45.914--ServerSession(2077670077)--Problem
while registering MBean: java.lang.NullPointerException

still shows up in catalina log after tomee and my webapp is started,


Aug 15, 2014 2:01:40 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deployment of web application archive
C:\apache-tomee-plus-1.7.0\webapps\mcmsweb.war has finished in 16,920 ms
Aug 15, 2014 2:01:40 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-nio-8080"]
Aug 15, 2014 2:01:40 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
Aug 15, 2014 2:01:40 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 17017 ms
Aug 15, 2014 2:01:41 PM org.atmosphere.cpr.AtmosphereFramework$4 run
INFO: Latest version of Atmosphere's JavaScript Client 2.2.2
Aug 15, 2014 2:01:50 PM org.apache.myfaces.el.unified.ResolverBuilderBase
sortELResolvers
INFO: Chain of EL resolvers for Faces sorted with:
org.apache.myfaces.el.unified.OpenWebBeansELResolverComparator@41b76e3f and
the result order is
[org.apache.myfaces.el.unified.resolver.implicitobject.ImplicitObjectResolver@8797b93,
org.apache.myfaces.el.unified.resolver.CompositeComponentELResolver@6a376b11,
org.apache.webbeans.el22.WebBeansELResolver@33c01d53,
org.apache.myfaces.el.FlashELResolver@497c4b82,
org.apache.myfaces.el.unified.resolver.ManagedBeanResolver@a1a04dd,
org.apache.myfaces.el.unified.resolver.ResourceResolver@5b24996c,
javax.el.ResourceBundleELResolver@683d2dde,
org.apache.myfaces.el.unified.resolver.ResourceBundleResolver@43b64b00,
javax.el.MapELResolver@19d09347, javax.el.ListELResolver@66c086e8,
javax.el.ArrayELResolver@67921433, javax.el.BeanELResolver@168dad8a]
[EL Info]: 2014-08-15 14:01:50.748--ServerSession(1699209850)--EclipseLink,
version: Eclipse Persistence Services - 2.3.2.v2025-r10461
[EL Info]: 2014-08-15
14:01:51.35--ServerSession(1699209850)--file:/C:/apache-tomee-plus-1.7.0/webapps/mcmsweb/WEB-INF/classes/_mcmsPU
login successful
[EL Warning]: 2014-08-15 14:01:51.354--ServerSession(1699209850)--Problem
while registering MBean: java.lang.NullPointerException
Aug 15, 2014 2:02:03 PM pf.ApplicationScopeBean login



On Fri, Aug 15, 2014 at 1:57 PM, Howard W. Smith, Jr. <
smithh032...@gmail.com> wrote:

> okay, see below:
>
> 1. added geronimo-osgi-locator/1.1/geronimo-osgi-locator-1.1.jar
> <http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-osgi-locator/1.1/geronimo-osgi-locator-1.1.jar>
>  to
> tomee/lib
> 2. removed geronimo-javamail_1.4_mail-1.8.3.jar from tomee/lib
> 3. added [Oracle] javax.mail.jar to tomee/lib
> 4. started tomee 1.7.0, no errors
> 5. logged into my app and saw the following exception
>
> [EL Warning]: 2014-08-15 13:52:45.914--ServerSession(2077670077)--Problem
> while registering MBean: java.lang.NullPointerException
>
> 6. javamail sendmail works as expected :)
>
> should I add geronimo-osgi-registry-1.1.jar
> <http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-osgi-registry/1.1/geronimo-osgi-registry-1.1.jar>
>  to
> resolve the exception in #5 above?
>
>
> On Fri, Aug 15, 2014 at 1:46 PM, Romain Manni-Bucau  > wrote:
>
>> Just replace geronimo javamail by
>>
>> http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-osgi-locator/1.1/geronimo-osgi-locator-1.1.jar
>> and maybe
>> http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-osgi-registry/1.1/geronimo-osgi-registry-1.1.jar
>> + mail.jar you want
>>
>>
>> Romain Manni-Bucau
>> Twitter: @rmannibucau
>> Blog: http://rmannibucau.wordpress.com/
>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>> Github: https://github.com/rmannibucau
>>
>>
>> 2014-08-15 19:42 GMT+02:00 Howard W. Smith, Jr. :
>> > okay, when i use (tomee 1.7.0) geronimo-javamail_1.4_mail-1.8.3.jar, my
>> app
>> > still has javamail sendmail issues. see exception below. next, I'll try
>> to
>> > add Sun/Oracle's javamail to my WAR. I hope that resolves the stacktrace
>> > issue below and allows me to use tomee 1.7.0. otherwise, i will just
>> have
>> > to keep using tomee 1.6.0.2 and/or the next tomee release that does
>> 'not'
>> > require geronimo-javamail_1.4_mail-1.8.3.jar.
>> >
>> >
>> > javax.mail.SendFailedException: Send failure
>> > (javax.mail.MessagingException: Connection error
>> > (java.net.ConnectException: Connection timed out: connect))
>> > at javax.mail.Transport.send(Transport.java:163)
>> > at 

Re: TomEE 1.7.0 Release: xbean error caused by NoClassDefFoundError: org/apache/geronimo/osgi/locator/ProviderLocator

[Howard W. Smith, Jr.]

okay, see below:

1. added geronimo-osgi-locator/1.1/geronimo-osgi-locator-1.1.jar
<http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-osgi-locator/1.1/geronimo-osgi-locator-1.1.jar>
to
tomee/lib
2. removed geronimo-javamail_1.4_mail-1.8.3.jar from tomee/lib
3. added [Oracle] javax.mail.jar to tomee/lib
4. started tomee 1.7.0, no errors
5. logged into my app and saw the following exception

[EL Warning]: 2014-08-15 13:52:45.914--ServerSession(2077670077)--Problem
while registering MBean: java.lang.NullPointerException

6. javamail sendmail works as expected :)

should I add geronimo-osgi-registry-1.1.jar
<http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-osgi-registry/1.1/geronimo-osgi-registry-1.1.jar>
to
resolve the exception in #5 above?


On Fri, Aug 15, 2014 at 1:46 PM, Romain Manni-Bucau 
wrote:

> Just replace geronimo javamail by
>
> http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-osgi-locator/1.1/geronimo-osgi-locator-1.1.jar
> and maybe
> http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-osgi-registry/1.1/geronimo-osgi-registry-1.1.jar
> + mail.jar you want
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-08-15 19:42 GMT+02:00 Howard W. Smith, Jr. :
> > okay, when i use (tomee 1.7.0) geronimo-javamail_1.4_mail-1.8.3.jar, my
> app
> > still has javamail sendmail issues. see exception below. next, I'll try
> to
> > add Sun/Oracle's javamail to my WAR. I hope that resolves the stacktrace
> > issue below and allows me to use tomee 1.7.0. otherwise, i will just have
> > to keep using tomee 1.6.0.2 and/or the next tomee release that does 'not'
> > require geronimo-javamail_1.4_mail-1.8.3.jar.
> >
> >
> > javax.mail.SendFailedException: Send failure
> > (javax.mail.MessagingException: Connection error
> > (java.net.ConnectException: Connection timed out: connect))
> > at javax.mail.Transport.send(Transport.java:163)
> > at javax.mail.Transport.send(Transport.java:48)
> > at utils.mail.JavaMail.sendMail(JavaMail.java:151)
> > at pf.ApplicationScopeBean.sendMail(ApplicationScopeBean.java:601)
> > at
> >
> pf.ApplicationScopeBean$$OwbNormalScopeProxy0.sendMail(pf/ApplicationScopeBean.java)
> > at
> >
> utils.mail.EmailOrderSentByUser.emailDriverWorksheet(EmailOrderSentByUser.java:102)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> > at
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > at java.lang.reflect.Method.invoke(Method.java:483)
> > at
> >
> org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:192)
> > at
> >
> org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:173)
> > at
> >
> org.apache.openejb.monitoring.StatsInterceptor.record(StatsInterceptor.java:181)
> > at
> >
> org.apache.openejb.monitoring.StatsInterceptor.invoke(StatsInterceptor.java:100)
> > at sun.reflect.GeneratedMethodAccessor96.invoke(Unknown Source)
> > at
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > at java.lang.reflect.Method.invoke(Method.java:483)
> > at
> >
> org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:192)
> > at
> >
> org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:173)
> > at
> >
> org.apache.openejb.core.interceptor.InterceptorStack.invoke(InterceptorStack.java:85)
> > at
> >
> org.apache.openejb.core.singleton.SingletonContainer._invoke(SingletonContainer.java:256)
> > at
> >
> org.apache.openejb.core.singleton.SingletonContainer.invoke(SingletonContainer.java:212)
> > at
> >
> org.apache.openejb.core.ivm.EjbObjectProxyHandler.synchronizedBusinessMethod(EjbObjectProxyHandler.java:308)
> > at
> >
> org.apache.openejb.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:303)
> > at
> >
> org.apache.openejb.core.ivm.EjbObjectProxyHandler._invoke(EjbObjectProxyHandler.java:92)
> > at
> >
> org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:308)
> > at
> >
> utils.mail.EmailOrderSentByUser$$LocalBeanProxy.emailDriverWorksheet(utils/mail/EmailOrd

Re: TomEE 1.7.0 Release: xbean error caused by NoClassDefFoundError: org/apache/geronimo/osgi/locator/ProviderLocator

[Howard W. Smith, Jr.]

Context.java:366)
at
org.apache.geronimo.connector.work.pool.NamedRunnable.run(NamedRunnable.java:32)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: javax.mail.MessagingException: Connection error
(java.net.ConnectException: Connection timed out: connect)
at
org.apache.geronimo.javamail.transport.smtp.SMTPConnection.protocolConnect(SMTPConnection.java:161)
at
org.apache.geronimo.javamail.transport.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:165)
at javax.mail.Service.connect(Service.java:274)
at javax.mail.Service.connect(Service.java:91)
at javax.mail.Service.connect(Service.java:76)
at javax.mail.Transport.send(Transport.java:94)
... 55 more
Caused by: java.net.ConnectException: Connection timed out: connect
at java.net.DualStackPlainSocketImpl.connect0(Native Method)
at
java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:79)
at
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
at
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at java.net.Socket.connect(Socket.java:538)
at java.net.Socket.(Socket.java:434)
at java.net.Socket.(Socket.java:286)
at
org.apache.geronimo.javamail.util.MailConnection.getConnectedSocket(MailConnection.java:307)
at
org.apache.geronimo.javamail.util.MailConnection.getConnection(MailConnection.java:250)
at
org.apache.geronimo.javamail.transport.smtp.SMTPConnection.protocolConnect(SMTPConnection.java:140)
... 60 more





On Fri, Aug 15, 2014 at 1:33 PM, Howard W. Smith, Jr. <
smithh032...@gmail.com> wrote:

> I solved the error by adding geronimo-javamail_1.4_mail-1.8.3.jar to
> tomee/lib. I do not like using this JAR, because of javamail sendmail
> issues that I have experienced with TomEE 1.5.x and 1.6.x.
>
> Now, TomEE 1.7.0 requires geronimo-javamail_1.4_mail-1.8.3.jar to exist in
> tomee/lib to run/start properly?
>
> My preference is to use Sun/Oracle's javamail.jar instead
> of geronimo-javamail_1.4_mail-1.8.3.jar. Should I add Sun/Oracle's
> javamail.jar to my WAR, since I'm assuming that I cannot add both JARs to
> tomee/lib?
>
>
>
>
> On Fri, Aug 15, 2014 at 12:57 PM, Howard W. Smith, Jr. <
> smithh032...@gmail.com> wrote:
>
>> I just downloaded TomEE 1.7.0 release, and I get the exception stack
>> trace below, when I start tomEE 1.7.0 (and java 8 update 11) after
>> deploying my webapp to tomee 1.7.0. Please advise.
>>
>>
>> INFO: Enterprise application "openejb" loaded.
>> Aug 15, 2014 12:19:36 PM org.apache.openejb.assembler.classic.Assembler
>> createRecipe
>> INFO: Creating TransactionManager(id=Default Transaction Manager)
>> Aug 15, 2014 12:19:36 PM org.apache.openejb.assembler.classic.Assembler
>> createRecipe
>> INFO: Creating SecurityService(id=Tomcat Security Service)
>> Aug 15, 2014 12:19:36 PM org.apache.openejb.util.OpenEJBErrorHandler
>> handleUnknownError
>> SEVERE: FATAL ERROR: Unknown error in Assembler.  Please send the
>> following stack trace and this message to us...@openejb.apache.org :
>>  org.apache.xbean.recipe.ConstructionException: Error invoking
>> constructor: public org.apache.tomee.catalina.TomcatSecurityService()
>> at
>> org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:968)
>>  at
>> org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:276)
>> at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96)
>>  at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61)
>> at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49)
>>  at
>> org.apache.openejb.assembler.classic.Assembler.createSecurityService(Assembler.java:2517)
>> at
>> org.apache.openejb.assembler.classic.Assembler.buildContainerSystem(Assembler.java:498)
>>  at
>> org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:420)
>> at org.apache.openejb.OpenEJB$Instance.(OpenEJB.java:150)
>>  at org.apache.openejb.OpenEJB.init(OpenEJB.java:298)
>> at
>> org.apache.tomee.catalina.TomcatLoader.initialize(TomcatLoader.java:253)
>>  at
>> org.apache.tomee.catalina.ServerListener.install(ServerListener.java:168)
>> at
>> org.apache.tomee.catalina.ServerListener.lifecycleEvent(ServerListener.java:55)
>>  at
>> org.apache.catalina.util.Lifecycl

Re: TomEE 1.7.0 Release: xbean error caused by NoClassDefFoundError: org/apache/geronimo/osgi/locator/ProviderLocator

[Howard W. Smith, Jr.]

I solved the error by adding geronimo-javamail_1.4_mail-1.8.3.jar to
tomee/lib. I do not like using this JAR, because of javamail sendmail
issues that I have experienced with TomEE 1.5.x and 1.6.x.

Now, TomEE 1.7.0 requires geronimo-javamail_1.4_mail-1.8.3.jar to exist in
tomee/lib to run/start properly?

My preference is to use Sun/Oracle's javamail.jar instead
of geronimo-javamail_1.4_mail-1.8.3.jar. Should I add Sun/Oracle's
javamail.jar to my WAR, since I'm assuming that I cannot add both JARs to
tomee/lib?




On Fri, Aug 15, 2014 at 12:57 PM, Howard W. Smith, Jr. <
smithh032...@gmail.com> wrote:

> I just downloaded TomEE 1.7.0 release, and I get the exception stack trace
> below, when I start tomEE 1.7.0 (and java 8 update 11) after deploying my
> webapp to tomee 1.7.0. Please advise.
>
>
> INFO: Enterprise application "openejb" loaded.
> Aug 15, 2014 12:19:36 PM org.apache.openejb.assembler.classic.Assembler
> createRecipe
> INFO: Creating TransactionManager(id=Default Transaction Manager)
> Aug 15, 2014 12:19:36 PM org.apache.openejb.assembler.classic.Assembler
> createRecipe
> INFO: Creating SecurityService(id=Tomcat Security Service)
> Aug 15, 2014 12:19:36 PM org.apache.openejb.util.OpenEJBErrorHandler
> handleUnknownError
> SEVERE: FATAL ERROR: Unknown error in Assembler.  Please send the
> following stack trace and this message to us...@openejb.apache.org :
>  org.apache.xbean.recipe.ConstructionException: Error invoking
> constructor: public org.apache.tomee.catalina.TomcatSecurityService()
> at
> org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:968)
>  at
> org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:276)
> at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96)
>  at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61)
> at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49)
>  at
> org.apache.openejb.assembler.classic.Assembler.createSecurityService(Assembler.java:2517)
> at
> org.apache.openejb.assembler.classic.Assembler.buildContainerSystem(Assembler.java:498)
>  at
> org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:420)
> at org.apache.openejb.OpenEJB$Instance.(OpenEJB.java:150)
>  at org.apache.openejb.OpenEJB.init(OpenEJB.java:298)
> at org.apache.tomee.catalina.TomcatLoader.initialize(TomcatLoader.java:253)
>  at
> org.apache.tomee.catalina.ServerListener.install(ServerListener.java:168)
> at
> org.apache.tomee.catalina.ServerListener.lifecycleEvent(ServerListener.java:55)
>  at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
> at
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
>  at
> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402)
> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:110)
>  at org.apache.catalina.startup.Catalina.load(Catalina.java:638)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:663)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
>  at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:280)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:454)
> Caused by: java.lang.NoClassDefFoundError:
> org/apache/geronimo/osgi/locator/ProviderLocator
> at
> javax.security.jacc.PolicyConfigurationFactory$1.run(PolicyConfigurationFactory.java:89)
>  at java.security.AccessController.doPrivileged(Native Method)
> at
> javax.security.jacc.PolicyConfigurationFactory.getPolicyConfigurationFactory(PolicyConfigurationFactory.java:80)
>  at
> org.apache.openejb.core.security.AbstractSecurityService.installJacc(AbstractSecurityService.java:314)
> at
> org.apache.openejb.core.security.AbstractSecurityService.(AbstractSecurityService.java:77)
>  at
> org.apache.openejb.core.security.AbstractSecurityService.(AbstractSecurityService.java:71)
> at
> org.apache.tomee.catalina.TomcatSecurityService.(TomcatSecurityService.java:51)
>  at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>  at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:408)
>  at
> org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:958)
> ... 24 more

TomEE 1.7.0 Release: xbean error caused by NoClassDefFoundError: org/apache/geronimo/osgi/locator/ProviderLocator

[Howard W. Smith, Jr.]

I just downloaded TomEE 1.7.0 release, and I get the exception stack trace
below, when I start tomEE 1.7.0 (and java 8 update 11) after deploying my
webapp to tomee 1.7.0. Please advise.


INFO: Enterprise application "openejb" loaded.
Aug 15, 2014 12:19:36 PM org.apache.openejb.assembler.classic.Assembler
createRecipe
INFO: Creating TransactionManager(id=Default Transaction Manager)
Aug 15, 2014 12:19:36 PM org.apache.openejb.assembler.classic.Assembler
createRecipe
INFO: Creating SecurityService(id=Tomcat Security Service)
Aug 15, 2014 12:19:36 PM org.apache.openejb.util.OpenEJBErrorHandler
handleUnknownError
SEVERE: FATAL ERROR: Unknown error in Assembler.  Please send the following
stack trace and this message to us...@openejb.apache.org :
 org.apache.xbean.recipe.ConstructionException: Error invoking constructor:
public org.apache.tomee.catalina.TomcatSecurityService()
at
org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:968)
at
org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:276)
at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96)
at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61)
at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49)
at
org.apache.openejb.assembler.classic.Assembler.createSecurityService(Assembler.java:2517)
at
org.apache.openejb.assembler.classic.Assembler.buildContainerSystem(Assembler.java:498)
at org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:420)
at org.apache.openejb.OpenEJB$Instance.(OpenEJB.java:150)
at org.apache.openejb.OpenEJB.init(OpenEJB.java:298)
at org.apache.tomee.catalina.TomcatLoader.initialize(TomcatLoader.java:253)
at org.apache.tomee.catalina.ServerListener.install(ServerListener.java:168)
at
org.apache.tomee.catalina.ServerListener.lifecycleEvent(ServerListener.java:55)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at
org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:110)
at org.apache.catalina.startup.Catalina.load(Catalina.java:638)
at org.apache.catalina.startup.Catalina.load(Catalina.java:663)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:280)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:454)
Caused by: java.lang.NoClassDefFoundError:
org/apache/geronimo/osgi/locator/ProviderLocator
at
javax.security.jacc.PolicyConfigurationFactory$1.run(PolicyConfigurationFactory.java:89)
at java.security.AccessController.doPrivileged(Native Method)
at
javax.security.jacc.PolicyConfigurationFactory.getPolicyConfigurationFactory(PolicyConfigurationFactory.java:80)
at
org.apache.openejb.core.security.AbstractSecurityService.installJacc(AbstractSecurityService.java:314)
at
org.apache.openejb.core.security.AbstractSecurityService.(AbstractSecurityService.java:77)
at
org.apache.openejb.core.security.AbstractSecurityService.(AbstractSecurityService.java:71)
at
org.apache.tomee.catalina.TomcatSecurityService.(TomcatSecurityService.java:51)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:408)
at
org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:958)
... 24 more
Caused by: java.lang.ClassNotFoundException:
org.apache.geronimo.osgi.locator.ProviderLocator
at java.net.URLClassLoader$1.run(URLClassLoader.java:372)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:360)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 36 more

Aug 15, 2014 12:19:36 PM org.apache.openejb.OpenEJB$Instance 
SEVERE: OpenEJB has encountered a fatal error and cannot be started:
Assembler failed to build the container system.
org.apache.openejb.OpenEJBException:
org.apache.xbean.recipe.ConstructionException: Error invoking constructor:
public org.apache.tomee.catalina.TomcatSecurityService(): Error invoking
constructor: public org.apache.tomee.catalina.TomcatSecurityService()
at org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:433)
at org.apache.openejb.OpenEJB$Instance.(OpenEJB.java:150)
at org.apache.openejb.OpenEJ

Re: Apache TomEE 1.7.0 Release

[Howard W. Smith, Jr.]

On Fri, Aug 15, 2014 at 9:57 AM, Hendrik Dev  wrote:

> Is there a roadmap for making TomEE JEE 7 compliant?
>

Quote below from http://t.co/ahbu6794su (at top of Andy's email, which
resolves to http://tomee.apache.org/tomee-1.7.0.html)

Java EE7 and Beyond

>From this point on the TomEE community will be focusing most of it's
efforts on TomEE 2.0.x, which will be the first TomEE Java EE 7 driven
version running on Apache Tomcat 8.x. It is more than likely that support
for Java SE 6 will be dropped so that Java SE 7 features can finally be
leveraged during the development process. We will of course continue to
maintain the 1.7.x branch for the foreseeable future.

Re: Apache TomEE 1.7.0 Release

[Howard W. Smith, Jr.]

Congratulations and thank you for TomEE!!! Especially, for posting the
release to the mail list, which I follow more than any other TomEE channel.
:)



On Fri, Aug 15, 2014 at 8:58 AM, Andy Gumbrecht 
wrote:

> Boom!!! @ApacheTomEE 1.7.0 release rocks @TheASF world today -
> http://tomee.apache.org 
>
> Hi Absolutely Everyone,
>
> Finally, we made it through the vote. We are so proud and extremely happy
> to bring you Apache TomEE 1.7.0 today.
>
> Thanks go out to everyone for making the TomEE community such a great
> place to work. You all deserve a huge pat on the back.
>
> We sincerely hope that this release brings smiles to your faces and
> performance to your world.
>
> Please tweet and announce the news to all your circles and friends and
> followers. We really appreciate your support.
>
> The Maven 1.7.0 binaries may take a day or so to filter out to Maven
> Central, so please be patient when trying to build your Maven projects.
>
> Core development will now move to the TomEE 2.x EE7 binaries, but the
> 1.7.x branch will also be a active for the foreseeable future.
>
> Have a great weekend, and enjoy!
>
> Andy.
>
> --
>   Andy Gumbrecht
>
>   http://www.tomitribe.com
>   agumbre...@tomitribe.com
>   https://twitter.com/AndyGeeDe
>
>   TomEE treibt Tomitribe! | http://tomee.apache.org
>
>

Re: Tomee 2 Release-Date

[Howard W. Smith, Jr.]

good stuff, you all keep up the good work/progress!


On Mon, Jul 28, 2014 at 7:52 AM, Romain Manni-Bucau 
wrote:

> Hi
>
> will surely be beginning of next year in the best case even if I'd
> like to get a pre release end of this year without all EE 7 features.
> We miss CDI 1.1 and JPA 2.1 to target EE 7  web profile ATM (work in
> progress for CDI, JPA will be tackled after I think).
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-07-28 13:46 GMT+02:00 Andy Gumbrecht :
> > Hi thanhvinh,
> >
> > You're kind of jumping the gun there.
> >
> > We've not even released 1.7.0 yet, so it's kind of hard to map out
> anything
> > yet.
> >
> > TomEE 2.0.0-SNAPSHOT is in progress, but we do not have a solid roadmap
> yet.
> > We will work on producing some information as soon as we can.
> >
> > Of course feel free to dig into the progress of the SNAPSHOT.
> >
> > Andy.
> >
> >
> > On 27/07/2014 20:40, thanhvinh wrote:
> >>
> >> Hi all,
> >> NetBeans 8 now supported TomEE.  That's a good news.  I'm going to build
> >> my
> >> apps based on NB 8, Tomcat 8, Java EE 7.
> >> So I need to use TomEE 2.  Can you please give us a update on the
> release
> >> date of TomEE 2?
> >> Thanks.
> >>
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >>
> http://tomee-openejb.979440.n4.nabble.com/Tomee-2-Release-Date-tp4670783.html
> >> Sent from the TomEE Users mailing list archive at Nabble.com.
> >>
> >>
> >
> > --
> >   Andy Gumbrecht
> >
> >   http://www.tomitribe.com
> >   agumbre...@tomitribe.com
> >   https://twitter.com/AndyGeeDe
> >
> >   TomEE treibt Tomitribe! | http://tomee.apache.org
> >
>

Re: question around entityManager.flush

[Howard W. Smith, Jr.]

okay, I will have to try that, asap, and report my/some test results.
thanks.



On Wed, May 21, 2014 at 3:54 PM, Romain Manni-Bucau
wrote:

> more or less. Try to get a single transaction (ejb call if you want) by
> request.
>
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-05-21 21:52 GMT+02:00 Howard W. Smith, Jr. :
>
> > On Wed, May 21, 2014 at 3:42 PM, Romain Manni-Bucau
> > wrote:
> >
> > > what I say is you can do eveything in a single method method.
> >
> >
> > Sounds like you are recommending something similar to the following:
> >
> > 1. @RequestScoped bean to get data to display in UI layer to enduser
> >
> > 2. If user modifies data, and data is submitted from client/UI to
> > server/bean (@Session/ViewScoped/RequestScoped), then pass modified
> @Entity
> > from Session/View/RequestScoped bean to @Stateless @EJB, and
> >
> > 3. @Stateless @EJB method(@Entity entity) does the following:
> >
> > a. find entity via SELECT or find
> > b. foundEntity.property = entity.property
> > c. repeat step 'b.' above for all properties
> > d. edit(foundEntity)
> >
> > are you recommending something like this (above)?
> >
> >
> >
> >
> > > The fact you need flush means your operation need a state provided by
> the
> > > database (@GeneratedValue?).
> > >
> > >
> > public class AuditTrail implements Serializable {
> > private static final long serialVersionUID = 1L;
> > @Id
> > @GeneratedValue(strategy = GenerationType.IDENTITY)
> > @Basic(optional = false)
> > @NotNull
> > @Column(name = "AUDIT_TRAIL_ID")
> > private Integer auditTrailId;
> >
>

Re: question around entityManager.flush

[Howard W. Smith, Jr.]

On Wed, May 21, 2014 at 3:42 PM, Romain Manni-Bucau
wrote:

> what I say is you can do eveything in a single method method.


Sounds like you are recommending something similar to the following:

1. @RequestScoped bean to get data to display in UI layer to enduser

2. If user modifies data, and data is submitted from client/UI to
server/bean (@Session/ViewScoped/RequestScoped), then pass modified @Entity
from Session/View/RequestScoped bean to @Stateless @EJB, and

3. @Stateless @EJB method(@Entity entity) does the following:

a. find entity via SELECT or find
b. foundEntity.property = entity.property
c. repeat step 'b.' above for all properties
d. edit(foundEntity)

are you recommending something like this (above)?




> The fact you need flush means your operation need a state provided by the
> database (@GeneratedValue?).
>
>
public class AuditTrail implements Serializable {
private static final long serialVersionUID = 1L;
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
@Basic(optional = false)
@NotNull
@Column(name = "AUDIT_TRAIL_ID")
private Integer auditTrailId;

Re: question around entityManager.flush

[Howard W. Smith, Jr.]

hmmm, create -> edit is useless?

I guess you are saying that after i 'create', even though I am adding a
related entity (e.g. tree 'has' branch).

create(tree)

Branch branch = new Branch(1)
tree.addBranch(branch)

so, you are saying that the edit(tree) is not necessary? is that the cause
of the issue that i experience when I remove entityManager.flush() ?




On Wed, May 21, 2014 at 3:31 PM, Romain Manni-Bucau
wrote:

> then the issue is the code you do needs atomicity for each JPA operation
> (why you use flush). but this shouldn't be needed. Typically: create ->
> edit is useless. Just create it once ;)
>
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-05-21 21:29 GMT+02:00 Howard W. Smith, Jr. :
>
> > okay, based on what you said below,
> >
> > On Wed, May 21, 2014 at 2:42 PM, Romain Manni-Bucau
> > wrote:
> >
> > > @Stateless // or singletong
> > > public class TxBean {
> > >@PersistenceContext EntityManager em;
> > >
> > > public void doSomeStuffAndCommit() {
> > > // em usage
> > > }
> > > }
> > >
> > >
> > > when exiting the method commit will trigger flush
> > >
> >
> > my @Stateless EJB has doSomeStuffAndCommit(), but doSomeStuffAndCommit()
> is
> > 'usually' SQL SELECTs, and in my Abstract class for @Stateless @EJB, I
> have
> > the following:
> >
> > protected abstract EntityManager getEntityManager();
> >
> > public void create(T entity) {
> > // 2011-09-17 flush immediately after persist/create
> > getEntityManager().persist(entity);
> > getEntityManager().flush();
> > }
> >
> > public void create(T entity, Boolean flush) {
> > getEntityManager().persist(entity);
> > if (flush) getEntityManager().flush();
> > }
> >
> > public void edit(T entity) {
> > // 2011-09-17 flush immediately after merge
> > getEntityManager().merge(entity);
> > getEntityManager().flush();
> > }
> >
> > public void edit(T entity, Boolean flush) {
> > getEntityManager().merge(entity);
> > if (flush) getEntityManager().flush();
> > }
> >
> > public void flush() {
> > getEntityManager().flush();
> > }
> >
> > public void remove(T entity) {
> > // 2011-09-17 flush immediately after remove/merge the
> > managed/detached entity
> > getEntityManager().remove(getEntityManager().merge(entity));
> > getEntityManager().flush();
> > }
> >
> > public void remove(T entity, Boolean flush) {
> > getEntityManager().remove(getEntityManager().merge(entity));
> > if (flush) getEntityManager().flush();
> > }
> >
> >
> > majority of my app, calls the create(T entity), edit(T entity), and
> > remove(T entity) methods above where flush() is called after the
> > entityManager operation.
> >
> > below, is a method I have in a @Singleton bean that is called via
> @Schedule
> > to get some data from email account and write data to database.
> >
> > again, the method below is only one of the methods that is in the
> > @Singleton bean.
> >
> > private void createAuditTrail(String relatedEntityName,
> >  Object relatedEntityObj,
> >  String description) {
> >
> > AuditTrail current = new AuditTrail();
> > current.setDescriptionTx(description);
> > try {
> > Users user = getUser("system");
> > if (user == null) {
> > logger.info("Error adding AUDIT TRAIL; 'system' user
> does
> > not exist");
> > return;
> > }
> > current.setUserName(user);
> > current.setAuditTrailId(1);
> > current.setAuditTrailDt(new Date());
> > ejbFacadeAuditTrail.create(current);
> > // add auditTrail to order
> > if (relatedEntityName.equals("orders")) {
> > Orders order = (Orders) relatedEntityObj;
> > current.addOrder(order);
> > ejbFacadeAuditTrail.edit(current);
> > }
> > } catch (Exceptio

Re: question around entityManager.flush

[Howard W. Smith, Jr.]

okay, based on what you said below,

On Wed, May 21, 2014 at 2:42 PM, Romain Manni-Bucau
wrote:

> @Stateless // or singletong
> public class TxBean {
>@PersistenceContext EntityManager em;
>
> public void doSomeStuffAndCommit() {
> // em usage
> }
> }
>
>
> when exiting the method commit will trigger flush
>

my @Stateless EJB has doSomeStuffAndCommit(), but doSomeStuffAndCommit() is
'usually' SQL SELECTs, and in my Abstract class for @Stateless @EJB, I have
the following:

protected abstract EntityManager getEntityManager();

public void create(T entity) {
// 2011-09-17 flush immediately after persist/create
getEntityManager().persist(entity);
getEntityManager().flush();
}

public void create(T entity, Boolean flush) {
getEntityManager().persist(entity);
if (flush) getEntityManager().flush();
}

public void edit(T entity) {
// 2011-09-17 flush immediately after merge
getEntityManager().merge(entity);
getEntityManager().flush();
}

public void edit(T entity, Boolean flush) {
getEntityManager().merge(entity);
if (flush) getEntityManager().flush();
}

public void flush() {
getEntityManager().flush();
}

public void remove(T entity) {
// 2011-09-17 flush immediately after remove/merge the
managed/detached entity
getEntityManager().remove(getEntityManager().merge(entity));
getEntityManager().flush();
}

public void remove(T entity, Boolean flush) {
getEntityManager().remove(getEntityManager().merge(entity));
if (flush) getEntityManager().flush();
}


majority of my app, calls the create(T entity), edit(T entity), and
remove(T entity) methods above where flush() is called after the
entityManager operation.

below, is a method I have in a @Singleton bean that is called via @Schedule
to get some data from email account and write data to database.

again, the method below is only one of the methods that is in the
@Singleton bean.

private void createAuditTrail(String relatedEntityName,
 Object relatedEntityObj,
 String description) {

AuditTrail current = new AuditTrail();
current.setDescriptionTx(description);
try {
Users user = getUser("system");
if (user == null) {
logger.info("Error adding AUDIT TRAIL; 'system' user does
not exist");
return;
}
current.setUserName(user);
current.setAuditTrailId(1);
current.setAuditTrailDt(new Date());
ejbFacadeAuditTrail.create(current);
// add auditTrail to order
if (relatedEntityName.equals("orders")) {
Orders order = (Orders) relatedEntityObj;
current.addOrder(order);
ejbFacadeAuditTrail.edit(current);
}
} catch (Exception e) {
logger.info("Error adding AUDIT TRAIL" +
(e.getMessage() != null ? "; " + e.getMessage() :
""));
}
}


Majority of my app is CDI @SessionScoped or @ViewScoped beans that call
@Stateless @EJB to select/create/update/delete data in database.

CDI @SessionScoped and @ViewScoped beans will get data via @Stateless @EJB,
and CDI @SessionScoped and @ViewScoped beans may do some data manipulation,
and then @Stateless @EJB is called to do the entityManager create(),
edit(), remove() to update database, accordingly.

The only time I write a lot of logic in @EJBs is when I am preparing for
SQL SELECT.

The @Singleton bean example code that I provided above is one of only
(@Singleton) @EJBs that have a lot of code that does a specific job.

So, when I removed entityManager.flush() from my Abstract class, earlier,
per Jean-Louis's recommendation, some data was saved to database by
@Singleton and most of the data was 'not' saved to database.

Definition of @Singleton is below:

@Singleton
@Lock(LockType.WRITE)
@AccessTimeout(value = 2, unit = TimeUnit.MINUTES)
public class AddEmailRequest {

Re: question around entityManager.flush

[Howard W. Smith, Jr.]

Andy, is there any sample code or blog or tomee test case that demonstrates
your recommendation?



On Wed, May 21, 2014 at 11:37 AM, Andy Gumbrecht
wrote:

> Which is why I used the additional local EJB in the past, basically where
> it 'feels' like a flush is being helpful replace the logic with a local
> bean that does that unit of work.
> Look up and call that bean method from the current method, if it completes
> then the current method is safe to complete. An explicit flush in an EJB
> context is 'usually' a hack.
>
> Andy.
>
>
> On 21/05/2014 17:19, Jean-Louis Monteiro wrote:
>
>> you should have mentioned that before. Eclipselink is a bit special 
>>
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>>
>>
>> On Wed, May 21, 2014 at 8:16 AM, Romain Manni-Bucau
>> wrote:
>>
>>  cause eclipselink ;)
>>>
>>>
>>>
>>> Romain Manni-Bucau
>>> Twitter: @rmannibucau
>>> Blog: http://rmannibucau.wordpress.com/
>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>> Github: https://github.com/rmannibucau
>>>
>>>
>>> 2014-05-21 17:11 GMT+02:00 Jean-Louis Monteiro >> >:
>>>
>>>  I don't see why, except if you are explicitly checking for database
>>>> constraints in your code.
>>>> Because, the default JDBC connection isolation level is READ COMMITTED
>>>> AFAIR or REPEATABLE_READ for MySQL.
>>>>
>>>> Anyway, that means that you can never read uncommitted data.
>>>>
>>>> JLouis
>>>>
>>>> --
>>>> Jean-Louis Monteiro
>>>> http://twitter.com/jlouismonteiro
>>>> http://www.tomitribe.com
>>>>
>>>>
>>>> On Wed, May 21, 2014 at 7:58 AM, Howard W. Smith, Jr. <
>>>> smithh032...@gmail.com> wrote:
>>>>
>>>>  removing the manual/forced entityManager.flush() broke my app in a few
>>>>> places. reverting to previous version and I may try to revisit this
>>>>>
>>>> later.
>>>>
>>>>> :)
>>>>>
>>>>>
>>>>>
>>>>> On Wed, May 21, 2014 at 10:00 AM, Howard W. Smith, Jr. <
>>>>> smithh032...@gmail.com> wrote:
>>>>>
>>>>>  Thanks Jean-Louis. Based on your response, i just commented out
>>>>>> entityManager.flush() in my AbstractFacade.java for create, edit, and
>>>>>> remove methods.
>>>>>>
>>>>>> i did some testing in my app, and seems to work well. will see how my
>>>>>>
>>>>> app
>>>>
>>>>> performs under load and when users are logged in and working,
>>>>>>
>>>>> concurrently.
>>>>>
>>>>>> thanks again.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, May 21, 2014 at 5:21 AM, Jean-Louis Monteiro <
>>>>>> jlmonte...@tomitribe.com> wrote:
>>>>>>
>>>>>>  As a general rule, I would recommend to never call flush(). The JPA
>>>>>>> provider optimizing the flushing to avoid connections between the
>>>>>>> Persistence Context and the rdbms.
>>>>>>>
>>>>>>> Of course at least at the end of the transaction (commit) the JPA
>>>>>>>
>>>>>> provider
>>>>>
>>>>>> flushes.
>>>>>>> But for example, when you have a loop with search, read, update 
>>>>>>>
>>>>>> the
>>>>
>>>>> JPA provider is able to detect that there is a risk of dealing with
>>>>>>>
>>>>>> stale
>>>>>
>>>>>> object and will therefor flush as well.
>>>>>>>
>>>>>>> The only case I call flush is basically when as mentioned already, I
>>>>>>>
>>>>>> need
>>>>>
>>>>>> to check database constraints (Unique, etc).
>>>>>>> The only reason is that I want to explicitly catch the exception
>>>>>>>
>>>>>> either
>>>>
>>>>> to
>>>>>
>>>>>> ignore, retry, or rethrow using a business exception.
>>>>>>>
>

Re: question around entityManager.flush

[Howard W. Smith, Jr.]

On Wed, May 21, 2014 at 11:19 AM, Jean-Louis Monteiro <
jlmonte...@tomitribe.com> wrote:

> you should have mentioned that before. Eclipselink is a bit special 


yeah, i love it (EclipseLink)! Gets the job done for me... EclipseLink
2.3.2 (that shipped with earlier version of Glassfish 3.1.x).  :)

Re: question around entityManager.flush

[Howard W. Smith, Jr.]

On Wed, May 21, 2014 at 11:16 AM, Romain Manni-Bucau
wrote:

> cause eclipselink ;)


+1 good memory, Romain! :)

Re: question around entityManager.flush

[Howard W. Smith, Jr.]

removing the manual/forced entityManager.flush() broke my app in a few
places. reverting to previous version and I may try to revisit this later.
:)



On Wed, May 21, 2014 at 10:00 AM, Howard W. Smith, Jr. <
smithh032...@gmail.com> wrote:

> Thanks Jean-Louis. Based on your response, i just commented out
> entityManager.flush() in my AbstractFacade.java for create, edit, and
> remove methods.
>
> i did some testing in my app, and seems to work well. will see how my app
> performs under load and when users are logged in and working, concurrently.
>
> thanks again.
>
>
>
> On Wed, May 21, 2014 at 5:21 AM, Jean-Louis Monteiro <
> jlmonte...@tomitribe.com> wrote:
>
>> As a general rule, I would recommend to never call flush(). The JPA
>> provider optimizing the flushing to avoid connections between the
>> Persistence Context and the rdbms.
>>
>> Of course at least at the end of the transaction (commit) the JPA provider
>> flushes.
>> But for example, when you have a loop with search, read, update  the
>> JPA provider is able to detect that there is a risk of dealing with stale
>> object and will therefor flush as well.
>>
>> The only case I call flush is basically when as mentioned already, I need
>> to check database constraints (Unique, etc).
>> The only reason is that I want to explicitly catch the exception either to
>> ignore, retry, or rethrow using a business exception.
>>
>> Sometimes, I also use an ejb with a REQUIRES_NEW, so that the current
>> transaction is suspended and a new one is created. Then, if an exception
>> occurs at commit time, I can catch in the current bean without changing
>> the
>> status of the current transaction.
>>
>> JLouis
>>
>>
>>
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>>
>>
>> On Mon, May 19, 2014 at 8:47 AM, Howard W. Smith, Jr. <
>> smithh032...@gmail.com> wrote:
>>
>> > Interesting question and answer.
>> >
>> > Per my 2+ year experience with Java EE 6, in my app, i used NetBeans to
>> > develop my JPA session facade (@EJB JPA DAO) classes, including abstract
>> > class. In the abstract class, in the create and edit methods, I did add
>> > flush(), so after every create and edit JPA request, data is written
>> > immediately.
>> >
>> > Honestly, I don't have any need to use @Scheduler or timer methods to
>> > ensure data is savedsuccessfully.
>> >
>> > In fact, I can maybe even remove flush(), but I have not done that
>> (yet).
>> > If I did remove flush() in my abstract class, then I would need to test
>> the
>> > app, accordingly, to see the impact.
>> >
>> > I really don't see any performance issues with my
>> approach/implementation,
>> > but the app does not have many concurrent
>> > users/database-update-requests/etc.
>> >
>> >
>> >
>> > On Mon, May 19, 2014 at 4:02 AM, Andy Gumbrecht <
>> agumbre...@tomitribe.com
>> > >wrote:
>> >
>> > > Hi there Radhakrishna,
>> > >
>> > >
>> > > On 19/05/2014 08:15, Radhakrishna Kalyan wrote:
>> > >
>> > >> Hi,
>> > >>
>> > >> I have question around entityManager.flush().
>> > >> Is it ok to call multiple times? Or will there be any performance
>> issue.
>> > >>
>> > > Every time you hit the the database you will take a performance hit
>> back
>> > -
>> > > How much is impossible to say and is very dependant on what your app
>> is
>> > > doing. Just always think along the lines of 'how can I do this with
>> less'
>> > > and you'll be fine.
>> > >
>> > >
>> > >> My case is, I have a timer service which executes periodically where
>> I
>> > >> create a database entity using a dao object using
>> > entityManager.persist(),
>> > >> after that I also  call entityManager.flush().
>> > >>
>> > >> The reason to do so is, if database commit fails due to certain
>> reason
>> > >> like
>> > >> unique constrain exception then I want the timer service to send a
>> JMS
>> > >> message.
>> > >>
>> > > What you are doing is not necessarily wrong, but why not just let the
>> > > container do the work for you. The container managed transactio

Re: question around entityManager.flush

[Howard W. Smith, Jr.]

Thanks Jean-Louis. Based on your response, i just commented out
entityManager.flush() in my AbstractFacade.java for create, edit, and
remove methods.

i did some testing in my app, and seems to work well. will see how my app
performs under load and when users are logged in and working, concurrently.

thanks again.



On Wed, May 21, 2014 at 5:21 AM, Jean-Louis Monteiro <
jlmonte...@tomitribe.com> wrote:

> As a general rule, I would recommend to never call flush(). The JPA
> provider optimizing the flushing to avoid connections between the
> Persistence Context and the rdbms.
>
> Of course at least at the end of the transaction (commit) the JPA provider
> flushes.
> But for example, when you have a loop with search, read, update  the
> JPA provider is able to detect that there is a risk of dealing with stale
> object and will therefor flush as well.
>
> The only case I call flush is basically when as mentioned already, I need
> to check database constraints (Unique, etc).
> The only reason is that I want to explicitly catch the exception either to
> ignore, retry, or rethrow using a business exception.
>
> Sometimes, I also use an ejb with a REQUIRES_NEW, so that the current
> transaction is suspended and a new one is created. Then, if an exception
> occurs at commit time, I can catch in the current bean without changing the
> status of the current transaction.
>
> JLouis
>
>
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Mon, May 19, 2014 at 8:47 AM, Howard W. Smith, Jr. <
> smithh032...@gmail.com> wrote:
>
> > Interesting question and answer.
> >
> > Per my 2+ year experience with Java EE 6, in my app, i used NetBeans to
> > develop my JPA session facade (@EJB JPA DAO) classes, including abstract
> > class. In the abstract class, in the create and edit methods, I did add
> > flush(), so after every create and edit JPA request, data is written
> > immediately.
> >
> > Honestly, I don't have any need to use @Scheduler or timer methods to
> > ensure data is savedsuccessfully.
> >
> > In fact, I can maybe even remove flush(), but I have not done that (yet).
> > If I did remove flush() in my abstract class, then I would need to test
> the
> > app, accordingly, to see the impact.
> >
> > I really don't see any performance issues with my
> approach/implementation,
> > but the app does not have many concurrent
> > users/database-update-requests/etc.
> >
> >
> >
> > On Mon, May 19, 2014 at 4:02 AM, Andy Gumbrecht <
> agumbre...@tomitribe.com
> > >wrote:
> >
> > > Hi there Radhakrishna,
> > >
> > >
> > > On 19/05/2014 08:15, Radhakrishna Kalyan wrote:
> > >
> > >> Hi,
> > >>
> > >> I have question around entityManager.flush().
> > >> Is it ok to call multiple times? Or will there be any performance
> issue.
> > >>
> > > Every time you hit the the database you will take a performance hit
> back
> > -
> > > How much is impossible to say and is very dependant on what your app is
> > > doing. Just always think along the lines of 'how can I do this with
> less'
> > > and you'll be fine.
> > >
> > >
> > >> My case is, I have a timer service which executes periodically where I
> > >> create a database entity using a dao object using
> > entityManager.persist(),
> > >> after that I also  call entityManager.flush().
> > >>
> > >> The reason to do so is, if database commit fails due to certain reason
> > >> like
> > >> unique constrain exception then I want the timer service to send a JMS
> > >> message.
> > >>
> > > What you are doing is not necessarily wrong, but why not just let the
> > > container do the work for you. The container managed transactions are
> > your
> > > friend.
> > >
> > >
> > >> If I don't call entityManager.flush() then I am not able to catch any
> > >> exception in my timer service thus fails to send any JMS message.
> > >>
> > > In your service look up another local bean that handles the persistence
> > >  and if required sends a message on success, this will all run in a
> > > transacted context - The success message will only be sent if the bean
> > > method actually completes.
> > > If the bean method call fails then you can catch the error and do the
> > > extra leg work to send the 'fail' message.
> > >
> > >
> > >> However at the end the database entity is never created which is
> > correct.
> > >> But if I can't able to send the JMS message upon exception then I does
> > not
> > >> meet the requirement.
> > >>
> > >> Any ideas or recommendations to do it in a better way
> > >>
> > >>
> > >>  So I guess my suggestion is to not try and do all the work in the
> timer
> > > service method, rather call another bean method do do the work.
> > >
> > > Andy.
> > >
> > > --
> > >   Andy Gumbrecht
> > >
> > >   http://www.tomitribe.com
> > >   agumbre...@tomitribe.com
> > >   https://twitter.com/AndyGeeDe
> > >
> > >   TomEE treibt Tomitribe! | http://tomee.apache.org
> > >
> > >
> >
>

Re: Netbeans Users

[Howard W. Smith, Jr.]

Andy,

I used NetBeans to develop my first Java EE 6 (JSF web) application.
Initially, I used Glassfish 3.1.x, and then migrated to TomEE
1.5.1-snapshot, and have been using TomEE 1.x ever since.

I usually just build WAR file and drop the WAR file from NetBeans 'dist'
folder into tomee/webapps folder...manually. I don't like hot deploy and
restart. i rather start and stop, drop WAR file, start, stop, ...

I usually have issues with NetBeans running my app in debug mode when
deploying to TomEE, so I avoid using debug mode  (no complaints here).

Thanks,
Howard



On Tue, May 20, 2014 at 4:30 AM, Andy Gumbrecht wrote:

> Hi Everyone,
>
> I am chatting with some of the Netbeans team in regards to how their IDE
> fits into the TomEE picture.
> I have used Netbeans in the past and think it is a great tool, but for the
> last few years it's been Intellij-IDEA on my desk.
>
> I'd like to get your feedback on who is using Netbeans, and what for?
>
> Thanks for your time, happy hacking.
>
> Andy.
>
> --
>   Andy Gumbrecht
>
>   http://www.tomitribe.com
>   agumbre...@tomitribe.com
>   https://twitter.com/AndyGeeDe
>
>   TomEE treibt Tomitribe! | http://tomee.apache.org
>
>

Re: question around entityManager.flush

[Howard W. Smith, Jr.]

Interesting question and answer.

Per my 2+ year experience with Java EE 6, in my app, i used NetBeans to
develop my JPA session facade (@EJB JPA DAO) classes, including abstract
class. In the abstract class, in the create and edit methods, I did add
flush(), so after every create and edit JPA request, data is written
immediately.

Honestly, I don't have any need to use @Scheduler or timer methods to
ensure data is savedsuccessfully.

In fact, I can maybe even remove flush(), but I have not done that (yet).
If I did remove flush() in my abstract class, then I would need to test the
app, accordingly, to see the impact.

I really don't see any performance issues with my approach/implementation,
but the app does not have many concurrent
users/database-update-requests/etc.



On Mon, May 19, 2014 at 4:02 AM, Andy Gumbrecht wrote:

> Hi there Radhakrishna,
>
>
> On 19/05/2014 08:15, Radhakrishna Kalyan wrote:
>
>> Hi,
>>
>> I have question around entityManager.flush().
>> Is it ok to call multiple times? Or will there be any performance issue.
>>
> Every time you hit the the database you will take a performance hit back -
> How much is impossible to say and is very dependant on what your app is
> doing. Just always think along the lines of 'how can I do this with less'
> and you'll be fine.
>
>
>> My case is, I have a timer service which executes periodically where I
>> create a database entity using a dao object using entityManager.persist(),
>> after that I also  call entityManager.flush().
>>
>> The reason to do so is, if database commit fails due to certain reason
>> like
>> unique constrain exception then I want the timer service to send a JMS
>> message.
>>
> What you are doing is not necessarily wrong, but why not just let the
> container do the work for you. The container managed transactions are your
> friend.
>
>
>> If I don't call entityManager.flush() then I am not able to catch any
>> exception in my timer service thus fails to send any JMS message.
>>
> In your service look up another local bean that handles the persistence
>  and if required sends a message on success, this will all run in a
> transacted context - The success message will only be sent if the bean
> method actually completes.
> If the bean method call fails then you can catch the error and do the
> extra leg work to send the 'fail' message.
>
>
>> However at the end the database entity is never created which is correct.
>> But if I can't able to send the JMS message upon exception then I does not
>> meet the requirement.
>>
>> Any ideas or recommendations to do it in a better way
>>
>>
>>  So I guess my suggestion is to not try and do all the work in the timer
> service method, rather call another bean method do do the work.
>
> Andy.
>
> --
>   Andy Gumbrecht
>
>   http://www.tomitribe.com
>   agumbre...@tomitribe.com
>   https://twitter.com/AndyGeeDe
>
>   TomEE treibt Tomitribe! | http://tomee.apache.org
>
>

Re: Remote Asynchronous EJB Method call followed quickly by client exit

[Howard W. Smith, Jr.]

On Fri, May 16, 2014 at 12:03 PM, Thiago Veronezi wrote:

> The list is still messed up. I'm trying to follow up the emails, but they
> are coming out of order.
>
> []s,
> Thiago
>

remember, there was an issue with Apache [email] servers, at least that is
what i heard on tomcat user list. :)

Re: CDI not working inside EAR with Atmosphere (BeanManager)

[Howard W. Smith, Jr.]

José,

When you get a chance, can you retest your test case with Romain's fix
(below), and report your test results ?



On Tue, Apr 22, 2014 at 7:17 PM, Romain Manni-Bucau
wrote:

> surely linked to https://issues.apache.org/jira/browse/TOMEE-1183
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-04-22 18:36 GMT+02:00 José Luis Cetina :
> > My tomee runs already under C:\tomee, in the related topic, i uploaded a
> > maven project that you can check it, this is a TomEE problem.
> >
> >
> > 2014-04-22 11:28 GMT-05:00 Romain Manni-Bucau :
> >
> >> Well first check basic things like spaces etc, can be a hidden bug
> >> until now. Basically try to deploy in c:\tomee. If the issue is still
> >> here we'll try to have a deeper look. But we have a lot of win users
> >> and a really blocking win issue would have popped earlier I guess.
> >>
> >>
> >> Romain Manni-Bucau
> >> Twitter: @rmannibucau
> >> Blog: http://rmannibucau.wordpress.com/
> >> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> >> Github: https://github.com/rmannibucau
> >>
> >>
> >> 2014-04-22 18:25 GMT+02:00 José Luis Cetina :
> >> > Hi, my problem was i mean IS with CODI using Windows.
> >> >
> >> > Here is the conversation:
> >> >
> >>
> http://openejb.979440.n4.nabble.com/No-bean-found-for-type-org-apache-myfaces-extensions-cdi-jsf-api-config-JsfModuleConfig-td454.html
> >> >
> >> > @Romain, maybe this is realted i hope you can have a windows pc for
> check
> >> > it!!
> >> >
> >> >
> >> >
> >> > 2014-04-22 11:09 GMT-05:00 Howard W. Smith, Jr. <
> smithh032...@gmail.com
> >> >:
> >> >
> >> >> Jose' can advise on this when he gets some time. Jose' is doing EARs
> +
> >> CDI
> >> >> + TomEE for some/many months now.
> >> >>
> >> >> Jose', please advise on this topic at your earliest convenience.
> >> >>
> >> >> I think Jose' had to use BeanManager and had to use the JNDI name
> >> specified
> >> >> in the tomee/catalina log when tomee starts. I could be wrong.
> >> >>
> >> >>
> >> >>
> >> >> On Tue, Apr 22, 2014 at 12:04 PM, Lars Knemeyer <
> >> lars.kneme...@gmail.com
> >> >> >wrote:
> >> >>
> >> >> > Ok, the problem seems to be platform-related.
> >> >> >
> >> >> > I started the same TomEE 1.6.1 SNAPHOT on two Windows 7 systems and
> >> one
> >> >> > Windows Server 2008 R2 (all with the latest JDK 7_55) and it
> failed in
> >> >> all
> >> >> > three cases (with the described error).
> >> >> > Then I started the same TomEE server (I used the same prepared zip
> in
> >> all
> >> >> > cases) on a (virtual) Ubuntu 13.10 machine with OpenJDK as well as
> >> Oracle
> >> >> > JDK and in both cases the sample worked without a problem (as you
> >> >> described
> >> >> > it).
> >> >> >
> >> >> > So it seems to be a Windows-specific problem (I first suspected
> it's
> >> the
> >> >> > Oracle JDK, but it works with that also on Ubuntu). I just don't
> know
> >> >> what
> >> >> > to do with this finding.
> >> >> >
> >> >> >
> >> >> >
> >> >> > --
> >> >> > View this message in context:
> >> >> >
> >> >>
> >>
> http://openejb.979440.n4.nabble.com/CDI-not-working-inside-EAR-with-Atmosphere-BeanManager-tp4668939p4668948.html
> >> >> > Sent from the OpenEJB User mailing list archive at Nabble.com.
> >> >> >
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > ---
> >> > *José Luis Cetina*
> >> > ---
> >>
> >
> >
> >
> > --
> > ---
> > *José Luis Cetina*
> > ---
>

Re: CDI not working inside EAR with Atmosphere (BeanManager)

[Howard W. Smith, Jr.]

Jose' can advise on this when he gets some time. Jose' is doing EARs + CDI
+ TomEE for some/many months now.

Jose', please advise on this topic at your earliest convenience.

I think Jose' had to use BeanManager and had to use the JNDI name specified
in the tomee/catalina log when tomee starts. I could be wrong.



On Tue, Apr 22, 2014 at 12:04 PM, Lars Knemeyer wrote:

> Ok, the problem seems to be platform-related.
>
> I started the same TomEE 1.6.1 SNAPHOT on two Windows 7 systems and one
> Windows Server 2008 R2 (all with the latest JDK 7_55) and it failed in all
> three cases (with the described error).
> Then I started the same TomEE server (I used the same prepared zip in all
> cases) on a (virtual) Ubuntu 13.10 machine with OpenJDK as well as Oracle
> JDK and in both cases the sample worked without a problem (as you described
> it).
>
> So it seems to be a Windows-specific problem (I first suspected it's the
> Oracle JDK, but it works with that also on Ubuntu). I just don't know what
> to do with this finding.
>
>
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/CDI-not-working-inside-EAR-with-Atmosphere-BeanManager-tp4668939p4668948.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>

Re: Fat example for tomee.maven.plugin

[Howard W. Smith, Jr.]

Download button = emails sent to this list

Download = Romain's response from his brain (and fingers)

:-)

On Sat, Apr 12, 2014 at 6:11 AM, Karl Kildén  wrote:

> Can I download your brain somewhere?

Re: TomEE performance degrades gradually

[Howard W. Smith, Jr.]

+1 you all!



On Wed, Apr 9, 2014 at 1:31 PM, Romain Manni-Bucau wrote:

> FYI https://issues.apache.org/jira/browse/TOMEE-1175
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
>
> 2014-04-09 17:29 GMT+02:00 Romain Manni-Bucau :
> > I think that's related to
> > org.apache.openejb.core.ivm.BaseEjbProxyHandler#equals which seems no
> > more adapted
> >
> > Index:
> container/openejb-core/src/main/java/org/apache/openejb/core/ivm/BaseEjbProxyHandler.java
> > ===
> > ---
> container/openejb-core/src/main/java/org/apache/openejb/core/ivm/BaseEjbProxyHandler.java
> > (revision 1585987)
> > +++
> container/openejb-core/src/main/java/org/apache/openejb/core/ivm/BaseEjbProxyHandler.java
> > (working copy)
> > @@ -480,10 +480,12 @@
> >  if (obj == null) {
> >  return false;
> >  }
> > -try {
> > -obj = ProxyManager.getInvocationHandler(obj);
> > -} catch (final IllegalArgumentException e) {
> > -return false;
> > +if (!BaseEjbProxyHandler.class.isInstance(obj)) {
> > +try {
> > +obj = ProxyManager.getInvocationHandler(obj);
> > +} catch (final IllegalArgumentException e) {
> > +return false;
> > +}
> >  }
> >  if (this == obj) {
> >  return true;
> >
> >
> > should fix it
> > Romain Manni-Bucau
> > Twitter: @rmannibucau
> > Blog: http://rmannibucau.wordpress.com/
> > LinkedIn: http://fr.linkedin.com/in/rmannibucau
> > Github: https://github.com/rmannibucau
> >
> >
> >
> > 2014-04-09 14:21 GMT+02:00 Anthony Fryer :
> >> Hi Ivan,
> >>
> >> I duplicated your results using the test case you uploaded and saw a
> steady
> >> performance degredation.  I was wondering if this was related to jpa,
> or the
> >> fact you're using ejb2, so i created a similar test case using ejb 3
> entity
> >> beans, based on the "injection-of-entitymanager" test case.  My test
> case is
> >> here...
> >>
> >> injection-of-entitymanager.zip
> >> <
> http://openejb.979440.n4.nabble.com/file/n4668673/injection-of-entitymanager.zip
> >
> >>
> >> Thankfully, i'm not seeing the same issue using ejb 3, so it looks like
> the
> >> problem is isolated to the use of ejb2 cmp entity beans.
> >>
> >>
> >>
> >> --
> >> View this message in context:
> http://openejb.979440.n4.nabble.com/TomEE-performance-degrades-gradually-tp4668090p4668673.html
> >> Sent from the OpenEJB User mailing list archive at Nabble.com.
>

Re: TomEE performance degrades gradually

[Howard W. Smith, Jr.]

On Fri, Apr 4, 2014 at 7:21 AM, Jean-Louis MONTEIRO wrote:

> I tend to disagree with that.
> Each part of a system has it's own goal and scope.
>
> Database is for data so I tend to use it as much as possible for sorting,
> joining, etc, instead of relaying on Java for sorting collections or even
> JPA to get a parent, then all childs, then all childs but applying a
> filter.
>
> But I would agree on the sense that each part (App Server, Database, etc)
> must be tuned according to your SLA and the overall architecture.
> So yes, take care of returning a large resultset to avoid heavy GC
> workload, and check if you have an index and if it's used (explain in mysql
> or any other database specific way to check the execution plan).
>
> JLouis
>
>
+1 I agree, Jean-Louis. Thanks! :)

Re: TomEE performance degrades gradually

[Howard W. Smith, Jr.]

On Fri, Apr 4, 2014 at 7:07 AM, Howard W. Smith, Jr.  wrote:

> yes, I have some quite complex SQL, and when I profile the app (via
> jvisualvm), I find that Apache Derby source code is not performing well
> with [my] SQL and/or [my] database design, etc...


Correction, EclipseLink and/or Derby may not be performing well with 'my'
SQL in 'my' app. :)