date:20180629

Re: EAR deployment

2018-06-29 Thread Jonathan Gallimore

I'll take a look - will be early next week before I can get to it.

Jon

On Fri, Jun 29, 2018 at 3:50 PM, Romain Manni-Bucau 
wrote:

> ears probably not (but you are not that numerous anymore ;)) but with a
> security manager is more the criteria here IMHO.
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github  rmannibucau> |
> LinkedIn  | Book
>  ee-8-high-performance>
>
>
> Le ven. 29 juin 2018 à 16:44,  a écrit :
>
> > Not terribly familiar with Git, but I assume you asking me to submit a
> > pull request that points to a fix?  The short answer is "no".  I would
> > love to see this fixed, but right now I don't have the time to grok git
> > (we use svn), set up a build environment for Tomee, pickup maven (we use
> > ant+ivy), and figure out the actual bug.If I have to, I will --- but
> > only God knows how long it will be before I can make the time to do these
> > things.
> >
> > But this raises a question: am I really the last person still deploying
> > EARs?!   Really???
> >
> > Thanks for your prompt help -- you guys are amazing!
> > Ross
> >
> >
> >
> >
> >
> > From:   "Romain Manni-Bucau" 
> > To: users@tomee.apache.org,
> > Date:   06/28/2018 04:03 PM
> > Subject:Re: EAR deployment
> >
> >
> >
> > I see
> >
> > Then it is just a bug and we miss a wrapping to be SM compliant in that
> > part of the code.
> >
> > Do you want to submit a PR to fix it?
> >
> > Le jeu. 28 juin 2018 19:37,  a écrit :
> >
> > > Couldn't find it in the summary.   Of course, its there as a VM
> > argument,
> > > but I expect that.   After digging around a bit more I found it in the
> > > MXBeans:  java.lang -> Runtime -> Attributes.
> > >
> > > Every thing there is set as it is in the file: ie
> > > java.security.policy=C:\IBM\liferay\tomee\conf\catalina.policy
> > > java.security.manager=
> > >
> > > -- both of which I would expect.
> > >
> > > Note that I have not tried chang  in
> > tomee.xml.
> > > Maybe that needs chaning -- though what I have seem really close to
> > > working.
> > >
> > > Just occurred to me that I never included my full VM args:
> > >
> > > -Dcatalina.base="C:\IBM\liferay\tomee"
> > > -Dcatalina.home="C:\IBM\liferay\tomee"
> > > -Dwtp.deploy="C:\IBM\liferay\tomee\webapps"
> > > -Djava.endorsed.dirs="C:\IBM\liferay\tomee\endorsed"
> > > -Dfile.encoding=UTF8 -Djava.net.preferIPv4Stack=true
> > >
> >
> > -Dorg.apache.catalina.loader.WebappClassLoader.ENABLE_
> CLEAR_REFERENCES=false
> > >
> > >
> > > -Duser.timezone=EST
> > > -Djava.security.manager
> > > -Djava.security.policy="C:\IBM\liferay\tomee\conf\catalina.policy"
> > >
> > -Djava.security.auth.login.config="C:\IBM\liferay\tomee\
> conf\jaas.config"
> > > -Dwnyric.deployment.properties.directory.path="C:\IBM\liferay"
> > > -Xmx2048m
> > >
> > >
> > > Thanks,
> > > Ross
> > >
> > >
> > >
> > >
> > >
> > > From:   "Romain Manni-Bucau" 
> > > To: users@tomee.apache.org,
> > > Date:   06/28/2018 11:20 AM
> > > Subject:Re: EAR deployment
> > >
> > >
> > >
> > > I think you can check it in the JVM info in system properties (VM
> > Summary)
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau <
> > >
> > >
> >
> > https://milton-web.wnyric.org/canit/urlproxy.php?_q=
> aHR0cHM6Ly90d2l0dGVyLmNvbS9ybWFubmlidWNhdQ%3D%3D&_s=ZXJpZTE%3D&_c=7b6344b3
> >
> > > > |  Blog
> > > <
> > >
> > >
> >
> > https://milton-web.wnyric.org/canit/urlproxy.php?_q=
> aHR0cHM6Ly9ybWFubmlidWNhdS5tZXRhd2VyeC5uZXQv&_s=ZXJpZTE%3D&_c=03b3f7d2
> >
> > > > | Old Blog
> > > <
> > >
> > >
> >
> > https://milton-web.wnyric.org/canit/urlproxy.php?_q=
> aHR0cDovL3JtYW5uaWJ1Y2F1LndvcmRwcmVzcy5jb20%3D&_s=ZXJpZTE%3D&_c=7ac52c4b
> >
> > > > | Github <
> > >
> > >
> >
> > https://milton-web.wnyric.org/canit/urlproxy.php?_q=
> aHR0cHM6Ly9naXRodWIuY29tL3JtYW5uaWJ1Y2F1&_s=ZXJpZTE%3D&_c=d53ffcf9
> >
> > > > |
> > > LinkedIn <
> > >
> > >
> >
> > https://milton-web.wnyric.org/canit/urlproxy.php?_q=
> aHR0cHM6Ly93d3cubGlua2VkaW4uY29tL2luL3JtYW5uaWJ1Y2F1&_s=
> ZXJpZTE%3D&_c=aff046f7
> >
> > > > | Book
> > > <
> > >
> > >
> >
> > https://milton-web.wnyric.org/canit/urlproxy.php?_q=
> aHR0cHM6Ly93d3cucGFja3RwdWIuY29tL2FwcGxpY2F0aW9uLWRldmVsb3Bt
> ZW50L2phdmEtZWUtOC1oaWdoLXBlcmZvcm1hbmNl&_s=ZXJpZTE%3D&_c=5ede79c4
> >
> > > >
> > >
> > >
> > > Le jeu. 28 juin 2018 à 17:19,  a écrit :
> > >
> > > > So:
> > > >
> > > > 1.   With the security manager disabled, the ear deploys fine, ejb's
> > > > instantitiate, initialize, etc -- no errors at all!
> > > >
> > > > 2.  I connected to the running jvm with jmx, and poked around for a
> > > while,
> > > > but could not find where it specified the policy file Tomcat was
> > using.
> > > > Can I get a hint as to where this info is?
> > > >
> > > > Thanks,
> > > > Ross
> > > >
> > > >
> > > >
> > > >

