Behaviour when caching remote reference..

In this application, whose crazy behavior I am trying to fix -
there are 2 Message driven beans that process message out of certain queues(say, batch and realtime)
There is a util class to which the MDB's onMessage() methods delegate. Util class in turn delegates all calls to a session bean. The session bean is accessed via a static member variable of remote reference, which is intialized during first call. Calls to session bean method can take around 2 min to complete. Given that, what will be the system behavior when there is a very huge volume of messages in One of the queues(say batch)? will each new message wait until the previous session bean call is over?
What is a safe session bean pool size in a very high volume environment?
TIA
RC

Each MDB will process its message, then go onto the next available one etc. Depending on the MDB pool size you should be able to process messages concurrently in different MDBs.
The only thing to be careful of is that your transaction timeout is not set so low that the container thinks the MDB is blocked and rolls back the transaction.
James
http://logicblaze.com/
Open Source SOA

Similar Messages

When do remote interface get invaliated? Can I cache them?

Hello,
I am designing an application, and considering using the "Service Locator" pattern, acting as a singleton that will cache jndi context, and bean home and remote interfaces. However I am unsure whether caching of remote interface is a problem or not:
1) Under what circumstances will the cached remote interface for a stateless session bean be invalidated?
2) Under what circumstances will the cached remote interface for an Entity Bean be invalidated?
3) Assuming that I cache Stateful session bean remote interfaces in a Servlet HTTPSESSION, under what circumstances will the cached remote interface for Stateful session bean be invalidated?
4) Finally, do I have to utilise home handles instead of remote interfaces for any of these situations? If so, why?
Thanks

I understand that caching the Home Interface or HomeHandle of this, is the solution for
reconnection to EJB's problems.
But I do not succeed in getting a working solution for handling the reconnection
to a restarted EJB server after some downtime.
First the HomeHandle of the Home Interface is successfully saved with:
"myHomeHandle = myHome.getHomeHandle();"
Later the HomeHandle is used to restore the Home Interface with:
"MyHome myHome = (MyHome) myHomeHandle.getEJBHome();"
But this gives an Exception like
Caused by: javax.naming.NoInitialContextException: Need to specify class name in environment or system property,
or as an applet parameter, or in an application resource file: java.naming.factory.initial
I have followed the recommandations in this postings, but in some way I lack a bit information.
Has somebody a code example in Java of how to do this?
Here is my code which throws the exception
InitialContext context = new InitialContext( properties );
Object obj = context.Lookup( "My" );
MyHome myHome = (MyHome) PortableRemoteObject.narrow( obj, MyHome.class );
myBean = myHome.create();
myHomeHandle = myHome.getHomeHandle();
// At this point everything fine, and a myBean is created.
// Now I try to recreate the myHome Interface
MyHome myHome = (MyHome) myHomeHandle.getEJBHome();
// In order to (re)create the myBean EJB.
myBean = myHome.create();
// But the second create is never executed, as the method call "...myHomeHandle.getEJBHome();"
throws the above Exception.
So, any help I will Appreciate.

Rmi remote reference lookup very slow in web start application

I have a little problem with the RMI communication in a web start test application.
It is a very simple program in which the client calls a remote object that returns a String.
Everything seems to be working fine when i'm running/debugging the client app in eclipse, but when i package my client project into a jar file and run it as a web start application (i'm providing the jnlp on a local webserver) the remote reference lookup takes about 15 seconds.
basically, what my client does is this:
Registry registry = LocateRegistry.getRegistry(address);
ServerTransaction st= (ServerTransaction) registry.lookup(name);
String result = st.test();
The server code looks like this:
String name = "ServerTransaction";
ServerTransaction engine = new DefaultServerTransaction();
ServerTransaction stub = (ServerTransaction) UnicastRemoteObject.exportObject(engine, 0);
Registry registry = LocateRegistry.createRegistry(Registry.REGISTRY_PORT);
registry.rebind(name, stub);
The server runs as a normal stand alone java application on my local machine as well.
And here the content of the jnlp file for the client application:
<resources>
     <jar href="WSTest.jar"/>
     <jar href="WSTestServer.jar"/>
     <j2se version="1.6+" href="http://java.sun.com/products/autodl/j2se"/>
     <property name="serverAddress" value="127.0.0.1" />
</resources>
<security>
     <all-permissions/>
