Jrockit- unsupported time format in cookie header

We have application which sets the cookie like below
Cookie sessionCookie = new Cookie(cookieName, cookieString);
sessionCookie.setMaxAge(timeOut);
response.addCookie(sessionCookie);
and The setMaxAge() method simply takes the integer value and converts it to cookie which is set into the browser session.
And the date formate was like below
1.     Sun, 06 Nov 1994 08:49:37 GMT
2.     Sunday, 06-Nov-94 08:49:37 GMT
This worked fine , until we are in wls8.x jdk 1.4.
After upgrading to wls 9.2 jdk 1.5 the cookie fails
reason we found was the date formate we are seeing now is
Wednesday, 07-Apr-2010 21:35:38 GMT
Is there any change or know issue in bea jrockit?
Anyone come across such a issue , kindly share your workaround if you have any
Thanks
M
So the browser is not accepting.

Hi Dennis,
Thank you very much for your response. Indeed, I am talking about Cont Acqu&Graph-To File(Binary).vi . And if that is not the data, what is that information contained in the first two columns of the text file? I hesitated to attach the code because it's messy due to further developments; I will attach it if you think is relevant. The conversion to the text file is done Saved Graph Acquired Binary Data.vi, so no customization or personal signature.
If that one is not the date, do you have an idea how I can have this information in the header, and how to timestamp the samples acquired, with the millisecond offset from the base-time?
Kind regards,
Dana
Attachments:
Acq_multiBS_splitfiles.vi ‏138 KB

