JDBC lookup error in 7.1

I get the below error while importing the metadata from table in the external definition dbtab, I am using the receiver communication channel,the channel is working fine for file to jdbc,any help appreciated
Error in CC
Error processing request in sax parser: Error when executing statement for table/stored proc. 'metadataRequest' (structure 'statement'): com.ibm.db2.jcc.b.SqlException: Invalid argument: unknown column name COLUMN_NAME
Error in ED
Error occurred while attempting to connect to database (LOOKUPEXCEPTION)
Exception during processing the payload. Error when
calling an adapter by using the communication channel
CC_GeoRestrictions_JDBC_Receiver (Party: , Service:
BC_GeoRestrictions_SAP_To_Legacy, Object ID: c0adebcbf7603e82a2b6a1b100139c8b)
XI AF API call failed. Module exception: (No information
available). Cause Exception: 'Error processing request
in sax parser: Error when executing statement for table/stored
proc. 'metadataRequest' (structure 'statement'): com.ibm.db2.jcc.b.SqlException:
Invalid argument: unknown column name COLUMN_NAME'.
com.sap.aii.mapping.lookup.LookupException: Error when
calling an adapter by using the communication channel
CC_GeoRestrictions_JDBC_Receiver (Party: , Service:
BC_GeoRestrictions_SAP_To_Legacy, Object ID: c0adebcbf7603e82a2b6a1b100139c8b)
XI AF API call failed. Module exception: (No information
available). Cause Exception: 'Error processing request
in sax parser: Error when executing statement for table/stored
proc. 'metadataRequest' (structure 'statement'): com.ibm.db2.jcc.b.SqlException:
Invalid argument: unknown column name COLUMN_NAME'.

select the display option in the Table import I see the tables displayed
did you try to login to the DB and check for the table structure?
If still not working then it seems to be a bug....you can raise an OSS ticket for this.
the channel is working fine for file to jdbc
is it working on the same table that is giving error?
Edited by: abhishek salvi on Jan 20, 2011 9:50 AM

Similar Messages

Getting error in JDBC lookup

Hi ,
I am developing a scenario file to file with the help of JDBC lookup. Message successfully process in MONI but when I check message payload in Technical Routing desired result not appears it will show some text like
"The returned object is not of type LinkedList: com.sap.aii.adapter.xi.ms.XIMessage" please suggest why this error occurred
Regards,
Amit Shivhare

Hi Satish,
in JAVA UDF i have put wrong CC. now i have put rec. JDBC channel in UDF but not getting error during mapping testing
Cannot produce target element /ns0:MT_JDBCLOOKUP_REC/row/UPDATE_USER. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
my database table structure is
DUMMY_KEY                      NOT NULL VARCHAR2(200)
INTEGRATIONNAME                NOT NULL VARCHAR2(60)
DEPLOYMENTNAME                 NOT NULL VARCHAR2(49)
COMPONENTINSTANCE1             NOT NULL VARCHAR2(40)
COMPONENTINSTANCE2             NOT NULL VARCHAR2(40)
MAXMEMORY                      NOT NULL NUMBER(4)
MAXCPU                         NOT NULL NUMBER(3)
FT_LB                          NOT NULL VARCHAR2(2)
HMA1                           NOT NULL VARCHAR2(200)
HMA2                           NOT NULL VARCHAR2(200)
ACTIVEFLAG                     NOT NULL VARCHAR2(5)
UPDATE_USER                             VARCHAR2(50)
UPDATE_DATE                    NOT NULL TIMESTAMP(6)
and UDF
   //write your code here