Re: EAR deployment

2018-06-29 Thread Romain Manni-Bucau

ears probably not (but you are not that numerous anymore ;)) but with a
security manager is more the criteria here IMHO.

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le ven. 29 juin 2018 à 16:44,  a écrit :

> Not terribly familiar with Git, but I assume you asking me to submit a
> pull request that points to a fix?  The short answer is "no".  I would
> love to see this fixed, but right now I don't have the time to grok git
> (we use svn), set up a build environment for Tomee, pickup maven (we use
> ant+ivy), and figure out the actual bug.If I have to, I will --- but
> only God knows how long it will be before I can make the time to do these
> things.
>
> But this raises a question: am I really the last person still deploying
> EARs?!   Really???
>
> Thanks for your prompt help -- you guys are amazing!
> Ross
>
>
>
>
>
> From:   "Romain Manni-Bucau" 
> To: users@tomee.apache.org,
> Date:   06/28/2018 04:03 PM
> Subject:Re: EAR deployment
>
>
>
> I see
>
> Then it is just a bug and we miss a wrapping to be SM compliant in that
> part of the code.
>
> Do you want to submit a PR to fix it?
>
> Le jeu. 28 juin 2018 19:37,  a écrit :
>
> > Couldn't find it in the summary.   Of course, its there as a VM
> argument,
> > but I expect that.   After digging around a bit more I found it in the
> > MXBeans:  java.lang -> Runtime -> Attributes.
> >
> > Every thing there is set as it is in the file: ie
> > java.security.policy=C:\IBM\liferay\tomee\conf\catalina.policy
> > java.security.manager=
> >
> > -- both of which I would expect.
> >
> > Note that I have not tried chang  in
> tomee.xml.
> > Maybe that needs chaning -- though what I have seem really close to
> > working.
> >
> > Just occurred to me that I never included my full VM args:
> >
> > -Dcatalina.base="C:\IBM\liferay\tomee"
> > -Dcatalina.home="C:\IBM\liferay\tomee"
> > -Dwtp.deploy="C:\IBM\liferay\tomee\webapps"
> > -Djava.endorsed.dirs="C:\IBM\liferay\tomee\endorsed"
> > -Dfile.encoding=UTF8 -Djava.net.preferIPv4Stack=true
> >
>
> -Dorg.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES=false
> >
> >
> > -Duser.timezone=EST
> > -Djava.security.manager
> > -Djava.security.policy="C:\IBM\liferay\tomee\conf\catalina.policy"
> >
> -Djava.security.auth.login.config="C:\IBM\liferay\tomee\conf\jaas.config"
> > -Dwnyric.deployment.properties.directory.path="C:\IBM\liferay"
> > -Xmx2048m
> >
> >
> > Thanks,
> > Ross
> >
> >
> >
> >
> >
> > From:   "Romain Manni-Bucau" 
> > To: users@tomee.apache.org,
> > Date:   06/28/2018 11:20 AM
> > Subject:Re: EAR deployment
> >
> >
> >
> > I think you can check it in the JVM info in system properties (VM
> Summary)
> >
> > Romain Manni-Bucau
> > @rmannibucau <
> >
> >
>
> https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly90d2l0dGVyLmNvbS9ybWFubmlidWNhdQ%3D%3D&_s=ZXJpZTE%3D&_c=7b6344b3
>
> > > |  Blog
> > <
> >
> >
>
> https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9ybWFubmlidWNhdS5tZXRhd2VyeC5uZXQv&_s=ZXJpZTE%3D&_c=03b3f7d2
>
> > > | Old Blog
> > <
> >
> >
>
> https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cDovL3JtYW5uaWJ1Y2F1LndvcmRwcmVzcy5jb20%3D&_s=ZXJpZTE%3D&_c=7ac52c4b
>
> > > | Github <
> >
> >
>
> https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9naXRodWIuY29tL3JtYW5uaWJ1Y2F1&_s=ZXJpZTE%3D&_c=d53ffcf9
>
> > > |
> > LinkedIn <
> >
> >
>
> https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly93d3cubGlua2VkaW4uY29tL2luL3JtYW5uaWJ1Y2F1&_s=ZXJpZTE%3D&_c=aff046f7
>
> > > | Book
> > <
> >
> >
>
> https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly93d3cucGFja3RwdWIuY29tL2FwcGxpY2F0aW9uLWRldmVsb3BtZW50L2phdmEtZWUtOC1oaWdoLXBlcmZvcm1hbmNl&_s=ZXJpZTE%3D&_c=5ede79c4
>
> > >
> >
> >
> > Le jeu. 28 juin 2018 à 17:19,  a écrit :
> >
> > > So:
> > >
> > > 1.   With the security manager disabled, the ear deploys fine, ejb's
> > > instantitiate, initialize, etc -- no errors at all!
> > >
> > > 2.  I connected to the running jvm with jmx, and poked around for a
> > while,
> > > but could not find where it specified the policy file Tomcat was
> using.
> > > Can I get a hint as to where this info is?
> > >
> > > Thanks,
> > > Ross
> > >
> > >
> > >
> > > From:   "Romain Manni-Bucau" 
> > > To: users@tomee.apache.org,
> > > Date:   06/27/2018 04:54 PM
> > > Subject:Re: EAR deployment
> > >
> > >
> > >
> > > Hi
> > >
> > > can you confirm it works without the security manager enabled?
> > >
> > > Also can you check connecting on the JVM through JMX that the right
> > policy
> > > file is used and tomcat didn't override the one you thought using?
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau <
> > >
> > >
> >
> >
>
>

Re: EAR deployment

2018-06-29 Thread rcohen

Not terribly familiar with Git, but I assume you asking me to submit a 
pull request that points to a fix?  The short answer is "no".  I would 
love to see this fixed, but right now I don't have the time to grok git 
(we use svn), set up a build environment for Tomee, pickup maven (we use 
ant+ivy), and figure out the actual bug.If I have to, I will --- but 
only God knows how long it will be before I can make the time to do these 
things.

But this raises a question: am I really the last person still deploying 
EARs?!   Really???

Thanks for your prompt help -- you guys are amazing!
Ross





From:   "Romain Manni-Bucau" 
To: users@tomee.apache.org, 
Date:   06/28/2018 04:03 PM
Subject:Re: EAR deployment



I see

Then it is just a bug and we miss a wrapping to be SM compliant in that
part of the code.

Do you want to submit a PR to fix it?

Le jeu. 28 juin 2018 19:37,  a écrit :

> Couldn't find it in the summary.   Of course, its there as a VM 
argument,
> but I expect that.   After digging around a bit more I found it in the
> MXBeans:  java.lang -> Runtime -> Attributes.
>
> Every thing there is set as it is in the file: ie
> java.security.policy=C:\IBM\liferay\tomee\conf\catalina.policy
> java.security.manager=
>
> -- both of which I would expect.
>
> Note that I have not tried chang  in 
tomee.xml.
> Maybe that needs chaning -- though what I have seem really close to
> working.
>
> Just occurred to me that I never included my full VM args:
>
> -Dcatalina.base="C:\IBM\liferay\tomee"
> -Dcatalina.home="C:\IBM\liferay\tomee"
> -Dwtp.deploy="C:\IBM\liferay\tomee\webapps"
> -Djava.endorsed.dirs="C:\IBM\liferay\tomee\endorsed"
> -Dfile.encoding=UTF8 -Djava.net.preferIPv4Stack=true
> 
-Dorg.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES=false
>
>
> -Duser.timezone=EST
> -Djava.security.manager
> -Djava.security.policy="C:\IBM\liferay\tomee\conf\catalina.policy"
> 
-Djava.security.auth.login.config="C:\IBM\liferay\tomee\conf\jaas.config"
> -Dwnyric.deployment.properties.directory.path="C:\IBM\liferay"
> -Xmx2048m
>
>
> Thanks,
> Ross
>
>
>
>
>
> From:   "Romain Manni-Bucau" 
> To: users@tomee.apache.org,
> Date:   06/28/2018 11:20 AM
> Subject:Re: EAR deployment
>
>
>
> I think you can check it in the JVM info in system properties (VM 
Summary)
>
> Romain Manni-Bucau
> @rmannibucau <
>
> 
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly90d2l0dGVyLmNvbS9ybWFubmlidWNhdQ%3D%3D&_s=ZXJpZTE%3D&_c=7b6344b3