</security>
<application-desc main-class="test.WSTest"/>
As i said, the whole thing works when run as a normal java application as well as with web start, with the difference that the remote reference lookup takes about 15 seconds with web start.
Can anyone tell me how i could go about this?

Meanwhile, i tried the same thing at home on my xp machine (i use vista at work), and even though my test at home basically does the same thing (invoking a simple remote method that just returns "hello world") it worked pretty fast, contary to the 15 second hang on vista.
So i can't really say where the problem is...
I also found these two rmi properties
sun.rmi.transport.connectionTimeout (1.1.6 and later)
The value of this property represents the period (in milliseconds) for which socket connections may reside in an "unused" state, before the Java RMI runtime will allow those connections to be freed (closed). The default value is 15000 milliseconds (15 seconds).
and
sun.rmi.transport.proxy.connectTimeout (1.1 and later)
The value of this property represents the maximum length of time (in milliseconds) that the Java RMI runtime will wait for a connection attempt (createSocket) to complete, before attempting to contact the server using HTTP. This property is only used when the http.proxyHost property is set and the value of java.rmi.server.disableHttp is false. The default value is 15000 milliseconds (15 seconds).
Hoping it would help (totally clueless) i tried to set these as system properties via System.setProperty(...) to a lower value (if that even works this was - please correct me if i am totally wrong here) but it didn't help.

Different behaviours when exporting pdf

hi,
i'm facing a strange behaviour when trying to export a pdf that is generated from db. i want to make pdfs available via dialog box. i set disposition to attachment in the response header. whereas FireFox shows the dialog box (as expected), IE renders the pdf in the same window:
   * downloads the report in the requested export format
public String exportReport()
    String outcome ="error";
    LayoutXSLT layout = null;
    ByteArrayInputStream xslt_bais=null;
    ByteArrayInputStream xml_bais=null;
    byte[] content=null;
    ByteArrayOutputStream fosByte = new ByteArrayOutputStream ();
    String fileName = "Report";
    String disposition="attachment";
    String contentType="application/pdf";
    FacesContext faces = FacesContext.getCurrentInstance();
    HttpServletResponse response = (HttpServletResponse) faces.getExternalContext().getResponse();
    FileExporter fex = new FileExporter();
    if (report != null && report.getRowCount()>0)
      try
        layout = accountingRemoteInterface.createXSLTLayout(userID, report.getForm().getId(), XSLT_TYPE.PDF);
      catch (UserAccountingException aex)
        messageError = errorWriter.writeUserAccountingException(rb, aex);
      if (layout != null)
        xslt_bais = new ByteArrayInputStream(layout.getXsltContent());
        try
          xml_bais = new ByteArrayInputStream(report.createXMLStream());
          XSLTHelper.doFOP(xslt_bais, xml_bais, fosByte, null);
          fosByte.flush();
          fosByte.close();
          content = fosByte.toByteArray();
          reportAvailable=1;
          outcome = fex.export(content, contentType, fileName, disposition, response);
          faces.responseComplete();
        catch (XMLWriterException xex)
          messageError = errorWriter.writeXmlException (rb, xex);
        catch (TransformerException tex)
          messageError = errorWriter.writeTransformerException(rb, tex);
        catch (FOPException foex)
          messageError = errorWriter.writeFopException(rb, foex);
        catch (IOException e)
          e.printStackTrace();
    else
      filteredItems=limitedItems=reportItems="";
      messageError=rb.getString("ERROR_NO_PDF_AVAILABLE");
    return outcome;
public String export(byte[] cnt, String cType, String fName, String dispo,
      HttpServletResponse response) throws IOException
    String outcome = "error";
    byte[] content = cnt;
    String contentType = cType;
    String fileName = fName;
    String disposition = dispo;
    response.reset();
    response.setContentType(contentType);
    response.setContentLength(content.length);
    response.setHeader("Content-disposition", disposition + ";filename=\"" + fileName + "\"");
    response.setHeader("Cache-Control", "cache, must-revalidate");
    ServletOutputStream out = response.getOutputStream();
    out.write(content);
    outcome = "success";
    return outcome;
    }Any help appreciated!

i checked the server log and couldn't find anything excepting a warning when setting the pdf layout :
WARN [BreakingAlgorithm] Line 1 of a paragraph overflows the available area. (fo:block, "****************")you mean i shouldn't stop the render response phase, don't you? what's the alternative? a file servlet?

Caching EJB references

Hi all,
I was wondering if anyone could give me a conclusive explanation regarding the caching options for EJB objects(SLSB, and Entity Beans), both home/remote and localHome/local.
I have read a lot of various EJB documentations including a fairly thorough look into the spec, and have about 2 years of practical expirience with EJBs.
The matter that is still vague to me after all this time is the matter of caching and reusing EJB references. practical expirience and some documentation lead me to believe that caching an EJB reference of any kind is hazardous. From what I saw the spec never adresses this issue in a straightforward conclusive manner. It does discuss some failover scenarios and the use of EJB handles as both optionally a persistent reference and a "long living" refernce, but never in a context that is "spec mandatory" and "encapsulates" the whole picture.
Now, there is no fundamental difference between caching a reference or using one that is locally scoped in a single method, except the time it is expected to be "alive", which is, by definition, a relative and unmeasurable matter.
Theoretically, I am sure there is no problem implementing references, which are actually client "proxies", stubs, in a way that will not be dependent of an exact instance, but rather on an abstract EJB ID(which may indeed cause a performance overhead).
Anyway, I don't want to get into implementation details, I am simply looking for a clear explanation about the matter of "long living" references, and what is mandatory by EJB specification.
Thanks for any insights....
I also crossposted to EJB forum -> http://forum.java.sun.com/thread.jsp?forum=13&thread=538526&tstart=0&trange=15

A locally scoped reference is only on the stack while the cached reference is on the heapOf course, but in the context of what I'm talking about here, that doesn't really matter. The point is that in both cases there is a reference to an EJB object/home, that is used for a longer/shorter time.
I think the main reason for not caching the references is that is interfere's with the server's ability to manage it's resources. OK, sounds reasonable enough. So why doesn't the specification provide clear rules, even restrective ones that say no caching can be applied? Looks to me as if it would be safe to say that home objects for example are safe to cache working with any EJB server as long as the EJB server isn't restarted. Why isn't it written anywhere?
It always refers to Handles as "long living" references. How can one measure "long"?
Now, I may have gotten the wrong picture. Maybe there are some widely agreed issues on this matter, for example that caching SLSB as you've mentioned, and home objects is always safe in the scope of an EJB server life time(from the point in which it starts to the point it goes down).
The thing is, where ever I looked I saw different strategies, and never it was clear what exactly they came to solve. For instance, an EJBHome service locator that caches the home object as is, vs. a service locator that caches the home handle.

Flash video - behaviour when buffering stops

I've started using progressive Flash video on one of my sites. The objective is to provide subtitling for foreign learners of English. It works well, subtitles jump around on full screen, but that's just cosmetic.
However, one of my testers reports that periodically the playback stops, and you have to press the start button to continue. The desired behaviour would be à la YouTube, where it pauses, the buffer fills, it continues. I've only seen this problem once on my system.
There are references to this in the discussions, eg http://forums.adobe.com/message/3794903#3794903 but few answers.
So, can I ask
1. With progressive flash video, what is the expected default behaviour when the playback hits the end of the buffer because too little data is being downloaded - is it supposed to recover and continue automatically ?
or
2. If not, is there a known fix ?
My goodness, it's a black art Flash Video ! Here's a link where maybe you'll see the problem.
http://www.regardez-des-videos-en-anglais.org/January2012/index.htm
... and if you don't you can enjoy the famous bit of the Rocky Horror Show !

I've started using progressive Flash video on one of my sites. The objective is to provide subtitling for foreign learners of English. It works well, subtitles jump around on full screen, but that's just cosmetic.
However, one of my testers reports that periodically the playback stops, and you have to press the start button to continue. The desired behaviour would be à la YouTube, where it pauses, the buffer fills, it continues. I've only seen this problem once on my system.
There are references to this in the discussions, eg http://forums.adobe.com/message/3794903#3794903 but few answers.
So, can I ask
1. With progressive flash video, what is the expected default behaviour when the playback hits the end of the buffer because too little data is being downloaded - is it supposed to recover and continue automatically ?
or
2. If not, is there a known fix ?
My goodness, it's a black art Flash Video ! Here's a link where maybe you'll see the problem.
http://www.regardez-des-videos-en-anglais.org/January2012/index.htm
... and if you don't you can enjoy the famous bit of the Rocky Horror Show !

Remote reference is getting garbase collected

