on 10-23-2006 10:44 AM
Subject,
Occurs on XI start (PI7 / NW04s SP6).
Meanwhile right above the error there is a message that "REPOSITORY" XI application is started successfully...
Error log:
=====================
Engine_Application_Thread[impl:3]_48##0#0#Error#1#com.sap.aii.ib.core.util.Abstr
actWebUtils#Plain###Internal error: Could not find SLD name for XI Application "DIRECTORY"
Thrown:
MESSAGE ID: com.sap.aii.ib.bom.landscape.rb_landscape.SLD_ASS_NOT_FOUND_EX
com.sap.aii.ib.bom.landscape.SLDElementNotFoundException: Unable to find an associated SLD element (source element: SAP_XIIntegrationRepository, [CreationClassN
ame, SAP_XIIntegrationRepository, string, Name, repository.<b><SID></b>.<b><HOST></b>, string], target element type: SAP_XIIntegrationDirectory)
at com.sap.aii.ib.server.sldquery.SLDQuery.getMyIntegrationDirectory(SLDQuery.java:193)
at com.sap.aii.ib.web.util.WebUtils.getMyIntegrationDirectory(WebUtils.java:179)
at com.sap.aii.ib.core.util.AbstractWebUtils.getSLDName(AbstractWebUtils.java:44)
...
VS
Hi,
1) Find out whether it is working as expected:
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1688 [original link is broken] [original link is broken]
/people/shabarish.vijayakumar/blog/2006/02/13/unable-to-open-iresrid-xipipi-71-updated-for-pi-71-support
/people/sravya.talanki2/blog/2006/02/21/verifying-xi-components
2) Refresh the Cache
a)Start transaction SXI_CACHE.
b)From the context menu XI Runtime Cache select Start Complete Cache Refresh.
If you still face issue try this .
Many actions require to access System Landscape Directory content from the Integration Builder. To optimize performance, this content is loaded into a cache so that the System Landscape Directory does not have to be accessed directly each time that System Landscape Directory content is required.
However, this cache is not automatically updated if changes are made to the content of the System Landscape Directory. For this reason that we delete the System Landscape Directory cache if changes have been made to content in the System Landscape Directory. The cache is then filled each time that the System Landscape Directory is accessed. If we log on to the Integration Builder after we have made a change in the SLD, we do not need to delete the SLD cache.
To clear the SLD cache, from the Integration Builder main menu, choose Environment ® Delete Cache for SLD Data.
Regards
Agasthuri Doss
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Andreas,
Thank you for the tip -- it's indeed was half a problem. I had to recreate integration_directory_hmi destination several times till authorization prompt disappears.
The second half was partly created SLD content -- XI server does not point to business system. Also fixed by note <a href="https://service.sap.com/sap/support/notes/764176">https://service.sap.com/sap/support/notes/<b>764176</b></a>.
Now I have some another problem:
#1.5#0017316968830055000000C8000018800004207AC1B1FC4B#1161611514506#/Applications/ExchangeInfrastructure/IntegrationServer#sap.com/com.sap.xi.services#com.sap.aii.ib.server.util.BasicJMSClient#PIDIRUSER#576##PC677_PI7_17447450#PISUPER#62b099d0629d11db928f001731696883#SAPEngine_Application_Thread[impl:3]_56##0#0#Error#1
#com.sap.aii.ib.server.util.BasicJMSClient#Plain###Exception during JMS startup for topic "SYNCHRONIZED_CACHE"
Thrown:
java.lang.ClassCastException: null
at com.sap.aii.ib.server.util.BasicJMSClient.initJmsResources(BasicJMSClient.java:111)
at com.sap.aii.ib.server.util.BasicJMSClient.init(BasicJMSClient.java:54)
at com.sap.aii.ib.server.util.BasicJMSClient.<init>(BasicJMSClient.java:48)
at com.sap.aii.ib.server.util.ClusterSyncedCache.<init>(ClusterSyncedCache.java:41)
at com.sap.aii.ib.server.sldquery.SLDCache.<clinit>(SLDCache.java:18)
at com.sap.aii.ib.server.sldaccess.SLDElementAccessor.<init>(SLDElementAccessor.java:32)
at com.sap.aii.ib.server.applcomp.StartupCodeEntry.startup(StartupCodeEntry.java:342)
at com.sap.aii.ib.core.applcomp.IStartupCodeEntry.startupIfNotAlreadyDone(IStartupCodeEntry.java:33)
at com.sap.aii.ibrun.server.applcomp.StartupCodeEntry.startup(StartupCodeEntry.java:55)
at com.sap.aii.ib.core.applcomp.IStartupCodeEntry.startupIfNotAlreadyDone(IStartupCodeEntry.java:33)
at com.sap.aii.ib.core.applcomp.ExplicitApplicationComponentImpl.startup(ExplicitApplicationComponentImpl.java:116)
at com.sap.aii.ib.core.applcomp.ExplicitApplicationComponents.startup(ExplicitApplicationComponents.java:383)
at com.sap.aii.ib.core.applcomp.ApplicationComponent.startup(ApplicationComponent.java:209)
at com.sap.aii.ib.server.hmi.HmiEnvironmentImpl.startupApplication(HmiEnvironmentImpl.java:226)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.initializeIfNotAlreadyDone(HmisServletImpl.java:329)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:439)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Anyone? Same exception for AIILogging JMS topic...
VS
Message was edited by: Valery Silaev
Closed without answer to latest question: JMS error. XI seems to auto-recover anyway after this error.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.