Similar Messages

  • Pre Lion iPhone videos show Thumbnail but can't play - new video generates Unsupported Video Format popup, no thumb but will play via quicktime

    This is really frustrating -
    Over the last year I have been uploading all of my photos and occasional iPhone video to Aperture 3 (latest version all patches in place).    Aperture would recognize the video, create a thumbnale and otherwise treat it nicely.
    Now, since upgrading to Lion I find that though I can "see" the old videos in their folders or projects and the associated Thunbnale, I can't play them - I either get the spinning color wheel and then nothing or Aperture will crash and report an error relating to Quicktime (sorry don't have an error code at the moment).
    If I try and export a video I can - but what I get also can't be played by Quicktime - just a black screen.  When I hit Play - the scroll bar moves, but there is no sound or video.
    From Final Cut Pro X, I can imoprt this exported video file and see that it appears complete - but FCPX uses it's own playback elements.
    If I shoot a new video on my iPhone, I find that I can see the thumbnale in the import option of Aperture when looking at the phone, but once imported I get a Popup telling me that it is an "Unsupported Video Format" - "Do you want to open this video clip with QuickTIme Player?"   If I hit Open then the clip does play, but the thumbnale remains a black square with the warning Exclamation Point.
    I have also had some issues with Lion Mail crashing when trying to play a video made on an iPhone and sent to me via email.   Seems more likley to be a Lion / Quicktime issue then an Aperture and Mail issue - but who knows.
    I spent 2.5 hours of quality time with the Genius bar this morning.  We reinstalled Lion and after that the suggestion was to trash and re-install Aperture, but that would require my disc and of coruse a trip home.   Mail doesn't seem to still have the issues with iPhone movies that it had - but Aperture is still not happy.
    Did as instructed and dragged Aperture 3 to the trash, did the empty trash option, restarted and reinstalled.   Then did a software update to catch the new update for Aperture and it found that.   Interestingly when I did start it up after that it DID NOT ask me for my key - so clearly some elements were left over.  
    Now upon retstarting Aperture 3 once again I find that I can still see my old movies (their thumbnails show up) but I still can't play them.   The new test movie is there but still generates the popup regarding it being an Unsupported Video Format.
    And it's not just my iPhone.   Video sent via email from another iPhone can play as an attachment, or when dragged and dropped to the desktop, but once imported into Aperture is once again proclaimed to be an Unsupported Video Format.  
    Hoping someone out there knows how to resolve this....

    For some reason it just started to work now. Have no idea what didn't work before.

  • Time Format using text variable with replacement path

    Hi Friends,
                                 I've used "Text variable with replacement path" to make the column heading dynamic by replacing the values referring from "0calday"...
    everything is working fine, but here it is displaying the time format like
    YYYYMMDD (20030101), i want it to be displayed DDMMYYYY (01012003) in the column heading... how to make it possible?
    pls waiting for ur inputs, it's an urgent...
    Regards,
    Pattnaik

    Hi Satyakam,
    In the text variable properties make sure that in the replacment path you have chosen "Text" to appear date as per user setting . Other wise as in your case it must be set to "Key" which always shows in the format YYYYMMDD.
    Hope that helps.
    Regards
    Mr Kapadia

  • Error message when I try to print: unsupported document-format"application/vnd.cups-command. I recently had my hard drive replaced in my early 2010 21" iMac. Can anyone help?

    Error message when I try to print: unsupported document-format"application/vnd.cups-command". I recently had my hard drive replaced in  my early 2010 21" iMac. Anyone know anything about this? Thanks in advance.

    What system are you running?  Have you tried going to the Canon website to download and install the latest drivers for that model?
    Are you running Time Machine?

  • Fed up with "Unsupported File format" crashes!

    I really like Aperture - but, I am totally fed up with only being able to edit a few photos before I get the dreaded red/brown screen and the message of 'Unsupported file format' This cannot be the case as they are all .tifs and I have just edited several OK. My whole day is now one of 'stop/start' and either quit or sometimes 'Force quit'. Then Aperture works fine for another short series of edits - before the same problem recurs. It wastes a lot of valuable editing time - and completely spoils the otherwise pleasurable experience of using Aperture!
    I have made a lot of scans from original slides via a Nikon Coolscan 5000 - using Silverfast I have converted these from 48 bit to 24 bit. However, the file size is still large at 100MB - to get the best from the slides. I then import these .tifs into Aperture 2.1. I am using a MacBook Pro, 2.4 Ghz Intel Core 2 Duo with 4 MB RAM. I have an external 24 inch monitor. The .tif files are on an external firewire hard drive - 500 GB LaCie. My Aperture library is in my pictures folder on my MacBook Pro.
    Can someone PLEASE explain how and why I can make a series of edits fine in Aperture and then suddenly I get the red/brown screen and this unsupported file format message?
    Is it a memory problem? Given that I need to edit such large files is it a problem for my (powerful) MacBook Pro? Or, is it a more general problem with Aperure 2.1?
    Any advice - or solutions - PLEASE

    It's a bug in Aperture 2.x with large files and/or large pixel dimensions on images (not clear which). I have submitted a bug report, as should anyone who is seeing this. You'll find quite a few threads on this if you search back. The error message is frustratingly incorrect: there is nothing whatsoever unsupported or wrong with the file format, it just leads you down some dead ends in trying to find a solution while you figure that out.
    I could sometimes not even work on one image before it would do this. I went from 6GB to 10GB in my Mac Pro, and now I can pretty reliably work on two images before having to restart. So that to me smells like a memory leak or memory mismanagement of some sort is at the root of this, but who knows. We're all just waiting for each next release, hoping Apple has finally found and fixed this, because as you know they don't spend a lot of time discussing what bugs they're addressing; they just show up fixed eventually (one hopes!)
    If anyone chimes in here to tell you it's your fault for working with such large images, just ignore them. There were releases of 1.5 that handled these images just fine, as Aperture should. It broke with 2.x.
    Duncan

  • "Unsupported Image Format" all of a sudden, with previously workable files

    Folks,
    I've got an issue that seems very strange indeed.
    Months ago, I bought a Pentax K20D. I also bought a 17" MacBook Pro and Aperture. Camera and Aperture played well together.
    I encountered the known issue with white spots on the image when using the 2-second timer for long exposures. I read about how the Pentax firmware update 1.01 changed the EXIF Make information, causing Aperture to be unable to read the K20D PEF RAWs. So I waited.
    When Aperture 2.1.1 was released (and I think the Apple RAW update), I installed both of those. When I heard through this forum that the updates fixed the problem, I also updated my camera's firmware and confirmed that it worked.
    So smooth sailing for a few months on Aperture 2.1.1, OS 10.5.3 (or .4, I forget), and K20D firmware 1.01.
    Then I bought a Mac Pro 8-Core with 10.5.4 on it. I sold the 17" MacBook Pro. I used the Migration Wizard to move my user account from one machine to the other, but did a fresh install of all applications. (I've been an Apple tech for the past 7 years, and have various certifications. I know the user transfer process isn't perfect, but it should have the following results... read on)
    Now, in Aperture 2.1.1 on 10.5.4 with all updates, PEF RAWs taken with K20D firmware 1.01 that were previously edited, manipulated, etc just fine on my MacBook Pro say "Unsupported Image Format" in a big reddish-black box when I try to view the master. If I switch to Quick Preview, it displays just fine, but is un-adjustable. Additionally, any NEW images I copy from my K20D show in the Import window as being 0x0 pixels (or occasionally 160x120 pixels) and will only show a tiny preview or "Unsupported Image Format." All PEF RAWs taken with K20D firmware 1.0 are just fine.
    So here's what I've done:
    1) Tested a fresh install of 10.5.4 on another HD in the Mac Pro. Installed Aperture 2.1, updated to 2.1.1. This should be perfectly clean. It gives the "Unsupported Image Format" error with any new images from my K20D. Copying the library from my other partition gives the same problems as described earlier.
    2) Tested a fresh install of 10.5.3 on another partition in a Macbook Pro. Installed Aperture 2.1, updated to 2.1.1. Applied the Apple RAW update and iLife enhancements. It gives the same errors as before.
    3) Tested a fresh install of 10.4.11 on another partition in a Macbook Pro. Installed Aperture 2.1, updated to 2.1.1. This worked perfectly for all PEFs and DNGs.
    4) Took a month-old backup (from when everything was working just fine) of my Aperture Library and loaded it into all of the above configurations. Same results!
    So what is the deal here? Aperture all of a sudden can't read images that it itself was able to edit a month ago? How come it works just fine in 10.4.11? This seems really messy. I have essentially lost a lot of the work I've put in.
    I can use DNGs moving forward, but my past work is now messed up, and the DNGs are almost 75% bigger than the PEFs!
    Anyone have any ideas for resolution or should I just call Apple?
    Message was edited by: MonsieurBon

    If it's any consolation, I had the EXACT same problem today; just opened Aperture 2 and my entire library of images shows "unsupported image format' -- the thumbnails are still intact but clicking on any image suddenly shows the red screen.
    Same situation, these images were previously editable and accessible. We had a power outage an hour ago and initially I thought my library had crashed, but I was not actually using Aperture 2 at the time of the outage so I don't think that's the case.
    Given the relatively sparse attention Apple gives to these forums, I don't expect there will be a quick response.
    I have Leopard 10.5.4 installed, I don't have access to another version of the OS to see if I can get it work. If I'm not mistaken, wasn't there a series of Software Updates recently? I click on these without really checking the apps that are affected; could Aperture have been one of the apps 'revised' by the recent update?

  • Raw Files Appear Deleted or Corrupted Suddenly in Aperture with Unsupported Image Format Error

    I have been using Aperture 3, latest update, for the past year. Today, I tried to import new raw files from my new Sony RX1r and, as far as I can see, all raw files in Aperture give the "Unsupported Image Format" and alert symbol in the library where not only new files should be, but also ALL PREVIOUS RAW FILES. These files do no even show up as existing in the iPhoto Library.
    This is, needless to say, distressing, as hundreds and hundreds of photos seem lost. Also, the files show a reduced pixel size and file sizes all go to .5 Mb. Some of the photos seemed to show up initially and look fine until I tried to open them, then they all either disappear or show the Unsupported Image Format instead of the opened file. I have tried rebuilding the iPhoto library, but no help.
    I have looked in these discussions and see similar problems with Aperture. Perhaps, Apple has not made an update for the RX1r from the RX1 for raw files, but why should all older raw files now be corrupted, especially those recently made with my Olympus OM-D? Had no problem with Aperture until this disaster.
    Please help.
    William

    Just an update. Restarted computer and attempted rebuilds of iPhoto library a couple more times and finally files and photos mostly recovered, except for those I had tried to open. Aperture seems to have a problem, or a host of them, dealing with RAW files, and there is no update yet for the Sony RX1R for Aperture or iPhoto. Lightroom 5, on the other hand, seems to work great with these files directly, so that will be where all photos go for now. Will iPhoto and Aperture just become old archives? It is so infuriating that Apple does not allow for simple importing and exporting compatibility with such an excellent program as Lightroom 5 just to protect their somewhat poorly supported Aperture. I've been a staunch Apple supporter and user since the 80's, but having more doubts about the direction this company is taking.

  • Unsupported image format after moving from one project to another

    I scanned several thousands of images to my Aperture library. Went thru all of them providing adjustments to many of them, keywords to all of them and adjust date/time to all of them. All of the pics were visible, format is jpeg.
    This is a managed library (all pics within Aperture db).
    This morning started to restructure the project files (had three of them). After moving couple of hundred images to newly created project file I started seeing "unsupported image format" red screen after clicking the jpeg. 20-30% of the pictures clicked showed on viewer "unsupported image format".
    Tried regenerating the previews. Tried command-option start with first fix the preferences option. Then with rebuild option.
    Tried moving the pictures back to their original project file.
    No joy... Still 20-30% of the pictures show the "unsupported image format".
    Aperture 2.1.
    Amy other tricks I could try?
    Reported this to Apple aperture feedback of course.
    --h

    Link the two Macs together: there are several ways to do this: Wireless Network, Firewire Target Disk Mode, Ethernet, or even just copy the Library to an external HD and then on to the new machine...
    But however you do choose to link the two machines...
    Simply copy the iPhoto Library from the Pictures Folder on the old Machine to the Pictures Folder on the new Machine.
    Then launch iPhoto. That's it.
    This moves photos, events, albums, books, keywords, slideshows and everything else.
    +Note: there is no importing involved+
    The thumbs appear, but the images are added 2 or 3 times each and the events are all messed up.
    This happens when you import one Library to another, which you've done by drag and drop:
    Creating a black library and over writing the new with the old.
    Your problem is arising because of the Network Share. iPhoto needs to have the Library sitting on disk formatted Mac OS Extended (Journaled). Users with the Library sitting on disks otherwise formatted regularly report issues including, but not limited to, importing, saving edits and sharing the photos.
    Regards
    TD

  • Unsupported Image Format after opening a file in Photoshop.

    As from today,I am getting an unsupported Image Format after opening a file in Photoshop. I have made nothing more than as crop on the image. Why?

    Ernie, I misread your post indeed. I never saw a option to send RAW files to an external editor. All I can see is the option to chose what editor and then specify if PSD or TIFF is used. I always use PSD, usually 16bit and in one other installation in 8bit (due to RAM restrictions there).
    So Aperture creates the PSD version and PS edits that very version and saves it back into aperture. This is where I sometimes () get that "unsupported image" problem.
    I think this also is what Mike does: select a RAW master, use an external editor -> Aperture creates a PSD or TIFF. I haven't tried the TIFF option , though.
    My main point was: it all worked for a very long time and with the latest updates it is broken.
    have a good day.
    Roland

  • Aperture 3 and DNGs from LX5 raw files: unsupported image format

    My LX5 arrived, and I tried converting a raw file to DNG with Adobe DNG Converter 6.2.0.21 beta and importing it into Aperture. No luck: Aperture says it's an unsupported image format. I tried setting the compatibility as far back as possible in the preferences, and still no luck. Any idea why this doesn't work? I used Adobe DNG Converter multiple times to work with raw files from unsupported cameras, so it's a real surprise to get the unsupported image file message.
    —Andreas

    Unfortunately, this is more about Apple dragging its feet than a cutting edge issue. I got an LX3 and upgraded to Aperture 3 in February of this year. RW2s straight out of the camera always imported just fine. However, I've never been able to get a DNG generated from an RW2 with Adobe DNG converter to work. Interestingly, DNGs from another file format I use (PEF) work fine in Aperture.
    I submitted a issue report to Apple about the RW2 to DNG problem back in March, and like so many other suggestions to them, it seems to have vanished into the ether.

  • After loading Lion I cannot open some pictures. I get Unsupported Image Format. It tells me picture was taken with Canon EOS Rebel with unknown lens

    After loading Lion I cannot open open some pictures in Aperture. I get Unsupported Image Format, all files even the ones I can open are .JPG. Also it tells me picture was made using Canon EOS Rebel with unknown lens.

    You mention that 'most' of your files are DNG. Try
    running the effected files through Adobe DNG
    converter again and then import your reprocessed
    files to Aperture and see if the problem persists.
    I had a problem with a batch of D2x files converted
    to DNG which had been metadata tagged by
    PhotoMechanic (the evil app).
    B.T.W. You mention that you had been using Bridge.
    Are you getting any of the embedded XMP metadata
    coming into Aperture during the import process?
    Already tried that multiple times...no luck. I'm wondering though if it might be related to metadata as you suggest. I'm still trying different things to see what happens.
    I was able to alleviate the problem on one set of images by painstakingly searching my external drive for the oldest backups I could find - CR2 files from before DNG conversion. I then ran those through DNG Converter and tried importing them again (this time, I embedded NO thumbnail, but I'm not sure if that made the difference - I think it was more likely a fluke in the original conversion that caused the problem). This time, it worked.
    Now, the big problem is that I still have a couple hundred images for which I can't seem to locate the original CR2 files. I don't typically keep them after conversion, as I don't have the space for both.

  • I have a fujifilm X100, at first there were no issues viewing my RAW photos but now all of a sudden the pictures come up as "unsupported image format"

    I have a fujifilm X100, at first there were no issues viewing my RAW photos but now all of a sudden the pictures come up as "unsupported image format".  How do I fix this?

    No, I did not do any updates between the time that the files were viewable and when they were not.  I was actually without an internet connection for a few days when the problem started.  I reported the bug to apple and have since been contacted by them asking for a few sample images so they can figure out the problem, so I'm hoping they come up with an answer for me.

  • Unsupported file format

    Hi
    In CS4 i saved one file after some time i try to open  the same file that file is not opening, can any one please tell what is the problem and how to open the file.i tried to open in different version also but it is not opening it is showing error messaage as Unsupported file format.

    Hi
    http://www.mediafire.com/?7ob473p7mcbua4z
    Please check the file i have attached here

  • What's with the occasional "Unsupported image format" errors?

    I get this error randomly -- suddenly Aperture can't show me anything but a brief flash of the image, and then I get the maroon screen "Unsupported image format" error. Restarting Aperture returns things to normal. I've seen this in both version 1.5.6 and 2.
    I can count on this occurring about every hour or so. This is quite frustrating. I use CR2 files almost exclusively, written from a Canon 5D.
    Any ideas or workarounds for this behavior?

    I was getting this all the time with 1.5, I have not seen it yet with 2. I think it's a memory thing, it happens more quickly if I am running Safari and other stuff. Sometimes quitting Aperture then starting again does the trick, more often shutting the machine down and rebooting clears it. I also have some very large tiff's in the library, Aperture can't (I've not tried it in 2 yet) cope with them, always the unsupported error message. These files are between 300mb to 1gig, sometimes it justs hangs on to the 300mb but mostly not. By the end of the day it was a real problem, I could only export images 2-3 at a time, if I tried to email 10 low res I would get either an out of memory warning or unsupported etc.
    Something holds onto the memory somewhere either in Ap or Safari or all things running.
    Kevin.

  • When I try to import raw files from my nikon d600 I get the message Unsupported image format, When I try to import raw files from my nikon d600 I get the message Unsupported image format

    When I import raw files from my Nikon D600 into Aperture I get a tryangle sign with "unsupported image format"

    Latest Adobe DNG converter (7.2) DOES indeed convert NEF pictures coming from a D600.
    Head up to Adobe's website and download the app.
    You'll only miss the focus information (focus distance and focus sensors used), but you'll be able to work with raw and not rely on jpg only!

Maybe you are looking for