Wednesday 17 April 2013

OVR and 9.1.3 not being reliable, OVR stuck Loading....

I've had OVR running reliably for quite some time, but since applying 9.1.3 there have been issues.  I've been looking at many different aspects, generally technical to solve the problem.  Things like access.log for http problems.


weblogic.utils.NestedRuntimeException: Cannot parse POST parameters of request: '/jde/URLBuilderService.mafService'
        at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.mergePostParams(ServletRequestImpl.java:2144)
        at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.parseQueryParams(ServletRequestImpl.java:2024)
        at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.getQueryParams(ServletRequestImpl.java:1918)

And
RENDER_MAFLET=E1Menu&cmd=getNamesMenu&e1.state=maximized&e1.mode=view HTTP/1.1" 200 41
192.168.204.59 - - [16/Apr/2013:15:54:11 +1000] "POST /jde/URLBuilderService.mafService?e1.namespace=&e1.service=URLBuilderService&RENDER_MAFLET=E1Menu&e1.state=maximized&e1.mode=view HTTP/1.1" 200 166
192.168.204.59 - - [16/Apr/2013:15:54:11 +1000] "POST /jde/WatchlistManagerService.mafService?e1.namespace=&e1.service=WatchlistManagerService&RENDER_MAFLET=E1Menu&cmd=getNamesMenu&e1.state=maximized&e1.mode=view HTTP/1.1" 200 41
192.168.204.41 - - [16/Apr/2013:15:54:25 +1000] "GET /jde/e1pages/MYREXAMPLE_55/img/lines_straight.png HTTP/1.1" 200 148
192.168.204.59 - - [16/Apr/2013:15:54:26 +1000] "POST /jde/URLBuilderService.mafService?e1.namespace=&e1.service=URLBuilderService&RENDER_MAFLET=E1Menu&e1.state=maximized&e1.mode=view HTTP/1.1" 500 2987

As you can see from the above, 500 errors are not good.  These are not reported to the browser, because I think only the OVR menu is getting them.


So I get the above, it never changes....  So, time to fix it.

I could not get a handle on what was going wrong, apart from the HTTP 500 errors.  I redeployed the web tools release (well, regressed to 9.1.2.3 and it worked (OVR)).  Then I tried putting 9.1.3 on and that got it working again. This was good.  Although after the  next restart it all came back down.

I had another instance running and it worked all of the time, so it started to get very confusing.

Finally I bought myself around to looking at the JDE logs.  I found that there were errors relating to F952420 and this could be found in JM13315.  So I took the update.  I'm guessing this ESU is in relation to new functionality in 9.1.3 and OVR.


17 Apr 2013 06:37:00,115 [SEVERE]  - [GENERATOR]       JavaGen error code = METADATA_NOT_FOUND com.jdedwards.runtime.generator.JavaGenException: No Metadata for spec type table was found using the key : F952420
17 Apr 2013 06:37:00,115 [WARN  ]  - [RUNTIME]         No Metadata for spec type table was found using the key : F952420
17 Apr 2013 06:37:00,116 [WARN  ]  - [RUNTIME]         No Metadata for spec type table was found using the key : F952420 com.jdedwards.runtime.generator.JavaGenException: No Metadata for spec type table was found using the key : F952420
17 Apr 2013 06:37:00,116 [SEVERE]  - [BASE]            com.jdedwards.database.base.JDBException: [WEBJITI_ERROR] Demand generation failed for TABLE-F952420: null
As you can see.  Error is very simple.  JITI failed - well that means my package does not know about the spec.  Well, I know this is a new full package - so must be new specs for new functionality.

I ran the ASI for the ESU and also generated the F952420 to the Central Objects - DV910 data source.  Once this was done - over started working again.

I really need to pay more attention to MTRs and documentation.




1 comment:

Anonymous said...

Please tell me where you can download an update to solve this problem. I do not have such a table.

Extending JDE to generative AI