Develop Mode problems

I have just downloaded LR5 & trying out the develop mode. Don't know how it happened but lost the 'basic' menu in develop mode, how can I gewt this back?

Please check the following thread link:
http://forums.adobe.com/message/5398443#5398443

Similar Messages

Development mode problem

Hi,
We are using weblogic 6.1 SP3 and are having a problem when redeploying applications
in development mode.
We register a number of custom MBeans using a managemen.war which has a "<load-on-startup>"
line in its web.xml descriptor. We do this so that the MBeans get created and
registered a deployment time.
The war is normally packaged within an ear and when I copy a new ear into the
'applications' directory I get a series of class not found exceptions relating
to classes used by the mbeans.
What I am assuming is that when an ear is updated, the weblogic server attempts
to re-initialize its list of mbeans ?
Anyone know what happens internally when an application is re-deployed ?
We get the same problem when redploying any ear in the applications directory
and I have also got the problem if I extract the management.war and deploy it
separately ( i.e. not within our ear )
Any help would be appreciated.
Thanks,
Paul.

Where does the Schema class live?
I am ataching 1 example, one in an ear, the other is the same webapp just
standalone. The use custom JMX and register the mbeans, note that the
classes for the mbeans are down in the WEB-INF/classes.
I am not sure if these ear and web apps will work on 6.1, but these both
deploy fine on 8.1
The only thing you might have to tweak is deployment descriptor dtd.s
Cheers
mbg
"Paul" <[email protected]> wrote in message
news:[email protected]...
>
Hi,
Thanks for the reply,
Our ear contain 2 ejb.jars and 3 wars, the war we use to register ourcustom mbeans
can be deployed separately (i.e. not within the ear) so it does not have aclasspath
line in its manifest file.
We use the following line to get a reference to the mbean server
mbeanServer = (MBeanServer) new InitialContext().lookup(weblogic.management.RemoteMBeanServer.JNDI_NAME);
>
we then register mbeans using code similar to this
mbeanServer.registerMBean(mbean, mbeanName);
I have attached a sample of the exception, the exception repeats for allof our
custom mbeans, the listing shows the server getting a class excecption forone
of our custom mbeans called "Schema"
Thanks,
Paul.
"Mark Griffith" <[email protected]> wrote:
What is the topology of your ear. ie. where does stuff live and manifest
classpath.
How are you "regestering" mbeans.
What is the exception and the full stack?
mbg
"Paul Ryan" <[email protected]> wrote:
Hi,
We are using weblogic 6.1 SP3 and are having a problem when redeploying
applications
in development mode.
We register a number of custom MBeans using a managemen.war which has
a "<load-on-startup>"
line in its web.xml descriptor. We do this so that the MBeans get
created
and
registered a deployment time.
The war is normally packaged within an ear and when I copy a new ear
into the
'applications' directory I get a series of class not found exceptions
relating
to classes used by the mbeans.
What I am assuming is that when an ear is updated, the weblogic server
attempts
to re-initialize its list of mbeans ?
Anyone know what happens internally when an application is re-deployed
We get the same problem when redploying any ear in the applicationsdirectory
and I have also got the problem if I extract the management.war anddeploy
it
separately ( i.e. not within our ear )
Any help would be appreciated.
Thanks,
Paul.
[jmxEar.ear]
[jmxWebApp.war]

Develop Mode to Print mode problem

I cannot find a Lightroom 4 beta thread so I will ask my questiion here. When using the Develop mode in Lightroom 4 beta and then switching to the Print mode the photo I was just working on in Develop mode does not show on the screen but the last photo I actually printed shows again. What do I not have set right so that the current picture I was working on shows in the Print mode? I did not have this problem in Lightroom 3.

At the top of this forum, see the notice "Read this before posting about LR 4!!!"

LR3 "Extra Processing in Develop" Performance Problem

I have been investigating a specific LR3 performance problem. It may explain a small subset of the problems people have reported in the "Why is LR3 So Slow?" thread. I'm starting this thread to focus on this particular problem. I hope others will confirm/refute/refine my findings.
The Problem
In Develop, when I make an adjustment, normally the following happens: The CPU usage (as shown in Activity Monitor's bar graph) jumps to between 50 and 75% for all four cores, the updated image appears, and the CPU usage settles back down. This all happens in less than half a second. Note: this is with the image at the Fit size. However, sometimes I instead get the following after an adjustment: the CPU usage jumps to 50 to 75% for all four cores and the updated image appears as usual, however, instead of settling back down, the CPU usage jumps up to 90 to 100% for all cores and stays there for 3 to 5 seconds before settling down. Thus it appears that LR is doing some kind of "extra processing" since a lot of computation is happening AFTER the updated image has already appeared. I will refer to this problem as "EP". Obviously, when you are getting EP, editing in Develop becomes very balky.
Dependency on ratio between image size and displayed size
It appears that EP only happens when the displayed size of the image (in Fit zoom level and perhaps also Fill zoom level) is above a certain percentage of the actual image size (as currently cropped). Evidence: When editing full 21MP 5D2 images, I don't experience EP. If I crop the 5D2 image fairly significantly, then I can get EP. When editing 10MP images from my Canon S90, I usually get EP for landscape orientation pictures but not for portrait orientation pictures (since in Fit mode, landscape images display at a higher zoom level than portrait images). If I am getting EP, I can eliminate it by sufficiently reducing the size that LR is displaying the image by resizing the LR window smaller, opening additional panels (I normally edit with only the right panel open), displaying the toolbar, etc. It appears that EP is enabled when the displayed image is about 50% or larger w.r.t. the actual image (as currently cropped). For example, EP becomes enabled when a 3648 pixel wide S90 image is displayed at least 17 and 7/8 inches wide on my 100 ppi monitor (i.e. about 1787 pixels).
Dependency on HOW an adjustment is invoked
Even when the displayed image size is large enough w.r.t. the actual image size to enable EP, whether you get it on a given adjustment depends on how you invoke it:
- If you CLICK (i.e. press the mouse button down and quickly release it) on the track of one of the sliders (a technique I use often to make big jumps), EP will happen.
- If you press the mouse button down on a slider handle, drag it to a new position, and quickly release the mouse button), EP will happen
- If you press the mouse button down on a slider handle, drag it to a new position, but continue to hold the mouse button down until the displayed image is updated, EP does NOT happen (either before or after you then release the mouse button).
- If you highlight the numeric field at the end of a slider and use the arrow keys (possibly along with Shift) to increment or decrement the value, EP does NOT happen.
- EP will happen if you resize the LR window such that the displayed image size is above the threshold. (In fact, I determined the threshold by making a series of window width increases until I saw EP indicated by the CPU bar graphs.)
- EP can happen with local adjustment brush applications, but as with the sliders, it depends on HOW you perform the brush stroke. Single click and drags with immediate mouse release cause EP, drags with delayed mouse button release don't.
- Clicking an earlier History state causes EP
- More exploration could be done. For example, I haven't looked at Graduated Filter and Spot Removal adjustments.
My theory of what's happening
With LR2, my understanding is that in Develop mode when the displayed image is below 1:1 zoom level, after an adjustment is invoked, LR calculates the new version of the image to display using a fast, simplified algorithm that doesn't include the more computationally intensive adjustments like Sharpening and Noise Reduction (and perhaps works on a lower rez version of the image with multiple sensels binned together?). It appears that in conditions described above, LR3 calculates the initial, fast image update and then goes on to do the full update of the image, including the computationally intensive adjustments. Evidence: setting Sharpening Amount and Luminance and Color Noise Reduction to zero eliminates EP (or reduces the amount of time it takes to be barely noticeable). I'm not sure whether the displayed image is updated with the results of the extra processing. I think the answer is Yes since when I tried an adjustment of changing Sharpening Amount from 0 to 90, the initial update of the displayed image showed sharpening but after the EP, the displayed image was updated again to show somewhat different sharpening. Perhaps Adobe felt that it would be useful to see the more accurate version of the image when it is at or above 50% zoom. Maybe the UI is supposed to cancel the EP if you start to make another adjustment before it has completed but the canceling doesn't happen unless you invoke the adjustment in one of the ways described above that doesn't cause EP.
Misc
- EP doesn't seem to happen for Process 2003
- As others have mentioned, I'm surprised that LR (both version 2 and 3) in 64bit mode doesn't use more available RAM. I don't think I've seen LR go above 4GB of virtual memory or above 3GB "Real Memory" (as reported by Activity Monitor) even though I have several GB free.
- It should be obvious from the above that if you experience EP, there are workarounds: reduce the size of the displayed image (e.g. by window resizing), invoke adjustments in ways that don't cause EP, turn off Sharpening and Noise Reduction until the end of editing an image.
System specs
First generation Intel Mac Pro with two dual-core CPUs at 2.66 Ghz
OS 10.5.8
21GB RAM
ACR cache on volume striped across 3 internal SATA drives
LR catalog and RAWs on an internal SATA drive
30" HP LP3065 monitor (2560 pixels wide)
NVIDIA GeForce 7300 GT

