From derby-dev-return-96785-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Sun Jul 1 05:14:13 2012 Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 04967CEE6 for ; Sun, 1 Jul 2012 05:14:12 +0000 (UTC) Received: (qmail 44780 invoked by uid 500); 1 Jul 2012 05:14:12 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 44650 invoked by uid 500); 1 Jul 2012 05:14:12 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 44626 invoked by uid 99); 1 Jul 2012 05:14:11 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Jul 2012 05:14:11 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 855BC141BDA for ; Sun, 1 Jul 2012 05:14:10 +0000 (UTC) Date: Sun, 1 Jul 2012 05:14:10 +0000 (UTC) From: "Bryan Pendleton (JIRA)" To: derby-dev@db.apache.org Message-ID: <232862158.76236.1341119650547.JavaMail.jiratomcat@issues-vm> In-Reply-To: <1556917336.29859.1332966206021.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (DERBY-5676) Database cannot to started MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404681#comment-13404681 ] Bryan Pendleton commented on DERBY-5676: ---------------------------------------- At the very least, it seems like we should document the incompatibility between IBMJCECCA encryption provider and Derby's encryption requests. Ideally, if we could understand the incompatibility more clearly, it would be nice to modify Derby's encryption code to be compatible with the IBMJCECCA provider. > Database cannot to started > -------------------------- > > Key: DERBY-5676 > URL: https://issues.apache.org/jira/browse/DERBY-5676 > Project: Derby > Issue Type: Bug > Components: Tools > Affects Versions: 10.5.3.0 > Environment: Operating System: Z/OS version > These are some of the OS properties. > 0SYSTEM PROPERTIES: > java.vendor=IBM Corporation > os.name=z/OS > java.vm.specification.vendor=Sun Microsystems Inc. > java.runtime.version=pmz3160_26sr1-20111114_01 (SR1) > user.language=en > java.version=1.6.0 > user.timezone=America/New_York > sun.arch.data.model=32 > com.ibm.zero.version=2 > java.endorsed.dirs=/HO43/Vantagegmi/runtime/apache-tomcat-6.0.20/common/endorsed > com.ibm.oti.vm.library.version=26 > sun.jnu.encoding=IBM-1047 > jxe.current.romimage.version=17 > package.access=sun.,org.apache.catalina.,org.apache.coyote.,org.apache.tomcat.,org.apache.jasper.,sun.beans. > file.separator=/ > java.specification.name=Java Platform API Specification > java.class.version=50.0 > user.country=US > java.home=/tfsjava/J6.0 > java.vm.info=JRE 1.6.0 z/OS s390-31 20111113_94967 (JIT enabled, AOT enabled) > J9VM - R26_Java626_SR1_20111113_1649_B94967 > JIT - r11_20111028_21230 > GC - R26_Java626_SR1_20111113_1649_B94967 > J9CL - 20111113_94967 > os.version=01.13.00 > ibm.serversocket.recover=true > java.awt.fonts= > path.separator=: > java.vm.version=2.6 > java.util.prefs.PreferencesFactory=java.util.prefs.FileSystemPreferencesFactory > user.variant= > java.awt.printerjob=sun.print.PSPrinterJob > sun.io.unicode.encoding=UnicodeBig > awt.toolkit=sun.awt.X11.XToolkit > ibm.signalhandling.sigint=true > java.assistive=ON > package.definition=sun.,java.,org.apache.catalina.,org.apache.coyote.,org.apache.tomcat.,org.apache.jasper. > java.naming.factory.url.pkgs=org.apache.naming > user.home=/HO43/tmp > com.ibm.cpu.endian=big > java.specification.vendor=Sun Microsystems Inc. > ibm.signalhandling.sigchain=false > sun.security.policy.utf8=false > java.library.path=/tfsjava/J6.0/lib/s390/default:/tfsjava/J6.0/lib/s390:/tfsjava/J6.0/lib/s390/default:/lib:/usr/lib:/tfsjava/J6 > .0/bin:/tfsjava/J6.0/bin/classic::/tfsjava/J6.0/lib/s390/default:/tfsjava/J6.0/lib/s390 > java.vendor.url=http://www.ibm.com/ > java.vm.vendor=IBM Corporation > platform.notASCII=true > common.loader=${catalina.home}/lib,${catalina.home}/lib/*.jar > java.fullversion=JRE 1.6.0 IBM J9 2.6 z/OS s390-31 20111113_94967 (JIT enabled, AOT enabled) > J9VM - R26_Java626_SR1_20111113_1649_B94967 > JIT - r11_20111028_21230 > GC - R26_Java626_SR1_20111113_1649_B94967 > J9CL - 20111113_94967 > java.runtime.name=Java(TM) SE Runtime Environment > java.class.path=/tfsjava/J6.0/lib/tools.jar:/HO43/Vantagegmi/runtime/apache-tomcat-6.0.20/bin/bootstrap.jar:/HO43/Vantagegmi/run > time/apache-tomcat-6.0.20/bin/commons-logging-api.jar: > java.vm.specification.name=Java Virtual Machine Specification > java.vm.specification.version=1.0 > sun.cpu.endian=big > ibm.system.encoding=IBM-1047 > os.arch=s390 > java.vm.name=IBM J9 VM > com.ibm.oti.shared.enabled=false > com.ibm.vm.bitmode=32 > file.encoding=ISO8859-1 > > Reporter: Ambili > Priority: Blocker > Attachments: db.pax.Z, db.tar, db.tar, derby.log, scriptinascii.zip, scripts.tar > > > The install is created on a HFS file system. And we create DB using this command > java -cp . -jar derbyrun.jar ij databaseAuth.sql > and databaseAuth.sql content is given below. > connect 'jdbc:derby: /HO4/test/testDb;create=true;dataEncryption=true;bootPassword=Password;encryptionAlgorithm=AES/CBC/NoPadding;'; > -------------------------------------------------------------------------------- > -- CREATE TESTTABLE TABLE WITH PRIMARY KEY OF USERNAME > -- STEP 2 > -------------------------------------------------------------------------------- > CREATE TABLE TESTTABLE > ( > USERNAME VARCHAR(30) NOT NULL, > PASSWORD VARCHAR(30) NOT NULL, > PRIMARY KEY (USERNAME) > ); > -------------------------------------------------------------------------------- > -- INSERT USER INTO TESTTABLE TABLE > -- STEP 3 > -------------------------------------------------------------------------------- > INSERT INTO TESTTABLE VALUES('', ''); > EXIT; > Create was successful. But when we try to connect to DB again it fails to start with error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira