You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by Bryce Ewing <br...@gmail.com> on 2010/07/11 11:52:41 UTC
Feature file downloading issue
Hi,
I am having a strange issue with attempting to upgrade to Karaf 1.6.0. The
feature files that are installed correctly in Karaf 1.4.0 now fail to
download. The set of circumstances that might be related are:
* feature files deployed within a jar file in a maven repository
* this is accessed via https
* this also requires a username/password
I have double checked configuration between the two instances and can't see
any difference in settings that would account for this. I get this log
output:
Unable to add features repository
jar:mvn:example/example.features/0.0.5!/example.xml at startup
java.io.IOException: URL [mvn:example/example.features/0.0.5] could not be
resolved. : jar:mvn:example/example.features/0.0.5!/example.xml
In debug I get (username/password/host changed):
09:16:46,284 | DEBUG | l Console Thread | Connection |
.pax.url.mvn.internal.Connection 190 | 1 - org.ops4j.pax.url.mvn - 1.1.2 |
Could not download [Version [0.0.5] from URL
[https://username:password@example.com/nexus/content/repositories/releases/example/example.features/0.0.5/example.features-0.0.5.jar]]
Using that url via wget or chrome works perfectly. I think from my
investigations that the pax url mvn version hasn't changed.
I am running out of things to try and was wondering if anyone had any
thoughts?
Cheers
Bryce
--
View this message in context: http://karaf.922171.n3.nabble.com/Feature-file-downloading-issue-tp957778p957778.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Feature file downloading issue
Posted by Charles Moulliard <cm...@gmail.com>.
Great. Thx for your collaboration and help.
On Fri, Jul 16, 2010 at 1:41 AM, Bryce Ewing <br...@gmail.com> wrote:
>
> Hi Charles,
>
> Sorry it has taken a while to try this and get back to you, been flat out
> with other things. Anyway today I got around to trying log level TRACE,
> should have done that earlier, and that lead to getting this extra detail:
> "javax.net.ssl.SSLKeyException: RSA premaster secret error"
>
> Which after searching around the internet a little lead to the following
> post:
> http://markmail.org/message/r4uwwisni7poghu6
>
> Which got me to change (in bin/karaf):
> exec $JAVA $JAVA_OPTS
> -Djava.endorsed.dirs="${JAVA_HOME}/lib/endorsed:${KARAF_HOME}/lib/endorsed"
> -Djava.ext.dirs="${JAVA_HOME}/lib/ext:${KARAF_HOME}/lib/ext"
> -Dstorage.location="${KARAF_HOME}/instances" -Dkaraf.home="$KARAF_HOME"
> -Dkaraf.base="$KARAF_BASE"
>
> -Djava.util.logging.config.file=$KARAF_BASE/etc/java.util.logging.properties
> $OPTS -classpath "$CLASSPATH" $MAIN "$@"
> to:
> exec $JAVA $JAVA_OPTS
> -Djava.endorsed.dirs="${JAVA_HOME}/lib/endorsed:${KARAF_HOME}/lib/endorsed"
> -Djava.ext.dirs="${JAVA_HOME}/jre/lib/ext:${KARAF_HOME}/lib/ext"
> -Dstorage.location="${KARAF_HOME}/instances" -Dkaraf.home="$KARAF_HOME"
> -Dkaraf.base="$KARAF_BASE"
>
> -Djava.util.logging.config.file=$KARAF_BASE/etc/java.util.logging.properties
> $OPTS -classpath "$CLASSPATH" $MAIN "$@"
>
> Note: only change is ${JAVA_HOME}/lib/ext -> ${JAVA_HOME}/jre/lib/ext
>
> And this works. I will raise a ticket about this.
>
> Cheers
> Bryce
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/Feature-file-downloading-issue-tp957778p970987.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
Re: Feature file downloading issue
Posted by Bryce Ewing <br...@gmail.com>.
Hi Charles,
Sorry it has taken a while to try this and get back to you, been flat out
with other things. Anyway today I got around to trying log level TRACE,
should have done that earlier, and that lead to getting this extra detail:
"javax.net.ssl.SSLKeyException: RSA premaster secret error"
Which after searching around the internet a little lead to the following
post:
http://markmail.org/message/r4uwwisni7poghu6
Which got me to change (in bin/karaf):
exec $JAVA $JAVA_OPTS
-Djava.endorsed.dirs="${JAVA_HOME}/lib/endorsed:${KARAF_HOME}/lib/endorsed"
-Djava.ext.dirs="${JAVA_HOME}/lib/ext:${KARAF_HOME}/lib/ext"
-Dstorage.location="${KARAF_HOME}/instances" -Dkaraf.home="$KARAF_HOME"
-Dkaraf.base="$KARAF_BASE"
-Djava.util.logging.config.file=$KARAF_BASE/etc/java.util.logging.properties
$OPTS -classpath "$CLASSPATH" $MAIN "$@"
to:
exec $JAVA $JAVA_OPTS
-Djava.endorsed.dirs="${JAVA_HOME}/lib/endorsed:${KARAF_HOME}/lib/endorsed"
-Djava.ext.dirs="${JAVA_HOME}/jre/lib/ext:${KARAF_HOME}/lib/ext"
-Dstorage.location="${KARAF_HOME}/instances" -Dkaraf.home="$KARAF_HOME"
-Dkaraf.base="$KARAF_BASE"
-Djava.util.logging.config.file=$KARAF_BASE/etc/java.util.logging.properties
$OPTS -classpath "$CLASSPATH" $MAIN "$@"
Note: only change is ${JAVA_HOME}/lib/ext -> ${JAVA_HOME}/jre/lib/ext
And this works. I will raise a ticket about this.
Cheers
Bryce
--
View this message in context: http://karaf.922171.n3.nabble.com/Feature-file-downloading-issue-tp957778p970987.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Feature file downloading issue
Posted by Charles Moulliard <cm...@gmail.com>.
Hy Brice,
Have you tried to install the feature with set log to level TRACE, this will
help us to get the error returned by Pax Url ?
Can you raised a jira ticket on Karaf web site in order for us to reproduce
the case please ?
https://issues.apache.org/jira/secure/CreateIssue!default.jspa?pid=12311140
Kind regards,
Charles Moulliard
Senior Enterprise Architect (J2EE, .NET, SOA)
Apache Camel - ServiceMix Committer
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Blog : http://cmoulliard.blogspot.com | Twitter :
http://twitter.com/cmoulliard
Linkedin : http://www.linkedin.com/in/charlesmoulliard | Skype: cmoulliard
On Sun, Jul 11, 2010 at 11:52 AM, Bryce Ewing <br...@gmail.com> wrote:
>
> Hi,
>
> I am having a strange issue with attempting to upgrade to Karaf 1.6.0. The
> feature files that are installed correctly in Karaf 1.4.0 now fail to
> download. The set of circumstances that might be related are:
> * feature files deployed within a jar file in a maven repository
> * this is accessed via https
> * this also requires a username/password
>
> I have double checked configuration between the two instances and can't see
> any difference in settings that would account for this. I get this log
> output:
> Unable to add features repository
> jar:mvn:example/example.features/0.0.5!/example.xml at startup
> java.io.IOException: URL [mvn:example/example.features/0.0.5] could not be
> resolved. : jar:mvn:example/example.features/0.0.5!/example.xml
>
> In debug I get (username/password/host changed):
> 09:16:46,284 | DEBUG | l Console Thread | Connection
> |
> .pax.url.mvn.internal.Connection 190 | 1 - org.ops4j.pax.url.mvn - 1.1.2 |
> Could not download [Version [0.0.5] from URL
> [
> https://username:password@example.com/nexus/content/repositories/releases/example/example.features/0.0.5/example.features-0.0.5.jar
> ]]
>
> Using that url via wget or chrome works perfectly. I think from my
> investigations that the pax url mvn version hasn't changed.
>
> I am running out of things to try and was wondering if anyone had any
> thoughts?
>
> Cheers
> Bryce
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/Feature-file-downloading-issue-tp957778p957778.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>