I'm impressed by your thorough analysis.
Clearly, the programmers haven't figured out the best way to do intelligent caching and/or parallel rendering at a reduced size yet.
In my experience reducing the settings in the "Details" panel doesn't help.
What really bugs me is that the lag (or increasing lack of interactiveness) depends on the number of adjustments one has made.
This shouldn't be the case. If a cache is produced then every further adjustment should only cost the effort for that latest adjustment and not include adjustments before it. There are things that stand in the way of straightforward edit applications:
If you work below 1:1 preview, adjustments have to be shown in a reduced form. If you don't have a way to faithfully mimic the adjustments on the reduced size, you have to do them on the original image and then scale down. That's expensive.
To the best of my knowledge LR uses a fixed image pipeline. Hence, independently of the order in which you apply edits, they are always performed in the same fixed order. Say all spot removal operations are done first. If you have a lot of adjustment brush edits and then add a spot removal operation, it means that all the adjustment brush operations have to be replayed each time you do a little adjustment on your spot removal edit.
I believe what you are seeing is mostly related to 1.
I also believe that the way LR currently handles a moderate number of edits is unacceptable and incompatible with the notion that it is usable in a commercial setting for more than trivial edits. I suspect there is something else going on. If everyone saw the deterioration in performance after a number of edits that I see, I don't think LR would be as accepted as it is. Having said that, I've read that the problem of repeated applications of the adjustment brush slowing LR down has existed for a long time. I truly hope that this doesn't mean we'll have to live for it for the foreseeable future.
There are two ways I can see how 2. should be addressed:
combine the effects of a set of operations into one bitmap operation. Instead of replaying all adjustment brush strokes one after the other (speedwise it feels like this is happening), compute a single bitmap operation that combines all effects.
give up the idea that there is an image pipeline with a fixed execution order.
Some might argue that the second point is at odds with the whole idea of parametric editing, but I dispute that. Either edit operations are commutable in which case the order is immaterial, or they are not. If they are not, the user applies the edits in a way as he/she sees fit and will thus compensate for any effect of a changed ordering.
N.B., currently the doctrine of "fixed ordering of edit applications" results in the effect that even if you convert an image into B&W all your adjustment brush edits that applied colour tints will still show through. Reasoning: The user should be able to locally tint a B&W image. I agree with the latter but this could be achieved by only applying those tinting brush strokes that were created after the B&W conversion. All the ones that happened before should only be used to obtain the correct luminance values for the B&W conversion but obviously they shouldn't cause tinted areas.
The above example demonstrates to me that users naturally expect operations to occurr in the order they have been introduced, not in a fixed predefined order. If that principle were followed, I see no reason why the speed of a single edit should depend on the number of edits that were done to the image before.
I hope the programmers can (and the management wants to) address the performance issues. While I find LR usable for pretty modest edits, in no way the performance on my system approaches that would I would expect from an industrial strenght application.
P.S.: Your message reminded me of the following: When I experience serious lag with LR showing the strokes I make with an adjustment brush, it helps to pause a moment after the first click before one starts moving. This allows LR to catch up and then one can see the effect of the application pretty much interactively. Otherwise, there is terrible lag and the feedback where you have brushed an effect comes way too late.

