EJB client timeout

WL6.1 SP2.
When a client(either in process or standalone) makes a call to a
stateless session bean, the client is blocked until the ejb method
returns. Is there any way for the synchronus call to timeout and throw
either a RemoteException or
TimeoutException after a specified period?
Thanks in advance!
Jimmy

Jimmy <[email protected]> wrote:
Thanks for your replies.
I've tried to set the timeout attibute in the RMI node of the
file s2t2uhEOImplRTD.xml in the temp ejb dir of weblogic
and it does not work. Where do you specify the timeout attribute?
What does RMI DD mean?I don't know what's the official name of xxx_EOImplRTD.xml is - that's what I meant by
RMI DD. You can edit it and put it back into ejb-jar.
Thanks!
Jimmy
"Dimitri I. Rakitine" <[email protected]> wrote in message news:<[email protected]>...
I didn't see any way to specify it using ejbc, but adding it to the
RMI DD works (for RMI timeout) :
<rmi ...
<method name="..." timeout="..."/>
</rmi>
and the remote invocation fails when timeout is exceeded:
weblogic.rmi.extensions.RequestTimeoutException: RJVM response timed out after: '1000' milliseconds.
at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:85)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:262)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:229)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy2.testTimeout(Unknown Source)
Rob Woollen <[email protected]> wrote:
There is a RMI timeout parameter, but I'm not sure if it's exposed in
6.1 or even 7.0. You might be better off asking support. That being
said, I believe it only times out the calling thread. We can't stop the
server thread doing the timed-out work.
-- Rob
Jimmy wrote:
WL6.1 SP2.
When a client(either in process or standalone) makes a call to a
stateless session bean, the client is blocked until the ejb method
returns. Is there any way for the synchronus call to timeout and throw
either a RemoteException or
TimeoutException after a specified period?
Thanks in advance!
Jimmy
Dimitri

Similar Messages

Web service client timeout

Hi,
I'm trying to set a timeout on my web service client. But its not working. Your tutorials do not seem to address this.
I am using weblogic 10.3.2, with Java 1.6.
============
Properties propSys = System.getProperties();
propSys.put( "weblogic.webservice.UseWebLogicURLStreamHandler", "true" );
Stub stub = (Stub)portObject;
BindingInfo bindingInfo = (weblogic.webservice.binding.BindingInfo)stub._getProperty("weblogic.webservice.bindinginfo");
bindingInfo.setTimeout(1);
Iterator itr = stub._getPropertyNames();
while (itr.hasNext()){
Object element = itr.next();
log("\n properties that can be set: "+element);
stub._setProperty("weblogic.webservice.rpc.timeoutsecs","1");
===========
I've also tried setting the transaction-timeout and the remove-client-timeout in the weblogic-ear-jar.xml.
===========
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>ExternalEntryEJB</ejb-name>
<transaction-descriptor>
<trans-timeout-seconds>1</trans-timeout-seconds>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>ExternalEntry</jndi-name>
<remote-client-timeout>1</remote-client-timeout>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>InternalEJB</ejb-name>
<local-jndi-name>Internal</local-jndi-name>
<enable-call-by-reference>True</enable-call-by-reference>
<remote-client-timeout>1</remote-client-timeout>
<transaction-descriptor>
<trans-timeout-seconds>1</trans-timeout-seconds>
</transaction-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
===========
in case it matters, I am using weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask as the clientgen task in my build.xml
============
<clientgen autotype="False" ear="${dist}/${app.earname}" warName="${servlet.warname}" packageName="MyPackage.webservices.client"
keepgenerated="False" useServerTypes="True" clientJar="${dist}/MyAppClient.jar">
<classpath refid="build.classpath.builddir"/>
</clientgen>
============
I am testing by putting a Thread.sleep(75000) in the method which is called in the internal EJB. But the method runs to completion and returns the reply object after 90 seconds or so (it normally takes about 12 seconds), but does not timeout.
I've been told that because it is a web services client, the remote-client-timeout will be ineffective. I've also been told that because the EJBs run in the same JVM, the transaction-timeout will be ineffective. Is this so?
Thanks,
Walter

Can you change the clientgen task to weblogic.wsee.tools.anttasks.ClientGenTask this is for jax-rpc 1.1.
<taskdef name="clientgen"
classname="weblogic.wsee.tools.anttasks.ClientGenTask" />
((Stub)port)._setProperty(weblogic.wsee.transport.connection.timeout,2);
((Stub)port)._setProperty(weblogic.wsee.transport.read.timeoutt,2);
Hope that helps.

EJB Client timing out with PeerGoneException

Environment: WLS 6.1 SP4 on WIn2K.
We have an ejb client calling a StatelessSession bean on the server. From
time to time, if there's a large amount of data
coming across (eg. 5 Meg and above ) the call, invariably we'd get a
PeerGone Exception.
eg.. mySessionEJB.logHistory( String logMsg)
Is there a way to increase the timeout on the call?

Hello
1) The web app is JSP based portal , which sends requests to another server using SOAP as a protocol.
2) The test client in this case , has been developed by us, which just sends requests to the using simple urls . In other words the client simulates a user accessing a JSP page, and requesting information.
3) The request being sent by the client , are to get the data stored on the Back end server. Each request has a specified timeout , configurbel using the web.xml file. In this case we have specified a very large value 0f about 3 hours ( which should be sufficient in most cases ). If the client does not get back the data within the specified time there are two causes
1) The request has not been sent to the back end server
2) The Back end server has not responded within the specified time
But on comparing the CPU usages, the back end server seems to be almost idle. whereas the Application server is consuming close to 100% CPU continuously.
thanks
-Aniruddha

