Routing maintenance problem in SAP ME 5.2.5.5

[Former Member]

Hi,

After upgrade to SAP ME 5.2.5.5 we have noticed the following with routing maintenance:

- When routing maintenance is started the first time a new Java VM is installed

- When trying to retrieve records for a previously created router the following error occurs:

java.lang.NumberFormatException: 1.0

at com.visiprise.globalization.impl.IcuNumberGlobalizationService.parse(IcuNumberGlobalizationService.java:288)

at com.visiprise.globalization.impl.IcuNumberGlobalizationService.parseAsBigDecimal(IcuNumberGlobalizationService.java:348)

at com.sap.me.productdefinition.client.vrouter2.VController.load300(VController.java:2604)

at com.sap.me.productdefinition.client.vrouter2.VController.load(VController.java:2347)

at com.sap.me.productdefinition.client.vrouter2.VController.display(VController.java:2291)

at com.sap.me.productdefinition.client.vrouter2.VRouter$7.run(VRouter.java:1564)

at java.awt.event.InvocationEvent.dispatch(Unknown Source)

at java.awt.EventQueue.dispatchEvent(Unknown Source)

at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.run(Unknown Source)

What can be the problem?

Br,

Johan

[Former Member]

I had the same problem. It was solved by changing the regional settings to English (US). It's probably caused by a wrong setting for the decimal point. At my computer the regional settings were set to Dutch, which uses the comma (,) for the decimal point.

Hans Otzen

MES Consultant

Atos Origin

[Former Member]

Hi Hans,

Thank you. You have hit the spot! Changing Regional language to English (US) works.

I have Windows 7 and tried keeping the Swedish language, but changing the decimal point to "." instead of "," does not

work so I am assuming there is something more than just the decimal point problem.

To SAP: This is a good workaround but not something we would like to keep forever. Any ideas to why this has

happened in 5.2.5.5?

Br,

Johan

[Former Member]

Hi again,

Two weeks since my last post and still no answer.. Do I have to log a ticket to get this solved?

Br,

Johan

[sergiy_katerinich]

Johan,

Please do so.

Regards,

Sergiy

[Former Member]

Hi,

Patch 11 of ME 5.2 SP05 fixed the problem.

Br,

Johan

[Former Member]

Hi,

Further information:

- The Java error occurs all the time a routing should be retrieved.

- New routing can be created but error still shows when routing should be retrieved.

Could there be any error in the Netweaver installation? I did an upgrade on this server

and during upgrade of SAP ME I chosed a new JVM installation JVM 5,1.058.

Br,

Johan

[alexander_teslyuk]

Hi Johan,

Have you tried to clean Java cache?

Regards,

Alex.

[Former Member]

Hi Alex,

Yes, I have tried deleting the temporary files from Control Panel - Java.

No Luck. The same error message appears.

Br,

Johan

[Former Member]

Hi again,

I would like to know if I have the correct versions of Netweaver and SAP ME.

Netweaver version is 7.11.06

SAP ME version is 5.2.5.5 counter 6.

Br,

Johan

[former_member182330]

Yes, NW SP and ME version are correct.

Konstantin

[Former Member]

Hi Konstantin,

Thank you for the information. Good to know that the versions are correct.

Am I the only one having these problems after upgrading?

Can you not reproduce the error?

Can I turn on some trace information to get more information about what is happening?

Br,

Johan

[former_member182330]

Hi Johan,

I've just installed 5.2.5.5 and everything works fine for me. Maybe you should try to run RM on different client computer to ckeck whether it's your environment issue or not. Also try to run it directly on the server.

Konstantin

[Former Member]

Hi,

The same problem appears on all our client computers as well as on the server.

Br,

Johan

[alexander_teslyuk]

Johan,

Could you please confirm that it worked fine before jave upgrade? What was the previous version?

Thank you,

Alex.

[Former Member]

Hi Alex,

Prior to upgrade from SAP ME 5.2.4.7 with NW 7.1 EHP1 SP05 to SAP ME 5.2.5.5 with NW 7.1 EHP1 SP06 it all worked fine.

We have the following scenarios at the moment:

Routing maintenance is working on:

SERVER: SAP ME 5.2.4.7, NW 7.1 EHP1 SP05, sapjvm_5.1.053

CLIENT: Oracle Java build 1.6.0_23-b05

Routing maintenance is not working on:

SERVER: SAP ME 5.2.5.5, NW 7.1 EHP1 SP06, sapjvm_5.1.058

CLIENT: Oracle Java build 1.6.0_23-b05

Br,

Johan

[Former Member]

Hi Konstantin,

You said that you have it working after 5.2.5.5 installation.

Have you tried deleting the Java-cache before running routing maintenance against the updated SAP ME server?

We can replicate this error now in two of our installation countries. Sweden and Estonia.

The scenario is:

1) Upgrade to NW 7.1 EHP1 SP06

2) Upgrade to SAP ME 5.2.5.5

3) When running routing maintenance against updated SAP ME server it works fine to retrieve records.

4) Delete Java Cache on client PC

5) When running routing maintenance new files are downloaded to client and retrieving of records results in

"java.lang.NumberFormatException: 1.0"

Checking in the Java Cache resources you can now see that the size of the folllowing files have changed

from previous SAP ME versions:

- common-api.jar from 5586 KB to 5891 KB

- common-globalization.jar from 124 KB to 128 KB

- service-core.jar from 257 KB to 267 KB

- VisualRouter2.jnlp from 2.2 KB to 2.5 KB

Obviously there is some changes done in routing maintenance that are causing this error.

Br,

Johan

[Former Member]

Hi,

Anyone from SAP have some feedback in this issue?

I provide some more trace messages if they might be of any help:

#2.0 #2011 03 12 11:52:09:303#+0100#Error#com.sap.me.trace#

##sap.com/me_{ear#1CC1DE01D044003F0000000100002DF8#1674450000000004#sap.com/me}ear#com.sap.me.trace.VM#Administrator#1##EC8FAAC64C8D11E0AB43000000198CD2#76c592034c9611e085d3000000198cd2#76c592034c9611e085d3000000198cd2#0#Thread[HTTP Worker [@576153008],5,Dedicated_Application_Thread]#Plain##

[EXCEPTION]

java.lang.NumberFormatException:

at com.visiprise.globalization.impl.IcuNumberGlobalizationService.parse(IcuNumberGlobalizationService.java:288)

at com.visiprise.globalization.impl.IcuNumberGlobalizationService.parseAsInteger(IcuNumberGlobalizationService.java:385)

at JEE_jsp_com_sap_me_administration_client_Admin_1674450_1297961116630_1299923326405._jspService(JEE_jsp_com_sap_me_administration_client_Admin_1674450_1297961116630_1299923326405.java:301)

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

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

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

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

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

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

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

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

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

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

at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

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

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:244)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)

at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)

at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327)

#

[former_member182330]

Hi Johan,

I have just tried to retrieve old router in RM after clearing cache and everything works fine. My NW is SP5 though. Will deploy SP6 and try again when I have more time.

Konstantin

[Former Member]

Hi Konstantin,

We have done our own tests on one of our Estonian application servers and only deployed NW SP05

together with SAP ME 5.2.5.5. With this configuration we still get the same error as before.

You said you cleared the cache before testing. Can you verify after you have started the routing maintenance

what your file sizes are in the java cache when it has been downloaded from 5.2.5.5? I stated in one of

my previous posting that we can get it to work with the files from 5.2.4.7 but not 5.2.5.5.

Br,

Johan