Corruption in LR Develop mode

Greetings,
I'm on a Mac Power PC running OS 10.5.5 with 6.5 GB RAM on LR 2.1. I am shooting with a Canon 1ds III on SanDisk Extreme IV 4.0 GB cards.
Sometimes I get a rainbow-colored corruption on part or most of an image while working with an image in the develop mode. I recently upgraded to LR 2.0 and was hoping that it would clear up what was happing in LR 1.0 but it has not.
The only good news is that when I restart the computer and then relaunch LR, the corruption disappears before my eyes. In other words, when the image is "loading" in LR's develop mode, the same corruption is there momentarily but then vanishes once the image has fully "loaded."
Any thoughts?
Let me know if I can provide more information as I'm sure I have not provided enough. I have a screen capture I can email (or post if I knew how).
Thanks,
Scott

Hey Martin,
I can't get your first link to work but what I get is a square or rectangular-rainbow-digital gobbeldigook usually starting from the lower right corner of the image covering anywhere from 5% to 90% of the image.
At the moment, I'm exploring the possibility that mine is RAM-related. I'm able to recover the flawed images after a restart. This points me to a problem with my Mac or the LR software. I could be wrong so take this with a grain of salt.
Anyway, I purchased online (for a buck and change) "Memtest OS X". It checks your RAM for errors/flaws. After running the program, it turns out I have a bad RAM chip in my desktop machine and so I have of course removed it. So far, with working all day today on post, I have had no problems (knock wood). This is by no means final in my mind however and I'm going to continue to cross my fingers and hold my breath for a little while every time I open an image in the develop mode of LR.
I hope this might lead you somewhere as well. I'll report back later after I've had some time to test the waters.
Any luck on your end?
Scott

JDeveloper IDE: Developer Mode Error

Hi All,
I am facing an issue after launcing JDEV through /jdevbin/NT/1223_db2dbg_17007206 (JDeveloper IDE for Release 12.2.3 Dev Build 2).
I am getting developer mode error after launcing my application. For the error to perish, we need to disable the same by :
Go Project Properties -> Oracle Applications -> Run Options and remove OADeveloperMode from the selected list.
However the OADeveloperMode option is not visible at project properties. Any idea on how to disable the option through any other means or any workarounds.
The profile “FND:Developer Mode” is already set to No in site level in environment. I am still seeing the Developer Mode error in jdev.
Thanks in advance.
Regards,
Arpita

