jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Parvulescu (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (JCR-3459) RmiRepositoryFactory regression, invalid stream header
Date Mon, 19 Nov 2012 11:40:59 GMT

     [ https://issues.apache.org/jira/browse/JCR-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alex Parvulescu resolved JCR-3459.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.6

fixed with rev r1411132.

It seems that extracting the #getRemoteRepository part in a dedicated class fixes the issue.

I'd like to see what others think.
                
> RmiRepositoryFactory regression, invalid stream header
> ------------------------------------------------------
>
>                 Key: JCR-3459
>                 URL: https://issues.apache.org/jira/browse/JCR-3459
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-jcr-rmi
>            Reporter: Alex Parvulescu
>            Assignee: Alex Parvulescu
>             Fix For: 2.6
>
>
> Following JCR-3454 I've noticed a regression, I have a remote test failing with the following
trace [0]
> I've narrowed it down to rev 1409181, which means that this change is not visible with
JR 2.5.2, but it is with 2.6-SNAPSHOT (a fresh trunk build).
> [0]
> org.apache.jackrabbit.rmi.client.RemoteRepositoryException: java.rmi.RemoteException:
Failed to read the resource at URL http://localhost:52833/....; nested exception is: 
> java.io.StreamCorruptedException: invalid stream header: 3C68746D
> at org.apache.jackrabbit.rmi.client.SafeClientRepository.remoteLogin(SafeClientRepository.java:112)
> at org.apache.jackrabbit.rmi.client.SafeClientRepository.login(SafeClientRepository.java:120)
> at org.apache.jackrabbit.rmi.client.SafeClientRepository.login(SafeClientRepository.java:131)

--
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

Mime
View raw message