[GitHub] [tomee] Daniel-Dos commented on issue #606: TOMEE-2734-Upgrade CXF to 3.3.4

[GitBox]

Daniel-Dos commented on issue #606: TOMEE-2734-Upgrade CXF to 3.3.4
URL: https://github.com/apache/tomee/pull/606#issuecomment-553670130
 
 
   ok . thanks :  )


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [tomee] jgallimore commented on issue #608: Ddded missing dependency for microprofile

[GitBox]

jgallimore commented on issue #608: Ddded missing dependency for microprofile
URL: https://github.com/apache/tomee/pull/608#issuecomment-553659193
 
 
   You could just make the change in your branch, commit and push again (which 
will update the PR here). Alternatively we could merge this, and you follow up 
with the refactor - that's also fine. New PR is also good. Shout if you get 
stuck, and thanks for giving this a go.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [tomee] asf-ci commented on issue #609: TOMEE-2739 use webcontext and the path to evaluate which context to a…

[GitBox]

asf-ci commented on issue #609: TOMEE-2739 use webcontext and the path to 
evaluate which context to a…
URL: https://github.com/apache/tomee/pull/609#issuecomment-553520737
 
 
   Can one of the admins verify this patch?


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [tomee] asf-ci commented on issue #609: TOMEE-2739 use webcontext and the path to evaluate which context to a…

[GitBox]

asf-ci commented on issue #609: TOMEE-2739 use webcontext and the path to 
evaluate which context to a…
URL: https://github.com/apache/tomee/pull/609#issuecomment-553520735
 
 
   Can one of the admins verify this patch?


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [tomee] asf-ci commented on issue #609: TOMEE-2739 use webcontext and the path to evaluate which context to a…

[GitBox]

asf-ci commented on issue #609: TOMEE-2739 use webcontext and the path to 
evaluate which context to a…
URL: https://github.com/apache/tomee/pull/609#issuecomment-553520741
 
 
   Can one of the admins verify this patch?


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [tomee] jgallimore opened a new pull request #609: TOMEE-2739 use webcontext and the path to evaluate which context to a…

[GitBox]

jgallimore opened a new pull request #609: TOMEE-2739 use webcontext and the 
path to evaluate which context to a…
URL: https://github.com/apache/tomee/pull/609
 
 
   …pply the filter to


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [tomee] scriptmonkey closed pull request #608: Ddded missing dependency for microprofile

[GitBox]

scriptmonkey closed pull request #608: Ddded missing dependency for microprofile
URL: https://github.com/apache/tomee/pull/608
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [tomee] scriptmonkey commented on issue #608: Ddded missing dependency for microprofile

[GitBox]

scriptmonkey commented on issue #608: Ddded missing dependency for microprofile
URL: https://github.com/apache/tomee/pull/608#issuecomment-553511003
 
 
   I will fix and make a new pull request.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: TomEE GraalVM native image

[Roberto Cortez]

GraalVM in JVM mode is still Hotspot with the GraalVM JIT compiler.

I would say that you should run some performance tests before doing the switch. 
In same workloads Graal JIT compiler performs better, some other cases Hotspot 
JIT compiler is better.

> On 13 Nov 2019, at 15:14, Richard Monson-Haefel  
> wrote:
> 
> Thanks, Roberto!  So, compiling with it is probably not going to be a
> priority, but running TomEE on it could be. I wonder if the
> performance advantages of using GraalVM over JVM is significant.
> 
> On Wed, Nov 13, 2019 at 8:46 AM Roberto Cortez 
> wrote:
> 
>> Hi,
>> 
>> Let me clarify that this repo:
>> https://github.com/tomitribe/graalvm-microprofile <
>> https://github.com/tomitribe/graalvm-microprofile>
>> 
>> Is just to play around with the polyglot features of GraalVM.
>> 
>> Building TomEE native images will be another story. I did try that when I
>> was playing with the other repo and there are a lot of things that fail.
>> This is not only about TomEE, but also about all the libraries used in
>> TomEE itself.
>> 
>> To be able to build to native image, you would need to comply with
>> Substrate VM limitations stated here:
>> https://github.com/oracle/graal/blob/master/substratevm/LIMITATIONS.md <
>> https://github.com/oracle/graal/blob/master/substratevm/LIMITATIONS.md>
>> 
>> For instance, projects like Quarkus or Micronaut removed all reflection
>> calls and resolve these at compile time rather than runtime. While it is
>> possible to instruct GraalVM about some reflection usage when doing the
>> native image, I believe it won’t be enough in TomEE case and most likely
>> some portions would need to be reimplemented. I have no idea what would be
>> the effort involved in a task like this. It is not trivial.
>> 
>> Cheers,
>> Roberto
>> 
>>> On 13 Nov 2019, at 12:55, Richard Monson-Haefel 
>> wrote:
>>> 
>>> Hi!
>>> 
>>> That would be cool. If memory serves there may be some issues with
>>> reflection and complication but running TomEE on GraalVM should work
>> since
>>> it won't try to compile the reflection stuff.  I haven't run it on
>> GraalVM
>>> myself, but this would be a really cool effort and if you can get it to
>>> work it would be an awesome addition to the project in my opinion.  Are
>> you
>>> interested in testing it out and working on it?
>>> 
>>> Richard
>>> 
>>> On Wed, Nov 13, 2019 at 5:35 AM COURTAULT Francois <
>>> francois.courta...@thalesgroup.com> wrote:
>>> 
 Hello everyone,
 
 I am able to see some initiatives around GraalVM native-image like
 Quarkus, Helidon,...
 I have also seen that Tomcat 9.0.26 could be built as a native image:
 http://tomcat.apache.org/tomcat-9.0-doc/graal.html
 
 Digging on the web, I discover some work on TomEE side as well:
 https://github.com/tomitribe/graalvm-microprofile
 
 Are you working on a TomEE version which can be built as a GraalVM
>> native
 image ?
 I think it should be a quite important topic to consider in the roadmap,
 right ?
 
 Best Regards.
 
 
 
 
 This message and any attachments are intended solely for the addressees
 and may contain confidential information. Any unauthorized use or
 disclosure, either whole or partial, is prohibited.
 E-mails are susceptible to alteration. Our company shall not be liable
>> for
 the message if altered, changed or falsified. If you are not the
>> intended
 recipient of this message, please delete it and notify the sender.
 Although all reasonable efforts have been made to keep this transmission
 free from viruses, the sender will not be liable for damages caused by a
 transmitted virus.
 
>>> 
>>> 
>>> --
>>> Richard Monson-Haefel
>>> https://twitter.com/rmonson
>>> https://www.linkedin.com/in/monsonhaefel/
>> 
>> 
> 
> -- 
> Richard Monson-Haefel
> https://twitter.com/rmonson
> https://www.linkedin.com/in/monsonhaefel/

Re: Re: Docker Images on Dockerhub

[Jenkins, Rodney J (Rod)]

I have submitted a pull request to fix this issue.  Please merge at your 
earlier convivence.

Jon, thank you for the guidance.

Thanks,
Rod.


On 11/8/19, 10:47 AM, "Jonathan Gallimore"  
wrote:


Looks like the microprofile distribution is missing jakarta.activation.
Adding that in (from the plus distribution) allows the server to start
correctly. I've filed a JIRA:
https://issues.apache.org/jira/browse/TOMEE-2731

I'm happy to take, but if you would like to take a swing at it Rod, let me
know and we'll get it assigned to you.

Jon

On Fri, Nov 8, 2019 at 4:35 PM Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote:

> I can confirm I see the same error. Looks like its specific to the
> microprofile flavor. I'll see if I can spot anything odd there.
>
> On Fri, Nov 8, 2019 at 3:39 PM Jenkins, Rodney J (Rod) <
> jenki...@nationwide.com> wrote:
>
>> I have done some further testing
>>
>> All testing is on :
>>
>> $ java -version
>> openjdk version "11.0.5" 2019-10-15 LTS
>> OpenJDK Runtime Environment 18.9 (build 11.0.5+10-LTS)
>> OpenJDK 64-Bit Server VM 18.9 (build 11.0.5+10-LTS, mixed mode, sharing)
>>
>> When I pull  apache-tomee-microprofile-7.1.1, I do not get the stack
>> traces, but when I pull apache-tomee-microprofile-8.0.0, I do get the 
stack
>> traces.
>>
>> According to the link the Richard provided, the issue occurs when
>> compiling the app.  In my case, I am not compiling anything.  All I am
>> doing is downloading the TomEE tar ball and running it.  It is the ROOT,
>> docs, manager, and host-manager apps that throw the stack trace.
>>
>> Can one of you please grab that tar ball and see if you get the same
>> issues as I do?
>>
>> Thank you!!
>> Rod.
>>
>>
>> On 11/7/19, 8:08 AM, "Richard Monson-Haefel" 
>> wrote:
>>
>> Hi Rodney,
>>
>> Thanks for all the hard work!  I think the problem is with JAXB which
>> suffered some changes in Java 8 - 11.  This article should provide
>> some
>> guidance on what needs to be done to fix the problem.
>>
>> https://www.jesperdj.com/2018/09/30/jaxb-on-java-9-10-11-and-beyond/
>>
>> Richard
>>
>> On Tue, Nov 5, 2019 at 12:09 AM Jenkins, Rodney J (Rod) <
>> jenki...@nationwide.com> wrote:
>>
>> > Hello all,
>> >
>> > I have a completed repo for you all to look at here:
>> > https://github.com/scriptmonkey/docker-tomee
>> >
>> > The only thing I am having an issue with is the Java 11 8.0.0
>> microprofile
>> > image.  I am getting some stack traces when I build that.  I have
>> pasted
>> > the log file below.  I did not create a pull request because I
>> would like
>> > to clean up the stack traces.
>> >
>> > All of the other images start without issue.
>> >
>> >
>> > Using CATALINA_BASE:   /usr/local/tomee
>> > Using CATALINA_HOME:   /usr/local/tomee
>> > Using CATALINA_TMPDIR: /usr/local/tomee/temp
>> > Using JRE_HOME:/usr/local/openjdk-11
>> > Using CLASSPATH:
>> >
>> /usr/local/tomee/bin/bootstrap.jar:/usr/local/tomee/bin/tomcat-juli.jar
>> > NOTE: Picked up JDK_JAVA_OPTIONS:
>> > --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/
>> java.io=ALL-UNNAMED
>> > --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
>> > WARNING: An illegal reflective access operation has occurred
>> > WARNING: Illegal reflective access by
>> > org.apache.tomee.catalina.ServerListener
>> > (file:/usr/local/tomee/lib/tomee-catalina-8.0.0.jar) to field
>> > java.lang.reflect.Field.modifiers
>> > WARNING: Please consider reporting this to the maintainers of
>> > org.apache.tomee.catalina.ServerListener
>> > WARNING: Use --illegal-access=warn to enable warnings of further
>> illegal
>> > reflective access operations
>> > WARNING: All illegal access operations will be denied in a future
>> release
>> > 05-Nov-2019 05:49:18.411 INFO [main]
>> > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Server version
>> name:
>> >  Apache Tomcat (TomEE)/9.0.22 (8.0.0)
>> > 05-Nov-2019 05:49:18.414 INFO [main]
>> > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Server built:
>> > Jul 4 2019 14:20:06 UTC
>> > 05-Nov-2019 05:49:18.414 INFO [main]
>> > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Server version
>> number:
>> > 9.0.22.0
>> > 05-Nov-2019 05:49:18.414 INFO [main]
>> > jdk.internal.reflect.NativeMethodAccessorImpl.invoke OS Name:
>> >  Linux
>> > 05-Nov-2019 05:49:18.415 

[GitHub] [tomee] asf-ci commented on issue #608: Ddded missing dependency for microprofile

[GitBox]

asf-ci commented on issue #608: Ddded missing dependency for microprofile
URL: https://github.com/apache/tomee/pull/608#issuecomment-553458066
 
 
   Can one of the admins verify this patch?


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [tomee] asf-ci commented on issue #608: Ddded missing dependency for microprofile

[GitBox]

asf-ci commented on issue #608: Ddded missing dependency for microprofile
URL: https://github.com/apache/tomee/pull/608#issuecomment-553458065
 
 
   Can one of the admins verify this patch?


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [tomee] asf-ci commented on issue #608: Ddded missing dependency for microprofile

[GitBox]

asf-ci commented on issue #608: Ddded missing dependency for microprofile
URL: https://github.com/apache/tomee/pull/608#issuecomment-553458060
 
 
   Can one of the admins verify this patch?


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [tomee] scriptmonkey opened a new pull request #608: Ddded missing dependency for microprofile

[GitBox]

scriptmonkey opened a new pull request #608: Ddded missing dependency for 
microprofile
URL: https://github.com/apache/tomee/pull/608
 
 
   Jira card:  TOMEE-2731
   
   This fixes a missing dependency for microprofile.  This was discussed in the 
dev email list.
   
   I added:
   ```

   com.sun.activation
  
   jakarta.activation  
  
   1.2.1 
  

   ```


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: TomEE GraalVM native image

[Richard Monson-Haefel]

Thanks, Roberto!  So, compiling with it is probably not going to be a
priority, but running TomEE on it could be. I wonder if the
performance advantages of using GraalVM over JVM is significant.

On Wed, Nov 13, 2019 at 8:46 AM Roberto Cortez 
wrote:

> Hi,
>
> Let me clarify that this repo:
> https://github.com/tomitribe/graalvm-microprofile <
> https://github.com/tomitribe/graalvm-microprofile>
>
> Is just to play around with the polyglot features of GraalVM.
>
> Building TomEE native images will be another story. I did try that when I
> was playing with the other repo and there are a lot of things that fail.
> This is not only about TomEE, but also about all the libraries used in
> TomEE itself.
>
> To be able to build to native image, you would need to comply with
> Substrate VM limitations stated here:
> https://github.com/oracle/graal/blob/master/substratevm/LIMITATIONS.md <
> https://github.com/oracle/graal/blob/master/substratevm/LIMITATIONS.md>
>
> For instance, projects like Quarkus or Micronaut removed all reflection
> calls and resolve these at compile time rather than runtime. While it is
> possible to instruct GraalVM about some reflection usage when doing the
> native image, I believe it won’t be enough in TomEE case and most likely
> some portions would need to be reimplemented. I have no idea what would be
> the effort involved in a task like this. It is not trivial.
>
> Cheers,
> Roberto
>
> > On 13 Nov 2019, at 12:55, Richard Monson-Haefel 
> wrote:
> >
> > Hi!
> >
> > That would be cool. If memory serves there may be some issues with
> > reflection and complication but running TomEE on GraalVM should work
> since
> > it won't try to compile the reflection stuff.  I haven't run it on
> GraalVM
> > myself, but this would be a really cool effort and if you can get it to
> > work it would be an awesome addition to the project in my opinion.  Are
> you
> > interested in testing it out and working on it?
> >
> > Richard
> >
> > On Wed, Nov 13, 2019 at 5:35 AM COURTAULT Francois <
> > francois.courta...@thalesgroup.com> wrote:
> >
> >> Hello everyone,
> >>
> >> I am able to see some initiatives around GraalVM native-image like
> >> Quarkus, Helidon,...
> >> I have also seen that Tomcat 9.0.26 could be built as a native image:
> >> http://tomcat.apache.org/tomcat-9.0-doc/graal.html
> >>
> >> Digging on the web, I discover some work on TomEE side as well:
> >> https://github.com/tomitribe/graalvm-microprofile
> >>
> >> Are you working on a TomEE version which can be built as a GraalVM
> native
> >> image ?
> >> I think it should be a quite important topic to consider in the roadmap,
> >> right ?
> >>
> >> Best Regards.
> >>
> >>
> >>
> >> 
> >> This message and any attachments are intended solely for the addressees
> >> and may contain confidential information. Any unauthorized use or
> >> disclosure, either whole or partial, is prohibited.
> >> E-mails are susceptible to alteration. Our company shall not be liable
> for
> >> the message if altered, changed or falsified. If you are not the
> intended
> >> recipient of this message, please delete it and notify the sender.
> >> Although all reasonable efforts have been made to keep this transmission
> >> free from viruses, the sender will not be liable for damages caused by a
> >> transmitted virus.
> >>
> >
> >
> > --
> > Richard Monson-Haefel
> > https://twitter.com/rmonson
> > https://www.linkedin.com/in/monsonhaefel/
>
>

-- 
Richard Monson-Haefel
https://twitter.com/rmonson
https://www.linkedin.com/in/monsonhaefel/

Re: TomEE GraalVM native image

[Roberto Cortez]

Hi,

Let me clarify that this repo:
https://github.com/tomitribe/graalvm-microprofile 


Is just to play around with the polyglot features of GraalVM.

Building TomEE native images will be another story. I did try that when I was 
playing with the other repo and there are a lot of things that fail. This is 
not only about TomEE, but also about all the libraries used in TomEE itself. 

To be able to build to native image, you would need to comply with Substrate VM 
limitations stated here:
https://github.com/oracle/graal/blob/master/substratevm/LIMITATIONS.md 


For instance, projects like Quarkus or Micronaut removed all reflection calls 
and resolve these at compile time rather than runtime. While it is possible to 
instruct GraalVM about some reflection usage when doing the native image, I 
believe it won’t be enough in TomEE case and most likely some portions would 
need to be reimplemented. I have no idea what would be the effort involved in a 
task like this. It is not trivial.

Cheers,
Roberto 

> On 13 Nov 2019, at 12:55, Richard Monson-Haefel  
> wrote:
> 
> Hi!
> 
> That would be cool. If memory serves there may be some issues with
> reflection and complication but running TomEE on GraalVM should work since
> it won't try to compile the reflection stuff.  I haven't run it on GraalVM
> myself, but this would be a really cool effort and if you can get it to
> work it would be an awesome addition to the project in my opinion.  Are you
> interested in testing it out and working on it?
> 
> Richard
> 
> On Wed, Nov 13, 2019 at 5:35 AM COURTAULT Francois <
> francois.courta...@thalesgroup.com> wrote:
> 
>> Hello everyone,
>> 
>> I am able to see some initiatives around GraalVM native-image like
>> Quarkus, Helidon,...
>> I have also seen that Tomcat 9.0.26 could be built as a native image:
>> http://tomcat.apache.org/tomcat-9.0-doc/graal.html
>> 
>> Digging on the web, I discover some work on TomEE side as well:
>> https://github.com/tomitribe/graalvm-microprofile
>> 
>> Are you working on a TomEE version which can be built as a GraalVM native
>> image ?
>> I think it should be a quite important topic to consider in the roadmap,
>> right ?
>> 
>> Best Regards.
>> 
>> 
>> 
>> 
>> This message and any attachments are intended solely for the addressees
>> and may contain confidential information. Any unauthorized use or
>> disclosure, either whole or partial, is prohibited.
>> E-mails are susceptible to alteration. Our company shall not be liable for
>> the message if altered, changed or falsified. If you are not the intended
>> recipient of this message, please delete it and notify the sender.
>> Although all reasonable efforts have been made to keep this transmission
>> free from viruses, the sender will not be liable for damages caused by a
>> transmitted virus.
>> 
> 
> 
> -- 
> Richard Monson-Haefel
> https://twitter.com/rmonson
> https://www.linkedin.com/in/monsonhaefel/

Re: TomEE GraalVM native image

[Richard Monson-Haefel]

That's really a good point, Jon!

We are so close to Jakarta EE 8 compliance it's worth focusing on that for
now and coming back to GraalVM later. However, anyone who is super pumped
about GraalVM should feel no hesitation in working that problem.

On Wed, Nov 13, 2019 at 8:35 AM Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote:

> > I think it should be a quite important topic to consider in the roadmap,
> right ?
>
> I agree its cool. What's the community take on the priority? Personally,
> I'd consider getting Jakarta EE 8 done the highest priority, behind bugs
> and security updates. I'm currently trying to finish one bug, and review 2
> PRs before getting a release out, and then I'll hopefully be back to
> Jakarta EE 8.
>
> If others want to work on GraalVM native images for TomEE, that's great and
> contributions are welcome. I'll keep plugging away at Jakarta EE 8.
>
> Jon
>
> On Wed, Nov 13, 2019 at 11:35 AM COURTAULT Francois <
> francois.courta...@thalesgroup.com> wrote:
>
> > Hello everyone,
> >
> > I am able to see some initiatives around GraalVM native-image like
> > Quarkus, Helidon,...
> > I have also seen that Tomcat 9.0.26 could be built as a native image:
> > http://tomcat.apache.org/tomcat-9.0-doc/graal.html
> >
> > Digging on the web, I discover some work on TomEE side as well:
> > https://github.com/tomitribe/graalvm-microprofile
> >
> > Are you working on a TomEE version which can be built as a GraalVM native
> > image ?
> > I think it should be a quite important topic to consider in the roadmap,
> > right ?
> >
> > Best Regards.
> >
> >
> >
> > 
> > This message and any attachments are intended solely for the addressees
> > and may contain confidential information. Any unauthorized use or
> > disclosure, either whole or partial, is prohibited.
> > E-mails are susceptible to alteration. Our company shall not be liable
> for
> > the message if altered, changed or falsified. If you are not the intended
> > recipient of this message, please delete it and notify the sender.
> > Although all reasonable efforts have been made to keep this transmission
> > free from viruses, the sender will not be liable for damages caused by a
> > transmitted virus.
> >
>


-- 
Richard Monson-Haefel
https://twitter.com/rmonson
https://www.linkedin.com/in/monsonhaefel/

Re: JIRA about CVEs

[Richard Monson-Haefel]

Excellent!  Thanks, Richard!

On Wed, Nov 13, 2019 at 8:18 AM Zowalla, Richard <
richard.zowa...@hs-heilbronn.de> wrote:

