EPI-USE DSM Client Synch problem

Tried to do a full years worth of data. It ended with errors. Opened ticket and was told "
The DB error "Database error -901 at PRE access to table ..." indicates a basis level problem and not a problem with how you are running DSM. I suggest you ask your basis admin to have a look at the following tables: VAPMA, VRKPA, VAKPA.
A good place to start is to use se11 to run the database and runtime object consistency check that is available under the utilities menu. I also see reports online that some users were able to fix the -901 database error by reactivating the table."
I have searched for solutions to these errors, and have not found any help.
Can anyone give me a clue what to do? This is being run on an iSeries with the database being DB2.
Just of the the errors is shown in attached screen shot.

Hi John,
When you get this error , please share
SM21 logs
dev_wx logs
Regards,
Deepak Kori

Similar Messages

Error after using Test Client (HomeFactory Problem)

All,
I am a newbie with websphere and I try to develop a sample EJB app.
My attempts to test my method of my stateless Session bean were not successful.
I got the following messaage:
[18.07.05 00:02:51:752 CEST] 31c7edd5 WebGroup I SRVE0180I: [bpesoapclient] [bpesoapclient] [Servlet.LOG]: InvokerServlet: init
[18.07.05 00:02:52:003 CEST] 31c7edd5 ApplicationMg A WSVR0221I: Die Anwendung wurde gestartet: BPERemoteDeploy
[18.07.05 00:02:52:023 CEST] 31c7edd5 ApplicationMg A WSVR0200I: Die Anwendung wird gestartet: query
[18.07.05 00:02:52:083 CEST] 31c7edd5 EJBContainerI I WSVR0207I: Der Start des EJB-JAR wird vorbereitet: querybean.jar
[18.07.05 00:02:52:333 CEST] 31c7edd5 EJBContainerI I WSVR0037I: EJB-JAR-Datei wird gestartet: querybean.jar
[18.07.05 00:02:52:524 CEST] 31c7edd5 ApplicationMg A WSVR0221I: Die Anwendung wurde gestartet: query
[18.07.05 00:02:52:534 CEST] 31c7edd5 ApplicationMg A WSVR0200I: Die Anwendung wird gestartet: TestDmProjectEAR
[18.07.05 00:02:52:644 CEST] 31c7edd5 EJBContainerI I WSVR0207I: Der Start des EJB-JAR wird vorbereitet: TestDmProject.jar
[18.07.05 00:02:57:671 CEST] 31c7edd5 EJBContainerI I WSVR0037I: EJB-JAR-Datei wird gestartet: TestDmProject.jar
[18.07.05 00:03:01:266 CEST] 31c7edd5 ApplicationMg A WSVR0221I: Die Anwendung wurde gestartet: TestDmProjectEAR
[18.07.05 00:03:01:496 CEST] 31c7edd5 StaffServiceI I STFF0032I: Der Staff Service wurde ordnungsgem葹 gestartet.
[18.07.05 00:03:02:899 CEST] 31c7edd5 HttpTransport A SRVE0171I: Der Transport http ist empfangsbereit an Port 9.080.
[18.07.05 00:03:06:003 CEST] 31c7edd5 HttpTransport A SRVE0171I: Der Transport https ist empfangsbereit an Port 9.443.
[18.07.05 00:03:06:043 CEST] 31c7edd5 SchedulerServ I SCHD0031I: Der Scheduler Service wird gestartet.
[18.07.05 00:03:12:733 CEST] 31c7edd5 SchedulerServ I SCHD0032I: Die Scheduler-Instanz BPEScheduler wird gestartet.
[18.07.05 00:03:17:309 CEST] 31c7edd5 SchedulerDaem I SCHD0038I: Der Scheduler-D舂on f・ die Instanz BPEScheduler wurde gestartet.
[18.07.05 00:03:17:500 CEST] 31c7edd5 SchedulerServ I SCHD0033I: Die Scheduler-Instanz BPEScheduler wurde gestartet.
[18.07.05 00:03:17:520 CEST] 31c7edd5 SchedulerServ I SCHD0001I: Der Scheduler Service wurde gestartet.
[18.07.05 00:03:19:012 CEST] 31c7edd5 RMIConnectorC A ADMC0026I: Der RMI-Connector ist an Port 2809 verf・bar.
[18.07.05 00:03:19:542 CEST] 31c7edd5 WsServer A WSVR0001I: Der Server server1 ist f・ e-business bereit.
[18.07.05 00:03:27:013 CEST] 46da2dd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: jndiLookupServlet: init
[18.07.05 00:03:29:517 CEST] 46da2dd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: /index.jsp: init
[18.07.05 00:03:29:827 CEST] 46da2dd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: /html/ejbPage/ejbFrame.jsp: init
[18.07.05 00:03:29:837 CEST] 4d94edd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: /html/toolbar/global_nav.jsp: init
[18.07.05 00:03:30:458 CEST] 46da2dd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: /html/ejbPage/referencePage.jsp: init
[18.07.05 00:03:30:468 CEST] 4d94edd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: /html/ejbPage/parameterPage.jsp: init
[18.07.05 00:03:30:939 CEST] 46da2dd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: /html/toolbar/toolbar.jsp: init
[18.07.05 00:03:30:959 CEST] 4d94edd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: /html/ejbPage/reference.jsp: init
[18.07.05 00:03:31:520 CEST] 46da2dd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: /html/ejbPage/parameter.jsp: init
[18.07.05 00:03:36:457 CEST] 4d94edd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: treeExpansionServlet: init
[18.07.05 00:03:39:932 CEST] 4d94edd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: selectMemberServlet: init
[18.07.05 00:03:42:145 CEST] 46da2dd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: invokeServlet: init
[18.07.05 00:03:44:388 CEST] 4d94edd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: addObjectServlet: init
[18.07.05 00:03:55:504 CEST] 46da2dd7 SystemOut O class=class com.mbusa.TestDm._EJSRemoteCMPStatusHome_ce727769_Stub
[18.07.05 00:03:55:504 CEST] 46da2dd7 SystemOut O ejbRef ejb/com/mbusa/TestDm/StatusHome is a remote reference.
[18.07.05 00:03:56:105 CEST] 46da2dd7 ExceptionUtil E CNTR0019E: Bei der Verarbeitung der Methode "setStatus" ist eine nicht auf die Anwendung zur・kzuf・rende Ausnahme eingetreten. Ausnahmedaten: com.ibm.ejs.container.CreateFailureException: ; nested exception is:
     java.lang.reflect.InvocationTargetException
     at com.ibm.ejs.container.StatelessBeanO.<init>(StatelessBeanO.java:151)
     at com.ibm.ejs.container.CMStatelessBeanO.<init>(CMStatelessBeanO.java:53)
     at com.ibm.ejs.container.CMStatelessBeanOFactory.create(CMStatelessBeanOFactory.java:40)
     at com.ibm.ejs.container.EJSHome.createBeanO(EJSHome.java:668)
     at com.ibm.ejs.container.EJSHome.createBeanO(EJSHome.java:755)
     at com.ibm.ejs.container.activator.UncachedActivationStrategy.atActivate(UncachedActivationStrategy.java:78)
     at com.ibm.ejs.container.activator.Activator.activateBean(Activator.java:516)
     at com.ibm.ejs.container.EJSContainer.preInvoke_internal(EJSContainer.java:2762)
     at com.ibm.ejs.container.EJSContainer.preInvoke(EJSContainer.java:2487)
     at com.ibm.ejs.container.EJSContainer.preInvoke(EJSContainer.java:2472)
     at com.mbusa.TestDm.EJSRemoteStatelessTestDmSession_3f7076e7.setStatus(EJSRemoteStatelessTestDmSession_3f7076e7.java:34)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
     at java.lang.reflect.Method.invoke(Method.java:391)
     at com.ibm.rmi.util.ProxyUtil$4.run(ProxyUtil.java:726)
     at java.security.AccessController.doPrivileged1(Native Method)
     at java.security.AccessController.doPrivileged(AccessController.java:351)
     at com.ibm.rmi.util.ProxyUtil.invokeWithClassLoaders(ProxyUtil.java:724)
     at com.ibm.CORBA.iiop.ClientDelegate.invoke(ClientDelegate.java:1121)
     at $Proxy5.setStatus(Unknown Source)
     at com.mbusa.TestDm._TestDmSession_Stub.setStatus(_TestDmSession_Stub.java:266)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
     at java.lang.reflect.Method.invoke(Method.java:391)
     at com.ibm.etools.utc.model.ReflectionMethodModel.invoke(ReflectionMethodModel.java:68)
     at com.ibm.etools.utc.servlet.InvokeServlet.invoke(InvokeServlet.java:110)
     at com.ibm.etools.utc.servlet.InvokeServlet.doPost(InvokeServlet.java:366)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
     at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
     at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
     at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
     at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
     at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
     at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:1019)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:592)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:204)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:125)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:286)
     at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
     at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:182)
     at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
     at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
     at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:615)
     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:439)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:912)
