java - org.omg.CORBA.TRANSIENT: initial and forwarded IOR inaccessible vmcid: IBM minor code: E07 from stand-alone app -
i'm connecting websphere instance stand-alone java app quite trivial:
initialcontext initctx = new initialcontext(); that code working in websphere 7, after updating websphere 8.5 got following exception:
caused by: org.omg.corba.transient: initial , forwarded ior inaccessible vmcid: ibm minor code: e07 completed: no @ com.ibm.rmi.corba.clientdelegate.createrequest(clientdelegate.java:1276) @ com.ibm.corba.iiop.clientdelegate.createrequest(clientdelegate.java:1457) @ com.ibm.rmi.corba.clientdelegate.createrequest(clientdelegate.java:1164) @ com.ibm.corba.iiop.clientdelegate.createrequest(clientdelegate.java:1423) @ com.ibm.rmi.corba.clientdelegate.request(clientdelegate.java:1886) @ com.ibm.corba.iiop.clientdelegate.request(clientdelegate.java:1379) @ org.omg.corba.portable.objectimpl._request(objectimpl.java:458) @ com.ibm.wsnbootstrap._wsnnameservicestub.getproperties(_wsnnameservicestub.java:38) @ com.ibm.ws.naming.util.wsninitctxfactory.mergewsnnsproperties(wsninitctxfactory.java:1441) ... 43 more after research, i've fout out ibm support page, said go csiv2 inbound , outbound settings (by me, admin console->security->globalsecurity->rmi/iiop security) , set transport ssl-supported.
however, didn't change anything. i've tried change 'cleint certificate authentication' never, , transport tcp/ip both csiv2 inbound , outbound, still without success. error persisted until i've turned off 'enable administrative security', not option, because need enable 'application security' (the application logic depends of that).
how can make code working again? ok on websphere 7.
the error description
org.omg.corba.transient: initial , forwarded ior inaccessible vmcid: ibm minor code: e07
is vague , happens under many, not directly connected circumstances.
in case had nothing rmi/iiop security settings, classpath problem. still using old version of com.ibm.ws.webservices.thinclient.
switching thinclient 8.5.0, setting launch jre standard (oracle) jvm has fixed problem.
Comments
Post a Comment