Error following upgrade from 3.0.1 to 3.0.1.2
Hi,
After the upgrade, the server starts OK, and I can log on to RRC, but the tomcat command window contains:
2012-04-02 16:59:01,118 RRC ERROR net.jazz.ajax.internal
.registry.Registry - Unable to translate "page.server" in bundle: "co
m.ibm.rdm.fronting.server.web"
Is this something I need to worry about?
Thanks!
After the upgrade, the server starts OK, and I can log on to RRC, but the tomcat command window contains:
2012-04-02 16:59:01,118 RRC ERROR net.jazz.ajax.internal
.registry.Registry - Unable to translate "page.server" in bundle: "co
m.ibm.rdm.fronting.server.web"
Is this something I need to worry about?
Thanks!
2 answers
Hi,
After the upgrade, the server starts OK, and I can log on to RRC, but the tomcat command window contains:
2012-04-02 16:59:01,118 RRC ERROR net.jazz.ajax.internal
.registry.Registry - Unable to translate "page.server" in bundle: "co
m.ibm.rdm.fronting.server.web"
Is this something I need to worry about?
Thanks!
Hi David,
No, you don't have to worry about this message. It's really just telling us that the national language translation for the string "page.server" could not be found.
Nonetheless, this issue has been fixed in 3.0.1.3 via work item 51621: Unable to translate "page.server" in bundle: "com.ibm.rdm.fronting.server.web"
Hi,
After the upgrade, the server starts OK, and I can log on to RRC, but the tomcat command window contains:
2012-04-02 16:59:01,118 RRC ERROR net.jazz.ajax.internal
.registry.Registry - Unable to translate "page.server" in bundle: "co
m.ibm.rdm.fronting.server.web"
Is this something I need to worry about?
Thanks!
Hi David,
No, you don't have to worry about this message. It's really just telling us that the national language translation for the string "page.server" could not be found.
Nonetheless, this issue has been fixed in 3.0.1.3 via work item 51621: Unable to translate "page.server" in bundle: "com.ibm.rdm.fronting.server.web"
Hi,
I am also getting this message in the out window and some times RRC is not displaying requirements that are already created. I tried this scenario by installing RRC 3.0.1.2 & after that with RRC 3.0.1.3 as well. Both cases, I am able to see the captured requirements in RRC in the first couple of login attempts. After that this problem starts. RRC does not display even the projects folders where requirements are stored.
Only difference I noticed here is, this error message gets displayed in case of 3.0.1.2 & no error message in case of 3.0.1.3. So, is this some other issue?
Now I am trying with RRC 3.0.1.1. Also, I am using a system with 3GB RAM (it is acting as both server & client). Also using Mozilla 3.6.28.
Your quick response will be appreciated, as I need to present a demo to my client tomorrow.
Entire error contents are as below (in 3.0.1.2)
***************
2012-04-17 23:43:06,187 RRC
.registry.Registry - Unable to translate "page.server" in bundle: "co
m.ibm.rdm.fronting.server.web"
2012-04-18 01:10:55,984 RRC ERROR ibm.team.dashboard.int
ernal.web.IFrameProxyServlet - POST https://localhost:9443/rm/_iframeproxy/http
s%253A%252F%252Flocalhost%253A9443%252Frm/multi-fetch
?size=512HEADER: host = localhost:9443
HEADER: user-agent = Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.28
) Gecko/20120306 Firefox/3.6.28 (.NET CLR 3.5.30729)
HEADER: accept = none
HEADER: accept-language = en-us,en;q=0.5
HEADER: accept-encoding = gzip,deflate
HEADER: accept-charset = ISO-8859-1,utf-8;q=0.7,*;q=0.7
HEADER: keep-alive = 115
HEADER: connection = keep-alive
HEADER: x-com-ibm-rdm-request-correlation-id = RRC_WEBUI_0.2650189761497369
HEADER: doorsrp-request-type = private
HEADER: net.jazz.jfs.owning-context = https://localhost:9443/jts/process/project
-areas/_EzprMIj7EeGRqp8Umd_rmQ
HEADER: content-type = text/plain; charset=UTF-8
HEADER: x-requested-with = XMLHttpRequest
HEADER: referer = https://localhost:9443/rm/_iframeproxy/https%253A%252F%252Floc
alhost%253A9443%252Frm/_ajax-modules/com.ibm.team.dashboard.web.iframe/com.ibm.r
dm.web.viewlet.ReqWithImplWorkItems?_proxyURL=%2Frm%2F_iframeproxy%2Fhttps%25253
A%25252F%25252Flocalhost%25253A9443%25252Frm
HEADER: content-length = 126
HEADER: cookie = JazzFormAuth=Form; X-Last-Modified-XSD=2012-04-18T06%3A04%3A21.
109Z;
***********
Thanks
Guru
Solution Architect.