//write your code here
String Query = " ";
Channel channel = null;
DataBaseAccessor accessor = null;
DataBaseResult resultSet = null;
// Build the Query String
Query = "Select UPDATE_USER from CMS_PAR_MONITOR where INTEGRATIONNAME = '" + UName[0] + " ' ";
try{
//Determine a channel, as created in the Configuration
channel = LookupService.getChannel("Ser_Test","CC_JDBC_REC_JDBCLookUP");
//Get a system accessor for the channel. As the call is being made to an DB, an DatabaseAccessor is obtained.
accessor = LookupService.getDataBaseAccessor(channel);
//Execute Query and get the values in resultset
resultSet = accessor.execute(Query);
for(Iterator rows = resultSet.getRows();rows.hasNext();){
Map rowMap = (Map)rows.next();
result.addValue((String)rowMap.get("URole"));
catch(Exception ex){
result.addValue(ex.getMessage());
finally{
try{
if (accessor!=null) accessor.close();
catch(Exception e){
result.addValue(e.getMessage());
regards, amit

Reg:Error in JDBC Lookup Table

Hi All,
My actual requirement is,A project ID is being triggered to PI which will pull the data from the database(SQL Server 2000) ,from different tables and it has to post to file.Receiver side I will be using the File Adapter.
For this I am using JDBC Lookup table through an User Defined function.
// code
String Query = " ";
Channel channel = null;
DataBaseAccessor accessor = null;
DataBaseResult resultSet = null;
//Build the Query String
Query = "Select proj_id, proj_short_name from PROJECT where proj_id = '"proj_id[0]"'";
try{
channel = LookupService.getChannel("bs_test" ,"cc_test");
//Get a system accessor for the channel. As the call is being made //to an DB, an DatabaseAccessor is obtained.
accessor = LookupService.getDataBaseAccessor(channel);
//Execute Query and get the values in output
resultSet = accessor.execute(Query);
Iterator rows = null;
rows = resultSet.getRows();
while(rows.hasNext())
Map rowMap = (Map)rows.next();
// String proj_id = rowMap.get("proj_id");
// String project_name = rowMap.get("proj_short_name");
result.addValue((String)rowMap.get("proj_id "));
result.addValue((String)rowMap.get("project_short_name "));
//result.addValue(proj_id);
//result.addValue(project_short_name);
catch(Exception ex)
result.addValue(ex.getMessage());
finally{
try{
if (accessor!=null) accessor.close();
catch(Exception e)
result.addValue(e.getMessage());
//@@end
While testing in test tab of Message Mapping,I am getting the value as 'NULL' for the project id and am not able to see the other field.
Please suggest me in this.
Thanks in Advance,
Lavanya.B

Hi All,
My actual requirement is,A project ID is being triggered to PI which will pull the data from the database(SQL Server 2000) ,from different tables and it has to post to file.Receiver side I will be using the File Adapter.
For this I am using JDBC Lookup table through an User Defined function.
// code
String Query = " ";
Channel channel = null;
DataBaseAccessor accessor = null;
DataBaseResult resultSet = null;
//Build the Query String
Query = "Select proj_id, proj_short_name from PROJECT where proj_id = '"proj_id[0]"'";
try{
channel = LookupService.getChannel("bs_test" ,"cc_test");
//Get a system accessor for the channel. As the call is being made //to an DB, an DatabaseAccessor is obtained.
accessor = LookupService.getDataBaseAccessor(channel);
//Execute Query and get the values in output
resultSet = accessor.execute(Query);
Iterator rows = null;
rows = resultSet.getRows();
while(rows.hasNext())
Map rowMap = (Map)rows.next();
result.addValue((String)rowMap.get("proj_id "));
result.addValue((String)rowMap.get("project_short_name "));
catch(Exception ex)
result.addValue(ex.getMessage());
finally{
try{
if (accessor!=null) accessor.close();
catch(Exception e)
result.addValue(e.getMessage());
//@@end
While testing in test tab of Message Mapping,I am getting the value as 'NULL' for the project id and am not able to see the other field value.
Output:
<?xml version="1.0" encoding="UTF-8" ?>
<ns0:mt_test_recv xmlns:ns0="http://xxxx">
<proj_id>null</proj_id>
<proj_short_name />
</ns0:mt_test_recv>
Please suggest me in this.
Thanks in Advance,
Lavanya.B
Edited by: Lavanya Balanandham on Dec 5, 2008 6:51 AM

How to use JDBC Lookup in PI 7.1 ?

Hi,
Please advise how to use JDBC lookup in message mapping PI 7.1 ? any reference link / document ?
I have followed this step below :
1. Create the external definition for the database table.
2. Use the external definition (table) in message mapping JDBC Lookup.
But the target still "Yellow colour" meanint the mapping hasnot completed yet ? why ? and when i double click the JDBC lookup
there some error message
"No suitable parameter found; define new parameter of type 'Channel' first"
Please advise.
Thank You and Best Regards
Fernand

Hi Fernand,
JDBC Lookup can be done in PI 7.1 using below mentioned steps :
1) Create a communication channel between PI and the database to connect to database.
2) Import the table data as External Definition.
3) In message mapping where this lookup is to be used select JDBC Lookup under Conversions and map
4) Double Click on JDBC Lookup
5) Select parameter and a database table (imported as the external definition). All the elements of the table will appear in the middle column. Select and move the input parameters to the left side column and the output parameters to the right side column. Click OK.
6) Under message mapping go to signature tab and define the parameter as channel and category as JDBC Adapter Type.
7) Under Operation mapping define the parameter & associate it with parameter defined in Message Mapping.
Thanks
Amit

JDBC Lookup in PI 7.1 - SELECT ? FROM DUAL and Connection timed out

Hi,
We have a scenarios (Idoc to JMS) with JDBC lookup. We have used graphical JDBC lookup functionality.
We are reading country names for a given country code from SAP in an external database table. The query is so simple. That should not take much time
Now the actual issues is,
When we are executing the scenario, its taking quite a long time. Almost 6 minutes to excute a mapping. Which causing high performance issue in the Porduction.
We started the inviestigation about found some interesting stuff. Here we have used Willy Introscope for the investigation.
1. First few messages are taking quite a long time. LIke 6 minutes per messages. As i can see in the log i am getting below error in Willy,
I dont know why PI is executing below queury apart from real secelt query to fetch the country name. I am getting below error: Error Message: Backends|ABCD2 mydatabase01-1526 (Oracle DB)|SQL|Dynamic|Query|SELECT ? FROM DUAL: java.sql.SQLException: Io exception: Connection timed out
2. After couple of messages, interface works very normal. I mean rest of the messages works pretty fine.
Please let me know if you have any idea about this error. What could be the problem for the issue.
Thank you in advnace.
Best Regards,
Prasad.

Did you check how many SQL requests were executed per one message ? Do you have a log of these SQL requests ?
I assume that the country table is quite small, so that lookup should not be an issue.
About this:
>Message: Backends|ABCD2 mydatabase01-1526 (Oracle DB)|SQL|Dynamic|Query|SELECT ? FROM DUAL: >java.sql.SQLException: Io exception: Connection timed out
1. I only know SELECT * FROM DUAL, not SELECT ? FROM DUAL. Better use the former
2. the exception means that the database server can not be reached => check your network configuration
So I assume that there is a network (performance) problem between PI and this Oracle server. Or the Oracle Server is so overloaded that it has (sometimes) problems in processing new requests.
CSY
Edited by: Christian Sy on Mar 9, 2010 10:17 AM

JDBC Lookup in message mapping

Hi Folks,
in a message-mapping i use a jdbc lookup.
i get this error, can anybody help me ?
Put value [Plain exception:Problem when calling an adapter by using communication channel JDBC_MKA_Receiver_Lookup (Party: , Service: R3EREDATA, Object ID: 3ab59ba811163c5697dbcd40fb0c4957) Check whether the communication channel exists in the Integration Directory; also check the cache notifications for the instance Integration Server (central Adapter-Engine) Channel object with Id Channel:3ab59ba811163c5697dbcd40fb0c4957 not available in CPA Cache.
thanks for your help

Hi Folks,
now i get a new error.
it will be nice when you could answered me, thanks
Put value [Exception during processing the payload.Problem when calling an adapter by using communication channel JDBC_MKA_Receiver_Lookup (Party: , Service: BS_EPS, Object ID: 866ef440ca5b3cefb1381267f5693591) XI AF API call failed. Module exception: (No information available). Cause Exception: 'JDBC Adapter configuration not initialized: null'. com.sap.aii.mapping.lookup.LookupException: Problem when calling an adapter by using communication channel JDBC_MKA_Receiver_Lookup (Party: , Service: BS_EPS, Object ID: 866ef440ca5b3cefb1381267f5693591) XI AF API call failed. Module exception: (No information available). Cause Exception: 'JDBC Adapter configuration not initialized: null'. at java.lang.Throwable.<init>(Throwable.java:194) at java.lang.Exception.<init>(Exception.java:41) at com.sap.aii.mapping.api.StreamTransformationException.<init>(StreamTransformationException.java:29) at com.sap.aii.mapping.lookup.LookupException.<init>(LookupException.java:72) at com.sap.aii.ibrun.server.lookup.AdapterProxyLocal.execute(AdapterProxyLocal.java:131) at com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.execute(SystemAccessorInternal.java:68) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:149) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:77) at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169) at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:296) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211) at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634) at javax.servlet.http.HttpServlet.service(HttpServlet.java:733) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:332) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:0) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:336) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:868) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:250) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:0) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:92) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:30) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:35) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:99) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.af.service.api.AFException: XI AF API call failed. Module exception: (No information available). Cause Exception: 'JDBC Adapter configuration not initialized: null'. at java.lang.Throwable.<init>(Throwable.java:194) at java.lang.Exception.<init>(Exception.java:41) at com.sap.aii.af.service.api.AFException.<init>(AFException.java:88) at com.sap.aii.af.service.api.AdapterAccess.sendMsg(AdapterAccess.java:214) at com.sap.aii.af.service.api.AdapterAccess.execute(AdapterAccess.java:283) at com.sap.aii.ibrun.server.lookup.AdapterProxyLocal.execute(AdapterProxyLocal.java:123) at com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.execute(SystemAccessorInternal.java:68) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:149) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:77) at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169) at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:296) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211) at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634) at javax.servlet.http.HttpServlet.service(HttpServlet.java:733) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:332) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:0) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:336) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:868) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:250) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:0) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:92) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:30) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:35) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:99) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) ]

