WLDF - Instrumentation for EJB call statistics

Hello,
I'm new with Weblogic and I'm looking for stats concerning my ejbs. I'm using weblogic 10.3.
With JMX I have only found data concerning EJB pool size but no statistics (like execution time)
thus, I'm looking for instrumentation using WLDF to see if it is possible to get the execution time of an EJB method.
Firstly, I try to instrument a method, i've used the following weblogic-diagnostic.xml file.
<wldf-resource xmlns="http://www.bea.com/ns/weblogic/90/diagnostics">
     <instrumentation>
     <enabled>true</enabled>
     <include>com.gemalto.*</include>
     <wldf-instrumentation-monitor>
     <name>ConfigurationManagerBean_Monitor</name>
<enabled>true</enabled>
     <action>DisplayArgumentsAction</action>
<location-type>before</location-type>
<pointcut>execution(public * com.xxx.* get*(...))</pointcut>
     </wldf-instrumentation-monitor>
     </instrumentation>
</wldf-resource>
When I put this file into my MEAT-INF EAR, the deploying is OK but I'cant see nothing into WLDF console extension ?
Could you please explain me a little bit how to configure correctly my instrumentation ?
Thank you a lot.
C.

When I put this file into my MEAT-INF EAR, the deploying is OK but I'cant see nothing into WLDF console extension ?Are there events in the WLDF Archive for the deployed monitor? Have you enabled Instrumentation through a WLDF System Resource targeted to the server?
In order to view instrumentation data through the console extension,
- the WLDF DyeInjection monitor needs to be deployed through the WLDF SystemResouce at server scope as well.
- the application monitors must be of the "Around" type with the TraceElapsedTimeAction assigned to them
Then the console extension can build a call-tree of known requests that have passed through the server, based on each request's Diagnostic Context ID.
If you truly want to view information from the DisplayArgumentsAction, you will need to view the data stored in the WLDF Archive using the WLS Console, or WLST. In the Console, you can view the data by navigating to Diagnostic Modules -> Logs and selecting the EventsDataArchive "log". On the resulting page you can customize your views (the default view only shows you the last 5 minutes of data in the archive, I believe).
Using WLST you can use the exportDiagnosticData (offline) or exportDiagnosticDataFromServer (online) functions. See the WLST help on these functions for details on how to use them.
Mike

Similar Messages

Best Practice for EJB calls from servlet?

Hi folks
I could not find general rules for making calls to an stateful EJB from the web container (e.g. from a backingBean). In some books they say it is a bad programming style calling them directly from a common servlet. The book says create first an HTTPSession Object and from there call the stateful EJB.
I'm a bit confused because, I'm missing some best practice guide from where to initiate such calls.
Can somebody please point me in the right direction?
Kind Regards
Bruno
Edited by: zajoho on Oct 30, 2008 11:14 PM

Hi Bruno,
The main issue with the combination of stateful session beans and servlets is the servlet threading model.
It is dangerous to store a stateful session bean reference in servlet instance state, since the servlet instance
can be accessed concurrently, yet a stateful session bean reference is intended to be used by only one
client.
As you point out, one alternative is to store the reference in the HttpSession. That associates the reference
with a particular client, which matches the stateful session bean programming model.

Call statistics for customer functions (CMOD)

Hi experts,
I wonder, whether R/3 4.6C provides an option to generate a call statistics for customer functions (w/o adding additional logging code in the ZX-includes).
This would be beneficial to identify customer functions called frequently (and to check/improve the performance of these subsequently).
I am aware of a similar feature for BAdIs as well as the coverage analyzer (in NW'04s).
Regards
Thomas

Hello Thomas
On a 4.6c release I would use the following approach:
(1) Identify the transactions which pass user-exits
(2) Analyze transaction log
Regards
Uwe

Bytes taken for a EJB call

Folks -- I looked around for a while but did not find any thing convincing. So if some one can help me here it would be great.
For example when the client makes an EJB call like
this
String getXXX(String yyy) on a RemoteIF -- Many bytes are send back and forth for this call?
Also if some one can point me as to how many bytes does each of the Wrapper version of the primitives take for Remote calls!
For example String, Integer, Long -- individually.
It would really be awesome to get a quick response ;)
Thanks, vk

