Bug database?

Can we get a bug database for Alchemy? I feel like all these emails are going to /dev/null.

Bhavin,
Not yet. This is being worked on currently.
Michael Girdley
BEA Systems
Learning WebLogic? Buy the book:
http://www.learnweblogic.com/
At Amazon:
http://www.amazon.com/exec/obidos/ASIN/0130911119/learnweblogic/103-6817548-
3834229
"Bhavin Raichura" <[email protected]> wrote in message
news:[email protected]..
Hi All,
Can I find any sort of Bug Database for Weblogic Server 6.1 ? Where I can
find Known Bugs / Problems ? Is there any sort of documentation available?
>
If there are newsgroups / links it will be very much help ful.
Thanks in advance.
Bhavin Raichura

Similar Messages

Bug Database for Sun ONE Studio 8

Is there an online bug database for the Sun ONE Studio 8 Compiler Collection, like there is for all of the Java related tools? I know we have product support, but I don't want to go through the overhead of 4 or 5 layers of people to report a minor problem I have found.
The minor problem is that the er_src utility will open files in the current working directory in preference to an absolute pathname specified on the command line. I used it from my home directory, giving it an executable name and source file name each about 5 levels deep in directories below my home -- with absolute paths. I was shocked to see the source from a six year old version of the file in the output. The 'truss' utility revealed that the source was being opened from my current directory -- ignoring the absolute path. This version of the file is one I have kept for reference, being the initial port of the program from a different language.
It appears that er_src attempts the unqualified file name first, then the absolute path if it fails to find the unqualified name.

The er_src man page does say the .er.rc files are processed, which implies that the setpath/addpath handling is done, at least to me. So the behavior reported is what I would have expected, but the manpage could, and should be more explicit.
The er_print man page is more specific, and does say that the compiled-in path is used only if the file is not found searching the current path mappings, which do contain "."
Can you tell me exactly what you'd like us to do? We did it this way because users complained about using the compiled in path, rather than finding the file in . or the experiments, where we explicitly tell people to copy files for archival purposes.
If you want us to change the behavior, please tell us EXACTLY what the desired behavior is. We could define a special symbol, like $EXPTS, to refer to the compiled-in path, $COMPPATH, perhaps, and then it could be put before or after . or $EXPTS.
Another issue is which name to use when. er_src has two referents for a path, one for "object", the thing whose source is being dumped, and a second for "item", specifying which item contained in the object should be dumped. For item, I believe we always only use the
base name, even if an absolute name is given. It is used to match against the names contained in object's symbol tables. All of this is complicated by NFS -- the present functionality is intended to behave gracefully when a file is examined on a machine other than the one on which
it was compiled.

Where can I find the bug database?

I was reading through the release notes for 2.4.16 and saw a reference to bug #16288 might have bearing on a problem I'm having. Would anyone know where I could find a detailed description of this bug? Also, if I find something that looks like a bug in the Berkeley DB XML, where would I send my report?

