Bug 724647 (BRMS-553) - Jackrabbit fails to start repository when deployed in WAS 7 with IBM JDK 1.6 SR2
Summary: Jackrabbit fails to start repository when deployed in WAS 7 with IBM JDK 1.6 SR2
Keywords:
Status: CLOSED DUPLICATE of bug 724646
Alias: BRMS-553
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: 3rd Party
Version: 5.1.0 GA
Hardware: Unspecified
OS: Unspecified
urgent
unspecified
Target Milestone: ---
: ---
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-15 16:13 UTC by Jiri Locker
Modified: 2011-09-20 12:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
RHEL 5 IBM WebSphere Application Server - ND7.0.0.0 IBM J9 VM (build 2.4, J2RE 1.6.0)
Last Closed: 2011-02-18 20:20:02 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-553 0 None None None Never

Description Jiri Locker 2011-02-15 16:13:54 UTC
Affects Testing: Blocks Testing
securitylevel_name: Public

{{(RepositoryImpl.java:<init>:404) failed to start Repository: : is not a registered namespace uri.}}

This configuration exposes https://issues.apache.org/jira/browse/JCR-888. Can be fixed by upgrading to Jackrabbit 2.1.3. It would be nice to include the fix in 5.1.1.

Comment 1 Jiri Locker 2011-02-15 16:28:23 UTC
Link: Added: This issue duplicates BRMS-552


Comment 2 Len DiMaggio 2011-02-15 18:08:47 UTC
We should test with the version of the IBM JDK that is available from RHN:

java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build pxi3260sr9-20101125_01(SR9))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260sr9-20101124_69295 (JIT enabled, AOT enabled)
J9VM - 20101124_069295
JIT - r9_20101028_17488ifx2
GC - 20101027_AA)
JCL - 20101119_01

java-1.6.0-ibm-1.6.0.9.0

https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=606191




Note You need to log in before you can comment on or make changes to this bug.