[jira] [Created] (TOMEE-1075) openejb.home system properties not correctly set
Jonathan Gallimore created TOMEE-1075: - Summary: openejb.home system properties not correctly set Key: TOMEE-1075 URL: https://issues.apache.org/jira/browse/TOMEE-1075 Project: TomEE Issue Type: Bug Affects Versions: 1.6.0 Environment: OSX 10.8, Java 1.7 Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore When org.apache.openejb.config.NewLoaderLogic.getExclusions() calls SystemInstance.get().getConf(EXCLUSION_FILE), openejb.home has not been set. SystemInstance therefore tries 'user.directory', which in my case was $TOMEE_HOME/bin and not $TOMEE_HOME. Seems that this happens *before* the TomcatLoader is invoked, which does set the property correctly. Looks like the javaagent loading is causing this behaviour at first glance. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (TOMEE-1213) Add support for security-role-ref
Jonathan Gallimore created TOMEE-1213: - Summary: Add support for security-role-ref Key: TOMEE-1213 URL: https://issues.apache.org/jira/browse/TOMEE-1213 Project: TomEE Issue Type: New Feature Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Priority: Minor Fix For: 1.7.0 Spec section 17.3.3 - allow the role specified in security-role-ref/role-link to be used if present -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (TOMEE-1342) OutputGeneratedDescriptors doesn't output complete ejb-jar.xml
Jonathan Gallimore created TOMEE-1342: - Summary: OutputGeneratedDescriptors doesn't output complete ejb-jar.xml Key: TOMEE-1342 URL: https://issues.apache.org/jira/browse/TOMEE-1342 Project: TomEE Issue Type: Bug Affects Versions: 1.7.0 Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Priority: Minor Fix For: 2.0.0, 1.7.1 Under certain circumstances the OutputGeneratedDescriptors functionality does not work correctly with the ejb-jar.xml being truncated after writing the enterprise-beans/ tag. The appears to be caused by the serializer not allowing subclasses of SessionBean (such as StatelessBean, SingletonBean etc). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TOMEE-1343) HSQL server shuts down saying no databases available
Jonathan Gallimore created TOMEE-1343: - Summary: HSQL server shuts down saying no databases available Key: TOMEE-1343 URL: https://issues.apache.org/jira/browse/TOMEE-1343 Project: TomEE Issue Type: Bug Affects Versions: 1.7.0 Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Priority: Minor Fix For: 2.0.0, 1.7.1 Setting disabled=false in hsql.properties allows the hsql service to start, but it shuts down straight away saying there are no databases available, even when a HSQL database is configured in tomee.xml. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1342) OutputGeneratedDescriptors doesn't output complete ejb-jar.xml
[ https://issues.apache.org/jira/browse/TOMEE-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore updated TOMEE-1342: -- Attachment: tomee-1342.diff Proposed patch for the tomee-1.7.x branch OutputGeneratedDescriptors doesn't output complete ejb-jar.xml -- Key: TOMEE-1342 URL: https://issues.apache.org/jira/browse/TOMEE-1342 Project: TomEE Issue Type: Bug Affects Versions: 1.7.0 Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Priority: Minor Fix For: 2.0.0, 1.7.1 Attachments: tomee-1342.diff Under certain circumstances the OutputGeneratedDescriptors functionality does not work correctly with the ejb-jar.xml being truncated after writing the enterprise-beans/ tag. The appears to be caused by the serializer not allowing subclasses of SessionBean (such as StatelessBean, SingletonBean etc). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (TOMEE-1343) HSQL server shuts down saying no databases available
[ https://issues.apache.org/jira/browse/TOMEE-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-1343 started by Jonathan Gallimore. - HSQL server shuts down saying no databases available Key: TOMEE-1343 URL: https://issues.apache.org/jira/browse/TOMEE-1343 Project: TomEE Issue Type: Bug Affects Versions: 1.7.0 Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Priority: Minor Fix For: 2.0.0, 1.7.1 Setting disabled=false in hsql.properties allows the hsql service to start, but it shuts down straight away saying there are no databases available, even when a HSQL database is configured in tomee.xml. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1343) HSQL server shuts down saying no databases available
[ https://issues.apache.org/jira/browse/TOMEE-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore updated TOMEE-1343: -- Attachment: tomee-1343.diff Patch for tomee-1.7.x branch HSQL server shuts down saying no databases available Key: TOMEE-1343 URL: https://issues.apache.org/jira/browse/TOMEE-1343 Project: TomEE Issue Type: Bug Affects Versions: 1.7.0 Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Priority: Minor Fix For: 2.0.0, 1.7.1 Attachments: tomee-1343.diff Setting disabled=false in hsql.properties allows the hsql service to start, but it shuts down straight away saying there are no databases available, even when a HSQL database is configured in tomee.xml. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TOMEE-1343) HSQL server shuts down saying no databases available
[ https://issues.apache.org/jira/browse/TOMEE-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore resolved TOMEE-1343. --- Resolution: Fixed HSQL server shuts down saying no databases available Key: TOMEE-1343 URL: https://issues.apache.org/jira/browse/TOMEE-1343 Project: TomEE Issue Type: Bug Affects Versions: 1.7.0 Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Priority: Minor Fix For: 2.0.0, 1.7.1 Attachments: tomee-1343.diff Setting disabled=false in hsql.properties allows the hsql service to start, but it shuts down straight away saying there are no databases available, even when a HSQL database is configured in tomee.xml. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TOMEE-1342) OutputGeneratedDescriptors doesn't output complete ejb-jar.xml
[ https://issues.apache.org/jira/browse/TOMEE-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore resolved TOMEE-1342. --- Resolution: Fixed OutputGeneratedDescriptors doesn't output complete ejb-jar.xml -- Key: TOMEE-1342 URL: https://issues.apache.org/jira/browse/TOMEE-1342 Project: TomEE Issue Type: Bug Affects Versions: 1.7.0 Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Priority: Minor Fix For: 2.0.0, 1.7.1 Attachments: tomee-1342.diff Under certain circumstances the OutputGeneratedDescriptors functionality does not work correctly with the ejb-jar.xml being truncated after writing the enterprise-beans/ tag. The appears to be caused by the serializer not allowing subclasses of SessionBean (such as StatelessBean, SingletonBean etc). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TOMEE-1442) Show list of deployed applications (including EARs) in the console
Jonathan Gallimore created TOMEE-1442: - Summary: Show list of deployed applications (including EARs) in the console Key: TOMEE-1442 URL: https://issues.apache.org/jira/browse/TOMEE-1442 Project: TomEE Issue Type: New Feature Affects Versions: 1.7.1 Reporter: Jonathan Gallimore Fix For: 1.7.2 The TomEE gui doesn't currently provide any information other than Your server is fully installed. We should provide a simple screen that lists all of the currently deployed applications including .ear files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (TOMEE-1493) Class loader working for wars but not ears
[ https://issues.apache.org/jira/browse/TOMEE-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore reassigned TOMEE-1493: - Assignee: Jonathan Gallimore Class loader working for wars but not ears -- Key: TOMEE-1493 URL: https://issues.apache.org/jira/browse/TOMEE-1493 Project: TomEE Issue Type: Task Affects Versions: 1.7.0 Reporter: Tom Molloy Assignee: Jonathan Gallimore We seem to be having an issue with class loading. When we package unzip our ear file and copy the wars to the webapps folder, our app works just fine. However when place the ear in the apps folder, we get a lot of class not found errors on our own classes as well as 3rd party. Should these not act the same? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TOMEE-1547) Use application classloader for resources defined in resources.xml
Jonathan Gallimore created TOMEE-1547:
-
Summary: Use application classloader for resources defined in
resources.xml
Key: TOMEE-1547
URL: https://issues.apache.org/jira/browse/TOMEE-1547
Project: TomEE
Issue Type: Improvement
Affects Versions: 1.7.1
Reporter: Jonathan Gallimore
Assignee: Jonathan Gallimore
Fix For: 2.0.0-Milestone-1, 1.7.2
Resources can be defined in applications using META-INF/resources.xml. This is
a useful feature, but because resources are created very early on in deployment
the final classloader for the application is not available.
I know I can manually specify a specific jar or classpath, but I specifically
want the resources I define to be loaded using the same classpath the
application uses.
So, for example, if I have an EJB jar in an EAR, and the EJB jar contains a
POJO called HelloBean, the following should load the resource from the
application classloader:
Resources
Resource id=Hello type=org.superbiz.HelloBean
property1 value1
property2 value2
/Resource
/Resources
Currently this fails with a class not found error, due to the following in
org.apache.openejb.assembler.classic.Assembler.createResource(ResourceInfo):
ClassLoader loader = Thread.currentThread().getContextClassLoader();
boolean customLoader = false;
try {
if (serviceInfo.classpath != null serviceInfo.classpath.length
0) {
final URL[] urls = new URL[serviceInfo.classpath.length];
for (int i = 0; i serviceInfo.classpath.length; i++) {
urls[i] = serviceInfo.classpath[i].toURL();
}
loader = new URLClassLoaderFirst(urls, loader);
customLoader = true;
}
} catch (final MalformedURLException e) {
throw new OpenEJBException(Unable to create a classloader for +
serviceInfo.id, e);
}
Object service = serviceRecipe.create(loader);
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (TOMEE-1554) Upgrade OpenJPA to 2.4.0
[ https://issues.apache.org/jira/browse/TOMEE-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore resolved TOMEE-1554. --- Resolution: Fixed Upgrade OpenJPA to 2.4.0 Key: TOMEE-1554 URL: https://issues.apache.org/jira/browse/TOMEE-1554 Project: TomEE Issue Type: Dependency upgrade Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Fix For: 2.0.0-Milestone-1, 1.7.2 OpenJPA 2.4.0 vote has passed. Upgrade TomEE to use it instead of the non-final version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TOMEE-1605) Status Page for Java EE 7
[ https://issues.apache.org/jira/browse/TOMEE-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore resolved TOMEE-1605. --- Resolution: Fixed Done, thanks for the patch, Roberto! Status Page for Java EE 7 - Key: TOMEE-1605 URL: https://issues.apache.org/jira/browse/TOMEE-1605 Project: TomEE Issue Type: Documentation Affects Versions: 7.0.0-M1 Reporter: Roberto Cortez Assignee: Jonathan Gallimore Fix For: 7.0.0-M1 Attachments: Added_status_page_for_Java_EE_7_.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (TOMEE-1605) Status Page for Java EE 7
[ https://issues.apache.org/jira/browse/TOMEE-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore reassigned TOMEE-1605: - Assignee: Jonathan Gallimore Status Page for Java EE 7 - Key: TOMEE-1605 URL: https://issues.apache.org/jira/browse/TOMEE-1605 Project: TomEE Issue Type: Documentation Affects Versions: 7.0.0-M1 Reporter: Roberto Cortez Assignee: Jonathan Gallimore Fix For: 7.0.0-M1 Attachments: Added_status_page_for_Java_EE_7_.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TOMEE-1688) Retry authentication if client identity is not logged in
Jonathan Gallimore created TOMEE-1688: - Summary: Retry authentication if client identity is not logged in Key: TOMEE-1688 URL: https://issues.apache.org/jira/browse/TOMEE-1688 Project: TomEE Issue Type: Improvement Affects Versions: 1.7.3 Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Fix For: 1.7.4 We are periodically seeing this exception: using 1.7.3: javax.security.auth.login.LoginException: Identity is not currently logged in: 4c201f33-5181-474b-b57a-854ee019bc26 at org.apache.openejb.core.security.AbstractSecurityService.associate(AbstractSecurityService.java:219) at org.apache.openejb.core.security.AbstractSecurityService.associate(AbstractSecurityService.java:61) at org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:287) at com.sun.proxy.$Proxy70.create(Unknown Source) at org.apache.openejb.core.ivm.naming.BusinessRemoteReference.getObject(BusinessRemoteReference.java:36) at org.apache.openejb.core.ivm.naming.IvmContext.lookup(IvmContext.java:175) at org.apache.openejb.server.ejbd.JndiRequestHandler.doLookup(JndiRequestHandler.java:261) at org.apache.openejb.server.ejbd.JndiRequestHandler.processResponse(JndiRequestHandler.java:174) at org.apache.openejb.server.ejbd.EjbDaemon.processJndiResponse(EjbDaemon.java:360) at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:272) at org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:86) at org.apache.openejb.server.httpd.ServerServlet.service(ServerServlet.java:58) at javax.servlet.http.HttpServlet.service(HttpServlet.java:731) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122) at org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:44) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:423) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1079) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:620) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1741) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1700) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1688) Retry authentication if client identity is not logged in
[ https://issues.apache.org/jira/browse/TOMEE-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore updated TOMEE-1688: -- Attachment: tomee-1688.patch Potential patch for discussion > Retry authentication if client identity is not logged in > > > Key: TOMEE-1688 > URL: https://issues.apache.org/jira/browse/TOMEE-1688 > Project: TomEE > Issue Type: Improvement >Affects Versions: 1.7.3 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore > Fix For: 1.7.4 > > Attachments: tomee-1688.patch > > > We are periodically seeing this exception: using 1.7.3: > javax.security.auth.login.LoginException: Identity is not currently logged > in: 4c201f33-5181-474b-b57a-854ee019bc26 > at > org.apache.openejb.core.security.AbstractSecurityService.associate(AbstractSecurityService.java:219) > at > org.apache.openejb.core.security.AbstractSecurityService.associate(AbstractSecurityService.java:61) > at > org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:287) > at com.sun.proxy.$Proxy70.create(Unknown Source) > at > org.apache.openejb.core.ivm.naming.BusinessRemoteReference.getObject(BusinessRemoteReference.java:36) > at org.apache.openejb.core.ivm.naming.IvmContext.lookup(IvmContext.java:175) > at > org.apache.openejb.server.ejbd.JndiRequestHandler.doLookup(JndiRequestHandler.java:261) > at > org.apache.openejb.server.ejbd.JndiRequestHandler.processResponse(JndiRequestHandler.java:174) > at > org.apache.openejb.server.ejbd.EjbDaemon.processJndiResponse(EjbDaemon.java:360) > at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:272) > at org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:86) > at > org.apache.openejb.server.httpd.ServerServlet.service(ServerServlet.java:58) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:731) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122) > at org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:44) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103) > at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:423) > at > org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1079) > at > org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:620) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1741) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1700) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at > org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TOMEE-1688) Retry authentication if client identity is not logged in
[ https://issues.apache.org/jira/browse/TOMEE-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073900#comment-15073900 ] Jonathan Gallimore commented on TOMEE-1688: --- Agreed. Trying to find more information on the root cause. > Retry authentication if client identity is not logged in > > > Key: TOMEE-1688 > URL: https://issues.apache.org/jira/browse/TOMEE-1688 > Project: TomEE > Issue Type: Improvement >Affects Versions: 1.7.3 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore > Fix For: 1.7.4 > > Attachments: tomee-1688.patch > > > We are periodically seeing this exception: using 1.7.3: > javax.security.auth.login.LoginException: Identity is not currently logged > in: 4c201f33-5181-474b-b57a-854ee019bc26 > at > org.apache.openejb.core.security.AbstractSecurityService.associate(AbstractSecurityService.java:219) > at > org.apache.openejb.core.security.AbstractSecurityService.associate(AbstractSecurityService.java:61) > at > org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:287) > at com.sun.proxy.$Proxy70.create(Unknown Source) > at > org.apache.openejb.core.ivm.naming.BusinessRemoteReference.getObject(BusinessRemoteReference.java:36) > at org.apache.openejb.core.ivm.naming.IvmContext.lookup(IvmContext.java:175) > at > org.apache.openejb.server.ejbd.JndiRequestHandler.doLookup(JndiRequestHandler.java:261) > at > org.apache.openejb.server.ejbd.JndiRequestHandler.processResponse(JndiRequestHandler.java:174) > at > org.apache.openejb.server.ejbd.EjbDaemon.processJndiResponse(EjbDaemon.java:360) > at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:272) > at org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:86) > at > org.apache.openejb.server.httpd.ServerServlet.service(ServerServlet.java:58) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:731) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122) > at org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:44) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103) > at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:423) > at > org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1079) > at > org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:620) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1741) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1700) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at > org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TOMEE-1705) Destroy application attempts to initialize lazily loaded resources
Jonathan Gallimore created TOMEE-1705: - Summary: Destroy application attempts to initialize lazily loaded resources Key: TOMEE-1705 URL: https://issues.apache.org/jira/browse/TOMEE-1705 Project: TomEE Issue Type: Bug Components: TomEE Core Server Affects Versions: 1.7.3, 7.0.0-M1 Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Fix For: 7.0.0-M2, 1.7.4 If an application defines multiple resources, and one of the resources fails to start, the application is undeployed (as it should be), but when trying to undeploy the application, TomEE will lookup other resources to undeploy. The lookup will cause those resources to initialize and potentially throw confusing exceptions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TOMEE-1705) Destroy application attempts to initialize lazily loaded resources
[ https://issues.apache.org/jira/browse/TOMEE-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore resolved TOMEE-1705. --- Resolution: Fixed > Destroy application attempts to initialize lazily loaded resources > -- > > Key: TOMEE-1705 > URL: https://issues.apache.org/jira/browse/TOMEE-1705 > Project: TomEE > Issue Type: Bug > Components: TomEE Core Server >Affects Versions: 7.0.0-M1, 1.7.3 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore > Fix For: 7.0.0-M2, 1.7.4 > > > If an application defines multiple resources, and one of the resources fails > to start, the application is undeployed (as it should be), but when trying to > undeploy the application, TomEE will lookup other resources to undeploy. The > lookup will cause those resources to initialize and potentially throw > confusing exceptions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TOMEE-1771) Expose Deployer reload() function through JMX
Jonathan Gallimore created TOMEE-1771: - Summary: Expose Deployer reload() function through JMX Key: TOMEE-1771 URL: https://issues.apache.org/jira/browse/TOMEE-1771 Project: TomEE Issue Type: New Feature Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Priority: Minor Fix For: 7.0.0-M4, 1.7.5 The deployer exposes has reload() function. It would be useful to expose this through the JMXDeployer alongside deploy() and undeploy() which are already there. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TOMEE-1771) Expose Deployer reload() function through JMX
[ https://issues.apache.org/jira/browse/TOMEE-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231985#comment-15231985 ] Jonathan Gallimore commented on TOMEE-1771: --- Pushed in 6f40e6f8c49b1f98ea44eea2a2e16655d806d517 and 56ebcce396838b394911c2641d79baa494341304 > Expose Deployer reload() function through JMX > - > > Key: TOMEE-1771 > URL: https://issues.apache.org/jira/browse/TOMEE-1771 > Project: TomEE > Issue Type: New Feature >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore >Priority: Minor > Fix For: 7.0.0-M4, 1.7.5 > > > The deployer exposes has reload() function. It would be useful to expose this > through the JMXDeployer alongside deploy() and undeploy() which are already > there. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (TOMEE-1771) Expose Deployer reload() function through JMX
[ https://issues.apache.org/jira/browse/TOMEE-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore closed TOMEE-1771. - Resolution: Fixed > Expose Deployer reload() function through JMX > - > > Key: TOMEE-1771 > URL: https://issues.apache.org/jira/browse/TOMEE-1771 > Project: TomEE > Issue Type: New Feature >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore >Priority: Minor > Fix For: 7.0.0-M4, 1.7.5 > > > The deployer exposes has reload() function. It would be useful to expose this > through the JMXDeployer alongside deploy() and undeploy() which are already > there. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TOMEE-1790) Allow primitive arrays to be serialized/deserialized over (http)ejbd
Jonathan Gallimore created TOMEE-1790: - Summary: Allow primitive arrays to be serialized/deserialized over (http)ejbd Key: TOMEE-1790 URL: https://issues.apache.org/jira/browse/TOMEE-1790 Project: TomEE Issue Type: Improvement Components: TomEE Core Server Affects Versions: 7.0.0-M3, 1.7.4 Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Priority: Minor Fix For: 7.0.0-M4, 1.7.5 Currently if a serializable object uses a char[], unless "C[" is added to the whitelist, this exception is thrown when deserializing: java.lang.SecurityException: [C is not whitelisted as deserialisable, prevented before loading it. at org.apache.openejb.client.EjbObjectInputStream$BlacklistClassResolver.check(EjbObjectInputStream.java:122) at org.apache.openejb.client.EjbObjectInputStream.resolveClass(EjbObjectInputStream.java:43) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1612) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1517) at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1663) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1344) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1990) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1915) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1798) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) at org.apache.openejb.client.EJBRequest$Body.readExternal(EJBRequest.java:468) at org.apache.openejb.server.ejbd.EjbRequestHandler.processRequest(EjbRequestHandler.java:138) at org.apache.openejb.server.ejbd.EjbDaemon.processEjbRequest(EjbDaemon.java:344) at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:240) at org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:104) at org.apache.openejb.server.httpd.ServerServlet.service(ServerServlet.java:58) at javax.servlet.http.HttpServlet.service(HttpServlet.java:731) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122) at org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:44) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:956) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:436) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1078) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:625) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1757) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1716) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TOMEE-1789) Expose Pool flush() through JMX
Jonathan Gallimore created TOMEE-1789: - Summary: Expose Pool flush() through JMX Key: TOMEE-1789 URL: https://issues.apache.org/jira/browse/TOMEE-1789 Project: TomEE Issue Type: Improvement Components: TomEE Core Server Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Priority: Trivial Fix For: 7.0.0-M4, 1.7.5 Allow stateless pools to be flushed by exposing the flush() method via JMX -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TOMEE-1789) Expose Pool flush() through JMX
[ https://issues.apache.org/jira/browse/TOMEE-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore resolved TOMEE-1789. --- Resolution: Fixed > Expose Pool flush() through JMX > --- > > Key: TOMEE-1789 > URL: https://issues.apache.org/jira/browse/TOMEE-1789 > Project: TomEE > Issue Type: Improvement > Components: TomEE Core Server >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore >Priority: Trivial > Fix For: 7.0.0-M4, 1.7.5 > > > Allow stateless pools to be flushed by exposing the flush() method via JMX -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1643) XADataSource can leak connections/skip the pool
[ https://issues.apache.org/jira/browse/TOMEE-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore updated TOMEE-1643: -- Fix Version/s: 1.7.5 > XADataSource can leak connections/skip the pool > --- > > Key: TOMEE-1643 > URL: https://issues.apache.org/jira/browse/TOMEE-1643 > Project: TomEE > Issue Type: Improvement >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau > Fix For: 7.0.0-M2, 1.7.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TOMEE-2000) TomEE PLUME 7.0.2 stability problem when using HTTPS on both Redhat and CentOS
[ https://issues.apache.org/jira/browse/TOMEE-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15829880#comment-15829880 ] Jonathan Gallimore commented on TOMEE-2000: --- Hi Thanks for logging this ticket. In order to help solve the issue, we'll need a bit more information: * What sort of workloads is your server handling? Specifically, I'm curious about requests per second, and the types of request. * How do you have SSL configured - have you just imported your private key / certificate to a java keystore, or do you use the native connector? * Are you using BIO or NIO on your HTTPS connector (you could provide server.xml with any sensitive data removed) * Probably the most helpful thing would be to get a thread dump when your server is in this state. To do that, you can run jstack passing the PID of TomEE in as a parameter. If you're able to get that and send it to the mailing list or attach it to this ticket, that would be really helpful. Regards Jon > TomEE PLUME 7.0.2 stability problem when using HTTPS on both Redhat and CentOS > -- > > Key: TOMEE-2000 > URL: https://issues.apache.org/jira/browse/TOMEE-2000 > Project: TomEE > Issue Type: Bug > Components: TomEE Core Server >Affects Versions: 7.0.2 > Environment: Red Hat Enterprise Linux Server release 7.2 (Maipo) > CentOS Linux release 7.2.1511 (Core) > Java(TM) SE Runtime Environment (build 1.8.0_101-b13) (64-bit server) >Reporter: Keerati > > There seems to be a bug on HTTPS feature. We've setup SSL on two different > machine (Redhat and CentOS) using two different SSL certificates, and the > exact same problem happen. > At first, TomEE runs normally, but after a few days (we are not exactly sure > how long), TomEE starts to have stability problem. In our case, TomEE starts > to have abnormal CPU consumption (~20% on all CPU cores) even when there is > no connection. Furthermore, when the server start to have HTTPS workloads, > TomEE did crash. So, we decided to disable SSL from our TomEE server, and > everything come back to normal. > Sorry that we did not record all the problems appropriately (the time we test > SSL on the 1st and 2nd server is about 2 months), but now that we found the > same problem happen on the 2nd server. We are quite sure that TomEE has > stability problem with SSL. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TOMEE-1917) Provide means to bypass CountingInputStream/OutputStream
Jonathan Gallimore created TOMEE-1917: - Summary: Provide means to bypass CountingInputStream/OutputStream Key: TOMEE-1917 URL: https://issues.apache.org/jira/browse/TOMEE-1917 Project: TomEE Issue Type: New Feature Affects Versions: 7.0.1, 1.7.4 Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Priority: Minor Fix For: 1.7.5, 7.0.2 Whilst useful, this introduces a small overhead on the stream, and therefore it may be desirable to skip this information using a system property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TOMEE-1995) Backport TomEE 7 change for ciphering any resource property to TomEE 1.7.x
[ https://issues.apache.org/jira/browse/TOMEE-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore resolved TOMEE-1995. --- Resolution: Fixed > Backport TomEE 7 change for ciphering any resource property to TomEE 1.7.x > -- > > Key: TOMEE-1995 > URL: https://issues.apache.org/jira/browse/TOMEE-1995 > Project: TomEE > Issue Type: Improvement >Affects Versions: 1.7.4 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore >Priority: Minor > Fix For: 1.7.5 > > > TomEE 7 provides the ability to cipher any property on a resource. TomEE > 1.7.x also intends to provide this, but a bug in the implementation means > that it does not work correctly. This functionality can be backported from > TomEE 7. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TOMEE-1995) Backport TomEE 7 change for ciphering any resource property to TomEE 1.7.x
Jonathan Gallimore created TOMEE-1995: - Summary: Backport TomEE 7 change for ciphering any resource property to TomEE 1.7.x Key: TOMEE-1995 URL: https://issues.apache.org/jira/browse/TOMEE-1995 Project: TomEE Issue Type: Improvement Affects Versions: 1.7.4 Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Priority: Minor Fix For: 1.7.5 TomEE 7 provides the ability to cipher any property on a resource. TomEE 1.7.x also intends to provide this, but a bug in the implementation means that it does not work correctly. This functionality can be backported from TomEE 7. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-2021) support to control a MDB listening through JMX
[ https://issues.apache.org/jira/browse/TOMEE-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore updated TOMEE-2021: -- Fix Version/s: 1.7.5 > support to control a MDB listening through JMX > -- > > Key: TOMEE-2021 > URL: https://issues.apache.org/jira/browse/TOMEE-2021 > Project: TomEE > Issue Type: New Feature >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau > Fix For: 1.7.5, 7.0.4 > > > Idea is to add in openejb-jar.xml to properties support: > - MdbActiveOnStartup = [true|false] > - MdbJMXControl = [true|false|objectname] > the first one will deploy the MDB but not activate the listener yet during > startup, > the second one will deploy on JMX a MBean either with a name like > default:J2EEServer=openejb,J2EEApplication=,EJBModule=app,StatelessSessionBean=ejb/Mdb,j2eeType=control,name=ejb/Mdb > or with the provided name allowing to start/stop the listening of the MDB. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (TOMEE-2118) @RunAs does not work properly when it is used in servlet
[
https://issues.apache.org/jira/browse/TOMEE-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Gallimore reassigned TOMEE-2118:
-
Assignee: Jonathan Gallimore
> @RunAs does not work properly when it is used in servlet
>
>
> Key: TOMEE-2118
> URL: https://issues.apache.org/jira/browse/TOMEE-2118
> Project: TomEE
> Issue Type: Bug
>Affects Versions: 7.0.3
>Reporter: Kaloyan Spiridonov
>Assignee: Jonathan Gallimore
>
> I have the following scenario:
> Servlet -> EjbOne -> EjbTwo
> My expectation is that @RunAs of the servlet will be propagated to EjbOne
> and the @RunAs of the EjbOne will be propagated to @EjbTwo.
> But this does not happen - see the output below. When i remove @RunAs
> annotation from the servlet the @RunAs of EjbOne is propagated correctly.
> Actual output:
> EjbOne (Before EjbTwo) expected role: Manager, isCallerInRole("Manager"):
> false
> EjbOne (Before EjbTwo) expected role: Manager, isCallerInRole("VP"): false
> EjbOne (Before EjbTwo) expected role: Manager,)
> isCallerInRole("Administrator"): false
> EjbTwo expected role: VP, isCallerInRole("Manager"): false
> EjbTwo expected role: VP, isCallerInRole("VP"): false
> EjbTwo expected role: VP, isCallerInRole("Administrator"): false
> EjbOne (After EjbTwo) expected role: Manager, isCallerInRole("Manager"):
> false
> EjbOne (After EjbTwo) expected role: Manager, isCallerInRole("VP"): false
> EjbOne (After EjbTwo) expected role: Manager,
> isCallerInRole("Administrator"): false
> Expected output:
> EjbOne (Before EjbTwo) expected role: Manager, isCallerInRole("Manager"):
> true
> EjbOne (Before EjbTwo) expected role: Manager, isCallerInRole("VP"): false
> EjbOne (Before EjbTwo) expected role: Manager,)
> isCallerInRole("Administrator"): false
> EjbTwo expected role: VP, isCallerInRole("Manager"): false
> EjbTwo expected role: VP, isCallerInRole("VP"): true
> EjbTwo expected role: VP, isCallerInRole("Administrator"): false
> EjbOne (After EjbTwo) expected role: Manager, isCallerInRole("Manager"):
> true
> EjbOne (After EjbTwo) expected role: Manager, isCallerInRole("VP"): false
> EjbOne (After EjbTwo) expected role: Manager,
> isCallerInRole("Administrator"): false
> Here is the source of the application: https://github.com/kal0ian/Examples
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (TOMEE-2093) Correct misspelt FailOnUnknownActivationSpec property
[ https://issues.apache.org/jira/browse/TOMEE-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16080549#comment-16080549 ] Jonathan Gallimore commented on TOMEE-2093: --- Looks good, running the tests and will then merge. This has already been discussed on dev@: http://tomee-openejb.979440.n4.nabble.com/Adds-an-option-to-ignore-mdb-activation-fields-td4682126.html > Correct misspelt FailOnUnknownActivationSpec property > - > > Key: TOMEE-2093 > URL: https://issues.apache.org/jira/browse/TOMEE-2093 > Project: TomEE > Issue Type: Improvement >Affects Versions: 7.0.3 >Reporter: Otavio Goncalves de Santana >Assignee: Jonathan Gallimore > Fix For: 7.0.4 > > > This property has been incorrectly spelled as 'FailOnUnknowActivationSpec' on > master. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (TOMEE-2093) Correct misspelt FailOnUnknownActivationSpec property
[ https://issues.apache.org/jira/browse/TOMEE-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore resolved TOMEE-2093. --- Resolution: Fixed > Correct misspelt FailOnUnknownActivationSpec property > - > > Key: TOMEE-2093 > URL: https://issues.apache.org/jira/browse/TOMEE-2093 > Project: TomEE > Issue Type: Improvement >Affects Versions: 7.0.3 >Reporter: Otavio Goncalves de Santana >Assignee: Jonathan Gallimore > Fix For: 7.0.4 > > > This property has been incorrectly spelled as 'FailOnUnknowActivationSpec' on > master. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (TOMEE-2092) Adds an option to ignore mdb.activation unknown properties
[ https://issues.apache.org/jira/browse/TOMEE-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-2092 started by Jonathan Gallimore. - > Adds an option to ignore mdb.activation unknown properties > -- > > Key: TOMEE-2092 > URL: https://issues.apache.org/jira/browse/TOMEE-2092 > Project: TomEE > Issue Type: Improvement >Affects Versions: 1.7.4 >Reporter: Otavio Goncalves de Santana >Assignee: Jonathan Gallimore > Fix For: 1.7.5 > > > Please backport > https://github.com/apache/tomee/commit/6522f349d0c31d6ec82e66378e0e55eded08aec0 > to tomee-1.7.x. > Patch is available here: > https://patch-diff.githubusercontent.com/raw/apache/tomee/pull/86.diff -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (TOMEE-2093) Correct misspelt FailOnUnknownActivationSpec property
[ https://issues.apache.org/jira/browse/TOMEE-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-2093 started by Jonathan Gallimore. - > Correct misspelt FailOnUnknownActivationSpec property > - > > Key: TOMEE-2093 > URL: https://issues.apache.org/jira/browse/TOMEE-2093 > Project: TomEE > Issue Type: Improvement >Affects Versions: 7.0.3 >Reporter: Otavio Goncalves de Santana >Assignee: Jonathan Gallimore > Fix For: 7.0.4 > > > This property has been incorrectly spelled as 'FailOnUnknowActivationSpec' on > master. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (TOMEE-2093) Correct misspelt FailOnUnknownActivationSpec property
[ https://issues.apache.org/jira/browse/TOMEE-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-2093 started by Jonathan Gallimore. - > Correct misspelt FailOnUnknownActivationSpec property > - > > Key: TOMEE-2093 > URL: https://issues.apache.org/jira/browse/TOMEE-2093 > Project: TomEE > Issue Type: Improvement >Affects Versions: 7.0.3 >Reporter: Otavio Goncalves de Santana >Assignee: Jonathan Gallimore > Fix For: 7.0.4 > > > This property has been incorrectly spelled as 'FailOnUnknowActivationSpec' on > master. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOMEE-2093) Correct misspelt FailOnUnknownActivationSpec property
[ https://issues.apache.org/jira/browse/TOMEE-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16080953#comment-16080953 ] Jonathan Gallimore commented on TOMEE-2093: --- Committed: https://git-wip-us.apache.org/repos/asf?p=tomee.git;a=commit;h=fcf068e1356253b916e6011990cfdeb01616d882 > Correct misspelt FailOnUnknownActivationSpec property > - > > Key: TOMEE-2093 > URL: https://issues.apache.org/jira/browse/TOMEE-2093 > Project: TomEE > Issue Type: Improvement >Affects Versions: 7.0.3 >Reporter: Otavio Goncalves de Santana >Assignee: Jonathan Gallimore > Fix For: 7.0.4 > > > This property has been incorrectly spelled as 'FailOnUnknowActivationSpec' on > master. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-2091) NetworkUtilTest
[ https://issues.apache.org/jira/browse/TOMEE-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore updated TOMEE-2091: -- Issue Type: Bug (was: Improvement) > NetworkUtilTest > --- > > Key: TOMEE-2091 > URL: https://issues.apache.org/jira/browse/TOMEE-2091 > Project: TomEE > Issue Type: Bug > Components: TomEE Build >Affects Versions: 1.7.4, 7.0.3 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore > Fix For: 1.7.5, 7.0.4 > > > This test seems to fail occasionally: > Running org.apache.openejb.util.NetworkUtilTest > Exception in thread "test-thread-20" java.lang.AssertionError: Got a > duplicate port with ten seconds > at org.junit.Assert.fail(Assert.java:88) > at > org.apache.openejb.util.NetworkUtilTest$1.run(NetworkUtilTest.java:68) > at java.lang.Thread.run(Thread.java:745) > Machine safe port list = [1025, 1026, 1027, 1028, 1029, 1030, 1031, 1032, > 1033, 1034, 1035, 1036, 1037, 1038, 1039, 1040, 1041, 1042, 1043, 1044] > Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 15.305 sec > <<< FAILURE! - in org.apache.openejb.util.NetworkUtilTest > testNext(org.apache.openejb.util.NetworkUtilTest) Time elapsed: 15.019 sec > <<< FAILURE! > java.lang.AssertionError > at > org.apache.openejb.util.NetworkUtilTest.testNext(NetworkUtilTest.java:82) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (TOMEE-2092) Adds an option to ignore mdb.activation unknown properties
[ https://issues.apache.org/jira/browse/TOMEE-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore resolved TOMEE-2092. --- Resolution: Fixed Committed: https://git-wip-us.apache.org/repos/asf?p=tomee.git;a=commit;h=71a6b4732dd0dc47d349d5e07d2602d7aeb1148b > Adds an option to ignore mdb.activation unknown properties > -- > > Key: TOMEE-2092 > URL: https://issues.apache.org/jira/browse/TOMEE-2092 > Project: TomEE > Issue Type: Improvement >Affects Versions: 1.7.4 >Reporter: Otavio Goncalves de Santana >Assignee: Jonathan Gallimore > Fix For: 1.7.5 > > > Please backport > https://github.com/apache/tomee/commit/6522f349d0c31d6ec82e66378e0e55eded08aec0 > to tomee-1.7.x. > Patch is available here: > https://patch-diff.githubusercontent.com/raw/apache/tomee/pull/86.diff -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOMEE-2093) Correct misspelt FailOnUnknownActivationSpec property
[ https://issues.apache.org/jira/browse/TOMEE-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16080547#comment-16080547 ] Jonathan Gallimore commented on TOMEE-2093: --- Patch is here: https://github.com/apache/tomee/pull/87 > Correct misspelt FailOnUnknownActivationSpec property > - > > Key: TOMEE-2093 > URL: https://issues.apache.org/jira/browse/TOMEE-2093 > Project: TomEE > Issue Type: Improvement >Affects Versions: 7.0.3 >Reporter: Otavio Goncalves de Santana >Assignee: Jonathan Gallimore > Fix For: 7.0.4 > > > This property has been incorrectly spelled as 'FailOnUnknowActivationSpec' on > master. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TOMEE-2092) Adds an option to ignore mdb.activation unknown properties
Jonathan Gallimore created TOMEE-2092: - Summary: Adds an option to ignore mdb.activation unknown properties Key: TOMEE-2092 URL: https://issues.apache.org/jira/browse/TOMEE-2092 Project: TomEE Issue Type: Improvement Affects Versions: 1.7.4 Reporter: Otavio Goncalves de Santana Assignee: Jonathan Gallimore Fix For: 1.7.5 Please backport https://github.com/apache/tomee/commit/6522f349d0c31d6ec82e66378e0e55eded08aec0 to tomee-1.7.x. Patch is available here: https://patch-diff.githubusercontent.com/raw/apache/tomee/pull/86.diff -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TOMEE-2093) Correct misspelt FailOnUnknownActivationSpec property
Jonathan Gallimore created TOMEE-2093: - Summary: Correct misspelt FailOnUnknownActivationSpec property Key: TOMEE-2093 URL: https://issues.apache.org/jira/browse/TOMEE-2093 Project: TomEE Issue Type: Improvement Affects Versions: 7.0.3 Reporter: Otavio Goncalves de Santana Assignee: Jonathan Gallimore Fix For: 7.0.4 This property has been incorrectly spelled as 'FailOnUnknowActivationSpec' on master. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TOMEE-2091) NetworkUtilTest
Jonathan Gallimore created TOMEE-2091: - Summary: NetworkUtilTest Key: TOMEE-2091 URL: https://issues.apache.org/jira/browse/TOMEE-2091 Project: TomEE Issue Type: Improvement Components: TomEE Build Affects Versions: 7.0.3, 1.7.4 Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Fix For: 1.7.5, 7.0.4 This test seems to fail occasionally: Running org.apache.openejb.util.NetworkUtilTest Exception in thread "test-thread-20" java.lang.AssertionError: Got a duplicate port with ten seconds at org.junit.Assert.fail(Assert.java:88) at org.apache.openejb.util.NetworkUtilTest$1.run(NetworkUtilTest.java:68) at java.lang.Thread.run(Thread.java:745) Machine safe port list = [1025, 1026, 1027, 1028, 1029, 1030, 1031, 1032, 1033, 1034, 1035, 1036, 1037, 1038, 1039, 1040, 1041, 1042, 1043, 1044] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 15.305 sec <<< FAILURE! - in org.apache.openejb.util.NetworkUtilTest testNext(org.apache.openejb.util.NetworkUtilTest) Time elapsed: 15.019 sec <<< FAILURE! java.lang.AssertionError at org.apache.openejb.util.NetworkUtilTest.testNext(NetworkUtilTest.java:82) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-2090) Randomly broken Test in CDI TCK MessageDrivenBeanInterceptorInvocationTest
[
https://issues.apache.org/jira/browse/TOMEE-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Gallimore updated TOMEE-2090:
--
Component/s: TomEE Build
> Randomly broken Test in CDI TCK MessageDrivenBeanInterceptorInvocationTest
> --
>
> Key: TOMEE-2090
> URL: https://issues.apache.org/jira/browse/TOMEE-2090
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Build
> Environment: Linux, FC25, Java8
>Reporter: Mark Struberg
>
> {noformat}
> [INFO] OpenEJB :: TCK :: Common ... SUCCESS [ 0.751
> s]
> [INFO] OpenEJB :: TCK :: CDI Embedded . FAILURE [04:12
> min]
> {noformat}
> {noformat}
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> INFORMATION - Invoke DecoratorTypeParamInitializerTest.testDeploymentFails:
> 1.479/1.479 Failed tests: 1 (644)
> INFORMATION - Stopping network services
> INFORMATION - Stopping server services
> INFORMATION - Destroying container system
> INFORMATION - Scheduler OpenEJB-TimerService-Scheduler_$_OpenEJB shutting
> down.
> INFORMATION - Scheduler OpenEJB-TimerService-Scheduler_$_OpenEJB paused.
> INFORMATION - Scheduler unregistered from name
> 'quartz:type=QuartzScheduler,name=OpenEJB-TimerService-Scheduler,instance=OpenEJB'
> in the local MBeanServer.
> INFORMATION - Scheduler OpenEJB-TimerService-Scheduler_$_OpenEJB shutdown
> complete.
> INFORMATION - Closing DataSource: jdbc
> INFORMATION - Closing DataSource: jdbcNonJta
> INFORMATION - Stopping ResourceAdapter: Default JMS Resource Adapter
> INFORMATION - Stopping ActiveMQ
> INFORMATION - Apache ActiveMQ 5.14.3 (localhost,
> ID:stehtnix-43855-1499679488155-0:1) is shutting down
> INFORMATION - Connector tcp://localhost.localdomain:35107 stopped
> INFORMATION - Connector vm://localhost stopped
> INFORMATION - Apache ActiveMQ 5.14.3 (localhost,
> ID:stehtnix-43855-1499679488155-0:1) uptime 4 minutes
> INFORMATION - Apache ActiveMQ 5.14.3 (localhost,
> ID:stehtnix-43855-1499679488155-0:1) is shutdown
> INFORMATION - Stopped ActiveMQ broker
> Tests run: 1479, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 250.712
> sec <<< FAILURE! - in TestSuite
> testMessageDrivenBeanMethodIntercepted(org.jboss.cdi.tck.tests.interceptors.definition.enterprise.jms.MessageDrivenBeanInterceptorInvocationTest)
> Time elapsed: 5.026 sec <<< FAILURE!
> java.lang.AssertionError: expected [true] but found [false]
> at org.testng.Assert.fail(Assert.java:94)
> at org.testng.Assert.failNotEquals(Assert.java:494)
> at org.testng.Assert.assertTrue(Assert.java:42)
> at org.testng.Assert.assertTrue(Assert.java:52)
> at
> org.jboss.cdi.tck.tests.interceptors.definition.enterprise.jms.MessageDrivenBeanInterceptorInvocationTest.testMessageDrivenBeanMethodIntercepted(MessageDrivenBeanInterceptorInvocationTest.java:92)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (TOMEE-2099) JAX-RS Application#getProperties is never called
[
https://issues.apache.org/jira/browse/TOMEE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Gallimore reassigned TOMEE-2099:
-
Assignee: Jonathan Gallimore
> JAX-RS Application#getProperties is never called
>
>
> Key: TOMEE-2099
> URL: https://issues.apache.org/jira/browse/TOMEE-2099
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 7.0.3
> Environment: $ mvn -version
> Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4;
> 2014-08-11T22:58:10+02:00)
> Maven home: D:\tools\apache-maven-3.2.3
> Java version: 1.8.0_111, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_111\jre
> Default locale: fr_FR, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
> Running TomEE Plus through the tomee maven plugin
>Reporter: TURPIN Michel
>Assignee: Jonathan Gallimore
> Labels: features
>
> The {{Application#getProperties()}} method is never called / used.
> As a consequence, it is impossible to configure a Feature or DynamicFeature
> that would read properties from the context configuration from an Application
> subclass.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (TOMEE-2099) JAX-RS Application#getProperties is never called
[
https://issues.apache.org/jira/browse/TOMEE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16092940#comment-16092940
]
Jonathan Gallimore commented on TOMEE-2099:
---
Hi Michel
I'd be happy to take a look at that for you - do you by any chance have a quick
code sample that you can share with us?
Thanks
Jon
> JAX-RS Application#getProperties is never called
>
>
> Key: TOMEE-2099
> URL: https://issues.apache.org/jira/browse/TOMEE-2099
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 7.0.3
> Environment: $ mvn -version
> Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4;
> 2014-08-11T22:58:10+02:00)
> Maven home: D:\tools\apache-maven-3.2.3
> Java version: 1.8.0_111, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_111\jre
> Default locale: fr_FR, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
> Running TomEE Plus through the tomee maven plugin
>Reporter: TURPIN Michel
> Labels: features
>
> The {{Application#getProperties()}} method is never called / used.
> As a consequence, it is impossible to configure a Feature or DynamicFeature
> that would read properties from the context configuration from an Application
> subclass.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (TOMEE-2082) Use a ASM based proxy in AutoConnectionTracker
Jonathan Gallimore created TOMEE-2082: - Summary: Use a ASM based proxy in AutoConnectionTracker Key: TOMEE-2082 URL: https://issues.apache.org/jira/browse/TOMEE-2082 Project: TomEE Issue Type: Improvement Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore This class wraps a ManagedConnection from a resource adapter in a proxy to enable an interceptor. This prevents resource adapters from executing methods implemented on the implementation class itself, and further prevents the use of package-local methods on that class as well. This resource adapter: https://github.com/jms-ra/generic-jms-ra, which is popular for connecting to JMS systems that are based on using remoting, and looking up objects in a remote JNDI, such as JBossMQ and Tibco, does this here: https://github.com/jgallimore/generic-jms-ra/blob/1.x/generic-jms-ra-jar/src/main/java/org/jboss/resource/adapter/jms/JmsSessionFactoryImpl.java#L368-L368. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (TOMEE-2081) Move the Mdb control logic from ActiveMQ to the MdbContainer
[ https://issues.apache.org/jira/browse/TOMEE-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore resolved TOMEE-2081. --- Resolution: Fixed > Move the Mdb control logic from ActiveMQ to the MdbContainer > > > Key: TOMEE-2081 > URL: https://issues.apache.org/jira/browse/TOMEE-2081 > Project: TomEE > Issue Type: Improvement >Affects Versions: 1.7.4, 7.0.3 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore > Fix For: 1.7.5, 7.0.4 > > > Building upon the great work in TOMEE-2021, move this logic to the > MdbContainer, so it is not specific to ActiveMQ and works with other JMS > providers and connectors. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (TOMEE-2082) Use a ASM based proxy in AutoConnectionTracker
[ https://issues.apache.org/jira/browse/TOMEE-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore resolved TOMEE-2082. --- Resolution: Fixed Fix Version/s: 1.7.5 > Use a ASM based proxy in AutoConnectionTracker > -- > > Key: TOMEE-2082 > URL: https://issues.apache.org/jira/browse/TOMEE-2082 > Project: TomEE > Issue Type: Improvement >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore > Fix For: 1.7.5 > > > This class wraps a ManagedConnection from a resource adapter in a proxy to > enable an interceptor. This prevents resource adapters from executing methods > implemented on the implementation class itself, and further prevents the use > of package-local methods on that class as well. > This resource adapter: https://github.com/jms-ra/generic-jms-ra, which is > popular for connecting to JMS systems that are based on using remoting, and > looking up objects in a remote JNDI, such as JBossMQ and Tibco, does this > here: > https://github.com/jgallimore/generic-jms-ra/blob/1.x/generic-jms-ra-jar/src/main/java/org/jboss/resource/adapter/jms/JmsSessionFactoryImpl.java#L368-L368. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (TOMEE-1688) Retry authentication if client identity is not logged in
[ https://issues.apache.org/jira/browse/TOMEE-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore closed TOMEE-1688. - Resolution: Not A Problem Fix Version/s: (was: 7.0.4) > Retry authentication if client identity is not logged in > > > Key: TOMEE-1688 > URL: https://issues.apache.org/jira/browse/TOMEE-1688 > Project: TomEE > Issue Type: Improvement >Affects Versions: 1.7.3 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore > Attachments: tomee-1688.patch > > > We are periodically seeing this exception: using 1.7.3: > javax.security.auth.login.LoginException: Identity is not currently logged > in: 4c201f33-5181-474b-b57a-854ee019bc26 > at > org.apache.openejb.core.security.AbstractSecurityService.associate(AbstractSecurityService.java:219) > at > org.apache.openejb.core.security.AbstractSecurityService.associate(AbstractSecurityService.java:61) > at > org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:287) > at com.sun.proxy.$Proxy70.create(Unknown Source) > at > org.apache.openejb.core.ivm.naming.BusinessRemoteReference.getObject(BusinessRemoteReference.java:36) > at org.apache.openejb.core.ivm.naming.IvmContext.lookup(IvmContext.java:175) > at > org.apache.openejb.server.ejbd.JndiRequestHandler.doLookup(JndiRequestHandler.java:261) > at > org.apache.openejb.server.ejbd.JndiRequestHandler.processResponse(JndiRequestHandler.java:174) > at > org.apache.openejb.server.ejbd.EjbDaemon.processJndiResponse(EjbDaemon.java:360) > at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:272) > at org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:86) > at > org.apache.openejb.server.httpd.ServerServlet.service(ServerServlet.java:58) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:731) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122) > at org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:44) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103) > at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:423) > at > org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1079) > at > org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:620) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1741) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1700) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at > org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (TOMEE-2081) Move the Mdb control logic from ActiveMQ to the MdbContainer
[ https://issues.apache.org/jira/browse/TOMEE-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-2081 started by Jonathan Gallimore. - > Move the Mdb control logic from ActiveMQ to the MdbContainer > > > Key: TOMEE-2081 > URL: https://issues.apache.org/jira/browse/TOMEE-2081 > Project: TomEE > Issue Type: Improvement >Affects Versions: 1.7.4, 7.0.3 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore > Fix For: 1.7.5, 7.0.4 > > > Building upon the great work in TOMEE-2021, move this logic to the > MdbContainer, so it is not specific to ActiveMQ and works with other JMS > providers and connectors. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TOMEE-2081) Move the Mdb control logic from ActiveMQ to the MdbContainer
Jonathan Gallimore created TOMEE-2081: - Summary: Move the Mdb control logic from ActiveMQ to the MdbContainer Key: TOMEE-2081 URL: https://issues.apache.org/jira/browse/TOMEE-2081 Project: TomEE Issue Type: Improvement Affects Versions: 7.0.3, 1.7.4 Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Fix For: 1.7.5, 7.0.4 Building upon the great work in TOMEE-2021, move this logic to the MdbContainer, so it is not specific to ActiveMQ and works with other JMS providers and connectors. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TOMEE-2111) Update CXF to 2.6.17
Jonathan Gallimore created TOMEE-2111: - Summary: Update CXF to 2.6.17 Key: TOMEE-2111 URL: https://issues.apache.org/jira/browse/TOMEE-2111 Project: TomEE Issue Type: Dependency upgrade Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Priority: Minor Fix For: 1.7.5 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (TOMEE-2111) Update CXF to 2.6.17
[ https://issues.apache.org/jira/browse/TOMEE-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore resolved TOMEE-2111. --- Resolution: Fixed > Update CXF to 2.6.17 > > > Key: TOMEE-2111 > URL: https://issues.apache.org/jira/browse/TOMEE-2111 > Project: TomEE > Issue Type: Dependency upgrade >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore >Priority: Minor > Fix For: 1.7.5 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TOMEE-2112) Update Taglibs, WSS4J, Jansi and OpenSAML
Jonathan Gallimore created TOMEE-2112: - Summary: Update Taglibs, WSS4J, Jansi and OpenSAML Key: TOMEE-2112 URL: https://issues.apache.org/jira/browse/TOMEE-2112 Project: TomEE Issue Type: Dependency upgrade Affects Versions: 1.7.4 Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Priority: Minor Fix For: 1.7.5 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (TOMEE-2105) Upgrade Eclipselink
[ https://issues.apache.org/jira/browse/TOMEE-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore resolved TOMEE-2105. --- Resolution: Fixed > Upgrade Eclipselink > --- > > Key: TOMEE-2105 > URL: https://issues.apache.org/jira/browse/TOMEE-2105 > Project: TomEE > Issue Type: Dependency upgrade > Components: TomEE Core Server >Affects Versions: 7.0.4 >Reporter: Daniel Cunha >Assignee: Jonathan Gallimore > Fix For: 7.0.4 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOMEE-2105) Upgrade Eclipselink
[ https://issues.apache.org/jira/browse/TOMEE-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16112669#comment-16112669 ] Jonathan Gallimore commented on TOMEE-2105: --- Merged - thank you for the patch! > Upgrade Eclipselink > --- > > Key: TOMEE-2105 > URL: https://issues.apache.org/jira/browse/TOMEE-2105 > Project: TomEE > Issue Type: Dependency upgrade > Components: TomEE Core Server >Affects Versions: 7.0.4 >Reporter: Daniel Cunha >Assignee: Jonathan Gallimore > Fix For: 7.0.4 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (TOMEE-2072) Update to Tomcat 7.0.78
[ https://issues.apache.org/jira/browse/TOMEE-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore resolved TOMEE-2072. --- Resolution: Fixed > Update to Tomcat 7.0.78 > --- > > Key: TOMEE-2072 > URL: https://issues.apache.org/jira/browse/TOMEE-2072 > Project: TomEE > Issue Type: Dependency upgrade >Affects Versions: 1.7.4 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore > Fix For: 1.7.5 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TOMEE-2072) Update to Tomcat 7.0.78
Jonathan Gallimore created TOMEE-2072: - Summary: Update to Tomcat 7.0.78 Key: TOMEE-2072 URL: https://issues.apache.org/jira/browse/TOMEE-2072 Project: TomEE Issue Type: Dependency upgrade Affects Versions: 1.7.4 Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Fix For: 1.7.5 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (TOMEE-2072) Update to Tomcat 7.0.78
[ https://issues.apache.org/jira/browse/TOMEE-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore closed TOMEE-2072. - > Update to Tomcat 7.0.78 > --- > > Key: TOMEE-2072 > URL: https://issues.apache.org/jira/browse/TOMEE-2072 > Project: TomEE > Issue Type: Dependency upgrade >Affects Versions: 1.7.4 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore > Fix For: 1.7.5 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work stopped] (TOMEE-2132) Upgrade to Tomcat 7.0.82
[ https://issues.apache.org/jira/browse/TOMEE-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-2132 stopped by Jonathan Gallimore. - > Upgrade to Tomcat 7.0.82 > > > Key: TOMEE-2132 > URL: https://issues.apache.org/jira/browse/TOMEE-2132 > Project: TomEE > Issue Type: Dependency upgrade >Affects Versions: 1.7.4 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore > Fix For: 1.7.5 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TOMEE-2132) Upgrade to Tomcat 7.0.82
Jonathan Gallimore created TOMEE-2132: - Summary: Upgrade to Tomcat 7.0.82 Key: TOMEE-2132 URL: https://issues.apache.org/jira/browse/TOMEE-2132 Project: TomEE Issue Type: Dependency upgrade Affects Versions: 1.7.4 Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Fix For: 1.7.5 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (TOMEE-2132) Upgrade to Tomcat 7.0.82
[ https://issues.apache.org/jira/browse/TOMEE-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-2132 started by Jonathan Gallimore. - > Upgrade to Tomcat 7.0.82 > > > Key: TOMEE-2132 > URL: https://issues.apache.org/jira/browse/TOMEE-2132 > Project: TomEE > Issue Type: Dependency upgrade >Affects Versions: 1.7.4 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore > Fix For: 1.7.5 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOMEE-2118) @RunAs does not work properly when it is used in servlet
[
https://issues.apache.org/jira/browse/TOMEE-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16164568#comment-16164568
]
Jonathan Gallimore commented on TOMEE-2118:
---
Thanks for checking in. I did successfully reproduce and was getting close to a
fix. I'll pick it back up later today.
> @RunAs does not work properly when it is used in servlet
>
>
> Key: TOMEE-2118
> URL: https://issues.apache.org/jira/browse/TOMEE-2118
> Project: TomEE
> Issue Type: Bug
>Affects Versions: 7.0.3
>Reporter: Kaloyan Spiridonov
>Assignee: Jonathan Gallimore
>
> I have the following scenario:
> Servlet -> EjbOne -> EjbTwo
> My expectation is that @RunAs of the servlet will be propagated to EjbOne
> and the @RunAs of the EjbOne will be propagated to @EjbTwo.
> But this does not happen - see the output below. When i remove @RunAs
> annotation from the servlet the @RunAs of EjbOne is propagated correctly.
> Actual output:
> EjbOne (Before EjbTwo) expected role: Manager, isCallerInRole("Manager"):
> false
> EjbOne (Before EjbTwo) expected role: Manager, isCallerInRole("VP"): false
> EjbOne (Before EjbTwo) expected role: Manager,)
> isCallerInRole("Administrator"): false
> EjbTwo expected role: VP, isCallerInRole("Manager"): false
> EjbTwo expected role: VP, isCallerInRole("VP"): false
> EjbTwo expected role: VP, isCallerInRole("Administrator"): false
> EjbOne (After EjbTwo) expected role: Manager, isCallerInRole("Manager"):
> false
> EjbOne (After EjbTwo) expected role: Manager, isCallerInRole("VP"): false
> EjbOne (After EjbTwo) expected role: Manager,
> isCallerInRole("Administrator"): false
> Expected output:
> EjbOne (Before EjbTwo) expected role: Manager, isCallerInRole("Manager"):
> true
> EjbOne (Before EjbTwo) expected role: Manager, isCallerInRole("VP"): false
> EjbOne (Before EjbTwo) expected role: Manager,)
> isCallerInRole("Administrator"): false
> EjbTwo expected role: VP, isCallerInRole("Manager"): false
> EjbTwo expected role: VP, isCallerInRole("VP"): true
> EjbTwo expected role: VP, isCallerInRole("Administrator"): false
> EjbOne (After EjbTwo) expected role: Manager, isCallerInRole("Manager"):
> true
> EjbOne (After EjbTwo) expected role: Manager, isCallerInRole("VP"): false
> EjbOne (After EjbTwo) expected role: Manager,
> isCallerInRole("Administrator"): false
> Here is the source of the application: https://github.com/kal0ian/Examples
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (TOMEE-2124) Update to Tomcat 7.0.81
[ https://issues.apache.org/jira/browse/TOMEE-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore resolved TOMEE-2124. --- Resolution: Fixed > Update to Tomcat 7.0.81 > --- > > Key: TOMEE-2124 > URL: https://issues.apache.org/jira/browse/TOMEE-2124 > Project: TomEE > Issue Type: Dependency upgrade >Affects Versions: 1.7.4 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore > Fix For: 1.7.5 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TOMEE-2124) Update to Tomcat 7.0.81
Jonathan Gallimore created TOMEE-2124: - Summary: Update to Tomcat 7.0.81 Key: TOMEE-2124 URL: https://issues.apache.org/jira/browse/TOMEE-2124 Project: TomEE Issue Type: Dependency upgrade Affects Versions: 1.7.4 Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Fix For: 1.7.5 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (TOMEE-2124) Update to Tomcat 7.0.81
[ https://issues.apache.org/jira/browse/TOMEE-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-2124 started by Jonathan Gallimore. - > Update to Tomcat 7.0.81 > --- > > Key: TOMEE-2124 > URL: https://issues.apache.org/jira/browse/TOMEE-2124 > Project: TomEE > Issue Type: Dependency upgrade >Affects Versions: 1.7.4 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore > Fix For: 1.7.5 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TOMEE-2133) Update to Tomcat 8.5.23
Jonathan Gallimore created TOMEE-2133: - Summary: Update to Tomcat 8.5.23 Key: TOMEE-2133 URL: https://issues.apache.org/jira/browse/TOMEE-2133 Project: TomEE Issue Type: Dependency upgrade Affects Versions: 7.0.4 Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Fix For: 7.0.5 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (TOMEE-2133) Update to Tomcat 8.5.23
[ https://issues.apache.org/jira/browse/TOMEE-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-2133 started by Jonathan Gallimore. - > Update to Tomcat 8.5.23 > --- > > Key: TOMEE-2133 > URL: https://issues.apache.org/jira/browse/TOMEE-2133 > Project: TomEE > Issue Type: Dependency upgrade >Affects Versions: 7.0.4 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore > Fix For: 7.0.5 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work stopped] (TOMEE-2133) Update to Tomcat 8.5.23
[ https://issues.apache.org/jira/browse/TOMEE-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-2133 stopped by Jonathan Gallimore. - > Update to Tomcat 8.5.23 > --- > > Key: TOMEE-2133 > URL: https://issues.apache.org/jira/browse/TOMEE-2133 > Project: TomEE > Issue Type: Dependency upgrade >Affects Versions: 7.0.4 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore > Fix For: 7.0.5 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOMEE-2133) Update to Tomcat 8.5.23
[ https://issues.apache.org/jira/browse/TOMEE-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197721#comment-16197721 ] Jonathan Gallimore commented on TOMEE-2133: --- Updated in my fork. Currently running the full test suite. > Update to Tomcat 8.5.23 > --- > > Key: TOMEE-2133 > URL: https://issues.apache.org/jira/browse/TOMEE-2133 > Project: TomEE > Issue Type: Dependency upgrade >Affects Versions: 7.0.4 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore > Fix For: 7.0.5 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (TOMEE-2149) beforeDelivery/afterDelivery should allow zero messages to be delivered
[ https://issues.apache.org/jira/browse/TOMEE-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-2149 started by Jonathan Gallimore. - > beforeDelivery/afterDelivery should allow zero messages to be delivered > --- > > Key: TOMEE-2149 > URL: https://issues.apache.org/jira/browse/TOMEE-2149 > Project: TomEE > Issue Type: Bug >Affects Versions: 1.7.5, 7.0.4 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore > > At present we enforce that exactly one message is delivered between the > resource adapter calling beforeDelivery() and afterDelivery(). The spec > actually states that the application server should allow the resource adapter > to not deliver a message. > From section 13.5.6 of JSR-322: > "There must not be more than one message delivery in-between a single > beforeDelivery and afterDelivery method call pair. The application server > must reject beforeDelivery or afterDelivery calls that are out of sequence by > throwing an IllegalStateException. > The application server must also allow a resource adapter not to perform any > message delivery in-between a single beforeDelivery and afterDelivery method > call pair. This scenario arises, for instance, when a resource adapter first > chooses to deliver a message and calls beforeDelivery, but later is unable to > deliver the message (for example in the case of JMS resource adapters, the > resource adapter may abort the message delivery and transfer the message to a > Dead Message Queue). The resource adapter must be able to call afterDelivery > and complete the delivery cycle. The application server must perform any > possible cleanup of actions that occurred in between the beforeDelivery and > afterDelivery method calls." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TOMEE-2149) beforeDelivery/afterDelivery should allow zero messages to be delivered
Jonathan Gallimore created TOMEE-2149: - Summary: beforeDelivery/afterDelivery should allow zero messages to be delivered Key: TOMEE-2149 URL: https://issues.apache.org/jira/browse/TOMEE-2149 Project: TomEE Issue Type: Bug Affects Versions: 7.0.4, 1.7.5 Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore At present we enforce that exactly one message is delivered between the resource adapter calling beforeDelivery() and afterDelivery(). The spec actually states that the application server should allow the resource adapter to not deliver a message. >From section 13.5.6 of JSR-322: "There must not be more than one message delivery in-between a single beforeDelivery and afterDelivery method call pair. The application server must reject beforeDelivery or afterDelivery calls that are out of sequence by throwing an IllegalStateException. The application server must also allow a resource adapter not to perform any message delivery in-between a single beforeDelivery and afterDelivery method call pair. This scenario arises, for instance, when a resource adapter first chooses to deliver a message and calls beforeDelivery, but later is unable to deliver the message (for example in the case of JMS resource adapters, the resource adapter may abort the message delivery and transfer the message to a Dead Message Queue). The resource adapter must be able to call afterDelivery and complete the delivery cycle. The application server must perform any possible cleanup of actions that occurred in between the beforeDelivery and afterDelivery method calls." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (TOMEE-2149) beforeDelivery/afterDelivery should allow zero messages to be delivered
[ https://issues.apache.org/jira/browse/TOMEE-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore resolved TOMEE-2149. --- Resolution: Fixed Fix Version/s: 1.7.6 7.0.5 > beforeDelivery/afterDelivery should allow zero messages to be delivered > --- > > Key: TOMEE-2149 > URL: https://issues.apache.org/jira/browse/TOMEE-2149 > Project: TomEE > Issue Type: Bug >Affects Versions: 1.7.5, 7.0.4 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore > Fix For: 7.0.5, 1.7.6 > > > At present we enforce that exactly one message is delivered between the > resource adapter calling beforeDelivery() and afterDelivery(). The spec > actually states that the application server should allow the resource adapter > to not deliver a message. > From section 13.5.6 of JSR-322: > "There must not be more than one message delivery in-between a single > beforeDelivery and afterDelivery method call pair. The application server > must reject beforeDelivery or afterDelivery calls that are out of sequence by > throwing an IllegalStateException. > The application server must also allow a resource adapter not to perform any > message delivery in-between a single beforeDelivery and afterDelivery method > call pair. This scenario arises, for instance, when a resource adapter first > chooses to deliver a message and calls beforeDelivery, but later is unable to > deliver the message (for example in the case of JMS resource adapters, the > resource adapter may abort the message delivery and transfer the message to a > Dead Message Queue). The resource adapter must be able to call afterDelivery > and complete the delivery cycle. The application server must perform any > possible cleanup of actions that occurred in between the beforeDelivery and > afterDelivery method calls." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TOMEE-2151) Use correct classloader for creating application resources specified in resources.xml
Jonathan Gallimore created TOMEE-2151: - Summary: Use correct classloader for creating application resources specified in resources.xml Key: TOMEE-2151 URL: https://issues.apache.org/jira/browse/TOMEE-2151 Project: TomEE Issue Type: Bug Affects Versions: 7.0.4, 1.7.5 Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore I have been digging into our support for connectors in WARs and EARs, and I believe I have uncovered (and hopefully patched) a few issues, relating to EAR deployments, and defining containers in an application's resources.xml file. I have 2 PRs (which are not ready to be merged yet), and both have a sample with a connector in a WAR and a connector in a EAR file. In essence, the issue that I have run into, is where the resource adapter and container are defined in an application's resources.xml, like this: ResourceAdapter=SampleResourceAdapter ActivationSpecClass=org.superbiz.connector.adapter.SampleActivationSpec MessageListenerInterface=org.superbiz.connector.api.InboundListener ResourceAdapter=SampleResourceAdapter TransactionSupport=none when that application is deployed through webapps, either as an EAR or a WAR, it would fail: at org.apache.openejb.assembler.classic.Assembler.replaceResourceAdapterProperty(Assembler.java:2680) at org.apache.openejb.assembler.classic.Assembler.createContainer(Assembler.java:2550) at org.apache.openejb.config.ConfigurationFactory.install(ConfigurationFactory.java:429) at org.apache.openejb.config.AutoConfig.processApplicationContainers(AutoConfig.java:906) at org.apache.openejb.config.AutoConfig.deploy(AutoConfig.java:191) at org.apache.openejb.config.ConfigurationFactory$Chain.deploy(ConfigurationFactory.java:403) at org.apache.openejb.config.ConfigurationFactory.configureApplication(ConfigurationFactory.java:971) In essence what was happening was, the resource for SampleResourceAdapter was being created as a lazy resource (i.e. initialized on first lookup), and the creation of the container (which happened with TCCL being set to the main TomEE classloader), triggered that lookup, which failed with a class not found exception. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OPENEJB-2136) JUnit tests relying on 'OpenEjbContainer' and 'EJBContainerRule' fail under Java-9
[
https://issues.apache.org/jira/browse/OPENEJB-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16237465#comment-16237465
]
Jonathan Gallimore commented on OPENEJB-2136:
-
Yes. We need a release of the xbean-asm subproject at Geronimo, which will
hopefully happen soon - there has been some chat about it on the mailing list
there. Some testing has been done with some snapshots already:
https://github.com/apache/tomee/pull/109, so hopefully the update will not be
too bad.
> JUnit tests relying on 'OpenEjbContainer' and 'EJBContainerRule' fail under
> Java-9
> --
>
> Key: OPENEJB-2136
> URL: https://issues.apache.org/jira/browse/OPENEJB-2136
> Project: OpenEJB
> Issue Type: Bug
>Affects Versions: 7.0.4
> Environment: OpenEJB: 7.0.4
> Java 9.0.1-U11 (Oracle)
> JUnit 4.12 and JUnit 5.0.1
> --
> IntelliJ 2017.2
> Maven 3.5.0, Surefire-Plugin 2.19.1
> MacOS 10.13
>Reporter: Martin Wiesner
>Priority: Major
>
> In a Java 9 environment, running a JUnit Test which is starting up an
> OpenEjbContainer like so:
> {code:java}
> @Properties(
> @Property(
> key = OpenEjbContainer.OPENEJB_EJBCONTAINER_CLOSE,
> value = OpenEjbContainer.OPENEJB_EJBCONTAINER_CLOSE_SINGLE))
> public class SomeJUnitTest {
> static {
> System.setProperty(Context.INITIAL_CONTEXT_FACTORY,
> "org.apache.openejb.client.RemoteInitialContextFactory");
> }
> @ClassRule
> public static final EJBContainerRule CONTAINER_RULE = new
> EJBContainerRule();
> @Rule
> public final InjectRule injectRule = new InjectRule(this, CONTAINER_RULE);
> @TestResource
> private Context ctx;
> // test methods skipped for better readability...
> }
> {code}
> I encounter the following stacktrace which causes the test class to fail
> immediately:
> {code:java}
> org.apache.openejb.OpenEjbContainer$InitializationException:
> java.lang.IllegalArgumentException
> at
> org.apache.openejb.OpenEjbContainer$Provider.createEJBContainer(OpenEjbContainer.java:377)
> at
> javax.ejb.embeddable.EJBContainer.createEJBContainer(EJBContainer.java:56)
> at
> org.apache.openejb.junit.jee.statement.StartingStatement.before(StartingStatement.java:96)
> at
> org.apache.openejb.junit.jee.statement.DecoratingStatement.evaluate(DecoratingStatement.java:30)
> at
> org.apache.openejb.junit.jee.statement.DecoratingStatement.evaluate(DecoratingStatement.java:32)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
> at
> com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
> at
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
> at
> com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
> Caused by: java.lang.IllegalArgumentException
> at org.apache.xbean.asm5.ClassReader.(Unknown Source)
> at org.apache.xbean.asm5.ClassReader.(Unknown Source)
> at org.apache.xbean.asm5.ClassReader.(Unknown Source)
> at
> org.apache.openejb.util.AnnotationFinder.readClassDef(AnnotationFinder.java:299)
> at
> org.apache.openejb.util.AnnotationFinder.find(AnnotationFinder.java:164)
> at
> org.apache.openejb.config.DeploymentLoader.checkAnnotations(DeploymentLoader.java:2088)
> at
> org.apache.openejb.config.DeploymentLoader.discoverModuleType(DeploymentLoader.java:1971)
> at
> org.apache.openejb.config.DeploymentsResolver.processUrls(DeploymentsResolver.java:361)
> at
> org.apache.openejb.config.DeploymentsResolver.loadFromClasspath(DeploymentsResolver.java:257)
> at
> org.apache.openejb.config.ConfigurationFactory.getModulesFromClassPath(ConfigurationFactory.java:705)
> at
> org.apache.openejb.OpenEjbContainer$Provider.load(OpenEjbContainer.java:471)
> at
> org.apache.openejb.OpenEjbContainer$Provider.createEJBContainer(OpenEjbContainer.java:277)
> ... 11 more
> {code}
> Reproducible in several runtime environments: _IntelliJ Idea 2017_ and _Maven
> 3.3.9_ or _Maven 3.5.0_
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Work started] (TOMEE-2145) EAR file deployed in webapps/ deploys multiple times
[ https://issues.apache.org/jira/browse/TOMEE-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-2145 started by Jonathan Gallimore. - > EAR file deployed in webapps/ deploys multiple times > > > Key: TOMEE-2145 > URL: https://issues.apache.org/jira/browse/TOMEE-2145 > Project: TomEE > Issue Type: Bug >Affects Versions: 1.7.5, 7.0.4 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore >Priority: Normal > > TomEE supports the ability to deploy EAR files in the webapps folder, but a > bug in TomcatWebappDeployer means these artifacts get deployed twice - once > for the artifact, and once for the exploded directory. The exploded directory > usually fails. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TOMEE-2145) EAR file deployed in webapps/ deploys multiple times
Jonathan Gallimore created TOMEE-2145: - Summary: EAR file deployed in webapps/ deploys multiple times Key: TOMEE-2145 URL: https://issues.apache.org/jira/browse/TOMEE-2145 Project: TomEE Issue Type: Bug Affects Versions: 7.0.4, 1.7.5 Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Priority: Normal TomEE supports the ability to deploy EAR files in the webapps folder, but a bug in TomcatWebappDeployer means these artifacts get deployed twice - once for the artifact, and once for the exploded directory. The exploded directory usually fails. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (TOMEE-2145) EAR file deployed in webapps/ deploys multiple times
[ https://issues.apache.org/jira/browse/TOMEE-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore resolved TOMEE-2145. --- Resolution: Fixed > EAR file deployed in webapps/ deploys multiple times > > > Key: TOMEE-2145 > URL: https://issues.apache.org/jira/browse/TOMEE-2145 > Project: TomEE > Issue Type: Bug >Affects Versions: 1.7.5, 7.0.4 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore >Priority: Normal > > TomEE supports the ability to deploy EAR files in the webapps folder, but a > bug in TomcatWebappDeployer means these artifacts get deployed twice - once > for the artifact, and once for the exploded directory. The exploded directory > usually fails. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (TOMEE-2154) Using properties-provider attribute in tomee.xml throws JAXB error
[ https://issues.apache.org/jira/browse/TOMEE-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-2154 started by Jonathan Gallimore. - > Using properties-provider attribute in tomee.xml throws JAXB error > -- > > Key: TOMEE-2154 > URL: https://issues.apache.org/jira/browse/TOMEE-2154 > Project: TomEE > Issue Type: Bug >Affects Versions: 1.7.5 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore > > Using properties-provider on a element in tomee.xml throws the > following exception: > org.apache.openejb.OpenEJBException: Unable to read OpenEJB configuration > file at /path/to/tomee.xml: Unsupported Attribute(s): properties-provider. > Supported Attributes are: type, jar, provider, id, class-name, constructor, > factory-name, classpath, ctype. If the setting is a configuration property it > must be placed inside the element body. > at org.apache.openejb.config.sys.JaxbOpenejb.readConfig(JaxbOpenejb.java:219) > at > org.apache.openejb.config.ConfigurationFactory.getOpenEjbConfiguration(ConfigurationFactory.java:458) > at > org.apache.openejb.config.ConfigurationFactory.getOpenEjbConfiguration(ConfigurationFactory.java:591) > at > org.apache.openejb.assembler.classic.Assembler.getOpenEjbConfiguration(Assembler.java:487) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TOMEE-2190) Checking for .ear and .rar files in webapps uses catalina home, as opposed to catalina base
Jonathan Gallimore created TOMEE-2190: - Summary: Checking for .ear and .rar files in webapps uses catalina home, as opposed to catalina base Key: TOMEE-2190 URL: https://issues.apache.org/jira/browse/TOMEE-2190 Project: TomEE Issue Type: Dependency upgrade Affects Versions: 7.0.4, 1.7.5 Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Fix For: 7.0.5, 1.7.6 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TOMEE-2190) Checking for .ear and .rar files in webapps uses catalina home, as opposed to catalina base
[ https://issues.apache.org/jira/browse/TOMEE-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore updated TOMEE-2190: -- Fix Version/s: (was: 7.0.5) > Checking for .ear and .rar files in webapps uses catalina home, as opposed to > catalina base > --- > > Key: TOMEE-2190 > URL: https://issues.apache.org/jira/browse/TOMEE-2190 > Project: TomEE > Issue Type: Dependency upgrade >Affects Versions: 1.7.5, 7.0.4 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore >Priority: Major > Fix For: 1.7.6 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (TOMEE-2190) Checking for .ear and .rar files in webapps uses catalina home, as opposed to catalina base
[ https://issues.apache.org/jira/browse/TOMEE-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore resolved TOMEE-2190. --- Resolution: Fixed > Checking for .ear and .rar files in webapps uses catalina home, as opposed to > catalina base > --- > > Key: TOMEE-2190 > URL: https://issues.apache.org/jira/browse/TOMEE-2190 > Project: TomEE > Issue Type: Dependency upgrade >Affects Versions: 1.7.5, 7.0.4 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore >Priority: Major > Fix For: 1.7.6 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (TOMEE-2193) Update to Tomcat 8.5.32
Jonathan Gallimore created TOMEE-2193: - Summary: Update to Tomcat 8.5.32 Key: TOMEE-2193 URL: https://issues.apache.org/jira/browse/TOMEE-2193 Project: TomEE Issue Type: Dependency upgrade Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Fix For: 7.0.5 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TOMEE-2183) org.apache.commons.codec filtered by the classloader but not provided by TomEE WebProfile
[
https://issues.apache.org/jira/browse/TOMEE-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1657#comment-1657
]
Jonathan Gallimore commented on TOMEE-2183:
---
I think this test does that:
[https://github.com/apache/tomee/commit/ff78569839e82752e0abfa91dbb99132482208bb]
I'll recheck manually this afternoon as well, in case Arquillian is doing
something special that is not representative of deploying an .ear in TomEE
manually.
> org.apache.commons.codec filtered by the classloader but not provided by
> TomEE WebProfile
> -
>
> Key: TOMEE-2183
> URL: https://issues.apache.org/jira/browse/TOMEE-2183
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 7.0.4
>Reporter: Violeta Georgieva
>Assignee: Jonathan Gallimore
>Priority: Major
>
> Hi,
>
> I have an EAR file with "lib" folder that contains "commons-codec" and a WAR
> file that uses the libraries located in the "lib" folder. I do not have
> issues with the other libraries in that folder but with "commons-codec" I
> receive the exception below.
>
> I'm using TomEE 7.0.4 WebProfile and in that distribution there is no
> "commons-codec" provided by TomEE itself because of this I'm providing it
> with the EAR file.
>
> While debugging I saw that "org.apache.commons.codec" is intentionally
> filtered by the classloader
>
> [https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/util/classloader/URLClassLoaderFirst.java#L305]
>
> How it is supposed to provide this library so that my application can use it?
>
> Thanks,
> Violeta
>
> {code}
> java.lang.ClassNotFoundException: org.apache.commons.codec.binary.Base64
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1285)
>
> org.apache.tomee.catalina.TomEEWebappClassLoader.loadClass(TomEEWebappClassLoader.java:208)
>
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1119)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (TOMEE-2183) org.apache.commons.codec filtered by the classloader but not provided by TomEE WebProfile
[
https://issues.apache.org/jira/browse/TOMEE-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522067#comment-16522067
]
Jonathan Gallimore commented on TOMEE-2183:
---
I added a test for this - see these commits:
[https://github.com/apache/tomee/commit/ff78569839e82752e0abfa91dbb99132482208bb]
[https://github.com/apache/tomee/commit/2f93f96233d1bff2173824e5e44f3746b92c3eca]
This passes with all the Arquillian adapters, so I'd need some help to
reproduce this issue.
Jon
> org.apache.commons.codec filtered by the classloader but not provided by
> TomEE WebProfile
> -
>
> Key: TOMEE-2183
> URL: https://issues.apache.org/jira/browse/TOMEE-2183
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 7.0.4
>Reporter: Violeta Georgieva
>Assignee: Jonathan Gallimore
>Priority: Major
>
> Hi,
>
> I have an EAR file with "lib" folder that contains "commons-codec" and a WAR
> file that uses the libraries located in the "lib" folder. I do not have
> issues with the other libraries in that folder but with "commons-codec" I
> receive the exception below.
>
> I'm using TomEE 7.0.4 WebProfile and in that distribution there is no
> "commons-codec" provided by TomEE itself because of this I'm providing it
> with the EAR file.
>
> While debugging I saw that "org.apache.commons.codec" is intentionally
> filtered by the classloader
>
> [https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/util/classloader/URLClassLoaderFirst.java#L305]
>
> How it is supposed to provide this library so that my application can use it?
>
> Thanks,
> Violeta
>
> {code}
> java.lang.ClassNotFoundException: org.apache.commons.codec.binary.Base64
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1285)
>
> org.apache.tomee.catalina.TomEEWebappClassLoader.loadClass(TomEEWebappClassLoader.java:208)
>
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1119)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (TOMEE-2187) Upgrade to XBean 4.9
[ https://issues.apache.org/jira/browse/TOMEE-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore resolved TOMEE-2187. --- Resolution: Fixed > Upgrade to XBean 4.9 > > > Key: TOMEE-2187 > URL: https://issues.apache.org/jira/browse/TOMEE-2187 > Project: TomEE > Issue Type: Dependency upgrade >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore >Priority: Major > Fix For: 8.0.0, 7.0.5 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (TOMEE-2175) Update to Tomcat 8.5.28
[ https://issues.apache.org/jira/browse/TOMEE-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore resolved TOMEE-2175. --- Resolution: Fixed > Update to Tomcat 8.5.28 > --- > > Key: TOMEE-2175 > URL: https://issues.apache.org/jira/browse/TOMEE-2175 > Project: TomEE > Issue Type: Dependency upgrade >Affects Versions: 7.0.4 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore >Priority: Major > Fix For: 7.0.5 > > > Update to Tomcat 8.5.28 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (TOMEE-2162) Activation overrides on MDB container ignored for containers defined in resources.xml
[ https://issues.apache.org/jira/browse/TOMEE-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore reassigned TOMEE-2162: - Assignee: Jonathan Gallimore Fix Version/s: 7.0.5 Description: Activation config properties defined on a in resources.xml are not accounted for when computing activation config overrides on beans. > Activation overrides on MDB container ignored for containers defined in > resources.xml > - > > Key: TOMEE-2162 > URL: https://issues.apache.org/jira/browse/TOMEE-2162 > Project: TomEE > Issue Type: Bug >Affects Versions: 1.7.5, 7.0.4 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore > Fix For: 7.0.5, 1.7.6 > > > Activation config properties defined on a in resources.xml are > not accounted for when computing activation config overrides on beans. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (TOMEE-2161) TomEE-embedded: Attribute "keystoreFile" is not set correctly in Container startup
[
https://issues.apache.org/jira/browse/TOMEE-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Gallimore reassigned TOMEE-2161:
-
Assignee: Jonathan Gallimore
> TomEE-embedded: Attribute "keystoreFile" is not set correctly in Container
> startup
> --
>
> Key: TOMEE-2161
> URL: https://issues.apache.org/jira/browse/TOMEE-2161
> Project: TomEE
> Issue Type: Bug
>Affects Versions: 7.0.5
>Reporter: Lars Fessen
>Assignee: Jonathan Gallimore
>
> When using the Tomee-embedded Container and trying to use HTTPs the
> "keystoreFile"-attribute is not set correctly. (We are using tomee-embedded
> 7.0.0 but the github master has still the same bug)
> *How I use the container:*
> {code:java}
> Configuration cfg = new Configuration();
> cfg.setSsl(true);
> cfg.setKeystoreFile("my/path/to/keystore/keystore.p12");
> cfg.setKeystoreType("PKCS12");
> cfg.setKeystorePass("changeit");
> cfg.setSslProtocol("TLS");
> cfg.setKeyAlias("alias");
> cfg.setSkipHttp(true);
> cfg.setHttpsPort(config.getPort());
> org.apache.tomee.embedded.Container container;
> container = new Container();
> container.setup(cfg);
> container.start();
> {code}
> *Where is the bug in Tomee-embedded:*
> https://github.com/apache/tomee/blob/master/tomee/tomee-embedded/src/main/java/org/apache/tomee/embedded/Container.java
> Line: 632
> {code:java}
> if (configuration.getKeystoreFile() != null) {
> httpsConnector.setAttribute("", configuration.getKeystoreFile());
> }
> {code}
> *What is the solution (in my opinion):*
> {code:java}
> if (configuration.getKeystoreFile() != null) {
> httpsConnector.setAttribute("keystoreFile",
> configuration.getKeystoreFile());
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (TOMEE-2162) Activation overrides on MDB container ignored for containers defined in resources.xml
[ https://issues.apache.org/jira/browse/TOMEE-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore resolved TOMEE-2162. --- Resolution: Fixed > Activation overrides on MDB container ignored for containers defined in > resources.xml > - > > Key: TOMEE-2162 > URL: https://issues.apache.org/jira/browse/TOMEE-2162 > Project: TomEE > Issue Type: Bug >Affects Versions: 1.7.5, 7.0.4 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore > Fix For: 7.0.5, 1.7.6 > > > Activation config properties defined on a in resources.xml are > not accounted for when computing activation config overrides on beans. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOMEE-2161) TomEE-embedded: Attribute "keystoreFile" is not set correctly in Container startup
[
https://issues.apache.org/jira/browse/TOMEE-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320200#comment-16320200
]
Jonathan Gallimore commented on TOMEE-2161:
---
Hi
Thanks for opening this ticket. I'm happy to make the change, or alternatively,
did you want to have a go and attach a patch to this ticket? This will need a
test adding for it, but probably doesn't require anything else to be changed.
Cheers
Jon
> TomEE-embedded: Attribute "keystoreFile" is not set correctly in Container
> startup
> --
>
> Key: TOMEE-2161
> URL: https://issues.apache.org/jira/browse/TOMEE-2161
> Project: TomEE
> Issue Type: Bug
>Affects Versions: 7.0.5
>Reporter: Lars Fessen
>Assignee: Jonathan Gallimore
>
> When using the Tomee-embedded Container and trying to use HTTPs the
> "keystoreFile"-attribute is not set correctly. (We are using tomee-embedded
> 7.0.0 but the github master has still the same bug)
> *How I use the container:*
> {code:java}
> Configuration cfg = new Configuration();
> cfg.setSsl(true);
> cfg.setKeystoreFile("my/path/to/keystore/keystore.p12");
> cfg.setKeystoreType("PKCS12");
> cfg.setKeystorePass("changeit");
> cfg.setSslProtocol("TLS");
> cfg.setKeyAlias("alias");
> cfg.setSkipHttp(true);
> cfg.setHttpsPort(config.getPort());
> org.apache.tomee.embedded.Container container;
> container = new Container();
> container.setup(cfg);
> container.start();
> {code}
> *Where is the bug in Tomee-embedded:*
> https://github.com/apache/tomee/blob/master/tomee/tomee-embedded/src/main/java/org/apache/tomee/embedded/Container.java
> Line: 632
> {code:java}
> if (configuration.getKeystoreFile() != null) {
> httpsConnector.setAttribute("", configuration.getKeystoreFile());
> }
> {code}
> *What is the solution (in my opinion):*
> {code:java}
> if (configuration.getKeystoreFile() != null) {
> httpsConnector.setAttribute("keystoreFile",
> configuration.getKeystoreFile());
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (TOMEE-2162) Activation overrides on MDB container ignored for containers defined in resources.xml
Jonathan Gallimore created TOMEE-2162: - Summary: Activation overrides on MDB container ignored for containers defined in resources.xml Key: TOMEE-2162 URL: https://issues.apache.org/jira/browse/TOMEE-2162 Project: TomEE Issue Type: Bug Affects Versions: 7.0.4, 1.7.5 Reporter: Jonathan Gallimore Fix For: 1.7.6 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (TOMEE-2162) Activation overrides on MDB container ignored for containers defined in resources.xml
[ https://issues.apache.org/jira/browse/TOMEE-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-2162 started by Jonathan Gallimore. - > Activation overrides on MDB container ignored for containers defined in > resources.xml > - > > Key: TOMEE-2162 > URL: https://issues.apache.org/jira/browse/TOMEE-2162 > Project: TomEE > Issue Type: Bug >Affects Versions: 1.7.5, 7.0.4 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore > Fix For: 7.0.5, 1.7.6 > > > Activation config properties defined on a in resources.xml are > not accounted for when computing activation config overrides on beans. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (TOMEE-2173) Update to Tomcat 7.0.85
[ https://issues.apache.org/jira/browse/TOMEE-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-2173 started by Jonathan Gallimore. - > Update to Tomcat 7.0.85 > --- > > Key: TOMEE-2173 > URL: https://issues.apache.org/jira/browse/TOMEE-2173 > Project: TomEE > Issue Type: Dependency upgrade >Affects Versions: 1.7.5 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore >Priority: Major > Fix For: 1.7.6 > > > Update to Tomcat 7.0.85 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TOMEE-2173) Update to Tomcat 7.0.85
[ https://issues.apache.org/jira/browse/TOMEE-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore updated TOMEE-2173: -- Fix Version/s: 1.7.6 > Update to Tomcat 7.0.85 > --- > > Key: TOMEE-2173 > URL: https://issues.apache.org/jira/browse/TOMEE-2173 > Project: TomEE > Issue Type: Dependency upgrade >Affects Versions: 1.7.5 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore >Priority: Major > Fix For: 1.7.6 > > > Update to Tomcat 7.0.85 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TOMEE-2173) Update to Tomcat 7.0.85
[ https://issues.apache.org/jira/browse/TOMEE-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore updated TOMEE-2173: -- Affects Version/s: 1.7.5 > Update to Tomcat 7.0.85 > --- > > Key: TOMEE-2173 > URL: https://issues.apache.org/jira/browse/TOMEE-2173 > Project: TomEE > Issue Type: Dependency upgrade >Affects Versions: 1.7.5 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore >Priority: Major > Fix For: 1.7.6 > > > Update to Tomcat 7.0.85 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (TOMEE-2173) Update to Tomcat 7.0.85
Jonathan Gallimore created TOMEE-2173: - Summary: Update to Tomcat 7.0.85 Key: TOMEE-2173 URL: https://issues.apache.org/jira/browse/TOMEE-2173 Project: TomEE Issue Type: Dependency upgrade Reporter: Jonathan Gallimore Assignee: Jonathan Gallimore Update to Tomcat 7.0.85 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
