Underflow Exception when trying to bind small double to BINARY_DOUBLE

I get exception when trying to insert small double value (1.0E-131) into BINARY_DOUBLE column via jdbc.
The exception I get:
Exception in thread "main" java.sql.SQLException: Underflow Exception trying to bind 1.0000000000000001E-131
at oracle.jdbc.driver.DoubleBinder.bind(OraclePreparedStatement.java:13856)
at oracle.jdbc.driver.OraclePreparedStatement.setupBindBuffers(OraclePreparedStatement.java:2866)
at oracle.jdbc.driver.OraclePreparedStatement.processCompletedBindRow(OraclePreparedStatement.java:2151)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3280)
at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3390)
at dbAccess.main(dbAccess.java:18)
According to oracle documentation the smallest positive number the BINARY_DOUBLE column can store is 2.22507485850720E-308.
I'm using oracle 10g r2 and thin jdbc driver.
Any ideas?

That is expected since a double is converted to a Oracle NUMBER before passing it to the database and Oracle NUMBER does not support 1.0e-131, the range is 1E-130 .. 10E125.
Look at the SQL output below,
SQL> select to_char(to_number(1.0e-131)) from dual;
T
0
SQL> select to_char(to_number(1.0e-130)) from dual;
TO_CHAR(TO_NUMBER(1.0E-130))
1.000000000000000000000000000000000E-130
==
Use oracle.sql.BINARY_DOUBLE for numbers like this.
eg:
preparedStatement.setBINARY_DOUBLE(1, new oracle.sql.BINARY_DOUBLE(1.0e-131));
==
hope this helps.
Ashok