EJB client session

What is an EJB client session? How many are there? When does it start and when does it end? Who controls that?
Thank you.

You may be thinking of a Stateful Session Bean. Each stateful session bean has state that is tied to a
particular client. In EJB 3.0, the stateful session bean is created when the client does a naming
lookup or has the stateful session bean injected. The client can remove the stateful session bean at
any time by calling a method annotated with the @Remove annotation.
The container can also choose to remove a stateful session bean. Typically, the container vendor
provides configuration options that specify the stateful session bean timeout parameters.
--ken

WebLogic Builder remote-client-timeout

Just wondering if anyone has encountered this before.
After using WebLogic Builder to make and save changes to an EAR file the weblogic-ejb-jar.xml file is updated to include the remote-client-timeout tag. This tag causes warning messages in the weblogic console.
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>HelloWorldEJB</ejb-name>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>test.HelloWorldHome</jndi-name>
<remote-client-timeout>0</remote-client-timeout>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Warning Messages
<Nov 2, 2005 4:46:22 PM PST> <Warning> <EJB> <BEA-014009> <Warning: EJB HelloWorldEJB, has the remote-client-timeout set to 0 secs. This timeout specifies a rmi level timeout in seconds for remote clients that call the home and remote methods of the ejb. The method call(s) timeout on the client side after the specified number of seconds. The server will continue to process the request(s) and may change the state. The rmi level timeout shall be set by the container only for non-transactional methods (i.e, method with tx-attributes of Never or Not-Supported). Please ensure that the parameter is used only for methods that are idempotent in nature.>

