Failed to lookup JNDI provider

Hi All,
I'm facing a problem sending Messages to a Queue within an OpenJMS server.
When I send the messages to a OpenJMS server runnin on my LocalHost, It is SUCCESSFUL.
then, I simply change the IP adress of the server (another machine on my local network) ... and here, I obtain the follwing exception :
Failed to lookup JNDI provider for URL: tcp://192.168.4.71:3035/
here is the code I'm using ( and where the exception is raised ):
Hashtable properties = new Hashtable();
properties.put(Context.INITIAL_CONTEXT_FACTORY, "org.exolab.jms.jndi.InitialContextFactory");
properties.put(Context.PROVIDER_URL, "tcp://192.168.4.71:3035/" );
context = new InitialContext(properties);Any help and suggestion please ?!
It's urgent

for more details :
this is the nested Exception I'm getting :
nested exception is:
java.io.InvalidClassException: org.exolab.jms.net.proxy.Proxy;
local class incompatible: stream classdesc serialVersionUID = -3335702252244367740, local class serialVersionUID = 1
?

Similar Messages

  • Fail to lookup jndi in EJB

    Hi,
    My application failed to lookup a JMS Object using JNDI lookup in EJB.
    The actual application flow is that a Servlet receive a request which
    then calls to an EJB
    where it loop up the JMS object to establish the message queue
    connection.
    It works with a simple Servlet which loop up the JMS Object without call
    to EJB.
    Does anyone known the possible reason causes the application failed to
    lookup the JMS Object?
    Thanks
    Avans
    the log is following
    The Status is :
    MQ java:comp/env/jms/theFactory
    MQjava:comp/env/jms/theFactoryjavax.naming.NameNotFoundException: Can't locate jms/theFactory
    at com.netscape.server.jndi.CompContext.resolveEnv(Unknown
    Source)
    at com.netscape.server.jndi.CompContext.lookup(Unknown Source)
    at com.netscape.server.jndi.java.javaURLContext.lookup(Unknown
    Source)
    at javax.naming.InitialContext.lookup(InitialContext.java:357)
    at
    com.hkex.common.mq.mqwrapper.MQReceiver.<init>(MQReceiver.java:109)
    at
    com.hkex.common.mq.mqwrapper.MQReceiverGroup.<init>(MQReceiverGroup.j
    ava:70)
    at
    com.hkex.common.mq.mqwrapper.MQContainer.createReceivers(MQContainer.
    java:545)
    at
    com.hkex.common.mq.mqwrapper.MQContainer.createMQObject(MQContainer.j
    ava:387)
    at
    com.hkex.common.mq.mqwrapper.MQContainer.initMQConfig(MQContainer.jav
    a:360)
    at
    com.hkex.common.mq.mqwrapper.MQContainer.<init>(MQContainer.java:93)
    at
    com.hkex.common.mq.mqwrapper.MQContainer.<clinit>(MQContainer.java:63
    at
    com.hkex.common.mq.interfacewrapper.FuncParameter.setExpiryTime(FuncP
    arameter.java:270)
    at
    com.hkex.common.mq.interfacewrapper.MQHostAccess.invoke(MQHostAccess.
    java:336)
    at
    com.hkex.common.mq.interfacewrapper.MQHostAccess.syncInvoke(MQHostAcc
    ess.java:236)
    at
    com.hkex.arch.msg.ToHostMessage.sendToMQ(ToHostMessage.java:150)
    at
    com.hkex.arch.msg.DefaultHostInterface.sendToMQ(DefaultHostInterface.
    java:28)
    at
    com.hkex.arch.msg.MFMModuleBase.sendToMQ(MFMModuleBase.java:26)
    at
    com.hkex.arch.msg.MFMModuleBase.sendToMQ(MFMModuleBase.java:21)
    at
    com.hkex.cl.model.dao.mq.MFM_PXCLTL02.processEnquiryDisplayRequest(MF
    M_PXCLTL02.java:1676)
    at
    com.hkex.cl.model.dao.mq.SettlementInstructionDAO.SITLenquiryDisplay(
    SettlementInstructionDAO.java:279)
    at
    com.hkex.cl.model.SIServicesEJB.SITLenquiryDisplay(SIServicesEJB.java
    :680)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    com.hkex.cl.model.ejb_skel_com_hkex_cl_model_SIServicesEJB.SITLenquir
    yDisplay(ejb_skel_com_hkex_cl_model_SIServicesEJB.java:1176)
    at
    com.hkex.cl.model.ejb_kcp_skel_SIServices.SITLenquiryDisplay__com_hke
    x_cl_SIDetail__com_hkex_arch_base_CCASSUs__43836001(ejb_kcp_skel_SIServices.java
    :1094)
    at com.kivasoft.ebfp.FPRequest.invokenative(Native Method)
    at com.kivasoft.ebfp.FPRequest.invoke(Unknown Source)
    at
    com.hkex.cl.model.ejb_kcp_stub_SIServices.SITLenquiryDisplay(ejb_kcp_
    stub_SIServices.java:1359)
    at
    com.hkex.cl.model.ejb_stub_SIServices.SITLenquiryDisplay(ejb_stub_SIS
    ervices.java:123)
    at
    com.hkex.cl.controller.SITLEnquiry.processQuery(SITLEnquiry.java:161)
    at
    com.hkex.arch.controller.base.HttpControllerAdvanced.list(HttpControl
    lerAdvanced.java:113)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    com.hkex.arch.controller.base.HttpControllerBasic.invokeActionHandler
    (HttpControllerBasic.java:1430)
    at
    com.hkex.arch.controller.base.HttpControllerBasic.handleBusinessReque
    st(HttpControllerBasic.java:1309)
    at
    com.hkex.arch.controller.base.HttpControllerBasicExtended.handleBusin
    essRequest(HttpControllerBasicExtended.java:236)
    at
    com.hkex.arch.controller.base.HttpControllerBasic.doMagic(HttpControl
    lerBasic.java:1168)
    at
    com.hkex.arch.controller.base.HttpControllerBasic.doPost(HttpControll
    erBasic.java:1038)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:772)
    at
    com.hkex.arch.controller.base.HttpControllerBasic.service(HttpControl
    lerBasic.java:1012)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
    at
    com.netscape.server.servlet.servletrunner.ServletInfo.service(Unknown
    Source)
    at
    com.netscape.server.servlet.servletrunner.ServletRunner.execute(Unkno
    wn Source)
    at com.kivasoft.applogic.AppLogic.execute(Unknown Source)
    at com.kivasoft.applogic.AppLogic.execute(Unknown Source)
    at com.kivasoft.thread.ThreadBasic.run(Native Method)
    at java.lang.Thread.run(Thread.java:479)
    MQ Error Msg : Can't locate jms/theFactory
    MQ Localized Msg: Can't locate jms/theFactory
    Resolved_Name():null
    UnResolved_Name():null
    Root Cause(): null
    Get Explaination():Can't locate jms/theFactory

    Hi,
    My application failed to lookup a JMS Object using JNDI lookup in EJB.
    The actual application flow is that a Servlet receive a request which
    then calls to an EJB
    where it loop up the JMS object to establish the message queue
    connection.
    It works with a simple Servlet which loop up the JMS Object without call
    to EJB.
    Does anyone known the possible reason causes the application failed to
    lookup the JMS Object?
    Thanks
    Avans
    the log is following
    The Status is :
    MQ java:comp/env/jms/theFactory
    MQjava:comp/env/jms/theFactoryjavax.naming.NameNotFoundException: Can't locate jms/theFactory
    at com.netscape.server.jndi.CompContext.resolveEnv(Unknown
    Source)
    at com.netscape.server.jndi.CompContext.lookup(Unknown Source)
    at com.netscape.server.jndi.java.javaURLContext.lookup(Unknown
    Source)
    at javax.naming.InitialContext.lookup(InitialContext.java:357)
    at
    com.hkex.common.mq.mqwrapper.MQReceiver.<init>(MQReceiver.java:109)
    at
    com.hkex.common.mq.mqwrapper.MQReceiverGroup.<init>(MQReceiverGroup.j
    ava:70)
    at
    com.hkex.common.mq.mqwrapper.MQContainer.createReceivers(MQContainer.
    java:545)
    at
    com.hkex.common.mq.mqwrapper.MQContainer.createMQObject(MQContainer.j
    ava:387)
    at
    com.hkex.common.mq.mqwrapper.MQContainer.initMQConfig(MQContainer.jav
    a:360)
    at
    com.hkex.common.mq.mqwrapper.MQContainer.<init>(MQContainer.java:93)
    at
    com.hkex.common.mq.mqwrapper.MQContainer.<clinit>(MQContainer.java:63
    at
    com.hkex.common.mq.interfacewrapper.FuncParameter.setExpiryTime(FuncP
    arameter.java:270)
    at
    com.hkex.common.mq.interfacewrapper.MQHostAccess.invoke(MQHostAccess.
    java:336)
    at
    com.hkex.common.mq.interfacewrapper.MQHostAccess.syncInvoke(MQHostAcc
    ess.java:236)
    at
    com.hkex.arch.msg.ToHostMessage.sendToMQ(ToHostMessage.java:150)
    at
    com.hkex.arch.msg.DefaultHostInterface.sendToMQ(DefaultHostInterface.
    java:28)
    at
    com.hkex.arch.msg.MFMModuleBase.sendToMQ(MFMModuleBase.java:26)
    at
    com.hkex.arch.msg.MFMModuleBase.sendToMQ(MFMModuleBase.java:21)
    at
    com.hkex.cl.model.dao.mq.MFM_PXCLTL02.processEnquiryDisplayRequest(MF
    M_PXCLTL02.java:1676)
    at
    com.hkex.cl.model.dao.mq.SettlementInstructionDAO.SITLenquiryDisplay(
    SettlementInstructionDAO.java:279)
    at
    com.hkex.cl.model.SIServicesEJB.SITLenquiryDisplay(SIServicesEJB.java
    :680)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    com.hkex.cl.model.ejb_skel_com_hkex_cl_model_SIServicesEJB.SITLenquir
    yDisplay(ejb_skel_com_hkex_cl_model_SIServicesEJB.java:1176)
    at
    com.hkex.cl.model.ejb_kcp_skel_SIServices.SITLenquiryDisplay__com_hke
    x_cl_SIDetail__com_hkex_arch_base_CCASSUs__43836001(ejb_kcp_skel_SIServices.java
    :1094)
    at com.kivasoft.ebfp.FPRequest.invokenative(Native Method)
    at com.kivasoft.ebfp.FPRequest.invoke(Unknown Source)
    at
    com.hkex.cl.model.ejb_kcp_stub_SIServices.SITLenquiryDisplay(ejb_kcp_
    stub_SIServices.java:1359)
    at
    com.hkex.cl.model.ejb_stub_SIServices.SITLenquiryDisplay(ejb_stub_SIS
    ervices.java:123)
    at
    com.hkex.cl.controller.SITLEnquiry.processQuery(SITLEnquiry.java:161)
    at
    com.hkex.arch.controller.base.HttpControllerAdvanced.list(HttpControl
    lerAdvanced.java:113)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    com.hkex.arch.controller.base.HttpControllerBasic.invokeActionHandler
    (HttpControllerBasic.java:1430)
    at
    com.hkex.arch.controller.base.HttpControllerBasic.handleBusinessReque
    st(HttpControllerBasic.java:1309)
    at
    com.hkex.arch.controller.base.HttpControllerBasicExtended.handleBusin
    essRequest(HttpControllerBasicExtended.java:236)
    at
    com.hkex.arch.controller.base.HttpControllerBasic.doMagic(HttpControl
    lerBasic.java:1168)
    at
    com.hkex.arch.controller.base.HttpControllerBasic.doPost(HttpControll
    erBasic.java:1038)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:772)
    at
    com.hkex.arch.controller.base.HttpControllerBasic.service(HttpControl
    lerBasic.java:1012)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
    at
    com.netscape.server.servlet.servletrunner.ServletInfo.service(Unknown
    Source)
    at
    com.netscape.server.servlet.servletrunner.ServletRunner.execute(Unkno
    wn Source)
    at com.kivasoft.applogic.AppLogic.execute(Unknown Source)
    at com.kivasoft.applogic.AppLogic.execute(Unknown Source)
    at com.kivasoft.thread.ThreadBasic.run(Native Method)
    at java.lang.Thread.run(Thread.java:479)
    MQ Error Msg : Can't locate jms/theFactory
    MQ Localized Msg: Can't locate jms/theFactory
    Resolved_Name():null
    UnResolved_Name():null
    Root Cause(): null
    Get Explaination():Can't locate jms/theFactory

  • PortalRuntimeException: Failed in WD JNDI lookup.

    Hi Experts
    We are getting the following exception when we try to run our WD application in an iView :
    com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name xxxxx.com
    If we deploy and run our application as such on the server,it works fine.This issue comes only after we have integrated it in the iview.
    Please provide some pointers.

    Hello Kunal
    when you integrate it in an iView, pcd address/location should be there atttributes..i think it's missing
    Bhudev

  • Failed in WD JNDI lookup in QA  Portal

    Hello Experts,
    I am facing the issue in custom WD application in QA portal system, in dev portal the application is working fine and after transporting the objects into QA portal ,while on preview the iview its giving me error : "Failed in WD JNDI lookup ".
    I have tested the WD application from Web dynpro console and its working fine , even i have created iview in QA portal and its working fine but while transporting the iview from DEV to QA Portal is not working . Can any one help me on that .
    Your help will highly appreciated ..
    Details error :
    com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name home~eth_dis
        at com.sap.portal.pcm.iview.admin.AdminBaseiView.createAttrSetLayersList(AdminBaseiView.java:357)
        at com.sap.portal.pcm.iview.admin.AdminBaseiView.getAttrSetLayersList(AdminBaseiView.java:205)
        at com.sap.portal.pcm.iview.admin.AdminBaseiView.getCustomImplementation(AdminBaseiView.java:148)
        at com.sap.portal.pcm.admin.PcmAdminBase.getImplementation(PcmAdminBase.java:530)
        at com.sapportals.portal.ivs.iviews.IviewServiceObjectFactory.getObjectInstance(IviewServiceObjectFactory.java:442)
        ... 40 more

    Hi Shanti,
    Thanks for the quick response.
    My portal version is EP 7 with SP21 .As I mention in my thread that I have tested custom application on QA Portal  and its working fine. But the problem is only appearing with the transported iview into QA portal.
    Regards
    Rashi

  • Javax.naming.NamingException: Failed in WD JNDI lookup

    Hi,
               I have deployed wdj applications,some times its working fine ,but some other times its through the following errors.
    javax.naming.NamingException: Failed in WD JNDI lookup
    Any one please suggest me
    Thanks,
    Venu

    Hi Friend,
    I am not sure what Other Reason can be for this problem mean while check these links. Hope it will help.
    /message/6928201#6928201 [original link is broken]
    /message/6315352#6315352 [original link is broken]
    Regards
    Jeetendra

  • Failed to lookup External Link

    Hi,
    I just upgraded to EP7 SP12 and deployed the ESS BP.  When I try to preview Content Administration -> Portal Content -> Content Provided by SAP -> Employee Self Service -> iViews -> Benefits and Payment -> Benefits Participation, we see the below error.
    com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed to lookup External Link for: portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.bp_folder/com.sap.pct.erp.ess.iviews/com.sap.pct.erp.ess.benefits_payment/com.sap.pct.erp.ess.benparticipation
    Any one have any ideas?
    Your help is greatly appreciated.
    Regards,
    Rick

    I did some more research. It seems like we are having the same problem on another portal server. So I don't think I caused the problem. This is coming from the standard business planning pages like planning wizard, planning modeler, etc.

  • Failed to lookup connection factory weblogic.jms.XAConnectionFactory

    when i deploy any service with jms protocol (write to queue) using sbconsole i face this error
    "Failed to lookup connection factory weblogic.jms.XAConnectionFactory"
    any suggestion?
    Thanks

    weblogic.jms.XAConnectionFactory is the default XA connection factory class. You wont see this in any JMS modules in Weblogic server. It should be available by default.
    Can you once check the JNDI tree of your servers if this JNDI name exists. (in Weblogic Administration console go to Servers, click on any server and there will be a link for JNDI tree on the server's page)
    Also, try creating a new connection factory in Weblogic console and using that in your service. Although it is highly unlikely that a new connection factory will work since all custom XA connection factories are dependent on the default connection factory class you mentioned.

  • [SOLVED]Failed to lookup alias 'nvidia' (X server dies during startop)

    Hello there everybody.
    I recenly reinstalled Arch so that I could have a nice, clean install, and also because I though I was having trouble with the systemd migration.  I think I was wrong there.
    I successfully installed using the February 1st cd.  Since that time, I have been unable to boot into a graphical system.
    I have the current proprietary nvidia drivers installed - I tried with an older set with no change, and I tried the Nouveau drivers and got as far as a blinking cursor on TTY7 (but similar X server errors), so I abandoned that route (I want the proprietary drivers).
    systemctl status kdm
    returns
    kdm.service - K Display Manager
    Loaded: loaded (/usr/lib/systemd/system/kdm.service; enabled)
    Active: active (running) since Sat 2013-03-23 08:42:09 EDT; 19 min ago
    Main PID: 289 (kdm)
    CGroup: name=systemd:/systemd/kdm.service
    └─289 /usr/bin/kdm -nodaemon
    Mar 23 08:42:10 awesomeDelicious kdm[289]: X server for display :0 cannot be started, session disabled
    Following advice on another thread, I issued
    echo 'nvidia' >> /etc/modules-load.d/nvidia.conf
    but I don't think that helps at all, as
    /lib/systemd/systemd-modules-load
    returns
    Failed to lookup alias 'nvidia': Function not implemented
    so I am currently at a loss.  I'd like to be able to get back into KDE as soon as I can, so any help is much appreciated!
    Last edited by nikolardo (2013-03-25 23:31:28)

    I assume you mean my Xorg.0.log (if not, correct me and direct me to xorg.log.0)
    [ 5.091]
    X.Org X Server 1.14.0
    Release Date: 2013-03-05
    [ 5.091] X Protocol Version 11, Revision 0
    [ 5.091] Build Operating System: Linux 3.8.2-1-ARCH x86_64
    [ 5.091] Current Operating System: Linux awesomeDelicious 3.7.6-1-ARCH #1 SMP PREEMPT Mon Feb 4 09:15:13 CET 2013 x86_64
    [ 5.091] Kernel command line: root=/dev/sda3 ro initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux
    [ 5.091] Build Date: 09 March 2013 11:43:05AM
    [ 5.091]
    [ 5.091] Current version of pixman: 0.28.2
    [ 5.091] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 5.091] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 5.091] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Mar 23 10:05:25 2013
    [ 5.147] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 5.159] (==) No Layout section. Using the first Screen section.
    [ 5.159] (==) No screen section available. Using defaults.
    [ 5.159] (**) |-->Screen "Default Screen Section" (0)
    [ 5.159] (**) | |-->Monitor "<default monitor>"
    [ 5.159] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 5.159] (==) Automatically adding devices
    [ 5.159] (==) Automatically enabling devices
    [ 5.159] (==) Automatically adding GPU devices
    [ 5.199] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 5.199] Entry deleted from font path.
    [ 5.215] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 5.215] Entry deleted from font path.
    [ 5.215] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 5.216] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 5.216] Entry deleted from font path.
    [ 5.216] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 5.216] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/
    [ 5.216] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 5.216] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 5.216] (II) Loader magic: 0x7fdc20
    [ 5.216] (II) Module ABI versions:
    [ 5.216] X.Org ANSI C Emulation: 0.4
    [ 5.216] X.Org Video Driver: 14.1
    [ 5.216] X.Org XInput driver : 19.1
    [ 5.216] X.Org Server Extension : 7.0
    [ 5.218] (--) PCI:*(0:1:0:0) 10de:0cb1:1043:203c rev 162, Mem @ 0xf2000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000d000/128, BIOS @ 0x????????/524288
    [ 5.234] Initializing built-in extension Generic Event Extension
    [ 5.234] Initializing built-in extension SHAPE
    [ 5.234] Initializing built-in extension MIT-SHM
    [ 5.234] Initializing built-in extension XInputExtension
    [ 5.234] Initializing built-in extension XTEST
    [ 5.234] Initializing built-in extension BIG-REQUESTS
    [ 5.234] Initializing built-in extension SYNC
    [ 5.234] Initializing built-in extension XKEYBOARD
    [ 5.234] Initializing built-in extension XC-MISC
    [ 5.234] Initializing built-in extension SECURITY
    [ 5.234] Initializing built-in extension XINERAMA
    [ 5.234] Initializing built-in extension XFIXES
    [ 5.234] Initializing built-in extension RENDER
    [ 5.234] Initializing built-in extension RANDR
    [ 5.234] Initializing built-in extension COMPOSITE
    [ 5.234] Initializing built-in extension DAMAGE
    [ 5.234] Initializing built-in extension MIT-SCREEN-SAVER
    [ 5.234] Initializing built-in extension DOUBLE-BUFFER
    [ 5.234] Initializing built-in extension RECORD
    [ 5.234] Initializing built-in extension DPMS
    [ 5.234] Initializing built-in extension X-Resource
    [ 5.234] Initializing built-in extension XVideo
    [ 5.234] Initializing built-in extension XVideo-MotionCompensation
    [ 5.234] Initializing built-in extension XFree86-VidModeExtension
    [ 5.234] Initializing built-in extension XFree86-DGA
    [ 5.234] Initializing built-in extension XFree86-DRI
    [ 5.234] Initializing built-in extension DRI2
    [ 5.234] (II) LoadModule: "glx"
    [ 5.401] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 5.924] (II) Module glx: vendor="NVIDIA Corporation"
    [ 5.924] compiled for 4.0.2, module version = 1.0.0
    [ 5.924] Module class: X.Org Server Extension
    [ 5.924] (II) NVIDIA GLX Module 313.26 Wed Feb 27 13:10:40 PST 2013
    [ 5.932] Loading extension GLX
    [ 5.932] (==) Matched nouveau as autoconfigured driver 0
    [ 5.932] (==) Matched nvidia as autoconfigured driver 1
    [ 5.932] (==) Matched nv as autoconfigured driver 2
    [ 5.932] (==) Matched vesa as autoconfigured driver 3
    [ 5.932] (==) Matched modesetting as autoconfigured driver 4
    [ 5.932] (==) Matched fbdev as autoconfigured driver 5
    [ 5.932] (==) Assigned the driver to the xf86ConfigLayout
    [ 5.932] (II) LoadModule: "nouveau"
    [ 5.932] (WW) Warning, couldn't open module nouveau
    [ 5.932] (II) UnloadModule: "nouveau"
    [ 5.932] (II) Unloading nouveau
    [ 5.932] (EE) Failed to load module "nouveau" (module does not exist, 0)
    [ 5.932] (II) LoadModule: "nvidia"
    [ 5.932] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 5.995] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 5.995] compiled for 4.0.2, module version = 1.0.0
    [ 5.995] Module class: X.Org Video Driver
    [ 5.995] (WW) NVIDIA: This server has an unsupported input driver ABI version (have 19.1, need < 19.0). The driver will continue to load, but may behave strangely.
    [ 6.021] (EE) NVIDIA: Failed to load the NVIDIA kernel module. Please check your
    [ 6.021] (EE) NVIDIA: system's kernel log for additional error messages.
    [ 6.021] (II) UnloadModule: "nvidia"
    [ 6.021] (II) Unloading nvidia
    [ 6.021] (EE) Failed to load module "nvidia" (module-specific error, 0)
    [ 6.021] (II) LoadModule: "nv"
    [ 6.021] (WW) Warning, couldn't open module nv
    [ 6.021] (II) UnloadModule: "nv"
    [ 6.021] (II) Unloading nv
    [ 6.021] (EE) Failed to load module "nv" (module does not exist, 0)
    [ 6.021] (II) LoadModule: "vesa"
    [ 6.021] (WW) Warning, couldn't open module vesa
    [ 6.021] (II) UnloadModule: "vesa"
    [ 6.021] (II) Unloading vesa
    [ 6.021] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 6.021] (II) LoadModule: "modesetting"
    [ 6.021] (WW) Warning, couldn't open module modesetting
    [ 6.021] (II) UnloadModule: "modesetting"
    [ 6.021] (II) Unloading modesetting
    [ 6.021] (EE) Failed to load module "modesetting" (module does not exist, 0)
    [ 6.021] (II) LoadModule: "fbdev"
    [ 6.022] (WW) Warning, couldn't open module fbdev
    [ 6.022] (II) UnloadModule: "fbdev"
    [ 6.022] (II) Unloading fbdev
    [ 6.022] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 6.022] (EE) No drivers available.
    [ 6.022]
    Fatal server error:
    [ 6.022] no screens found
    [ 6.022] (EE)
    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    [ 6.022] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    [ 6.022] (EE)
    ...so I seem to have a problem with ABI version?
    A quick search shows that some people have fixed this with an ignoreABI option somewhere, is this advisable, and how would I accomplish it?
    Anyway yes further advice please!

  • JNDI Provider Connection With Weblogic 8.1

    Hi all,
    I am using SUN ONE Studio V 5.0 update 1 with weblogic 8.1 integrated with it.
    Today I have added weblogic.jar in the classpath of the project.
    Now I went to "runtime tab" and installed a jndi provider with factoryname and url successfully.
    I tested the provider successfully :)
    But when I tried to connect it to the service it failed.
    IDE thrown a NPE and error message in dialog appears, says "TimeOut value is too short to connect".
    There is no option for setting this timeout value.
    Could any one pls help me regarding this. How can I get connected to JNDI service given by WL 8.1 ?
    Has anyone also faced such problem ?
    My server is up and smiling on me.
    I am adding that error message fully....
    java.lang.NullPointerException
         at weblogic.rmi.internal.StubGenerator.getStubOnClient(StubGenerator.java:785)
         at weblogic.rmi.internal.StubGenerator.getStubClass(StubGenerator.java:758)
         at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:803)
         at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:790)
         at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:79)
         at weblogic.common.internal.RMIBootServiceStub.getStub(RMIBootServiceStub.java:50)
         at weblogic.security.acl.internal.Security.authenticate(Security.java:152)
         at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRemotely(WLInitialContextFactoryDelegate.java:597)
         at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:534)
         at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:336)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:308)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:234)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
         at javax.naming.InitialContext.init(InitialContext.java:219)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:80)
         at org.netbeans.modules.jndi.JndiDirContext.<init>(JndiDirContext.java:47)
         at org.netbeans.modules.jndi.JndiDataType$1$Connector.checkContextValidity(JndiDataType.java:211)
         at org.netbeans.modules.jndi.JndiDataType$1$Connector.run(JndiDataType.java:169)
         at java.lang.Thread.run(Thread.java:534)
    --------------- nested within: ------------------
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Failed to generate class for weblogic.common.internal.RMIBootServiceImpl_811_WLStub ] - with nested exception:
    [java.lang.NullPointerException]
         at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:807)
         at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:790)
         at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:79)
         at weblogic.common.internal.RMIBootServiceStub.getStub(RMIBootServiceStub.java:50)
         at weblogic.security.acl.internal.Security.authenticate(Security.java:152)
         at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRemotely(WLInitialContextFactoryDelegate.java:597)
         at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:534)
         at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:336)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:308)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:234)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
         at javax.naming.InitialContext.init(InitialContext.java:219)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:80)
         at org.netbeans.modules.jndi.JndiDirContext.<init>(JndiDirContext.java:47)
         at org.netbeans.modules.jndi.JndiDataType$1$Connector.checkContextValidity(JndiDataType.java:211)
         at org.netbeans.modules.jndi.JndiDataType$1$Connector.run(JndiDataType.java:169)
    [catch] at java.lang.Thread.run(Thread.java:534)
    one this more, if u see help then it is written that WL plugin will work only with jdk 1.3.1 and not with 1.4 but my plugin works successfully. What does it mean ?
    My userdir is : C:\Utility\Dir4j, when I installed the provider for connecting to JNDI service of WL, then IDE created a dir C:\Utility\Dir4j\system\JNDI folder and created weblogic_jndi_WLInitialContextFactory.impl file under it.
    Because I added that weblogic.jar file on my FSystem thats' why It created it under my userdir.
    Pls Help
    Sanjeev

    Hi Sanjeev :
    I am running into the same problem . Could you please be kind enough to tell me how you fixed the problem. I followed your solution but I am still running into the same problem.
    Basically my WebStart application should be getting a connection from the Connection pool making a t3 call to a Weblogic server.
    Thanks in advance .

  • Failed to fetch data provider data. (LO 26306)

    Hi,
    We have created a webi report, which is having a date prompts.
    The same webi report, we have used in xelsius using a live office connection.
    In Xelsius, We have checked the box 'refresh on load', under usage tab.
    When we run the xelsius dashboard, we are getting an "Failed to fetch data provider data. (LO 26306)".
    Can anyone please help. why this error is getting. Is it because of prompts which are there in webi report.
    Basically, our requirement is when the user runs the dashboard, prompts should be displayed. User will enter the prompts and based on that, dash board should get display.
    Regards
    Ramesh Ganji

    See SAP Note 1440129.
    Symptom
    Change the Live Office documentation to clearly state that before importing a Live Office document within Xcelsius the Live Office document has to be opened in Excel and the 'Refresh All objects' triggered.  If this step is not done and the Excel file is saved without prior refresh the error 'Failed to fetch data provider data (LO 26306) in Xcelsius is raised (when previewing the model)
    Environment
    Live Office 3.1
    Xcelsius 2008
    Cause
    The information is not stated in the official documentation.
    Resolution
    The issue has been identified and logged under Problem Report ID ADAPT01374107
    Keywords
    01374107, ADAPT, ADAPT01374107, LO, 26306, LO 26306, LiveOffice

  • Using JNDI Provider for Oracle JMS Queue

    Hello,
    I created a JMS Queue in Oracle 9.2.0.1 and would like
    a Java client to receive events from the Queue. I am
    not running Oracle9iAS. I have access to WebLogic server
    7.0 which is also a JNDI provider. Is there a sample code
    that shows the steps on how to go about this.
    thanks very much for any pointers.

    To define an Enterprise Message Source for AS JMS and OJMS in BAM, see Chapter 3 in the BAM Architect's User Guide.
    Specifying Settings for Oracle (AS JMS and OJMS)
    Settings for Oracle (AS JMS and OJMS) include:
    ■ Initial Context Factory.
    For 10.1.3: oracle.j2ee.rmi.RMIInitialContextFactory
    For 10.1.2: com.evermind.server.rmi.RMIInitialContextFactory
    ■ JNDI Service Provider URL. For standalone use oc4j: ormi://machine_name/
    where machine_name is the OC4J installed host, and for production use Application Server: opmn:ormi://<machine_name>:<opmn request port>:home where machine_name is the application server installed host, opmn request port could be found from looking at opmn.xml in <App server install location>/opmn/conf
    ■ TopicConnectionFactory Name.
    java:comp/resource/BAMTTT/TopicConnectionFactories/bam_ttq_tab
    ■ Topic Name. java:comp/resource/BAMTTT/Topics/bam_ttq
    ■ JMS Message Type. TextMessage.
    ■ Durable Subscriber Name. BAMFilteredSubscription
    ■ Message Selector. Message selector, for example, BAMFilter='true'
    ■ Client ID. ClientID
    You can also refer to:
    http://www.oracle.com/technology/products/integration/bam/10.1.3/TechNotes/TechNote_BAM_AQ_Configuration.pdf
    Regards, Stephen

  • HT1145 I downloaded the Airport Utility 5.6 for OS X Lion and when I finish installing it sends a message that says "the instalation failed contact your software provider"

    I downloaded the Airport Utility 5.6 for OS X Lion and when I finish installing it sends a message that says "the instalation failed contact your software provider" And seems like thats the solution so I can use my time capsule.
    Thanks

    Thanks. Please review my post above to see that we asked five basic questions.
    Looks like we got two answers.
    Can you please provide answers to the other questions that we asked?
    1)  Are you trying to connect your Time Capsule to your modem using an Ethernet cable?
    2)  What is the make and model number of your modem?
    3)  Are you still using Lion (10.7.5) as you indicate in your profile, or have you updated to Mountain Lion or Mavericks?
    I understand that things appear clear to you there, but we cannot read your mind or see your network, so we only know as much about your problem and your network as you can tell us.

  • JNDI Provider for wls 5.1 cluster

    hi,
              how can I specify a JNDI provider URL for a WLS 5.1 cluster where the
              cluster nodes are different machines ? Is there a way to specify the
              URL without using a single servers IP address ?
              thx
              johannes
              

    [att1.html]
              

  • Failed to lookup port type on Mediator Callback

    Hi everyone,
    I'm new to SOA Suite and to learn it i've started following the book "Getting Started with Oracle Soa Suite: A Hands On Tutorial". In chapter 7 about BPEL i'm getting the following error message when i try to set a callback on the mediator to a BPEL process:
    Nov 6, 2012 9:09:46 PM oracle.tip.tools.ide.fabric.model.WSDLInterface loadOperations
    SEVERE: Failed to lookup PortType for {http://xmlns.oracle.com/pcbpel/adapter/file/POProcessing/POProcessing/WriteApprovalResults}Write_ptt in POProcessing/WriteApprovalResults
    Nov 6, 2012 9:09:46 PM oracle.tip.tools.ide.fabric.model.WSDLInterface loadOperations
    SEVERE: Failed to lookup PortType for {http://oracle.com/sca/soapservice/CreditCardValidation/validationForCC/getStatusByCC}execute_ptt in POProcessing/getCreditCardStatus
    I've already acessed the WSDL on browser, tested them on EM and everything seems ok with these two services.
    Please, could you help me to solve this error? If you need some code or configuration i can post here.
    Best regards,
    Hugo

    SEVERE: Failed to lookup PortType for...
    1. Maybe its just really a different port type and you have it mistyped or something in the calling webservices inside your code (where it makes a call to the WSDL endpoint)
    2. It could be that the WSDL basically needs to be local. That is, although its an off the shelf application and all.. you need to download the WSDL on your local computer in a C:\drive or
    a location and then use that WSDL file to generate web services from the tool you are using (like eclipse/jdev so on so forth)
    what is the port type that you have and the port number ?
    -Rtiee

  • Failed MX lookup on tcp_intranet

    Hi, I have a new test installation of Comms Suite 5:
    Sun Java(tm) System Messaging Server 6.3-0.15 (built Feb 9 2007)
    libimta.so 6.3-0.15 (built 19:27:56, Feb 9 2007)
    SunOS uwc 5.10 Generic_118833-36 sun4v sparc SUNW,Sun-Fire-T1000
    This is a two-tiered deployment. If I enable Messenger Express on the message store system, I can send and receive mail within this test domain. But when I send mail with either Messenger Express or Communications Express on the front-end, it sits in the tcp_intranet queue with the following message in mail.log_current:
    24-May-2007 21:18:08.79 tcp_intranet Q 1 [email protected] rfc822;[email protected] @store.mydomain.com:[email protected] Failed MX lookup; try again later
    This all makes sense to me: This is a user in this domain, on the system store.mydomain.com. I don't understand why it is attempting a DNS lookup. The store system is reachable as both "store.mydomain.com" and "store" using entries in /etc/hosts. It is correct that DNS is not configured on this system, it just seems odd to me that DNS is necessary on the tcp_intranet channel.
    Can anyone shed some light?
    Thanks.

    Hi,
    This is a two-tiered deployment. If I enable
    Messenger Express on the message store system, Ican
    send and receive mail within this test domain.But
    when I send mail with either Messenger Express or
    Communications Express on the front-end, it sits in
    the tcp_intranet queue with the following message
    in
    mail.log_current:
    24-May-2007 21:18:08.79 tcp_intranet Q
    1
    [email protected] rfc822;[email protected]
    @store.mydomain.com:[email protected] Failed MX
    lookup; try again later
    This all makes sense to me: This is a user in this
    domain, on the system store.mydomain.com. I don't
    understand why it is attempting a DNS lookup. The
    store system is reachable as both
    "store.mydomain.com" and "store" using entries in
    /etc/hosts. It is correct that DNS is not
    configured
    on this system, it just seems odd to me that DNS is
    necessary on the tcp_intranet channel.
    DNS is fundamental to the delivery of email. By
    default tcp_intranet channel has the 'mx' keyword
    which means it will try an MX lookup for the outgoing
    host/domain.
    You can prevent this by changing the 'mx' to 'nomx'
    on the tcp_intranet channel definition in the
    imta.cnf file so it will deliver to the A record of
    the domain instead.
    Run ./imsimta cnbuild;./imsimta restart for the
    change to take affect.
    Regards,
    Shane.Shane, thanks for your reply.
    This is still a little confusing. I can set up DNS, but if this MTA looks up the MX record for the domain, it will get its own address. This MTA is the front-end, it is trying to deliver to the message store. I completely understand the need for DNS and the MX lookup on tcp_local, but I'm not clear about what the MTA will do with the information it receives in the MX record.
    Thanks.

Maybe you are looking for