[
https://issues.apache.org/jira/browse/CLEREZZA-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997144#comment-12997144
]
Henry Story commented on CLEREZZA-430:
--------------------------------------
A few notes:
- When connected remotely to the shell via ssh, any standard output is sent to
the startup shell - the one that one ran the command line on. So that console
is still active for output
- if one connects to a remote ssh shell and runs the new X509Key() code above
that will also close the remote connection
> scala shell crashes on null pointer exception
> ---------------------------------------------
>
> Key: CLEREZZA-430
> URL: https://issues.apache.org/jira/browse/CLEREZZA-430
> Project: Clerezza
> Issue Type: Bug
> Reporter: Henry Story
> Priority: Minor
>
> On a machine running a sun jvm one can crash the shell by running
> zz> val dnsKey = new sun.security.x509.X509Key()
> console terminated
> org.apache.clerezza.shell.Shell$$anon$1@28f9f1b9: caught
> java.lang.NoClassDefFoundError: sun/security/x509/X509Key
> java.lang.NoClassDefFoundError: sun/security/x509/X509Key
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2427)
> at java.lang.Class.getMethod0(Class.java:2670)
> at java.lang.Class.getMethod(Class.java:1603)
> at scala.tools.nsc.Interpreter$Request.loadAndRun(Interpreter.scala:972)
> On can connect back to the shell using
> $ ssh admin@localhost -p 8022
> but it could be annoying.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
