The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
Project and Portfolio Management Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

Upgraded 9.14 to 9.21 : Workbench stopped working

Highlighted
Arjun_K
Member

Upgraded 9.14 to 9.21 : Workbench stopped working

Hello,

We recently upgraded PPM from 9.14 to 9.20 (and 9.21 by applying SP1).
For the upgrade we did have JDK version 1.7.0_3 on the app server and set this as JAVA_HOME.

 

Soon after the upgrade when we try open the workbench on Windows and mac machines I get the below error.

 

The issue is persistent even if I clear java cache from client machine, clear work & tmp on the app server, recompile JSP and update HTML.

 

Any inputs on this would be of great help.

 

ERROR:
java.lang.NullPointerException
    at com.kintana.core.gui.LogonApplet.loadInstalledLanguages(LogonApplet.java:273)
    at com.kintana.core.gui.LogonApplet.init(LogonApplet.java:337)
    at com.kintana.core.gui.LogonApplet.main(LogonApplet.java:1135)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at com.sun.javaws.Launcher.executeApplication(Unknown Source)
    at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
    at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
    at com.sun.javaws.Launcher.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)

Warm Regards,
Mallikarjun.S
11 REPLIES
Arjun_K
Member

Re: Upgraded 9.14 to 9.21 : Workbench stopped working

Below is the detailed error message from Java Console on my windows client machine.

Java Web Start 10.25.2.16
Using JRE version 1.7.0_25-b16 Java HotSpot(TM) 64-Bit Server VM
User home directory = C:\Users\malikarjuns
----------------------------------------------------
c:   clear console window
f:   finalize objects on finalization queue
g:   garbage collect
h:   display this help message
m:   print memory usage
o:   trigger logging
p:   reload proxy configuration
q:   hide console
r:   reload policy configuration
s:   dump system and deployment properties
t:   dump thread list
v:   dump thread stack
0-5: set trace level to <n>
----------------------------------------------------
Missing Permissions manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/oracleapps.jar
Missing Codebase manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/oracleapps.jar
Missing Permissions manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/knta_client.jar
Missing Codebase manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/knta_client.jar
Missing Permissions manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/knta_client.jar
Missing Codebase manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/knta_client.jar
Missing Permissions manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/oracleapps.jar
Missing Codebase manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/oracleapps.jar
Missing Permissions manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/acme.jar
Missing Codebase manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/acme.jar
Missing Permissions manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/crypto.jar
Missing Codebase manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/crypto.jar
Missing Permissions manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/jakarta_regexp_1_3.jar
Missing Codebase manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/jakarta_regexp_1_3.jar
Missing Permissions manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/knta_jimi.jar
Missing Codebase manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/knta_jimi.jar
Missing Permissions manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/knta_log4j.jar
Missing Codebase manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/knta_log4j.jar
Missing Permissions manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/krmi.jar
Missing Codebase manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/krmi.jar
Missing Permissions manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/looks-2.0.4.jar
Missing Codebase manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/looks-2.0.4.jar
Missing Permissions manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/looks-2.0.4.jar
Missing Codebase manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/looks-2.0.4.jar
Missing Permissions manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/knta_log4j.jar
Missing Codebase manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/knta_log4j.jar
** Your URL: rmis://wpce16.hot.corp:1099/KintanaServer
Missing Permissions manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/krmi.jar
Missing Codebase manifest attribute for: http://wpce16.hot.corp:8080/itg/html/client/krmi.jar
com.kintana.rmi.RemoteException: Unable to connect; nested exception is
    javax.net.ssl.SSLException: Received fatal alert: internal_error
    at com.kintana.rmi.ObjectBroker.getRemoteRegistry(ObjectBroker.java:248)
    at com.kintana.rmi.ObjectBroker.lookup(ObjectBroker.java:459)
    at com.kintana.core.gui.LogonApplet.loadInstalledLanguages(LogonApplet.java:246)
    at com.kintana.core.gui.LogonApplet.init(LogonApplet.java:337)
    at com.kintana.core.gui.LogonApplet.main(LogonApplet.java:1135)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at com.sun.javaws.Launcher.executeApplication(Unknown Source)
    at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
    at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
    at com.sun.javaws.Launcher.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
