Bus members troubleshooting tips

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 or server cluster 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: 這個主題參照一或多個應用程式伺服器日誌檔。 此外,在分散式和 IBM® i 系統上,另外也建議您可以配置伺服器來使用「高效能可延伸記載 (HPEL)」日誌和追蹤基礎架構,而不使用 SystemOut.logSystemErr.log, trace.logactivity.log 檔案。HPEL 與原生 z/OS® 記載機能也可以一起使用。如果您使用 HPEL,則可以從伺服器設定檔 bin 目錄,利用 LogViewer 指令行工具來存取您所有的日誌和追蹤資訊。請參閱有關利用 HPEL 疑難排解應用程式的資訊,以取得更多使用 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.


指出主題類型的圖示 參照主題



時間戳記圖示 前次更新: July 9, 2016 11:12
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=rjj_prob0
檔名:rjj_prob0.html