> > |  Blog
> <
>
> 
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9ybWFubmlidWNhdS5tZXRhd2VyeC5uZXQv&_s=ZXJpZTE%3D&_c=03b3f7d2

> > | Old Blog
> <
>
> 
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cDovL3JtYW5uaWJ1Y2F1LndvcmRwcmVzcy5jb20%3D&_s=ZXJpZTE%3D&_c=7ac52c4b

> > | Github <
>
> 
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9naXRodWIuY29tL3JtYW5uaWJ1Y2F1&_s=ZXJpZTE%3D&_c=d53ffcf9

> > |
> LinkedIn <
>
> 
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly93d3cubGlua2VkaW4uY29tL2luL3JtYW5uaWJ1Y2F1&_s=ZXJpZTE%3D&_c=aff046f7

> > | Book
> <
>
> 
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly93d3cucGFja3RwdWIuY29tL2FwcGxpY2F0aW9uLWRldmVsb3BtZW50L2phdmEtZWUtOC1oaWdoLXBlcmZvcm1hbmNl&_s=ZXJpZTE%3D&_c=5ede79c4

> >
>
>
> Le jeu. 28 juin 2018 à 17:19,  a écrit :
>
> > So:
> >
> > 1.   With the security manager disabled, the ear deploys fine, ejb's
> > instantitiate, initialize, etc -- no errors at all!
> >
> > 2.  I connected to the running jvm with jmx, and poked around for a
> while,
> > but could not find where it specified the policy file Tomcat was 
using.
> > Can I get a hint as to where this info is?
> >
> > Thanks,
> > Ross
> >
> >
> >
> > From:   "Romain Manni-Bucau" 
> > To: users@tomee.apache.org,
> > Date:   06/27/2018 04:54 PM
> > Subject:Re: EAR deployment
> >
> >
> >
> > Hi
> >
> > can you confirm it works without the security manager enabled?
> >
> > Also can you check connecting on the JVM through JMX that the right
> policy
> > file is used and tomcat didn't override the one you thought using?
> >
> > Romain Manni-Bucau
> > @rmannibucau <
> >
> >
>
> 
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly90d2l0dGVyLmNvbS9ybWFubmlidWNhdQ%3D%3D&_s=ZXJpZTE%3D&_c=7b6344b3