I think the tool sets the default value for this flag. The default value
should not have any effect. However, I would expect the tool (weblogic
builder) not to insert this element in the descriptor.
More details on this setting can be found here -
http://e-docs.bea.com/wls/docs81/rmi/rmi_api.html#rmi_timeout
--Sathish
<Colin Yeung> wrote in message news:[email protected]..
Just wondering if anyone has encountered this before.
After using WebLogic Builder to make and save changes to an EAR file the
weblogic-ejb-jar.xml file is updated to include the remote-client-timeout
tag. This tag causes warning messages in the weblogic console.
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>HelloWorldEJB</ejb-name>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>test.HelloWorldHome</jndi-name>
<remote-client-timeout>0</remote-client-timeout>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Warning Messages
<Nov 2, 2005 4:46:22 PM PST> <Warning> <EJB> <BEA-014009> <Warning: EJB
HelloWorldEJB, has the remote-client-timeout set to 0 secs. This timeout
specifies a rmi level timeout in seconds for remote clients that call the
home and remote methods of the ejb. The method call(s) timeout on the
client side after the specified number of seconds. The server will
continue to process the request(s) and may change the state. The rmi level
timeout shall be set by the container only for non-transactional methods
(i.e,
method with tx-attributes of Never or Not-Supported). Please ensure that
the parameter is used only for methods that are idempotent in nature.>

Getting an EJB to Timeout

What is the best way to get a Stateless EJB to timeout?
If my application makes a call to an EJB and I want the
maximum length of the call to take X seconds, how do I
accomplish this. If X seconds has passed, I want the EJB
to timeout and return to the client.
Is there some RMI timeout feature? Do I have to create threads
on my own to perform the timeout? What is the best method?
Thanks.

Are you using Container Managed Transactions? If your business method
is declared to execute within a TX (by setting it's TX attribute to
"Required", for example), you can then specify the timeout period for
the transaction in your weblogic-ejb-jar.xml file:
<transaction-descriptor>
<trans-timeout-seconds>60</trans-timeout-seconds>
</transaction-descriptor>
Hope this helps,
Tim

EJB call timeout

Our EJB application is calling another EJB application to provide services for several frontend applications. For some reasons the other EJB application (not under our control) sometimes takes very long time to response, causing our EJB application to hang. Now we want to implement a timeout mechanism for the calls from our EJB application to the other EJB application, but we haven't found a feasible way to implement this timeout mechanism. I appreciate any suggestions or solution.

That's a pretty good question -- typically the problem is inverted where the EJB itself has a client timeout so it can disconnect clients who are not using the system anymore.
There's nothing I can immediately recall which lets a client initiated timeout be set.
I'll ask around and see if we have anything in our InitialContext factories which can define this type of timeout.
-steve-

RMI - How to set a client timeout?

Hey folks,
please don't crucify me, but i googled for "rmi client timeout" and i only found confusing and / or really dated information.
Could somebody enlighten me on how to set a timeout for an RMI-client?
Even an RTFM would be fine, but which?

Hi,
thanks for your insistence.....:-)
ejp wrote:
1. Are you using rmic? UnicastRemoteObject? or some JBoss API?Ehm, for the client?
The client's sourcecode for connecting to the Jboss-Server / my EJB-application is:
Hashtable<String, String> props = new Hashtable<String, String>();
props.put(Context.INITIAL_CONTEXT_FACTORY,"org.jnp.interfaces.NamingContextFactory");
props.put(Context.PROVIDER_URL,"jnp://" + "myhost");
props.put(Context.SECURITY_PRINCIPAL, "myuser");
props.put(Context.SECURITY_CREDENTIALS, "mypassword");
Context ctx = new InitialContext(props);
// get RMI stub
ISendCommand sendCommand = (ISendCommand) ctx.lookup(myjndiname);
String result = sendCommand.sendCommand(myArgs);So i think this corrensponds to "UnicastRemoteObject" from your enumeration?
ejp wrote:
2. How do you know JBoss terminates the connection?Because i have a timeout configured in my EJB-application, but in the example i try to get working, the client shall use its own timeout which is before the EJB-timeout.
The EJB-timeout works, but not the client timeout.....(as described above)
ejp wrote:
3. What happens at the client? An exception? Nothing?"Nothing", i.e. the client terminates when the connection times out (from the JBoss / EJB-side!)
ejp wrote:
4. Are you ignoring any exceptions at the client?No.
Shouldn't this client timeout be totally independent from any server / Jboss / whatever stuff?
Any more ideas?