Problem JDBC lookup PI 7.1

Hello everybody,
I have a scenario where the PI interface that were 7, were migrated to the PI 7.1 SP 05.
With this, we are having problems in PI 7.1, JDBC Lookup.
If I use the JDBC Lookup that exists in PI 7.1, it works.
Plus the problem, I have many interfaces, which were made by the JDBC Lookup IP 7, and error is happening in the IP 7.1, the error is
Error when calling an adapter by using the communication channel CC_EAI_JDBC_CADASTRO_Receiver (Party: , Service: BS_MSSQL_DEV, Object ID: 574a4888bf11379d99fa7359026ddb7c) The channel with object ID 574a4888bf11379d99fa7359026ddb7c could not be found in the Integration Server Java Cache. Check if the channel exists in the Integration Builder Directory and execute a refresh of the Java Cache.
The error happens in the line of code Featured:
   / / Set channel According to config Directory
   channel = LookupService.getChannel (BS_MSSQL_DEV "," CC_EAI_JDBC_CADASTRO_Receiver ");
   / / Set database accessor
   accessor = LookupService.getDataBaseAccessor (channel);
Its in PI 7.1, still be done this type of JDBC Lookup??
How can I solve this problem??
Thanks,
Marlon

Hello,
Stefan and Guru, had not noticed the '*' in the Party's CC.
I created another CC without the '*', and it worked.
Thank you all for your help.
Marlon
Edited by: Marlon Sperandio Monteiro on Sep 15, 2010 3:54 PM
Edited by: Marlon Sperandio Monteiro on Sep 15, 2010 3:54 PM

Can not save JDBC lookup in mapping (PI 7.1 SP07)

Hi All,
When I try to save my JDBC lookup, I get error while executing save - 'Binding rec0 is not found in the brick. Check update method'
I made Re-initialization in Java Web Start Administration, but problem did not resolve.
Regards,
Andrey.

Hi
We have the same error. Did you find a solution?
Cheers
Philippe

DB Lookup Error

Dear All,
I am getting following Error in the DB Lookup:
Error: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.connector.exceptions.BaseResourceException: Cannot open resource(Managed Connection) with LocalTransaction support or add a second one in the same transaction, for component "webContainer/applications/sap.com/TestDB/TestDB" in application "sap.com/TestDB".
I followed exactly as told in this Blog Please Help
/people/william.li/blog/2007/03/30/using-jdbc-connection-pool-in-xi-message-mapping
Please Help
Regards,
Prakash

Dear Amit,
Sorry for the very late reply. as you told i am not ableto change the isolation parameter inthe DataSource at all. its resetting back to DEFAULT , i am not able to set it to SERIALISABLE.
So i tried to create a new Data Source with isolation level anything other t han DEFAULT its showing following error
error----
java.rmi.RemoteException: com.sap.engine.services.dbpool.exceptions.BaseRemoteException: Error during runtime changes of application "sap.com/SQLServer". [id = ConfigError]     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.updateDataSourceApplication(DataSourceManagerImpl.java:705)     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)     at java.lang.reflect.Method.invoke(Method.java:324)     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)     at java.security.AccessController.doPrivileged(Native Method)     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)Caused by: java.rmi.RemoteException: Error occurred while making runtime changes with application sap.com/SQLServer; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 8612850:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Error while parsing file "SQLServer.xml".     at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:484)     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)     at com.sap.engine.services.deploy.server.application.RuntimeTransaction.finalActions(RuntimeTransaction.java:286)     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:339)     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.makeRuntimeChanges(DeployCommunicatorImpl.java:344)     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.updateDataSourceApplication(DataSourceManagerImpl.java:685)     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)     at java.lang.reflect.Method.invoke(Method.java:324)     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)     at java.security.AccessController.doPrivileged(Native Method)     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)Caused by: com.sap.engine.services.dbpool.exceptions.BaseIllegalArgumentException: The value of tag <driver-name> is not specified.     at com.sap.engine.services.dbpool.deploy.XMLUtils.processDataSource(XMLUtils.java:298)     at com.sap.engine.services.dbpool.deploy.XMLUtils.processXML(XMLUtils.java:231)     at com.sap.engine.services.dbpool.deploy.XMLUtils.processXML(XMLUtils.java:206)     at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:457)     ... 39 more
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.makeRuntimeChanges(DeployCommunicatorImpl.java:346)     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.updateDataSourceApplication(DataSourceManagerImpl.java:685)     ... 29 moreCaused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 8612850:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Error while parsing file "SQLServer.xml".     at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:484)     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)     at com.sap.engine.services.deploy.server.application.RuntimeTransaction.finalActions(RuntimeTransaction.java:286)     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:339)     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.makeRuntimeChanges(DeployCommunicatorImpl.java:344)     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.updateDataSourceApplication(DataSourceManagerImpl.java:685)     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)     at java.lang.reflect.Method.invoke(Method.java:324)     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)     at java.security.AccessController.doPrivileged(Native Method)     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)Caused by: com.sap.engine.services.dbpool.exceptions.BaseIllegalArgumentException: The value of tag <driver-name> is not specified.     at com.sap.engine.services.dbpool.deploy.XMLUtils.processDataSource(XMLUtils.java:298)     at com.sap.engine.services.dbpool.deploy.XMLUtils.processXML(XMLUtils.java:231)     at com.sap.engine.services.dbpool.deploy.XMLUtils.processXML(XMLUtils.java:206)     at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:457)     ... 39 more
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.sleepClientThread(ParallelAdapter.java:270)     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:127)     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)     at com.sap.engine.services.deploy.server.application.RuntimeTransaction.finalActions(RuntimeTransaction.java:286)     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:339)     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.makeRuntimeChanges(DeployCommunicatorImpl.java:344)     ... 30 more     at com.sap.engine.services.dbpool.exceptions.BaseRemoteException.writeReplace(BaseRemoteException.java:178)     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)     at java.lang.reflect.Method.invoke(Method.java:324)     at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:896)     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1011)     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)     at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)     at javax.management.MBeanException.writeObject(MBeanException.java:126)     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)     at java.lang.reflect.Method.invoke(Method.java:324)     at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)     at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)     at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:964)     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)     at java.lang.reflect.Method.invoke(Method.java:324)     at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)     at com.sap.engine.services.jmx.ResponseMessage.writeBody(ResponseMessage.java:177)     at com.sap.engine.services.jmx.Message.writeMsg(Message.java:257)     at com.sap.engine.services.jmx.Message.getMsg(Message.java:453)     at com.sap.engine.services.jmx.Message.writeExternal(Message.java:505)     at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1267)     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:66)     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)     at java.security.AccessController.doPrivileged(Native Method)     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
error----
Please Advice
Regards,
prakash