>
> > > |  Blog
> > <
> >
> >
>
> 
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9ybWFubmlidWNhdS5tZXRhd2VyeC5uZXQv&_s=ZXJpZTE%3D&_c=03b3f7d2

>
> > > | Old Blog
> > <
> >
> >
>
> 
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cDovL3JtYW5uaWJ1Y2F1LndvcmRwcmVzcy5jb20%3D&_s=ZXJpZTE%3D&_c=7ac52c4b

>
> > > | Github <
> >
> >
>
> 
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly9naXRodWIuY29tL3JtYW5uaWJ1Y2F1&_s=ZXJpZTE%3D&_c=d53ffcf9

>
> > > |
> > LinkedIn <
> >
> >
>
> 
https://milton-web.wnyric.org/canit/urlproxy.php?_q=aHR0cHM6Ly93d3cubGlua2VkaW4uY29tL2luL3JtYW5uaWJ1Y2F1&_s=ZXJpZTE%3D&_c=aff046f7

>
> > > | Book
> > <
> >
> >
>
>

Re: FailOnUnknowActivationSpec for MessageDriven Bean

2018-06-29 Thread Romain Manni-Bucau

Hi Gropp,

feel free to do a PR on https://github.com/apache/tomee-site-generator.
This is also probably related to this one
https://github.com/apache/tomee-site-generator/pull/4

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le ven. 29 juin 2018 à 12:42, Gropp Volker  a
écrit :

> Hi,
>
> the documentation
> http://tomee.apache.org/admin/configuration/containers.html is not
> updated, so I used the 'old' wrong spelling. The spelling was fixed in
> https://issues.apache.org/jira/browse/TOMEE-2093 without updating the
> documentation. This was a pain to resolve. For anyone who is looking for a
> solution, I updated my openejb test repository with a working
> configuration: https://github.com/vgropp/openEjbContainer
>
> Regards Volker Gropp
>
> From: Gropp Volker [mailto:volker.gr...@e-velopment.de]
> Sent: Freitag, 22. Juni 2018 17:06
> To: users@tomee.apache.org
> Subject: FailOnUnknowActivationSpec for MessageDriven Bean
>
> Hi,
>
> is it possible to either not deploy MessageDriven Beans at all in openejb
> or turn off FailOnUnknowActivationSpec for all Container/MDB using
> properties? I use openEjb for my container based unit-tests and it fails
> to deploy a JMS MDB with
> messageListenerInterface = MessageListener.class,
> activationConfig = {
> @ActivationConfigProperty(propertyName="maxSession",
> propertyValue="1")
>  }
>
> I found you can declare it in Properties using
> http://tomee.apache.org/admin/configuration/containers.html
> But after adding that I get:
> Assembler failed to build the container system.
> org.apache.openejb.OpenEJBException: No existing resource adapter defined
> with id 'Default JMS Resource Adapter'.
>
> My original error without trying to set FailOnUnknowActivationSpec to
> false is:
>
> org.apache.openejb.OpenEjbContainer$AssembleApplicationException:
> org.apache.openejb.OpenEJBException: Creating application failed: C:\test:
> Error deploying 'ListenerMDB'.  Exception: class
> org.apache.openejb.OpenEJBException: Unable to create activation spec: No
> setter found for the activation spec properties: [maxSession]: Unable to
> create activation spec: No setter found for the activation spec properties:
> [maxSession]
>  at
> org.apache.openejb.OpenEjbContainer$Provider.createEJBContainer(OpenEjbContainer.java:347)
>  at
> javax.ejb.embeddable.EJBContainer.createEJBContainer(EJBContainer.java:127)
>  at
> de.evelopment.openejb.util.EjbTestHelper.startContainer(EjbTestHelper.java:91)
>  at de.evelopment.openejb.EjbTestCase.startUp(EjbTestCase.java:39)
>  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.RunBefores.evaluate(RunBefores.java:24)
>  at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>  at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>  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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>  at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>  at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>  at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>  at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>  at
>

