Topic
4 replies Latest Post - ‏2013-05-18T21:26:59Z by kr.mukesh
Jinka
Jinka
11 Posts
ACCEPTED ANSWER

Pinned topic Batch Processor Exception

‏2011-10-27T12:18:34Z |
Hi Team,

I got the below exception while running the batch processor on unix server. I am using weblogic server v10.3 and MDM v9.0.2.

Please help me out in resolving this issue.

The system reads the input file: /home/mdm/BatchProcessor/xml/parse/AddPerson.txt
The system writes to the output file: /home/mdm/BatchProcessor/xml/parse/out
ERROR - Exception_CustomerReflectionDelegate_JNDINameLookup: CDKBC2030E:Unable to locate a reference using the following parameters. JNDI = com/dwl/base/requestHandler/beans/DWLServiceController; URL = null; additional error message = While trying to lookup 'com.dwl/base/requestHandler/beans/DWLServiceController' didn't find subcontext 'com'. Resolved ''
javax.naming.NameNotFoundException: While trying to lookup 'com.dwl/base/requestHandler/beans/DWLServiceController' didn't find subcontext 'com'. Resolved '' ; remaining name 'com/dwl/base/requestHandler/beans/DWLServiceController'
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at weblogic.jndi.internal.ServerNamingNode_1032_WLStub.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:405)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at com.dwl.tcrm.delegate.CustomerReflectionDelegate.init(CustomerReflectionDelegate.java:382)
at com.dwl.tcrm.delegate.CustomerReflectionDelegate.<init>(CustomerReflectionDelegate.java:190)
at com.dwl.tcrm.delegate.CustomerDelegate.<init>(CustomerDelegate.java:93)
at com.dwl.batchframework.delegate.Customer.init(Customer.java:122)
at com.dwl.batchframework.delegate.CustomerSingleton.init(CustomerSingleton.java:82)
at com.dwl.batchframework.BatchController.initServerConfiguration(BatchController.java:395)
at com.dwl.batchframework.BatchController.initialize(BatchController.java:360)
at com.dwl.batchframework.BatchController.runBatch(BatchController.java:273)
at com.dwl.batchframework.BatchController.main(BatchController.java:202)
Caused by: javax.naming.NameNotFoundException: While trying to lookup 'com.dwl/base/requestHandler/beans/DWLServiceController' didn't find subcontext 'com'. Resolved ''
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
An error occurred. See the log file for details. Additional error message = While trying to lookup 'com.dwl/base/requestHandler/beans/DWLServiceController' didn't find subcontext 'com'. Resolved ''
Exception in thread "main" java.lang.NullPointerException
at com.dwl.batchframework.BatchController.closeIOqueues(BatchController.java:335)
at com.dwl.batchframework.BatchController.runBatch(BatchController.java:295)