Hi,
I'm using Weblogic 5.1, on Windows NT.
I have RMI remote object on the server side, and my client is an applet.
In the applet I use JNDI to get the reference of the server object, and
use it. The problem is after sometime ( like 10 min or so) I get
weblogic.rmi.NoSuchObjectException
and at the WLServer console I see
' <DGCServer> tried to renew lease for 1 lost reference'.
At the server side, I bind the object using JNDI.
I want thsi reference to be available all the time in the applet.
any help is appreciated.
thanks,
Abdul.

thanks, I will try and let you know by tomorrow.
I tried both methods, you suggested, but i didn't get any errors. I still
have to test the client connections and see whether they are gc'd or not.
i gave a idletime of 1000.
- Sam Jacob
Iconixx Corp.
Wei Guan <[email protected]> wrote in message
news:[email protected]...
set
weblogic.rmi.dgc.idlePeriodsUntilTimeout=xxx
in your weblogic.properties file.
If it didn't work (I haven't tested),
use -Dweblogic.rmi.dgc.idlePeriodsUntilTimeout=xxx in your startup script.
Give a try and let me know.
Cheers - Wei
Sam <[email protected]> wrote in message
news:[email protected]...
how do you set this property.I think i have the same issue.
Sam Jacob
Iconixx Corp.
Wei Guan <[email protected]> wrote in message
news:[email protected]...
You can tune up this property:
weblogic.rmi.dgc.idlePeriodsUntilTimeout
The default is 2. WebLogic will dereference a remote object referece
if
that
reference hasn't been referenced for a period of time. The timeout
value
is
determined by this property and other properties. The default idle
timeout
is 360 secs when idlePeriodsUntilTimeout=2. Use this formula to figurethe
timeout: 60 x (4 + idlePeriodsUntilTimeout).
Use at your own risk. If you set up this value too high, there will be
unused remote reference on WebLogic server for cleaning up, which inturn
degrade WeLogic performance.
My 2 cents.
Cheers - Wei
aroshan <@cisco.com> wrote in message
news:[email protected]...
Hi,
I'm using Weblogic 5.1, on Windows NT.
I have RMI remote object on the server side, and my client is anapplet.
In the applet I use JNDI to get the reference of the server object,and
use it. The problem is after sometime ( like 10 min or so) I get
weblogic.rmi.NoSuchObjectException
and at the WLServer console I see
' <DGCServer> tried to renew lease for 1 lost reference'.
At the server side, I bind the object using JNDI.
I want thsi reference to be available all the time in the applet.
any help is appreciated.
thanks,
Abdul.

Remote references

Hi all,
We have our product (RMI Client) that has references to objects that belong to various RMI servers running in different systems. This seem to spawn many RMIRenewClean and RMI ConnectionExpiration threads for each end point and they seem to still hang around for a long time.
Obviously, there must be still some references I am holding to, which I am not aware of. Is there a way to find out which reference objects these threads are waiting to be released? Is there some RMI properties I need to set so as to get these logged somewhere?
Thanks in advance
Anand

The home stub does know which host/port it was connected to, and I
believe by default will attempt to reconnect. As long as you restarted
the server on the same host/port, it can reconnect.
That being said, it's probably a good practice to redo the JNDI lookup.
-- Rob
Emma wrote:
I am currently investigating a problem with the reconnection of a client to the weblogic server after a server crash.
We have a stateful session bean which provides functionality for logon and session management of the client. When the client first performs a logon, a lookup to the JNDI is done to get a remote reference to this bean's home object. Then the create method on the home interface is called to create the bean instance. If the server crashes then the reconnection code is called. This currently only contains the call to the create method and doesn't peform any JNDI lookups. I was expecting all references to be lost when the server crashed and therefore thought that this reconnection wouldn't work but it does! (The weblogic instance is not clustered) Does anyone have an explanation as to why this might happen?

Activatable Servers and Remote References [RMI]

