Skip to Main Content

Integration

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

General SSLEngine problem on one node of cluster

Peter551059Mar 13 2019 — edited May 3 2019

Hi,

I use Oracle SOA Suite 12.2.1.3 on Weblogic 12.2.1.3 cluster with 2 nodes.

I have OSB service which makes proxy to HTTPS service with basic authorization. I have deployed this OSB service to my cluster. Service worked well.

But now service works well only one node. On another node it returns OSB-380000: General runtime error: General SSLEngine problem.

What could be problem?

Thanks in advance.

Comments

Bayanna Kuruba

Hi,

Can you try once like below ,

select * from hr.emp

in the above hr is the schema name and emp table Name. I guess it will useful for you.

Regards,

Bayanna K.

ShayG

Hi,

I will clarify.

I have two schemas lets say one is HR and the second one is  DICTIONARIES.

There's a table in the HR schema called employees, this table has field JOB_TITLE_ID.

There's another table in the DICTIONARIES schema which called JOB_TITLES_DICTIONARY.

So my VO would be based on the EMPLOYEES table in the db it would be HR.EMPLOYEES.

JobtitleId attribute in that VO needs to get it's value from JOB_TITLES_DICTIONARY table from the DICTIONARIES schema.

I have two separate AM each of which points to one of the schemas HrApplicationModule and DictionariesApplicationModule which defined as shared module with session cache level.

On the page there's a table with rows from the HR schema when editing the JobTitle field the supposed to be a List Of Values opened from JobTitlesDictionary  VO in the DictionariesApplicationModule.

Each of the AM's point to a separate data source on the weblogic server.

When I'm running the page I get table or view doesn't exists.

I i define a synonym in the HR schema on JOB_TITLES_DICTIONARY table from DICTIONARIES  schema it will work, meaning the application doesn't accessing the table through the correct data source.

Ajay Taneja

I am sorry, but it make me more sense to replicate the table in same schema.

Any benefit you find to create a new connection to call a lov, let say you run this page so in one time you are creating two connection and would increase by number of users.

ShayG

I our organisation we have multiple systems that refer same dictionaries it's crucial that all systems have updated dictionaries all time.

So there's a centralized schema for all dictionaries and there's people devoted to managing those dictionaries.

So this is a given situation.

1 - 4

Post Details

Added on Mar 13 2019
16 comments
3,853 views