buildbot failure in ASF Buildbot on tomee-trunk-ubuntu
The Buildbot has detected a new failure on builder tomee-trunk-ubuntu while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/tomee-trunk-ubuntu/builds/50 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: hemera_ubuntu Build Reason: scheduler Build Source Stamp: [branch tomee/tomee/trunk] 1439278 Blamelist: rmannibucau BUILD FAILED: failed test sincerely, -The Buildbot
buildbot success in ASF Buildbot on tomee-trunk-ubuntu
The Buildbot has detected a restored build on builder tomee-trunk-ubuntu while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/tomee-trunk-ubuntu/builds/51 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: hemera_ubuntu Build Reason: scheduler Build Source Stamp: [branch tomee/tomee/trunk] 1439279 Blamelist: rmannibucau Build succeeded! sincerely, -The Buildbot
[jira] [Commented] (TOMEE-465) Classloader memory leak on redeployment
[ https://issues.apache.org/jira/browse/TOMEE-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13564238#comment-13564238 ] Romain Manni-Bucau commented on TOMEE-465: -- is it still an issue? Classloader memory leak on redeployment --- Key: TOMEE-465 URL: https://issues.apache.org/jira/browse/TOMEE-465 Project: TomEE Issue Type: Bug Affects Versions: 1.5.0 Reporter: Harald Wellmann Attachments: tomee-leak.zip Redeploying the attached webapp a couple of times in a row (e.g. by modifying and saving the source file in Eclipse with WTP and automatic publishing enabled) leads to an OutOfMemoryError. Inspecting the heap with Eclipse Memory Analyzer, I see stale copies of the LeakingSingleton class having the contextClassLoader of an org.apache.openejb.scheduler.pool thread as GC root. Tested with apache-tomee-1.5.1-20121014.041023-38-webprofile.zip -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TOMEE-551) Prepare blog announcement
[ https://issues.apache.org/jira/browse/TOMEE-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau closed TOMEE-551. Resolution: Fixed Prepare blog announcement - Key: TOMEE-551 URL: https://issues.apache.org/jira/browse/TOMEE-551 Project: TomEE Issue Type: Sub-task Reporter: Jean-Louis MONTEIRO Commands: http://svn.apache.org/repos/asf/openejb/trunk/sandbox/release-tools/src/main/java/org/apache/openejb/tools/release/cmd/.java -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TOMEE-501) Implement openjpa load-time enhancement by means of PersistenceUnitInfo.addTransformer(ClassTransformer)
[ https://issues.apache.org/jira/browse/TOMEE-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau closed TOMEE-501. Resolution: Not A Problem Assignee: Romain Manni-Bucau it is already the case through the javaagent. In TomEE we could duplicate the code in the webappclassloader but we clearly can't in OpenEJB embedded (or arquillian-openejb-embedded) so to avoid to duplicate the logic and since the only constraint is to ensure the javaagent 'openejb one) is present (case by default) i'm closing this issue. If you need something more specific please reopen and add a comment Implement openjpa load-time enhancement by means of PersistenceUnitInfo.addTransformer(ClassTransformer) Key: TOMEE-501 URL: https://issues.apache.org/jira/browse/TOMEE-501 Project: TomEE Issue Type: Improvement Affects Versions: 1.5.0 Reporter: Anthony Fryer Assignee: Romain Manni-Bucau Labels: openjpa See http://openejb.979440.n4.nabble.com/JPA-Load-Time-Enhancement-td4658181.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOMEE-671) TomEE does not implement jaxrs-2.0 specification item 2.3.2
[
https://issues.apache.org/jira/browse/TOMEE-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13564240#comment-13564240
]
Romain Manni-Bucau commented on TOMEE-671:
--
@Thiago: is it still the case?
TomEE does not implement jaxrs-2.0 specification item 2.3.2
Key: TOMEE-671
URL: https://issues.apache.org/jira/browse/TOMEE-671
Project: TomEE
Issue Type: Bug
Affects Versions: 1.5.1, 1.5.2
Reporter: Thiago Veronezi
Labels: features
TomEE does not publish applications via the servlet trick proposed by the
jaxrs-2.0 specification
Item 2.3.2:
servlet
servlet-namejavax.ws.rs.core.Application/servlet-name
/servlet
servlet-mapping
servlet-namejavax.ws.rs.core.Application/servlet-name
url-pattern/app/*/url-pattern
/servlet-mapping
It throws a null pointer exception at the line 180 of the
org.apache.openejb.util.classloader.URLClassLoaderFirst class.
// making all these call inline if far more costly than factorizing
packages
public static boolean shouldSkip(final String name) {
for (String prefix : FORCED_SKIP) {
if (name.startsWith(prefix)) {
return true;
}
}
for (String prefix : FORCED_LOAD) {
if (name.startsWith(prefix)) {
return false;
}
}
if (name.startsWith(java.)) return true; //HERE - name is NULL
if (name.startsWith(javax.faces.)) return false;
if (name.startsWith(javax.)) return true;
if (name.startsWith(sun.)) return true;
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TOMEE-423) Move TomEE's transport out of the tomee's management UI web app
[ https://issues.apache.org/jira/browse/TOMEE-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau closed TOMEE-423. Resolution: Fixed doc added so closing this jira. please reopen if more info are needed Move TomEE's transport out of the tomee's management UI web app --- Key: TOMEE-423 URL: https://issues.apache.org/jira/browse/TOMEE-423 Project: TomEE Issue Type: Improvement Affects Versions: 1.0.0, 1.5.0 Reporter: Alex the Rocker As a measure of security hardening, people want to delete the application server's management UI to prevent remote access to it ; especially for app servers exposed to Internet access. Problem with removing tomee from webapps directory is that it contains EE features such an EJB transport. This JIRA is to request a separation of TomEE transport features from TomEE management web app ; so that this later web app can safely deleted without risking any regression for web applications run-time features. Apache Tomcat supports with process, so it can be a showstopper for organizations considering a move from Tomcat to TomEE. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TOMEE-503) @EndpointProperty property ignored
[
https://issues.apache.org/jira/browse/TOMEE-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Romain Manni-Bucau closed TOMEE-503.
Resolution: Fixed
Fix Version/s: 1.5.1
Assignee: Romain Manni-Bucau
please reopen if you still encounter the issue
@EndpointProperty property ignored
--
Key: TOMEE-503
URL: https://issues.apache.org/jira/browse/TOMEE-503
Project: TomEE
Issue Type: Bug
Reporter: David Blevins
Assignee: Romain Manni-Bucau
Fix For: 1.5.1
[15:28] reinis_v @EndpointProperties(value = { @EndpointProperty(key =
ws-security.callback-handler, value = { SchedulerServicePasswordCallback
}) }) - only by means of ejb-jar.xml as I found out
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TOMEE-188) Trim TomEE web profile libraries
[ https://issues.apache.org/jira/browse/TOMEE-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau closed TOMEE-188. Resolution: Fixed Fix Version/s: 1.5.1 Trim TomEE web profile libraries Key: TOMEE-188 URL: https://issues.apache.org/jira/browse/TOMEE-188 Project: TomEE Issue Type: Improvement Reporter: David Blevins Fix For: 1.5.1 Some libraries can likely be removed. In particular: - asm-3.2.jar - commons-cli-1.2.jar - gson-2.1.jar - scannotation-1.0.2.jar - xbean-bundleutils-3.11-SNAPSHOT.jar The need for the following should be investigated: - commons-lang-2.6.jar - commons-lang3-3.1.jar - slf4j-api-1.6.4.jar - slf4j-jdk14-1.6.4.jar -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (OPENEJB-1994) App directory with space in name fails on Win platforms
[ https://issues.apache.org/jira/browse/OPENEJB-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on OPENEJB-1994 started by Andy Gumbrecht. App directory with space in name fails on Win platforms --- Key: OPENEJB-1994 URL: https://issues.apache.org/jira/browse/OPENEJB-1994 Project: OpenEJB Issue Type: Bug Environment: Win platforms Reporter: Andy Gumbrecht Assignee: Andy Gumbrecht Priority: Blocker Jars placed in an application deployment directory with space in the directory name fails on Win platforms -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
