WARNING: workaround for critical clustering bug in OC4J

I found a workaround for the HTTP clustering bug described in my previous posting of August 16, 2001 "Urgent: serious HTTP clustering bug in OC4J?" (http://technet.oracle.com:89/ubb/Forum99/HTML/000261.html)
The workaround:
When adding the <cluster config/> tag in orion-web.xml specify and ID (numeric) with no more than 9 figures. The autogenerated ID is longer (14 figures on my test system)
and will cause the error.
Luciano
null

burricall wrote:
..Did you find a solution?See [this post|http://forums.sun.com/thread.jspa?threadID=5426321&messageID=11001580#11001580].

Similar Messages

Suggested workaround for list itemrenderer bug?

Can someone point me in the right direction for a workaround for the problem described as Flex bug 28191:
https://bugs.adobe.com/jira/browse/SDK-28191
Steps to reproduce:
1. Populate a Tree/List with data and provide a custom itemRenderer class factory.
2. Change the class factory and dataProvider at the same time.
3. List.createItemRenderer() will crash during since Factory is the key and it has been changed.
                delete freeItemRenderersByFactory[factory][renderer];
Actual Results:
Crash because the renderer can not be found since it does not exist on that factory dictionary since the class factory was changed and the lookup is using the new factory.
Expected Results:
Not crash.
Seems like a race condition, as sometimes during this process it skips that block of code but in other cases it falls into this block and fails.
I need to change the data provider and item renderer of a tree control at runtime. Is there one or more methods I should run to prevent this? As the bug notes state, this is an intermittent problem. The error occurs here:
if (factory == itemRenderer)
            if (freeItemRenderers && freeItemRenderers.length)
                renderer = freeItemRenderers.pop();
                delete freeItemRenderersByFactory[factory][renderer];

Thanks. Actually, I have been updating (not setting or changing) the tree's dataprovider, and then changing the classFactory like this:
processesXML = event.result as XML;
nodeTreeData.source = processesXML.children();
if (treeMultiSelect)
nodeTree.itemRenderer=new ClassFactory(renderers.TreeItemRendererV1);
nodeTree.allowMultipleSelection = true;
nodeTree.setStyle("selectionColor", "0xFFFFFF");
nodeTree.setStyle("disclosureOpenIcon", MinusIcon);
nodeTree.setStyle("disclosureClosedIcon", PlusIcon);
else
nodeTree.itemRenderer=new ClassFactory(mx.controls.treeClasses.TreeItemRenderer);
nodeTree.allowMultipleSelection = false;
nodeTree.setStyle("selectionColor", "0x7FCEFF");
nodeTree.setStyle("disclosureOpenIcon", OpenArrowIcon);
nodeTree.setStyle("disclosureClosedIcon", ClosedArrowIcon);
I had tried using validateNow after changing the ClassFactory before but did get the error again. I will try it again but update the data provider after. Since it's an intermittent error I'm finding it hard to know if a fix is really working.

Workaround for H264 playback bug on Android?

We have been doing extensive testing on H264 playback in both FLV and MP4 containers on Android AIR 3.2 / 3.3 (beta 3) for ICS. The process is documented here:
https://bugbase.adobe.com/index.cfm?event=bug&id=3164920
Summarized:
==========
Android AIR 3.2 / 3.3 (beta 3) H264 playback (both in FLV and MP4 container) on Android 4 is severely broken.
Video object (not StageVideo) with H264 content is:
1) not playing videos consistently ("NetStream.Play.Stop" is triggered to early) so the movie stops before the end is reached. This also happens on Android 3. Note! The bug is not in AIR 3.1.
2) not supporting filters (video frame is being scaled). Only Android 4 (ICS).
3) not supporting seeking when video is paused (video frame is not being updated). Only Android 4 (ICS).
Is there any known workarounds for these bugs?
Best,
Bjørn Rustberggard
Co-founder
WeVideo

Hi,
I just wanted to follow up. It looks from your bug comments like the issues you experienced in AIR 3.2 have been resolved AIR 3.3.
Are there any outstanding problems that you're seeing with regard to the issues you've described that we need to look into further for AIR 3.3?
Thanks!

Has anyone come up with new workarounds for Logic routing bugs?