> Ok, John did comment in the JIRA, that the upgrades are already conducted
> in previous commits.
> I will run an OWASP scan on the code. If this reveals some more vulnerable
> dependencies, I will report in the JIRA and provide a PR, if possible.
>
> Best,
> Richard Z.
>
> Am Mittwoch, den 13.11.2019, 14:08 + schrieb Zowalla, Richard:
>
> Alright, I will proceed :)
>
> Best,
> Richard
>
> Am Mittwoch, den 13.11.2019, 07:52 -0600 schrieb Richard Monson-Haefel:
>
> If you don't mind, Richard, can you do the upgrades and create a PR? We
> can let it run overnight and see how it goes.
>
> I'm not sure as to what the best policy is for announcing the CVE so that
> people know to upgrade. I think we should figure that out after the ci has
> run. As an alternative you can run the full test suite on your own machine
> (takes about an hour or something like that) and see if you pick up any
> errors.  I did this yesterday with a different PR but I don't have the
> extra cycles to do it again today.
>
> On Wed, Nov 13, 2019 at 7:07 AM Zowalla, Richard <
> richard.zowa...@hs-heilbronn.de> wrote:
>
> Sounds reasonable to me. If I can assist in upgrading, let me know.
>
> However, we should publish the link to the ASF CI somewhere, so we can
> better monitor the current build status.
>
> Best,
> Richard Z
>
> Am Mittwoch, den 13.11.2019, 07:00 -0600 schrieb Richard Monson-Haefel:
>
> Is this a matter of upgrading and testing or is there more to it than
>
> that?  If that's it we can create a PR with the updates and let the asf ci
>
> run the tests and look for problems.
>
>
>
> On Wed, Nov 13, 2019 at 5:58 AM COURTAULT Francois <
>
> francois.courta...@thalesgroup.com> wrote:
>
>
> Hello,
>
>
> Could you take this JIRA entry (
>
> https://issues.apache.org/jira/browse/TOMEE-2737) into account please ?
>
>
> Best Regard.
>
>
>
>
> 
>
> This message and any attachments are intended solely for the addressees
>
> and may contain confidential information. Any unauthorized use or
>
> disclosure, either whole or partial, is prohibited.
>
> E-mails are susceptible to alteration. Our company shall not be liable for
>
> the message if altered, changed or falsified. If you are not the intended
>
> recipient of this message, please delete it and notify the sender.
>
> Although all reasonable efforts have been made to keep this transmission
>
> free from viruses, the sender will not be liable for damages caused by a
>
> transmitted virus.
>
>
>
>
>
> --
>
> Richard Zowalla, M.Sc.
> Research Associate, PhD Student | Medical Informatics
>
>
>
> Hochschule Heilbronn – University of Applied Sciences
> Max-Planck-Str. 39
> D-74081 Heilbronn
> phone: +49 7131 504 6791
> mail: richard.zowa...@hs-heilbronn.de
> web: http://www.mi.hs-heilbronn.de/
>
>
>
> --
>
> Richard Zowalla, M.Sc.
> Research Associate, PhD Student | Medical Informatics
>
>
>
> Hochschule Heilbronn – University of Applied Sciences
> Max-Planck-Str. 39
> D-74081 Heilbronn
> phone: +49 7131 504 6791
> mail: richard.zowa...@hs-heilbronn.de
> web: http://www.mi.hs-heilbronn.de/
>


-- 
Richard Monson-Haefel
https://twitter.com/rmonson
https://www.linkedin.com/in/monsonhaefel/

Re: TomEE GraalVM native image

[Jonathan Gallimore]

> I think it should be a quite important topic to consider in the roadmap,
right ?

I agree its cool. What's the community take on the priority? Personally,
I'd consider getting Jakarta EE 8 done the highest priority, behind bugs
and security updates. I'm currently trying to finish one bug, and review 2
PRs before getting a release out, and then I'll hopefully be back to
Jakarta EE 8.

If others want to work on GraalVM native images for TomEE, that's great and
contributions are welcome. I'll keep plugging away at Jakarta EE 8.

Jon

On Wed, Nov 13, 2019 at 11:35 AM COURTAULT Francois <
francois.courta...@thalesgroup.com> wrote:

> Hello everyone,
>
> I am able to see some initiatives around GraalVM native-image like
> Quarkus, Helidon,...
> I have also seen that Tomcat 9.0.26 could be built as a native image:
> http://tomcat.apache.org/tomcat-9.0-doc/graal.html
>
> Digging on the web, I discover some work on TomEE side as well:
> https://github.com/tomitribe/graalvm-microprofile
>
> Are you working on a TomEE version which can be built as a GraalVM native
> image ?
> I think it should be a quite important topic to consider in the roadmap,
> right ?
>
> Best Regards.
>
>
>
> 
> This message and any attachments are intended solely for the addressees
> and may contain confidential information. Any unauthorized use or
> disclosure, either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for
> the message if altered, changed or falsified. If you are not the intended
> recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission
> free from viruses, the sender will not be liable for damages caused by a
> transmitted virus.
>

Re: JIRA about CVEs

[Jonathan Gallimore]

Please note my comment on the JIRA:

These have already been done:
Update to Jackson Databind 2.10.0:
https://github.com/apache/tomee/commit/5e38138463f65146c4087da8085c8dcd93079ef1
TOMEE-2725 update beanutils to 1.9.4:
https://github.com/apache/tomee/commit/0e433e9e565dac45c2c04368f8da6f1e827db295
TOMEE-2726 update Xmlsec to 2.1.4:
https://github.com/apache/tomee/commit/e3b05ddf8e4e06286f45a936474fee4eee6dcc99

Shout if you think there are other dependency updates needed.

Jon

On Wed, Nov 13, 2019 at 2:09 PM Zowalla, Richard <
richard.zowa...@hs-heilbronn.de> wrote:

> Alright, I will proceed :)
>
> Best,
> Richard
>
> Am Mittwoch, den 13.11.2019, 07:52 -0600 schrieb Richard Monson-Haefel:
>
> If you don't mind, Richard, can you do the upgrades and create a PR? We
> can let it run overnight and see how it goes.
>
> I'm not sure as to what the best policy is for announcing the CVE so that
> people know to upgrade. I think we should figure that out after the ci has
> run. As an alternative you can run the full test suite on your own machine
> (takes about an hour or something like that) and see if you pick up any
> errors.  I did this yesterday with a different PR but I don't have the
> extra cycles to do it again today.
>
> On Wed, Nov 13, 2019 at 7:07 AM Zowalla, Richard <
> richard.zowa...@hs-heilbronn.de> wrote:
>
> Sounds reasonable to me. If I can assist in upgrading, let me know.
>
> However, we should publish the link to the ASF CI somewhere, so we can
> better monitor the current build status.
>
> Best,
> Richard Z
>
> Am Mittwoch, den 13.11.2019, 07:00 -0600 schrieb Richard Monson-Haefel:
>
> Is this a matter of upgrading and testing or is there more to it than
>
> that?  If that's it we can create a PR with the updates and let the asf ci
>
> run the tests and look for problems.
>
>
>
> On Wed, Nov 13, 2019 at 5:58 AM COURTAULT Francois <
>
> francois.courta...@thalesgroup.com> wrote:
>
>
> Hello,
>
>
> Could you take this JIRA entry (
>
> https://issues.apache.org/jira/browse/TOMEE-2737) into account please ?
>
>
> Best Regard.
>
>
>
>
> 
>
> This message and any attachments are intended solely for the addressees
>
> and may contain confidential information. Any unauthorized use or
>
> disclosure, either whole or partial, is prohibited.
>
> E-mails are susceptible to alteration. Our company shall not be liable for
>
> the message if altered, changed or falsified. If you are not the intended
>
> recipient of this message, please delete it and notify the sender.
>
> Although all reasonable efforts have been made to keep this transmission
>
> free from viruses, the sender will not be liable for damages caused by a
>
> transmitted virus.
>
>
>
>
>
> --
>
> Richard Zowalla, M.Sc.
> Research Associate, PhD Student | Medical Informatics
>
>
>
> Hochschule Heilbronn – University of Applied Sciences
> Max-Planck-Str. 39
> D-74081 Heilbronn
> phone: +49 7131 504 6791
> mail: richard.zowa...@hs-heilbronn.de
> web: http://www.mi.hs-heilbronn.de/
>
>
>
> --
> Richard Monson-Haefel
> https://twitter.com/rmonson
> https://www.linkedin.com/in/monsonhaefel/
>
> --
>
> Richard Zowalla, M.Sc.
> Research Associate, PhD Student | Medical Informatics
>
>
>
> Hochschule Heilbronn – University of Applied Sciences
> Max-Planck-Str. 39
> D-74081 Heilbronn
> phone: +49 7131 504 6791
> mail: richard.zowa...@hs-heilbronn.de
> web: http://www.mi.hs-heilbronn.de/
>

Re: JIRA about CVEs

[Zowalla, Richard]

Ok, John did comment in the JIRA, that the upgrades are already
conducted in previous commits.I will run an OWASP scan on the code. If
this reveals some more vulnerable dependencies, I will report in the
JIRA and provide a PR, if possible.
Best,Richard Z.
Am Mittwoch, den 13.11.2019, 14:08 + schrieb Zowalla, Richard:
> Alright, I will proceed :)
> Best,Richard
> Am Mittwoch, den 13.11.2019, 07:52 -0600 schrieb Richard Monson-
> Haefel:
> > If you don't mind, Richard, can you do the upgrades and create a
> > PR? We can let it run overnight and see how it goes.
> > I'm not sure as to what the best policy is for announcing the CVE
> > so that people know to upgrade. I think we should figure that out
> > after the ci has run. As an alternative you can run the full test
> > suite on your own machine (takes about an hour or something like
> > that) and see if you pick up any errors.  I did this yesterday with
> > a different PR but I don't have the extra cycles to do it again
> > today.
> > 
> > On Wed, Nov 13, 2019 at 7:07 AM Zowalla, Richard <
> > richard.zowa...@hs-heilbronn.de> wrote:
> > > Sounds reasonable to me. If I can assist in upgrading, let me
> > > know.
> > > 
> > > However, we should publish the link to the ASF CI somewhere, so
> > > we can better monitor the current build status.
> > > 
> > > Best,
> > > Richard Z
> > > 
> > > Am Mittwoch, den 13.11.2019, 07:00 -0600 schrieb Richard Monson-
> > > Haefel:
> > > > Is this a matter of upgrading and testing or is there more to
> > > > it thanthat?  If that's it we can create a PR with the updates
> > > > and let the asf cirun the tests and look for problems.
> > > > 
> > > > On Wed, Nov 13, 2019 at 5:58 AM COURTAULT Francois <
> > > > francois.courta...@thalesgroup.com> wrote:
> > > > Hello,
> > > > Could you take this JIRA entry (
> > > > https://issues.apache.org/jira/browse/TOMEE-2737) into account
> > > > please ?
> > > > Best Regard.
> > > > 
> > > > 
> > > > This message and any
> > > > attachments are intended solely for the addresseesand may
> > > > contain confidential information. Any unauthorized use
> > > > ordisclosure, either whole or partial, is prohibited.E-mails
> > > > are susceptible to alteration. Our company shall not be liable
> > > > forthe message if altered, changed or falsified. If you are not
> > > > the intendedrecipient of this message, please delete it and
> > > > notify the sender.Although all reasonable efforts have been
> > > > made to keep this transmissionfree from viruses, the sender
> > > > will not be liable for damages caused by atransmitted virus.
> > > > 
> > > > 
> > > > 
> > > -- 
> > > Richard Zowalla, M.Sc.Research Associate, PhD Student | Medical
> > > Informatics
> > > 
> > > 
> > > Hochschule Heilbronn – University of Applied SciencesMax-Planck-
> > > Str. 39 D-74081 Heilbronn phone: +49 7131 504 6791mail:
> > > richard.zowalla@hs-heilbronn.deweb: 
> > > http://www.mi.hs-heilbronn.de/ 
> > 
> > 
-- 
Richard Zowalla, M.Sc.Research Associate, PhD Student | Medical Informatics


Hochschule Heilbronn – University of Applied SciencesMax-Planck-Str. 39 D-74081 
Heilbronn phone: +49 7131 504 6791mail: richard.zowalla@hs-heilbronn.deweb: 
http://www.mi.hs-heilbronn.de/ 


smime.p7s
Description: S/MIME cryptographic signature

Re: JIRA about CVEs

[Zowalla, Richard]

Alright, I will proceed :)

