Exception handling in rmi in client side

Hello everybody, I'm developing a small client-server application using JDBC and RMI .
I would like to ask if any body can help to know how handle exceptions thrown in the server side and show them for the client.
Any help will be appreciated

I prefer not to have the server's exceptions known to the client. The client only gets the exceptions the client expects. This is part of the server interface which is defined and owned by the client.
So any exception thrown on the server I would handle and rethrow a different appropriate exception up to the client.

Similar Messages

Uncaught exception raised in Open Directory client-side plugin

I am having an issue whenever I try to access my Open Directory. It says Uncaught exception raised in Open Directory client-side plugin.
In updateConfigurationViewFromDescription: NSInvalidArgumentException *** - [NSplaceholderMutableString initWithString:]: nil argument.
I'm having a hard time finding a directory with the relative plugin. Could you point me the right way? Perhaps finding and deleting that little bugger would help? I'm running Lion Server 10.7.3 with the 10.7.3 Server Admin tools. The goal here is to set up Deploy Studio for our organization, which I had working for a little while until this little guy started rearing his ugly head.
Thanks much-

Dear cdolan92,
not really. It has been a while. I think I also deleted server.app and admin tools and reinstalled those.
Perhaps I even did a backup of open directory and turned off the master to local and back to master.
But I am not sure any more.
Sorry.
Best
H.

Client side handling of exceptions thrown by a webservice

I have a webservice that is deployed in Tomcat 5.5 running on Windows XP, Java version is 1.5, using jwsdp 1.5. My client, when run as an applet in a browser (have tried IE 6 and FireFox 1), seems to be unable to parse any exception thrown from the webservice. Instead the following exception is caught by the client:
==========================================================
Checking the security service exception that occurred [Runtime exception; nested exception is:
XML parsing error: com.sun.xml.rpc.sp.ParseException:1: Document root element is missing]
com.irista.security.services.data.SecurityServiceException: Runtime exception; nested exception is:
XML parsing error: com.sun.xml.rpc.sp.ParseException:1: Document root element is missing
at com.irista.security.services.webclient.SecurityServiceProxy.removeAuthenticatio nProfile(SecurityServiceProxy.java:1276)
at com.irista.security.ui.applet.AuthenticationProfilesListPanel.deleteAction(Auth enticationProfilesListPanel.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.irista.ui.webapp.framework.WebAppletPane.performAction(WebAppletPane.java:1 80)
at com.irista.ui.webapp.framework.WebAppletPane.performAction(WebAppletPane.java:1 51)
at com.irista.ui.webapp.framework.WebAppToolbar$ButtonActionListener.actionPerform ed(WebAppToolbar.java:368)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at javax.swing.JComponent.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
==========================================================
If I run the client outside of a browser it catches the exception that is actually thrown by the webservice.
Is there possibly a problem with the java 5 plugin handling exceptions thrown by webservices?
I have not found any bug reports or forumn posts regarding this so any assistance would be greatly appreciated.
thanks,
scott

Thanks for the reply, here is what the printStackTrace() output:
java.rmi.RemoteException: Runtime exception; nested exception is:
     XML parsing error: com.sun.xml.rpc.sp.ParseException:1: Document root element is missing
     at com.sun.xml.rpc.client.StreamingSender._handleRuntimeExceptionInSend(StreamingSender.java:318)
     at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:300)
     at com.irista.security.services.webservice.SecurityServiceIF_Stub.removeAuthenticationProfile(SecurityServiceIF_Stub.java:1963)
     at com.irista.security.services.webclient.SecurityServiceProxy.removeAuthenticationProfile(SecurityServiceProxy.java:1266)
     at com.irista.security.ui.applet.AuthenticationProfilesListPanel.deleteAction(AuthenticationProfilesListPanel.java:131)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at com.irista.ui.webapp.framework.WebAppletPane.performAction(WebAppletPane.java:180)
     at com.irista.ui.webapp.framework.WebAppletPane.performAction(WebAppletPane.java:151)
     at com.irista.ui.webapp.framework.WebAppToolbar$ButtonActionListener.actionPerformed(WebAppToolbar.java:368)
     at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
     at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
     at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
     at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
     at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.Component.processMouseEvent(Unknown Source)
     at javax.swing.JComponent.processMouseEvent(Unknown Source)
     at java.awt.Component.processEvent(Unknown Source)
     at java.awt.Container.processEvent(Unknown Source)
     at java.awt.Component.dispatchEventImpl(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: XML parsing error: com.sun.xml.rpc.sp.ParseException:1: Document root element is missing
     at com.sun.xml.rpc.streaming.XMLReaderImpl.next(XMLReaderImpl.java:120)
     at com.sun.xml.rpc.streaming.XMLReaderBase.nextContent(XMLReaderBase.java:23)
     at com.sun.xml.rpc.streaming.XMLReaderBase.nextElementContent(XMLReaderBase.java:41)
     at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:123)
     ... 34 more

