More....! Aperture 3.0.2 bugs...??

Hi...
Since the Aperture 3.0.2.update I have experienced quite a few frustrating faults. Prior to this update... from what everyone else has experienced, I had no glitches at all.
1. As I posted elsewhere here, I had the Teal Green effect.. where a number of photo's were.. er very green..!
2. Then came the recent update, which gave me the HUD with no slider's...!!
3. Now I have no version numbers next to each project indicating how many versions there are...! When I hover over the project the version numbers appear.
You can look at these two screengrabs to see what I mean.... http://gallery.me.com/gm.g#100736
My MBP does not have any of these issues. I have done the repair/re-build library and delete the aperture.plist, this worked fine, got rid of the teal green effect, and gave me some sliders to work with...
Now I have this added plus of 'no numbers'... I can live without it... but hey it should be there..!!
I will submit feedback to Apple, but has anyone seen this...??
Thanks...
Gerry.........

Thanks Gerry for your help.
I had already tried repairing my library, but did not remove the aperture.plist. Done now and will see what next.
I have no problem with space on my HD. I have only my Aperture libraries on a Drobo with 4x1.5 GB. Plenty space free.
For the import, I always used the Destination as one of my existing Album within one existing Project. It always worked well before, even with version 2.0 with all my photos in the project and in the album at the same time.
Now, still my photos ONLY go in the project and I have to look for them and drag them in the selected album.
Weird!
Anyway, will see if Aperture does not crash again after some adjustments.
Cheers
Frederic

Similar Messages

More Aperture 3 bugs....Grrrr

The export to email options are totally messed up. You can select the size of the photo but aperture happily ignored that and uses it's previousm setting. You can see this by quiting aperture, going into preferences again and there is the old value. So for example, if I select medium JPEG it will still pass along a great big full size one across to mail, if that was the previous setting.
Now you can get it to remember the option but only if you edit the new size you have selected and pretend to change it and then save it. All fine and good you would think - a workaround. Well no, this leads to an even worse bug...
Try and add a new option. I tried JPEG and made it full size (by duplicating the existing one) and then moved the slider along to full quality. Well that results is a 12MB JPEG file - for a 12MP camera? ***?
I've never seen such a buggy application from Apple before. There is *no way* this application was properly tested. I'm getting a little tired of beta (or is that alpha?) testing this.

I can't agree with you more. I keep thinking it's me, but this is a horrible release:
1) Memory leaks like crazy.
2) Gratuitous pinwheel of death for no good reason.
3) Mouse scrollwheel support broken.
4) Your preset bug.

Aperture 2.1 / Photshop bug?

This is a weird one. When I select a RAW image and a version is created, I make my adjustments and send it to be edited in Photoshop (in this case, Elements 4). I do my touch-ups and save the file. The new version appears in the Aperture stack for that photo, but the image is only showing one of the previous layers I created when in Photoshop and not the final flattened version. I flatten the image before I save it, so there is no more selection or any other layer but the background. If I tell Aperture to load the version into Photoshop, it looks fine. But in Aperture's browser and preview windows, it looks like a layer I created from a selection and everything else (that wasn't selected) is black.
Is this a bug or am I doing something wrong?
Matt

Matt-
PS Elements is at version 6 now. First thing is to upgrade. Also, I don't know about PSE but with PSCS3 and OS 10.5.2 Adobe has said that problems exist that would not be resolved until OS 10.5.3 at the earliest. 10.5.3 is out now and at least some issues are fixed.
I recommend that you update to PSE v6 and OS 10.5.3.
Good luck!
-Allen Wicks

More Aperture/iPad syncing issues

