You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Gary Gregory (JIRA)" <ji...@apache.org> on 2015/10/27 18:27:27 UTC
[jira] [Commented] (DBCP-449) Cannot use DBCP on Google App Engine
[ https://issues.apache.org/jira/browse/DBCP-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976790#comment-14976790 ]
Gary Gregory commented on DBCP-449:
-----------------------------------
I'm not sure that's going to cut it. We might need to create a separate class to handle JMX and JNDI features so they are not loaded when a main class is loaded.
> Cannot use DBCP on Google App Engine
> ------------------------------------
>
> Key: DBCP-449
> URL: https://issues.apache.org/jira/browse/DBCP-449
> Project: Commons Dbcp
> Issue Type: Bug
> Affects Versions: 2.0.1, 2.1
> Environment: Google App Engine
> Reporter: Grzegorz D.
> Priority: Blocker
>
> There is no way to disable the use of JMX when using PoolableConnections. Line 53 of PoolableConnection.java uses the ManagementFactory which is blacklisted in Google App Engine.
> MBEAN_SERVER = ManagementFactory.getPlatformMBeanServer();
> "java.lang.NoClassDefFoundError: java.lang.management.ManagementFactory is a restricted class. Please see the Google App Engine developer's guide for more details."
> Closed issue DBCP-418 should catch (NoClassDefFoundError | Exception ex) instead of (Exception ex)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)