Hello everyone,
I'm wondering if there's a way to know, on an activatable server, how many clients have an active reference to that and their id. I need to know exactly who did not renew his lease with the server, and once I know it I can remove that client from a list of logged-in client..
example:
client "user1" gets a remote reference of the activatable server, that adds "user1" to a logged-in-list I made (like a online userlist in a forum). suddenly user1 crashes without invoking "logout" method (and for the userlist he's still online!).
Once the lease for user1 expires, the activatable servers decreases the remoteRef count.
I'd like to associate the client username with the remote reference or the lease in some way, so once a client lease is not renewed I know for sure who I've to remove with the server from the online userlist..
Hope you can understand my problem, thanks in advance
Edited by: Guguz on 28-dic-2010 6.44

Each time a client connects to the login server, I give him a new activatable server.A new server. Making it activatable is pointless: you're creating it dynamically per client. Only the login server needs to be activatable. It goes something like this, modulo typos:
public interface Login extends Remote
Session login(String username, char[] password) throws RemoteException;
public class LoginImpl extends Activatable implements Login
public interface Session extends Remote
// your session API here
void logout() throws RemoteException; // explicit logout
public class Session extends UnicastRemoteObject implements Session, Unreferenced
// ... implementation of your session API
// Unreferenced.unreferenced()
public void unreferenced()
    // Log the enforced logout via unreferenced()
    logout();
// logout()
public void logout()
    // Log the logout
    // call UnicastRemoteObject.unexportObject(this, true);
    // and do whatever else you have to do when a client logs out
In the activatable unreferenced methodIn the Unreferenced.unreferenced() method
then I can put the "logout user".And wherever else it should go.
And this should prevent crashes right ?Wrong. It won't prevent crashes. It will detect them.

I created boolean references in my main vi block diagram and copied them to my sub vi front panel. when wire my reference in my main vi to one the input node of the sub vi the wire is broken. the error says its a class conflict why?

i created boolean references in my main vi block diagram and copied them to my sub vi front panel. when wire my reference in my main vi to one the input node of the sub vi the wire is broken. the error says its a class conflict why?

Expanding and clarifying what BJD said;
After you create the temporary sub-VI that BJD mentioned, open its front panel and copy the reference control that LV created when it created the sub-VI.
This reference control will be correct class etc that you need. Use the control to replace the original control that you were attempting to wire up.
The technique of "create sub-VI...copy" always works for me.
There is one more thing that you should watch out for.
The mechanical action of the boolean can not be set for latch action when attempting to read the value using a value property node.
Trying to help,
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

What is the logic for the behavior of LV9 when opening vi references?

I recently started using LV 9 and I can't figure out what the rationale is for the LV 9 behavior when opening references to vis. The way I understand it, LV9 looks up vis using the absolute path on the disk where they came from when opening references, even if they are in memory. If just a vi name is given, LV9 tacks on the path of the referring vi on disk when trying to open the reference. So, as far as I can see, either an application opening references to vis needs to specify absolute paths to the location on disk and be modified whenever a dynamically called vi's location on disk is changed, or a dynamically called vi has to be saved in the same directory as the vi doing the calling or in a rigid and inflexible directory structure.
Example:
I am trying to use a 3rd party library whose vis open a reference to a vi that I create, the name of which is obtained from those in memory using a name pattern. The library vis get the name of the vi I created and try to open a reference to it. Previously this worked because LV looked in memory for "my.vi" when opening the reference but this fails with LV9 because it apparently looks for, e.g., "D:\VI\3rdparty.llb\my.vi", not "my.vi". So, as far as I can see, I have to save my.vi in 3rdparty.llb in order to use it. And, if I want to use 3rdparty.llb in another application, I have to save other vis to 3rdparty.llb or create a new copy elsewhere and save to that copy for the new application. A similar situation would occur if I passed the name of my vi to the 3rdparty.llb vis - either I would need to pass an absolute path and modify my application if I ever want to move my.vi, or save it in 3rdparty.llb.
Another example:
I have a large application built into an executable that calls up to ca. 60 vis using references. Previously I could just specify the path to the executable, and I could easily open references to my vis. Now (if I try to use the LV 9 file structure), I can't figure out the paths I need to open references. Either I have to specify the absolute path to the original location in my development directories, or I have to store all my source vis in some particular directory structure. If I want to reuse my vis in other applications (which I do) things would get pretty complicated. Likewise if I want to optionally open references in other vis than my top level vi (which I do), it seems well nigh impossible.
Basically I am struggling with the concept that an application remembers the directory structure where the source files were located, and/or depends on a particular directory structure of the source files to work. Maybe I'm missing some tricks that would make things easier, but someone will have to explain to me why these are good things.

I appreciate the responses and explanations. I've certainly learned
some things. I have extensive experience using LV but over a fairly
narrow set of
applications so I'm certainly not aware of many of the possible
techniques. I clearly don't use LV in the same way as what appears to
be the mainstream for LV programmers.
I have some additional
comments on the various responses:
"But
with VI libraries and LVOOP this had the problem that multiple VIs could
end up with the same name..."
I'm not clear what this means exactly. My first response would be
that it doesn't seem like a good idea in general to use different
portions of code with the same name in a single application. I'm
surprised this is even possible. I don't think LV will even let me
build from a project in which it finds name conflicts for vis.
"In addition to what Rolf wrote, it should be
pointed out that LV should NOT be looking for files if you built your
app correctly. Each VI maintains a relative path to all VI it calls and
it should know exactly where to find them (assuming they're there).
I think this illustrates one thing I was talking about. The
assumption appears to be that the organization of your source files is
an essential ingredient in the application that is built, which is a
foreign concept to me. My project file knows where all my vis are, the
applications build correctly, and, using the 8.x and previous file
structure for my exe, they work, and have for some time. As far as I'm
concerned the main point of using a project that identifies my source
files is to be able to pull in code from different places - if I want to
use a different version of one of my dynamically called subvis, from a
different location, for example, I tell the project file to use the new
version and rebuild. In your scenario, as I understand it, I'm not sure
why a project file in which you identify source files is even needed,
if LV already knows everything about the components of the application
you're building. As I mentioned, my primary application uses ca. 60
dynamically called vis. Most of these control different subsystems of a
large distributed hardware control and data acquisition system. All of
these are used sometimes when the application is used, but pretty much
never all of them at once - typically something like 10-30 of the
user-interactive vis are run at once. There is some communication
between them using globals, queues, and semaphores and such, but for the
most part they are independent and I test them separately. Until the
application is built and used, there is no need to run the entire
application including all subvis, and I never do it. When I build my
application, the app builder finds all the vis I specify and constructs
the exe file including all the vis I've told it about. Before LV 9 it
never occurred to me that I might actually have to worry about being
able to find vis inside the executable.
"However as tst has mentioned having an
executable search for VIs is a VERY VERY bad idea as it can break your
entire app if it happens to find the wrong VI at some point."
I don't really follow this point at all. Where are these vis
masquerading as the ones I want that will break my application? The only
vis on the machines where my applications are used are there because I
put them there inside the executables. I certainly would never use
different vis with the same name in an application - as I said above, I
don't even know if it is possible, and don't want to find out. Search
paths to find components like shared libraries are a common thing. It
doesn 't seem like a stretch for the run-time environment to define a
default search path like "somewhere in the exe file containing the
application".
I don't want to make a mountain out of a mole hill here, as I said
before, I am happy as long as NI supports the 8.x file structure, but if
nothing else I have definitely learned to appreciate how different
executables built w/ labview are from executables constructed in other
systems.

How can I set up a new network on my apple tv when my remote app isn't picking it up because they aren't on the same network?

How can I set up a new network on my apple tv when my remote app isn't picking it up because they aren't on the same network? The actual remote doesn't work anymore, so I've been using the remote app on my phone but now that our internet changed, I can't do anything at all. Please help!

You can't use the remote app to setup a network. If your physical remote isn't working you will need borrow another or purchase a replacement.

"Index: 0, Size: 0" error when using lexical references

I got "Index: 0, Size: 0" when using lexical references in data template. Can any body tell me what happen? The detail error is:
[042308_084608187][][EXCEPTION] java.lang.IndexOutOfBoundsException: Index: 0, S
ize: 0
at com.sun.java.util.collections.ArrayList.RangeCheck(ArrayList.java:492
at com.sun.java.util.collections.ArrayList.get(ArrayList.java:306)
at oracle.apps.xdo.dataengine.DataTemplateParser.getParentDataSource(Dat
aTemplateParser.java:1802)
at oracle.apps.xdo.dataengine.XMLPGEN.writeDefaultGroup(XMLPGEN.java:329
at oracle.apps.xdo.dataengine.XMLPGEN.writeGroupStructure(XMLPGEN.java:2
84)
at oracle.apps.xdo.dataengine.XMLPGEN.processData(XMLPGEN.java:271)
at oracle.apps.xdo.dataengine.XMLPGEN.processXML(XMLPGEN.java:213)
at oracle.apps.xdo.dataengine.XMLPGEN.writeXML(XMLPGEN.java:252)
at oracle.apps.xdo.dataengine.DataProcessor.processDataStructre(DataProc
essor.java:390)
at oracle.apps.xdo.dataengine.DataProcessor.processData(DataProcessor.ja
va:355)
at oracle.apps.xdo.servlet.data.bind.AdvancedQueryBoundValue11.callDataP
rocessor(AdvancedQueryBoundValue11.java:212)
at oracle.apps.xdo.servlet.data.bind.AdvancedQueryBoundValue11.getValue(
AdvancedQueryBoundValue11.java:101)
at oracle.apps.xdo.servlet.ReportContextImplV11.getReportXMLData(ReportC
ontextImplV11.java:399)
at oracle.apps.xdo.servlet.CoreProcessor.process(CoreProcessor.java:143)

Here is the data template, the lexical reference is &where_clause, thanks.
<dataTemplate name="Tamplate" dataSourceRef="dmdb" defaultPackage="RRBY_PKG">
     <properties>
          <property name="debug_mode" value="on"/>
     </properties>
     <parameters>
               <parameter name="BUName" dataType="character"/>
          <parameter name="StartDate" dataType="date"/>
          <parameter name="EndDate" dataType="date"/>
     </parameters>
<dataTrigger name="beforeReport" source="RRBY_PKG.dynamic_where(BUName => :BUName)"/>
     <dataQuery>
     <sqlstatement name="GroupByAgent">
               <![CDATA[SELECT
NVL(businessunit.name, 'Unassigned') UNITNAME,
queue.name QUEUENAME,
NVL2(businessunit.name, 'Unassigned', businessunit.name || ': ' || queue.name) FULLQUEUENAME,
COUNT(queueEvent.requestNumber) REQNUM
FROM((((queueevent queueevent
INNER JOIN assignment assignment ON queueevent.assignmentkey = assignment.assignmentkey)
INNER JOIN datedim datedim ON queueevent.datekey = datedim.datekey)
INNER JOIN businessunit businessunit ON queueevent.businessunitkey = businessunit.businessunitkey)
INNER JOIN queue queue ON queueevent.forwardedqueuekey = queue.queuekey)
INNER JOIN timedim timedim ON queueevent.timekey = timedim.timekey
WHERE dateDim.FULLDATE >= TO_DATE(:StartDate, 'yyyy-mm-dd')
AND BW_COMMON_DATEADD('s', timeDim.SECONDOFDAY, BW_COMMON_DATEADD('s', queueEvent.EVENTDURATION, dateDim.FULLDATE)) > TO_DATE(:StartDate, 'yyyy-mm-dd')
AND BW_COMMON_DATEADD('s', timeDim.SECONDOFDAY, BW_COMMON_DATEADD('s', queueEvent.EVENTDURATION, dateDim.FULLDATE)) < TO_DATE(:EndDate, 'yyyy-mm-dd') AND &where_clause
group by businessunit.name, queue.name]]>
          </sqlstatement>
     </dataQuery>
</dataTemplate>

Printing to a Printer Connected to TIme Machine when using Remote Desktop

Hi,
I am having trouble printing to a printer connected to our wireless network via Time Capsule when I am on my remote desktop connection. Printing from all other programs work. I downloaded Bonjour on our Windows based server, and it did not detect any printers. When I am connected directly to the printer, I can print when using remote desktop. Any suggestions are much appreciated.
Thanks!
Mac OS X (10.5.4)

Airport Extreme/Express do emulate Jetdirect/port 9100 printing, but that isn't what they use for printing from OS X. OS X and the Bonjour/airport software use USB port redirection, a unique and separate method.
If the HP driver supports any protocol over ethernet, it would be appletalk. Does that router server use appletalk?

Outlook 2013 archiving doesn't work when cached mode is enabled

Hi All,
I have a problem in Outlook 2013 which I've been able to replicate on two separate PCs, operating against two separate Exchange servers. In both cases, archiving of old items does not work in Outlook 2013 when cached mode is enabled. It works
fine if cached mode is switched off so I don't believe the problem is related to the archiving settings.
Has anyone else come across this?
Thanks,
Matt
Systems Engineer
BOM Group LTD

Based on my knowledge, Outlook auto archieve setting is stored in registry and only affects on local host.
If the AutoArchive doesn't work anymore, please refer to the follow article to troubleshoot the issue
http://www.howto-outlook.com/faq/archivenotworking.htm
If we are talking about Microsoft Exchange Online Archiving, I think it would run fine when you in Exchange online mode as your expected.
Tony Chen
TechNet Community Support

Behaviour when caching remote reference..

Similar Messages

Maybe you are looking for