Best,
Richard

Am Mittwoch, den 13.11.2019, 07:52 -0600 schrieb Richard Monson-Haefel:
> If you don't mind, Richard, can you do the upgrades and create a PR?
> We can let it run overnight and see how it goes.
> I'm not sure as to what the best policy is for announcing the CVE so
> that people know to upgrade. I think we should figure that out after
> the ci has run. As an alternative you can run the full test suite on
> your own machine (takes about an hour or something like that) and see
> if you pick up any errors.  I did this yesterday with a different PR
> but I don't have the extra cycles to do it again today.
> On Wed, Nov 13, 2019 at 7:07 AM Zowalla, Richard <
> richard.zowa...@hs-heilbronn.de> wrote:
> > Sounds reasonable to me. If I can assist in upgrading, let me know.
> > 
> > However, we should publish the link to the ASF CI somewhere, so we
> > can better monitor the current build status.
> > 
> > Best,
> > Richard Z
> > 
> > Am Mittwoch, den 13.11.2019, 07:00 -0600 schrieb Richard Monson-
> > Haefel:
> > > Is this a matter of upgrading and testing or is there more to it
> > > thanthat?  If that's it we can create a PR with the updates and
> > > let the asf cirun the tests and look for problems.
> > > 
> > > On Wed, Nov 13, 2019 at 5:58 AM COURTAULT Francois <
> > > francois.courta...@thalesgroup.com> wrote:
> > > Hello,
> > > Could you take this JIRA entry (
> > > https://issues.apache.org/jira/browse/TOMEE-2737) into account
> > > please ?
> > > Best Regard.
> > > 
> > > 
> > > This message and any attachments
> > > are intended solely for the addresseesand may contain
> > > confidential information. Any unauthorized use ordisclosure,
> > > either whole or partial, is prohibited.E-mails are susceptible to
> > > alteration. Our company shall not be liable forthe message if
> > > altered, changed or falsified. If you are not the
> > > intendedrecipient of this message, please delete it and notify
> > > the sender.Although all reasonable efforts have been made to keep
> > > this transmissionfree from viruses, the sender will not be liable
> > > for damages caused by atransmitted virus.
> > > 
> > > 
> > > 
> > -- 
> > Richard Zowalla, M.Sc.Research Associate, PhD Student | Medical
> > Informatics
> > 
> > 
> > Hochschule Heilbronn – University of Applied SciencesMax-Planck-
> > Str. 39 D-74081 Heilbronn phone: +49 7131 504 6791mail:
> > richard.zowalla@hs-heilbronn.deweb: http://www.mi.hs-heilbronn.de/ 
> 
> -- 
> Richard Monson-Haefelhttps://twitter.com/rmonson
> https://www.linkedin.com/in/monsonhaefel/
> 
> 
-- 
Richard Zowalla, M.Sc.Research Associate, PhD Student | Medical Informatics


Hochschule Heilbronn – University of Applied SciencesMax-Planck-Str. 39 D-74081 
Heilbronn phone: +49 7131 504 6791mail: richard.zowalla@hs-heilbronn.deweb: 
http://www.mi.hs-heilbronn.de/ 


smime.p7s
Description: S/MIME cryptographic signature

Re: JIRA about CVEs

[Richard Monson-Haefel]

If you don't mind, Richard, can you do the upgrades and create a PR? We can
let it run overnight and see how it goes.

I'm not sure as to what the best policy is for announcing the CVE so that
people know to upgrade. I think we should figure that out after the ci has
run. As an alternative you can run the full test suite on your own machine
(takes about an hour or something like that) and see if you pick up any
errors.  I did this yesterday with a different PR but I don't have the
extra cycles to do it again today.

On Wed, Nov 13, 2019 at 7:07 AM Zowalla, Richard <
richard.zowa...@hs-heilbronn.de> wrote:

> Sounds reasonable to me. If I can assist in upgrading, let me know.
>
> However, we should publish the link to the ASF CI somewhere, so we can
> better monitor the current build status.
>
> Best,
> Richard Z
>
> Am Mittwoch, den 13.11.2019, 07:00 -0600 schrieb Richard Monson-Haefel:
>
> Is this a matter of upgrading and testing or is there more to it than
>
> that?  If that's it we can create a PR with the updates and let the asf ci
>
> run the tests and look for problems.
>
>
>
> On Wed, Nov 13, 2019 at 5:58 AM COURTAULT Francois <
>
> francois.courta...@thalesgroup.com> wrote:
>
>
> Hello,
>
>
> Could you take this JIRA entry (
>
> https://issues.apache.org/jira/browse/TOMEE-2737) into account please ?
>
>
> Best Regard.
>
>
>
>
> 
>
> This message and any attachments are intended solely for the addressees
>
> and may contain confidential information. Any unauthorized use or
>
> disclosure, either whole or partial, is prohibited.
>
> E-mails are susceptible to alteration. Our company shall not be liable for
>
> the message if altered, changed or falsified. If you are not the intended
>
> recipient of this message, please delete it and notify the sender.
>
> Although all reasonable efforts have been made to keep this transmission
>
> free from viruses, the sender will not be liable for damages caused by a
>
> transmitted virus.
>
>
>
>
>
> --
>
> Richard Zowalla, M.Sc.
> Research Associate, PhD Student | Medical Informatics
>
>
>
> Hochschule Heilbronn – University of Applied Sciences
> Max-Planck-Str. 39
> D-74081 Heilbronn
> phone: +49 7131 504 6791
> mail: richard.zowa...@hs-heilbronn.de
> web: http://www.mi.hs-heilbronn.de/
>


-- 
Richard Monson-Haefel
https://twitter.com/rmonson
https://www.linkedin.com/in/monsonhaefel/

[GitHub] [tomee] monsonhaefel commented on issue #606: TOMEE-2734-Upgrade CXF to 3.3.4

[GitBox]

monsonhaefel commented on issue #606: TOMEE-2734-Upgrade CXF to 3.3.4
URL: https://github.com/apache/tomee/pull/606#issuecomment-553403322
 
 
   Someone else may have a better solution but this is how I would get
   started.
   
   If you look at the stack trace you'll see that openejb is involved from
   
   at org.apache.openejb.loader.IO.slurp(IO.java:156)
at 
org.apache.openejb.server.httpd.AsyncHttpTest.async(AsyncHttpTest.java:58)
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:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.apache.openejb.junit.DeployApplication$1.call(DeployApplication.java:44)
at 
org.apache.openejb.junit.DeployApplication$1.call(DeployApplication.java:40)
at 
org.apache.openejb.testing.ApplicationComposers.evaluate(ApplicationComposers.java:1070)
at 
org.apache.openejb.junit.DeployApplication.evaluate(DeployApplication.java:40)
   
   
   I would put a break point at
   
org.apache.openejb.junit.DeployApplication.evaluate(DeployApplication.java:40)
   and when you hit that test activate another break point at at
   org.apache.openejb.loader.IO.slurp(IO.java:156) and see if you can
   figure out what's going wrong.
   
   Richard
   
   
   On Wed, Nov 13, 2019 at 6:51 AM Daniel Dias 
   wrote:
   
   > Hi Richard ,
   >
   > I would like, good that I learn something different.
   >
   > I just need some guidance.
   >
   > because I just did a lib update, and if I run the build without the tests
   > it passes.
   >
   > Em qua., 13 de nov. de 2019 às 09:46, Richard Monson-Haefel <
   > notificati...@github.com> escreveu:
   >
   > > Hi Daniel,
   > >
   > > Do you plan to work on this? We are probably going to want to upgrade
   > > eventually.
   > >
   > > Richard
   > >
   > > On Tue, Nov 12, 2019 at 8:30 PM Daniel Dias 
   > > wrote:
   > >
   > > > Hi @monsonhaefel ,
   > > >
   > > > from what I saw in the log he gave recursed connection error :
   > > >
   > > > INFO: Closing DataSource: My Unmanaged DataSource
   > > > [ERROR] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
   > > 2.439 s <<< FAILURE! - in org.apache.openejb.server.httpd.AsyncHttpTest
   > > > [ERROR] async(org.apache.openejb.server.httpd.AsyncHttpTest) Time
   > > elapsed: 1.174 s <<< ERROR!
   > > > java.net.ConnectException: Connection refused (Connection refused)
   > > > at java.net.PlainSocketImpl.socketConnect(Native Method)
   > > > at
   > >
   > 
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
   > > > at
   > >
   > 
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
   > > > at
   > >
   > java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
   > > > 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 sun.net.NetworkClient.doConnect(NetworkClient.java:180)
   > > > at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
   > > > at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
   > > > at sun.net.www.http.HttpClient.(HttpClient.java:242)
   > > > at sun.net.www.http.HttpClient.New(HttpClient.java:339)
   > > > at sun.net.www.http.HttpClient.New(HttpClient.java:357)
   > > > at
   > >
   > 
sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1220)
   > > > at
   > >
   > 
sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1156)
   > > > at
   > >
   > 
sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1050)
   > > > at
   > >
   > 
sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:984)
   > > > at
   > >
   > 
sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1564)
   > > > at
   > >
   > 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
   > > > at java.net.URL.openStream(URL.java:1045)
   > > > at org.apache.openejb.loader.IO.slurp(IO.java:156)
   > > > at
   > >
   > org.apache.openejb.server.httpd.AsyncHttpTest.async(AsyncHttpTest.java:58)
   > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   > > > at
   > >
   > 

Re: TOMEE-2734-Upgrade CXF to 3.3.4

[Richard Monson-Haefel]

Hi Daniel,

This is a great chance for you to do a code contribution if you are
interested.  Do you want to dig into it?

Richard

On Wed, Nov 13, 2019 at 6:48 AM Daniel Dias Dos Santos <
daniel.dias.analist...@gmail.com> wrote:

> Hi ,
>
> I too had problems with tests full,
> for me broke in openejb-core .
>
> I don't know if it's my machine, because it's not very good.
>
> because I also ran the full test on the master and it broke too.
> --
>
> *Daniel Dias dos Santos*
> Java Developer
> SouJava & JCP Member
> GitHub: https://github.com/Daniel-Dos
> Linkedin: www.linkedin.com/in/danieldiasjava
> Twitter: http://twitter.com/danieldiasjava
>
>
> Em qua., 13 de nov. de 2019 às 09:44, Richard Monson-Haefel <
> monsonhae...@gmail.com> escreveu:
>
> > Hi Daniel!
> >
> > I had some errors when running the full body of TomEE tests. See the PR
> for
> > more details.
> >
> > Richard
> >
> > On Tue, Nov 12, 2019 at 2:31 PM Daniel Dias Dos Santos <
> > daniel.dias.analist...@gmail.com> wrote:
> >
> > > Hi ,
> > >
> > > great  Richard :  )
> > > --
> > >
> > > *Daniel Dias dos Santos*
> > > Java Developer
> > > SouJava & JCP Member
> > > GitHub: https://github.com/Daniel-Dos
> > > Linkedin: www.linkedin.com/in/danieldiasjava
> > > Twitter: http://twitter.com/danieldiasjava
> > >
> > >
> > > Em ter., 12 de nov. de 2019 às 10:21, Richard Monson-Haefel <
> > > monsonhae...@gmail.com> escreveu:
> > >
> > > > I'm testing the entire project now.  If all is well I think we can
> > merge
> > > > this.
> > > >
> > > > On Mon, Nov 11, 2019 at 7:21 PM Daniel Dias Dos Santos <
> > > > daniel.dias.analist...@gmail.com> wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I created a ticket jira[1].
> > > > > can some admin assign for me .
> > > > > and too open an PR [2] .
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/TOMEE-2734
> > > > > [2] https://github.com/apache/tomee/pull/606
> > > > >
> > > > > thanks .
> > > > > --
> > > > >
> > > > > *Daniel Dias dos Santos*
> > > > > Java Developer
> > > > > SouJava & JCP Member
> > > > > GitHub: https://github.com/Daniel-Dos
> > > > > Linkedin: www.linkedin.com/in/danieldiasjava
> > > > > Twitter: http://twitter.com/danieldiasjava
> > > > >
> > > >
> > > >
> > > > --
> > > > Richard Monson-Haefel
> > > > https://twitter.com/rmonson
> > > > https://www.linkedin.com/in/monsonhaefel/
> > > >
> > >
> >
> >
> > --
> > Richard Monson-Haefel
> > https://twitter.com/rmonson
> > https://www.linkedin.com/in/monsonhaefel/
> >
>


-- 
Richard Monson-Haefel
https://twitter.com/rmonson
https://www.linkedin.com/in/monsonhaefel/

Re: JIRA about CVEs

[Zowalla, Richard]