How to handle Exception on Server Side as well as Client side

Hello All,
what is the method of EXCEPTION HANDLING in Web Dynpro Java ? I have no idea how these exception throw.
Thks in advance.

Hi,
Exception handling in WDJav ais similar to that of Java.
exception handling in webdynpro
Regards,
SrinivaS

RMI client-side - how to encrypt,decrypt in client-side

I write javacard RMI style. My problem is...
Source code below is work when it write in applet (card - side)
but in client-side (reader -side) I copy it to client - side code and test to run, if fail --> throw exception 0x3 - javacard.security.CryptoException.NO_SUCH_ALGORITHM
It seem to be "javacardx.crypto" and "javacard.security" is make for use in applet in card only. Did I misunderstand?
if it make for use in applet only, how is possible to do like this " card use privatekey to sign message and send to reader , reader use card's publickey to verify that card sign this signature or not."
or
"card use reader's publickey to encrypt message and send to reader, then reader use privatekey to decrypt message (reader authencate itself) "
because I can't do any of cipher , keybuilder in RMI-client side(reader)
Cipher.getInstance(Cipher.ALG_RSA_PKCS1,false);
it will throw nullPointerException
and if (change false to true)
Cipher.getInstance(Cipher.ALG_RSA_PKCS1,true);
throw exception 0x3 - javacard.security.CryptoException.NO_SUCH_ALGORITHM
after that I swap this line with
pri_key = (RSAPrivateKey) KeyBuilder.buildKey(KeyBuilder.TYPE_RSA_PRIVATE,KeyBuilder.LENGTH_RSA_512, false);
since it will do this first (i swap the line already) it also throw exception 0x3 - javacard.security.CryptoException.NO_SUCH_ALGORITHM
also be the same result with swap
kp = new KeyPair(KeyPair.ALG_RSA,(short)KeyBuilder.LENGTH_RSA_512 );
to a first line
it throw exception 0x3 - javacard.security.CryptoException.NO_SUCH_ALGORITHM
Please help me
RSAPrivateKey pri_key;
RSAPublicKey pub_key;
KeyPair kp;
Cipher RSAcipher;
RSAcipher = Cipher.getInstance(Cipher.ALG_RSA_PKCS1,false);
pri_key = (RSAPrivateKey) KeyBuilder.buildKey(KeyBuilder.TYPE_RSA_PRIVATE,KeyBuilder.LENGTH_RSA_512, false);
pub_key =(RSAPublicKey) KeyBuilder.buildKey(KeyBuilder.TYPE_RSA_PUBLIC,KeyBuilder.LENGTH_RSA_512, false);
kp = new KeyPair(KeyPair.ALG_RSA,(short)KeyBuilder.LENGTH_RSA_512 );
kp.genKeyPair();
pri_key = (RSAPrivateKey) kp.getPrivate();
pub_key = (RSAPublicKey) kp.getPublic();
//ENCRYPT
RSAcipher.init(pri_key, Cipher.MODE_ENCRYPT);
t_cipherLengthRSA = RSAcipher.doFinal(plaintxt,(short)0, (short)plaintxt.length, t_cipherText, (short)0);
//DECRYPT
RSAcipher.init(pub_key, Cipher.MODE_DECRYPT);
RSAcipher.doFinal(ciphertxt,(short)0,(short) t_cipherLengthRSA, temp1, (short)0);

