Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #33576 > unrolled thread

New Exceptions When Moved from 1.60105 to 1.6033 (and Have SSH Non-default Options)

Back to article view | Back to comp.lang.java.programmer

Contents

  New Exceptions When Moved from 1.60105 to 1.6033 (and Have SSH Non-default Options) "FrankJ@gmail.com" <ashos.owner@gmail.com> - 2016-02-03 10:44 -0800
    Re: New Exceptions When Moved from 1.60105 to 1.6033 (and Have SSH Non-default Options) Knute Johnson <nospam@rabbitbrush.frazmtn.com> - 2016-02-03 15:57 -0800

#33576 — New Exceptions When Moved from 1.60105 to 1.6033 (and Have SSH Non-default Options)

Hello,

Can anyone tell me how to fix a large application which gives runtime exceptions when the operator has a newer version of Java installed and uses SSH cipher options? (I.E. When SSH options are specified with the new version of Java exceptions are produced.)

I do not get the exceptions with Java 1.60105 and with SSH having no options (I.E.: which uses the default cipher).

I get the exceptions with Java 1.6033 and with SSH options which specify a non-default cipher.


(1) When I start the application's manager, I get the exception:

java.io.IOException

(2) When I login into the manager of the application, I get the exception:

Error authenticating java.lang.IllegalStateException: Session is closed

(3) When I try to access a manager plugin of the application, I get exceptions such as:

javax.xml.bind.UnmarshalException
org.springframework.http.converter.HttpMessageNotReadableException
org.springframework.oxm.UnmarshallingFailureException
javax.xml.bind.UnmarshalException
org.springframework.oxm.jaxb.Jaxb2Marshaller.convertJaxException
com.google.gwt.user.server.rpc.UnexpectedException

java.net.malformedURLException   //First exception seen under (3)

(4) When I access another module in the same application, I get exceptions such as:

org/apache/activeis/journal/active/JournalLockedException
org.jasypt.exceptions.ENcryptionOperationNotPossibleException

WebApplicationException


Thank you,
Frank Justine

P.S.: I run the failed and successful application on the same operating systems. The only difference on the hardware is that on a sparc 4.2 it works but on sparc 4.3 we get exceptions. 

[toc] | [next] | [standalone]

#33579

On 2/3/2016 10:44, FrankJ@gmail.com wrote:
> Hello,
>
> Can anyone tell me how to fix a large application which gives runtime exceptions when the operator has a newer version of Java installed and uses SSH cipher options? (I.E. When SSH options are specified with the new version of Java exceptions are produced.)
>
> I do not get the exceptions with Java 1.60105 and with SSH having no options (I.E.: which uses the default cipher).
>
> I get the exceptions with Java 1.6033 and with SSH options which specify a non-default cipher.
>
>
> (1) When I start the application's manager, I get the exception:
>
> java.io.IOException
>
> (2) When I login into the manager of the application, I get the exception:
>
> Error authenticating java.lang.IllegalStateException: Session is closed
>
> (3) When I try to access a manager plugin of the application, I get exceptions such as:
>
> javax.xml.bind.UnmarshalException
> org.springframework.http.converter.HttpMessageNotReadableException
> org.springframework.oxm.UnmarshallingFailureException
> javax.xml.bind.UnmarshalException
> org.springframework.oxm.jaxb.Jaxb2Marshaller.convertJaxException
> com.google.gwt.user.server.rpc.UnexpectedException
>
> java.net.malformedURLException   //First exception seen under (3)
>
> (4) When I access another module in the same application, I get exceptions such as:
>
> org/apache/activeis/journal/active/JournalLockedException
> org.jasypt.exceptions.ENcryptionOperationNotPossibleException
>
> WebApplicationException
>
>
> Thank you,
> Frank Justine
>
> P.S.: I run the failed and successful application on the same operating systems. The only difference on the hardware is that on a sparc 4.2 it works but on sparc 4.3 we get exceptions.
>

Just use the version that works and seriously consider updating the 
program for a newer version of Java.

-- 

Knute Johnson

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.java.programmer

csiph-web