Using JarSettings to generate EJB client jar, but supported classes missed

Appreciated for any comments in advance.
I am using @jarSetting to generate EJB client jar file from workshop 9.2. The remote method of EJB has one input parameter that is defined as an interface. The interface is included in client jar, but the implementation of this interface is not.
Please advise how I can add the implementation of this interface to client jar?
Best Regards,
James

Hi James,
I believe the algorithm for creating the client jar is to simply inspect the EJB interfaces using reflection and to include all user defined classes and exceptions that are referenced by the interfaces. In your case, it sounds like a class is not being included because it is not directly referenced by one of the EJB interfaces.
I think the client jar creation algorithm can be described as "best effort" and unfortunately, it does not always end up including all classes needed by the client. I would recommend you add the additional classes manually using the jar tool.
- Matt

Hi, I am using HP11 and iPlanet web server. When trying to upload files over HTTP using FORM ENCTYPE="multipart/form-data" that are bigger than a few Kilobytes i get a 408 error. (client timeout).

Hi, I am using HP11 and iPlanet web server. When trying to upload files over HTTP using FORM ENCTYPE="multipart/form-data" that are bigger than a few Kilobytes i get a 408 error. (client timeout). It is as if the server has decided that the client has timed out during the file upload. The default setting is 30 seconds for AcceptTimeout in the magnus.conf file. This should be ample to get the file across, even increasing this to 2 minutes just produces the same error after 2 minutes. Any help appreciated. Apologies if this is not the correct forum for this, I couldn't see one for iPlanet and Web, many thanks, Kieran.

Hi,
You didnt mention which version of IWS. follow these steps.
(1)Goto Web Server Administration Server, select the server you want to manage.
(2)Select Preference >> Perfomance Tuning.
(3)set HTTP Persistent Connection Timeout to your choice (eg 180 sec for three minutes)
(4) Apply changes and restart the server.
*Setting the timeout to a lower value, however, may prevent the transfer of large files as timeout does not refer to the time that the connection has been idle. For example, if you are using a 2400 baud modem, and the request timeout is set to 180 seconds, then the maximum file size that can be transferred before the connection is closed is 432000 bits (2400 multiplied by 180)
Regards
T.Raghulan
[email protected]

How can I run EJB Client in other computer ?

Hello,
I'm trying to run converter examples.
if ejb client pgm resides on a same machine with j2ee server , it works fine.
But when I put client pgm on a different maching
below message show.
No application client descriptors defined for: ConverterClinet
I put ConverterApp.ear, ConverterAppClient.jar and ConverterClient.class on the machine and
set APPCPATH=ConverterAppClient.jar
set VMARGS=-Dorg.omg.CORBA.ORBInitialHost=xxx.xxx.xx.xx
What should I do to run ejb client on different machine?

Hi SangHPark,
I had the same problem but have solved it and it works.
I ran the client remotely from a win98 box.
Keep two things in mind
1> Deploy the applications to an ip address and not to the local host using the deploy too. Use the deploy tool Gui to add a new server and then deploy the application to this ip address.
2> I am running j2ee version 1.3 and jsdk 1.3
Use the following code but instead of using "java:comp/env/ejb/SimpleConverter" use the jndi name of the object: "MyConverter" as specified in the tutorial.
Properties prop = new Properties();
prop.setProperty(Context.INITIAL_CONTEXT_FACTORY,"com.sun.enterprise.naming.SerialInitContextFactory");
prop.setProperty(Context.PROVIDER_URL,"IIOP://xxx.xx.x.xxx:1050");
System.out.println("Attempting to create context...");
Context initial = new InitialContext(prop);
// Instead of this use the below line of code
//Object objref = initial.lookup("java:comp/env/ejb/SimpleConverter");
Object objref = initial.lookup("MyConverter");
// MyConverter is the Jndi name of the ConverterBean as per the tutorial
You need to do the following things.
1> After making changes to the code recompile using Ant and redeploy it.
2> Copy the j2ee.jar, ConverterAppClient.jar and ConverterClient.class file to the machine that u want to run the client from.
3> create a directory called "config" on the remote machine where you copied the files in step two.
4> Copy to this directory the files ejb.properties and security.properties from your j2ee_home\config\ directory.
For example you copied the files in step 2 on the remote machine in the c:\test directory. Create c:\test\config directory and copy the files from step 4 into this directory.
5> Run the following command from the directory where u copied the client files
java -Dorg.omg.CORBA.ORBInitialHost="host name" -classpath .\j2ee.jar;.;.\ConverterAppClient.jar ConverterClient
Monal

