When clicking on sharedjmscon files or sharedjdbc files in TIBCO Business Events Studio, the error "Could not initialize class com.tibco.security.providers.CryptoVendorImpl_j2se" will be recorded in the error log.

When clicking on sharedjmscon files or sharedjdbc files in TIBCO Business Events Studio, the error "Could not initialize class com.tibco.security.providers.CryptoVendorImpl_j2se" will be recorded in the error log.

book

Article ID: KB0093323

calendar_today

Updated On:

Products Versions
TIBCO BusinessEvents Enterprise Edition -
Not Applicable -

Description

Description:
When clicking on sharedjmscon files or sharedjdbc files in TIBCO Business Events Studio, the error "Could not initialize class com.tibco.security.providers.CryptoVendorImpl_j2se" will be recorded in the log file. You will not be able to add any items to this object. The objects will not be editable and this may happen for other objects.

Symptoms:
Editing sharedjmscon files or sharedjdbc files in TIBCO Business Events Studio generates the error "Could not initialize class com.tibco.security.providers.CryptoVendorImpl_j2se".  You will not be able to add any items to this object.

Cause:
Unnecessary entry in the studio.ini file.

Issue/Introduction

When clicking on sharedjmscon files or sharedjdbc files in TIBCO Business Events Studio, the error "Could not initialize class com.tibco.security.providers.CryptoVendorImpl_j2se" will be recorded in the error log.

Resolution

Remove from TIBCO_HOME\be\5.1\studio\eclipse\studio.ini the entry for -Djava.ext.dirs. This entry is not needed.

Additional Information

See also KB 42190