Rmi-iiop1.2.jar and CyberSource cdkjava3300,jar

We are trying to use CyberSource with BEA. When we include
cdkjava3300.jar (from
CyberSource) to WL-classpath with rmi-iiop1.2.jar and test our client,
it throws a " I get
an exception java.lang.UnsatisfiedLinkError: no jsafe in
java.library.path."
Although in WL Commerce server (in sethome.bat)
%WEBLOGIC+HOME%\lib\rmi-iiop1.2.jar is included in WL-CLASSPATH, that
file does
not exist. However, if we remove rmi-iiop1.2 from WL-classpath,
everything works fine
which makes. Any ideas what is going on?
Thank you

rmi-iiop1.2 is an artifact form the beta period for this release. It nolonger exists. That it shows up in a start script what we ship is an, apparently, not so innocuous bug. Fell free to remove it.
I don't understand what the story with jsafe missing is... ask the security guys?
Muhtar Bulut wrote:
We are trying to use CyberSource with BEA. When we include
cdkjava3300.jar (from
CyberSource) to WL-classpath with rmi-iiop1.2.jar and test our client,
it throws a " I get
an exception java.lang.UnsatisfiedLinkError: no jsafe in
java.library.path."
Although in WL Commerce server (in sethome.bat)
%WEBLOGIC+HOME%\lib\rmi-iiop1.2.jar is included in WL-CLASSPATH, that
file does
not exist. However, if we remove rmi-iiop1.2 from WL-classpath,
everything works fine
which makes. Any ideas what is going on?
Thank you

Similar Messages

OOME when doing RMI with wlclient.jar

