deployment JMS-MQ driver crashes the PI repository...

Hi Expert,

we have scenario ECC--> XI --> MQ. So we deployed the JMS driver for MQ 6.0 to PI 7.0, the jar files are like stated in SAP Note : 747601. However after we deployed the new aii_af_jmsproviderlib.sda, sxmb_sfr can NOT start the page successfully, we got error page like :Unable to start component REPOSITORY since unable to execute StartupCodeEntry class com.sap.aii.ibrep.server.applcomp.StartupCodeEntry. Therefor the ID and IR are not accessible any more. Anyone knows how this happens? Anyone has experience to deploy JMS MQ driver to PI 7.0?

Thanks

Jayson

SAP Managed Tags:
SAP Process Integration

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (1)

Hi Jayson,

Did you try to restart your java stack?

Carlos

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Carlos

yes, we did restart the java stack. It didn't help.

The RWB and SLD are still working fine. Also since it crashes the ID and IR, we tried to deploy the original empty sda which comes with default installation, still same error occurs --> Can not access ID nor IR.

Any clue?

Jayson

Hi Jayson,

Have a look to this note: 928038

I think it could help you.

Regards,

Carlos

Hi Carlos,

the note provides some help hints, but it's not same problem as ours, we got com.sap.aii.ib.core.applcomp.StartupException: Unable to start component DIRECTORY since unable to execute StartupCodeEntry class com.sap.aii.ibdir.server.applcomp.StartupCodeEntry. Cause: com.sap.aii.ib.server.pvcadapt.migration.PvcMigrationException: java.lang.NullPointerException which is not the same exeption as the note talks about.

We are really stuck with this error.

Jayson

Hi Jayson,

Have you checkec if your JAVA engine is working properly? I mean, if you restart your system after importing .SDA maybe the system is not up. Check in MMC.

Can you acces to any Java Component?

For example:

http://host:port/index.html

http://host:port/rep/start/index.jsp

Hi Carlos

yes, the java engine should be working properly. We can start the http://host:port/index.html or http://host:port/sld or http://host:port/rwb. Just the repository and directory can not be started.

If I try http://host:server/dir/start/directory.jnlp, error message Startup of server application failed appears.

Jayson

Edited by: Jayson Xiao on Sep 16, 2008 4:27 PM

Guys,

Any success????

I am working on PI 7.1. I m also facing same issue..... when I tried to upgrade SAP-XICONS and SAP_XIPCK component from SP 4.0 to 7.0.

In my case the SLD, RWB and NWA is working... but I am not able to access

http://pidev:50000/dir/start/index.jsp.

The error says:

Internal error: Unable to start component DIRECTORY_SERVER. Specified StartupCodeEntry class "com.sap.aii.ibdir.server.applcomp.StartupCodeEntry" does not exist

deatiled error ************************

Stacktrace

Thrown:

com.sap.aii.ib.core.applcomp.StartupException: Internal error: Unable to start component DIRECTORY_SERVER. Specified StartupCodeEntry class "com.sap.aii.ibdir.server.applcomp.StartupCodeEntry" does not exist

at com.sap.aii.ib.core.applcomp.StartupException.newEntryClassNotFound(StartupException.java:78)

at com.sap.aii.ib.core.applcomp.ExplicitApplicationComponentImpl.startup(ExplicitApplicationComponentImpl.java:101)

at com.sap.aii.ib.core.applcomp.ExplicitApplicationComponents.startup(ExplicitApplicationComponents.java:438)

at com.sap.aii.ib.core.applcomp.ApplicationComponent.startup(ApplicationComponent.java:203)

at JEE_jsp_start_index_6931850_1232360340765_1232372432437._jspService(JEE_jsp_start_index_6931850_1232360340765_1232372432437.java:122)

at com.sap.engine.services.servlets_jsp.lib.jspruntime.JspBase.service(JspBase.java:102)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)

at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:433)

at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:240)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)

at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)