I'm quite sure the original poster meant the overhead involved with the process of making the call, not the size of some object being transferred either as parameter or as a return value.
I have a feeling it might be rather appserver dependent since it generates the stub/skeleton objects. Overhead for making just the RMI call (disregarding everything else) should be constant, though I don't know what it is.

"Multicast" support for EJB-EJB calls to cluster

What I have to work with:
+ WebLogic Server 5.1 cluster
+ Stateless session EJBs
What I want to do:
+ Be able to know list of available servers in the cluster
and use this list to broadcast same information to all EJBs
with same name in cluster
+ I understand that the cluster-aware EJB stub has this list
when a client gets a home reference to the EJB Object
+ I have not seen any specific WebLogic API to get this list
either by accessing the cluster-aware JNDI table or the
cluster-aware EJB stub.
+ Othwerwise, I would then need to implement my own server
list manager to get this list. Such task should not be that difficult.
Why I want to do the above:
+ I would like to implement a EJB sendAll() method that will
send the same request to all EJBs of the same JNDI name in the cluster.
+ Please correct me if I am wrong but I have not seen anywhere
in the WebLogic 5.1 documentation regarding the automatic multicast
ability of broadcasting EJBs calls via EJB-to-EJB communication to a
cluster.
+ I understand that multicasting is only used internally, ie,
heartbeats.
Plus, I believe that RMI does not support multicasting.

I'd like to hear a bit more about what you are trying to do. (at a
higher level)
RMI / EJB is a point-to-point model. A client is making an RMI call to
a server. Granted, in our clustering solution, there may not be one
physical server, but the idea is to give the appearance of one big,
reliable server.
-- Rob
Ren Bitonio wrote:
>
What I have to work with:
+ WebLogic Server 5.1 cluster
+ Stateless session EJBs
What I want to do:
+ Be able to know list of available servers in the cluster
and use this list to broadcast same information to all EJBs
with same name in cluster
+ I understand that the cluster-aware EJB stub has this list
when a client gets a home reference to the EJB Object
+ I have not seen any specific WebLogic API to get this list
either by accessing the cluster-aware JNDI table or the
cluster-aware EJB stub.
+ Othwerwise, I would then need to implement my own server
list manager to get this list. Such task should not be that difficult.
Why I want to do the above:
+ I would like to implement a EJB sendAll() method that will
send the same request to all EJBs of the same JNDI name in the cluster.
+ Please correct me if I am wrong but I have not seen anywhere
in the WebLogic 5.1 documentation regarding the automatic multicast
ability of broadcasting EJBs calls via EJB-to-EJB communication to a
cluster.
+ I understand that multicasting is only used internally, ie,
heartbeats.
Plus, I believe that RMI does not support multicasting.--
Coming Soon: Building J2EE Applications & BEA WebLogic Server
by Michael Girdley, Rob Woollen, and Sandra Emerson
http://learnweblogic.com

JNDI Lookup in JSP fails for EJB 3.0

