Session Params from Java

Does anyone know how to set an xsql session parameter from within a custom java handler? I looked through the xsql java api and couldn't find anything that would accomplish this.
Thanks
null

XSQL does not have its own API for setting session level parameters. To do this, you should get hold of the HttpServletRequest object, get the Http Session from there, and set the session parameters in the way you would from any servlet.
If what you mean is set XSQL page-level private parameter, then the API to use from within your action handler is:
getPageRequest().setPageParam()

Similar Messages

How to call a Oracle Proc,which contains Object Type as in Param, from java

Hi
Would like to know how to call a Oracle Procedure which contains the Object Type Parameter from java.
Here is my code will look like...
1. CREATE OR REPLACE TYPE emp AS OBJECT
Empno NUMBER,
Ename VARCHAR2(50)
[COLOR=royalblue]In step1 I have created object type.[COLOR]
2.CREATE OR REPLACE PACKAGE ref_pkg IS
TYPE tab_emp IS TABLE OF emp;
END ref_pkg;
[COLOR=royalblue]In step2,I have created a table type which is of type emp;[COLOR]
3. CREATE OR REPLACE PROCEDURE p_emp(p_emptab IN ref_pkg.tab_emp) as
BEGIN
FOR I IN 1..p_emptab.COUNT
LOOP
Some code written here
END LOOP;
END;
[COLOR=royalblue]In step3 I have passed tabletype which is of type emp as argument.[COLOR]
Now I need to invoke this procedure from JAVA.
Calling a procedure doesn�t matter.
But how I can map objecttype ? how will java recognize oracle object ?
How can I implement this ?
Any Help/Clues is Appreciated.
Thanks
Krishna

Hi Bob
You can call a stored proc from a database control with the jc:sql annotation itself.
Assume a stored proc taking one In parameter
* @jc:sql statement="call sp_updateData({id})"
void call_sp_updateCust(int id);
You can even call stored proc with OUT parameters using
* @jc:sql statement="{call sp_MyProc(?, ?)}"
void call_sp_MyProc(SQLParameter[] params)
You can also call stored functions via db control.
More info and diff ways to call at
http://e-docs.bea.com/workshop/docs81/doc/en/workshop/guide/controls/database/conStoredProcedures.html
Thanks
Vimala

SQL Tracing for session started from Java code

I am working with Oracle 10g on Solaris 9. I am facing a problem when trying to enable SQL Trace for Oracle sessions initiated from Weblogic server. I am querring V$SESSION to get the SID and SERIAL# of those sessions and then using DBMS_SYSTEM.SET_SQL_TRACE_IN_SESSION(<sid>, <serial#>, TRUE); from the SQLPlus (using sys login). But the trace file is not being generated in UDUMP even after some queries are fired from the application. But when I am using the same procedure to turn SQL Trace on for SQLPlus sessions or SQLDeveloper sessions, they are just working fine.
Can anyone please help me out?

Please help.....
There is already a thread
Problem with SQL_Trace for a Session
but there is no solution there.

Why?When send a String type param from Java to C,I get An unexpected error.

