Community
Participate
Working Groups
Target <weblogic-setup> in jpa/eclipselink.jpa.test/weblogic.xml failed to create datasource connecting to Apache Derby Network Server 10.5.3.0 Error Message: ============== server-setup: weblogic-setup: [wlconfig] Ok [wlconfig] Ok [wlconfig] Ok [wlconfig] Ok [wlconfig] Ok [wlconfig] Ok [wlconfig] Ok [wlconfig] [wlconfig] weblogic.management.DistributedManagementException : Distributed Management [1 exceptions] [wlconfig] BUILD FAILED /net/qaott07.ca.oracle.com/scratch/aime/eclipselink/org.eclipse.persistence/trunk/jpa/eclipselink.jpa.test/build.xml:1391: The following error occurred while executing this line: /net/qaott07.ca.oracle.com/scratch/aime/eclipselink/org.eclipse.persistence/trunk/jpa/eclipselink.jpa.test/weblogic.xml:135: Error invoking MBean command: javax.management.MBeanException Total time: 6 seconds
>see additional info setting up a local server Derby 10.5.3.0 datasource for an EclipseLink based EAR via the WebLogic console. http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial#Derby_JTA_Datasource_Setup
This bug fix did not make the cut off for 2.1. We are deferring the bugs to Future where we can properly sort them all together and severity. And then assign them accordingly to future patch sets and releases.
Since Derby need to provide database name and server name (host) except database URL, so not like other database (e.g. Oracle, MySQL, DB2, SQLServer, etc) only need database URL. Fix this issue by providing special Python scripts for Derby (wls_derby_setup.py). Verified by running JPA LRG on WLS 10.3.4 against Derby 10. Code reviewed by Edwin Tang. Checked in trunk (2.3).
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink