cancel
Showing results for 
Search instead for 
Did you mean: 

SEVERE: Problem while creating JCA connection to MDM server Px.xx.name.com

Former Member
0 Kudos

Hi All,

I believe this error is not a new one. Your suggestions would be really helpful. when we try to load the solution, we are quite frequently getting this error.

SEVERE: Problem while creating JCA connection to MDM server 'Px.xx.name.com'

com.sap.mdm.net.ConnectionException: Can not resolve JCA connection

this error we are getting not always. but quite frequently in all environments. Since this is working sometimes, we couldn't be sure whether it is a coding issue. For the SAP standard iviews, we are getting this error on the portal screen and for custom application, we could see the screen blanks out.

Is that something we need to do from server or from the portal side?

This issue is affecting a lot in the production environment. your help will be really supportive.

Thanks,

SK

Kindly see the below full log trace file:

Oct 5, 2010 3:29:27 PM com.sap.mdm.logging.MdmLogger error

SEVERE: Problem while creating JCA connection to MDM server 'Px.xx.name.com'

com.sap.mdm.net.ConnectionException: Can not resolve JCA connection

at com.sap.mdm.internal.session.JcaConnectionUtil.getJcaConnection(JcaConnectionUtil.java:129)

at com.sap.mdm.internal.session.JcaConnectionUtil.getJcaConnectionAccessor(JcaConnectionUtil.java:65)

at com.sap.mdm.internal.session.JcaConnectionAccessor.reserveConnection(JcaConnectionAccessor.java:81)

at com.sap.mdm.internal.session.JcaConnectionAccessor.reserveConnection(JcaConnectionAccessor.java:69)

at com.sap.mdm.data.commands.AbstractRetrieveLimitedRecordsCommand.execute(AbstractRetrieveLimitedRecordsCommand.java:164)

at com.sap.mdm.data.commands.RetrieveLimitedRecordsCommand.execute(RetrieveLimitedRecordsCommand.java:173)

at com.sap.mdm.extension.data.commands.RetrieveLimitedRecordsExCommand.execute(RetrieveLimitedRecordsExCommand.java:42)

at com.sap.pct.mdm.appl.web.RecordHelper.performFlatSearch(RecordHelper.java:255)

at com.sap.pct.mdm.appl.web.LookupPickList.populate(LookupPickList.java:149)

at com.sap.pct.mdm.appl.masteriviews.PicklistSearch$PicklistSearchDynPage.displayPickList(PicklistSearch.java:430)

at com.sap.pct.mdm.appl.masteriviews.PicklistSearch$PicklistSearchDynPage.myDoProcessBeforeOutput(PicklistSearch.java:158)

at com.sap.pct.mdm.appl.masteriviews.MdmeBaseDynPage.doProcessBeforeOutput(MdmeBaseDynPage.java:197)

at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:127)

at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)

at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)

at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)

at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)

at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)

at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)

at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)

at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)

at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)

at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)

at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)

at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)

at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)

at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)

at java.security.AccessController.doPrivileged(Native Method)

at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)

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

at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)

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

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

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

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

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

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

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:104)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Caused by: com.sapportals.connector.connection.ConnectionFailedException: Connection Failed: Can not create SimpleConnection for MDM server 'Px.xx.name.com'. Original exception: 'Unable to create new connection.'

at com.sap.mdm.connector.connection.MdmConnectionFactory.getConnectionEx(MdmConnectionFactory.java:223)

at com.sap.mdm.internal.session.JcaConnectionUtil.getJcaConnection(JcaConnectionUtil.java:111)

... 45 more

Caused by: javax.resource.ResourceException: Can not create SimpleConnection for MDM server 'Px.xx.name.com'. Original exception: 'Unable to create new connection.'

at com.sap.mdm.connector.connection.MdmManagedConnectionFactory.createManagedConnection(MdmManagedConnectionFactory.java:181)

at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:338)

at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:262)

at com.sap.mdm.connector.connection.MdmConnectionFactory.getConnectionEx(MdmConnectionFactory.java:213)

... 46 more

Component: System.err

Location: sap.com/irj

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Air Lite,

If your MDM server is installed on Windows OS...

Then try doing this...

Make an entry of your J2EE server ip address into hostfile of your MDM server.

Let us know if this solves your problem...

Regards,

Shaailesh.

Former Member
0 Kudos

Thanks for supporting.

How to do this? an entry means, simply adding the java host address or how it should be?

you have any specific format.

we had a small test. and loaded system to 40 users... and we could see the same error and when the users are ramped down, no issues like this.

i also need to tell this, the number of MDM sessions in the console was too high. we use the connction pools..

would ttere be any possibility because of the number óf sessions high, MDM doesnt provide the connections?

please let m know your suggestions.

Thanks,

SK

Former Member
0 Kudos

Hello,

For example: if ip address is 172.25.10.36 and host name is eportal.company.com

Then you should append a line in mdm server's hostfile as follows...

172.25.10.36 eportal.company.com

You basis guy can help you in this case.

Regards,

Shaailesh.

Former Member
0 Kudos

Thanks! i will ask my basis colleague to try this out. will update the message

Former Member
0 Kudos

Hi,

I checked with basis guy, and end up in this question.

Does the IP address change often? then how come giving this address will help?

let me know your suggestions?

thanks,

SK

Former Member
0 Kudos

Hello,

Does the IP address change often?

- This depends on the owner of your NetWeaver server, when & why to change ip address.

How come giving this address will help?

- When Java API sends request to MDM server. MDM server will prepare a response and try to find out the NetWeaver server in our network domain. Depends on your network speed and complexity it may take longer to find NetWeaver server.

MDM Server OS first checks the entry in hostfile, and if not found it will search in your entire network.

From Java API point of view, there is some timeout for request being sent to MDM server.

If your MDM server doesn't respond within this timeout period, then you will get an error (which you are getting now).

We faced similar issue long back and host entry solved our problem.

Regards,

Shailesh Surve.

Former Member
0 Kudos

Hi,

Sorry, it seems we are usng the HP system. Is ther any alternatives.

And basis colleague also told, there are no parameters like ip address in the mds.ini files

Kindly help me out.

thanks,

SK

Former Member
0 Kudos

Hello SK,

In your first post in this thread you said...

For the SAP standard iviews, we are getting this error on the portal screen and for custom application, we could see the screen blanks out.

Also one of the exception message in your error is...

com.sapportals.connector.connection.ConnectionFailedException: Connection Failed: Can not create SimpleConnection for MDM server 'Px.xx.name.com'.

This error message says that your code is trying to use SimpleConnection for connecting to MDM server.

Try setting connection type in your custom code to "JCA Connection".

Regards,

Shaailesh.

Former Member
0 Kudos

Hi Shaailesh,

thanks for your commited help.

And this problem is coming in the stadard iviews. and when the problem comes, it has the other issues like shown above in the previous error.

This error is not coming continuous normally. when the user is loaded huge, this error is quite frequently.

sometimes this solves in a refresh and sometimes after some time this is ok...

i understood this is a weiered behavior, but this is the situation we have. whenever we have the load test with some high users we face this issue.

Thanks,

SK

Former Member
0 Kudos

Hi,

Please check this thread

Thanks,

Sudhanshu

Former Member
0 Kudos

Hi Sudhanshu,

thanks for responding.

I could see .. restarting is one solution. But also that cannot be permannent solution in the producton enviroment,

For ex we are facing that error 10-15 times in 2 hours ad a day around 20-30 times..

Would you suggest some alternatives to quickly check the settngs.

thanks,

SK

Former Member
0 Kudos

Hi,

Just try with restart .

If you still get same problem after restarting then we have to check some other solution.

I dont think you will get the problem after restarting the server.

Just try and revert back with your findings.

Thanks,

Sudhanshu

Former Member
0 Kudos

Hi ,

thanks for the suggestion, we have done the restart several times in this week.. still the problem is same.

my questions are as follows.

1. Why the MDM server/repositories gets disconnected or not usable, quite often? Any thing related to load or performance things?

2. And sometimes, a refresh makes the user to load the page again. by this , we couldnt conclude, the repository is not available? what could be the reason for not getting reached?

ur help and suggestion would be really helpful.

thanks,

SK