Caused by: java.lang.reflect.InvocationTargetException
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
     at java.lang.reflect.Method.invoke(Method.java:391)
     at com.ibm.ejs.container.StatelessBeanO.<init>(StatelessBeanO.java:144)
     ... 51 more
Caused by: java.lang.ClassCastException: com.mbusa.TestDm._EJSRemoteCMPStatusHome_ce727769_Stub
     at com.mbusa.TestDm.TestDmSessionBean.getHomes(TestDmSessionBean.java:71)
     at com.mbusa.TestDm.TestDmSessionBean.ejbCreate(TestDmSessionBean.java:39)
     ... 57 more
The code looks as follows:
package com.mbusa.vrm;
* Bean implementation class for Enterprise Bean: VrmSession
import javax.ejb.*;
import javax.naming.*;
import java.rmi.RemoteException;
import java.sql.Date;
import com.test.dm.homeFactory.*;
public class TestDmSessionBean implements javax.ejb.SessionBean {
     private javax.ejb.SessionContext mySessionCtx;
     protected StatusLocalHome statusHome = null;
          * getSessionContext
          public javax.ejb.SessionContext getSessionContext() {
               return mySessionCtx;
          * setSessionContext
          public void setSessionContext(javax.ejb.SessionContext ctx) {
               mySessionCtx = ctx;
          * ejbCreate
          public void ejbCreate() throws javax.ejb.CreateException {
               getHomes();
          * ejbActivate
          public void ejbActivate() {
               getHomes();
          * ejbPassivate
          public void ejbPassivate() {
               statusHome = null;
          * ejbRemove
          public void ejbRemove() {
          protected void getHomes() {
               try {
                    statusHome = (StatusLocalHome) HomeFactory.singleton().getHome("ejb/com/test/dm/StatusHome");
               } catch (NamingException ex) {
                    ex.printStackTrace();
                    throw new EJBException("Error looking up homes: "+ex.getMessage());
     public void setStatus(int statusId, String description) throws FinderException, CreateException {
          try {
               StatusLocal status = statusHome.create(statusId);
               status.setDescription(description);
          } catch (EJBException ex) {
               throw new EJBException("Status setStatus failed for "+ statusId);
     public String getStatusDEscription(int statusId) throws FinderException, CreateException {
          try {
               StatusLocal status = statusHome.findByPrimaryKey(new StatusKey(statusId));
               return status.getDescription();
          } catch (EJBException ex) {
               throw new EJBException("Status setStatus failed for "+ statusId);
I appreciate any help!!!
Cheers
Greg

Hi,
I am using the Universal test client to test my methods.
Thank you very much for your help!!!
Greg

Problem using CORBA clients with RMI/EJB servers..!!!???

Hi,
I have a question on using EJB / or RMI servers with CORBA clients using
RMI-IIOP transport, which in theory should work, but in practice has few
glitches.
Basically, I have implemented a very simple server, StockTreader, which
looks up for a symbol and returns a 'Stock' object. In the first example, I
simplified the 'Stock' object to be a mere java.lang.String, so that lookup
would simply return the 'synbol'.
Then I have implemented the above, as an RMI-IIOP server (case 1) and a
CORBA server (case 2) with respective clients, and the pair of
client-servers work fine as long as they are CORBA-to-CORBA and RMI-to-RMI.
But the problem arises when I tried using the RMI server (via IIOP) with the
CORBA client, when the client tries to narrow the object ref obtained from
the naming service into the CORBA idl defined type (StockTrader) it ends up
with a class cast exception.
This is what I did to achieve the above results:
[1] Define an RMI interface StockTrader.java (extending java.rmi.Remote)
with the method,
public String lookup( String symbol) throws RMIException;
[2] Implement the StorckTrader interface (on a PortableRemoteObject derived
class, to make it IIOP compliant), and then the server to register the stock
trader with COS Naming service as follows:
String homeName =....
StockTraderImpl trader =new StockTraderImpl();
System.out.println("binding obj <" homeName ">...");
java.util.Hashtable ht =new java.util.Hashtable();
ht.put("java.naming.factory.initial", args[2]);
ht.put("java.naming.provider.url", args[3]);
Context ctx =new InitialContext(ht);
ctx.rebind(homeName, trader);
[3] Generate the RMI-IIOP skeletons for the Implementation class,
rmic -iiop stock.StockTraderImpl
[4] generate the IDL for the RMI interface,
rmic -idl stock.StockTraderImpl
[5] Generate IDL stubs for the CORBA client,
idlj -v -fclient -emitAll StockTraderImpl.idl
[6] Write the client to use the IDL-defined stock trader,
String serverName =args[0];
String symList =args[1];
StockClient client =new StockClient();
System.out.println("init orb...");
ORB orb =ORB.init(args, null);
System.out.println("resolve init name service...");
org.omg.CORBA.Object objRef
=orb.resolve_initial_references("NameService");
NamingContext naming =NamingContextHelper.narrow(objRef);
... define a naming component etc...
org.omg.CORBA.Object obj =naming.resolve(...);
System.out.println("narrow objRef: " obj.getClass() ": " +obj);
StockTrader trader =StockTraderHelper.narrow(obj);
[7] Compile all the classes using Java 1.2.2
[8] start tnameserv (naming service), then the server to register the RMI
server obj
[9] Run the CORBA client, passing it the COSNaming service ref name (with
which the server obj is registered)
The CORBA client successfully finds the server obj ref in the naming
service, the operation StockTraderHelper.narrow() fails in the segment
below, with a class cast exception:
org.omg.CORBA.Object obj =naming.resolve(...);
StockTrader trader =StockTraderHelper.narrow(obj);
The <obj> returned by naming service turns out to be of the type;
class com.sun.rmi.iiop.CDRInputStream$1
This is of the same type when stock trader object is registered in a CORBA
server (as opposed to an RMI server), but works correctly with no casting
excpetions..
Any ideas / hints very welcome.
thanks in advance,
-hari

On the contrary... all that is being said is that we needed to provide clearer examples/documentation in the 5.1.0 release. There will be no difference between the product as found in the service pack and the product found in the 5.1.1. That is, the only substantive will be that 5.1.1 will also
include the examples.
"<=one way=>" wrote:
With reference to your and other messages, it appears that one should not
expect that WLS RMI-IIOP will work in a complex real-life system, at least
not now. In other words, support for real-life CORBA clients is not an
option in the current release of WLS.
TIA
"Eduardo Ceballos" <[email protected]> wrote in message
news:[email protected]...
We currently publish an IDL example, even though the IDL programmingmodel in Java is completely non-functional, in anticipation of the support
needs for uses who need to use IDL to talk to the Weblogic server,
generically. This example illustrates the simplest connectivity; it does not
address how
to integrate CORBA and EJB, a broad topic, fraught with peril, imo. I'llnote in passing that, to my knowledge, none of the other vendors attempt
this topic either, a point which is telling if all the less happy to hear.
For the record then, what is missing from our distribution wrt RMI-IIOPare a RMI-IIOP example, an EJB-IIOP example, an EJB-C++. In this you are
correct; better examples are forth coming.
Still, I would not call our RMI-IIOP implementation fragile. I would saythat customers have an understandably hard time accepting that the IDL
programming model is busted; busted in the sense that there are no C++
libraries to support the EJB model, and busted in the sense that there is
simply no
support in Java for an IDL interface to an EJB. Weblogic has nothing to doit being busted, although we are trying to help our customers deal with it
in productive ways.
For the moment, what there is is a RMI (over IIOP) programming model, aninherently Java to Java programming model, and true to that, we accept and
dispatch IIOP request into RMI server objects. The way I look at it is this:
it's just a protocol, like HTTP, or JRMP; it's not IDL and it has
practically nothing to do with CORBA.
ST wrote:
Eduardo,
Can you give us more details about the comment below:
I fear that as soon as the call to narrow succeeds, the remainingapplication will fail to work correctly because it is too difficult ot
use an idl client in java to work.It seems to me that Weblogic's RMI-IIOP is a very fragile
implementation. We
don't need a "HelloWorld" example, we need a concrete serious example(fully
tested and seriously documented) that works so that we can get a betteridea
on how to integrate CORBA and EJB.
Thanks,
Said
"Eduardo Ceballos" <[email protected]> wrote in message
news:[email protected]...
Please post request to the news group...
As I said, you must separate the idl related classes (class files and
java
files) from the rmi classes... in the rmic step, you must set a newtarget
(as you did), emit the java files into that directory (it's not clearyou
did this), then remove all the rmi class files from the class path... ifyou
need to compile more classes at that point, copy the java files to theidl
directly is you must, but you can not share the types in any way.
I fear that as soon as the call to narrow succeeds, the remainingapplication will fail to work correctly because it is too difficult otuse
an idl client in java to work.
Harindra Rajapakshe wrote:
Hi Eduardo,
Thanks for the help. That is the way I compiled my CORBA client, by
separating the IDL-generated stubs from the RMI ones, but still I
get a
CORBA.BAD_PARAM upon narrowing the client proxy to the interfacetype.
Here's what I did;
+ Define the RMI interfaces, in this case a StockTrader interface.
+ Implement RMI interface by extendingjavax.rmi.PortableRemoteObject
making
it IIOP compliant
+ Implemnnt an RMI server, and compile using JDK1.2.2
+ use the RMI implementation to generate CORBA idl, using RMI-IIOPplugin
utility rmic;
rmic -idl -noValueMethods -always -d idl stock.StockTraderImpl
+ generate Java mappings to the IDL generated above, using RMI-IIOPplugin
util,
idlj -v -fclient -emitAll -tf src stocks\StockTrader.idl
This creates source for the package stock and also
org.omg.CORBA.*
package, presumably IIOP type marshalling
+ compile all classes generated above using JDK1.2.2
+ Implement client (CORBA) using the classes generated above, NOTthe
RMI
proxies.
+ start RMI server, with stockTrader server obj
+ start tnameserv
+ start CORBA client
Then the client errors when trying to narrow the obj ref from the
naming
service, into the CORBA IDL defined interface using,
org.omg.CORBA.Object obj =naming.resolve(nn);
StockTrader trader =StockTraderHelper.narrow(obj); // THIS
ERRORS..!!!
throwing a CORBA.BAD_PARAM exception.
any ideas..?
Thanks in advance,
-hari
----- Original Message -----
From: Eduardo Ceballos <[email protected]>
Newsgroups: weblogic.developer.interest.rmi-iiop
To: Hari Rajapakshe <[email protected]>
Sent: Wednesday, July 26, 2000 4:38 AM
Subject: Re: problem using CORBA clients with RMI/EJBservers..!!!???
Please see the post on june 26, re Errors compiling... somewherein
there,
I suspect, you are referring to the rmi class file when you are
obliged
to
completely segregate these from the idl class files.
Hari Rajapakshe wrote:
Hi,
I have a question on using EJB / or RMI servers with CORBA
clients
using
RMI-IIOP transport, which in theory should work, but in practice
has
few
glitches.
Basically, I have implemented a very simple server,
StockTreader,
which
looks up for a symbol and returns a 'Stock' object. In the firstexample, I
simplified the 'Stock' object to be a mere java.lang.String, so
that
lookup
would simply return the 'synbol'.
Then I have implemented the above, as an RMI-IIOP server (case
1)
and a
CORBA server (case 2) with respective clients, and the pair of
client-servers work fine as long as they are CORBA-to-CORBA andRMI-to-RMI.
But the problem arises when I tried using the RMI server (via
IIOP)
with
the
CORBA client, when the client tries to narrow the object ref
obtained
from
the naming service into the CORBA idl defined type (StockTrader)
it
ends
up
with a class cast exception.
This is what I did to achieve the above results:
[1] Define an RMI interface StockTrader.java (extending
java.rmi.Remote)
with the method,
public String lookup( String symbol) throws RMIException;
[2] Implement the StorckTrader interface (on a
PortableRemoteObject
derived
class, to make it IIOP compliant), and then the server to
register
the
stock
trader with COS Naming service as follows:
String homeName =....
StockTraderImpl trader =new StockTraderImpl();
System.out.println("binding obj <" homeName ">...");
java.util.Hashtable ht =new java.util.Hashtable();
ht.put("java.naming.factory.initial", args[2]);
ht.put("java.naming.provider.url", args[3]);
Context ctx =new InitialContext(ht);
ctx.rebind(homeName, trader);
[3] Generate the RMI-IIOP skeletons for the Implementation
class,
rmic -iiop stock.StockTraderImpl
[4] generate the IDL for the RMI interface,
rmic -idl stock.StockTraderImpl
[5] Generate IDL stubs for the CORBA client,
idlj -v -fclient -emitAll StockTraderImpl.idl
[6] Write the client to use the IDL-defined stock trader,
String serverName =args[0];
String symList =args[1];
StockClient client =new StockClient();
System.out.println("init orb...");
ORB orb =ORB.init(args, null);
System.out.println("resolve init name service...");
org.omg.CORBA.Object objRef
=orb.resolve_initial_references("NameService");
NamingContext naming=NamingContextHelper.narrow(objRef);
... define a naming component etc...
org.omg.CORBA.Object obj =naming.resolve(...);
System.out.println("narrow objRef: " obj.getClass() ":"
+obj);
StockTrader trader =StockTraderHelper.narrow(obj);
[7] Compile all the classes using Java 1.2.2
[8] start tnameserv (naming service), then the server to
register
the
RMI
server obj
[9] Run the CORBA client, passing it the COSNaming service ref
name
(with
which the server obj is registered)
The CORBA client successfully finds the server obj ref in the
naming
service, the operation StockTraderHelper.narrow() fails in thesegment
below, with a class cast exception:
org.omg.CORBA.Object obj =naming.resolve(...);
StockTrader trader =StockTraderHelper.narrow(obj);
The <obj> returned by naming service turns out to be of the
type;
class com.sun.rmi.iiop.CDRInputStream$1
This is of the same type when stock trader object is registeredin a
CORBA
server (as opposed to an RMI server), but works correctly with
no
casting
excpetions..
Any ideas / hints very welcome.
thanks in advance,
-hari

Problem using instant client with Win 7

Hi,
I have a Powerbuilder application that runs very well with Win XP and Oracle client 8 to 10.
With new computers (Win 7), we try to use instant client... but there are problems with accents ! In fact, all accents are replaced by a "¿" in the database.
It only appears when we are using our programs from a Win 7 machine with instant client.
Do you know if there is something to configure to solve this problem ?
Best regards.

user1931557 wrote:
Hi,
I have a Powerbuilder application that runs very well with Win XP and Oracle client 8 to 10.
With new computers (Win 7), we try to use instant client... but there are problems with accents ! In fact, all accents are replaced by a "¿" in the database.
It only appears when we are using our programs from a Win 7 machine with instant client.
Do you know if there is something to configure to solve this problem ?
Best regards.
If the characters only appear on certain clients, then they are NOT being "replaced ... in the database". What you are seeing is an issue with presentation, not data.

Problem using application client for local stateful session bean

Hi,
I have deployed a local stateful session bean in Sun J2EE 1.4 application server.
On running the applclient for the stateful session bean application client i get the following error:
Warning: ACC006: No application client descriptor defined for: [null]
cant we use application client for local stateful session beans. becoz the application runs smoothly when i changed the stateful sesion bean to remote.

Hi,
No, an ejb that exposes a local view can only be accessed by an ejb or web component packaged within the same application. Parameters and return values for invocations through the ejb local view are passed by reference instead of by value. That can't work for an application client since it's running in a separate JVM.
--ken

EPI use of hierarchies in SAP R/3 FICO

Hi
This is related to a BW report which gets its data from SAP R/3 FICO.
We are facing a problem wherein development R/3 and quality R/3 are not in sync. Since they are not in sync with respect to Customer Group Hierarchy (PH6) our BW report does not work.
This hierarchy is created in SAP and then BW picks up any amendments when a material master update routine is run.
The problem is that we have a correct version of this hierarchy in P01(live system) which ideally we would like to be able to copy back into R01(quality) and D01(development) so these can then be updated in BD1(BW development) and BQ1(BW quality). We would probably need to copy back a Customer Group Table (T151) as well.
I believe there is a SAP functionality called EPI-Use that may allow us to do this and was wondering if any of your guys have used this process and could advise whether this is possible or not.
It would save a significant amount of work if we were able to use this facility.
Any help would be welcome.
Thanks.

Hi karthik,
thanks, please let me Know , in which tables,The SAP components are get stored.
like all infoobjects, infoarea,ods,infocubes,data sources,etc.
Eg: ods is get stored in "RSDODSO" tables.
Thanks,
santosh.

I am automating the process of sending appointment reminders to my clients. I started with an alert with an email in calendar using the clients email address as a custom entry in my me card in my contacts. this was resulting in three emails being sent wit

I am automating the process of sending appointment reminders to my clients. I started with an alert with an email in calendar using the clients email address as a custom entry in my me card in my contacts. this was resulting in three emails being sent with slightly different versions of the same address (see my previous post). Heating someone else's suggestion I created a workflow file to send an email and calling that file from an alert on my calendar. This is working and sends only one email to the client.
My calendar is on I cloud and I access it from three different computers so I can keep my appointment calendar current. The files that send the email only exist on one computer. My other computers show error messages when those emails get sent. It seems that each computer wants to send the email. It's a small problem but is there a way that I could not get those alerts.
But appreciate any thoughts about this. It seems like both problems might be related to the iCloud system.
Thank you in advance,
Michael

Good work, catch so far Michael, does seem to be a "feature" of iCloud syncing, not sure what you could do to disable it.

Error invoking bpel process using axis client

When I am trying to invoke bpel process using axis client I'am having following error:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: org.xml.sax.SAXException: Bad envelope tag: html
faultActor:
faultNode:
faultDetail:
     {http://xml.apache.org/axis/}stackTrace: org.xml.sax.SAXException: Bad envelope tag: html
     at org.apache.axis.message.EnvelopeBuilder.startElement(EnvelopeBuilder.java:109)
     at org.apache.axis.encoding.DeserializationContextImpl.startElement(DeserializationContextImpl.java:976)
     at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
     at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
     at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
     at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
     at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
     at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
     at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
     at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
     at org.apache.axis.encoding.DeserializationContextImpl.parse(DeserializationContextImpl.java:242)
     at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:538)
     at org.apache.axis.Message.getSOAPEnvelope(Message.java:376)
     at org.apache.axis.client.Call.invokeEngine(Call.java:2583)
     at org.apache.axis.client.Call.invoke(Call.java:2553)
     at org.apache.axis.client.Call.invoke(Call.java:1753)
     at com.oracle.sample.ws.ArrayClient.main(ArrayClient.java:44)
org.xml.sax.SAXException: Bad envelope tag: html
     at org.apache.axis.AxisFault.makeFault(AxisFault.java:129)
     at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:543)
     at org.apache.axis.Message.getSOAPEnvelope(Message.java:376)
     at org.apache.axis.client.Call.invokeEngine(Call.java:2583)
     at org.apache.axis.client.Call.invoke(Call.java:2553)
     at org.apache.axis.client.Call.invoke(Call.java:1753)
     at com.oracle.sample.ws.ArrayClient.main(ArrayClient.java:44)
Caused by: org.xml.sax.SAXException: Bad envelope tag: html
     at org.apache.axis.message.EnvelopeBuilder.startElement(EnvelopeBuilder.java:109)
     at org.apache.axis.encoding.DeserializationContextImpl.startElement(DeserializationContextImpl.java:976)
     at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
     at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
     at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
     at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
     at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
     at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
     at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
     at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
     at org.apache.axis.encoding.DeserializationContextImpl.parse(DeserializationContextImpl.java:242)
     at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:538)
     ... 5 more
My client code is following:
Service service = new Service();
Call call = (Call) service.createCall();
call.setTargetEndpointAddress(new java.net.URL("http://localhost:9700/orabpel/default/Array"));
SOAPEnvelope env = new SOAPEnvelope();
Name bodyName = env.createName("ArrayRequest", "tns", "http://localhost/");
SOAPBodyElement request = body.addBodyElement(bodyName);
Name childName = env.createName("input","tns","http://localhost/");
SOAPElement input = request.addChildElement(childName);
input.addTextNode("ORCL");
call.invoke(env);
MessageContext mc = call.getMessageContext();
System.out.println("\n============= Response ==============");
XMLUtils.PrettyElementToStream(mc.getResponseMessage().getSOAPEnvelope().getAsDOM(), System.out);
I'am having the same error with client generated by wsdl2java.
Regards

Hi -
A few things that you may want to try to troubleshoot this issue:
1) Run our sample of calling a BPEL process from Axis, located in:
C:\orabpel\samples\interop\axis\AXISCallingSyncBPEL
2) Run your client through a TCP tunnel to see the specific SOAP request message that is being sent to the BPEL process and the SOAP response that is being generated. This should help you determine which side of the communication is causing the problem, as well as to rule out proxy server or other issues that are very common problems for this situation.
Dave

Error connection using JCO.Client

Hello all,
I got the following problem <b>"Error connection using JCO.Client"</b> and don't know what's wrong. All connections works at the content administration when I test the connection.
Can anyone help me please?
Best regards
Petra

Hi,
I almost tested the JCO connection with the 'test' button successfully at the content administrator. I tested again and it still works. And I have a stand alone webdynpro application (no portal).
Now I got the following error message after completing the coding with 'e.printStackTrace().'.
<i>
"Error connection using JCO.Client:null"
"[Ljava.lang.StackTraceElement:@60db08"
"Could not create JCOClientConnection for logical System:WD_MODELDATA_DEST - Model: class impersonalaccout.intro.model.Z_Fh0002_Datenverwaltung.Please assure that you have configured the RFC connections and/or logical System"
"com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCException:Error connection using JCO.Client:null"
"com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCException: Could not create JCOClientConnection for logical System: WD_MODELDATA_DEST - Model:class impersonalaccout.intro.model.Z_Fh0002_Datenveraltung.Please ***"</i>
Can anyone explaine me what's wrong?
Bye
Petra

WDDynamicRFCExecuteException: Error connecting using JCO.Client: null

Hi
This is a common problem,I have seen many threads , but following them did not solve my problem.
I have the JCOs tested successful from WD Admin. When I create a sample WDJ application with RFC model and deploy it to the server, I get
Exception:com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecution: Error connecting using JCO.Client: null.
I have checked my binding , I have only one input parameter and the code is
      wdComponentAPI.getMessageManager().reportSuccess("Inside wdInit in Component ctrller");
      Z_Plm44_Obsoleteimpactanalysis_Input input = new Z_Plm44_Obsoleteimpactanalysis_Input();
     wdContext.nodeZ_Plm_Input().bind(input);
     wdContext.createZ_Plm_InputElement(input).setV_Type(wdContext.currentZ_Plm_InputElement().getV_Type());
Also I have implemented closing the connection
disconnectifalive
I contacted the basis team... they tell me that everything is fine from their end. they have tried increasing the JCO connection pools.
Thanks for your help in advance
Karthika

Hi Karthika
Check this pdf and try to catch WDDynamicRFCExecution in catch block.
Please put your code in try catch and also import com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecution in your code;
http://www.sappro.com/downloads/WebDynproJava.pdf
Re: User has no RFC authorization for function group.
Hope this will help you.
thanks
Arun Jaiswal

Error in Connecting to BAPI (Error connecting using JCO.Client: null)

Hi,
    I am trying to connect to a BAPI to extract data. However, I am getting this error
    Error connecting using JCO.Client: null
    Pls explain the meaning of the error and solution to the problem
TIA
Himanshu

Hi,
This means you are getting error while executing your model. its not able to use the JCO's.
as I asked previously check your JCO status... its up and running????
Here are some threads having same problem
URGENT :Error connecting using JCO.Client: null
Model and MetaData configarations in JCO Connection
Exception while executing
PradeeP
Edited by: pradeep bondla on Jul 31, 2008 11:53 AM

Error connecting using JCO.Client: null in xRPM in EP

Hi Friends,
I am getting the following error in xRPM through EP
"Error connecting using JCO.Client: null"
I can't enter xRPM, but I can enter other Business packages iViews.
The problem is intermittant and user specific.
Can you pls provide any input on this ?
thanks in advance and warm regards
Purnendu

Hi Flavio,
Thanks for your reply.
The user is created both in the backend as well as in portal.
The roles are also ok.
The error I am getting only while accessing xRPM iViews.
If I restart the instance the error is removed. But it reappears again may be after few days.
This error is intermittant.
May be it is related to the Maximum Number of JCo connections in the WebDynpro configuration.
But I don't have much idea on that.
Can you pls provide any help on this.
Warm regards
Purnendu

Memory leak using thin client

Subject: Memory Leak while using thin client.
From: [email protected] (Alon Albert)
Newsgroups: weblogic.developer.interest.jndi
I have a small test program that causes a memory leak while connecting
to a weblogic server. The code is appended to the end of the msg. The
problem is definatly caused by the InitialContext creation.
Even if I explicitly call the InitialContext.close() method, the
problem persists. I realize I can avoid the problem by using a one
time connection outside the loop but keep in mind that this is only a
test program. The full application REQUIRES me to do a full
reconnection each time it is accessed.
I have read in a previous simmilar post that the problem mught be RMI
related. Is anything I can do about this?
package jmxleak;
import java.net.*;
import java.util.*;
import javax.management.*;
import javax.naming.*;
public class Main {
String host;
String username;
String password;
MBeanServer mbs;
public static void main(String[] args) {
while (true) {
Main main = new Main(args[0], args[1], args[2]);
main.connect();
main = null;
System.out.println("Collecting garbage.");
System.gc();
public Main(String host, String username, String password) {
this.host = host;
this.username = username;
this.password = password;
private void connect() {
try {
System.out.print("Connecting..., ");
Thread.currentThread().setContextClassLoader(new
URLClassLoader(new URL[] { new URL("http://" + host + "/classes/")}));
Hashtable env = new Hashtable();
env.put("java.naming.factory.initial",
"weblogic.jndi.WLInitialContextFactory");
env.put("java.naming.provider.url", "t3://" + host);
if (username.length() > 0 && password.length() > 0) {
env.put("java.naming.security.principal", username);
env.put("java.naming.security.credentials", password);
System.out.print("Creating context..., ");
InitialContext ctx = new InitialContext(env);
catch (Exception e) {
e.printStackTrace();

Subject: Memory Leak while using thin client.
From: [email protected] (Alon Albert)
Newsgroups: weblogic.developer.interest.jndi
I have a small test program that causes a memory leak while connecting
to a weblogic server. The code is appended to the end of the msg. The
problem is definatly caused by the InitialContext creation.
Even if I explicitly call the InitialContext.close() method, the
problem persists. I realize I can avoid the problem by using a one
time connection outside the loop but keep in mind that this is only a
test program. The full application REQUIRES me to do a full
reconnection each time it is accessed.
I have read in a previous simmilar post that the problem mught be RMI
related. Is anything I can do about this?
package jmxleak;
import java.net.*;
import java.util.*;
import javax.management.*;
import javax.naming.*;
public class Main {
String host;
String username;
String password;
MBeanServer mbs;
public static void main(String[] args) {
while (true) {
Main main = new Main(args[0], args[1], args[2]);
main.connect();
main = null;
System.out.println("Collecting garbage.");
System.gc();
public Main(String host, String username, String password) {
this.host = host;
this.username = username;
this.password = password;
private void connect() {
try {
System.out.print("Connecting..., ");
Thread.currentThread().setContextClassLoader(new
URLClassLoader(new URL[] { new URL("http://" + host + "/classes/")}));
Hashtable env = new Hashtable();
env.put("java.naming.factory.initial",
"weblogic.jndi.WLInitialContextFactory");
env.put("java.naming.provider.url", "t3://" + host);
if (username.length() > 0 && password.length() > 0) {
env.put("java.naming.security.principal", username);
env.put("java.naming.security.credentials", password);
System.out.print("Creating context..., ");
InitialContext ctx = new InitialContext(env);
catch (Exception e) {
e.printStackTrace();

Interactive reporting using web client in Hyperion Workspace

Hi all,
I was trying to create a new interactive report using following process:
1)Logon to Workspace using browser
2)File -> New -> document
3)select the option: "Create interactive reporting document"
4)Browse for .oce file
5)Click finish, once the .oce file is selected.
After these steps:
Initially I was getting message regarding checking web client status...
this was taking lots of time so I cancelled the process and restarted from step 1.
Now, after step 5, I am getting a file save option showing source of file as server of the Workspace.I am working on a local machine and accessing the workspace product through web browser.
If I save this file in local machine I don't get an option to open this file from workspace using :
File -> open -> document.
and alternatively if try to open this locally from the machine I don't have proper application on my local machine.
I am badly trapped in this viscious circle.... Kindly help.
Also, it will be gr8 if somebody could suggest some link for understanding the process of creating a new interactive report , using web client on workspace.
Thanks in advance..
Edited by: user12973893 on May 5, 2010 3:40 AM

Hi all,
I got to know that import and export option is available with "user->reports" and "file in report folder" respectively, when we go for Explore option.
So storing to local machine and retrieving it back is no more a problem.
But still I have hardly any idea as to how to start with interactive reporting in Workspace using web client.
If any of you come across any such tutorial on interactive reporting using web client on workspace please tell.
I come to know that Interactive reporting studio is available for interactive reporting purpose: any of you please tell me if "reporting and analysis client.." available on oracle edelivery is sufficient for interactive reporting studio or we need to install something specific for working with Interactive reporting studio.

Web service client authentication problem

I applied security role to deployed web services. When I use clientgen to generate client stub or using java client to get WSDL, I got authentication error asking for username and password.
This only happens when I use import in my WSDL file to import other schema files. I think the authentication process happened when retrieving wsdl file, but not import schema files.
Is this some kind of BEA bugs or known issue?
Any advice is appreciated.

Yes, this is a problem. It should be fixed in upcoming release. The work around is embeding the schema to WSDL or run clientgen against a local copy.

EPI-USE DSM Client Synch problem

Similar Messages

Maybe you are looking for