There have been many threads regarding what seem to be a set of similar bugs. These inlude an audio intrument not sounding after a while, or a channel of automation not being read; and the problem is easily fixed by closing and re-opening the song. That would be a fine workaround except that some songs take a long time to load. I used to have these problems occasionally, but recently they have become so common as to be almost constant. That's bad news, but it also is potentially good news since it means that something in my system has an influence on these bugs. I haven't found a thread in which anyone isolated a factor that helps or hurts, but it's hard to imagine all the keywords for this set of problems, so maybe I missed an idea.
Also a new similar bug has started appearing in my system. When I add a bus send, once in a while either some or all audio channels will go silent, even though the graphic indicators indicate that they should be heard. The silent channels might or might not include the one with the new bus send. Remove the bus send and the sound comes back.
It seems as though changes in routing have binding problems.
Thanks for any ideas!

Absolutely no ideas on workarounds. I have the exact same issues.
Most of the time restarting the computer and session will cure them, but there have been projects where no matter what I do, the faders will not follow the automation data and EXS24 instruments cut out at the same exact time in the arrangement. This occurs even with as few as 6 EXS24 instruments open when on some projects I have up to about 85 open and 30 streaming at the same before I get a CoreAudio error.
Terrible...terrible.
Any word on whether or not 7.2 addresses this issues?

Apache POI Word support - workaround for a write bug