Hi,
I'm calling EJB-components that are hosted on a WLS 8.1 server.
The client uses wlclient.jar from WLS 9 distribution (WebLogic Server 9.2 Fri Jun 23 20:47:26 EDT 2006 783464) and jre 1.5.0_11.
I get OOME at the client after doing several hundred EJB calls.
I have checked that the client code does not leak ejb-references, initial contexts etc. I have also tried to call ejb remove and close the initialcontext and start anew but it does not help, the "com.sun.corba.se.impl.orbutil.CacheTable" still becomes the top heap consumer.
The outline of how the program proceeds is:
1. create initial context
2. lookup ejb home
3. call the create-method of a stateless session bean
4. call some ejb business methods several hundred times
-- here is the OOME, most often not during the ejb call, but when memory is examined the RMI-implementation objects are filling the heap
5. call ejb remove
6. close initial context
So that's the problem. How could I get around this?
I included some HPROF statistics below. HPROF made the stats immidiately after the OOME . All the top rank rows are related to RMI implementation classes, not application classes.
Regards,
Kari
SITES BEGIN (ordered by live bytes) Tue Oct 06 12:02:10 2009
percent live alloc'ed stack class
rank self accum bytes objs bytes objs trace name
1 10.29% 10.29% 3758560 3614 39151840 37646 310238 byte[]
2 9.31% 19.60% 3400848 45698 3400848 45698 312167 char[]
3 5.46% 25.06% 1994432 62326 3528256 110258 312197 com.sun.corba.se.impl.orbutil.CacheTable$Entry
4 3.21% 28.27% 1172952 8747 1172952 8747 312066 char[]
5 3.00% 31.27% 1096752 45698 1096752 45698 312166 java.lang.String
6 2.90% 34.17% 1059688 6869 1089912 7103 310593 byte[]
7 2.30% 36.47% 838592 26206 2827456 88358 312171 com.sun.corba.se.impl.orbutil.CacheTable$Entry
8 2.19% 38.65% 798200 25112 798200 25112 306612 char[]
9 2.02% 40.67% 738552 30773 769344 32056 310605 java.util.HashMap$Entry
10 1.99% 42.66% 727064 6991 3915184 37646 310235 com.sun.corba.se.impl.encoding.CDROutputStream_1_2
11 1.84% 44.50% 671712 1294 1196448 3818 312195 com.sun.corba.se.impl.orbutil.CacheTable$Entry[]
12 1.84% 46.34% 671712 1294 1196448 3818 312196 com.sun.corba.se.impl.orbutil.CacheTable$Entry[]
13 1.65% 48.00% 604472 6869 625064 7103 310578 com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl
14 1.65% 49.65% 603792 25158 628680 26195 300952 java.util.HashMap$Entry
15 1.65% 51.30% 602688 25112 602688 25112 306611 java.lang.String
16 1.50% 52.80% 549520 6869 568240 7103 310599 com.sun.corba.se.impl.protocol.giopmsgheaders.RequestMessage_1_2
17 1.50% 54.31% 549520 6869 568240 7103 310587 java.util.HashMap$Entry[]
18 1.44% 55.74% 524352 4 524352 4 302751 java.util.HashMap$Entry[]
19 1.26% 57.00% 460632 3387 475592 3497 310457 com.sun.corba.se.impl.interceptors.ClientRequestInfoImpl
20 1.21% 58.21% 441072 9189 2515152 52399 304085 java.nio.HeapByteBuffer
21 1.05% 59.27% 385000 6875 397768 7103 310405 com.sun.corba.se.impl.legacy.connection.SocketFactoryContactInfoImpl
22 1.03% 60.29% 375120 15630 375120 15630 313808 java.lang.StackTraceElement
23 1.00% 61.29% 364728 3507 1939496 18649 309771 com.sun.corba.se.impl.encoding.CDRInputStream_1_2
24 0.96% 62.25% 349696 3877 5040200 58488 310969 char[]
25 0.90% 63.15% 329712 6869 340944 7103 310231 com.sun.corba.se.impl.encoding.CDROutputObject
26 0.77% 63.92% 279904 8747 279904 8747 312070 com.sun.corba.se.impl.orbutil.CacheTable$Entry
27 0.75% 64.67% 275040 6876 365360 9134 304217 char[]
28 0.75% 65.42% 274760 6869 284120 7103 310586 java.util.HashMap
29 0.74% 66.16% 271200 3390 289920 3624 310960 java.util.HashMap$Entry[]
30 0.74% 66.91% 271200 3390 289920 3624 310941 com.sun.corba.se.impl.protocol.giopmsgheaders.ReplyMessage_1_2
31 0.74% 67.65% 271120 3389 287360 3592 311344 java.util.HashMap$Entry[]
32 0.67% 68.32% 243984 10166 257856 10744 310884 java.util.HashMap$Entry
33 0.67% 68.99% 243984 10166 257856 10744 310879 com.sun.corba.se.spi.servicecontext.UnknownServiceContext
34 0.65% 69.64% 239272 2583 908696 10308 300090 char[]
35 0.60% 70.24% 219808 6869 227296 7103 310799 com.sun.corba.se.impl.encoding.BufferManagerWriteStream
36 0.60% 70.84% 219808 6869 227296 7103 310584 com.sun.corba.se.spi.servicecontext.ServiceContexts
37 0.57% 71.42% 209928 8747 209928 8747 312065 java.lang.String
38 0.56% 71.98% 205776 8574 205776 8574 313784 java.lang.StackTraceElement
39 0.54% 72.52% 196800 5427 427112 11183 310920 byte[]
40 0.54% 73.06% 196352 1700 444904 4043 310971 char[]
41 0.47% 73.53% 172056 7169 172056 7169 312484 java.lang.StackTraceElement
42 0.47% 73.99% 170000 2125 178800 2235 311358 java.util.HashMap$Entry[]