RE: FailOnUnknowActivationSpec for MessageDriven Bean

2018-06-29 Thread Gropp Volker

Hi,

the documentation http://tomee.apache.org/admin/configuration/containers.html 
is not updated, so I used the 'old' wrong spelling. The spelling was fixed in 
https://issues.apache.org/jira/browse/TOMEE-2093 without updating the 
documentation. This was a pain to resolve. For anyone who is looking for a 
solution, I updated my openejb test repository with a working configuration: 
https://github.com/vgropp/openEjbContainer

Regards Volker Gropp

From: Gropp Volker [mailto:volker.gr...@e-velopment.de]
Sent: Freitag, 22. Juni 2018 17:06
To: users@tomee.apache.org
Subject: FailOnUnknowActivationSpec for MessageDriven Bean

Hi,

is it possible to either not deploy MessageDriven Beans at all in openejb or 
turn off FailOnUnknowActivationSpec for all Container/MDB using properties? I 
use openEjb for my container based unit-tests and it fails  to deploy a JMS MDB 
with
messageListenerInterface = MessageListener.class,
activationConfig = {
@ActivationConfigProperty(propertyName="maxSession", propertyValue="1")
 }

I found you can declare it in Properties using 
http://tomee.apache.org/admin/configuration/containers.html
But after adding that I get:
Assembler failed to build the container system.
org.apache.openejb.OpenEJBException: No existing resource adapter defined with 
id 'Default JMS Resource Adapter'.

My original error without trying to set FailOnUnknowActivationSpec to false is:

org.apache.openejb.OpenEjbContainer$AssembleApplicationException: 
org.apache.openejb.OpenEJBException: Creating application failed: C:\test: 
Error deploying 'ListenerMDB'.  Exception: class 
org.apache.openejb.OpenEJBException: Unable to create activation spec: No 
setter found for the activation spec properties: [maxSession]: Unable to create 
activation spec: No setter found for the activation spec properties: 
[maxSession]
 at 
org.apache.openejb.OpenEjbContainer$Provider.createEJBContainer(OpenEjbContainer.java:347)
 at 
javax.ejb.embeddable.EJBContainer.createEJBContainer(EJBContainer.java:127)
 at 
de.evelopment.openejb.util.EjbTestHelper.startContainer(EjbTestHelper.java:91)
 at de.evelopment.openejb.EjbTestCase.startUp(EjbTestCase.java:39)
 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.RunBefores.evaluate(RunBefores.java:24)
 at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
 at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
 at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
 at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
 at org.junit.rules.RunRules.evaluate(RunRules.java:20)
 at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
 at 
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
 at 
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
 at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:538)
 at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:760)
 at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:460)
 at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:206)
Caused by: org.apache.openejb.OpenEJBException: Creating application failed: 
C:\test: Error deploying 'ListenerMDB'.  Exception: class 
org.apache.openejb.OpenEJBException: Unable to create activation spec: No

Re: EAR deployment

Re: EAR deployment

Re: EAR deployment

Re: FailOnUnknowActivationSpec for MessageDriven Bean

RE: FailOnUnknowActivationSpec for MessageDriven Bean

5 matches

Site Navigation

Mail list logo

Footer information