Error in running EJB Client on a remote machine

I delploy my beans and can run the EJB Client locally. However when I try to run the Client on another machine, there are errors.
Here is the errors
Syntax error
Out of environment space
Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/enterprise/appclient/Main
I have follow the step in the j2ee tutorial and set the env variables according. Here is the bat file I write
set APPCPATH=CBSAppClient.jar
set VMARGS=-Dj2eelogin.name=guest -Dj2eelogin.password=guest123 -Dorg.omg.CORBA.ORBInitialHost=192.168.0.2
runclient -client CBSApp.ear -name CBSClient -textauth
Do anyone facing the same problem with me?
And how can I solve the problems?
This is really URGENT, please help

You are running on Windows 9x or Me, right? The darn OS has 300 or so bytes allocated for environment by default.
Try setting the Initial environment to 4096 in the Properties|Memory tab for the batch file. That will get rid of "Out of environment space". The syntax error is another matter; Windows (except NT and derivatives) shells do not allow '=' in an environment variables value. You cannot overcome that. Some software (Sybase for instance) interprets # as = just because of that. Unfortunately, the JVM doesn't take such an approach.
Better, grab copies of Unix utilities for Windows (www.gnu.org) including the wonderful shell 'bash' and write .sh scripts, which are inherently more powerful.

Steps to deploy an ejb application and running an ejb client in weblogic server6.1

steps to deploy an ejb application and steps to run an ejb client in weblogic server6.1
if the client is an simple java application and if the client is a servlet

Hi.
Check out the beanManaged example that ships with WLS and read the accompanying docs. This
is a simple EJB with a servlet that invokes it.
Michael
shekhar sachdev wrote:
steps to deploy an ejb application and steps to run an ejb client in weblogic server6.1
if the client is an simple java application and if the client is a servlet--
Michael Young
Developer Relations Engineer
BEA Support

EJB Client Access From JDeveloper9iR2