Andy Piper wrote:
Configuration:
=============
* Windows 2000 Prof SP3
* Sun JDK 1.4.1_01 (1.4.2)Incidentally you should be using 1.4.1_03 (or later) in the client if
you are using wlclient.jar.I tried some combinations of WL and client JDKs,
even that:
* WL started under Sun JDK 1.4.2
* client started under Sun JDK 1.4.2
* all classes (EJBs, value objects, etc)
compiled under Sun JDK 1.4.2
>
>
FAIL because of java.rmi.MarshalException
weblogic.iiop.IIOPInputStream.checkChunk(IIOPInputStream.java:449)
at
weblogic.iiop.IIOPInputStream.read_longlong(IIOPInputStream.java:1002)There is known bug with reading longs inside a chunked value. This is
fixed in SP2 and the relevant CR is CR124377 - you can get a patch for
SP1 from support.It's realy very nice news for us.
Thank you very match for help and quick response.
Best regards,
Eugene Voytitsky

Can't start RMI server using JAR file

I found it interesting that if I start my RMI server from
a plain directory, everything goes fine.
But if I jar all these necessary files into a jar file,
and start my RMI server with command below
java -jar server.jar
UnmarshalException and ClassNotFoundException are
thrown to indecate that my stub class can't be found
(which I'm sure my stub class is in jar file)
Why is jar file so special that it can't act like
what it originally does when it hasn't been jared?
or I really should take care of some configuration
before I really can run a jar file?
thanks

To clarify few things...
What I don't understand is that when I convert all my
directories and class files properly into the jar file, they
just can't work properly.
I don't know if it's a problem of JAR file,
or it's RMI that make this JAR file special?
I'll simulate my JAR file structure that listed below,
these structure works fine when they have'nt been
converted into JAR file.
META-INF/
META-INF/MANIFEST.MF
a/b/x1.class
a/b/x2.class
a/b/c/Y.class
a/b/c/Y_Skel.class
a/b/c/Y_Stub.class
And when I use command "java -jar server.jar"
to run my application, ClassNotFound exception
is thrown to indecate my stub class is not found.
Is there anything I can do to correct this?
thanks

Some basic questions about rmi registry context "bind" and "lookup"

We have more processing to do than can be accomplished with a single computer. To solve the problem I've implemented a distributed computing solution using RMI. (The first time I saw RMI was about 2 weeks ago, so please bear with me!)
The implementation is a proof of concept not a fully fleshed out system. I have one "Workunit Distributor" computer and any number of "Data Processor" computers all on the same lan segment. "Workunit Distributor" and "Data Processor" computers are both RMI client and server to each other. The "Data Processor" computers are given the ip address and name of the "Data Distributor" on the commandline when they start. They communicate their willingness to receive and process a workunit to the ""Workunit Distributor" via a RMI call. Work units are sent to available "DataProcessors" and results are eventually returned to the "WorkunitDistributor" (minutes or hours later). The model program works quite well, and appears to be capable of doing the processing we need to get done.
But now that it seems viable, I've been asked to make it a little more scalable, flexible and self configuring. In particular, instead of one "Workunit Distributor", any number of "Workunit Distributors" should be allowed to show up or disappear from the lan at any time and the system should continue to function. I've worked out a good scheme for how this can be done, but I have a couple of questions about the RMI registry (registries?). I'm trying to keep from implementing some functionality that may already be available as a library or subsystem.
With my current model design, each computer binds to its own registry with a unique name. For instance:
CRDataProcessorImpl crdpi = new CRDataProcessorImpl(svr);
Context crDataProcessingContext = new InitialContext();
crDataProcessingContext.bind("rmi:"+hostName, crdpi);
Currently the "Data Processors" get the info they need for a Context lookup() of the one and only "Workunit Distributor" from the commandline. And the info the "Workunit Distributor" needs to do a Context lookup() of a "DataProcessor" is passed to it from each "DataProcessor" via a RMI call.
But in the newer (yet to be implemented) scheme where any and all "Workunit Distributors" show up and disappear whenever they feel like, the naming bootstrapping scheme described above won't work.
I can imagine a few ways of solving this problem. For instance, having "Workunit Distributors" multicast their contact information on the lan and have a worker thread on each "Data Processor" keep track of the naming information that was multicast. Another alternative (more organized, but more complex) might be to have a dedicated host with a "well known" address and port that "Workunit Distributors" and "Data Processors" could all go to, to register or look up at an application level. Sort of a "domain name service" for RMI. But both these schemes look like a lot of work to implement , debug and maintain.
The BEST thing would be if there was one plain vanilla RMI registry that was usable by all RMI enabled computers instead of having each computer have its own local name registry. In volume 2 of the Core Java2 book it says that every registry must be local. I'm only hoping there's been progress since the book was published and now a central rmi registry is available.
If you have any ideas about this I'd like to hear what you know.
Thanks in advance for any advice.
Lenny Wintfeld
ps - I don't believe web services, as full featured as it is, is a useful alternative. I'm moving 100's (in the future possibly 1000's) of megabytes back an forth for processing.