Similar Messages

  • What are solutions to the "Unexpected error while attempting to bind.  Operation cancelled." message when trying to bind

    What are solutions to the "Unexpected error while attempting to bind.  Operation cancelled." message when trying to bind and i alreeady cheack my DNS settings and everything

    Has this worked before, or is this a new configuration?
    On the server, launch Terminal.app from Applications > Utilities and post the output of the following harmless diagnostic command — and you'll need to enter an administrative password when requested:
    sudo changeip -checkhostname
    On the OS X (presumably) Mavericks client, please post the IP address(es) of the DNS server(s) you're referencing.  These are available via the System Preferences > Network > Advanced > DNS settings.
    To check the console logs, launch Console.app from Applications > Utilities on both the client and the server, and then attempt the binding, and then post a (short! no more than ~25 to 50 lines!) of any errors related to the binding error.
    If you're not in a position to post configuration details here — which is perfectly reasonable, and entirely your prerogative — or if I'm getting too confusing or too technical with some of the questions here, which would be my error of course — then (assuming these systems are under warranty) I'd suggest contacting the folks at the local Apple Store and having a chat with the local Geniuses about this, or checking directly with the Apple Support folks via telephone.

  • "Protocol family unavailable" when trying to bind to an IPv6 address

    Hi,
    When trying to bind to an IPv6 address using the Socket class, I get "Protocol family unavailable". Is there a fix to that?
    Thanks,
    Ronen

    read:
    http://search.msdn.microsoft.com/search/Default.aspx?
    query=IPv6&brand=msdn&locale=en-us&refinement=00&lang=en-us

  • Exception when trying to run an Web Application that uses a Web service

    Hello All,
    I get an exception when trying to run an Web Application that uses a Web service. The web application is a WebDynpro Application.(an application similar to the one "Using an Email Web Service in Web Dynpro" in the tutorial section of Web Dynpro but using a different web service)
    The exception is
    <b>Service call exception; nested exception is: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (404) Not Found.</b>
    Could anyone give me an idea on what might be the problem ?
    Regards,
    Loveline.

    Hello,
    Like you said it was the problem with url.
    The webservice I used is actually running on the local machine (where the NetWeaver developer studio is installed); so in the url I had specified localhost. But I deployed the application on another server(SAP J2EE Engine). That is why it didn't work. On changing the url as required, the application is working fine.
    Thanks !
    Regards,
    Loveline.

  • Getting an interrupted exception when trying to bring down the service

    Hi,
    From the client side , I started an invocation service which is giving an interrupted exception when trying to shut it down.
    2013-08-01 12:21:15.576 PDT ERROR -  -  -  - Oracle Coherence 3.7.1.6 (thread=Invocation:customerLoaderWM:EventDispatcher, member=5): This thread was interrupted while waiting for the results of a request:
    Poll
      PollId=20, active
      InitTimeMillis=1375384875574
      Service=Cluster (0)
      RespondedMemberSet=[]
      LeftMemberSet=[]
      RemainingMemberSet=[1]
    2013-08-01 12:21:15.576 PDT ERROR -  -  -  - Oracle Coherence 3.7.1.6 (thread=Invocation:customerLoaderWM:EventDispatcher, member=5): Error while starting service "customerLoaderWM": (Wrapped: Interrupted while waiting for response from:[Member(Id=1, Timestamp=2013-08-01 12:20:11.375, Address=10.241.100.189:18088, MachineId=42483, Location=site:,machine:slc05esi,process:4777,member:ecs1, Role=OracleChargingLauncher)]) java.lang.InterruptedException
        at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.processPollInterrupt(Grid.CDB:40)
        at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.poll(Grid.CDB:54)
        at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.poll(Grid.CDB:11)
        at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.ClusterService.ensureService(ClusterService.CDB:15)
        at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.register(Grid.CDB:5)
        at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:3)
        at com.tangosol.coherence.component.util.SafeService.startService(SafeService.CDB:39)
        at com.tangosol.coherence.component.util.SafeService.restartService(SafeService.CDB:28)
        at com.tangosol.coherence.component.util.SafeService.ensureRunningService(SafeService.CDB:23)
        at com.tangosol.coherence.component.util.SafeService.start(SafeService.CDB:14)
        at com.tangosol.coherence.commonj.WorkManager.getServers(WorkManager.java:599)
        at com.tangosol.coherence.commonj.WorkManager.disableServer(WorkManager.java:656)
        at com.tangosol.coherence.commonj.WorkManager$ServiceListener.memberLeft(WorkManager.java:1213)
        at com.tangosol.net.MemberEvent.dispatch(MemberEvent.java:116)
        at com.tangosol.net.MemberEvent.dispatch(MemberEvent.java:87)
        at com.tangosol.coherence.component.util.SafeService.translateEvent(SafeService.CDB:28)
        at com.tangosol.coherence.component.util.SafeService.memberLeft(SafeService.CDB:1)
        at com.tangosol.net.MemberEvent.dispatch(MemberEvent.java:116)
        at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid$DispatchEvent.run(Grid.CDB:7)
        at com.tangosol.coherence.component.util.daemon.queueProcessor.Service$EventDispatcher.onNotify(Service.CDB:26)
        at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
        at java.lang.Thread.run(Thread.java:662)
    Caused by: java.lang.InterruptedException
        at java.lang.Object.wait(Native Method)
        at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.poll(Grid.CDB:39)
    It says one thread is interrupted by another. Has anyone faced this issue?.
    Any info on this is appreciated.
    Thanks.

    Error in the TDS datastream: unknown block: 68Sounds like Microsoft have updated the TDS protocol for MSSQL2000. If you're using the Free TDS (www.freetds.org) driver I know you can configure the it for different versions of TDS (check out the FAQ or the doco on their web site) but whether it works with SQL 2000 or not I don't know.
    Col

  • DataSource CORP_LDAP: Naming exception when trying to create principal

    Using NetWeaver 6.40 SP 15.
    I have configured the UME to use writable LDAP and database. Specifically, for LDAP I'm using the Sun One Directory Server. I'm able to authenticate using one of the LDAP users using a Web Dynpro app.
    When I try to create a user through the NWA web app, I simply get a "Could not create user" error in the application. In the server instance "security.log" I found the following:
    Date : 03/08/2006
    Time : 16:22:59:248
    Message : DataSource CORP_LDAP: Naming exception when trying to create principal ***************************************************************************
    com.sap.security.core.persistence.imp.PrincipalDatabagMaint Wed Mar 08 16:22:59 CST 2006
    UniqueID: USER.CORP_LDAP.testuser
    Type: USER
    Home data source: CORP_LDAP
    Private id part: testuser
    "com.sap.security.core.usermanagement"|->"uniquename" (no time limit)="testuser"
    "com.sap.security.core.usermanagement"|->"department" (no time limit)="CI&T"
    "com.sap.security.core.usermanagement"|->"PRINCIPAL_CREATION_DATE" (no time limit)="0001141856579248"
    "com.sap.security.core.usermanagement"|->"firstname" (no time limit)="user"
    "com.sap.security.core.usermanagement"|->"lastname" (no time limit)="test"
    "com.sap.security.core.usermanagement"|->"PRINCIPAL_TYPE_ATTRIBUTE" (no time limit)="USER"
    "com.sap.security.core.usermanagement"|->"email" (no time limit)="[email protected]"
    "com.sap.security.core.usermanagement"|->"company" (no time limit)=""
    "com.sap.security.core.usermanagement"|->"accessibilitylevel" (no time limit)="0"
    Severity : Error
    Category : /System/Security/Usermanagement
    Location : com.sap.security.core.persistence
    Application : sap.com/com.sap.security.core.admin
    Thread : SAPEngine_Application_Thread[impl:3]_22
    Datasource : 1141856104605:C:\usr\sap\J2E\JC00\j2ee\cluster\server0\log\system\security.log
    Message ID : 000D60DD8A4D00540000001C0000136000040E8333C9FD7C
    Source Name : /System/Security/Usermanagement
    Argument Objs : CORP_LDAP,***************************************************************************
    com.sap.security.core.persistence.imp.PrincipalDatabagMaint Wed Mar 08 16:22:59 CST 2006
    UniqueID: USER.CORP_LDAP.testuser
    Type: USER
    Home data source: CORP_LDAP
    Private id part: testuser
    "com.sap.security.core.usermanagement"|->"uniquename" (no time limit)="testuser"
    "com.sap.security.core.usermanagement"|->"department" (no time limit)="CI&T"
    "com.sap.security.core.usermanagement"|->"PRINCIPAL_CREATION_DATE" (no time limit)="0001141856579248"
    "com.sap.security.core.usermanagement"|->"firstname" (no time limit)="user"
    "com.sap.security.core.usermanagement"|->"lastname" (no time limit)="test"
    "com.sap.security.core.usermanagement"|->"PRINCIPAL_TYPE_ATTRIBUTE" (no time limit)="USER"
    "com.sap.security.core.usermanagement"|->"email" (no time limit)="[email protected]"
    "com.sap.security.core.usermanagement"|->"company" (no time limit)=""
    "com.sap.security.core.usermanagement"|->"accessibilitylevel" (no time limit)="0"
    Arguments : CORP_LDAP,***************************************************************************
    com.sap.security.core.persistence.imp.PrincipalDatabagMaint Wed Mar 08 16:22:59 CST 2006
    UniqueID: USER.CORP_LDAP.testuser
    Type: USER
    Home data source: CORP_LDAP
    Private id part: testuser
    "com.sap.security.core.usermanagement"|->"uniquename" (no time limit)="testuser"
    "com.sap.security.core.usermanagement"|->"department" (no time limit)="CI&T"
    "com.sap.security.core.usermanagement"|->"PRINCIPAL_CREATION_DATE" (no time limit)="0001141856579248"
    "com.sap.security.core.usermanagement"|->"firstname" (no time limit)="user"
    "com.sap.security.core.usermanagement"|->"lastname" (no time limit)="test"
    "com.sap.security.core.usermanagement"|->"PRINCIPAL_TYPE_ATTRIBUTE" (no time limit)="USER"
    "com.sap.security.core.usermanagement"|->"email" (no time limit)="[email protected]"
    "com.sap.security.core.usermanagement"|->"company" (no time limit)=""
    "com.sap.security.core.usermanagement"|->"accessibilitylevel" (no time limit)="0"
    Dsr Component : <masked id>_J2E_7234450
    Dsr Transaction : 79521ee0aef011da9168000d60dd8a4d
    Dsr User : Administrator
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 1
    Relatives : com.sap.security.core.persistence
    Resource Bundlename :
    Session : 200
    Source : /System/Security/Usermanagement
    ThreadObject : SAPEngine_Application_Thread[impl:3]_22
    Transaction :
    User : Administrator
    Where can I find the initial NamingException?

    Hi All,
    Thanks for your replies and SORRY for my late response.
    Now, what I actually want is that though my UME is connected to LDAP i want to the portal admin to be able to create users in the portal DB. I checked my UME configuration and it says
    Microsoft ADS (Deep Hheirarchy) + Database
    and the name of the configuration file is
    dataSourceConfiguration_ads_deep_writeable_db.xml
    Now I could not understand why I am not able to create users in the DB?
    Does the portal has any restriction like at any given point of time only one of the user stores can be active? Doesnt the portal allow both the user stores to be active at a time?
    regards,
    PK

  • Caught Exception when trying to create pool Object

    Hi All,
    When a stateless session bean is looking up the entity bean following 'could not create pool object' exception is throwing.
    [14/Jan/2003:09:12:50] SEVERE ( 1048): EJB5070: Exception creating stateless session bean : [java.lang.reflect.InvocationTargetException]
    [14/Jan/2003:09:12:50] SEVERE ( 1048): EJB5017: Exception while running preinvoke : ejbName = [ConfigSessionBean]
    [14/Jan/2003:09:12:50] SEVERE ( 1048):
    javax.ejb.EJBException: nested exception is: java.lang.RuntimeException: c
    java.lang.RuntimeException: Caught Exception when trying to create pool Object
    at com.sun.ejb.containers.util.pool.NonBlockingPool.getObject(Unknown Source)
    at com.sun.ejb.containers.StatelessSessionContainer.getContext(Unknown Source)
    at com.sun.ejb.containers.BaseContainer.preInvoke(Unknown Source)
    at com.siptech.pdf.ejb.config.session.ConfigSessionBean_EJBObjectImpl.getAllModules(ConfigSessionBean_EJBObjectImpl.java:255)
    at com.siptech.pdf.ejb.config.session._ConfigSessionBean_EJBObjectImpl_Tie._invoke(Unknown Source)
    at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatchToServant(Unknown Source)
    at com.sun.corba.ee.internal.POA.GenericPOAServerSC.internalDispatch(Unknown Source)
    at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatch(Unknown Source)
    at com.sun.corba.ee.internal.iiop.ORB.process(Unknown Source)
    at com.sun.corba.ee.internal.iiop.RequestProcessor.process(Unknown Source)
    at com.iplanet.ias.corba.ee.internal.iiop.ServicableWrapper.service(Unknown Source)
    at com.iplanet.ias.util.threadpool.FastThreadPool$ThreadPoolThread.run(Unknown Source)
    at java.lang.Thread.run(Thread.java:536)
    Caused by: javax.ejb.EJBException: nested exception is: javax.ejb.CreateException: Could not create stateless EJB:
    java.lang.reflect.InvocationTargetException
    at com.sun.ejb.containers.StatelessSessionContainer$SessionContextFactory.create(Unknown Source)
    ... 13 more
    javax.ejb.EJBException: nested exception is: java.lang.RuntimeException: Caught Exception when trying to create pool Object
    at com.sun.ejb.containers.StatelessSessionContainer.getContext(Unknown Source)
    at com.sun.ejb.containers.BaseContainer.preInvoke(Unknown Source)
    at com.siptech.pdf.ejb.config.session.ConfigSessionBean_EJBObjectImpl.getAllModules(ConfigSessionBean_EJBObjectImpl.java:255)
    at com.siptech.pdf.ejb.config.session._ConfigSessionBean_EJBObjectImpl_Tie._invoke(Unknown Source)
    at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatchToServant(Unknown Source)
    at com.sun.corba.ee.internal.POA.GenericPOAServerSC.internalDispatch(Unknown Source)
    at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatch(Unknown Source)
    at com.sun.corba.ee.internal.iiop.ORB.process(Unknown Source)
    at com.sun.corba.ee.internal.iiop.RequestProcessor.process(Unknown Source)
    at com.iplanet.ias.corba.ee.internal.iiop.ServicableWrapper.service(Unknown Source)
    at com.iplanet.ias.util.threadpool.FastThreadPool$ThreadPoolThread.run(Unknown Source)
    at java.lang.Thread.run(Thread.java:536)
    I have also specified the following properties in the sunejbjar.xml for the session bean.
    <ejb>
    <bean-pool>
    <steady-pool-size>2</steady-pool-size>
    <resize-quantity>5</resize-quantity>
    <max-pool-size>200</max-pool-size>
    <pool-idle-timeout-in-seconds>3600</pool-idle-timeout-in-seconds>
    </bean-pool>
    </ejb>
    --Muthu.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    

    Muthu,
    To find out whether the problem is with container setting or with your application, can you create a simple stateless session bean and check if it works fine. If it works fine send me ejb-jar.xml and sun-ejb-jar.xml for your application.
    Deepak

  • Exception when trying to create pool Object

    I've been trying to get the forte 4.0ee ProductRichClient example for container managed beans to work.
    After the deployment to Sun One I got following exception when I'm using the client:
    18.10.2002 10:56:20 com.iplanet.ias.appclient.Main <init>
    INFO:
    ---------AppClient Container--------
    18.10.2002 10:56:20 com.iplanet.ias.appclient.Main setTagetServerProperties
    INFO: ACC001:Using ClientContainer file: [C:\Sun\AppServer7\appserv\domains\domain1\server1\config\sun-acc.xml].
    18.10.2002 10:56:20 com.iplanet.ias.appclient.Main <init>
    INFO: ACC014: ORB host name: [NOD]
    18.10.2002 10:56:20 com.iplanet.ias.appclient.Main <init>
    INFO: ACC013: ORB port number: [3700]
    18.10.2002 10:56:21 com.sun.enterprise.appclient.AppContainer preInvoke
    INFO: ACC007: Initiating Login ...
    18.10.2002 10:56:21 com.iplanet.ias.appclient.Main <init>
    INFO: ACC009: Load Application Class: [CMPClient.SwingClient]
    18.10.2002 10:56:23 com.iplanet.ias.appclient.Main <init>
    INFO: Application main() finished normally
    java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
    java.rmi.RemoteException: nested exception is: java.lang.RuntimeException: Caught Exception when trying to create pool Object ; nested exception is:
    java.lang.RuntimeException: Caught Exception when trying to create pool Object
    at com.sun.corba.ee.internal.iiop.ShutdownUtilDelegate.mapSystemException(Unknown Source)
    at javax.rmi.CORBA.Util.mapSystemException(Util.java:65)
    at CMPServer._ProductHome_Stub.create(Unknown Source)
    at CMPClient.SwingClient.AddRow_ButtonActionPerformed(SwingClient.java:127)
    at CMPClient.SwingClient.access$100(SwingClient.java:24)
    at CMPClient.SwingClient$2.actionPerformed(SwingClient.java:89)
    at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1767)
    at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1820)
    at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:419)
    at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:257)
    at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:258)
    at java.awt.Component.processMouseEvent(Component.java:5021)
    at java.awt.Component.processEvent(Component.java:4818)
    at java.awt.Container.processEvent(Container.java:1525)
    at java.awt.Component.dispatchEventImpl(Component.java:3526)
    at java.awt.Container.dispatchEventImpl(Container.java:1582)
    at java.awt.Component.dispatchEvent(Component.java:3367)
    at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3359)
    at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3074)
    at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3004)
    at java.awt.Container.dispatchEventImpl(Container.java:1568)
    at java.awt.Window.dispatchEventImpl(Window.java:1581)
    at java.awt.Component.dispatchEvent(Component.java:3367)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:445)
    at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:191)
    at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:144)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:130)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:98)
    Caused by: java.rmi.RemoteException: nested exception is: java.lang.RuntimeException: Caught Exception when trying to create pool Object ; nested exception is:
    java.lang.RuntimeException: Caught Exception when trying to create pool Object
    at com.sun.enterprise.iiop.POAProtocolMgr.mapException(Unknown Source)
    at com.sun.ejb.containers.BaseContainer.postInvoke(Unknown Source)
    at CMPServer.ProductEJB2024414397_ConcreteImpl_RemoteHomeImpl.create(ProductEJB2024414397_ConcreteImpl_RemoteHomeImpl.java:33)
    at CMPServer._ProductEJB2024414397_ConcreteImpl_RemoteHomeImpl_Tie._invoke(Unknown Source)
    at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatchToServant(Unknown Source)
    at com.sun.corba.ee.internal.POA.GenericPOAServerSC.internalDispatch(Unknown Source)
    at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatch(Unknown Source)
    at com.sun.corba.ee.internal.iiop.ORB.process(Unknown Source)
    at com.sun.corba.ee.internal.iiop.RequestProcessor.process(Unknown Source)
    at com.iplanet.ias.corba.ee.internal.iiop.ServicableWrapper.service(Unknown Source)
    at com.iplanet.ias.util.threadpool.FastThreadPool$ThreadPoolThread.run(Unknown Source)
    at java.lang.Thread.run(Thread.java:536)
    Caused by: java.lang.RuntimeException: Caught Exception when trying to create pool Object
    at com.sun.ejb.containers.util.pool.NonBlockingPool.getObject(Unknown Source)
    at com.sun.ejb.containers.util.pool.NonBlockingPool.getObject(Unknown Source)
    at com.sun.ejb.containers.EntityContainer.getPooledEJB(Unknown Source)
    at com.sun.ejb.containers.EntityContainer.getContext(Unknown Source)
    at com.sun.ejb.containers.BaseContainer.preInvoke(Unknown Source)
    at CMPServer.ProductEJB2024414397_ConcreteImpl_RemoteHomeImpl.create(ProductEJB2024414397_ConcreteImpl_RemoteHomeImpl.java:25)
    ... 9 more
    Caused by: javax.ejb.EJBException: nested exception is: java.lang.NullPointerException
    at com.sun.ejb.containers.EntityContainer$EntityContextFactory.create(Unknown Source)
    ... 15 more
    Any thoughts on why this exception is being thrown?
    Thanks for any help!
    Richard

    this sample has been tested by the SunONE TOOLs QA
    and is working. Please check your deployment descriptors
    and use the cmp samples which come with S1AS to see if your
    descriptors are correct.

  • Page/JNI: Exception when trying to connect in 1,page/ContentFetcher InterruptedIOExce

    We have upgraded to fro m 3.0.8 portal 3.0.9.8.2 9iAS 1.0.2.2 on database 8.1.7
    the system is very fast and run for sometime but after a while we see the following errors in Jserv.log file.
    this error causes the whole system to hang and we have to restart apache/jserv.
    Any light on this issue will be helpful and very much appreciated.
    thanks,
    Sunil Bontha
    25/07/2001 14:07:51:388 CEST] Viewer/oracle.discoiv.Disco4iv: init
    [25/07/2001 14:07:51:388 CEST] Viewer/oracle.discoiv.Disco4iv: Initializing Discoverer 4i Viewer (4.1.37.82)
    [25/07/2001 14:09:15:219 CEST] page/oracle.webdb.page.ParallelServlet: init
    [25/07/2001 14:09:15:249 CEST] page/JNI: Cache is enabled.
    [25/07/2001 14:09:15:299 CEST] page/Starting a pool of 25 handlers.
    [25/07/2001 14:09:43:820 CEST] page/JNI: Exception when trying to connect in 1.
    [25/07/2001 14:09:43:830 CEST] page/Timeout occurred, label=145 url=http://www.myserver.com/pls/pmsportal30/!PMSPORTAL30.wwpro_app_provider.execute_portlet [25/07/2001 14:09:43:830 CEST] page/ContentFetcher InterruptedIOException Caught, Fetcher Timedout name=content-fetcher23
    [25/07/2001 14:09:43:840 CEST] page/JNI: Exception when trying to connect in 1.
    [25/07/2001 14:09:43:840 CEST] page/Timeout occurred, label=293 url=http://www.myserver.com/pls/pmsportal30/!PMSPORTAL30.wwpro_app_provider.execute_portlet [25/07/2001 14:09:43:840 CEST] page/ContentFetcher InterruptedIOException Caught, Fetcher Timedout name=content-fetcher22
    [25/07/2001 14:09:53:864 CEST] page/JNI: Exception when trying to connect in 1.

    Hi Avi,
    My application is a standalone application trying to access MBeans present in oc4j.
    I tried
    using the code
    props.put(Context.INITIAL_CONTEXT_FACTORY ,"oracle.j2ee.rmi.RMIInitialContextFactory");
    obj = (ManagementHome) ctx.lookup("ejb/mgmt/MEJB");
    but i am getting the following error.
    javax.naming.NameNotFoundException: ejb/mgmt/MEJB not found
    at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java
    :45)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    at TestMBean.doSomething(TestMBean.java:90)
    at TestMBean.main(TestMBean.java:237)
    java.lang.NullPointerException
    at TestMBean.doSomething(TestMBean.java:107)
    at TestMBean.main(TestMBean.java:237)
    Regards
    Siva

  • Getting exception when trying to get taskdetails url using BPM worklist api

    Getting exception when trying to get taskdetails url using BPM worklist api method :
    String url = WorklistUtil.getTaskDisplayURL(
    wfSvcClient,
    ctx,
    task,
    null,
    "worklist",
    parameters);
    Jul 21, 2011 11:24:40 AM oracle.bpel.services.common.ServicesLogger __log
    WARNING: <oracle.bpel.services.workflow.client.worklist.util.TaskFlowPropsUtil.getServerPropertiesFromMbean()> Exception while loading install config file in standalone Error : javax.management.InstanceNotFoundException: com.bea:Name=RuntimeService,Type=weblogic.management.mbeanservers.runtime.RuntimeServiceMBean: com.bea:Name=RuntimeService,Type=weblogic.management.mbeanservers.runtime.RuntimeServiceMBean
    oracle.fabric.common.FabricException: javax.management.InstanceNotFoundException: com.bea:Name=RuntimeService,Type=weblogic.management.mbeanservers.runtime.RuntimeServiceMBean: com.bea:Name=RuntimeService,Type=weblogic.management.mbeanservers.runtime.RuntimeServiceMBean
    at oracle.soa.common.util.PlatformUtils.getServerInfo(PlatformUtils.java:184)
    at oracle.bpel.services.workflow.client.worklist.util.TaskFlowPropsUtil.getServerPropertiesFromMbean(TaskFlowPropsUtil.java:319)
    at oracle.bpel.services.workflow.client.worklist.util.TaskFlowPropsUtil.getServerInfoForWeblogicServer(TaskFlowPropsUtil.java:491)
    at oracle.bpel.services.workflow.client.worklist.util.TaskFlowPropsUtil.getServerInfo(TaskFlowPropsUtil.java:363)
    at oracle.bpel.services.workflow.worklist.api.util.WorklistUtil.getDefaultURLPrefix(WorklistUtil.java:264)
    at oracle.bpel.services.workflow.worklist.api.util.WorklistUtil.getTaskDisplayURL(WorklistUtil.java:353)
    at oracle.bpel.services.workflow.worklist.api.util.WorklistUtil.getTaskDisplayURL(WorklistUtil.java:293)
    at com.test.WorflowServiceClient.main(WorflowServiceClient.java:198)
    Caused by: javax.management.InstanceNotFoundException: com.bea:Name=RuntimeService,Type=weblogic.management.mbeanservers.runtime.RuntimeServiceMBean
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1094)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:662)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:638)
    at oracle.as.jmx.framework.config.session.ConfigurationMBeanServerImpl.getAttribute(ConfigurationMBeanServerImpl.java:210)
    at oracle.soa.common.util.PlatformUtils.getServerInfo(PlatformUtils.java:78)
    ... 7 more
    Caught workflow exception: null
    Process exited with exit code 0.
    Can anyone please help me

    Actually i'm using Jdeveloper 11.1.1.4 and our requirement is to show list of BPM worklist tasks for the logged in user on the first page and onclick of each task task details page should be opened. I can use Webcenter PS3 worklist taskflow. But i'm not able to customize that taskflow. So, i'm going for Worklist client api.
    I'm able to retrive the taskId,task title and few other details like task payload. But i don't know why the below method is giving exception.
    String url =
    WorklistUtil.getTaskDisplayURL(wfSvcClient,
    ctx, task, null,
    "worklist", parameters);
    And i observed that you have also used the same code for getting Taskdetails url. And one more thing is i'm trying to access BPM worklist which is installed on remote machine.
    Can you tell me what could be the reason for the exception?

  • Exception when trying to post to a page

    In NetD we created and submitted a form with JavaScript.
    The form looked something like this
    <FORM ACTION=pgXYZ METHOD=POST>
    <INPUT TYPE=hidden NAME=SPIDERSESSION VALUE=12345>
    </FORM>
    So now in Jato, we're trying to do the exact same thing,
    except that instead of SPIDERSESSION, we use the three Jato
    variables. Now the form is like this:
    <FORM ACTION=pgXYZ METHOD=POST>
    <INPUT TYPE=hidden NAME=GXHC_GX_jst VALUE=12345>
    <INPUT TYPE=hidden NAME=GXHC_gx_session_id_ VALUE=12345>
    <INPUT TYPE=hidden NAME=pageAttributes VALUE=12345>
    </FORM>
    Notice we're not submitting to a handler, but just to the page itself.
    When we do this, we get an exception:
    [02/Oct/2001 16:29:59:4] error: Exception: SERVLET-execution_failed:
    Error in executing servlet portalServlet:
    javax.servlet.ServletException: The request was not be handled by the
    specified handler
    Exception Stack Trace:
    javax.servlet.ServletException: The request was not be handled by the
    specified handler^M
    at
    com.putnaminvestments.common.jato.ApplicationServletBase.dispatchReque
    st(ApplicationServletBase.java:668)^M
    at
    com.putnaminvestments.common.jato.ApplicationServletBase.processReques
    t(ApplicationServletBase.java:428)^M
    at
    com.putnaminvestments.common.jato.ApplicationServletBase.doPost(Applic
    ationServletBase.java:296)^M
    at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:772)^M
    at
    com.putnaminvestments.bp.bpServletBase.service(bpServletBase.java:139)
    ^M
    at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:865)^M
    at
    com.netscape.server.servlet.servletrunner.ServletInfo.service(Unknown
    Source)^M
    at
    com.netscape.server.servlet.servletrunner.ServletRunner.execute(Unknow
    n Source)^M
    at com.kivasoft.applogic.AppLogic.execute(Unknown Source)^M
    at com.kivasoft.applogic.AppLogic.execute(Unknown Source)^M
    at com.kivasoft.thread.ThreadBasic.run(Native Method)^M
    at java.lang.Thread.run(Thread.java:479)^M
    So what are we missing??

    Thanks Kostas, good answer.
    Todd
    ----- Original Message -----
    From: "Kostas Morfis" <kmorfis@i...>
    Sent: Tuesday, October 02, 2001 4:31 PM
    Subject: RE: [iPlanet-JATO] Exception when trying to post to a page
    Hi Mark
    You are trying to submit to a view bean using java script right ?
    Notice we're not submitting to a handler, but just to the page itself.You are actually submitting the request to your JATO selvlet base, is that
    you intention ?
    The exception is being thrown because there is no request handler found.
    If you are trying invoke a handleBtnXXXmethod then your form action would
    look something like,
    <form method="post" action="../myServlet/pgMyPage?pgMypage.btnMyButton=">
    This adds to the request an appropriate handler as a parameter. Another
    option could be to add a hidden field
    with the same name as your button.
    Attempting to post the form without specifying a request handler will not
    work eg:
    <form method="post" action="../myServlet/pgMyPage">
    This throws a ServletException("The request was not be handled by the
    specified handler")
    because you are doing a post to ViewBean from a form which implies youwant
    to handle some kind web action.
    The way JATO enforces this is to check for the prescence of pageAttributes
    in the request (implemented using hidden fields)
    which you have in your form.
    Kostas
    -----Original Message-----
    From: Mark_Dubinsky@p... [mailto:<a href="/group/SunONE-JATO/post?protectID=174166091163159191130171186101229144026098131198043123114199021239115076086020224">Mark_Dubinsky@p...</a>]
    Sent: Tuesday, October 02, 2001 10:04 PM
    Subject: [iPlanet-JATO] Exception when trying to post to a page
    In NetD we created and submitted a form with JavaScript.
    The form looked something like this
    <FORM ACTION=pgXYZ METHOD=POST>
    <INPUT TYPE=hidden NAME=SPIDERSESSION VALUE=12345>
    </FORM>
    So now in Jato, we're trying to do the exact same thing,
    except that instead of SPIDERSESSION, we use the three Jato
    variables. Now the form is like this:
    <FORM ACTION=pgXYZ METHOD=POST>
    <INPUT TYPE=hidden NAME=GXHC_GX_jst VALUE=12345>
    <INPUT TYPE=hidden NAME=GXHC_gx_session_id_ VALUE=12345>
    <INPUT TYPE=hidden NAME=pageAttributes VALUE=12345>
    </FORM>
    Notice we're not submitting to a handler, but just to the page itself.
    When we do this, we get an exception:
    [02/Oct/2001 16:29:59:4] error: Exception: SERVLET-execution_failed:
    Error in executing servlet portalServlet:
    javax.servlet.ServletException: The request was not be handled by the
    specified handler
    Exception Stack Trace:
    javax.servlet.ServletException: The request was not be handled by the
    specified handler^M
    at
    com.putnaminvestments.common.jato.ApplicationServletBase.dispatchReque
    st(ApplicationServletBase.java:668)^M
    at
    com.putnaminvestments.common.jato.ApplicationServletBase.processReques
    t(ApplicationServletBase.java:428)^M
    at
    com.putnaminvestments.common.jato.ApplicationServletBase.doPost(Applic
    ationServletBase.java:296)^M
    at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:772)^M
    at
    com.putnaminvestments.bp.bpServletBase.service(bpServletBase.java:139)
    ^M
    at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:865)^M
    at
    com.netscape.server.servlet.servletrunner.ServletInfo.service(Unknown
    Source)^M
    at
    com.netscape.server.servlet.servletrunner.ServletRunner.execute(Unknow
    n Source)^M
    at com.kivasoft.applogic.AppLogic.execute(Unknown Source)^M
    at com.kivasoft.applogic.AppLogic.execute(Unknown Source)^M
    at com.kivasoft.thread.ThreadBasic.run(Native Method)^M
    at java.lang.Thread.run(Thread.java:479)^M
    So what are we missing??
    [email protected]
    [Non-text portions of this message have been removed]
    [email protected]

  • Exception when trying to run OneEJBHotelSample

    I get the following exception when trying to run the one ejb hotel sample,
    any clues as to what is wrong??
    java.lang.IncompatibleClassChangeError: Unimplemented interface method
    at javax.naming.spi.NamingManager.getURLObject(Compiled Code)
    at javax.naming.spi.NamingManager.getURLContext(Compiled Code)
    at javax.naming.InitialContext.getURLOrDefaultInitCtx(Compiled Code)
    at javax.naming.InitialContext.lookup(Compiled Code)
    at client.JavaGUIClient.EJBHotelSample.getHotelSystemBean(Compiled Code)
    at client.JavaGUIClient.EJBHotelSample.main(Compiled Code)
    null

    Hello,
    Like you said it was the problem with url.
    The webservice I used is actually running on the local machine (where the NetWeaver developer studio is installed); so in the url I had specified localhost. But I deployed the application on another server(SAP J2EE Engine). That is why it didn't work. On changing the url as required, the application is working fine.
    Thanks !
    Regards,
    Loveline.

  • My iPad works perfectly except when trying to update apps.  Then I get a message that says "Cannot connect to the iTunes store."

    My iPad works perfectly except when trying to update apps.  Then I get a message that says "Cannot connect to the iTunes store."

    Try logging out of your account on the iPad by tapping on your id in Settings > Store and then log back in and see if it then works.
    If that doesn't solve it then what has worked for some people is going into Settings > General > Date & Time and change the date to a few months in the future and then re-trying

  • Getting exception when trying to open Alert Configuration in RW

    Hello friends,
    I am getting the following exception when i am trying to open the Alert Configuration/Alert Inbox in RWB.
    Exception:
    com.sap.aii.rwb.exceptions.BuildLandscapeException: No central monitoring server in exchange profile
            at com.sap.aii.rwb.core.MonitoringServer.(MonitoringServer.java:77)
            at com.sap.aii.rwb.agent.server.SLDAgentBean.buildMonitoringServer(SLDAgentBean.java:799)
            at com.sap.aii.rwb.agent.server.SLDAgentBean.getMonitoringServer(SLDAgentBean.java:1462)
            at com.sap.aii.rwb.agent.api.SLDAgentObjectImpl0.getMonitoringServer(SLDAgentObjectImpl0.java:999)
            at com.sap.aii.rwb.agent.api.SLDAgent_Stub.getMonitoringServer(SLDAgent_Stub.java:1931)
            at com.sap.aii.rwb.agent.client.EJBAgent.getMonitoringServer(EJBAgent.java:493)
            at jsp_alert_inbox1204719699497._jspService(jsp_alert_inbox1204719699497.java:28)
            at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
            at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
            at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
            at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
            at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
            at jsp_FC_Secure1204104271605._jspService(jsp_FC_Secure1204104271605.java:24)
            at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
            at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
            at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
            at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
            at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
            at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
            at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
            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)
    Could you please help me out in solving this problem?
    Thanks & Regards,
    Senthil

    From your error, maybe your profile parameter for alert message server is not properly configured:
    I just came cross a post elaborating alerting configuration from Aashish Sinha, hope it helps,
    Liang
    =====Post from Aashish Sinha=======
    Prerequisites
    The following prerequisites have to be met in order to use the Alert Management (ALM):
    · For using the Alert Inbox (BSP based display program of ALM), the corresponding service has to be activated in the service maintenance transaction SICF. Choose Default_host ? sap ? bc ? bsp ? sap ? alert inbox, and Activate in the context menu.
    · For customizing or administration of the Alert Management the corresponding authorization role has to be assigned. The end users do not need any additional authorization.
    · The central alert server must be maintained as an RFC destination in transaction SM59 in the local system. If there is no suitable user, you have to create a user for the RFC connection in the central alert system in transaction SU01. To make this RFC destination known as the RFC destination of the Alert Management System in the local system, the central alert server must also be selected as the RFC destination in transaction SALRT1 of the local system or in Settings ? RFC-Destination of Alert Server.
    If the central alert server is running on the local system in the same client, you do not have to maintain an RFC destination. In this case, you can simply enter NONE in transaction SALRT1.
    · If external communication types, such as e-mail, SMS, and fax are used, these communication types must be correctly configured in SAPconnect, because the alerts are then sent from the central alert system via SAPconnect.
    Process Flow
    The following describes the process flow from alert configuration (transaction ALRTCATDEF) to alert display and confirmation (for example in the alert inbox transaction ALRTINBOX):
    1. Optional: You can define alert classifications. These are useful to group alert categories. For example, you can create an alert classification CRM that contains alert categories referring to CRM. Alert classifications can now have subclassifications. This enables you to build up your own classification hierarchy. Especially, if you use the Alert Mangement (ALM) extensively, classification and subclassification help you to organize your ALM alert landscape and to have a clear overview.
    2. For different types of alerts you have to define different categories. The category contains various properties and other specifications that define the alerts within that category, for example expiry date, or the escalation recipient. You can define an alert category to suit your business requirements and assign the category to the corresponding classification. For example, for the alert classification CRM you can create the alert categories Contract Cancelled and Decrease in Sales. When the critical situation defined in the alert category arises, the system recognizes this and sends an alert instance of this category to the recipients determined. The alerts can always be found in the display programs configured for the recipient (UWL, application-specific program, or alert inbox). Additionally, the alerts are sent via eventual external communication channels, such as e-mail, sms, or fax.
    3. You have to determine recipients so that the Alert Management knows who the recipients of alerts of a particular category are and that the correct parties are informed.
    4. You can configure the way how alerts are processed. For the general use of the Alert Management you do not have to change the default settings. However, if for example you want to send alerts to third-party systems, or to be able to confirm alerts by SMS/Internet mail, or to have logs written, then you have to configure alert processing.
    5. There is a number of Alert Management administration reports that you must schedule according to your requirements. For example, report RSALERTPROC must be executed in order to enable escalation.
    6. Alerts of a particular category must be triggered by an application at runtime. Triggering alerts can be done in various ways. You can call a function module directly or use middleware components that trigger alerts, such as the Business Object Repository (BOR), Post Processing Framework (PPF), SAP Workflow, or CCMS.
    7. Recipients can view the alerts assigned to them in the UWL of Enteprise Portal, in application-specific display programs, or in the alert inbox. In addition, alerts can be received as e-mail, SMS, or fax, if these external communication channels are configured in SAPconnect.
    8. If the problem causing the alert is solved by a recipient, the recipient can confirm the alert, this means its status is changed and it will not be delivered, escalated, or displayed anymore. Alerts are generally confirmed by the recipient in the display program, such as the UWL or Alert Inbox. However, if an alert is sent by Internet mail or SMS message, it is also possible to confirm it by sending an Internet mail or SMS message back to the SAP system. Alert Management uses inbound processing for this.
    Hope this will help you.
    Regards
    Aashish Sinha
    ============End of the Post=======================

  • Exception when trying to run baseline_update.bat

    Hi,
    I am just trying to configure my machine for Endeca Guided Search. I am the steps given in Oracle Endeca Guided Search Getting Started guide. The section i am referring to is :- "Configuring the sample application on a single development server".
    1. I have run the deployment template deploy script - No error
    2. Ran initialize_services script from the Endeca Deployment Template - No Error
    3. To run a baseline update script on the Data Processing (ITL) server:
    a. Ran load_baseline_test_data.bat - No Error
    b. Ran baseline_update.bat - Getting the below exception (logs):
    INFO: [ITLHost] Starting component 'Dgidx'.
    Oct 28, 2012 3:55:02 PM com.endeca.soleng.eac.toolkit.script.Script runBeanShellScript
    SEVERE: Error communicating with EAC agent while starting component.
    Occurred while executing line 32 of valid BeanShell script:
    29| Forge.archiveLogDir();
    30| Forge.run();
    31| Dgidx.archiveLogDir();
    32| Dgidx.run();
    33|
    34| // distributed index, update Dgraphs
    35| DistributeIndexAndApply.run();
    Oct 28, 2012 3:55:02 PM com.endeca.soleng.eac.toolkit.Controller execute
    SEVERE: Caught an exception while invoking method 'run' on object 'BaselineUpdate'. Releasing locks.
    java.lang.reflect.InvocationTargetException
         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:597)
         at com.endeca.soleng.eac.toolkit.Controller.invokeRequestedMethod(Controller.java:923)
         at com.endeca.soleng.eac.toolkit.Controller.execute(Controller.java:208)
         at com.endeca.soleng.eac.toolkit.Controller.main(Controller.java:87)
    Caused by: com.endeca.soleng.eac.toolkit.exception.AppControlException: Error executing valid BeanShell script.
         at com.endeca.soleng.eac.toolkit.script.Script.runBeanShellScript(Script.java:132)
         at com.endeca.soleng.eac.toolkit.script.Script.run(Script.java:80)
         ... 7 more
    Caused by: com.endeca.soleng.eac.toolkit.exception.EacCommunicationException: Error communicating with EAC agent while starting component.
         at com.endeca.soleng.eac.toolkit.component.Component.start(Component.java:153)
         at com.endeca.soleng.eac.toolkit.component.BatchComponent.run(BatchComponent.java:66)
         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:597)
         at bsh.Reflect.invokeMethod(Unknown Source)
         at bsh.Reflect.invokeObjectMethod(Unknown Source)
         at bsh.Name.invokeMethod(Unknown Source)
         at bsh.BSHMethodInvocation.eval(Unknown Source)
         at bsh.BSHPrimaryExpression.eval(Unknown Source)
         at bsh.BSHPrimaryExpression.eval(Unknown Source)
         at bsh.BSHBlock.evalBlock(Unknown Source)
         at bsh.BSHBlock.eval(Unknown Source)
         at bsh.BSHBlock.eval(Unknown Source)
         at bsh.BSHIfStatement.eval(Unknown Source)
         at bsh.BSHBlock.evalBlock(Unknown Source)
         at bsh.BSHBlock.eval(Unknown Source)
         at bsh.BSHBlock.eval(Unknown Source)
         at bsh.BSHIfStatement.eval(Unknown Source)
         at bsh.Interpreter.eval(Unknown Source)
         at bsh.Interpreter.eval(Unknown Source)
         at bsh.Interpreter.eval(Unknown Source)
         at com.endeca.soleng.eac.toolkit.script.Script.runBeanShellScript(Script.java:118)
         ... 8 more
    Caused by: An error occurred while trying to start the component: ENDECA_MDEX_ROOT is required for this component,but eac.properties does not contain a valid ENDECA_MDEX_ROOT definition.: ENDECA_MDEX_ROOT is required for this component,but eac.properties does not contain a valid ENDECA_MDEX_ROOT definition.
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
         at java.lang.Class.newInstance0(Class.java:355)
         at java.lang.Class.newInstance(Class.java:308)
         at org.apache.axis.encoding.ser.BeanDeserializer.<init>(BeanDeserializer.java:104)
         at org.apache.axis.encoding.ser.BeanDeserializer.<init>(BeanDeserializer.java:90)
         at com.endeca.eac.client.EACFault.getDeserializer(EACFault.java:75)
         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:597)
         at org.apache.axis.encoding.ser.BaseDeserializerFactory.getSpecialized(BaseDeserializerFactory.java:154)
         at org.apache.axis.encoding.ser.BaseDeserializerFactory.getDeserializerAs(BaseDeserializerFactory.java:84)
         at org.apache.axis.encoding.DeserializationContext.getDeserializer(DeserializationContext.java:464)
         at org.apache.axis.encoding.DeserializationContext.getDeserializerForType(DeserializationContext.java:547)
         at org.apache.axis.message.SOAPFaultDetailsBuilder.onStartChild(SOAPFaultDetailsBuilder.java:157)
         at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)
         at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501)
         at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:179)
         at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:377)
         at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2747)
         at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
         at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
         at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
         at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807)
         at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
         at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107)
         at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
         at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
         at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
         at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
         at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
         at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
         at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
         at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
         at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
         at org.apache.axis.client.Call.invoke(Call.java:2767)
         at org.apache.axis.client.Call.invoke(Call.java:2443)
         at org.apache.axis.client.Call.invoke(Call.java:2366)
         at org.apache.axis.client.Call.invoke(Call.java:1812)
         at com.endeca.eac.client.ComponentControlPortSOAPBindingStub.startComponent(ComponentControlPortSOAPBindingStub.java:263)
         at com.endeca.soleng.eac.toolkit.component.Component.start(Component.java:149)
         ... 31 more
    Oct 28, 2012 3:55:02 PM com.endeca.soleng.eac.toolkit.base.LockManager releaseLock
    INFO: Released lock 'update_lock'.
    Checked the value of com.endeca.mdexRoot in eac.properties. It's C:\\Users\\Aditya\\Endeca\\MDEX\\6.2.2 , which is correct.
    Not sure what else to check now. Because of the above exceptions, not able to verify the installation with the JSP reference application. Get the below exception when try to test using host: localhost and port:15000:
    status >> invalid ENE location
    ENEConnectionException
    com.endeca.navigation.ENEConnectionException: Error establishing connection to retrieve Navigation Engine request 'http://localhost:15000/graph?node=0&offset=0&nbins=10&irversion=620'. Connection refused: connect
    Regards,
    Sachin Kakkar

    Are you executing baseline update using Aditya as a user?
    Open command prompt and try executing below command,
    echo %ENDECA_MDEX_ROOT% It should give you output as C:\\Users\\Aditya\\Endeca\\MDEX\\6.2.2
    HTH
    -Pravin

Maybe you are looking for