|
Posted
over 13 years
ago
by
[email protected]
I have following mapping for severity field and same mapping is working properly in HPQC 9.2 BUT FOR HPQC 11 i am getting following error.
======================================================
Exception while creating Bug -11: Invoke of: Post
|
|
Posted
over 13 years
ago
by
[email protected]
Hi Shivendra,
Probably I need a more detailed explanation of the issue you are facing.
I was under the impression that you were saying that starting with HP ALM, you have to provide a value for the severity field and suggested that you change
|
|
Posted
over 13 years
ago
by
[email protected]
I am not able to understand your previous comment.
You are telling taht i have to set severity value in xml ?
|
|
Posted
over 13 years
ago
by
[email protected]
Hi Shivendra,
HP ALM 11 needs you to set severity explicitly, so you would need to include in your field mapping.
Best, Johannes
On Mar 27, 2012, at 7:56, "Shivendra Dwivedi" wrote:
> HI Johannes,
>
> If we can set severity
|
|
Posted
over 13 years
ago
by
[email protected]
HI Johannes,
If we can set severity value from XML in HPQC 9.2 Then we should be able to same in HPQC 11 also.
Please advise if this problem can be resolved.
Because without resolving this issue we can migrate to HPQC 11.
Please advise.
|
|
Posted
over 13 years
ago
by
[email protected]
Sorry for the inconvenience, CCF Cores are using Java Service wrapper to restart automatically in case of a crash and this one behaves differently than your appserver 8-(
Best, Johannes
-----Original Message-----
From: Mark 0Brien
|
|
Posted
over 13 years
ago
by
[email protected]
Thanks. Needed to add to cacerts keystore in JRE under JDK install and to the JRE outside the JDK install.
Mark
|
|
Posted
over 13 years
ago
by
[email protected]
The Web UI is using the JVM configured by TomCat. The core is using the keystore of the default JVM in your system.
Best, Johannes
-----Original Message-----
From: Mark 0Brien [mailto:[email protected]]
Sent: Thursday, March 22, 2012
|
|
Posted
over 13 years
ago
by
[email protected]
Okay, the URL was updated to https via eclipse. Next issue is a certificate issue. Is the core using a different java/key store that needs to be updated?
============================================
ERROR 2012-03-22 11:21:55,768
|
|
Posted
over 13 years
ago
by
[email protected]
Hi Mark,
Seems you ran into a situation where the Web UI already authenticates against the correct URL but the cores are still using the old URL.
The problem can be fixed easily if you connect using one of our rich clients (Eclipse or Windows)
|