The local bind/rebind/unbind restriction is still there and it will always be there.
I would look at
(a) RMI/IIOP, where you use COSNaming as a registry, which doesn't have that registriction, and which also has location-independent object identifiers
(b) Jini.

RMI client losing connection and weblogic.rjvm.PeerGoneException

What causes PeerGoneExceptions? We are seeing this very often on our
production and test systems. We use WLS RMI clients connected to WLS 4.5.1
servers w/ service pack 10. I understand that there is a heartbeat between
the client JVM and the server JVM. Is there any documentation that explains
how this actually works. For example, how often does the client send its
heartbeat. Is it configurable? What could cause it to stop or drop the
connection. We are using straight T3 (no T3S or HTTP).
thanks for your help,
Edwin Marcial
Intercontinental Exchange

What causes PeerGoneExceptions? We are seeing this very often on our
production and test systems. We use WLS RMI clients connected to WLS 4.5.1
servers w/ service pack 10. I understand that there is a heartbeat between
the client JVM and the server JVM. Is there any documentation that explains
how this actually works. For example, how often does the client send its
heartbeat. Is it configurable? What could cause it to stop or drop the
connection. We are using straight T3 (no T3S or HTTP).
thanks for your help,
Edwin Marcial
Intercontinental Exchange

Fundamental question on EJB, JNDI and client jars

Hi,
This is a very fundamental question on EJBs and their clients - what
all should go into the client jar of an ejb?
I know for sure that just the remote and home interface classes of the
ejb are sufficient on the client's classpath to work with an EJB on a
totally different server, but I dont understand the logic behind it.
If the client has to pass its object parameters over the network to
the server where the ejb bean is located, should the container
generated stub not be present on the client's classpath? After the
client does the JNDI lookup of the ejb home on the server, how does it
serialize and pass the parameters over the network if the container
generated stub is not present?
Any help would be greatly appreciated. Pointers to material on the
internet which explain this/related things in detail would be a great
help.
Thank you,
Anoushka

hello,
well, the process is fairly simple actually.. The client needn't necessarily have
the container generated stub. as a client u could contact what is known as a boot-strap
service to download the stub over the wire.. infact one of the advantages of RMI
is precisely that. and since RMI is the underlying architecture of EJBs, it all
becomes rather simple. when u 'lookup' a bean, what u are in essence doing is
asking the server to send down the stub to your JVM. well.. right now this is
what i got time for..i will try to post a lengthier explanation in a couple of
days at leisure..
Vijay
"Anoushka" <[email protected]> wrote:
>
Hi,
This is a very fundamental question on EJBs and their clients - what
all should go into the client jar of an ejb?
I know for sure that just the remote and home interface classes of the
ejb are sufficient on the client's classpath to work with an EJB on a
totally different server, but I dont understand the logic behind it.
If the client has to pass its object parameters over the network to
the server where the ejb bean is located, should the container
generated stub not be present on the client's classpath? After the
client does the JNDI lookup of the ejb home on the server, how does it
serialize and pass the parameters over the network if the container
generated stub is not present?
Any help would be greatly appreciated. Pointers to material on the
internet which explain this/related things in detail would be a great
help.
Thank you,
Anoushka

Wlfullclient jar and preserving jms javadoc

Is there a way in which when creating the wlfullclient jar file that the JMS API classes can either:
a. Be excluded
b. Or contain the javadoc
c. Or is there a way to easily create wlfullclient-sources.jar
Thanks.