Hi Shobit,
Error message :
(This developer mode error is thrown instead of being registered due to the lack of the page context object.) The OA passivation framework coding standard has been violated. Web bean properties cannot be modified in the controller processFormData or processFormRequest method. Web bean properties should be modified in the processRequest method only. An attempt to modify a web bean has been made in the following call stack: java.lang.Throwable at oracle.apps.fnd.framework.OACommonUtils.getCallStack(OACommonUtils.java:822) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.setAttributeValue(OAWebBeanHelper.java:1857) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.setAttributeValue(OAWebBeanHelper.java:1891) at oracle.apps.fnd.framework.webui.OAWebBeanFormElementHelper.setAttributeValue(OAWebBeanFormElementHelper.java:2108) at oracle.apps.fnd.framework.webui.beans.message.OAMessageLovInputBean.setAttributeValue(OAMessageLovInputBean.java:616) at oracle.cabo.ui.beans.form.TextInputBean.setRequired(TextInputBean.java:441) at oracle.apps.po.common.webui.ClientUtil.setViewOnlyRecursiveInternal(ClientUtil.java:743) at oracle.apps.po.common.webui.ClientUtil.setViewOnlyRecursiveInternal(ClientUtil.java:864) at oracle.apps.po.common.webui.ClientUtil.setViewOnlyRecursiveInternal(ClientUtil.java:864) at oracle.apps.po.common.webui.ClientUtil.setViewOnlyRecursiveInternal(ClientUtil.java:864) at oracle.apps.po.common.webui.ClientUtil.setViewOnlyRecursiveInternal(ClientUtil.java:864) at oracle.apps.po.common.webui.ClientUtil.setViewOnlyRecursive(ClientUtil.java:704) at oracle.apps.ozf.oa.claim.webui.ClaimUpdateCO.setPageReadOnly(ClaimUpdateCO.java:425) at oracle.apps.ozf.oa.claim.webui.ClaimUpdateCO.processFormRequest(ClaimUpdateCO.java:239) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequest(OAWebBeanHelper.java:854) at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processFormRequest(OAWebBeanContainerHelper.java:385) at oracle.apps.fnd.framework.webui.OAPageLayoutHelper.processFormRequest(OAPageLayoutHelper.java:1241) at oracle.apps.fnd.framework.webui.beans.layout.OAPageLayoutBean.processFormRequest(OAPageLayoutBean.java:1579) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequestChildren(OAWebBeanHelper.java:1066) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequestChildren(OAWebBeanHelper.java:1032) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequest(OAWebBeanHelper.java:887) at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processFormRequest(OAWebBeanContainerHelper.java:385) at oracle.apps.fnd.framework.webui.beans.form.OAFormBean.processFormRequest(OAFormBean.java:395) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequestChildren(OAWebBeanHelper.java:1066) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequestChildren(OAWebBeanHelper.java:1032) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequest(OAWebBeanHelper.java:887) at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processFormRequest(OAWebBeanContainerHelper.java:385) at oracle.apps.fnd.framework.webui.beans.OABodyBean.processFormRequest(OABodyBean.java:363) at oracle.apps.fnd.framework.webui.OAPageBean.processFormRequest(OAPageBean.java:3113) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:1897) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:558) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:446) at _OA._jspService(_OA.java:72) at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:473) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:734) at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:391) at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:908) at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:458) at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:226) at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:127) at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:116) at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260) at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303) at java.lang.Thread.run(Thread.java:662)
This error part of the file (oracle.apps.ozf.oa.claim.webui.ClaimUpdateCO) present in the error message is an already existing code.
Now the problem with solving this issues may end up solving many other issues. I am also not sure that my solving one part will fix it or not.
If you can please help me with suppressing the option how we used to do that earlier via jdev, then I can move ahead with my changes and test them.
Thanks,
Arpita

Image in Develop mode - Orange Tint

I'm having an issue with my images when I switch to Develop mode. There is an orange tint that appears in each image while I'm tweaking it. Sometimes the tint is minor like the example I've attached and other times it makes it very difficult to edit the image. When I return to Library mode or export the image it's normal.
I've attached the same image in both Library and Develop mode to illustrate the issue. I've highlighted the problem areas with Yellow call-outs in the image that's open in Develop mode (note no adjustments have been made the tint appears as soon as I switch to Develop).
My system uses two video drivers (they are current as of today):
Intel HD Graphics 4000, Driver version 10.18.10.3621
NVIDIA NVS 5200M, Driver version 340.84
Thanks in advance for any assistance.
Jack

DOH, so much to learn!
Thanks

How can I REPLACE original RAW files with JPG's and keep my 'Develop mode' edits?

An image describing my problem:
http://i.imgur.com/hcqMYkv.jpg
(Lightroom 5)
'edits' = Edits made in develop mode.
'CR2' = My RAW image file format.
I have existing CR2's with edits for them saved in Lightroom.
I want to replace the CR2's with JPG's, and do nothing else. I want those JPG's to inherit the CR2's edits, but I DO NOT want the edits to be permanently applied to the image.
If I export the CR2's (which have edits) to JPG's, the edits will be permanently applied to them. I do not want this.
If I export the CR2's to JPG's without the edits, I have no way of getting the edits back and will have to redo the work if I use that photo again.
Any solutions? I've been trying for a while and have no idea how to do this.
Q: Why not keep the CR2's?
A: I am uploading these files to an online host (S3) as my primary storage method and uploading CR2's takes way too long with my internet speeds. Furthermore, online storage costs money.
Q: Why not shoot with JPGs instead of shooting raw?
A: I do my initial edits with the raw files and then archive them as JPG's to save storage space. They won't be raw anymore if I apply future edits, but I still have the option of retouching them from the 'original' state and still have my old edits preserved.