I write javacard RMI style. My problem is...
Source code below is work when it write in applet (card - side)
but in client-side (reader -side) I copy it to client - side code and test to run, if fail --> throw
exception 0x3 - javacard.security.CryptoException.NO_SUCH_ALGORITHMYou can not share code between card and client. On the card use the classes of javacardx.crypto and on the client side those of javax.crypto and java.security.
It seem to be "javacardx.crypto" and "javacard.security" is make for use in applet in card only. That is right.
if it make for use in applet only, how is possible to
do like this " card use privatekey to sign message
and send to reader , reader use card's publickey to
verify that card sign this signature or not." or
"card use reader's publickey to encrypt message and
send to reader, then reader use privatekey to decrypt
message (reader authencate itself) "On each platform you have classes that provide the same cryptographic operations but the interface of these classes is different (because of the limitations of the java card platform).
because I can't do any of cipher , keybuilder in
RMI-client side(reader)Use the java.security.KeyFactory instead.
Cipher.getInstance(Cipher.ALG_RSA_PKCS1,false);
it will throw nullPointerException
and if (change false to true)
Cipher.getInstance(Cipher.ALG_RSA_PKCS1,true);
throw exception 0x3 -
javacard.security.CryptoException.NO_SUCH_ALGORITHMCryptographic support on java cards is optional. Not every card supports every algorithm. Try to use another algo.
Jan

Java.rmi.server.codebase=file:(?????); at client side: classnotfounexceptio

I'm trying to run an RMI application (under Windows XP, one machine for client and server) like this:
at server side:
java -Djava.rmi.server.codebase=file://\..\..\..\j\ -Djava.security.policy=file:.\polityka.txt sss
- and it works fine, but at client side:
java -Djava.security.policy=file:.\polityka.txt -Djava.rmi.server.codebase=file://\..\..\..\j\ kkk
results in:
Exception in thread "main" java.lang.NoClassDefFoundError: PrzykladowaKlasa
at kkk.main(kkk.java:31)
when I'm listing directory (at client side) got with System.getProperty("java.rmi.server.codebase") i get this
file://\..\..\..\j\
OdleglaKlasa_Stub.class
PrzykladowaKlasa.class
Folder Structure is:
|------j\
| |------(*_Stub.class, and ClassNeededByClient.class)
|------2\
| |------Server\
| | |------(serwer files)
| |------Klient\
| | |------(klient files)
I'm fresh in RMI and Codebase poperty, but with some exp with Java...
(policy files are allright - grant {permission java.security.AllPermission;};)
Any help will be appreciated.

I've come back to this issue again (since I am moving code around to different systems again). Using linux I can use -Djava.rmi.server.codebase=file://$PWD/build/
Presumably there is a similar command in WIndows.

Exception handling in client proxy

Hi
Can someone please help me with exception handling in ABAP client proxy.

HI
Welcome to SDN
Check this link you wil get information regarding ABAP Proxy http://help.sap.com/saphelp_nw04/helpdata/en/c9/74246d8ad2447799063d39013e9a11/content.htm

How to handle text of iframe to send to remote printer in client side?

Hello everybody,
I am having problem to handle the printing text of iframe to send to remote printer. I am using JDK 1.5, JSP and JBOSS. My clients have to print the information displayed in iframe to their remote Printer. I am using javascript code below to print:
/* CODE IS IN JAVASCRIPT */
document.frames[frameName].focus();
document.frames[frameName].print(); But the main problem is that it takes a lot of times about 2 mins. Why is the above code taking so long time? Is it due to javascript code or the printing process? Is there any method or function to send printing text of iframe to printer faster?
can anyone help me to solve this problem.....
Thank You.
Edited by: ritesh163 on Aug 20, 2008 2:45 PM