a. No. But if you want a WL client jar without JMS capability, then, as an alternative to the full client, you can use the (slower) thin jars. The thin JMS client jar is different jar than the the basic RMI capable thin jar.
b. If you need API information, I think the general approach is to use the standard JEE javadoc, and then reference WebLogic API javadoc extensions (linked from the edoc) as needed. The "Reference" section of the 10.3 edocs sitemap is a good place to start: [http://edocs.bea.com/wls/docs103/sitemap.html].
c. WebLogic does not provide the source for its clients.
Tom

Difference between Naming.lookup and Registry.lookup in RMI

Hi Folks,
I have an RMI client which tries to look up a remote object using both
Naming.lookup("//host[:port]/name OR rmi://<host_name>[:<name_service_port>]/<service_name>") and LocateRegistry.getRegistry().lookup("rmi://<host_name>[:<name_service_port>]/<service_name>").
The first one fails whereas the second one succeeds. I am in a fix as to why it is so.Is there any difference between the lookup methods provided by Naming and Registry?
The remote object was registered on the server using
LocateRegistry.createRegistry().rebind("rmi://<host_name>[:<name_service_port>]/<service_name>").

I suggest you take a look at this site to understand how to ask questions.
And don't crosspost again

RMI recovery and multi-client questions

Hello,
I'm new to RMI and managed to get a sample HelloWorld-code running. After secceeding two major questions came up.
1) If the RMI server is running and the registry server crashes and is restarted, then the new instance of the registry server does know anything about the still running RMI server. What do you need to to that the RMI server rebinds. My idea is that the RMI server must be multithreaded, controls in the background the registry and automatically rebinds after a crash. Any other easier and even better solutions?
2) My impression is that there is one instance of the RMI server waiting for incoming requests. What happens, if a request takes a long time and a second request from a second client comes in? How can it be achieved that one RMI server handles many client requests? I know for database connections ther is something like pooling. Do you need to implement a similar technique for RMI.
3) Would the implementation of a web service avoid the problems mentioned above?
Thanks for any suggestions or hints to related topics.
Regards, Rainer

Hi carr_onstott ,
thanks for clarification and the suggestion to start the name service withing the own application. � need to discuss this approach with the customer, normally there is one and only one name service on a server using the default port. With your suggestion I need to reserve a second portnumber and moreover standard tools providing a list of registered RMI servers will not detect my RMI server.
The problem I see with web services is that we plan to exchange huge binary data byte[] and this is not really what web services are made for. There are sultions to use multibodypart to transfer the XML web service request/response, but the amount of data increases dramatically.
Regards, Rainer

Rmi and http

i know this might sound silly but i am new to rmi ( to java too )
i want to understand the difference between rmi and other protocols such as http,ftp and so.
now what i think i know - and sometimes think im not sure i know or
perhaps im sure i know nothing about - is that rmi is java specific and can only work with java while http is different if im not wrong.. and rmi does not require http r8?
so how can rmi work over http or ftp ..,( can it in the 1st place ?)

Which version of WLS you are using?
Applet should also need to satisfy the version requirements similar to
standalone java client. With WLS 5.1, it may work. But, it will not work
with 6.* servers.
Again, the JRE versions in the Netscape and IExplorer are different. So the
applet, working in IE may not work on Netscape. It is better to test a
sample application, than taking assumptions.
Cheers,
..maruthi
"Andrea Musumeci" <[email protected]> wrote in message
news:3cb1dcba$[email protected]..
can an applet written in java 1.1.x work in a browser using weblogic rmiwithout a plugin? I need to create a java chat applet with callback. Tnx in
advance

RMI-server works on Windows and Linux but not on Solaris

