Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Changes to Cat Schemas Not Being Saved in 7.5.1

We upgraded to 7.5.1 a few weeks back and just noticed that when we edit a category schema the changes are not being saved. I've tried simple changes like reordering the elements, and more complicated changes like removing elements and adding new ones.

There are no error messages and there are no errors in the log files.

We've tested this using IE and Firefox browsers. All the indexing jobs seem to be running normally and we haven't seen any other problems.

The problem occurs with both repository administrators and community administrators.

Any idea what be causing this?
==============================

Did further testing. It's working fine on our dev box which is also 7.5.1, so it must be a configuration setting of some sort. We recently raised the ulimit and open files settings.

What other setting could cause this?

0 votes



7 answers

Permanent link
Hi,

It shouldn't be necessary but try clearing you browser's cache and cookies.

Also, what levels of Firefox and IE have you tried?

--
Rich Kulp
Rational Asset Manager developer

0 votes


Permanent link
hmmm.... assuming you clicked that Ok button top/bottom right corner (many time I personally forget).


Any differences in the deployment env. between the two (firewalls, web servers ...)?

0 votes


Permanent link
We upgraded to 7.5.1 a few weeks back and just noticed that when we edit a category schema the changes are not being saved. I've tried simple changes like reordering the elements, and more complicated changes like removing elements and adding new ones.

There are no error messages and there are no errors in the log files.

We've tested this using IE and Firefox browsers. All the indexing jobs seem to be running normally and we haven't seen any other problems.

The problem occurs with both repository administrators and community administrators.

Any idea what be causing this?
==============================


Did further testing. It's working fine on our dev box which is also 7.5.1, so it must be a configuration setting of some sort. We recently raised the ulimit and open files settings.

What other setting could cause this?


I did a lot of testing today. We found that the problems occur when we go to the server using HTTPS. Using the direct HTTP url does not have problems.

Then we tried using HTTPS but by-passing the proxy server. This worked fine as well.

So it seems that somehow the proxy server is introducing some kind of error. It affects saving changes to lifecycles and category schemas.

Testing now to see if there is some weird cache issue involved.

0 votes


Permanent link
The actual error message I get when trying to save a life cycle changes is:

Error: Unable to load https://w3-950.chs.ibm.com/ram/internal/lifecycles/ then the long GUID followed by /1.0/status:0

0 votes


Permanent link
Ensure that your proxy server is allowing PUTs. In the past there was a customer who had a front end server that was allowing GETs and POSTs, but not PUTs. Maybe you're seeing the same issue.

0 votes


Permanent link
Ensure that your proxy server is allowing PUTs. In the past there was a customer who had a front end server that was allowing GETs and POSTs, but not PUTs. Maybe you're seeing the same issue.


It is looking more like that. We've narrowed it down to a proxy server problem. If we bypass the proxy, all is good. Going to test, but we need a change window to reconfig the proxy, so weekend work it is.

I'll update this on Monday.

0 votes


Permanent link
Ensure that your proxy server is allowing PUTs. In the past there was a customer who had a front end server that was allowing GETs and POSTs, but not PUTs. Maybe you're seeing the same issue.


It is looking more like that. We've narrowed it down to a proxy server problem. If we bypass the proxy, all is good. Going to test, but we need a change window to reconfig the proxy, so weekend work it is.

I'll update this on Monday.

We confirmed that it is the proxy server causing the error. It is not configured to allow PUTs. I've opened a ticket with the hosting team to change this.

Thanks for the help!

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Feb 10 '12, 6:39 a.m.

Question was seen: 7,230 times

Last updated: Feb 10 '12, 6:39 a.m.

Confirmation Cancel Confirm