Sounds reasonable to me. If I can assist in upgrading, let me know.
However, we should publish the link to the ASF CI somewhere, so we can
better monitor the current build status.
Best,Richard Z
Am Mittwoch, den 13.11.2019, 07:00 -0600 schrieb Richard Monson-Haefel:
> Is this a matter of upgrading and testing or is there more to it
> thanthat?  If that's it we can create a PR with the updates and let
> the asf cirun the tests and look for problems.
> 
> On Wed, Nov 13, 2019 at 5:58 AM COURTAULT Francois <
> francois.courta...@thalesgroup.com> wrote:
> Hello,
> Could you take this JIRA entry (
> https://issues.apache.org/jira/browse/TOMEE-2737) into account please
> ?
> Best Regard.
> 
> 
> This message and any attachments are
> intended solely for the addresseesand may contain confidential
> information. Any unauthorized use ordisclosure, either whole or
> partial, is prohibited.E-mails are susceptible to alteration. Our
> company shall not be liable forthe message if altered, changed or
> falsified. If you are not the intendedrecipient of this message,
> please delete it and notify the sender.Although all reasonable
> efforts have been made to keep this transmissionfree from viruses,
> the sender will not be liable for damages caused by atransmitted
> virus.
> 
> 
> 
-- 
Richard Zowalla, M.Sc.Research Associate, PhD Student | Medical Informatics


Hochschule Heilbronn – University of Applied SciencesMax-Planck-Str. 39 D-74081 
Heilbronn phone: +49 7131 504 6791mail: richard.zowalla@hs-heilbronn.deweb: 
http://www.mi.hs-heilbronn.de/ 


smime.p7s
Description: S/MIME cryptographic signature

Re: JIRA about CVEs

[Richard Monson-Haefel]

Is this a matter of upgrading and testing or is there more to it than
that?  If that's it we can create a PR with the updates and let the asf ci
run the tests and look for problems.


On Wed, Nov 13, 2019 at 5:58 AM COURTAULT Francois <
francois.courta...@thalesgroup.com> wrote:

> Hello,
>
> Could you take this JIRA entry (
> https://issues.apache.org/jira/browse/TOMEE-2737) into account please ?
>
> Best Regard.
>
>
>
> 
> This message and any attachments are intended solely for the addressees
> and may contain confidential information. Any unauthorized use or
> disclosure, either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for
> the message if altered, changed or falsified. If you are not the intended
> recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission
> free from viruses, the sender will not be liable for damages caused by a
> transmitted virus.
>


-- 
Richard Monson-Haefel
https://twitter.com/rmonson
https://www.linkedin.com/in/monsonhaefel/

Re: TomEE GraalVM native image

[Richard Monson-Haefel]

Hi!

That would be cool. If memory serves there may be some issues with
reflection and complication but running TomEE on GraalVM should work since
it won't try to compile the reflection stuff.  I haven't run it on GraalVM
myself, but this would be a really cool effort and if you can get it to
work it would be an awesome addition to the project in my opinion.  Are you
interested in testing it out and working on it?

Richard

On Wed, Nov 13, 2019 at 5:35 AM COURTAULT Francois <
francois.courta...@thalesgroup.com> wrote:

> Hello everyone,
>
> I am able to see some initiatives around GraalVM native-image like
> Quarkus, Helidon,...
> I have also seen that Tomcat 9.0.26 could be built as a native image:
> http://tomcat.apache.org/tomcat-9.0-doc/graal.html
>
> Digging on the web, I discover some work on TomEE side as well:
> https://github.com/tomitribe/graalvm-microprofile
>
> Are you working on a TomEE version which can be built as a GraalVM native
> image ?
> I think it should be a quite important topic to consider in the roadmap,
> right ?
>
> Best Regards.
>
>
>
> 
> This message and any attachments are intended solely for the addressees
> and may contain confidential information. Any unauthorized use or
> disclosure, either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for
> the message if altered, changed or falsified. If you are not the intended
> recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission
> free from viruses, the sender will not be liable for damages caused by a
> transmitted virus.
>


-- 
Richard Monson-Haefel
https://twitter.com/rmonson
https://www.linkedin.com/in/monsonhaefel/

Re: TOMEE-2736 - Please check PR 607

[Richard Monson-Haefel]

Nice work!  Thanks for putting in the effort and figuring out the problem!

On Wed, Nov 13, 2019 at 5:03 AM Zowalla, Richard <
richard.zowa...@hs-heilbronn.de> wrote:

> Hi,
>
> please check https://github.com/apache/tomee/pull/607 and the related
> JIRA https://issues.apache.org/jira/projects/TOMEE/issues/TOMEE-2736
>
>
> Would be great, if this could be included in 8.0.1 as this is a blocker for 
> my colleague mawiesne, who consumed a ton of coffee over this bug.
>
>
> Best,
>
> Richard Z
>
>

-- 
Richard Monson-Haefel
https://twitter.com/rmonson
https://www.linkedin.com/in/monsonhaefel/

[GitHub] [tomee] Daniel-Dos commented on issue #606: TOMEE-2734-Upgrade CXF to 3.3.4

[GitBox]

Daniel-Dos commented on issue #606: TOMEE-2734-Upgrade CXF to 3.3.4
URL: https://github.com/apache/tomee/pull/606#issuecomment-553390941
 
 
   Hi Richard ,
   
   I would like, good that I learn something different.
   
   I just need some guidance.
   
   because I just did a lib update, and if I run the build without the tests
   it passes.
   
   Em qua., 13 de nov. de 2019 às 09:46, Richard Monson-Haefel <
   notificati...@github.com> escreveu:
   
   > Hi Daniel,
   >
   > Do you plan to work on this? We are probably going to want to upgrade
   > eventually.
   >
   > Richard
   >
   > On Tue, Nov 12, 2019 at 8:30 PM Daniel Dias 
   > wrote:
   >
   > > Hi @monsonhaefel ,
   > >
   > > from what I saw in the log he gave recursed connection error :
   > >
   > > INFO: Closing DataSource: My Unmanaged DataSource
   > > [ERROR] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
   > 2.439 s <<< FAILURE! - in org.apache.openejb.server.httpd.AsyncHttpTest
   > > [ERROR] async(org.apache.openejb.server.httpd.AsyncHttpTest) Time
   > elapsed: 1.174 s <<< ERROR!
   > > java.net.ConnectException: Connection refused (Connection refused)
   > > at java.net.PlainSocketImpl.socketConnect(Native Method)
   > > at
   > 
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
   > > at
   > 
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
   > > at
   > java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
   > > 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 sun.net.NetworkClient.doConnect(NetworkClient.java:180)
   > > at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
   > > at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
   > > at sun.net.www.http.HttpClient.(HttpClient.java:242)
   > > at sun.net.www.http.HttpClient.New(HttpClient.java:339)
   > > at sun.net.www.http.HttpClient.New(HttpClient.java:357)
   > > at
   > 
sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1220)
   > > at
   > 
sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1156)
   > > at
   > 
sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1050)
   > > at
   > 
sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:984)
   > > at
   > 
sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1564)
   > > at
   > 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
   > > at java.net.URL.openStream(URL.java:1045)
   > > at org.apache.openejb.loader.IO.slurp(IO.java:156)
   > > at
   > org.apache.openejb.server.httpd.AsyncHttpTest.async(AsyncHttpTest.java:58)
   > > 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:498)
   > > at
   > 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
   > > at
   > 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
   > > at
   > 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
   > > at
   > 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
   > > at
   > 
org.apache.openejb.junit.DeployApplication$1.call(DeployApplication.java:44)
   > > at
   > 
org.apache.openejb.junit.DeployApplication$1.call(DeployApplication.java:40)
   > > at
   > 
org.apache.openejb.testing.ApplicationComposers.evaluate(ApplicationComposers.java:1070)
   > > at
   > 
org.apache.openejb.junit.DeployApplication.evaluate(DeployApplication.java:40)
   > > at org.junit.rules.RunRules.evaluate(RunRules.java:20)
   > > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
   > > at
   > 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
   > > at
   > 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
   > > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
   > > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
   > > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
   > > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
   > > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
   > > at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
   > > at
   > 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
   > > at
   > 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)

Re: Issue with Chunked encoding in tomcat/tomee with a specific file

[Richard Monson-Haefel]

OK. That narrows it down. Can you share the client source code?

On Wed, Nov 13, 2019 at 12:39 AM mshvr 
wrote:

> Didn't get any errors in the tomee server but when the client tried to read
> the data from stream, this exception is thrown..
> Just to reiterate, this happens for this specific file only and with same
> set of libraries and client program i didn't see this exception in other
> app
> server..
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>


-- 
Richard Monson-Haefel
https://twitter.com/rmonson
https://www.linkedin.com/in/monsonhaefel/

Re: TOMEE-2734-Upgrade CXF to 3.3.4

[Daniel Dias Dos Santos]

Hi ,

I too had problems with tests full,
for me broke in openejb-core .

I don't know if it's my machine, because it's not very good.

because I also ran the full test on the master and it broke too.
--

*Daniel Dias dos Santos*
Java Developer
SouJava & JCP Member
GitHub: https://github.com/Daniel-Dos
Linkedin: www.linkedin.com/in/danieldiasjava
Twitter: http://twitter.com/danieldiasjava


Em qua., 13 de nov. de 2019 às 09:44, Richard Monson-Haefel <
monsonhae...@gmail.com> escreveu:

> Hi Daniel!
>
> I had some errors when running the full body of TomEE tests. See the PR for
> more details.
>
> Richard
>
> On Tue, Nov 12, 2019 at 2:31 PM Daniel Dias Dos Santos <
> daniel.dias.analist...@gmail.com> wrote:
>
> > Hi ,
> >
> > great  Richard :  )
> > --
> >
> > *Daniel Dias dos Santos*
> > Java Developer
> > SouJava & JCP Member
> > GitHub: https://github.com/Daniel-Dos
> > Linkedin: www.linkedin.com/in/danieldiasjava
> > Twitter: http://twitter.com/danieldiasjava
> >
> >
> > Em ter., 12 de nov. de 2019 às 10:21, Richard Monson-Haefel <
> > monsonhae...@gmail.com> escreveu:
> >
> > > I'm testing the entire project now.  If all is well I think we can
> merge
> > > this.
> > >
> > > On Mon, Nov 11, 2019 at 7:21 PM Daniel Dias Dos Santos <
> > > daniel.dias.analist...@gmail.com> wrote:
> > >
> > > > Hi,
> > > >
> > > > I created a ticket jira[1].
> > > > can some admin assign for me .
> > > > and too open an PR [2] .
> > > >
> > > > [1] https://issues.apache.org/jira/browse/TOMEE-2734
> > > > [2] https://github.com/apache/tomee/pull/606
> > > >
> > > > thanks .
> > > > --
> > > >
> > > > *Daniel Dias dos Santos*
> > > > Java Developer
> > > > SouJava & JCP Member
> > > > GitHub: https://github.com/Daniel-Dos
> > > > Linkedin: www.linkedin.com/in/danieldiasjava
> > > > Twitter: http://twitter.com/danieldiasjava
> > > >
> > >
> > >
> > > --
> > > Richard Monson-Haefel
> > > https://twitter.com/rmonson
> > > https://www.linkedin.com/in/monsonhaefel/
> > >
> >
>
>
> --
> Richard Monson-Haefel
> https://twitter.com/rmonson
> https://www.linkedin.com/in/monsonhaefel/
>

