IOException on web demo when trying to connect through SSH
----------------------------------------------------------
Key: KARAF-137
URL: https://issues.apache.org/jira/browse/KARAF-137
Project: Karaf
Issue Type: Bug
Affects Versions: 1.6.2
Environment: Ubuntu Karmic x86_64, kernel 2.6.32-23-generic #37-Ubuntu
Reporter: Jorge Riquelme Santana
Priority: Minor
I found this issue in apache-servicemix-4.2.0-fuse-02-00, the Fuse distribution
of ServiceMix (with karaf-1.4.0-fuse-02-00 embedded).
When trying to connect via ssh to the web demo, the client receives a "closed
connection", and the log
/var/lib/tomcat6/webapps/servicemix/WEB-INF/karaf/data/log/karaf.log shows:
java.io.IOException: Unable to start shell
at
org.apache.felix.karaf.shell.ssh.ShellFactoryImpl$ShellImpl.start(ShellFactoryImpl.java:120)
at
org.apache.sshd.server.channel.ChannelSession.handleShell(ChannelSession.java:377)
at
org.apache.sshd.server.channel.ChannelSession.handleRequest(ChannelSession.java:230)
at
org.apache.sshd.server.channel.ChannelSession.handleRequest(ChannelSession.java:199)
at
org.apache.sshd.common.session.AbstractSession.channelRequest(AbstractSession.java:999)
at
org.apache.sshd.server.session.ServerSession.handleMessage(ServerSession.java:210)
at
org.apache.sshd.common.session.AbstractSession.decode(AbstractSession.java:522)
at
org.apache.sshd.common.session.AbstractSession.messageReceived(AbstractSession.java:225)
at
org.apache.sshd.common.AbstractSessionIoHandler.messageReceived(AbstractSessionIoHandler.java:58)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain$TailFilter.messageReceived(DefaultIoFilterChain.java:713)[26:org.apache.mina.core:2.0.0.RC1]
at
org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)[26:org.apache.mina.core:2.0.0.RC1]
at
org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:46)[26:org.apache.mina.core:2.0.0.RC1]
at
org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:793)[26:org.apache.mina.core:2.0.0.RC1]
at
org.apache.mina.core.filterchain.IoFilterAdapter.messageReceived(IoFilterAdapter.java:119)[26:org.apache.mina.core:2.0.0.RC1]
at
org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)[26:org.apache.mina.core:2.0.0.RC1]
at
org.apache.mina.core.filterchain.DefaultIoFilterChain.fireMessageReceived(DefaultIoFilterChain.java:426)[26:org.apache.mina.core:2.0.0.RC1]
at
org.apache.mina.core.polling.AbstractPollingIoProcessor.read(AbstractPollingIoProcessor.java:638)[26:org.apache.mina.core:2.0.0.RC1]
at
org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:598)[26:org.apache.mina.core:2.0.0.RC1]
at
org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:587)[26:org.apache.mina.core:2.0.0.RC1]
at
org.apache.mina.core.polling.AbstractPollingIoProcessor.access$400(AbstractPollingIoProcessor.java:61)[26:org.apache.mina.core:2.0.0.RC1]
at
org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run(AbstractPollingIoProcessor.java:969)[26:org.apache.mina.core:2.0.0.RC1]
at
org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:64)[26:org.apache.mina.core:2.0.0.RC1]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)[:1.6.0_20]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)[:1.6.0_20]
at java.lang.Thread.run(Thread.java:619)[:1.6.0_20]
The workaround is to create the directory /usr/share/tomcat6/.karaf with
writing permissions to the user tomcat6 (so karaf can create the file
karaf.history, reason of the IOEx). As a note, I set the variable
storage.location in tomcat; maybe this is the place to put the .karaf directory.
The error still happens in karaf-1.7-SNAPSHOT (checked out from
https://svn.apache.org/repos/asf/karaf/branches/karaf-1.x)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