The error trace like this:
# An unexpected error has been detected by HotSpot Virtual Machine:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x10001d9c, pid=1944, tid=3204
# Java VM: Java HotSpot(TM) Client VM (1.5.0_07-b03 mixed mode, sharing)
# Problematic frame:
# C [sample.dll+0x1d9c]
--------------- T H R E A D ---------------
Current thread (0x00036158): JavaThread "main" [_thread_in_native, id=3204]
siginfo: ExceptionCode=0xc0000005, reading address 0x00000051
Registers:
EAX=0x7ffffffe, EBX=0x26c24ad0, ECX=0x00000051, EDX=0x7fffffff
ESP=0x0007f748, EBP=0x0007f9fc, ESI=0x0007fa38, EDI=0x0007fa88
EIP=0x10001d9c, EFLAGS=0x00010206
Top of Stack: (sp=0x0007f748)
0x0007f748: 0007fa88 0007fa38 26c24ad0 7c930738
0x0007f758: 7fffffff 00000030 7c931596 7c9306eb
0x0007f768: 00000007 00000008 26c24ad0 0007f788
0x0007f778: 0007f7b4 00ae29a4 00000000 22bf60d0
0x0007f788: 10001005 00000000 00000001 00000000
0x0007f798: 0007f790 02eb02b0 0007f7e0 7ffffffe
0x0007f7a8: 00000000 00000051 0007f7dc 0007f7f4
0x0007f7b8: 00000000 00000000 00000000 00000000
Instructions: (pc=0x10001d9c)
0x10001d8c: 89 85 a8 fd ff ff 85 d2 74 1e 8b 8d b0 fd ff ff
0x10001d9c: 0f be 11 85 d2 74 11 8b 85 b0 fd ff ff 83 c0 01
Stack: [0x00040000,0x00080000), sp=0x0007f748, free space=253k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [sample.dll+0x1d9c]
C [sample.dll+0x10ca]
C [sample.dll+0x12e7a]
j HelloWorld.sayHello(Ljava/lang/String;)V+0
j HelloWorld.main([Ljava/lang/String;)V+11
v ~StubRoutines::call_stub
V [jvm.dll+0x86401]
V [jvm.dll+0xdb172]
V [jvm.dll+0x862d2]
V [jvm.dll+0x8d2a2]
C [java.exe+0x14c5]
C [java.exe+0x69cd]
C [kernel32.dll+0x16d4f]
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j HelloWorld.sayHello(Ljava/lang/String;)V+0
j HelloWorld.main([Ljava/lang/String;)V+11
v ~StubRoutines::call_stub
--------------- P R O C E S S ---------------
Java Threads: ( => current thread )
0x00a7f6c8 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=3216]
0x00a7e3c0 JavaThread "CompilerThread0" daemon [_thread_blocked, id=2040]
0x00a7d480 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=1760]
0x00a51f58 JavaThread "Finalizer" daemon [_thread_blocked, id=3212]
0x00a50a70 JavaThread "Reference Handler" daemon [_thread_blocked, id=3208]
=>0x00036158 JavaThread "main" [_thread_in_native, id=3204]
Other Threads:
0x00a4e178 VMThread [id=1952]
0x00a808e0 WatcherThread [id=3220]
VM state:not at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: None
Heap
def new generation total 576K, used 238K [0x22bd0000, 0x22c70000, 0x230b0000)
eden space 512K, 46% used [0x22bd0000, 0x22c0b930, 0x22c50000)
from space 64K, 0% used [0x22c50000, 0x22c50000, 0x22c60000)
to space 64K, 0% used [0x22c60000, 0x22c60000, 0x22c70000)
tenured generation total 1408K, used 0K [0x230b0000, 0x23210000, 0x26bd0000)
the space 1408K, 0% used [0x230b0000, 0x230b0000, 0x230b0200, 0x23210000)
compacting perm gen total 8192K, used 339K [0x26bd0000, 0x273d0000, 0x2abd0000)
the space 8192K, 4% used [0x26bd0000, 0x26c24e90, 0x26c25000, 0x273d0000)
ro space 8192K, 67% used [0x2abd0000, 0x2b12d9f8, 0x2b12da00, 0x2b3d0000)
rw space 12288K, 46% used [0x2b3d0000, 0x2b973808, 0x2b973a00, 0x2bfd0000)
Dynamic libraries:
0x00400000 - 0x0040d000      c:\Program Files\Java\jdk1.5.0_07\bin\java.exe
0x7c920000 - 0x7c9b4000      C:\WINDOWS\system32\ntdll.dll
0x7c800000 - 0x7c91c000      C:\WINDOWS\system32\kernel32.dll
0x77da0000 - 0x77e49000      C:\WINDOWS\system32\ADVAPI32.dll
0x77e50000 - 0x77ee1000      C:\WINDOWS\system32\RPCRT4.dll
0x77be0000 - 0x77c38000      C:\WINDOWS\system32\MSVCRT.dll
0x6d730000 - 0x6d8c7000      c:\Program Files\Java\jdk1.5.0_07\jre\bin\client\jvm.dll
0x77d10000 - 0x77d9f000      C:\WINDOWS\system32\USER32.dll
0x77ef0000 - 0x77f37000      C:\WINDOWS\system32\GDI32.dll
0x76b10000 - 0x76b3a000      C:\WINDOWS\system32\WINMM.dll
0x76300000 - 0x7631d000      C:\WINDOWS\system32\IMM32.DLL
0x62c20000 - 0x62c29000      C:\WINDOWS\system32\LPK.DLL
0x73fa0000 - 0x7400b000      C:\WINDOWS\system32\USP10.dll
0x6d2f0000 - 0x6d2f8000      c:\Program Files\Java\jdk1.5.0_07\jre\bin\hpi.dll
0x76bc0000 - 0x76bcb000      C:\WINDOWS\system32\PSAPI.DLL
0x6d700000 - 0x6d70c000      c:\Program Files\Java\jdk1.5.0_07\jre\bin\verify.dll
0x6d370000 - 0x6d38d000      c:\Program Files\Java\jdk1.5.0_07\jre\bin\java.dll
0x6d720000 - 0x6d72f000      c:\Program Files\Java\jdk1.5.0_07\jre\bin\zip.dll
0x10000000 - 0x10033000      E:\jnis\sample.dll
VM Arguments:
java_command: HelloWorld
Launcher Type: SUN_STANDARD
Environment Variables:
JAVA_HOME=C:\Program Files\Java\jdk1.5.0_07
CLASSPATH=.;.;C:\PROGRA~1\JMF21~1.1E\lib\sound.jar;C:\PROGRA~1\JMF21~1.1E\lib\jmf.jar;C:\PROGRA~1\JMF21~1.1E\lib;
PATH=C:\cygwin\usr\local\bin;C:\cygwin\bin;C:\cygwin\bin;C:\cygwin\usr\X11R6\bin;c:\WINDOWS\system32;c:\WINDOWS;c:\WINDOWS\System32\Wbem;c:\Program Files\Java\jdk1.5.0_07\bin;c:\Program Files\OPENXTRA\Ethereal;c:\Program Files\OPENXTRA\WinDump;d:\Program Files\jProbe\bin;c:\maven-2.0.6-bin\maven-2.0.6\bin;d:\Open Source\apache-ant-1.7.0\bin;d:\swtdlls;d:\Program Files\CVSNT\;c:\Program Files\OPENXTRA\WinPCap
USERNAME=Administrator
OS=Windows_NT
PROCESSOR_IDENTIFIER=x86 Family 15 Model 4 Stepping 9, GenuineIntel
--------------- S Y S T E M ---------------
OS: Windows XP Build 2600 Service Pack 2
CPU:total 1 family 15, cmov, cx8, fxsr, mmx, sse, sse2, ht
Memory: 4k page, physical 515572k(238244k free), swap 1260260k(935080k free)
vm_info: Java HotSpot(TM) Client VM (1.5.0_07-b03) for windows-x86, built on May 3 2006 01:04:38 by "java_re" with MS VC++ 6.0
Java Code like this:
     static{
          try{
               System.loadLibrary("sample");
          }catch(Exception e){
               System.out.println("Can't load sample.dll");
     //Declare native method
     public native void sayHello(String name);
public static void main(String[] args){
    HelloWorld hw=new HelloWorld();
    hw.sayHello("QUKI");
}And C code like this:
JNIEXPORT void JNICALL Java_HelloWorld_sayHello
(JNIEnv *env, jobject obj, jstring s)
     /* Obtain a C-copy of the Java string */
     //printf("Hello,every one");
    const char *str = (*env)->GetStringUTFChars(env, s, 0);
     printf("Java Call C success....%s\n",*str);
}Any one can tell me why??Thanx very much.

const char str = (env)->GetStringUTFChars(env, s, 0);
printf("Java Call C success....%s\n",*str);
Any one can tell me why??Thanx very much.That asterisk(*) in front of str in the printf() statement is dereferencing the variable. Thus it is a char and not a char*. But %s requires a char*.
EXCEPTION_ACCESS_VIOLATION (0xc0000005) Note that when you get the above, with the ...05 error, that it always means you did something incorrect with a pointer somewhere.

How to pass session from Java to Perl

Hi,
I need to pass a session value from Java to Perl, does anyone knows how can I do it?
Thanks

If you want to run java code from Perl, and have it return a single value, that's one thing: but having Perl interact with java code - calling methods, returning values - that may not be possible.
Look into python to see if it may be what you're looking for. It's a scripting language that allows real interaction with java.
If all you want to do is run java code and have it return some data, that would be trivial, so I assume that's not what you mean. But in case it is heres an idea:
Set up a network connection between them with your own protocol, seeing as both languages are good at networking.

How to send a Varying Array param to a PL/SQL Stored Procedure from Java

* I am VERY new to jdbc, and even somewhat new to Java
* I'm using Java 1.5, Oracle 10g.
* I need to call the following PL/SQL Stored Procedure from Java:
procedure setEventStatus
i_deQueueStatus in deQueueStatus_type
*deQueueStatus_type is the following (an array of deQueueStatus_OBJ):
CREATE OR REPLACE TYPE deQueueStatus_OBJ as object
eventID number (20),
dequeuestatus varchar2(20)
CREATE OR REPLACE TYPE deQueueStatus_TYPE IS VARYING ARRAY(500) of deQueueStatus_obj
*I have created a Java object as follows:
public class EventQueueDeQueueStatus
     long      eventID;
     String      dequeueStatus;
     EventQueueDeQueueStatus(long eventID, String dequeueStatus)
          this.eventID = eventID;
          this.dequeueStatus = dequeueStatus;
I have an ArrayList of these.
I need to pass this list to the Stored Procedure. How do I create a java.sql.Array so I can call CallableStatement.setArray to set the parameter? Or do I use something else? I have tried setObject with both the ArrayList and also with a primitive array, but got "Invalid Column Type" both times.
Any help would be greatly appreciated. I just got this task today, and I have to make it work by Tuesday :-( !
Thanks,
Kathy

Kathy,
Search the archives of this forum and the JDBC forum for the terms STRUCT and ARRAY and you can find some sample code on the JDBC How-To Documents page and the JDBC Samples which can both be accessed from this page:
http://www.oracle.com/technology/tech/java/sqlj_jdbc/index.html
Good Luck,
Avi.

Calling Stored Procedures from JAVA Application

Hi all,
i am using JDeveloper 3.2.2 for creating a DB Application that
uses Oracle8i as DB Server.
One approach of the application is to only use PL/SQL Stored
Procedures to write Data back to the DB.
Some of the stored procedures expect more than 20 parameters.
I want to know if there is a better way to call such a stored
procedure from Java than using a CallableStatement and setting
its 20 parameters.
Another reason why the way above isnt possible for me is that
i need a dynamic way to set the parameters of the stored
procedure.
A solution for that dynamic way i could think of is to get
the information of the stored procedure by using some functions
of DatabaseMetaData and than use this information to map the
parameters with their respective variables in the java
application.
The best argument against this way is that it would be time and
performance consuming.
So could anybody tell me a solution to call PL/SQL stored
procedures from java which is better than doing something like:
String calString = "{Call myStoredProc(";
while(counter < 22) {
params += "?";
if(counter<21) params += ",";
counter++;
calString += params + ")}";
try {
CallableStatement cs = session.prepareCall(calString);
} catch(SQLException ex) { ... }
cs.setString(1, var1);
cs.setString(1, var2);
And that for every Stored Procedure i want to call ?!?
Any help or direction-leading would be really appreciated.
Tank you much.
MfG,
Oliver Bankel

Hi Oliver,
If you your Stored Procedures were in Java and seamlessly
integrated with your Java application would that make your life
easier?
I don't know if this is a practical or acceptable solution in
your environment but it would certainly solve all of your issues
and provide your with a couple of nice advantages. Scalability
and platform independence are just a couple I could think of.
There is a tool called in2j (see http://www.in2j.com) which will
automatically migrate your PL/SQL Stored Procedures into Java.
You can download a copy of the tool and migrate your PL/SQL to
Java with no upfront costs. If you're happy with the generated
Java and want to deploy it, the migration fee falls due - simple.
Hope this helps.
Elton

Xsql:set-session-param

I experience a problem with exception arising when I try to set session parameter and then to post to a page with insert-request.
Here is exception message:
XSQL-018: Unexpected Error Occurred processing stylesheet null
oracle.xml.parser.v2.XMLDOMException: Node of this type cannot be added.
at oracle.xml.parser.v2.XMLDocument.checkChildType(XMLDocument.java, Compiled Code)
at oracle.xml.parser.v2.XMLNode.appendChild(XMLNode.java, Compiled Code)
at oracle.xml.parser.v2.XMLDocument.appendChild(XMLDocument.java, Compiled Code)
at oracle.xml.parser.v2.XMLNode.appendChild(XMLNode.java, Compiled Code)
at oracle.xml.parser.v2.XMLDocument.appendChild(XMLDocument.java, Compiled Code)
at oracle.xml.parser.v2.XMLNode.appendChild(XMLNode.java, Compiled Code)
at oracle.xml.xsql.XSQLStylesheetProcessor.processToDocument(XSQLStylesheetProcessor.java:66)
at oracle.xml.xsql.actions.XSQLInsertRequestHandler.handleAction(XSQLInsertRequestHandler.java:82)
at oracle.xml.xsql.XSQLDocHandler.getDocument(XSQLDocHandler.java, Compiled Code)
at oracle.xml.xsql.XSQLPageProcessor.process(XSQLPageProcessor.java, Compiled Code)
at oracle.xml.xsql.XSQLServlet.doGet(XSQLServlet.java, Compiled Code)
at oracle.xml.xsql.XSQLServlet.doPost(XSQLServlet.java:81)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:521)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
at org.apache.jserv.JServConnection.processRequest(JServConnection.java, Compiled Code)
at org.apache.jserv.JServConnection.run(JServConnection.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
Using 1.0.4.1 production xsql servlet.
Code to set param:
<xsql:set-session-param name="issuethesid" value="aaa" only-if-unset="yes"/>
Code for the page producing error
<?xml version="1.0"?>

<page connection="coastbase" xmlns:xsql="urn:oracle-xsql">
<xsql:include-request-params/>
<xsql:insert-request
table="domain"
transform="coastbaseinsert.xsl"/>
<xsql:set-page-param name="CURRENTID">
SELECT ID_SEQ.CURRVAL FROM DUAL
</xsql:set-page-param>
<xsql:include-param name="CURRENTID"/>
</page>
Works everything but insert-request.

This error usually occurs when your transformation produces an illegal XML fragment.
If you temporarily rename the transform attribute to transformXXX so that the inbound XSLT transformation is not performed, does the stack trace go away?

Accessing the same stateful session bean from multiple clients in a clustered environment

I am trying to access the same stateful session bean from multiple
          clients. I also want this bean to have failover support so we want to
          deploy it in a cluster. The following description is how we have tried
          to solve this problem, but it does not seem to be working. Any
          insight would be greatly appreciated!
          I have set up a cluster of three servers. I deployed a stateful
          session bean with in memory replication across the cluster. A client
          obtains a reference to an instance of one of these beans to handle a
          request. Subsequent requests will have to use the same bean and could
          come from various clients. So after using the bean the first client
          stores the handle to the bean (actually the replica aware stub) to be
          used by other clients to be able to obtain the bean. When another
          client retrieves the handle gets the replica aware stub and makes a
          call to the bean the request seems to unpredictably go to any of the
          three servers rather than the primary server hosting that bean. If the
          call goes to the primary server everything seems to work fine the
          session data is available and it gets backed up on the secondary
          server. If it happens to go to the secondary server a bean that has
          the correct session data services the request but gives the error
          <Failed to update the secondary copy of a stateful session bean from
          home:ejb20-statefulSession-TraderHome>. Then any subsequent requests
          to the primary server will not reflect changes made on the secondary
          and vice versa. If the request happens to go to the third server that
          is not hosting an instance of that bean then the client receives an
          error that the bean was not available. From my understanding I thought
          the replica aware stub would know which server is the primary host for
          that bean and send the request there.
          Thanks in advance,
          Justin


          If 'allow-concurrent-call' does exactly what you need, then you don't have a problem,
          do you?
          Except of course if you switch ejb containers. Oh well.
          Mike
          "FBenvadi" <[email protected]> wrote:
          >I've got the same problem.
          >I understand from you that concurrent access to a stateful session bean
          >is
          >not allowed but there is a
          >token is weblogic-ejb-jar.xml that is called 'allow-concurrent-call'
          >that
          >does exactly what I need.
          >What you mean 'you'll get a surprise when you go to production' ?
          >I need to understand becouse I can still change the design.
          >Thanks Francesco
          >[email protected]
          >
          >"Mike Reiche" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >> Get the fix immediately from BEA and test it. It would be a shame to
          >wait
          >until
          >> December only to get a fix - that doesn't work.
          >>
          >> As for stateful session bean use - just remember that concurrent access
          >to
          >a stateful
          >> session bean is not allowed. Things will work fine until you go to
          >production
          >> and encounter some real load - then you will get a surprise.
          >>
          >> Mike
          >>
          >> [email protected] (Justin Meyer) wrote:
          >> >I just heard back from WebLogic Tech Support and they have confirmed
          >> >that this is a bug. Here is their reply:
          >> >
          >> >There is some problem in failover of stateful session beans when its
          >> >run from a java client.However, it is fixed now.
          >> >
          >> >The fix will be in SP2 which will be out by december.
          >> >
          >> >
          >> >Mike,
          >> >Thanks for your reply. I do infact believe we are correctly using
          >a
          >> >stateful session bean however it may have been misleading from my
          >> >description of the problem. We are not accessing the bean
          >> >concurrently from 2 different clients. The second client will only
          >> >come into play if the first client fails. In this case we want to
          >be
          >> >able to reacquire the handle to our stateful session bean and call
          >it
          >> >from the secondary client.
          >> >
          >> >
          >> >Justin
          >> >
          >> >"Mike Reiche" <[email protected]> wrote in message
          >news:<[email protected]>...
          >> >> You should be using an entity bean, not a stateful session bean
          >for
          >> >this application.
          >> >>
          >> >> A stateful session bean is intended to be keep state (stateful)
          >for
          >> >the duration
          >> >> of a client's session (session).
          >> >>
          >> >> It is not meant to be shared by different clients - in fact, if
          >you
          >> >attempt to
          >> >> access the same stateful session bean concurrently - it will throw
          >> >an exception.
          >> >>
          >> >> We did your little trick (storing/retrieving handle) with a stateful
          >> >session bean
          >> >> on WLS 5.1 - and it did work properly - not as you describe. Our
          >sfsb's
          >> >were not
          >> >> replicated as yours are.
          >> >>
          >> >> Mike
          >> >>
          >> >> [email protected] (Justin Meyer) wrote:
          >> >> >I am trying to access the same stateful session bean from multiple
          >> >> >clients. I also want this bean to have failover support so we want
          >> >to
          >> >> >deploy it in a cluster. The following description is how we have
          >tried
          >> >> >to solve this problem, but it does not seem to be working. Any
          >> >> >insight would be greatly appreciated!
          >> >> >
          >> >> >I have set up a cluster of three servers. I deployed a stateful
          >> >> >session bean with in memory replication across the cluster. A client
          >> >> >obtains a reference to an instance of one of these beans to handle
          >> >a
          >> >> >request. Subsequent requests will have to use the same bean and
          >could
          >> >> >come from various clients. So after using the bean the first client
          >> >> >stores the handle to the bean (actually the replica aware stub)
          >to
          >> >be
          >> >> >used by other clients to be able to obtain the bean. When another
          >> >> >client retrieves the handle gets the replica aware stub and makes
          >> >a
          >> >> >call to the bean the request seems to unpredictably go to any of
          >the
          >> >> >three servers rather than the primary server hosting that bean.
          >If
          >> >the
          >> >> >call goes to the primary server everything seems to work fine the
          >> >> >session data is available and it gets backed up on the secondary
          >> >> >server. If it happens to go to the secondary server a bean that
          >has
          >> >> >the correct session data services the request but gives the error
          >> >> ><Failed to update the secondary copy of a stateful session bean
          >from
          >> >> >home:ejb20-statefulSession-TraderHome>. Then any subsequent requests
          >> >> >to the primary server will not reflect changes made on the secondary
          >> >> >and vice versa. If the request happens to go to the third server
          >that
          >> >> >is not hosting an instance of that bean then the client receives
          >an
          >> >> >error that the bean was not available. From my understanding I
          >thought
          >> >> >the replica aware stub would know which server is the primary host
          >> >for
          >> >> >that bean and send the request there.
          >> >> >
          >> >> >Thanks in advance,
          >> >> >Justin
          >>
          >
          >

Error while running EJB from java client on JBOSS

Hi
As i am new to EJB i have created a helloworld application in ejb which is working fine when i try to call it from servlet but when i try to invoke the same ejb from java client (i.e from diff jvm) on jboss i got the following error:
javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]]]
     at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1399)
     at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:579)
     at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at com.gl.TestClient.main(TestClient.java:39)