Thanks,
Rohit.
Updated on 2011-11-09T10:28:55Z at 2011-11-09T10:28:55Z by TVSKS
  • Jinka
    Jinka
    11 Posts
    ACCEPTED ANSWER

    Re: Batch Processor Exception

    ‏2011-10-28T07:23:24Z  in response to Jinka
    Hi,

    The earlier exception is resolved. Now I am getting the below exception. Please let me knoe If you have any idea on this.

    runbatch.sh /home/mdm/BatchProcessor/xml/parse/AddPerson.txt /home/mdm/BatchProcessor/xml/parse/out
    The system reads the input file: /home/mdm/BatchProcessor/xml/parse/AddPerson.txt
    The system writes to the output file: /home/mdm/BatchProcessor/xml/parse/out
    ERROR - Exception_BatchController_ExceptionCount: CDKBC2006E:Exception occurred: count = 1; processorID = ParseAndExecuteConsumer; messageID = 0; additional error message = EJB Exception: ; nested exception is:
    java.lang.NoClassDefFoundError: Could not initialize class com.dwl.tcrm.coreParty.xmlHandler.XMLRequestParser
    Faulty record: 1
    The system finished processing. Number of records processed = 1; Time spent (in milliseconds) = 823

    Thanks,
    Rohit.
    • TVSKS
      TVSKS
      7 Posts
      ACCEPTED ANSWER

      Re: Batch Processor Exception

      ‏2011-11-09T10:28:55Z  in response to Jinka
      Hi Rohit, we are also facing the same issue. Can you please let us know how ur earlier exception got resolved?

      Thanks
    • kr.mukesh
      kr.mukesh
      3 Posts
      ACCEPTED ANSWER

      Re: Batch Processor Exception

      ‏2013-05-18T21:26:59Z  in response to Jinka

      You could check if all the EJB's are being able to start when you are publishing on the server.

       

      Thanks,

      Mukesh

  • jacksonwilliam
    jacksonwilliam
    1 Post
    ACCEPTED ANSWER

    Re: Batch Processor Exception

    ‏2013-05-18T14:52:09Z  in response to Jinka

    I have this same error message as well.

     

    A actually have a working 8.5 install but version 10 install fails - not so much difference between the two versions so was trying to leverage that to get this working.  In other words i used the 8.5 config and examine everything for differences and modified accordingly.  There was nothing really that raised a question that would be responsible for this error message

     

    There was some deviation in what made MDM85 work  so the default use of

    ${JAVA_HOME}/bin/java" -Xms${minMemory} -Xmx${maxMemory} ${WAS_LOGGING} -Djava.security.auth.login.config="${USER_INSTALL_ROOT}/properties/wsjaas_client.conf" -Djava.ext.dirs="${JAVA_HOME}/jre/lib/ext:${WAS_EXT_DIRS}:${WAS_HOME}/plugins:${WAS_HOME}/lib/WMQ/java/lib" -Djava.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory -Dserver.root="${WAS_HOME}" "${USER_INSTALL_PROP}" "${CLIENTSAS}" "${CLIENTSSL}" -classpath "${WAS_CLASSPATH}:${CP}" com.dwl.batchframework.BatchControllerRestart $restartOption $batchData $outputFile $batch_extension $batchLoad $instanceName
     

    is modified for example wsjaas_client.conf not used.  In fact because the installer for batchprocssor has never been run, someone put known configs in - I have no idea what the installer populates as a reference point for some of these. Still hope/think my config is close to working if I just knew more about this error and how folks have addressed it.

     

    not using sas.client.props to enter the username/pw - using a file called ClientAuthenticationProperties in

    ../MDMServer/BatchProcessor/properties

    also

    SAS_CONFIG environment variable passed to the java command in runBatch.sh has all corba

    SAS_CONFIG="-Dcom.ibm.CORBA.securityEnabled=true -Dcom.ibm.CORBA.authenticationTarget=BasicAuth -Dcom.ibm.CORBA.authenticationRetryEnabled=true -Dcom.ibm.CORBA.authenticationRetryCount=3 -Dcom.ibm.CORBA.validateBasicAuth=true -Dcom.ibm.CORBA.securityServerHost= -Dcom.ibm.CORBA.securityServerPort= -Dcom.ibm.CORBA.loginTimeout=300 -Dcom.ibm.CORBA.loginSource=properties -Dcom.ibm.CORBA.loginUserid=XXXXXXXXX -Dcom.ibm.CORBA.loginPassword=XXXXXXXXX -Dcom.ibm.CSI.performStateful=true -Dcom.ibm.CSI.performClientAuthenticationRequired=false -Dcom.ibm.CSI.performClientAuthenticationSupported=true -Dcom.ibm.CSI.performTLClientAuthenticationRequired=false -Dcom.ibm.CSI.performTLClientAuthenticationSupported=false -Dcom.ibm.CSI.performTransportAssocSSLTLSRequired=false -Dcom.ibm.CSI.performTransportAssocSSLTLSSupported=true -Dcom.ibm.CSI.performMessageIntegrityRequired=true -Dcom.ibm.CSI.performMessageIntegritySupported=true -Dcom.ibm.CSI.performMessageConfidentialityRequired=false -Dcom.ibm.CSI.performMessageConfidentialitySupported=true -Dcom.ibm.ssl.alias=DefaultSSLSettings -Dcom.ibm.CORBA.requestTimeout=180"

     

     

    and also

    SSL_CONFIG=-Dcom.ibm.SSL.ConfigURL=file:/usr/WebSphere610/AppServer/profiles/Dmgr01/properties/ssl.client.props