ritesh163 wrote:
Hello stevejluke,
I am seeking for the suggestion whether it can be done through javascript or there is any other function or method in JSP that can replay javascript code and also work faster.
Thank you.But JSP has nothing to do with it. JSP lives on the server, not the client. If can't control the client printer, can't know about it, and can't print to it. This is purely client-side, which means not JSP.

Client-side handler: static config?

I would like to provide a client-side JAX-RPC handler that would
be invoked without any modification to existing client code.
The idea is that user's would only need to modify a config file
(something like the web-services.xml file, but on the client-
side) to use our handler.
We are already doing this in axis (uses a client-side deployment
descriptor: client_deploy.wsdd), but based on another thread
("Client Handler Chain - help ??"), it looks like there is
currently no equivalent in WLS?
Are there plans to add the ability to statically configure
client-side handlers in WLS via some sort of client-side config
file/descriptor, or is the programmatic method of modifying
the HandlerRegistry in the client code the only way?
Any help/ideas would be greatly appreciated!
--Terry

In 7.0, you can do this in a handler:
import weblogic.webservice.binding.soap.HttpClientBinding;
String url = http://my/new/address/;
sslAdapter = null; //only needed for ssl
Binding binding = new HttpClientBinding( url, sslAdapter );
context.setProperty( WLMessageContext.BINDING_PROP,
binding );
HTHs
-manoj
http://manojc.com
"William Cassidy" <[email protected]> wrote in message
news:[email protected]...
>
Is there a similar way to set the endPointAddress.
"manoj cheenath" <[email protected]> wrote:
Ok, I will add this as a feature request.
If you are ok with using WLS internal APIs (This APIs may change in
the future), try this:
weblogic.webservice.Operation operation
=
((weblogic.webservice.WLMessageContext)messageContext).getOperation();
>>
weblogic.webservice.Port port = operation.getPort();
String endPointAddress = port.getAddress();
regards,
-manoj
"Terry Martin" <[email protected]> wrote in message
news:[email protected]...
Manoj, thanks for the response.
We'd definitely like to see a client side dd at some point, but
can work with the API's for now. Thanks much for adding this as
a feature request.
On another subject:
I need to determine the target/endpoint URL from my client-side
request handler. Again, this was something we were able to do in
axis, but is currently not part of the JAX-RPC standard (JSR101).
I could be missing something, but haven't seen any way of
determining the target URL given only the SOAPMessageContext.
The only way seems to be if it were passed as a "standard"
property in the SOAPMessageContext (this is one way it is done
in axis).
I imagine this will someday be standardized in JAX-RPC (I can
think of many uses for this feature, other than our own). In the
meantime, could you also add this as a feature request for WLS?
Thanks again,
-Terry
"manoj cheenath" <[email protected]> wrote:
True. In WLS 7.0 there are no client side dd in which you can specify
the handler chain. We did not comeup with ourown client side dd,
hopeing that JSR109 will define the dd.
It is quite easy to register the handlers through APIs. Let us know
if
that will not help you.
I will add client side dd as a feature requst for the next release.
regards,
-manoj
"Terry Martin" <[email protected]> wrote in message
news:[email protected]...
I would like to provide a client-side JAX-RPC handler that would
be invoked without any modification to existing client code.
The idea is that user's would only need to modify a config file
(something like the web-services.xml file, but on the client-
side) to use our handler.
We are already doing this in axis (uses a client-side deployment
descriptor: client_deploy.wsdd), but based on another thread
("Client Handler Chain - help ??"), it looks like there is
currently no equivalent in WLS?
Are there plans to add the ability to statically configure
client-side handlers in WLS via some sort of client-side config
file/descriptor, or is the programmatic method of modifying
the HandlerRegistry in the client code the only way?
Any help/ideas would be greatly appreciated!
--Terry

RMI client side callbacks