JDev 10.1.3 lookup error

Hello everybody.
I'm trying get session bean in JDev 10.1.3 debug:
Context context = new InitialContext();
Object obj = context.lookup("ManageRecords");
ManageRecordsHome home =
(ManageRecordsHome)PortableRemoteObject.narrow(
obj, ManageRecordsHome.class);
return home.create();
ang got this exception:
05/06/27 23:52:11 javax.naming.NamingException: Lookup error: java.io.IOException: Attempted read of 1802399607 bytes exceeds the maximum interceptor data length of 5242880; nested exception is:
     java.io.IOException: Attempted read of 1802399607 bytes exceeds the maximum interceptor data length of 5242880 [Root exception is java.io.IOException: Attempted read of 1802399607 bytes exceeds the maximum interceptor data length of 5242880]
05/06/27 23:52:11      at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:183)
05/06/27 23:52:11      at javax.naming.InitialContext.lookup(InitialContext.java:347)
05/06/27 23:52:11      at com.msr.op.flat.model.EDMLocator.getService(EDMLocator.java:21)
05/06/27 23:52:11      at com.msr.op.vc.DicCheckBox.doStartTag(DicCheckBox.java:50)
05/06/27 23:52:11      at formUnload2e_jsp._jspService(formUnload.jsp:16)
05/06/27 23:52:11      at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
05/06/27 23:52:11      at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:343)
05/06/27 23:52:11      at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:543)
05/06/27 23:52:11      at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:441)
05/06/27 23:52:11      at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
05/06/27 23:52:11      at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:61)
05/06/27 23:52:11      at oracle.security.jazn.oc4j.JAZNFilter.doFilter(Unknown Source)
05/06/27 23:52:11      at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:672)
05/06/27 23:52:11      at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:378)
05/06/27 23:52:11      at com.evermind.server.http.ServletRequestDispatcher.unprivileged_forward(ServletRequestDispatcher.java:272)
05/06/27 23:52:11      at com.evermind.server.http.ServletRequestDispatcher.access$100(ServletRequestDispatcher.java:36)
05/06/27 23:52:11      at com.evermind.server.http.ServletRequestDispatcher$2.oc4jRun(ServletRequestDispatcher.java:206)
05/06/27 23:52:11      at oracle.oc4j.security.OC4JAccessController.doPrivilegedWithException(OC4JAccessController.java:186)
05/06/27 23:52:11      at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:85)
05/06/27 23:52:11      at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:211)
05/06/27 23:52:11      at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069)
05/06/27 23:52:11      at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
05/06/27 23:52:11      at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
05/06/27 23:52:11      at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
05/06/27 23:52:11      at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
05/06/27 23:52:11      at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
05/06/27 23:52:11      at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
05/06/27 23:52:11      at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:61)
05/06/27 23:52:11      at oracle.security.jazn.oc4j.JAZNFilter.doFilter(Unknown Source)
05/06/27 23:52:11      at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:672)
05/06/27 23:52:11      at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:378)
05/06/27 23:52:11      at com.evermind.server.http.ServletRequestDispatcher.unprivileged_forward(ServletRequestDispatcher.java:272)
05/06/27 23:52:11      at com.evermind.server.http.ServletRequestDispatcher.access$100(ServletRequestDispatcher.java:36)
05/06/27 23:52:11      at com.evermind.server.http.ServletRequestDispatcher$2.oc4jRun(ServletRequestDispatcher.java:206)
05/06/27 23:52:11      at oracle.oc4j.security.OC4JAccessController.doPrivilegedWithException(OC4JAccessController.java:186)
05/06/27 23:52:11      at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:85)
05/06/27 23:52:11      at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:211)
05/06/27 23:52:11      at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069)
05/06/27 23:52:11      at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
05/06/27 23:52:11      at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
05/06/27 23:52:11      at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
05/06/27 23:52:11      at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
05/06/27 23:52:11      at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
05/06/27 23:52:11      at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
05/06/27 23:52:11      at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:61)
05/06/27 23:52:11      at oracle.security.jazn.oc4j.JAZNFilter.doFilter(Unknown Source)
05/06/27 23:52:11      at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:672)
05/06/27 23:52:11      at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:378)
05/06/27 23:52:11      at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:869)
05/06/27 23:52:11      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:288)
05/06/27 23:52:11      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:120)
05/06/27 23:52:11      at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:299)
05/06/27 23:52:11      at java.lang.Thread.run(Thread.java:534)
05/06/27 23:52:11 Caused by: java.io.IOException: Attempted read of 1802399607 bytes exceeds the maximum interceptor data length of 5242880
05/06/27 23:52:11      at com.evermind.server.rmi.RMIConnection.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMIConnection.java:800)
05/06/27 23:52:11      at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:114)
05/06/27 23:52:11      at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:250)
05/06/27 23:52:11      at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:154)
05/06/27 23:52:11      ... 52 more
Under JDev 10.1.2 this code works fine.
Any ideas?
Me guarded, that at OC4J container startup i've got this messages:
27.06.2005 23:52:03 com.evermind.server.ejb.EJBPackageDeployment isIIOPConfigured
INFO: Beans associated with application current-workspace-app will not be available via RMI/IIOP: GenerateIIOP system property=false, enableIIOP application setting=false, server.xml configured for IIOP=true