Hello,
Your problem is definitely [#16288] (see response on another thread). As Lauren said there is no publicly available bug database. Report them here and if you have a question about something from the changelog post that here as well, as you did.
Regards,
George

Javac bug database still being maintained?

After the Oracle acquisition, is the javac bug database still being maintained? I submitted a bug report on 04/20/2010 and received an e-mail response back confirming it was a new bug on 04/22/2010. The e-mail said it would be posted in the external database in "a day or two", but now 12 days later Bug ID [6946211|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6946211] is still not visible. I tried replying back to the e-mail but no response.
If anyone's interested, here is the sample code I submitted with the bug report.
public interface BaseType {
BaseType clone() throws CloneNotSupportedException;
public interface SubType<T extends BaseType & java.io.Closeable> extends BaseType {
}It should compile correctly but fails. It appears to be a generics bug.

I am rather certain that years ago (thus pre Oracle) it could take weeks before posted bugs showed up.
And presumably this was discussed in the Generics forum before posting it as a bug.

How to find my submitted bug report in Java bug database

I just submitted a bug report in Java bug database and it told me that the submission is successful without its bug ID and no email notification is received from Oracle.
And I cannot find the bug in bug database with the title I submitted.
The bug's product/category is Java Plug-in in JRE7
So how could I get the bug status? Will it be fixed and how is it going on?

I just submitted a bug report in Java bug database and it told me that the submission is successful without its bug ID and no email notification is received from Oracle.Last time I did that it also said it wouldn't appear straight away. They have to qualify bugs you know.
And I cannot find the bug in bug database with the title I submitted.How long ago?
So how could I get the bug status?Wait till it turns up?
Will it be fixed and how is it going on?How would anyone on this forum know?

I'm trying to make a Bug Database

Hi there,
I am trying to make my own bug database app using Objective-C(I will try and work out the Core Data part later - sticking to the code now).
So here goes.
I have created the code to add a column;
NSTableColumn *newColumn = [[NSTableColumn alloc] initWithIdentifier:@"identifier"];
[[newColumn headerCell] setStringValue:@"column name"];
[tableView addTableColumn:newColumn];
That works. But I have two questions;
1. How do I clear the table of all columns on startup?
2. How do I add contents to the table! I don't have a data source, I just want to add things when in the application.
Cheers,
Ricky.
P.S - I can't understand why there is a formatting issue in that code.

The tutorial is based on having a list of "VersionReleases"... and each VersionRelease can potentially have many CommitMessages... so the interface has the two table views. One table view shows you the list of all the VersionReleases and then when you've selected one of the VersionReleases the second table view shows you a list of all the CommitMessages associated with the selected VersionRelease. In addition, each CommitMessage has several pieces of data associated with it (the message, creationDate, and isCommitted attributes). And when you select one of the "CommitMessages" from the second table view then it's data items display in the remaining fields.
But based on your screen shot it appears that you want to create a list of Bugs to track... each individual bug item will have one notes field, one date founded and one platform (and also one bug name). But there doesn't appear to be a list of several items associated with each bug (like in the tutorial where there's a list of CommitMessages associated with each VersionRelease). So there doesn't appear to be any reason to split the information related to a single bug report into two different entities.
So (assuming I'm understanding your screen shot correctly) in essence you don't need the "VersionRelease" entity. Your interface looks like it could be handled with one entity similar to the "CommitMessage" entity from the tutorial. Sort of like you removed the "VersionMessage' table view from the left side of the tutorial window and then moved the "CommitMessage" table view from the top right of the window and instead placed it along the left side of the window where the first table view used to be... that gives you essentially what your screen shot displays and eliminates the need for the two entities.
Your "BugEntry" entity could contain a name, notes, date and platform. The table view on the left of your window would display a list of all the bug names (like the "CommitMessage" table view displays a list of commit messages in the tutorial), then depending on which one was selected the remaining fields would display the notes, date and platform of the selected bug.
Steve

Bug - Database Object Dependencies report and Interactive Reports

Hello,
I think I found a bug, perhaps that not the right word, in the Database Object Dependencies report. I don't think it's including problems in Interactive Report regions.
Regards,
Dan
http://danielmcghan.us
http://sourceforge.net/projects/tapigen

Scott,
Sorry, that was a useless bug report... ;)
What I was actually referring to was the little Parsing Errors report at the bottom of the page/report. I've come to rely on this quite a bit but I had an Interactive Report that was based in part on a table that was dropped and it was not displayed in the parsing errors. I believe the main report is working fine.
Regards,
Dan
http://danielmcghan.us
http://sourceforge.net/projects/tapigen

Small bug: Database configuration - Initialization parameters

Hi!
SQLDeveloper version: 3.2.20.09
View -> DBA -> Database configuration -> Initialization Parameters -> right click "Open" -> editor with "Parameter" and "Value" (inter alia) columns appears
Changing value for parameter "optimizer_features_enable" isn't working:
Example:
Parameter: optimizer_features_enable
Changing value from 11.2.0.1 to 9.2.0 -> commiting changes -> ORA-02017 error appears ("integer value required")
In "Messages - Log" window appears the following statement: ALTER SYSTEM SET optimizer_features_enable=9.2.0 COMMENT='' SCOPE=MEMORY
I think rather it should be: ALTER SYSTEM SET optimizer_features_enable='9.2.0' COMMENT='' SCOPE=MEMORY
It looks like a small bug.

Hi dz_r,
One workaround for this case is, when editing the data in the grid cell, to enclose the Oracle version in single quotes. After committing to apply the update (which works), the grid refresh strips away the single quotes, leaving the desired value displayed in the cell.
So this is, as you say, a small bug. Note that not all parameters of type String require single quotes, e. g., cursor_sharing=exact. Probably any String beginning with a numeric digit should be enclosed in quotes automatically.
I logged the following bug:
Bug 16733790 - UPDATING INITIALIZATION PARAMETER OF TYPE STRING FAILS IF BEGINS WITH A NUMERIC
Thanks for reporting this,
Gary
SQL Developer Team

4.0EA3 BUG: Database copy of a SDO_GEOMETRY column fails

I'm trying to copy a table that has a SDO_GEOMETRY column and it just fails:
When copying a error message appears:
Error occurred inserting data for TABLE: CLIENT_LOCATION. Batch 1 containing 500 rows failed.
ORA-00932: inconsistent datatypes: expected MDSYS.SDO_GEOMETRY got CHAR
The problem seems to be present also in sql developer 3.2.20.09: https://forums.oracle.com/message/11001171

It's still a bug. Limitation in the JDBC driver and user defined types is causing the issue.

How to vote, add to watch list or comment on a bug in the Java Bug Database

Sorry, could not fine a better place where to post this question.
I'm successfully logged-in but I cannot add a particular bug to my bug watch list, comment on it or vote for it (ok, here I may have already used all my 3 votes but I could also not find where to check this in my profile).
I am particular interested in this bug #4787931:
http://bugs.sun.com/view_bug.do?bug_id=4787931
Thanks for you support!

The Java bug DB was a Sun-time idea. Oracle hasn't put much effort into it since the merger:
- the performance has been horrible, see e.g. {thread:id=2173553}), and it is not clear whether they intend to keep maintaining it as such (open, vote-able,...)
- the "recently closed bugs" page (http://bugs.sun.com/recently_closed.do) seems out of date
- At the time of this writing, I cannot even find a link to log on it from the welcome page http://bugs.sun.com/ :(
Until Oracle openly declares that they will maintain this resource, I wouldn't put much hope nor effort into it...
Much luck,
J.
Edited by: jduprez on Sep 17, 2012 11:59 AM

BUG: Database Modeling in JDeveloper 11.1.2.1.0

Hello,
I'm defining a foreign key constraint in a database diagram in JDeveloper 11.1.2.1.0 with several columns, and within the Edit Constraint dialog in the Associations list the local columns names does not match the referenced columns names in the grid, although the associations are well defined internally. The same occurs in the Foreign Keys section of the Edit Table dialog, so I would like to know if there is any service pack or something that fixes this,
Thanks in advance.

Hi,
Shay is correct that what you are trying to do requires JDeveloper 12c.
Frank

Please explain the meaning of "Deferred" in JIRA bug database

Dear Adobe Team,
I have posted a few bugs recently and discovered this morning that they are now "Closed" with resolution "Deferred".
Some of these bugs are
https://bugs.adobe.com/jira/browse/FB-26396
https://bugs.adobe.com/jira/browse/FB-26317
https://bugs.adobe.com/jira/browse/FB-26081
Please explain how we should understand this decision.
My assumption is that bugs stay open until they are resolved in the next release.
Why are these bugs closed/deferred?
When are deferred bugs reopened?

Worth having a look at the 'Basic Workflow' to understand more of the statuses...
http://bugs.adobe.com/confluence/display/ADOBE/Basic+Workflow
I tend to find the start of the workflow more frustrating - unless you can attract a couple of votes or Adobe folks pick up the cause early, an issue can remain at 'Community' status for quite some time. By comparison getting to 'deferred' status is a good thing
Paul Evans
http://www.creative-cognition.co.uk/
http://blog.creacog.co.uk/

How to look at Coherence's bug database?

Hello,
I would like to give a look at COH-2767 but I do not know where to look at. Can anyone point me to the site where I can search for this Coherence's issue ??
Thank you,
Ugo.

Hi Ugo,
Unfortunately, it is not possible to have direct access to this system from outside of Oracle.
This problem refers to an issue that was fixed in 3.5.3 and 3.6. Let me know (directly by email) what you want to know about this problem. I will try to get you the information that you are looking for.
Thanks,
-PT

[Patch 정보] TRACKING BUG FOR CUMULATIVE MLR#6 ON TOP OF BPEL PM 10.1.3.3.1

최근에 출시된 BPEL PM 10.1.3.3.1의 통합패치입니다.
아래는 readme.txt에 포함된 patch list입니다.
# WARNING: Failure to carefully read and understand these requirements may
# result in your applying a patch that can cause your Oracle Server to
# malfunction, including interruption of service and/or loss of data.
# If you do not meet all of the following requirements, please log an
# iTAR, so that an Oracle Support Analyst may review your situation. The
# Oracle analyst will help you determine if this patch is suitable for you
# to apply to your system. We recommend that you avoid applying any
# temporary patch unless directed by an Oracle Support Analyst who has
# reviewed your system and determined that it is applicable.
# Requirements:
# - You must have located this patch via a Bug Database entry
# and have the exact symptoms described in the bug entry.
# - Your system configuration (Oracle Server version and patch
# level, OS Version) must exactly match those in the bug
# database entry - You must have NO OTHER PATCHES installed on
# your Oracle Server since the latest patch set (or base release
# x.y.z if you have no patch sets installed).
# - [Oracle 9.0.4.1 & above] You must have Perl 5.00503 (or later)
# installed under the ORACLE_HOME, or elsewhere within the host
# environment.
# Refer to the following link for details on Perl and OPatch:
# http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=189489.1
# If you do NOT meet these requirements, or are not certain that you meet
# these requirements, please log an iTAR requesting assistance with this
# patch and Support will make a determination about whether you should
# apply this patch.
# 10.1.3.3.1 Bundle Patch 6823628
# DATE: March 14, 2008
# Platform Patch for : Generic
# Product Version # : 10.1.3.3.1
# Product Patched : Oracle(R) SOA
# Bugs Fixed by 10.1.3.3.1 Initial patch 6492514 :
# Bug 5473225 - PATCH01GENESIS HOT UNABLE TO CATCH AN EXCEPTION DURING A
# TRANSFORM
# Bug 5699423 - PARTNERLINK PROPERTY THAT SET BPELXPROPERTY FUNCTION DOESN'T
# WORK
# Bug 5848272 - STATEFUL WEBSERVICES DEMO ON OTN DOES NOT WORK 10.1.3.1
# Bug 5872799 - ANT DEPLOY BPEL TEST FAILS/RUNS ON DEFAULT DOMAIN NOT
# SPECIFIED TARGET DOMAIN
# Bug 5883401 - ALLOW A WAY TO CREATE EMPTY NODES - AND USE FOR REQUIRED
# NODES
# Bug 5919412 - SAMPLE DEMO BPEL PROCESSES MIMESERVICE MIMEREQUESTER AXIS
# JAVA EXAMPLE ERROR
# Bug 5924483 - ESB SHOULD SUPPORT SOAP EDNPOINT LOCATION DYNAMIC UDDI LOOKUP
# Bug 5926809 - ORAPARSEESCAPEDXML XPATH EXPRESSION FAILED TO EXECUTE
# FOTY0001 TYPE ERROR
# Bug 5937320 - STRANGE BEHAVIOUR CALLING FROM BPEL TO BPEL GETTING
# NULLPOINTEREXCEPTION.
# Bug 5944641 - BPA BLUEPRINT NOT AVAIALBLE IN JDEVELOPER
# Bug 5945059 - JAVA.LANG.NULLPOINTEREXCEPTION SENDING EMAILS WITH PAYLOADS
# LARGER THAT 1MB
# Bug 5962677 - WS RESPONSE IS EMPTY SOAP BODY IN ONE-WAY CALL
# Bug 5963425 - WHEN THE OUTCOMES FOR A HT CHANGED & IMPORTED - UPDATE
# CONNECTION ROLES IN BPEL
# Bug 5964097 - AQ ADAPTER DEPLOYMENT CAUSES OPMN TO PERFORM A FORCEFUL
# SHUTDOWN IN SOA
# Bug 5971534 - CANNOT GRANT USER TASK VIEWS TO GROUPS, ONLY TO USERS.
# Bug 5989367 - REFER TO SR 6252219.993 BPEL 10.1.3 ONLY COPIES IN ASSIGN,
# IN 10.1.2 IT CREATES
# Bug 5989527 - ENHANCEMENT WARNING SHOULD BE GIVEN UPON UPLOAD IF BPEL
# PROCESS IS OPEN IN ARIS
# Bug 5997936 - ESB FAULT DOES NOT GET PROPAGATED TO BPEL
# Bug 6000575 - PERF NEED ESB PURGE SCRIPT TO PURGE BY DATE AND PROCESS
# Bug 6001796 - POSTING OF DATE RECEIVED FROM XML GATEWAY TO BPEL FAILED IN
# ESB
# Bug 6005407 - BPEL PROCESS DOESN'T PROPOGATE FAULT THROWN BY BPEL
# SUB-PROCESS
# Bug 6017846 - MIMETYPE OF EMAIL NOTIFICATION IS NOT SET THROUGH HUMAN TASK
# Bug 6027734 - DECISION SERVICE IMPORT - LOCATING DECISION SERVICE IN .DECS
# FILE IMPROPER
# Bug 6028985 - EXCEEDED MAXIMUM NUMBER OF SUBSCRIBERS FOR QUEUE
# ORAESB.ESB_CONTROL
# Bug 6041508 - CREATING/UPDATING DVM CAUSE EXCEPTION
# Bug 6053708 - FTP ADAPTER DOES NOT SUPPORT ENCRYPTED PASSWORD IN
# OC4J-RA.XML
# Bug 6054034 - INDEX4,INDEX5 AND INDEX6 CANNOT BE USED IN BPEL CONSOLE
# Bug 6068801 - BACKPORT OF BPEL ON WEBLOGIC - VERSION 10.1.3.3
# Bug 6070991 - HT EXPORT DOES NOT EXPORT PARAMETERS, ALLOW PARTICIPANTS TO
# INVITE OTHERS
# Bug 6071001 - WSIF HTTP BINDING NOT WORKING FROM ESB
# Bug 6073311 - STRESS SCOPE NOT FOUND ON CALLBACK - WRONG (DUPE)
# SUBSCRIPTION IN TABLE
# Bug 6081070 - JMS ADAPTER REJECTION HANDLER CREATE 0 BYTE FILES
# Bug 6083419 - DECISION SERVICE SCOPE NEED TO HAVE A SPECIAL INDICATOR
# Bug 6085799 - HUMAN TASK ADDED IN SCOPE IN JDEV IS NOT UPDATED TO BPA
# SERVER
# Bug 6085933 - EXPORT AND EXPLORE SHOULD USE USER LANGUAGE AND NOT ENGLISH
# ALWAYS
# Bug 6086281 - STRING INDEX OUT OF RANGE ERROR FOR COBOL COPYBOOK WITH PIC
# CLAUSE HAVING S
# Bug 6086453 - DOMAINS CREATED IN A CLUSTER GETS NOT PROPAGATED TO NEW OR
# EXISTING NODES
# Bug 6087484 - MULTIPLE HEADER SETTING CAUSES ESB EXCEPTION
# Bug 6087645 - ESB SHOULD ALLOW USER PICK RUNTIME PROTOCOL (HTTP/HTTPS)
# Bug 6110231 - TRANSLATION NOT BASED ON MQ CCSID CHARSET
# Bug 6120226 - BPEL IS NOT SETTING THE APPS CONTEXT CORRECTLY
# Bug 6120323 - COMPLETIONPERSISTPOLICY ON DOMAIN LEVEL HAS DISAPPEARED
# Bug 6125184 - ESB JMS SESSION ROLLBACK ORACLE.JMS.AQJMSEXCEPTION
# Bug 6127824 - [AIA2.0] CURRENT XREF IMPLEMENTATION IS MISSING REQUIRED
# INDEXES ON XREF SCHEMA
# Bug 6128247 - HTTPCONNECTOR POST() METHOD SHOULD RAISE EXCEPTION FOR ALL
# STATUS CODES EXCEPT 2
# Bug 6131159 - ENABLE USERS TO CHOOSE XSD WHEN CREATING A BPEL PROCESS FROM
# BLUE PRINT
# Bug 6132141 - PROCESS_DEFAULT TABLE STILL CONTAINS INFORMATION FROM
# UNDEPLOYED PROCESSES
# Bug 6133190 - ENABLING ESB CONSOLE HTTP/S IS MAKING THE CONSOLE TO COME UP
# BLANK.
# Bug 6139681 - BPEL WSDL LINK IN CLUSTERED RUNTIME POINTS TO A SINGLE NODE
# Bug 6141259 - BASICHEADERS NOT PUTTING WWW-AUTHENTICATE HEADERS FOR HTTP
# BINDING IN BPEL
# Bug 6148021 - BPEL NATIVE SCHEMA FOR COBOL COPYBOOK WITH IMPLIED DECIMAL
# LOSES DIGIT IN OUTPUT
# Bug 6149672 - XOR DATA - CONDITION EXPRESSION SPECIFICATION IS NOT
# INTUITIVE IN BPMN MODELS
# Bug 6152830 - LOSING CONDITIONAL EXPRESSIONS CREATED IN JDEV UPON MERGE
# Bug 6158128 - BASICHEADERS NOT PUTTING WWW-AUTHENTICATE HEADERS FOR HTTP
# BINDING
# Bug 6166991 - WHEN STARTING SOA SUITE,, PROCESSES FAIL DUE TO UNDEFINED
# WSDL
# Bug 6168226 - LOCATION-RESOLVER EXCEPTION THROWN IN OPMN LOGS
# Bug 6187883 - CHANGES FOR BPEL RELEASE ON JBOSS- VERSION 10.1.3.3
# Bug 6206148 - [AIA2.0] NEW FUNCTION REQUEST, XREFLOOKUPPOPULATEDCOLUMNS()
# Bug 6210481 - BPEL PROCESS WORKS INCORRECTLY WHEN AN ACTIVITY HAS MULTIPLE
# TRANSITIONCONDITION
# Bug 6240028 - WEBSERVICE THAT DOES NOT CHALLENGE FOR BASIC CREDENTIALS
# CANNOT BE INVOKED
# Bug 6257116 - MULTIPLE HEADER SETTING CAUSES ESB EXCEPTION
# Bug 6258925 - MESSAGE RECEIVED BY THE TARGET ENDPOINT VIA HTTP POST IS
# MISSING THE XML HEADER
# Bug 6259686 - TOO MANY UNNECESSARY WORKFLOW E-MAIL NOTIFICATIONS GENERATED
# Bug 6267726 - 10.1.3.3 ORACLE APPLICATIONS ADAPTER - NOT ABLE TO CAPTURE
# BUSINESS EVENT
# Bug 6272427 - WEBSPHERE BPEL FAILS FOR DATA RETRIEVAL OF SIZE 500+ KB
# Bug 6276995 - MERGE SCOPE NAME IS NOT UPDATED WHEN CHANGED IN THE SERVER
# Bug 6280570 - XPATH EXPRESSION ERROR IN MEDIATOR FOR ASSIGNING USER-DEFINED
# CONTEXT VALUES
# Bug 6282339 - RETRYCOUNT DOES NOT WORK PROPERLY
# Bug 6311039 - ONE RECORD IS INSERTED TO SYNC_STORE IF
# COMPLETIONPERSISTPOLICY SET TO FAULTED
# Bug 6311809 - [AIA2.0] NON-RETRYABLE ERRORS ARE NOT POSTED ON ESB_ERROR
# TOPIC
# Bug 6314784 - THE PRIORITY DEFINED IN THE BPA SUITE IS NOT TRANSFERRED TO
# THE JDEV CORRECTLY
# Bug 6314982 - THREADPOOL RACE CONDITION IN ADAPTER INITIALIZATION MESSAGES
# NOT PROCESSED
# Bug 6315104 - (SET)CLASSNAME MISSING IN TSENSOR JAXB OBJECTS
# Bug 6316554 - CONSUME FUNCTIONALITY OF JMS ADAPTER FOR BEA WEBLOGIC DOES
# NOT WORK
# Bug 6316950 - FILEADAPTER HARPER ENHANCEMENTS SYNC WRITE AND CHUNKED
# INTERACTION SPEC
# Bug 6317398 - THE ICON FOR COMPUTING DIFFERENCE IS MISSING IN JDEV REFRESH
# FROM SERVER DIALOG
# Bug 6320506 - IMPORT FAILS WHEN THERE IS AN UNNAMED CASE
# Bug 6321011 - CANNOT PROCESS 0 BYTE FILE USING FTP ADAPTER
# Bug 6325749 - TRACKING BUG FOR TRACKING ADDITIONAL CHANGES TO BUG #6032044
# Bug 6328584 - NEED A NEW XPATH EXPRESSION TO GET ATTACHMENT CONTENT VIA
# SOAP INVOKATION
# Bug 6333788 - COLLAPSING OF CONSECUTIVE ASSIGN TASKS BREAKS BAM SENSOR
# Bug 6335773 - BUILD.XML CONTAINS DO NOT EDIT .. - WHILE <CUSTOMIZE> TASK
# MUST BE IN <BPELC>
# Bug 6335805 - AQ ADAPTER OUTBOUND DOESN'T RECONNECT AFTER FAILURE
# Bug 6335822 - [AIA2.0] PSRPERFESB - RUNTIME DVM PERFORMANCE OVERHEAD IN ABS
# USE CASE
# Bug 6339126 - CHECKPOINT BPEL JAVA METHOD DOESN'T WORK IN BPEL 10.1.3.3
# Bug 6342899 - OUTLINECHANGE.XML NOT UPDATE WITH ACTIVITY FROM NEW BRANCH
# Bug 6343299 - ESB CONCRETE WSDL NAMESPACE SHOULD BE DIFFERENT FROM IMPORTED
# WSDL NAMESPACE
# Bug 6372741 - DEHYDRATION DATABASE KEEPS GROWING IN 10.1.3.3
# Bug 6401295 - NXSD SHOULD SUPPORT ESCAPING THE TERMINATED/QUOTED/SURROUNDED
# DELIMITERS
# Bug 6458691 - DIST DIRECTORY FOR 10.1.3.3.1 NEEDS UPDATE
# Bug 6461516 - BPEL CONSOLE CHANGES FOR DISPLAYING RELEASE 10.1.3.3.1
# Bug 6470742 - CHANGE THE VERSION NUMBER AND BUILD INFO IN ABOUT DIALOG IN
# ESB
# BUG ADDED IN MLR#1, 6671813 :
# Bug 6494921 - ORABPEL-02154 IF LONG DOMAIN AND SUITECASE NAMES IN USE
# BUGS ADDED IN MLR#2, 6671831 :
# Bug 6456519 - ERROR IN BPEL CONSOLE THREADS TAB:SERVLETEXCEPTION CANNOT GET
# DISPATCHER TRACE
# Bug 6354719 - WHICH JGROUP CONFIGURATION PARAMETER IMPACTS BPEL CLUSTER
# ACTIVITY
# Bug 6216169 - SCOPE NOT FOUND ERROR WHILE DELIVERING EXPIRATION MESSAGE OF
# ONALARM
# Bug 6395060 - ORA-01704 ON INSERTING A FAULTED INVOKE ACTIVITY_SENSOR
# Bug 6501312 - DEHYDRATION DATABASE KEEPS GROWING IN 10.1.3.3 #2
# Bug 6601020 - SEARCHBASE WHICH INCLUDES PARENTHESIS IN THE NAMES DOES NOT
# WORK
# Bug 6182023 - WAIT ACTIVITY FAILS TO CONTINUE IN CLUSTER WHEN PROCESSING
# NODE GOES DOWN
# BUGS ADDED IN MLR#3, 6723162 :
# Bug 6725374 - INSTANCE NOT FOUND IN DATASOURCE
# Bug 4964824 - TIMED OUT IF SET CORRELATIONSET INITIATE YES IN REPLY
# ACTIVITY
# Bug 6443218 - [AIA2.0]BPEL PROCESS THAT REPLIES A CAUGHT FAULT AND THEN
# RETHROWS IT IS STUCK
# Bug 6235180 - BPPEL XPATH FUNCTION XP20 CURRENT-DATETIME() IS RETURNING AN
# INCORRET TIME
# Bug 6011665 - BPEL RESTART CAUSES ORABPEL-08003 FAILED TO READ WSDL
# Bug 6731179 - INCREASED REQUESTS CAUSE OUTOFMEMORY ERRORS IN OC4J_SOA WHICH
# REQUIRES A RESTART
# Bug 6745591 - SYNC PROCESS <REPLY> FOLLOWED BY <THROW> CASE CAUSING
# OUTOFMEMORY ERRORS
# Bug 6396308 - UNABLE TO SEARCH FOR HUMAN TASK THAT INCLUDES TASK HISTORY
# FROM PREVIOUS TASK
# Bug 6455812 - DIRECT INVOCATION FROM ESB ROUTING SERVICE FAILS WHEN CALLED
# BPEL PROCESS
# Bug 6273370 - ESBLISTENERIMPL.ONFATALERROR GENERATING NPE ON CUSTOM ADAPTER
# Bug 6030243 - WORKFLOW NOTIFICATIONS FAILING WITHOUT BPELADMIN USER
# Bug 6473280 - INVOKING A .NET 3.0 SOAP SERVICE EXPOSED BY A ESB ENDPOINT
# GIVES A NPE
# BUGS ADDED IN MLR#4, 6748706 :
# Bug 6336442 - RESETTING ESB REPOSITORY DOES NOT CLEAR DB SLIDE REPOSITORY
# Bug 6316613 - MIDPROCESS ACTIVATION AGENT DOES NOT ACTIVATED FOR RETIRED
# BPEL PROCESS
# Bug 6368420 - SYSTEM IS NOT ASSIGNING TASK FOR REAPPROVAL AFTER REQUEST
# MORE INFO SUBMITTED
# Bug 6133670 - JDEV: UNABLE TO CREATE AN INTEGRATION SERVER CONNETION WHEN
# ESB IS ON HTTPS
# Bug 6681055 - TEXT ATTACHMENT CONTENT IS CORRUPTED
# Bug 6638648 - REQUEST HEADERS ARE NOT PASSED THROUGH TO THE OUTBOUND HEADER
# Bug 5521385 - [HA]PATCH01:ESB WILL LOSE TRACKING DATA WHEN JMS PROVIDER IS
# DOWN
# Bug 6759068 - WORKLIST APPLICATION PERFORMANCE DEGRADATION W/ SSL ENABLED
# FOR BPEL TO OVD
# BUGS ADDED IN MLR#5, 6782254 :
# Bug 6502310 - AUTOMATED RETRY ON FAILED INVOKE WITH CORRELATIONSET INIT
# FAILS
# Bug 6454795 - FAULT POLICY CHANGE NEEDS RESTART OF BPEL SERVER
# Bug 6732064 - FAILED TO READ WSDL ERROR ON THE CALLBACK ON RESTARTING BPEL
# OC4J CONTAINER
# Bug 6694313 - ZERO BYTE FILE WHEN REJECTEDMESSAGEHANDLERS FAILS
# Bug 6686528 - LINK IN APPLICATION.XML FILES CHANGED TO HARD LINKS WHEN MORE
# THAN 1 HT PRESENT
# Bug 6083024 - TEXT AND HTML DOC THAT RECEIVED AS ATTACHMENTS WERE EITHER
# BLANK OR GARBLED
# Bug 6638648 - REQUEST HEADERS ARE NOT PASSED THROUGH TO THE OUTBOUND HEADER
# Bug 6267726 - 10.1.3.3 ORACLE APPLICATIONS ADAPTER - NOT ABLE TO CAPTURE
# BUSINESS EVENT
# Bug 6774981 - NON-RETRYABLE ERRORS ARE NOT POSTED ON ESB_ERROR TOPIC
# Bug 6789177 - SFTP ADAPTER DOES NOT SUPPORT RENAMING FILES
# Bug 6809593 - BPEL UPGRADE TO 10.1.3.3.1 WITH ESB CALLS FAILS DUE TO
# CACHING OF PLNK - SERVICE
# BUGS ADDED IN MLR#6, 6823628 :
# Bug 6412909 - <BPELX:RENAME> DOES NOT ADD XMLNS DECLARATION AUTOMATICALLY
# Bug 6753116 - OUTPUT FROM HUMAN TASK IS NOT IS NOT CONSISTENT WITH
# SCHEMA
# ORDERING
# Bug 6832205 - BAD VERIFICATIONSERVICE PERFORMANCE IF LDAP SERVICE HAS HUGE
# DATA
# Bug 6189268 - CALLING BPEL PROCESS VIA SOAP FROM ESB FAILS WITH
# NAMENOTFOUNDEXCEPTION
# Bug 6834402 - JMS ADAPTER IMPROPERLY CASTS XAQUEUESESSION TO QUEUESESSION
# Bug 6073117 - TASK SERVICE DOESN'T RENDER THE TASK ACTIONS
# Bug 6054263 - REUSING SOAP WSDL IN RS CAUSES SOAP ACTION'S NS TO BE
# STRIPPED
# AWAY
# Bug 6489703 - ESB: NUMBER OF LISTENERS > 1 GIVES JMS EXCEPTION UNDER STRESS
# Bug 5679542 - FTP ADAPTER: COULD NOT PARSE TIME:
# JAVA.LANG.STRINGINDEXOUTOFBOUNDSEXCEPTION
# Bug 6770198 - AQ ACTIVATIONINSTANCES >1 DOESN'T WORK IN ESB
# Bug 6798779 - ESB ROUTING RULES CORRUPTED ON RE-REGISTERING WITH ROUTING
# ORDER
# IN WSDL CHANGED
# Bug 6617974 - BACKPORT REQUEST FOR MOVING FILES FUNCTION OF FTP ADAPTER
# Bug 6705707 - VALIDATION ON ESB CAN'T HANDLE NESTED SCHEMAS
# Bug 6414848 - FTP ADAPTER ARCHIVE FILENAME FOR BPEL IS BEING SCRAMBLED
# AFTER
# THE 10.1.3.3 UPGR
# Bug 5990764 - INFORMATION ARE LOST WHEN BPEL PROCESS IS POLLING FOR MAILS
# WITH
# ATTACHEMENTS
# Bug 6802070 - ORA-12899 SUBSCRIBER_ID/RES_SUBSCRIBER COLUMN SMALL FOR LONG
# DOMAIN AND PROCESS
# Bug 6753524 - WRONG SERVICE ENDPOINT OPEN WHEN TEST WEB SERVICE OF ESB
# Bug 6086434 - PROBLEM IN BPEL FILE ADAPTER WHILE READING A FIXED LENGTH
# FILE
# Bug 6823374 - BPEL 10.1.3.3.1 BAM SENSOR ACTION FAILS WITH BAM 11
# Bug 6819677 - HTTS STATUS 202 RETURNED INSTEAD OF SOAP FAULT
# Bug 6853301 - MQ ADAPTER REJECTED MESSAGES IS NOT REMOVED FROM THE RECOVERY
# QUEUE
# Bug 6847200 - 10.1.3.3.1 PATCH (#6748706) HAS STOPPED FTP ADAPTER POLLING
# IN
# SFTP MODE
# Bug 6895795 - AQ OUTBOUND DOESN'T WORK WITH MLR#6
업무에 참고하시기 바랍니다.

David,
You are right, theer are some changes incorporated in the latest MLR # 16 on the configurations files and on the dehydration store metrics(such as performance, fields,..).
However, I would not suggest to continue working on olite, even for Development/Test purposes as you might get stuck with strange errors...and the only solution would be to re-install SOA Suite if your olite gets corrupted. There might be ways to gets your olite back to position, but trust me..its not so simple.
Also, when you develop and stress test all your testcase scenarios in an TEST Adv installation, its simple to mimic the same in actual production box, as you exactly know its behavior.
So, go for a brand new SOA 10.1.3.4 MLR # 5 (or) 10.1.3.3.1 MLR # 16 SOA Suite Advanced installation with Oracle DB 10.2.0.3 as its dehydration store.
Hope this helps!
Cheers
Anirudh Pucha

Problem with JMenus that Persist - Is this a Java bug?

I am having a problem with JMenus that persist. By this I mean
that my drop down menus persist on the screen even after they have
been selected.
I've checked the Java bug database, and the following seems
to come closest to my problem:
Bug ID: 4235188
JPopupMenus and JMenus persist when their JFrame becomes visible
State: Closed, not a bug
http://developer.java.sun.com/developer/bugParade/bugs/4235188.html
This page says that the matter is closed and is not a bug. The
resolution of this matter printed at the bottom of the page
is completely abstruse to me and I would appreciate any
comments to understand what they are talking about.
The code at the end of my message illustrates my problem.
1. Why should paintComponent() make any difference to
Menu behavior?
2. Is this a bug?
3. What's the workaround if I have to paint() or repaint()?
Thanks
Tony Lin
// Example of Menu Persistence Problem
// Try running this with line 41, paintComponent(), and without line 41
// Menus behave normally if line 41 is commented out
// If line 41 exists, menus will persist after they have been selected
import java.awt.*;
import java.awt.event.*;
import javax.swing.*;
public class P2 extends JPanel {
JMenuItem[] mi;
public P2() {
JFrame thisFrame = new JFrame();
thisFrame.getContentPane().add(this);
JMenu menu = new JMenu("My Menu");
JMenuBar mb = new JMenuBar();
mi = new JMenuItem[4];
for (int i=0; i<mi.length; i++) {
mi[i] = new JMenuItem("Menu Item " + String.valueOf(i));
menu.add(mi);
mb.add(menu);
thisFrame.setJMenuBar(mb);
thisFrame.setSize(400,200);
thisFrame.setLocation(150,200);
thisFrame.addWindowListener(new WindowAdapter() {
public void windowClosing(WindowEvent we) {
System.exit(0);
thisFrame.setVisible(true);
public void paintComponent(Graphics g) {} //Affects menu behavior!
public static void main(String[] args) {
new P2();

Well, my understanding of the way painting works is that a component doesn't UNPAINT itself. Instead a message is sent to the component under the coordinates of the menu to REPAINT itself.
In your demo program the JFrame is the component under the JMenu. The paintComponent() method of JFrame is empty, so nothing gets repainted.
I added super.paintComponent(g); to the method and everything works fine.

Bug database?

Similar Messages

Maybe you are looking for