Hi all,
I have an RMI server and a number of clients that run on different machines. What I need to do is, implement the "observer" pattern. i.e.
in my case, not only the clients call the server, but also the server
must notify the registered clients when its state changes.
For that purpose, I suppose, that my clients must also be RMI servers.
My first question is, is that true what I suppose? Is there any other
way to implement asynchron client side callbacks with RMI?
My second question is, if it must be done so (clients are also RMI servers), how can I implement this? Server needs client interface jar
file, ans client needs server interface jar file at compile time.
(Important: I do not use any HTTP server from which I can load _Stub
classes at runtime)
I don't like this architecture at all and therefore think that there
may be better solutions. One solution may be to poll the state of the
server from the clients periodically, so that there is no need for
callbacks. But that is also not the perfect solution for me.
Can someone suggest anything else?
Any idea will be greatly appreciated!
Thank you

Hello guvener
Some time ago, I did exactly what you are thinking about. Here was the strategy.
1. There was a server program, sitting (obviously) on the server machine, where rmiserver was running. The server class had only a single public method for the calling routines to call.
2. That public method took, as a parameter, a transaction request. One possible transaction was, "Here is a message for another client." Another possible transaction was, "Listen out for a message for me." For example, a client would call the server with the "listen" transaction or with a "here's a message" transaction.
3. When the calling method requested a "listen" transaction, the server would enter a "wait" state until it received a message for that particular client.
4. To prevent blocking, there were three specific strategies:
(a) The client would call the server with a "listen" transaction in a separate thread.
(b) There was a "cancel" transaction that would allow a client to cancel its "listen" transaction with the server.
(c) There was a "close-down" transaction that would allow the server to tell the clients their "listen" transactions had been cancelled, as it was closing down.
This requires thorough and careful planning. However, once the classes are correctly planned, this strategy is elegant and simple and leads to only a small amount of coding. It's also flexible, without any restrictions on how many transactions a client could request at a time.
Do be careful to synchronize where applicable!
I hope this helps.

Possible to use RMI to upload client side image files?

Is it possible to use RMI to upload client side image files? My intent is to allow remote clients to upload a number of small image files (jpg & gif) to a central server DBMS, by modifying a "Customer" object (eg adding a new Image object to a vector of Images?) Is this possible? Any suggestions greatly appreciated :))

Is it possible to use RMI to upload client side image
files? One possibility is to implement a serializable image object that you can upload to the server as any other object. When your server receives this serialized image object, just generate a new gif/jpg from it.
But if your client-program is an applet, the situation is different: how can applet read image-file from users harddrive?
krera

Uncaught exception raised in Server Client-side plugin

When I try to connect to my XServe from the Server Admin on my desktop computer. I get the following error:
Uncaught exception raised in Server Client-side plugin
Sorry but the feature you tried to access cannot be used. Exception is:
In updateConfigurationViewFromDescription: NSInvalidArgumentException * -[NSCFNumber count]: unrecognized selector sent to instance 0x18819ee0 .
There is a second error with similar wording.
If I say ok to the warnings I can make changes but they do not save.
I can access the Server Admin on the XServe
Anyone know of a solution so that I can login and edit the settings for my XServe from a remote computer?

I'm getting this too, server is XServe running 10.6.6, remote Server Admin is on a 10.5.8 PPC iMac. No errors with same remote against a PowerMac server running 10.5.8. No errors with 10.6.6 remote against either server.
Unlike the OP, however, the changes I've tried "take." The pop-ups are annoying though.
Another issue with the 10.5 Server Admin/10.6 Server, if it isn't a thread hijack, disk volumes do not show up in the File Sharing pane, Share Points appear OK.

Query: creating client side handler

how can I create a client side handler for a webservice on weblogic 9.2 workshop

Take a peek at edocs for some examples and code you can get started with:
http://edocs.bea.com/wls/docs92/webserv/client.html#client_handlers
Best of luck,
-Jacobd
Mihir Khanwalkar wrote:
how can I create a client side handler for a webservice on weblogic 9.2 workshop

JMS Exception at Client Side