Each time I create a new project or album in Aperture, I have trouble getting the images to the iPad when I sync. I sometimes need to sync several times until the images are recognized and imported to iPad. I do have the albums designated manually, rather than all, which means I have to sync and then sync again after I check the checkbox for the new album. I understand that, but sometimes I have to go back into Aperture to make sure the previews are updated. If I choose to update the previews for a project, Aperture will usually tell me that they're already up to date, but often they will not show up on the iPad, even after I check the appropriate box for the album in iTunes. Sometimes I get good results if I delete the previews and regenerate them in Aperture.
The second problem is the sort order. Even if I have "sort by filename" selected in Aperture, they do not show up in this order on the iPad--despite what the support article says about this. They appear to only show up in Date order. I've tried repeatedly resetting the sort order, but it does not change on the iPad. Sometimes I have to delete the album from the iPad, (uncheck the album in iTunes and sync again), then recheck it and sync yet another time. This does not always work, however.
It is very frustrating. The interface between Aperture and the iPad is very wonky. I often have to sync repeatedly, just to get the photos on the iPad and even then they're usually in the wrong order.
Aperture appears to have two types of previews: "previews" and "sharing previews," but "sharing previews" don't seem to appear in the documentation. I've noticed that, even when Aperture says the previews are up to date, when I exit the program, it will sometimes (but, maddeningly, not always), give the message, "updating sharing previews" before quitting. I cannot figure out how to force this, however. Sometimes opening and closing Aperture several times will cause it to do this, but I can't be sure.
iTunes seems to have its own process in which it "optimizes" images for importing to the iPad. Like Aperture's mysterious "sharing previews," "optimizing" does not show up in the iTunes documentation or help files.
This process either needs to be improved, or at least documented so users can understand how to avoid these problems.

1. Some people have reported slow syncing with anything but the iPad's own USB cable (e.g. using a US cable from an iPhone/iPod). Try different cables
2. More work - disable iTunes syncing completely, then re-enable a bit at a time, e.g. one movie at a time, one playlist at a time, one photo album at a time. There are periodic reports of syncing issues caused by a bit of media that's been corrupted, and this (tedious) approach allows you to identify where the problem might be.
3. If that fails, do a clean restore back to factory settings, then progressively re-enable syncing as above.
Hope this helps

Aperture ... Bug .... timezones and smart albums