log4j:WARN No appenders could be found for logger (com.kintana.core.server).
log4j:WARN Please initialize the log4j system properly.
#### Java Web Start Error:
#### null

Warm Regards,
Mallikarjun.S
Utkarsh_Mishra
Honored Contributor

Re: Upgraded 9.14 to 9.21 : Workbench stopped working

Install JRE 6.18 or above (but not 7) and then go to Control panel->Java->Java(tab)->View(button)-> and uncheck version 7 and select ONLY version 6 JRE.

 

 

here in our case client that have version 7, for them workbench is not opening or it is getting open in around 15-20 minutes.

 

On selecing JRE6 it is working fine. Try the above approach... it should work.

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
Arjun_K
Member

Re: Upgraded 9.14 to 9.21 : Workbench stopped working

Hi Utkarsh,

 

Thank you for the suggestion.

 

Unfortunately, we are enforced by the network security policies and have to use the latest version of java on Windows machines which is JDK1.7.0_25.

 

The policy does not apply for machines with Ubuntu & mac and we can have any version of java installed on these. Interestingly, having the older version of JDK resolved the issue on Ubuntu but not on Mac!


Do we have any other workarounds to make workbench work on Windows with JDK 1.7.0_25?

 

Warm Regards,
Mallikarjun.S
Utkarsh_Mishra
Honored Contributor

Re: Upgraded 9.14 to 9.21 : Workbench stopped working

Probably HP can provide work around for this..

 

But I had observed that on JDK version 7.x workbench will open (not on desktop one) in around 15-20 minutes... can give a try.

 

To open workbench JRE would be need... JDK won't be required.. can ask for JRE 6.18 or above...

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
ielito
Super Collector

Re: Upgraded 9.14 to 9.21 : Workbench stopped working

Hi Arjun / Hi Experts,

 

I have the same problem.... Anybody knows what's the solution ?!

 

Tks a loooot

Arjun_K
Member

Re: Upgraded 9.14 to 9.21 : Workbench stopped working

Hi ielito,

 

Unfortunately this issue is still not resolved for us!

Seems like a .jar file is missing which is related the the language pack but we are yet to receive a fix from HP on this.

 

 

 

Warm Regards,
Mallikarjun.S
Linda Hauck
Regular Collector

Re: Upgraded 9.14 to 9.21 : Workbench stopped working

We are going to upgrade from 9.14 to 9.21 next week.  According to the documentation, on the application server, JDK  must be JDK 1.7 update 4 or later.

 

I noticed that is not what you had.

 

Linda

 

 

Kaushal_Kishore
Acclaimed Contributor

Re: Upgraded 9.14 to 9.21 : Workbench stopped working

Hello Everyone,

 

Even we are facing the same issue when upgraded from 9.14 to 9.2. If anyone has successfully achieved the upgrade and resolved this null pointer exception, Please inform the steps to solve the issue.

 

Thanks in advance

 

Warm Regards

Kaushal

pepdwill
Senior Member

Re: Upgraded 9.14 to 9.21 : Workbench stopped working

Same problem here also. 

Kaushal_Kishore
Acclaimed Contributor

Re: Upgraded 9.14 to 9.21 : Workbench stopped working


pepdwill wrote:

Same problem here also. 


You can give it a try.

Download jar file from "http://mvnrepository.com/artifact/org.bouncycastle/bcprov-jdk16/1.46"

 

and replace the existing similar jdk15 jar file in path.

 

 

Regards

Kaushal

mallik_248
Super Collector

Re: Upgraded 9.14 to 9.21 : Workbench stopped working

Hello,

 

Has anyone notices the  jar files related to the Language Pack when you see and error opening the Workbench?

For us, the issue was with a language jar file which was from older version/out of support and HP provided us with a new version of the files.

 

Additionally, some of the jar files were having expired certificates. Due to the security settings that were enforced on the Java console in our organization, these jar files were stopped from loading because of the expired certificate date thus stopping Workbench from loading.

 

How did we identify the Certificate date on the jar files?

1. We used the standard linux command that lists the jar file certificate details.

2. We can also list the cer details from the Java console when opening the workbench. Make sure that you are opening java console (Show Console) when opening the workbench on the desktop.

 

Few of these issues are reported in here

 

http://docs.oracle.com/javase/tutorial/deployment/jar/secman.html 

 

//Add this to "OnDomLoad" event