[GitHub] [tomee] monsonhaefel commented on issue #606: TOMEE-2734-Upgrade CXF to 3.3.4

[GitBox]

monsonhaefel commented on issue #606: TOMEE-2734-Upgrade CXF to 3.3.4
URL: https://github.com/apache/tomee/pull/606#issuecomment-553389127
 
 
   Hi Daniel,
   
   Do you plan to work on this? We are probably going to want to upgrade
   eventually.
   
   Richard
   
   On Tue, Nov 12, 2019 at 8:30 PM Daniel Dias 
   wrote:
   
   > Hi @monsonhaefel ,
   >
   > from what I saw in the log he gave recursed connection error :
   >
   > INFO: Closing DataSource: My Unmanaged DataSource
   > [ERROR] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 
2.439 s <<< FAILURE! - in org.apache.openejb.server.httpd.AsyncHttpTest
   > [ERROR] async(org.apache.openejb.server.httpd.AsyncHttpTest)  Time 
elapsed: 1.174 s  <<< ERROR!
   > java.net.ConnectException: Connection refused (Connection refused)
   >at java.net.PlainSocketImpl.socketConnect(Native Method)
   >at 
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
   >at 
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
   >at 
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
   >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 sun.net.NetworkClient.doConnect(NetworkClient.java:180)
   >at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
   >at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
   >at sun.net.www.http.HttpClient.(HttpClient.java:242)
   >at sun.net.www.http.HttpClient.New(HttpClient.java:339)
   >at sun.net.www.http.HttpClient.New(HttpClient.java:357)
   >at 
sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1220)
   >at 
sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1156)
   >at 
sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1050)
   >at 
sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:984)
   >at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1564)
   >at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
   >at java.net.URL.openStream(URL.java:1045)
   >at org.apache.openejb.loader.IO.slurp(IO.java:156)
   >at 
org.apache.openejb.server.httpd.AsyncHttpTest.async(AsyncHttpTest.java:58)
   >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:498)
   >at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
   >at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
   >at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
   >at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
   >at 
org.apache.openejb.junit.DeployApplication$1.call(DeployApplication.java:44)
   >at 
org.apache.openejb.junit.DeployApplication$1.call(DeployApplication.java:40)
   >at 
org.apache.openejb.testing.ApplicationComposers.evaluate(ApplicationComposers.java:1070)
   >at 
org.apache.openejb.junit.DeployApplication.evaluate(DeployApplication.java:40)
   >at org.junit.rules.RunRules.evaluate(RunRules.java:20)
   >at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
   >at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
   >at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
   >at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
   >at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
   >at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
   >at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
   >at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
   >at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
   >at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
   >at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
   >at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
   >at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
   >at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:379)
   >at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:340)
   >at 

Re: TOMEE-2734-Upgrade CXF to 3.3.4

[Richard Monson-Haefel]

Hi Daniel!

I had some errors when running the full body of TomEE tests. See the PR for
more details.

Richard

On Tue, Nov 12, 2019 at 2:31 PM Daniel Dias Dos Santos <
daniel.dias.analist...@gmail.com> wrote:

> Hi ,
>
> great  Richard :  )
> --
>
> *Daniel Dias dos Santos*
> Java Developer
> SouJava & JCP Member
> GitHub: https://github.com/Daniel-Dos
> Linkedin: www.linkedin.com/in/danieldiasjava
> Twitter: http://twitter.com/danieldiasjava
>
>
> Em ter., 12 de nov. de 2019 às 10:21, Richard Monson-Haefel <
> monsonhae...@gmail.com> escreveu:
>
> > I'm testing the entire project now.  If all is well I think we can merge
> > this.
> >
> > On Mon, Nov 11, 2019 at 7:21 PM Daniel Dias Dos Santos <
> > daniel.dias.analist...@gmail.com> wrote:
> >
> > > Hi,
> > >
> > > I created a ticket jira[1].
> > > can some admin assign for me .
> > > and too open an PR [2] .
> > >
> > > [1] https://issues.apache.org/jira/browse/TOMEE-2734
> > > [2] https://github.com/apache/tomee/pull/606
> > >
> > > thanks .
> > > --
> > >
> > > *Daniel Dias dos Santos*
> > > Java Developer
> > > SouJava & JCP Member
> > > GitHub: https://github.com/Daniel-Dos
> > > Linkedin: www.linkedin.com/in/danieldiasjava
> > > Twitter: http://twitter.com/danieldiasjava
> > >
> >
> >
> > --
> > Richard Monson-Haefel
> > https://twitter.com/rmonson
> > https://www.linkedin.com/in/monsonhaefel/
> >
>


-- 
Richard Monson-Haefel
https://twitter.com/rmonson
https://www.linkedin.com/in/monsonhaefel/

Re: TOMEE-2736 - Please check PR 607

[Jonathan Gallimore]

Looks reasonable to me. I'll run a few tests and get that merged in.

On Wed, Nov 13, 2019 at 11:03 AM Zowalla, Richard <
richard.zowa...@hs-heilbronn.de> wrote:

> Hi,
>
> please check https://github.com/apache/tomee/pull/607 and the related
> JIRA https://issues.apache.org/jira/projects/TOMEE/issues/TOMEE-2736
>
>
> Would be great, if this could be included in 8.0.1 as this is a blocker for 
> my colleague mawiesne, who consumed a ton of coffee over this bug.
>
>
> Best,
>
> Richard Z
>
>

TOMEE-2736 - Please check PR 607

[Zowalla, Richard]

Hi,

please check https://github.com/apache/tomee/pull/607 and the related
JIRA https://issues.apache.org/jira/projects/TOMEE/issues/TOMEE-2736

Would be great, if this could be included in 8.0.1 as this is a blocker for my 
colleague mawiesne, who consumed a ton of coffee over this bug.
Best,Richard Z


smime.p7s
Description: S/MIME cryptographic signature

[GitHub] [tomee] asf-ci commented on issue #607: TOMEE-2736 - Override cached system properties in RemoteServer for Maven TomEE Plugin

[GitBox]

asf-ci commented on issue #607: TOMEE-2736 - Override cached system properties 
in RemoteServer for Maven TomEE Plugin
URL: https://github.com/apache/tomee/pull/607#issuecomment-553352434
 
 
   Can one of the admins verify this patch?


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [tomee] asf-ci commented on issue #607: TOMEE-2736 - Override cached system properties in RemoteServer for Maven TomEE Plugin

[GitBox]

asf-ci commented on issue #607: TOMEE-2736 - Override cached system properties 
in RemoteServer for Maven TomEE Plugin
URL: https://github.com/apache/tomee/pull/607#issuecomment-553352439
 
 
   Can one of the admins verify this patch?


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [tomee] rzo1 opened a new pull request #607: TOMEE-2736 - Override cached system properties in RemoteServer for Maven TomEE Plugin

[GitBox]

rzo1 opened a new pull request #607: TOMEE-2736 - Override cached system 
properties in RemoteServer for Maven TomEE Plugin
URL: https://github.com/apache/tomee/pull/607
 
 
   ## What does this PR do?
   
   This PR provides a fix for 
https://issues.apache.org/jira/projects/TOMEE/issues/TOMEE-2736 by using the 
property override mechanism of RemoteServer.
   
   It fixes a regression introduced with 
https://github.com/apache/tomee/commit/6d5e5a39006492fcd6d1ee5b80cbe460168dba86 
, in which SystemProperties are cached within a static context in 
`RemoteServer`.
   
   This is a problem in environments, where a shared JVM is used for the TomEE 
container, e.g. for integration testing in build tools such as Maven, where the 
(Maven) JVM is used and shared across different module builds.
   
   However, this is not a problem for production / standalone TomEE.
   
   
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [tomee] asf-ci commented on issue #607: TOMEE-2736 - Override cached system properties in RemoteServer for Maven TomEE Plugin

[GitBox]

asf-ci commented on issue #607: TOMEE-2736 - Override cached system properties 
in RemoteServer for Maven TomEE Plugin
URL: https://github.com/apache/tomee/pull/607#issuecomment-553352435
 
 
   Can one of the admins verify this patch?


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services