$(function () { pageContext.i18n.modTalk = 'moderation talk'; pageContext.i18n.replyToComment = 'Reply'; pageContext.i18n.modTalkEmpty = 'moderation talk is empty'; pageContext.url.getModTalk = "/comments/%25ID%25/listModTalk.json"; pageContext.url.possibleCommentRecipients = "/comments/%ID%/possibleRecipients.json"; pageContext.url.commentEdit = '/comments/%25ID%25/edit.html'; pageContext.url.commentView = '/comments/%ID%/view.html'; pageContext.i18n.commentVisibility = { 'full': 'Viewable by all users', 'op': 'Viewable by the original poster', 'mod': 'Viewable by moderators', 'opAndMod': 'Viewable by moderators and the original poster', 'other': 'Advanced visibility', 'dialogTitle': 'Comment visibility', 'selectGroups': 'Visible to groups', 'selectOther': 'Other recipients', 'selectOriginalPoster': 'Original poster', 'selectModerators': 'Moderators', 'selectAssignees': 'Asked to answer users' }; pageContext.i18n.commentMenuLabels = { 'comment-edit': 'comments.menu.edit', 'comment-delete': 'comments.menu.delete', 'comment-convert': 'comments.menu.convert' };pageContext.i18n.answer= { bestAnswer: 'Best Answer', controlBar : { accept: 'Accept', unaccept: 'Unaccept', acceptCommand: 'Accept this answer as correct', cancelAcceptedCommand: 'Remove this answers accepted status' } }; window.croles = { u: false, op: false, m: false, og: false, as: false, ag: false, dc: false, doc: false, eo: false, ea: false }; tools.init({ q: { e: false, ew: false, eo: false, r: false, ro: false, d: false, dow: false, fv: false, c: false, co: false, p: false, tm: false , ms: false, mos: false }, n: { f: false, vf: false, vfo: false, vr: false, vro: false, c: false, co: false, vu: false, vd: false, w: false, wo: false, l: false }, c: { e: false, eo: false, d: false, dow: false, ta: false, tao: false, l: false }, a: { e: false, ew: false, eo: false, d: false, dow: false, a: false, aoq: false, ao: false, tc: false, tco: false, p: false, tm: false }, pc: croles }, { tc: true, nsc: true }); commandUtils.initializeLabels(); }); Skip to Content
0

Solman 7.2: Error while calling a servlet on Java Application Server

Jan 26, 2017 at 02:24 PM

1.2k

avatar image
Former Member

Hi !

I have been looking through a lot of notes about this error, but I can't solve it.

In Solman 7.2 "Infrastructure Preparation" 2.1 "Define HTTP Connectivity" I get this error message during "Test Connectivity" or "Save" "Error while calling a servlet on Java Application Server". Help give me the error message "SISE_BASIS009". I can't find that anywhere on th notes database. I have checked the user SM_INTERN_WS for authorization problems as described in some places.

But I still get this message. I have green on all steps before this one.

Anyone know anything about this?

// Claes

solman-error-1.jpg

solman-error-1.jpg (140.0 kB)
SAP Solution Manager
Answers Answers and Comments
10 |10000 characters needed characters left characters exceeded
▼ Viewable by all users
* Please Login or Register to Answer, Follow or Comment.

7 Answers

Sort by:
avatar image
Former Member Answered Jan 27, 2017 at 09:49 AM
1

Hey Robert,

i was getting the same error, but could resolve it by setting the Internal WS port as same as the external WS port.

You should also connect to your ABAP ICM. Standart port is 8000 when using http

edit: Also have a look on previous steps, as they showing Warnings.

SLD Connection should be fine and your LMDB syncronized and checked before doing the JAVA Connectivity Setup.

Regards

Philipp Neubert

Show 1 Share
10 |10000 characters needed characters left characters exceeded
▼ Viewable by all users
Former Member
Jul 06, 2017 at 03:08 PM

This solved it for me.

Thanks!

0
Comment
avatar image
Former Member Answered Jan 30, 2017 at 01:18 PM
0

Hi Philipp !

I have used port 5xxxx, isn't that used these days? For the external port it's 443, and for the Java message it's 8102 (SCS = 02).

SLD connection is green, and the synchronizing has been done.

// Claes using Roberts user

Share
10 |10000 characters needed characters left characters exceeded
▼ Viewable by all users
avatar image
Former Member Answered Jan 30, 2017 at 01:40 PM
0

Hi !.

Since this is version 7.2 ABAP and Java is two different instances. In my case ABAP is 31, and Java is 32. So should the internal ICM port be related to the ABAP or the Java system? It says configuration Java in the http configuration.

// Claes

Share
10 |10000 characters needed characters left characters exceeded
▼ Viewable by all users
avatar image
Subhashini Krishnan Answered May 02, 2017 at 07:25 PM
0

Hi Robert ,

Did you get the resolution for the issue. I am facing the same issue.

Can you please let me know if there is a way to solve the issue.

Thanks,

Subhashini.

Share
10 |10000 characters needed characters left characters exceeded
▼ Viewable by all users
avatar image
Yogesh Patel Answered
May 05, 2017 at 02:36 PM
0

In your screenshot I do not see ABAP Application server ICM???

Please look SAP note below

2319315 - Error "Logical port check failure" when testing connectivity for HTTPS ICM URL in step "Define Http Connectivity"

-Yogesh

Share
10 |10000 characters needed characters left characters exceeded
▼ Viewable by all users
avatar image
ABU SANDEEP Answered Jul 28, 2017 at 08:27 AM
0

Is this issue resolved ?

Share
10 |10000 characters needed characters left characters exceeded
▼ Viewable by all users
avatar image
Vijay Chandra Answered Oct 02, 2017 at 11:48 AM
0

I had the same error. The problem was that the SM_WS_INTERN user was not autocreated in the AS JAVA system. Even though the UME was configured to go to the ABAP Client where the user existed - i needed to create this user in AS JAVA for it to work. very strange indeed.

Share
10 |10000 characters needed characters left characters exceeded
▼ Viewable by all users