I am new to Java technology. I read the EJB FAQ, NetBeans docs and may forum discussions and I am still confused with the error I am having.
Background:
I have developed a persistance bean and related sessions beans (similar to the customer-cmp-ear application in the Java App Server samples). Now I am trying to access this bean using a JSP. After deploying the war file in the App Server and try to access the page, I get the following error.
javax.naming.NameNotFoundException: No object bound to name java:comp/env/ConsumerSessionLocal
After reading many articles, I understood that I dont have to prepare any descriptors, or JAR files for EJB 3.0.
Environment Details:
Java App Server Ver 9.0
NetBeans 5.5
I normally build the war files using NetBeans.
I use App Server Admin console to deploy the web applications using the above war file.
EJB details:
Persistance EJB : person.java
Session Objects
Consumer.java (this implements ConsumerSessionLocal, ConsumerSessionRemote). This Stateless bean accesses the methods in person.java.
ConsumerSessionLocal.java - local interface
ConsumerSessionRemote.java - remote interface
SearchConsumer.jsp
This JSP page is calling the ConsumerSessionLocal using the JNDI lookup through InitialContext.
Here is the Code snippet:
try {
InitialContext ic = new InitialContext();
Object o = ic.lookup("java:comp/env/ConsumerSessionLocal");
ConsumerSessionLocal consSession = (ConsumerSessionLocal) o;
I am able to see the jsp page in the browser, however, after a submit action, I get the Java Naming Exception error.
javax.naming.NameNotFoundException: No object bound for java:comp/env/ConsumerSessionLocal
I would appreciate your help/any of your thoughts.
Thanks in advance.
-Ram

I did not really solve it. Instead I used some of the tutorials that used JNDI lookup and modified those as my way forward. I did not really find out exactly what I was doing wrong.
/Anders

Difference between narrow() method usage and simple class cast for EJB

Hi,
I have a very simple question:
what is the difference between PortableRemoteObject.narrow(fromObj,
toClass) method usage and simple class cast for EJB.
For example,
1)
EJBObject ejbObj;
// somewhere in the code the home.create() called for bean ...
ABean a = (ABean)PortableRemoteObject.narrow(ejbObj,ABean.class);
OR
2)
EJBObject bean;
// somewhere in the code the home.create() called for bean ...
ABean a = (ABean)ejbObj;
Which one is better?
P.S. I'm working with WL 6.1 sp2
Any help would be appreciated.
Thanks in advance,
Orly

[email protected] (Orly) writes:
Hi,
I have a very simple question:
what is the difference between PortableRemoteObject.narrow(fromObj,
toClass) method usage and simple class cast for EJB.
For example,
1)
EJBObject ejbObj;
// somewhere in the code the home.create() called for bean ...
ABean a = (ABean)PortableRemoteObject.narrow(ejbObj,ABean.class);
OR
2)
EJBObject bean;
// somewhere in the code the home.create() called for bean ...
ABean a = (ABean)ejbObj;
Which one is better?(1) is mandated by the spec. It is required because CORBA systems may
not have sufficient type information available to do a simple case.
P.S. I'm working with WL 6.1 sp2 You should always use PRO.narrow()
andy

Simplest way to restrict access to remote EJB calls

