Java Communication Error - WAD

Question

Hi
I get a 'Java Communication Error - Error when opening RFC Connection' when I save or try to execute my web template.
Any help how to fix this problem...

Answer 1

Summary
Symptom
You are using SAP Netweaver 2004s Web Application Designer.
An operation that you want to perform is answered by a popup saying:
"Error during RFC communication (subrc = ...)", followed by the a certain
function name and in most cases an information that the portal or java
communication has failed. The message usually has the message class
RSBOLAP, numbers are 15, 17, 18.
This may occur during an operation like Save Template, Load Template,
Validate Template on Server, Load Reusable Web Item, Save Reusable Web
Item, Get Valuehelp, Execute Template in Portal, Publish Template to...,
Download of Metadata, and others.
All of these operations use functionality from the Java Server in some way
or the other, so they require a valid connection.
Function modules that may be mentioned in the error message (the list is
not complete) are:
RZX2_BTMP_SET, RZX2_BTMP_GET, RZX2_BITM_SET, RZX2_BITM_GET,
RSWAD_WEBPUB_CALL_SERVICE, RZX2_MIG3X70_DATA_GET, RSWAD_METADATA_GET,
RSWAD_TEMPLATE_SERVICES, RSWAD_PF_WEBPUBGETVH, ...
This note also applies if you for example change a Web Template, save it,
and the changes do not seem to be reflected when executing the Template
again.
More Terms
Setup, RSBOLAP015, RSBOLAP017, RSBOLABP18, RSBOLAP, 015, 017, 018, 15, 17,
18
Cause and Prerequisites
The Web Application Designer needs an active and valid Portal connection
for most of its operations. It can not be used without being connected to a
BI backend system (Netweaver BI Server).
Additionally, the connectivity Java->ABAP and ABAP->Java has to work for
the user currently logged on.
The usual communication flow is like this:
1. The frontend calls for a service on the Netweaver Server.
2. The call first meets the ABAP server.
3. The call is processed in the ABAP server as far as possible, and then
(if necessary) forwarded to the Java server.
4. The Java server processes the call as far as possible, and if
necessary calls another service functionality on the ABAP server.
5. The result is sent back on exactly the same way that it has arrived
25.01.2007 Page 2 of 3
SAP Note Number 916090
RFC-error messages in Web Application Designer 2004s
(in the most complex scenario: ABAP back to Java, then back to ABAP,
and then back to the frontend).
So if either the call from ABAP to Java fails, or the later call Java back
to ABAP does not work, an RFC-error occurs, leading to the error message in
the frontend.
Solution
This is not an error in the Web Application Designer.
When such an RFC-connection error occurs, the call from the Web Application
Designer frontend to the backend has not worked or not received a result.
In most cases, this means that the requested operation could not be
performed.
It may be that only the current call has failed, while the connectivity in
general is set up correctly. This may be for example, if the maximum number
of concurrent connections for the Portal is reached at the moment.
For that reason, please wait a few moments or minutes, and try again to see
whether the operation can be performed then.
In most cases, however, the connectivity is not properly configured, so the
call will not return a result also during the second and all following
tries.
In that case please ask your system administrator to set up the ABAP->JAVA
and JAVA->ABAP connectivity in a valid way (at least for your user...).
Please use note 888687 and 917950 (and their related notes) for the task.
If you do not succeed, please make sure to provide all the information
requested in these notes in your message. Otherwise an efficient message
processing is not possible, postponing the solution unnecessarily.
Header Data
Release Status: Released for Customer
Released on: 27.02.2006 11:11:38
Priority: Recommendations/additional info
Category: Consulting
Main Component BW-BEX-ET-WEB-AD WEB Application Designer (Publishing)
Additional Components:
BW-BEX Business Explorer
BW-BEX-ET Enduser Technology
BW-BEX-ET-WEB BEx Web ABAP Runtime
BW-BEX-ET-WEB-RT WEB Run Time
Valid Releases
25.01.2007 Page 3 of 3
SAP Note Number 916090
RFC-error messages in Web Application Designer 2004s
Software Component Release From
Release
To Release and
Subsequent
SAP_BW 70 700 700
SAP_BW 710 710 710
Related Notes
Number Short Text
953109 RSPOR_SETUP: "Option Unicode flag is not set (ABAP is Unicod
917950 SAP NetWeaver 2004s: Setting Up BEx Web
888687 BEx Web Java: Analysis of communication/logon problems
Attributes
Attribute Value
weitere Komponenten 0000000050
weitere Komponenten 0000030974
weitere Komponenten 0000032291
weitere Komponenten 0000034475