I seem to be running into a lot of problems when trying to get a simple EJB client to talk to an EJB on our 9IAS platform. I have developed a simple session bean (just to test) which simply returns a string. When I create the default client code this works fine using the embedded OC4J server in Jdeveloper but I can't run a similar client against 9IAS when I deploy the code. When I go through the client wizard it seems to produce the same code as the standalone EJB OC4J client. I simply changed the name of the server (Context.PROVIDER_URL, "ormi://pe2500/). This is the parameter code I use:
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
env.put(Context.SECURITY_PRINCIPAL, "admin");
env.put(Context.SECURITY_CREDENTIALS, "welcome");
env.put(Context.PROVIDER_URL, "ormi://pe2500:23891/MyEJBs");
This is the output I receive:
D:\jdeveloper9ir2\jdk\bin\javaw.exe -ojvm -classpath D:\javadev\ejbservlet\ejbservlet\WEB-INF\classes;D:\jdeveloper9ir2\jdev\lib\jdev-rt.jar;D:\jdeveloper9ir2\j2ee\home\lib\ojsp.jar;D:\jdeveloper9ir2\j2ee\home\jsp\lib\taglib\ojsputil.jar;D:\jdeveloper9ir2\j2ee\home\oc4j.jar;D:\jdeveloper9ir2\j2ee\home\lib\servlet.jar;D:\jdeveloper9ir2\jdev\lib\ojc.jar;D:\jdeveloper9ir2\j2ee\home\lib\activation.jar;D:\jdeveloper9ir2\j2ee\home\lib\ejb.jar;D:\jdeveloper9ir2\j2ee\home\lib\jaas.jar;D:\jdeveloper9ir2\j2ee\home\lib\jaxp.jar;D:\jdeveloper9ir2\j2ee\home\lib\jcert.jar;D:\jdeveloper9ir2\j2ee\home\lib\jdbc.jar;D:\jdeveloper9ir2\j2ee\home\lib\jms.jar;D:\jdeveloper9ir2\j2ee\home\lib\jndi.jar;D:\jdeveloper9ir2\j2ee\home\lib\jnet.jar;D:\jdeveloper9ir2\j2ee\home\lib\jsse.jar;D:\jdeveloper9ir2\j2ee\home\lib\jta.jar;D:\jdeveloper9ir2\j2ee\home\lib\mail.jar;D:\jdeveloper9ir2\j2ee\home\oc4j.jar;D:\jdeveloper9ir2\lib\xmlparserv2.jar;D:\jdeveloper9ir2\lib\xmlcomp.jar;D:\jdeveloper9ir2\j2ee\home\oc4j.jar;D:\jdeveloper9ir2\j2ee\home\lib\servlet.jar Samplemypackage6.ctejb1Client3
javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused: connect; nested exception is:
     java.net.ConnectException: Connection refused: connect
     java.lang.Object com.evermind.server.rmi.RMIContext.lookup(java.lang.String)
          RMIContext.java:134
     java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
          InitialContext.java:350
     void Samplemypackage6.ctejb1Client3.main(java.lang.String[])
          ctejb1Client3.java:18
Process exited with exit code 0.
Can anyone tell me if this is the correct communication method for client EJB's talking to the 9IAS server?
Any help really appreciated.
Chris Taylor

hi Chris Taylor, did you find the solution for this error. i too get this error and i am looking for the answer. if you find any answer please share with me too. if i get any answer for this i will reply you too.

Ejb client error

Hi, I use jdev 10g. I created a session bean with wizards and after that I created I Ejb client for that bean. When I start the embedded server and run the client java file I get the following error :
com.evermind.server.rmi.OrionRemoteException: jazn.com/admin is not allowed to call this EJB method, check your security settings (method-permission in ejb-jar.xml and security-role-mapping in orion-application.xml).
     at denemeSessionHome_StatelessSessionHomeWrapper1.create(denemeSessionHome_StatelessSessionHomeWrapper1.java:41)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:124)
     at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:48)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
     at java.lang.Thread.run(Thread.java:534)
at connection to localhost/127.0.0.1 as admin
     at com.evermind.server.rmi.RMIConnection.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMIConnection.java:1527)
     at com.evermind.server.rmi.RMIConnection.invokeMethod(RMIConnection.java:1480)
     at com.evermind.server.rmi.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:55)
     at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(RecoverableRemoteInvocationHandler.java:22)
     at __Proxy0.create(Unknown Source)
     at ejbpackage.denemeSessionClient.main(denemeSessionClient.java:21)
Process exited with exit code 0.
all settings are the default ones.
Anyone has any idea???

hi
There was no problem with that... the AdviceClient is not in the package... I needed j2ee.jar and AdviceAppClient.jar to run the client and hte AdviceClient is in C\java\Projects\Advice directory.... can anyone help me with what is wrong with my first command which didnt work ...
java -classpath c:\Sun\AppServer\lib\j2ee.jar;c:\java\Projects\Advice;c:\java\Projects\AdviceAppClient.jar AdviceClient
This one worked though....
java -cp {$CLASSPATH}:"C:\java\Projects\Advice";AdviceAppClient.jar;c:\Sun\AppServer\lib\j2ee.jar; AdviceClient
I dont know what makes the difference...
vidhya

EJB client timeout

Similar Messages

Maybe you are looking for