I'm using weblogic 10.3 and I'm new to security in weblogic. I was looking at the documentation at http://docs.oracle.com/cd/E13222_01/wls/docs103/ConsoleHelp/taskhelp/security/ManageSecurityForDD.html
but got a little overwhelmed by the many options on how to implement security. Plus, I am getting confused between JDNI security and EJB Layer security (they're not the same thing, right?)
Can someone explain what the simplest way would be to prevent an "unauthorized" client to make remote EJB calls? For example, I know of the ConnectionFilters that you can implement, which can prevent remote callers from making T3 or IIOP calls if they're not from an authorized IP, etc. This is a good start but ideally I would want to password protect the EJBs, and any EJB client would have to provide this username/password somehow. Or possibly use two-way SSL for t3? The client app would have to provide a certificate to prove that it's trusted.
To be clear, I don't think I need weblogic to handle any fine-grained access control. I just want to make sure that the client (e.g., a webapp) is a trusted one. Once the EJB container is satisfied that the client is trusted (preferably by user/pass) then the client is free to execute any EJB methods.
Thanks in advance.
Edited by: user10123426 on Mar 14, 2012 10:26 AM

I'm don't think you can do a posture check by MAC address. If you're using SSLVPN, and you're running Windows, you can do a Host Scan check for the following registry key:
HKLM\System\CurrentControlSet\Services\Tcpip\Parameters\Domain
Then set up a Pre-Login policy that goes Windows->Registry Check->Success->RegCheckOK
|->Fail->RegCheckFail
At this point you've just verified that you can read that key and the value is stored for later use. You're not making an allow/deny decision yet.
Then in your Dynamic Access policy you do a Policy check for Location=RegCheckFail, that says "Unable to read registry". The following DAP policy check looks for Location=RegCheckOK, and validates that the value is your AD domain.
Alternatively, you could put a NAC box (ISE or Clean Access) 'behind/after' the VPN box, so although anyone can connect only domain machines (and/or whatever other posture checks you want to make, e.g. Antivirus status) make it through to the rest of the network.

How to map sync EJB call to async JMS req/resp pair

Folks,
Basically, we have the situation our session bean synchronous
transactions map to asynchronous JMS transactions.
In other words, a session bean method call would have the
following implementation logic:
1. marshall params and send async JMS message.
2. wait around for a reply message to be ready
3. receive a reply JMS message, unmarshall response.
4. return.
The problem, clearly, is that we can't do step 2 in the EJB method itself for fear
of tying up threads.
This seems like a classic problem of mapping synchronous EJB calls to asynchronous
backends.
Any suggestions how to do this?
Thanks,
Jabir

I don't know if there are any great solutions, short of making everything
async
(even to the EJB client) which should be considered if possible. E.g., EJB
sends
JMS message and immediately returns. Then an MDB gets the JMS response,
and calls back the client. If you can't modify the client, maybe you can
write a
"proxy" service between the client and the EJB layer.
Otherwise you'll need to bump the number of threads, knowing that a certain
amount of them will be sleeping.
regards,
-Ade
"Jabir" <[email protected]> wrote in message
news:3d2d14aa$[email protected]..
>
Folks,
Basically, we have the situation our session bean synchronous
transactions map to asynchronous JMS transactions.
In other words, a session bean method call would have the
following implementation logic:
1. marshall params and send async JMS message.
2. wait around for a reply message to be ready
3. receive a reply JMS message, unmarshall response.
4. return.
The problem, clearly, is that we can't do step 2 in the EJB method itselffor fear
of tying up threads.
This seems like a classic problem of mapping synchronous EJB calls toasynchronous
backends.
Any suggestions how to do this?
Thanks,
Jabir

JAVA client JNDI lookup for EJB session in cluster in WLS 5.1

The documentation says :
          to obtain a Context for JNDI lookup do the following :
          Hashtable ht = new Hashtable();
          ht.put(Context.INITIAL_CONTEXT_FACTORY,
          "weblogic.jndi.WLInitialContextFactory");
          ht.put(Context.PROVIDER_URL, "t3://mycluster:7001");
          try {
          Context ctx = new InitialContext(ht);
          // Do the client's work
          catch (NamingException ne) {
          // A failure occurred
          finally {
          try {ctx.close();}
          catch (Exception e) {
          // a failure occurred
          where "mycluster" is the DNS name of my cluster. My DNS server (Windows 200
          DNS server) use round robin
          to call alernatively all the wls server node in "mycluster" and it's OK. The
          two servers of my cluster
          are called alternatively for my EJB session stateless.
          Now I unplug one of the two nodes of my cluster and the remaining server is
          called only 2 times
          and not after.
          Questions :
          -is the load balancing between the nodes of mycluster only rely on DNS or
          is there an internal
          mecanism in EJB sub to try one server then an other ?
          - do I need to obtain a new reference on JNDI Context for each call ?
          Thank's a lot.
          Farid Bellameche.


          I too have the same problem. My scenario is :
          I have the web tier architecture away from cluster. All ejbs are in cluster
          running in two seperate machines. We have a factory class running in
          webtier(we use servlet in this tier) which obtains home interface only once
          and stores it for future reference. When ever we need the remoteobject stub,
          we ask the factory class and which in turn uses the stored home interface to
          get the same.
          In the webtier, I list all the servers in the cluster as a part of url as
          mentioned by you.
          I started the web tier as well as Object tier cluster. I could see the
          request coming in both the machines in the cluster for the ejb. But When I
          bring one the server in the cluster,
          1. Web tier throws an exception saying that it could not connect
          to server using t3.
          2. The other machine which is running the server, also says
          'failed to create socket to : -32323234324 sever name
          using protocol t3.
          It looks like I am able to get load balance. But I am not able to get the
          fail over to be working.
          In the weblogic-ejb-jar.xml, I added the following.
          <clustering-descriptor>
          <home-is-clusterable>true</home-is-clusterable>
          <home-load-algorithm>round-robin</home-load-algorithm>
          </clustering-descriptor>
          I compiled and added the .jar file. So the jar file now has replica aware
          stubs.
          Could any one of you help me for why the fail over is not working?
          Suersh
          "Giri Alwar" <[email protected]> wrote in message
          news:[email protected]...
          > Farid,
          > (1) Yes, the stub has the logic to perform load-balancing and
          fail-over.
          > (2) In almost all cases, no. You can get the context once, store it
          and
          > use it thereafter. Please refer to
          > http://www.weblogic.com/docs51/cluster/concepts.html#1025061 for more
          info.
          >
          > A couple of notes on your situation. From what you are describing, your
          > Windows DNS server is setup to serve only one IP from the cluster (using
          > round-robin) as opposed to a list of all IP's in the cluster. Hence, the
          > initial context you obtain is tied to a single server in the cluster (the
          > one returned by the DNS). The weblogic implementation on the client side
          has
          > no idea of the existence of the other servers in the cluster. This is not
          a
          > cluster aware context. To obtain a cluster aware context, either list all
          > the IP's in the URL like t3://server1,server2,server3:7001 or have
          > "mycluster" return a list of all servers in the cluster.
          >
          > Giri
          >
          >
          > "Farid Bellameche" <[email protected]> wrote in message
          > news:[email protected]...
          > > The documentation says :
          > >
          > > to obtain a Context for JNDI lookup do the following :
          > > Hashtable ht = new Hashtable();
          > > ht.put(Context.INITIAL_CONTEXT_FACTORY,
          > > "weblogic.jndi.WLInitialContextFactory");
          > > ht.put(Context.PROVIDER_URL, "t3://mycluster:7001");
          > > try {
          > > Context ctx = new InitialContext(ht);
          > > // Do the client's work
          > > }
          > > catch (NamingException ne) {
          > > // A failure occurred
          > > }
          > > finally {
          > > try {ctx.close();}
          > > catch (Exception e) {
          > > // a failure occurred
          > > }
          > > }
          > >
          > > where "mycluster" is the DNS name of my cluster. My DNS server (Windows
          > 200
          > > DNS server) use round robin
          > > to call alernatively all the wls server node in "mycluster" and it's OK.
          > The
          > > two servers of my cluster
          > > are called alternatively for my EJB session stateless.
          > > Now I unplug one of the two nodes of my cluster and the remaining server
          > is
          > > called only 2 times
          > > and not after.
          > >
          > > Questions :
          > > -is the load balancing between the nodes of mycluster only rely on DNS
          > or
          > > is there an internal
          > > mecanism in EJB sub to try one server then an other ?
          > >
          > > - do I need to obtain a new reference on JNDI Context for each call ?
          > >
          > >
          > > Thank's a lot.
          > >
          > > Farid Bellameche.
          > >
          > >
          > >
          > >
          >
          >

EJBException::No valid security context for the caller identity

Hi,
I was working with EJB and i had a basic doubt in security propogation from the web tier to EJB tier.
I deployed an EJB on JBOSS app server and in that bean i was trying to get the caller principal object from the EJBContext and i was printing the name of the principal.
System.out.println(ctx.getCallerPrincipal().getName());
then i created ordinary EJB client which is a java class and when i invoked the business method i was getting the below error
Exception in thread "main" javax.ejb.EJBException: java.lang.IllegalStateException: No valid security context for the caller identity
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:63)
at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
This error sounds meaningful but how will i set the security context from the java class. If it can be done then is this the same way that the security principal propogates from web tier to EJB tier.
Thanks,
Suresh B

Hi,
I was working with EJB and i had a basic doubt in security propogation from the web tier to EJB tier.
I deployed an EJB on JBOSS app server and in that bean i was trying to get the caller principal object from the EJBContext and i was printing the name of the principal.
System.out.println(ctx.getCallerPrincipal().getName());
then i created ordinary EJB client which is a java class and when i invoked the business method i was getting the below error
Exception in thread "main" javax.ejb.EJBException: java.lang.IllegalStateException: No valid security context for the caller identity
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:63)
at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
This error sounds meaningful but how will i set the security context from the java class. If it can be done then is this the same way that the security principal propogates from web tier to EJB tier.
Thanks,
Suresh B

How to get logs from CUCM for initiated calls

Dears,
like in Voice Gateway for initiated calls we can run debugs command like debug voip ccapi inout to know the calling and the called number and the status of the call, matched dial-peer, ... etc
Can we do the same in CUCM
Thanks in advance for your help

CDR is used mainly for call statistics, it is not designed for detailed troubleshooting. Reading cucm logs requires a detailed understanding of how different components function and some practice. It can be a little daunting.
This book is excellent. This is what I always recommend as the starting point..
http://books.google.co.in/books?id=YcCjKsssklIC&pg=PA42&lpg=PA42&dq=call+manager+trace+reading&source=bl&ots=ZW5_hvNFGA&sig=22rtALJZjQFfe9JrHjgAB_GgtRU&hl=en&ei=4qT3TLfTDsuYOs_I3YwI&sa=X&oi=book_result&ct=result&redir_esc=y#v=onepage&q=call%20manager%20trace%20reading&f=false
This doc explains how to read h323 traces in cucm
https://supportforums.cisco.com/docs/DOC-11779
This blog explains how to understand sip traces..
https://supportforums.cisco.com/document/113271/understanding-sip-traces

EJB call from one domain to another, authentication problem

Two Weblogic servers. WLS A and WLS B. Different domains. Trust relationship between the domains can't be established.
I have an EJB in WLS B and there is a Web Application deployed to WLS A. There are method-permission declarations in the EJB descriptor xml.
Step 1. User authenticates to Servlet in Web Application (WLS A). Authentication is done with Http Basic Authentication.
Step 2. Servlet makes a JNDI lookup to get a handle to the EJB. Handle can not be fetched with the authentication information which was provided by user to servlet. This means that I need to specify a different username and password, which should be used for authentication at WLS B.
Step 3. After getting a handle to the EJB Servlet calls a method of the EJB.
Everything seems extremely simple. And it should be. But no.
At step 2 servlet propagates authentication information from WLS A to WLS B. This authentication information is valid only inside WLS A, not in WLS B. Result: SecurityException: Invalid Subject.
Setting SECURITY_PRINCIPAL and SECURITY_CREDENTIALS to InitialContext while creating it still results in propagation of authentication information. Same exception.
So I tried something else.
Tthe code doing the JNDI lookups and EJB calls was wrapped inside Security.runAs(new Subject(), ....) -block. Authentication information is no longer propagated to WLS B. So JNDI lookup succeeds, excellent!
But we only got one step further. Now we still need to make the call to EJB method at step 3.
Now that EJB method call results in Security Violation: User: <anonymous> has insufficient permission to access my method.
It's a bit strange, because username and password (for WLS B) were provided for InitialContext while creating it. If the password is invalid, the InitialContext can't be created. So it seems that atleast the username and password ARE checked at WLS B.
Any help and/or suggestions would be highly appreciated.
Here is a misc list of some misc wondering:
-Step 2. Should we make the JNDI lookup to JNDI tree of WLS A instead of WLS B. If we do so, then we should use ejb-ref's at web.xml. This was also quickly tested with no results.
-Would run-as-identity (or some similar element) help? Maybe we could set up some Credential Mapper to WLS A, which would provide username/password when making calls to EJB's of WLS B. Documentation about Credential Mappers seems to be quite useless.

There was a time, and it was quite some time ago when something similar was tried and it didn't meet with much success. Sure, it may not have been Domain files, it may have been something more like, say, rocks, but the general principle still applies. If you look at the XML and media parts that make up a Domain file, you can think of those pieces as analogous to the atoms in your average run-of-the-mill rock. Though the atoms in two given average run-of-the-mill rocks may seem quite similar, and cracking them open reveals innards that are almost entirely, but not quite, the same, it's still quite difficult to make one whole rock out of the two.
Now, some say alchemists might be able to accomplish this quite daunting task, but, until a study of use for Domain files (perhaps XMLchemy?) is initiated and studied most earnestly, we shall probably remain unable to bring about the union of one Domain file and another. Or were we talking about the rocks? (You can't melt Domain files, can you? The thought just hit me is all...)
How's that for a long answer?

ADF 11, USING EJB, CALL STORE PROCEDURE, A PROBLEAM?

ADF 11, USING EJB, CALL STORE PROCEDURE, A PROBLEAM?
I have a store procedure:
CREATE OR REPLACE PACKAGE BODY PK_HR1
IS
FUNCTION FUNC04
RETURN CUR_RESULT
IS
X_CUR CUR_RESULT;
BEGIN
OPEN X_CUR FOR
select mako, tenko, diachiko from kho;
RETURN X_CUR;
EXCEPTION
WHEN OTHERS THEN
RAISE;
END FUNC04;
END PK_HR1;
In the entities class, I have a NamedStoredProcedureQuery:
@Entity
@NamedStoredProcedureQuery(name="Kho.FUNC04",
          resultClass=Kho.class,
          procedureName="PK_HR1.FUNC04" )
public class Kho implements Serializable {
In session bean, i have a method
public class SessionEJBBean implements SessionEJB, SessionEJBLocal
public void test() throws Exception{
try {
//code here ...
List<Kho> listKho = em.createNamedQuery("Kho.FUNC04").getResultList();
System.out.println("aaaa");
} catch (Exception ex) {
ex.printStackTrace();
} finally {
I try running, but always show errror
this errors:
Internal Exception: java.sql.SQLException: ORA-06550: line 1, column 7:
PLS-00221: 'FUNC04' is not a procedure or is undefined
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
Error Code: 6550
Call: BEGIN PK_HR1.FUNC04(); END;
Query: ReadAllQuery(jp.co.mfr.sgs.bean.Kho)
help help me?

You need to use a CallableStatement for this.
--olaf

Non-Immersive Endpoints Call Statistics Reports - jitter, packet loss

Hi,
We are trying to have reports from calls of Non-Immersive Endpoints. We need to have info about jitter and packet loss.
I know it is saved in the logs in file called call_history.txt and available via Web interface under "Diagnostics - Call History".
Issue is how to collect/download such data from Non-Immersive Endpoint automatically. I am not talking about download logs, extract the files, go to specific folder and open specific file.
We have such reports for Immersive Endpoints because Call Statistics are included in MIB.
Any idea/experience to collect such data from Non-Immersive Systems?
Many thanks,
Josef

@Raju_raju
Many thanks for this - its what I expected but its still disappointing to hear. I think Microsoft are missing a trick here, even WebRTC (in Chrome at least) and most other conferencing applications have call statistics built in.
The lack of true real time monitoring in Lync out of the box worries me somewhat. I know that there might be third party options, including Microsoft's own SCOM (which of course, not everybody uses), but I would like to see some real time monitoring of this
real time system as part of its native functionality. True stats available at the client would still be a great help - even if it meant a ALT+Click type procedure.
I need to dig deeper into the normal Lync monitoring options but I'm used to environments where we can analyse each "video hop" as often, there are specific network segments that cause glitches. For instance, in a call where media is routed via
an edge, I would liek to see the stats on the leg from the client to the edge then from the edge to the FEP or Director etc.
Thanks for the heads up on the Snooper documentation. I have read this page previously but will re-visit, yet this is somewhat over kill for some basic real time statistical output.
@Eric - Great table. I must say I have never come across this and it certainly has useful stuff. I can almost understand why Microsoft shows the simplistic feedback by default, but for an advanced user or engineer having to look up the dumbed down feedback
against such a table is simply a waste of time. The actually stats (including both percentage and raw packet loss data) is eminently more useful and immediate.
Microsoft - are you listening?
Chris

WLDF - Instrumentation for EJB call statistics

Similar Messages

Maybe you are looking for