Caused by: javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]]
     at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:254)
     at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1370)
     ... 4 more
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]
     at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:228)
     ... 5 more
Caused by: java.net.ConnectException: Connection refused
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
     at java.net.Socket.connect(Socket.java:519)
     at java.net.Socket.connect(Socket.java:469)
     at java.net.Socket.<init>(Socket.java:366)
     at java.net.Socket.<init>(Socket.java:266)
     at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:69)
     at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:62)
     at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:224)
     ... 5 more
Following is my code:
Home Interface:
package com.gl;
import javax.ejb.CreateException;
public interface testHome extends EJBHome {
     String JNDI_NAME = "testBean";
     public     test create()
     throws java.rmi.RemoteException,CreateException;
Remote Interface:
package com.gl;
import java.rmi.RemoteException;
import javax.ejb.EJBObject;
public interface test extends EJBObject {
     public String welcomeMessage() throws RemoteException;
Bean:
package com.gl;
import java.rmi.RemoteException;
import javax.ejb.EJBException;
import javax.ejb.SessionBean;
import javax.ejb.SessionContext;
public class testbean implements SessionBean {
     public void ejbActivate() throws EJBException, RemoteException {
          // TODO Auto-generated method stub
     public void ejbPassivate() throws EJBException, RemoteException {
          // TODO Auto-generated method stub
     public void ejbRemove() throws EJBException, RemoteException {
          // TODO Auto-generated method stub
     public void setSessionContext(SessionContext arg0) throws EJBException,
               RemoteException {
          // TODO Auto-generated method stub
     public void ejbCreate(){}
     public String welcomeMessage(){
          return "Welcome to the World of EJB";
ejb-jar.xml:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>testBean</ejb-name>
<home>com.gl.testHome</home>
<remote>com.gl.test</remote>
<ejb-class>com.gl.testbean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
</ejb-jar>
jboss.xml:
<?xml version='1.0' ?>
<!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 3.2//EN" "http://www.jboss.org/j2ee/dtd/jboss_3_2.dtd">
<jboss>
<enterprise-beans>
<entity>
<ejb-name>testBean</ejb-name>
<jndi-name>testBean</jndi-name>
</entity>
</enterprise-beans>
</jboss>
Client code:
package com.gl;
import java.util.Properties;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.rmi.PortableRemoteObject;
public class TestClient {
     public static void main(String[] args) throws Exception{
               try{
               /*     Properties props=new Properties();
                    props.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
                    props.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
                    props.put(Context.PROVIDER_URL, "jnp://localhost:1099");
               Properties props = new Properties();
props.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jnp.interfaces.NamingContextFactory");
props.put(Context.PROVIDER_URL, "localhost:1099");
                    System.out.println("Properties ok");
                    //env.setProperty(Context.INITIAL_CONTEXT_FACTORY,"org.jboss.naming.HttpNamingContextFactory");
                    //env.put(Context.PROVIDER_URL,"http://localhost:8080");
                    //env.put(Context.SECURITY_PRINCIPAL, "");
                    //env.put(Context.SECURITY_CREDENTIALS, "");
                    Context ctx=new InitialContext(props);
                    System.out.println("context ok");
                    //testHome home = (testHome)ctx.lookup("testBean");
                    Object obj = ctx.lookup ("testBean");
                    System.out.println("ojb = " + obj);
                    testHome ejbHome = (testHome)PortableRemoteObject.narrow(obj,testHome.class);
               test ejbObject = ejbHome.create();
               String message = ejbObject.welcomeMessage();
                    System.out.println("home ok");
                    System.out.println("remote ok");
                    System.out.println(message);
                    catch(Exception e){e.printStackTrace();}
I am able to successfully deployed my ejb on JBOSS but i m getting above error when i am trying to invoke ejb from java client.
kindly suggest me something to solve this issue.
Regards
Gagan
Edited by: Gagan2914 on Aug 26, 2008 3:28 AM

Is it a remote lookup? Then maybe this will help:
[http://wiki.jboss.org/wiki/JBoss42FAQ]
- Roy

Calling Local Stateless session bean from Spring in weblogic 10.3

We are in the process of upgrading to Weblogic 10.3 from OC4J (OAS). We are using Spring and Stateless Session EJB 3 Local beans (Don't ask me why, it is decided before I came to the project).
Previously (OC4J):
-> There is no ejb-jar.xml. EJBs are configured with annotation @Stateless. No "name" or "mappedName" are defined.
Spring POJOs access EJBs by using "EJBMODULENAME_<<EJBBeanClass>>Local" as JNDI Name. I think this strange JNDI name is what OC4J assigns when there is no explicit JNDI name defined.
Sample Spring Bean configuration -
<bean name="securityEJB" class="org.springframework.ejb.access.LocalStatelessSessionProxyFactoryBean" lazy-init="true">
          <property name="jndiName">
               <value>myapp-ejb_SecurityEJBImplLocal</value>
          </property>
          <property name="resourceRef">
               <value>false</value>
          </property>
          <property name="businessInterface">
               <value>my.package.SecurityEJB</value>
          </property>
     </bean>
I understand that weblogic 10.x doesn't give any global JNDI name (JNDI tree is empty) and also looked at the blog, Link: [http://m-button.blogspot.com/2008/07/reminder-on-how-to-use-ejb3-with.html]
So far I have tried,
1. @EJB annotation works but, I don't want to add @EJB annotations in the entire application. Since we are using Spring and EJB3, I am trying to avoid mixing them -
2. java:comp/env is supposed to work (since it is a local session bean), but it doesn't for me.
I haven't added weblogic-ejb-jar.xml as I don't think it is going to help, as there is no global JNDI name defined. Am I missing some thing?
Thx

Hi,
if you don't want to use @EJB to inject the EJB, then you'll need declare the EJB reference in deployment descriptor.
Here is an example copied from EJB3 spec:
<ejb-local-ref>
<description>
This is a reference to the local business interface
of an EJB 3.0 session bean that provides a payroll
service.
</description>
<ejb-ref-name>ejb/Payroll</ejb-ref-name>
<local>com.aardvark.payroll.Payroll</local>
</ejb-local-ref>
then you can lookup the local ejb from "java:comp/env/ejb/Payroll".

Calling web service from Java

Hi,
Can anyone help me in calling a web service url from java client?
Regds,
Nandakumar

sample code:
static string url = "http://my.webservice.url"; ---------------> The actual web service URL
Call = new Call(url); --------------------------------------------------> The call object used by JAX-RPC
Object[] params = new Object[]{param1, param2};---------> build the call parameters
Boolean/Integer/Whatever result = call.invoke("method name", params);------>call the invoke method to get the result

How to call session EJB from EP service in EP 7.0?

Hi,
I am trying to invoke stateless session EJB from my portal service. Both the service and EJB are deployed on the same server which is EP 7.0.
I found [this|http://help.sap.com/saphelp_nw70/helpdata/EN/42/9ddcc9bb211d72e10000000a1553f6/frameset.htm] in SAP help and tried to implement it (added PrivateSharingReference to portalapp.xml and implemented the code), but everytime I try to lookup the session bean and cast it using P4ObjectBroker.narrow() method, I get java.lang.ClassCastException. The object found in JNDI and my portal service have different classloaders, so I suppose this is the problem, but I don't know how to handle it...
Can anyone please help me?
Regards,
Tomas

Hi Satya ,
please go though following blog for used DC concept.
Componentization of Webdynpro Application in CE7.1
In netweaver 7.1 interface controler is abstract and component controller is implementing interface controller so the context data and methods have to be implemented by component controller

JNDI Naming Problem accessing Session Bean from Message Driven Bean

Hi,
     I am facing a very strange problem in JNDI look up accessing a Session Bean from a Message Driven Bean. I have a session fa�ade bean(Remote Bean) which is being called from Struts Action class getting the home reference from the ServiceLocator (I have implemented ServiceLocator pattern to obtain JNDI reference for all EJBs). When I am calling the session fa�ade EJB from the Struts Action class everything is working fine.
     But when I am trying to call the same EJB from my Message Driven Bean, I am getting a JNDI exception (NameNotFoundException - No Object bound to name �java:comp/env/ejb/EJBJNDIName�). I am trying to get the remote reference from the same ServiceLocator which is successfully providing me a reference while calling from the struts action class. But the same ServiceLocator is not able to provide me a reference while calling from the Message Driven Bean. If I use the JNDI name directly like �EJBJNDIName� in the lookup it is working fine. The lookup for the name is working fine and I am able to call the Session Fa�ade bean with that reference.
     I am really not sure what exactly the problem is. If I have any problem in the ServiceLocator, it should have given me the same error while calling from Struts Action class. But it is working fine with the full name �java:comp/env/ejb/EJBJNDIName� calling from the struts action class. I am not sure whether Message Driven Bean has something to do with it. Why I am not able to get a reference of the EJB with the full name? Please Help.
Thanks
Amit

Hi Bhagya,
Thanks for your response. I think from EJB container we can call Local EJBs with the full JNDI name. The session facade bean which is being called is a remote bean. From the session facade bean I am calling a local stateless session bean for database access. I am getting the reference of the local EJB from my session facade bean with full JNDI name "java:comp/env/ejb/EJBJNDIName". It is working fine with out any problem. My servicelocator is able to provide me the reference of the local EJB from the session facade remote bean with Full JNDI name. I am only having this problem calling from the MDB. I am really not sure whether what is causing it?
Thanks
Amit

How can i lookup a session bean from the client side

how can i lookup a session bean from the client side...........i am using sun appserver..............
this is my code.................[B]
private final static String JNDI_NAME="ejb/LmsBean";
private static String url="ldap://localhost:4848";
Hashtable h=new Hashtable();
h.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.ldap.LdapCtxFactory");
h.put(Context.PROVIDER_URL,url);
System.out.println("Before Loading Context in Delegate");
Context ctx=new InitialContext(h);
System.out.println("Loaded Context in Delegate");
Object obj=ctx.lookup(JNDI_NAME);
System.out.println("Loaded Object in Delegate");
System.out.println("Before Loading Home in Delegate");
LmsHome home = (LmsHome )PortableRemoteObject.narrow(obj,com.parx.lms.controller.LmsHome.class);
System.out.println("Loaded Home in Delegate");
lms = home.create();
System.out.println("Loaded remote in Delegate");
[B]and i got the exception........
Inside Client before calling delegate
Before Loading Context in Delegate
javax.naming.CommunicationException: Request: 1 cancelled
javax.naming.CommunicationException: Request: 1 cancelled
at com.sun.jndi.ldap.LdapRequest.getReplyBer(LdapRequest.java:60)
at com.sun.jndi.ldap.Connection.readReply(Connection.java:405)
at com.sun.jndi.ldap.LdapClient.ldapBind(LdapClient.java:340)
at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:171)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2640)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:290)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.ja
va:136)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.jav
a:66)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
62)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.parx.lms.lmsdelegate.LmsDelegate.getController(LmsDelegate.java:3
0)
at com.parx.lms.lmsdelegate.LmsDelegate.addUserDelegate(LmsDelegate.java
:50)
at com.parx.lms.client.consoleClient.Client.main(Unknown Source)
pls go tru the exception and pls help.........

That url string should be having the server name or ip instead of localhost.

Session Params from Java

Similar Messages

Maybe you are looking for