Use this set of specific tips to help you troubleshoot
problems with bus members.
Error 500 when adding a new member to a
service integration bus.
When using the
WebSphere® Application Server administrative console to
add a server as
a new member of a service integration bus, you can receive an Error
500 message, with the additional message
"An error
occurred while processing request: /ibm/console/sIBusMemberCollection.do".
In addition, the SystemOut log contains a null pointer exception for
the stepsLayout.jsp; for example:
[9/21/04 14:35:18:282 CDT] 00000031 ServletWrappe E SRVE0068E: Could not invoke
the service() method on servlet /secure/layouts/stepsLayout.jsp. Exception thrown :
java.lang.NullPointerException
Note: This topic references one or more of the application
server log files. As a recommended alternative, you can configure
the server to use the High Performance Extensible Logging (HPEL) log
and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM® i systems. You can also use
HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access
all of your log and trace information using the LogViewer command-line
tool from your server profile bin directory. See the information
about using HPEL to troubleshoot applications for more information
on using HPEL.
This occurs in situations where your firewall product
is configured to remove the private header information (Referer) from
requests, because the WebSphere Application Server administrative
console requires the header to contain the referer.
To solve
this problem, you can either configure your firewall product to allow
the private header information (Referer) in requests or disable the
firewall product. For example, for information about configuring ZoneLabs
to allow the referer in requests, see the Private Header Information
(Referer) article at http://www.hotcomm.com/FAQ/FAQ_ZA.asp#referer.