Hi All
We have application consisting of applets
a) We have signed the Application JAR (CA ) and put in the below attributes in the manifest file
Codebase: <<CodebasePath>>
Application-Library-Allowable-Codebase: <<CodebasePath>>
permissions: all-permissions
b) We use the wlclient.jar and wljmsclient.jar as well. For these JARS we have added the below attribute in the manifest file
Permissions: all-permissions
c) We are getting exceptions at the client side while launching the application ( JRE is 1.6.0_51)
Exception in initJMS()>>>>>>>>>>>>>>>
javax.naming.NamingException: Unhandled exception in lookup [Root exception is org.omg.CORBA.NO_PERMISSION: vmcid: 0x0 minor code: 0 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:83)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:232)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:168)
at javax.naming.InitialContext.lookup(Unknown Source)
at com.orbitreasury.moneymarket.presentation.util.MessagingServiceFactory.initJMS(MessagingServiceFactory.java:142)
at com.orbitreasury.moneymarket.presentation.util.MessagingServiceFactory.<init>(MessagingServiceFactory.java:102)
at com.orbitreasury.moneymarket.presentation.util.MessagingServiceFactory.getInstance(MessagingServiceFactory.java:94)
at com.orbitreasury.moneymarket.presentation.applet.FrontOfficeDesk.init(FrontOfficeDesk.java:328)
at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: org.omg.CORBA.NO_PERMISSION: vmcid: 0x0 minor code: 0 completed: No
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at java.lang.Class.newInstance0(Unknown Source)
at java.lang.Class.newInstance(Unknown Source)
at com.sun.corba.se.impl.protocol.giopmsgheaders.MessageBase.getSystemException(Unknown Source)
at com.sun.corba.se.impl.protocol.giopmsgheaders.ReplyMessage_1_2.getSystemException(Unknown Source)
at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.getSystemExceptionReply(Unknown Source)
at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.processResponse(Unknown Source)
at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete(Unknown Source)
at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.invoke(Unknown Source)
at org.omg.CORBA.portable.ObjectImpl._invoke(Unknown Source)
at weblogic.corba.cos.naming._NamingContextAnyStub.resolve_any(_NamingContextAnyStub.java:80)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:208)

Hi Amitava,
This error may happen when creating foreign JMS server and user credentials (principal name) is not provided. As a result, Weblogic is unable to create the required JNDI name.
To rectify the error you can provide principal name in the JMS Configuration and restart Weblogic. See the following for sample configuration required:
<foreign-server name="ForeignServer">
<sub-deployment-name>subDep</sub-deployment-name>
<foreign-destination name="ForeignDestination">
<local-jndi-name>localQueue</local-jndi-name>
<remote-jndi-name>remoteQueue</remote-jndi-name>
</foreign-destination>
<foreign-connection-factory name="ForeignConnectionFactory-0">
<local-jndi-name>localJNDI</local-jndi-name>
<remote-jndi-name>remoteJNDI</remote-jndi-name>
</foreign-connection-factory>
<connection-url>t3://localhost:7010</connection-url>
<jndi-properties-credential-encrypted>{3DES}yK0ERotSucIGRVFORfS4Kw==</jndi-properties-credential-encrypted>
<jndi-property>
<key>java.naming.security.principal</key>
<value>weblogic</value>
</jndi-property>
</foreign-server>
Refer to documentation below for more details:
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/jms_admin/advance_config.html#wp1075917
Hope it helps.
Thanks,
Cris

What is Client-Side API for RMI on the Java Card Platform

What is Client-Side API for RMI on the Java Card Platform ?
And what is host software ?

Your post is weird: you seem not to agree with yourself O_o
OF COURSE sim cards have CPUs, otherwise how would you run an OS or a java vm on them?
to drive the wifi there will be a proprietary api, just like mifare access on normal cards.
the OS should manage the wiki stack in C/asm and expose javacard entry points. only "should" because this is only a press release.

Exception handling in rmi in client side

Similar Messages

Maybe you are looking for