Hi all,
Just finished battling with the bugs in POI HWPF component. When searching forums, I found more questions than answers so I wanted to save others a significant effort until POI guys implement all the fixes.
Basically, the synopsis is, all the delete() methods are broken and replacing a string with a string of a different size corrupts the document. But insertAfter and insertBefore methods are mostly working.
I did not want to add a method to their class, because it will probably be overwritten. On the other hand, it is unknown when it will be fixed. Therefore, I had to go via reflection.
Here's the method, just attach it to your class and it's ready to use:
      * Replaces text in the paragraph by a specified new text.
      * @param r     A paragraph to replace.
      * @param newText     A new text.
      * @throws Exception     if anything goes wrong
     protected void setParagraphText(Paragraph r, String newText) throws Exception {
          int length = r.text().length() - 1;
          Class clRange = Range.class;
          Field fldText = clRange.getDeclaredField("_text");
          fldText.setAccessible(true);
          Field fldTextEnd = clRange.getDeclaredField("_textEnd");
          fldTextEnd.setAccessible(true);
          Field fldStart = clRange.getDeclaredField("_start");
          fldStart.setAccessible(true);
          List textPieces = (List)fldText.get(r);
          int _textEnd = fldTextEnd.getInt(r);
          TextPiece t = (TextPiece)textPieces.get(_textEnd - 1);
          StringBuffer sb = t.getStringBuffer();
          int offset = fldStart.getInt(r);
          int diff = newText.length() - length;
          if (diff <= 0) {
               // delete doesn't work properly yet, corrupting the documents.
               // Therefore a quick and ugly workaround is to pad the new text with spaces
               for (int i = 0; i < -diff; i++)
                    newText += " ";
               sb.replace(offset, offset + length, newText);
          } else {
               // when the new text is longer, the old one must be replaced
               // character by character, and the difference is added using
               // insertAfter method
               if (r.isInTable()) {
                    // more obstacles when working with tables though.
                    // Not only the regular insertAfter does not work,
                    // but also insertAfter called from a cell overruns cell delimiters.
                    // Needless to say, getTable(r) does not return the required table.
                    // Fortunately, there's a workaround
                    TableIterator ti = new TableIterator(range);
                    TableCell tc;
                    while (ti.hasNext()) {
                         Table tbl = ti.next();
                         for (int i = 0; i < tbl.numRows(); i++) {
                              TableRow tr = tbl.getRow(i);
                              for (int j = 0; j < tr.numCells(); j++) {
                                   tc = tr.getCell(j);
                                   if (tc.text().startsWith(sb.substring(offset, offset + length))) {
                                        sb.replace(offset, offset + length,
                                                  newText.substring(newText.length() - length));
                                        // only like this, otherwise cell delimiter will be run over
                                        tc.insertBefore(newText.substring(0, newText.length() - length));
                                        return;
                    sb.replace(offset, offset + length, newText.substring(0, length));
               } else {
                    sb.replace(offset, offset + length, newText.substring(0, length));
                    r.insertAfter(newText.substring(length));
     }

user8984775 wrote:
My requirement is I need to apply this formula for Entire column to achieve the need like
When user enters data in col2 (B) of greater than the number specified in col1 (A) and then show the ErrorBox.
I am able to get the formula working through code only for first cell as per below code... I want it to dynamically apply for the entire column. Well I'm certainly no expert on POI, but that looks like a very odd formula to me.
When you "pull" a formula down a column, Excel automatically changes the formula for each row, but because you've fixed both the column AND the row ($A$1), it'll be the same in all cases.
I don't know if POI allows that sort of "auto-generate" for formulas, but if so try something like $A1 instead; otherwise I suspect you'll need a different formula for each row.
Winston

Workaround for JColorChooser setPreviewPanel bug?

In 1.5:
JColorChooser's setPreviewPanel(null) doesn't work.
JColorChooser's setPreviewPanel(JPanel) removes the default preview panel but the new panel doesn't show up.
This bug was supposed to be resolved for 1.4.2, but according to http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6199676, it is still around. (there are many other related bug entries).
Any workaround, please?

Use the following code before you set the preview panel. For more info look at Bug ID 5029286
previewPanel.setSize(previewPanel.getPreferredSize());
previewPanel.setBorder(BorderFactory.createEmptyBorder(0,0,1,0));

Workaround for ]] XML export bug with schema?

Hi,
It is a known issue that the ]]> sequence will not export properly to XML. If you are using a DTD, there is an entity-based workaround that is described here:
http://forums.adobe.com/message/3774389
The question... is there a workaround when using schema? I'm unable to figure it out.
Thanks,
Russ

Hi Lynne,
Thanks again for the thoughts. And by the way, I sympathize with your implicit complaint about how these forums work with respect to revised messages. I am accustomed to hitting Ctrl+S all the time, probably from my FM experience Unfortunately, if you accidentally do it in the forum webpage, it submits the message. The system really needs to send revisions when they occur, because some people might just read the original email and think that's it.
Anyway, I'm intrigued by some things you said. #1 is possible but not preferable, as schema was specifically chosen for the ability to validate attribute values. My level of attribute-based conditionalization is fairly heavy and the schema makes sure that an invalid value cannot be entered. I seem to remember back in the outset that a DTD couldn't do the level of validation I like, but I don't remember the exact reasoning. Note that I frequently assign lots of values to an attribute, tokenized with whitespace as customary.
#3 is what I'm doing now, except with the fancy coverup tricks with spacing and back-end XSLT. I like your ideas.
#4 is actually pure genious and it is the route I think I will go. Something you didn't know yet is that I have a script that automatically formats an XML instance like an XML editor does, incidentally by wrapping <ph> elements and setting color-formatting attributes. Thanks to ExtendScript, I was able to use regular expressions to parse out all the individual components and then create a "map" for the subsequent wrapping/formatting activities. It is quite lovely and gives me the best looking XML instances in town, with a click. Bragging aside, it would be elementary to modify that script slightly to insert another <ph> element as you suggest. Elegant and simple, but I would have never thought of that myself.
Many thanks again,
Russ

Extensions like Ghostery, WOT or AdBlock stop working after two or three times. Restarting the webpage in a new tab the extensions will work again for several times and then stop again. Has anybody an explanation or a workaround for this bug in Safari 5?

Extensions like Ghostery, WOT or AdBlock stop working after two or three times. Restarting the webpage in a new tab the extensions will work again for several times and then stop again. Has anybody an explanation or a workaround for this bug in Safari 5?

Remove the extensions, redownload Safari, reload the extensions.
http://www.apple.com/safari/download/
And if you really want a better experience, use Firefox, tons more choices and possibilities there.
Firefox's "NoScript" will block the Trojan going around on websites. Best web security you can get.
https://addons.mozilla.org/en-US/firefox/addon/noscript/
Ghostery, Ad Block Plus and thousands of add-ons more have originated on Firefox.

Workaround for JSFL shape selection bug?

There seems to be a bug in the document selection reporting in JSFL in CS4 (haven't tested earlier versions). I submitted it as a bug to Adobe but I'd really like to find a workaround for it. I've included my bug report below. Has anyone else encountered this? If so, have you figured out a workaround? It's pretty annoying, making the tool I'm working on really difficult to manage.
******BUG******
After performing a publish preview, fl.getDocumentDOM().selection reports an incorrect selection of raw shapes.
Steps to reproduce bug:
1. Create a JSFL command with the following contents:
doc = fl.getDocumentDOM();
fl.trace("there are " + doc.selection.length + " items selected");
2. Start the authoring environment fresh, with a new document.
3. Draw several shapes on the stage, not touching each other, all in the same frame and layer.
4. Select one of those shapes but leave the others unselected.
5. Run the previously created JSFL command. It will send the following text to the output panel, as one would expect:
"there are 1 items selected"
6. Do a publish preview (either Flash or HTML).
7. When it comes up, close the preview window.
8. Deselect all and then select one of the shapes (again, keeping the others unselected).
9. Run the JSFL command again. This time, it will say that there are n items selected (where n is the number of shapes you drew in step 3). So if you drew three shapes, it will print out the following:
there are 3 items selected
Note that this result will be the same even if you go to a different document, do a publish preview on that document, then return to the original. It seems that simply doing a publish preview alters Flash's state to report the selection incorrectly.
Results: The JSFL command reports that all the shapes are selected, despite the fact that only one of them is. The only way I've found to get Flash back to its normal behavior is to restart the authoring environment.
Expected results: In the steps above, the JSFL command should always print out that there is one element selected. There's no reason that doing a publish preview should change that.

When selected all shapes in selection are treated as one. You can see it if you run this script with selected multiple shapes:
fl.trace( fl.getDocumentDOM().selection[0].contours.length );
It will output you twise bigger number then selected shapes (because each Shape has two contours - one clockwise, other counterclockwise).
Of course this. implementation is strange for me too. Thats how i found your post

Is there a workaround for the Safari "clickable hidden content" bug?

Hi,
I'm encountering a bug in Safari where hidden content (non-visible content hidden with the CSS attribute overflow:hidden) to be clickable. I did some googling and found other people who are having this same problem:
http://www.dmxzone.com/forum/go/?35908
http://archivist.incutio.com/viewlist/css-discuss/76660
http://lists.macosforge.org/pipermail/webkit-dev/2005-November/000496.html
But no one seems to have a workaround for this. The last post contains a reply by an Apple developer saying he checked in a bug fix for this, but his reply was posted two years ago and I'm still seeing the problem.
Does anyone know of a workaround for this? Hacks or kludges welcome.
Cheers,
-bri
Message was edited by: omega-

Hi
As Safari uses the WebKit structure, you may find an answer to your question at the FreeNode Network. You may also find help at the WebKit Open Source Project.

Disk Utilization for 0 C: D: E: is 99.61%, crossed warning (80) or critical

Hi,
I have windows 2008 R2 64 bit OS and database version is 11.1.0.7.0 64 bit ...
I got the below error via EM.
Target Name=ORSDEV.xxxdomain.com
Target Type=Host
Host=ORSDEV.xxxdomain.com
Metric=Disk Device Busy (%)
Metric Value=99.61
Disk Device=0 C: D: E:
Timestamp=Mar 21, 2012 7:41:58 PM SGT
Severity=Critical
Message=Disk Utilization for 0 C: D: E: is 99.61%, crossed warning (80) or critical (95) threshold.
Notification Rule Name=Host Availability and Critical States
Notification Rule Owner=SYSMAN
Notification Count=1
1.Can any one tell how to trace this warning and where to check for this alert ?
2.what is the meaning of Disk Utilization for 0 ?
3.How to identify the problem and resolve the issue in this case ?
Thanks & Regards,
Vikash (Junior DBA)

Hi Vikash,
This "Disk Utilization" metric actually points to hos busy is the disk device (in percentage) and not a percentage of disk capacity. As a matter of fact, in the 11.1. Database Control, it has been renamed to "Disk Device Busy(%)".
Regarding of the meaning of a disk busy, it is the percentage of time the physical disk is active. And it may no be a problem, as you can see at http://sunsite.uakom.sk/sunworldonline/swol-08-1999/swol-08-perf.html : "Complex systems can be 100 percent busy, but still have a lot of spare capacity".
On the other hand, to check how "full" a Disk is, the metric 'Filesystem Space Available (%)' can be used. This metric represents the percentage of free space available in the file system. Also, the Filesystem Size (MB) checks the total space (in megabytes) allocated in the file system.
Hope this helps.
Thanks,
Cris

[svn:fx-trunk] 10526: Temporary workaround for A+ bug SDK-23387.

Revision: 10526
Author:   [email protected]
Date:     2009-09-22 21:48:33 -0700 (Tue, 22 Sep 2009)
Log Message:
Temporary workaround for A+ bug SDK-23387.
The LinkNormalFormat, LinkHoverFormat, and LinkActiveFormat classes have been removed from FXG, and the FXG compiler was autogenerating static vars of these types (for linkage reasons?) that no longer compiled. I've commented out the offending lines in FXGCompiler.java, but we need a correct fix to cope with the fact that the way hyperlinks are formatted in FXG has changed.
Instead of formatting hyperlinks by writing
tag) but at least it can once again compile FXG as long as it doesn't involve styled hyperlinks.
QE notes: None
Doc notes: None
Bugs: SDK-23387
Reviewer: Carol
Tests run: ant checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23387
    http://bugs.adobe.com/jira/browse/SDK-23387
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/fxg/FXGCompiler.java

error dateField not selecion date 27/11/2002 ?
This is bug flex 3 ?
thanks

[svn] 4910: Implementing workaround for history manager rendering issue ( Firefox/Mac) caused by a long standing player bug.

Revision: 4910
Author: [email protected]
Date: 2009-02-10 11:51:58 -0800 (Tue, 10 Feb 2009)
Log Message:
Implementing workaround for history manager rendering issue (Firefox/Mac) caused by a long standing player bug.
Bugs: SDK-17020.
QE Notes: None
Doc Notes: None
Reviewer: Alex
Tests: DeepLinking
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-17020
Modified Paths:
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/managers/BrowserManagerImpl.as
flex/sdk/branches/3.x/templates/html-templates/client-side-detection-with-history/history /history.js
flex/sdk/branches/3.x/templates/html-templates/express-installation-with-history/history/ history.js
flex/sdk/branches/3.x/templates/html-templates/no-player-detection-with-history/history/h istory.js

Temp Workaround for Bug CSCun19415 - SPA 504G Transfer stopped by incoming calls

We have found that if you turn the CW Setting (User, Supplementary Services, CW Setting) to "No", then this provides a workaround for this issue. Obviously, there is a loss of functionality of the Call Waiting feature on all lines since this is a macro setting for the phone. However, until a bug fix for this issue (it is NOT an enhancement) comes out this does provide a good workaround. This also provides a workaround for the discussion on this support forum labeled "SPA 504G Transfer stopped by incoming calls".
Bob Conner

At least in our case this is not a valid workaround, for we need our operator (only one person) to know how many calls are waiting.
I agree completely: it is a bug, and not an enhancement. The second incoming call interrupts and aborts the transfer process associated to the previous call. It is amazing that so many firmware upgrades has been released since this behaviour was detected, and it is still here unresolved.
My only workaround is using an old Linksys SPA942 (which works as expected) or another brand's model.
My need: A multi-line SIP terminal for an operator to distribute the calls. And, as bizarre as it may sound, this cannot be addressed with CISCO (at least with 50x series).
Paul

[CC] Search for Workaround for old Bug: XML Validation fails

In Dreamweaver the validation of an XHTML document "as XML" fails.
Result:
An exception occurred! Type:NetAccessorException, Message:Could not open file: http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd[xml]
The bug seems to be very old:
http://forums.adobe.com/thread/874435
Do you know any workaround? Is there may be a plugin which can validate XML?
Thanks.

I appreciate your detailed answers, David. It's a pleasure to discuss with you
My own criterium, if a non-fixing is shameful or not, does not depend on the frequency of the usage of a function (by me or any other user).
It depends on the facts, that Adobe knows the bug since many years and that it is a bug in a very basic module - the search and replace module.
I take it as a proof of my assumption, that Adobe behaves arrogantly in many ways.
They just don't care about maintanance.
Thanks for filing the bug about "validate as xml".
I logged into my prerelease account (I took part some years ago). But it seems that I have no access to the bug database.
In my prerelease account there's no link to the bug database.
I agree with you, that concerns would have more chances to be read by developers when you talk about them in the pre release forums.
But my experiences with filing bugs are so disappointing, that I do not like to spend my time anymore for that.
While betatesting we had a "personal usability engineer" to talk to him. I talked a lot to him, constructively and polite. But in fact, he has no influence to the decisions which bugs will fixed and which not.
We can talk about the search and replace module in 10 years.
I'm sure it will look the same as today. It will have the same bugs as today. It will have the same functionality as today.
No improvement at all in such an important module.
That's my assumption based on the experience of the last 8 years.

WARNING: workaround for critical clustering bug in OC4J

Similar Messages

Maybe you are looking for