Hi Dvohra,
Thank you so much for your help. I implemented your suggested changes, it's getting a bit better, no lookup hick up Yeah :=), BUT I have following message:
[TopLink Finest]: Register the existing object tomis2.webapp.data.model.UtilityCompanies@dcbc7b
07/11/30 17:49:45 javax.naming.NameNotFoundException: java:comp/env/jdbc/P03DB not found in OFMTomis-ViewController-webapp
07/11/30 17:49:45      at com.oracle.naming.J2EEContext.getSubContext(J2EEContext.java:225)
07/11/30 17:49:45      at com.oracle.naming.J2EEContext.lookup(J2EEContext.java:172)
07/11/30 17:49:45      at com.evermind.server.ApplicationContext.lookupInJavaContext(ApplicationContext.java:308)
DO I NEED ANOTHER XML TO FIX java:comp/env/jdbc/P03DB ?
Robert.

JDBC Scenario with JDBC Lookup and Updates

Dear Experts,
I am working on a JDBC receiver scenario.
In this scenario, we are also using JDBC lookup to check the maximum EntyNumber which is a primary key. We are manually incrementing this primary key by one and inserting the record into the database.
Both JDBC lookup and JDBC Insert are two differnt tasks. Thus when we send multiple IDOC's concurrently JDBC lookup fetches old values and when we try to insert the record if gives error of PRIMARY KEY VIOLATION.
For example, consider the below scenario,
Assume that there are already 10 records in the database.
1. Two IDOCs No 1 and 2 sent from SAP system at the same time.
2. Now, during the mapping of 1st IDOC we did a lookup and found that latest entry number in the database table is 10 and we mapped the entry number to 11 ( 10+1, i.e. next record )
3. Before updating this record in the database, second IDOC triggered. During JDBC lookup of the sceond IDOC, we got the same entry as the earlier record has yet to be updated.
4. During JDBC call we get the SQL error that "Primary Key Violation" because both the records have same primary key as "11".
Kindly share your ideas.
(SAP system is not sending the IDOC's in any certain order and we need a solution in PI itself. )
- Shri

>>> I am actually sending the primary key value to more than one table as a foreign key. I am looking for some solution
If you are passing primary key value to many tables then jdbc lookup would not be solution. Use stored procedure.
Refer this link for data type creation for stored procedure
http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm

JDBC Lookup problem

we are facing this problem...
from SAP we send the idoc: WP_PLU03 to PI through transaction WPMA.
PI do the data format in: XML Document Format for the Mode XMB2DB_XML (http://help.sap.com/saphelp_sem40bw/helpdata/en/4d/8c103e05df2e4b95cbcc68fed61705/frameset.htm)
but before to do this format, a couple of RFC Lookups and JDBC lookups are executed.
the important here are the JDBC lookups.
when SAP sends a lot of Articles, the WP_PLU03 generates many segments, so only one LUW is not enough,then SAP automatically separates in 2 or more LUWs as needed.
the first LUW is processed correctly, so, the JDBC adapter does good all the LOOKUPS, and the XMB2DB_XML is well formed and sent to the JDBC adapter for his process.
but, the error is in the second LUW process , when the JDBC adapter begins to do the LOOKUPS, it STOPS, without error, or any alert...
any idea?

>
Christophe PFERTZEL wrote:
> Hi Guillermo,
>
> 1 LUW = 1 IDOC = 1 msg ? Do you use the same JDBC adapter for lookups AND msg sending ? Are those lookups performed using your own UDF/class or are you using PI feature ?
>
> Have you also check for error msgs in XI/PI logs and traces ?
>
> Rgds
> Chris
hi,
1 LUW = A LOT of iDoc = MANY MSG.
I've tried both, first, only one JDBC adapter for the lookup and process the message...
result = the same problem, JDBC stops with the green circle in the RWB.
second try, 2 jdbc adapters, one for the lookup and the other for the message process,
result = the lookup jdbc adapter face the same problem.
I'm using an UDF for the lookup.
> Have you also check for error msgs in XI/PI logs and traces ?
that's the problem, PI doesn't shows error.
THANKS!

Lookup error throwing capabilities

Hi Gurus,
Help me by giving some good solutions for the below requirement:-
I am using a JDBC lookup in my scenario. Now, I want to implement some error throwing capabilities in the same.
For eg:- If the lookup was not excuted because of the connection failure, or the data was not fetched as a result of the lookup, then some exception should come up in the monitoring.
Thanks in advance.
Neetesh

Hi,
Here is some information about alerts ;):
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
/people/ginger.gatling/blog/2005/12/02/innovative-ways-to-use-alerts
/people/bhavesh.kantilal/blog/2006/07/25/triggering-xi-alerts-from-a-user-defined-function
/people/alessandro.guarneri/blog/2006/01/26/throwing-smart-exceptions-in-xi-graphical-mapping
/people/michal.krawczyk2/blog/2005/03/13/alerts-with-variables-from-the-messages-payload-xi--updated
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7f2243d711d1893e0000e8323c4f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/68/253239bd1fa74ee10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/cf/f2bbc8142c11d3b93a0000e8353423/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5d/2166e6a91d11d188de0000e8216438/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/05/bb223905b61b0ae10000000a11402f/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/33/4a773f12f14a18e10000000a114084/frameset.htm
Regarding this error, please first import archive with this class. Afterwards import correct package in UDF. And of course remember that in java you end line with ; not .
Regards,
Wojciech

A jdbc transaction error occur

Hi Everybody
A jdbc transaction error occur when I deploy the application on the server .
Below is the stack trace
#SAP J2EE Engine JTA Transaction : [03bfffffffd3a000ffffffc0]####Application [13]##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.dbpool.exceptions.BaseSQLException: Cannot commit transaction from this connection of "YTSQLS2K" DataSource. This resource participates in a local or distributed transaction.
#SAP J2EE Engine JTA Transaction : [03bfffffffd3a000ffffffc0]####Application [13]##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.dbpool.exceptions.BaseSQLException: Cannot initiate transaction from a connection of "YTSQLS2K" DataSource. Local or distributed transaction has already started.
#SAP J2EE Engine JTA Transaction : [03bfffffffd3a000ffffffc0]####Application [13]##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.dbpool.exceptions.BaseSQLException: Cannot commit transaction from this connection of "YTSQLS2K" DataSource. This resource participates in a local or distributed transaction.
Any idea about it
I use the jdbc version in datasource <jdbc-1.x>
is there a need to replace it with <jdbc-2.0>
Thank You
Syed Saifuddin

Hibernate allows you to choose transaction manager. As Nikolay pointed out, in a JEE envirnment it's prefferable to use JTA transactions. All you need to do is to configure hibernate to use a JTA transaction manager. It is all written in the Hibernate documentations. See
http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#configuration-j2ee
and
http://www.hibernate.org/42.html#A5 .
The relevant properties that need to be set in the configuration are:
hibernate.transaction.factory_class=org.hibernate.transaction.JTATransactionFactory
and
hibernate.transaction.manager_lookup_class=<Class that knows how to lookup>
You need to implement a class that knows how to lookup user transaction in SAP J2EE Egnine.
The class must extend org.hibernate.transaction.JNDITransactionManagerLookup and only override its abstract method getName (simply returning the lookup string). Then provide the fully qualified name as value of the property and make sure that Hibernate can load the class.
That should work.
HTH
-Georgi
Message was edited by:
Georgi Pavlov

JDBC Lookup - Import table data from a different schema in same DB

Hi XI Experts,
We are facing an issue while importing a Database table into the external definition in PI 7.1.
The details are as below:
I have configured user 'A' in PI communication channel to access the database. But the table that I want to access is present in schema "B". Due to this, I am unable to view the table that I have to import in the list available.
In other words, I am trying to access a table present in a different schema in the same database. Please note that my user has been given all the required permissions to access different schema. Even then, I am unable to access the table in different schema.
Kindly provide your valuable suggestions as to how I can import table which is present in another schema but in the same Database.
Regards,
Subbu

If you are using PI 7.1, then you can do JDBC Lookup to import JDBC meta data (table structures from DB). Configure a jdbc receiver communication channel where you specify username and password which has permission to access schema A and Schema B of database. Specify database name in the connection string. Then you might have access to import both schema.
Please refer these links
SAP PI 7.1 Mapping Enhancements Series: Graphical Support for JDBC and RFC Lookups
How to use JDBC Lookup in PI 7.1 ?

JDBC lookup error in 7.1

Similar Messages

Maybe you are looking for