Probably the best thing for you to do is simply use lossy DNG format (e.g. export as, or convert to..): raw data is re-formatted with jpeg compression (full-rez or reduced-rez), but all raw settings apply.
If you insist on trying to have a true jpeg file with (mostly) raw settings, then:
The simplest way I can think of to do it without a script or plugin:
* Reset the raw photo (consider preserving things that don't translate well, like profile-based lens corrections and white balance).
* Export jpeg
* Un-reset the image (e.g. using edit history or pre-reset snapshot).
* Sync settings from raw to jpeg (note: omit settings that don't transfer well, or that were not reset..).
* Optionally: Delete raw
To automate/streamline would require a script or plugin.

I use lightroom with the soft proofing feature for my printing. I used to make a copy proof, but all of the sudden something changed, and even if I'm on the copy in the developing mode it prints the original. Also, If i chose a file that was already in li

I use lightroom with the soft proofing feature for my printing. I used to make a copy proof, but all of the sudden something changed, and even if I'm on the copy in the developing mode it prints the original. Also, If i chose a file that was already in light room to print, even though I have the chosen file up in the developing mode, it will instead print the most recent file that I added to lightroom. If found a way to work around these problems, (check make this the copy in the soft proofing, and copy my settings and delete and reload the old files) but it's a slight hassle and it didn't use to do this. Not sure why it changed. Could I have accidentally changed a setting?

See
iOS: Device not recognized in iTunes for Windows
- I would start with
Removing and Reinstalling iTunes, QuickTime, and other software components for Windows XP
or
Removing and reinstalling iTunes and other software components for Windows Vista, Windows 7, or Windows 8
However, after your remove the Apple software components also remove the iCloud Control Panel via Windows Programs and Features app in the Window Control Panel. Then reinstall all the Apple software components
- Then do the other actions of:
iOS: Device not recognized in iTunes for Windows
paying special attention to item #5
- New cable and different USB port
- Run this and see if the results help with determine the cause
iTunes for Windows: Device Sync Tests
Also see:
iPod not recognised by windows iTunes
Troubleshooting issues with iTunes for Windows updates
- Try on another computer to help determine if computer or iPod problem

Developer Mode Exception encountered in item EffectiveFrom Error

In Oracle apps , When I click on Configurator Developer, I get this error on the very first page :
Developer Mode Exception encountered in item EffectiveFrom Error: The item EffectiveFrom has a type (DATETIME) which is incompatible with the associated VO attribute, EffectFromAsString (VARCHAR2). Action: Make sure they are compatible by either changing the datatype or the attribute associated with the item.
Developer Mode Exception encountered in item EffectiveTo Error: The item EffectiveTo has a type (DATETIME) which is incompatible with the associated VO attribute, EffectUntilAsString (VARCHAR2). Action: Make sure they are compatible by either changing the datatype or the attribute associated with the item.
Developer Mode Exception encountered in item EffectiveFrom Error: The item EffectiveFrom has a type (DATETIME) which is incompatible with the associated VO attribute, EffectFromAsString (VARCHAR2). Action: Make sure they are compatible by either changing the datatype or the attribute associated with the item.
Developer Mode Exception encountered in item EffectiveTo Error: The item EffectiveTo has a type (DATETIME) which is incompatible with the associated VO attribute, EffectUntilAsString (VARCHAR2). Action: Make sure they are compatible by either changing the datatype or the attribute associated with the item.
I havent been working in any seeded applications lately . I am working on some other custom application and have depolyed it on server and this error did not occur untill yesterday.
There is a profile option : FND: Developer Mode which is set to nothing on server.
Also I have enabled developer mode to true in zone.properties
could any of this be a problem ?
Thanks
Edited by: user633772 on Sep 12, 2008 11:42 AM

A few doubts :
1. How is it different to set prof. opt. from Func Admin to setting it from Sys Admin ?
2. Do I need apache bounce after this ?
3. I had not touched these p/os and the values for site/user were null from before, so why do I see the error and others do not ?
4. Apart from all the error I posted in this thread I also get some error when I launch configurator from my custom webpage -
error is like this :
The OA passivation framework coding standard has been violated. The view object with full name, CZApplicationModule.TreeViewUsage, is not properly prepared for row insertion. Either setMaxFetchSize(0) or executeQuery() (or any equivalent method that ends up executing the view object query) must be called on the view object before new rows are inserted. For a detail view object in a master - detail relationship, executeQuery() (or any equivalent method that ends up executing the view object query) must be called instead of setMaxFetchSize(0) on the detail view object before new rows are inserted into the detail view object. setMaxFetchSize(0) call on the detail view object could cause a number of adverse effects.
Thanks

Developer Mode Error

Hi everyone,
I'm trying to find out what I did wrong closing the connection after calling a Stored Proc, the stored works fine and it made the update and others intructions, the problem comes when I whant to reload some VO's before they data was updated.
Here's the error:
Developer Mode Error - The database connection in the AppsContext object associated with the root application module's transaction has changed while the application module was in use. Cause: This could have been caused if application code called releaseJDBCConnection(), logOut(), or freeWebAppsContext() on the AppsContext object. Note that the AppsContext's JDBC connection is referenced and used by the application module's transaction. Action: Check your application code and remove these calls if the AppsContext was handed out from OADBTransactionImpl.getAppsContext(). (This developer mode check cannot detect the release event, if the same connection instance got checked out again through the getJDBCConnection call on AppsContext after the release.).
and here's my code in the AM
public void methodExample(String famEX){
Connection con = getOADBTransaction().getJdbcConnection();
CallableStatement cs = null;
for(blah blah blah){
if( blah blah){
try{
cs = con.prepareCall("begin dbEschema.SP_Example_Update_Proc(?,?); end;");
//some instructions
//declare and enter the "IN" values
int p_Id_Fam = (Integer.parseInt(famEX));
String p_Item_Id = r.getItemId();
cs.setInt(1, p_Id_Fam);
cs.setString(2, p_Item_Id);
//Execute the procedure
cs.executeUpdate();
cs.close();
con.close();
}catch(Exception e){
System.err.println("Exception: "+ e.getMessage());
}finally{
try{
if(cs != null)
cs.close();
if(con != null)
con.close();
}catch(Exception ex){
System.err.println("2nd Exception: "+ ex.getMessage());
cs = null;
con = null;
I wonder what can be the mistake, I hope you can help me
Regards,
Mentor
Edited by: mentor on 9/08/2010 03:29 PM

Thanks Ajay, Reetesh
I found another way to call without any problem the StroredProc from AOF, this can be helpful for another users.
OADBTransactionImpl oadbtransactionimpl = (OADBTransactionImpl)getDBTransaction();
Row[] rows = getacDVO1().getAllRowsInRange();
for(int i = 0; i < rows.length; i++){
acDVORowImpl r = (acDVORowImpl)rows;
StringBuilder procedureCall = new StringBuilder();
if(r.getSelected().equals("ON")){
try{
int p_Id_Cat = (Integer.parseInt(String));
String p_cve = r.getYourElements();
procedureCall.append("begin SCHEMA.YOUR_STORED_PROCEDURE('").append(p_Id_Cat);
procedureCall.append("', '").append(p_cve_ac).append("'");
procedureCall.append("); end;");
OracleCallableStatement oraclecallablestatement = (OracleCallableStatement)oadbtransactionimpl.createCallableStatement(procedureCall.toString(), -1);
oraclecallablestatement.execute();
getOADBTransaction().commit();
}catch(SQLException sqlexception){
System.err.println("SQL Exception: "+ sqlexception.getMessage());
getOADBTransaction().rollback();
throw OAException.wrapperException(sqlexception);
}catch(Exception e){
System.err.println("Exception: "+ e.getMessage());
getOADBTransaction().rollback();
throw OAException.wrapperException(e);
I hope this example can be very useful to this community
Best Regards,
Mentor

Develop Mode 2nd Monitor not showing edit adjustments

I am using Lightroom 4.1 RC2 on a Windows 7 64 bit system with dual monitors. When I am in the develop mode and make edit adjustments on any setting the 2nd monitor does not update. If I move to another image then come back the image is updated but it does not work in real time. I have never had this problem before and it worked fine in Lightroom V4.0

It's a bug in LR4.1 RC2.
The workaround seems to be to increase the size of the Standard Preview setting (File Handling tab of the Catalog Settings)....go up at least one setting (e.g. if it's currently 1024 change it to 1440 or 1680). No need to recreate your previews, just increasing the setting seems to work in most cases.
You might also, without realising it, be suffering a fairly dramatic memory leak which is also stopped by changing the settings.
For a longer answer, see here:
http://www.lightroomforums.net/showthread.php?15591-Interesting-Problem-with-LR4-1-RC2

Develop mode doesn`t work in realtime

Winsows 8.1 x64
Lightroom 5.4 CC
When I move any sliders in develop mode image in main view doesn`t change, but in filmstrip changes. If I switch to another image and back all changes applies.
Please help.

I'm having the same problem. Started just after I upgraded to Lightroom 5.4 CC

Develop Mode closes LR 2.1; now resolved

LR 2.1 has been working fine, but today switching to Develop mode closed LR.
Each time I opened LR, switching to Develop would close LR, independent of
the folder or image selected. No events were registered by Windows XP SP3.
After several failures, I optimized the catalog, and now the problem has
been resolved.
Best,
Christopher

> Interesting! I couldn't get LR to Export to Catalog, even after quitting
> and restarting, but doing as you did seemed to be the fix also.
One more note. Performing a backup and integrity test did not isolate or
resolve the problem. Apparenlty, there can be integrity problems that are
not identified by the integrity test, but can be resolved by optimizing the
catalog. In summary, if you are having problems with a catalog, you might
try optimization to see if that helps.
Best,
Christopher

It doesn't seem to be as sharp as it is in the "Develop" mode. This seems to occur more with wide angle than macro. Any suggestions would be extremely welcome...Norm

Here's my problem: (Lightroom 4) I will edit a photo in "Develop" to the point where it looks great and I'm satisfied with the results. Then I click back to "Library" and the photo seems to go a little out of focus. When I export the photo, it doesn't seem to be as sharp as it is in "Develop" mode. This seems to occur more with wide angle than macro. Any suggestions would be greatly appreciated! Norm

Okay guys, some good news!
First of all, thanks again to Sean for his suggestion to look inside the transaction log!
Indeed that specific table that I noticed was filling the transaction log, is the largest table in my database. Its size stands at about ~65GB. Like I said earlier, it has no LOB or Overflow columns. But one interesting fact about it is - it had absolutely
no indexes! It was a heap, but it was also partitioned. I didn't know a case like this could cause such problems with shrink? It's weird but it also kinda makes sense in a way.
Anyways, I ran a script to create a partitioned clustered index on that table. That took pretty much all day long due to the table size (almost 7 hours). But once that was finished, shrinking the data file was a breeze!
At least... Until the shrink started "hanging" again because now it started dealing with my
second largest table (~55GB). Like the first one, this one is also a partitioned
heap without any indexes. So I expected this to happen. I guess the solution this time will be the same: Create a clustered index.
Does this make sense to you? A partitioned heap table causing such heavy workload to SHRINK, but when it's moved to a clustered index, suddenly it flies?
Eitan Blumin; SQL Server Consultant - Madeira SQL Server Services

Develop Mode problems

Similar Messages

Maybe you are looking for