I wrote an application which uses RMI. The server is successfully tested on Windows and Linux. However it doesn't work on Solaris.
Naming.lookup works, I can find the server. But calling a method on my remote interface causes a ConnectionException:
java.rmi.ConnectException: Connection refused to host: 192.168.1.123; nested exception is:
     java.net.ConnectException: Connection refused: connect
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source)
     at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source)
     at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source)
     at sun.rmi.server.UnicastRef.newCall(Unknown Source)
     at at.triton.javaengine.server.ServerImpl_Stub.connectToWindow(Unknown Source)
     at at.triton.javaengine.client.JavaEngineClient.connectToWindow(JavaEngineClient.java:288)
     at at.triton.javaengine.client.JavaEngineClient.main(JavaEngineClient.java:787)
Caused by: java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(Unknown Source)
     at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
     at java.net.PlainSocketImpl.connect(Unknown Source)
     at java.net.SocksSocketImpl.connect(Unknown Source)
     at java.net.Socket.connect(Unknown Source)
     at java.net.Socket.connect(Unknown Source)
     at java.net.Socket.<init>(Unknown Source)
     at java.net.Socket.<init>(Unknown Source)
     at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(Unknown Source)
     at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(Unknown Source)
     ... 7 moreNote that I have almost no experience with Solaris.
Additional information about the common pitfalls which I have already checked:
* rmiregistry finds the server classes (the exception was different without them)
* the server is in the LAN and the desktop firewall of the client is double-checked to let the required ports through to any destination.

java.rmi.ConnectException: Connection refused tohost: >192.168.1.123; nested exception is:
java.net.ConnectException: Connection refused:
: connect
Clearly indicates what is happening inside there.Clearly indicates that you don't know what you are talking about.
Any applications invoked with a security manager must
be granted explicit permission to access local system
resources apart from read access to the directory and
its subdirectories where the program is invoked.Any application that gets a java.net.ConnectionException: Connection
refused is getting it more or less directly from the TCP/IP stack. If the problem had anything to do with policies and permissions and SecurityManagers, it would have been an AccessControlException .
if your client RMI doesnt include these lines then If your 'client RMI' does include these lines then I would like a definition of what exactly a 'client RMI' really is, because I've been using RMI for ten years and wrote a book about it and I certainly don't know.
1)just include these lines
if (System.getSecurityManager() == null) {
System.setSecurityManager(new
SecurityManager());In other words, if the application doesn't already have a security manager, in which case the contents of the policy file or the 'client RMI', or whatever you want to call it, are completely irrelevant, such that they couldn't possibly be having the problem you desrcribe, add a security manager so that we get into the land where you might possibly know what you're talking about?
e a policy file
grant {
permission java.net.SocketPermission
"192.168.1.123:1099", "accept,connect,resolve";
};And this is completely unnecessary if there isn't a security manager, and completely unrelated to the OP's problem.

How can I sign and encrypt massage to send via rmi ??

Hi,,,
I want to sign a massage with RMI client private key and then encrypt the message with the signature using the RMI server public key.
How can I do this ?

I suspect you won't like my answer but a good starting point is "Beginning Cryptography with Java" by David Hook published by Wrox.
P.S. It is much more secure to use RMI with secure sockets since this provides both authentication and encryption and most of the work is done by existing system libraries.

RMI, SSL, and compression

Hi,
I am trying to find an example of how to create a custom socket factory for RMI that does SSL and compression. Doing either separately is easy, but it seems that using SSL precludes the use of a custom socket as one would want for compression. Any suggestions or pointers would be appreciated.
Regards,
Neal

Thank you for the help. Sadly, I am still unable to wrap my brain around this one. I am hoping a concrete example will help out:
public class SecureServerSocketFactory implements java.rmi.server.RMIServerSocketFactory, java.io.Serializable
    /** Creates new SSLServerSocketFactory */
    public SecureServerSocketFactory()
     * Create a server socket on the specified port (port 0 indicates
     * an anonymous port).
     * @param port the port number
     * @return the server socket on the specified port
     * @exception IOException if an I/O error occurs during server socket
     * creation
    public java.net.ServerSocket createServerSocket( int port )
        throws java.io.IOException
         SSLSocketFactory sssf = null;
        ServerSocketFactory ssf = null;
        ClassLoader cl = this.getClass().getClassLoader();
         try
            // set up key manager to do server authentication
            SSLContext ctx;
            KeyManagerFactory kmf;
            TrustManagerFactory tmf;
            KeyStore ks;
            char[] passphrase = "xxxxxxxxxxxxxx".toCharArray();
            ctx = SSLContext.getInstance( "TLS" );
            kmf = KeyManagerFactory.getInstance( "SunX509" );
            tmf = TrustManagerFactory.getInstance( "SunX509" );
            ks = KeyStore.getInstance( "JKS" );
            ks.load( new FileInputStream( SimpleLocator.getInstanceValue( "ServerKeystore") ), passphrase );
            kmf.init( ks, passphrase );
            tmf.init( ks );
            ctx.init( kmf.getKeyManagers(), tmf.getTrustManagers(), null );
            // this is w/o compression
            //ssf = ctx.getSocketFactory();
        catch( Exception e ) { e.printStackTrace(); }
        // need to put ejp's idea to practice here...
        // create a LZMACompressedSocket
        // put it into server mode?
        // wrap in SSL?
        return socket;
    }Any help you can provide would be appreciated.