Hello everyone,
i've just jumped into the mac world a week ago, just bought my first macbook ! Yeah !
I decided to give Aperture a try, and given i've played with it now for 2 days, if this bug I found is really there, NO WAY am I going to pay for such software !
I've been using Picasa on PC for the past couple years now.
Its handling my photo library extremely well: over 50gb of photos, 10 years worth of photos.
So after looking at all the Aperture videos on the apple site, I decided to give it a try to replace my picasa, since there is no picasa for my new mac.
The bug I found (and I'm a newbie !, 2 days of playing, struggling to import my pictures, and bam ... bug .... hummmm).
I tried importing only 1 folder in my library.
I'm french and this summer, went to USA for holiday. Western deserts and all.
So, I took my folder:
2008 08 09 - USA Grand West
And tried importing it.
It contains around 100 photos of the 1st 3 days of the trip.
My camera was set to French time, so at import I appreciated the "Change time thingy" and set it to Los Angeles time.
Did the import in a new project.
Great.
All pictures in the project. Exif Date updated to los angeles time. GREAT !
Now.
I want to have them show up on a day to day basis.
So, I created smart albums giving the date I wanted.
August 9 2008, August 10 2008 and August 11 2008.
It DOES NOT WORK ! BUGGGGGGGG
photos taken on the 3rd day, having correct EXIF date metadata, show 11/08/2008 for the date (correct), however they are not shown in the August 11 2008 album !
They are shown in the August 12 2008 album !
Reason !
The smart album is using the wrond date. The French one.
Since there is 11 hours difference.
Some late August 11 (Los Angeles time) pictures are pushed to August 12 (early morning French time).
Am I the only one with this bug ?
The only fix I found for now that works, is adding 3 rules to the smart albums:
- exif: day of the month = 11
- exif: month of the yar = 08
- exif: year = 2008
That works.
However there is NO WAY, i'm setting up 50gb worth of smart albums having to apply 3 specific rules to compensate for a bugged out calendar rule that does not work.
Any ideas ? fixes ?
Thanks
Regards
Tim

Hum, i'm not sure I understand what is going on, or what you are describing.
you say: "... Aperture is correct in it's assertion the image was taken on 12th"
I dont understand.
When i've done the import, and look at that pictures metadata, the date/time is corrected. It shows up as 15:42 20080811 (youre writting).
So if the metadata is correct, I really dont understand how the computers time and timezone has any effect on the smart albums ... could you explain ?
Unless what you are suggesting, is that the smart album date is applied to the computers time zone, and thus when searching for the files, it automatically does a conversion of the time of the picture to fit the computers timezone => thus my 15:42 20080811 set to Los Angeles time zone, is researched using a French timezone and thus found on 00:42 20080812 ?
Wow, if so, this would be a stretch !
And if this is the answer, I do not understand the "feature" to import using a different time zone, and not be able to search according to it ?
There is effectively no point?
In respect to the workaround you describe. Its effectively what I did, I sorted using 3 criterias: exif day of the month = 11, month of the year = 08, year = 2008. And for some reason that works !
Would there be another workaround? Instead of using the TimeZone panel, import them untouched, and doing a batch Time change on the pictures once imported and leaving them at the same Paris timezone, but compensating for 9 hours, effectively, bringing them to 15:42 Paris time, instead of Los Angeles time ?
If my memory is correct when having played with this, the batch time modification, did not compensate the days: Effectively, clicking 9 times on the down arrow when showing 00:42 12th did not change the 12th into an 11th ...

Aperture 2.1 crop bug? Feature?

I'm going nuts with something that is either a bug or a really annoying feature.
When trying to crop an image, I may select the 8 x 10 aspect ratio and draw a crop frame on the image. However, if I try to select of the corner anchors for the first time to resize it and move it at all, the aspect ratio of the crop immediately jumps to the image's current aspect ratio and the crop heads-up display now reads "Custom."
Am I doing something wrong? Is this a bug or is this somehow supposed to be how it works? Can't find anything in the manual on it suggesting it is supposed to do this.
Thanks.
Matt

Was doing a search for something else and stumbled across your Crop issue.
I am having the same issue. Another issue I get quite often is a change in the Width and Height boxes. If I choose 3x4 and drag an anchor point, the size changes to 128x85 or some other random numbers, (not same aspect ratio and is this inches or pixels?). So I go and change it back. This happens with all sizes (2x3, 4x5, etc.).
Anyway, sorry I can't help you, I just wanted to let you know that you are not the only one out there with this issue. I was hoping that there was an answer to this. Alas no, just a, "mine works fine", in your face answer.
Also, my files are not on a network drive or firewire or USB. I back up to an external drive but I put my library on an internal drive. I have also reinstalled Aperture to see if this might fix things. Good Luck,
Narvon

Aperture 2 - Possible UI bug?

G'day all,
I've been just being enjoying my first couple of days of Aperture 2. Fantastic, really enjoy using this version (keep it up Joe & team!)
I think I may have stumbled into a UI bug though. When I cycle through the viewer mode until the filmstrip disapears and the selected image is displayed at it's largest, I can't use the cursor keys or the arrows under the view to move to the next image.
Do you think it's a bug or is this intentional?
Cheers,
Dean
p.s. I'm looking for the Aperture feedbank link to send as feedback.

Is it a matter of what "window" has focus? (...which can be hard to tell) Try clicking the cursor once in the viewer then using the arrows? Does that work?
One way you can get into what you are seeing: If you click in a field in the metadata tab, then try and use the arrow key, its the metadata tab that is getting the keystroke, not the viewer, so the image doesn't change. You can see how it can happen, if you click there, the switch with a click to the adjustments tab, then adjust, then use the arrow key, you get nothing. If this is what you are seeing, then no need to quit the app, just click the window first with the cursor.

Vault does not work any more Aperture 2.1.1

Hi,
I just experienced that the vault function does not work anymore for me. When I click on the icon to show the vaults I created, nothing happens and Aperture seems to hang for some time. Sometimes it finally comes back and I can quite Aperture normally. Sometime I just need to force exit.
I switched to a different library, where no vaults have been created and when I tried to create one by opeing the vault area first, I got the same effect. When I select directly "create vault", it creates the file, but it does not put any content in.
I'm using Aperture 2.1.1 and MacOS 10.5.4.
Any hints ?

I had a similar problem. A portable Maxtor USB drive worked fine as a vault till this am, then message that there is not enough space. Get Info tells me about 54 GB available, and my entire Aperture Library is only 54 GB. Up till today it did incremental backups just fine.
I added a firewire drive and it seemed to work as a second vault, except while Get Info for the drive says it has a 50 GB Aperture library now, the Vault window in Aperture says this vault is backed up but it only used up 3 GB of the drive. The second widow for the original drive shows the expected amount used, ie about 50 GB.
So if I run Get Info on the firewire drive, it tells me I have a 50 GB Aperture library, but the small vault window in Aperture says only 3 GB.
I was going to reformat the original USB drive and re-try it, but this last information is coflicting, Any ideas on how to proceed?
Don

More Aperture improvements

This article http://www.appleinsider.com/article.php?id=1752 says that the next OSX update, 10.4.7, will have help for Aperture users.
Mark

This article http://www.appleinsider.com/article.php?id=1752 says that the next OSX update, 10.4.7, will have help for Aperture users.
Mark

More than 8 Cores crash (BUG REPORT)

My setup:
Hello guys, I'd like to report a bug with the Flash Media Live Encoder 3.1 specifically when handling systems of greater than 8 reported cores. If you select either VP6 or H.264 and have a framerate over 25 FPS, any time you attempt to change the Output Size the encoder will crash when you begin the broadcast (click Start).
If you match the input size to the output size FMLE will be stable. This effects both the command line and GUI version of FMLE 3.1. Systems specs and feeds are below:
CPU: Intel 6-Core i7-980 Gulftown 3.3GHz (12 cores with HT)
OS: Windows 7 Ultimate x64
Feeds tested were: 1920x1080 and a different resolution to convert to.
If someone from the adobe team could take a look at this I'd appreciate it. I have remote access if needed.

Thanks XmeF. This bug is already known, and has been fixed for the coming release, and is currently in pre-release mode.

More FB 4.5 BlazeDS bugs

For FB 4.5 Plugin Mac Cocoa 32 bit:
1. I am having trouble deleting and adding BlazeDS services from the Flash Builder perspective.
2. Re-adding a service now forces me to create an additional valueObject instead of re-using the
    one I already created with another service. This is the first time I've seen this behavior since
    until now the tool was smart enough to reuse the existing VO.
3. BlazeDS pops open a dialog box 'The following data types are already present or have
    conflicting properties on your project. Please rename the types or '<serviceName> will be
    prefixed to the existing name". The only option on the dialog box is an 'OK' button. When I
    click on the OK button, the service is created (versus giving me the ability to rename the
    service...which is not something I want to do nor should I have to)

This problem went away after I shut down my computer completely then restarted it.
Shutting down and restarting the IDE did not cure it.
UPDATE: I couldn't find a way to delete this post:
Restarting my machine does not fix the problem. I now have corrupted ValueObjects.

Mobile me gallery vs Aperture 3 -- incompatible?

My Mobile Me gallery worked perfectly in Aperture 2. I upgraded to Aperture 3 and about 20% of my gallery images got deleted and the remaining ones appeared in a random order. I am rebuilding the galleries now, but the process is VERY annoying (not to mention the time and effort needed to select from ten thousand images). The order of the images keep changing; when I try to rearrange then, some stay in their desired positions while others jump around. Although my update preference is set to "manual", Aperture keeps updating every 30 seconds or so, slowing down work significantly. My final grudge is that some of the images that appear in the published gallery are not the same as the ones I chose to create the gallery. It appears that Aperture 3 is full of bugs ... Any advice?

Aperture does not have bugs any more, at least that is what some folk would have you believe.
If you have just installed Ap3. It needs quite a long time to do all that it has to, to finish fully, and depending mostly on the library size, it could take a couple of days to several to finish. It is best left to get on with it. If this is not the problem then i have no other ideas. Allan

Aperture will not import all CR2 (iPhoto is fine....)

I'm currently attempting to move from a PC to a Mac. For the most part this has been a positive experience however Aperture is starting to bug me.
My photo library has been copied across and some old NEF files converted to JPEG. The library is located in a folder in the Pictures directory. The entire library imports fine into iPhoto.
When attempting to import into Aperture I get seemingly random rejection of CR2 files. Photos prior to the failure import fine. Photos after the failure import fine. Around 20% of images are rejected.
When the failure occurs no error messages are sent to the console. Examination of photo metadata shows not significant differences between photos that work and photos that do not. Changing the file name to something shorter does not help.
Restarting Aperture does not work. Restarting the OS does not help. Downgrading to RAW 2.1 does not help.
The only similar report I have found was from people having issues with CF cards, and the solution was to copy the files locally and then import....
I'm not going to convert my CR2 files to DNG or JPEG just because Aperture is buggy. Other than that any suggestions would be greatly appreciated (is there an Aperture log file somewhere ?)
Camera: Canon EOS 30D
Aperture 2.1.2
OSX 10.5.6
Raw Bundle 2.5
iPhoto 09
Thanks !

I seem to be having the same problem. I was to shoot an entire stage production with a canon 50D and when I only had a 4gb card at my disposal, I wanted to take some more pics so I went with Raw2. apparently aperture doesnt like this. it imported the project but all it gives me are thumbnails and in the canvas it says "unsupported image format".
what do they expect me to do...spin back time and reshoot the entire production? no i dont think so...apple needs to get on this (if they havent already) and make this work.

ITunes, iPhoto & Aperture - odd sync issue

Hi all,
I am a user of both iPhoto & Aperture, with unified photo library, and occasionally sync one or more events to my iPhone (rather than syncing all photos automatically).
I've noticed recently a rather odd issue, where iTunes does not seem to be "seeing" my iPhoto library. If I set Aperture to the source, then all my events/projects show up correctly. If I choose iPhoto as the source, 0 photos .
Opening the library directly in either iPhoto or Aperture works just fine - all events and photos present and correct - so the issue appears to be around the link from iPhoto to iTunes - weirdly, given the unified library, Aperture to iTunes seems to be fine.
Whilst I _could_ just sync to Aperture, a) the error bugs me , and I'd like to sort it out, and b) iPhoto is a better manager of events (chronological order etc) so I would prefer to use iPhoto to sync to iPhone, iPad etc.
I'm running Mountain Lion and both Photo apps are up to date. Hopefully some kind soul can assist!?

Hey Aljrob_UK
Thanks for the question. It sounds like there may be a permissions issue with your iPhoto library, let's see if repairing this will help to resolve the issue. See the additional information section of the following article:
Important: Please backup your library first (http://support.apple.com/kb/PH2504)
iPhoto 6 and later: Rebuilding the iPhoto library
http://support.apple.com/kb/HT2638
Additional Information
iPhoto 9.3 and later introduces a new Library First Aid dialog in place of the previous rebuild options.
If Repair Permissions does not resolve your issue, attempt Repair Database and/after Rebuild Database. You can skip the Rebuild Thumbnails.
Thanks,
Matt M.

[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

More....! Aperture 3.0.2 bugs...??

Similar Messages

Maybe you are looking for