On a related note, I do agree that compressing at this level likely will not help, but I want to try all solutions.
Thanks again for your help.

RMI/IIOP and WTC

The web docs talk about modifying RMI/IIOP applications to use WTC.
Just need a confirmation that RMI/IIOP calls to EJBs in WLS will not be
transactional. That XA transactions will require the ATMI interface to
Tuxedo EJBs. (Beta in WLS 6.1)

Carl,
I for one would be interested to hear how you are using the Tuxedo/WTC (I
assume you mean Java ATMI) in your application. We need some feedback here
in development land so that we can see which things you like about jATMI and
which things you like less...
Of course, anyone using jATMI can reply as well...
John Wells (Aziz)
[email protected]
[email protected]
"Carl Lawstuen" <[email protected]> wrote in message
news:3bba357d$[email protected]..
Thanks for the clarification. While we will need to support CORBA style
access at some time, the Tuxedo/WTC interface fits nicely in our current
legacy to WLS architecture.
"Andy Piper" <[email protected]> wrote in message
news:[email protected]..
"Carl Lawstuen" <[email protected]> writes:
Yes, the ATMI interface to WTC should be transactional.
But I would assume that RMI/IIOP applications that uses WTC for access
to
WLS naming service would not be transactional due to limitations in
the
RMI/IIOP specification regarding transactions.
Just looking for confirmation that BEA has not done anything to make
RMI/IIOP calls into WLS transactional.RMI-IIOP calls over wtc (i.e. RMI-TGIOP) are transactional and
secure. RMI-IIOP calls over vanilla IIOP are not transactional, but
can be secure. OTS support is coming in Acadia.
RMI-IIOP over wtc totally leverages the ATMI support so you get all
the same features + CORBA-style access. The RMI-IIOP spec is fairly
irrelevant in this instance since we do not have to to support
interoperable transactions to support transaction propagation from Tux
over WTC. That's kind of the whole point - the specs have their rough
edges when it comes to defining transactions and security over IIOP
but we give you exactly what you want (transactions and security)
using the internal tux domains protocol.
andy

WLE 6.1 and RMI

Hi,
Is i possible to have RMI comm. between WLE and a native java program /
applet ?
Or do i need a WL lisence that enables EJB on the webserver ?
TIA,
Borre

Hi,
This is an WLX question i was miss spelling
Borre
"Chuck" <[email protected]> wrote in message
news:3c3b4c2b$[email protected]..
>
Borre,
Is this a Weblogic Server (WLS) or WebLogic Enterprise (WLE) question?Are you
wondering if you need an additional XML 'stanza' in the license.bea foraccessing
an RMI object from a Java client?

Rmi-iiop1.2.jar and CyberSource cdkjava3300,jar

Similar Messages

Maybe you are looking for