Failing to lookup UserManagerHome

Hi,
In BEA portal 8.1. I am trying to call the following snippet on code inside a J2EE servlet filter intercepting any requests to URI /sampleportal.
Hashtable env = new Hashtable();
env.put(javax.naming.Context.SECURITY_PRINCIPAL, "weblogic");
env.put(javax.naming.Context.SECURITY_CREDENTIALS, "weblogic");
return new InitialContext(env);
InitialContext initContext = new InitialContext(env);
_usrManagerHome = (UserManagerHome)
initContext.lookup(ApplicationHelper.getApplicationName() + ".BEA_personalization.UserManager"); -> 1
userManager = usrManagerHome.create();
_userManager.userExists(userName);
The JNDI lookup (1) is failing. I have tried many combinations after studying the samples (CreateUserBacking.java) but nothing worked. Even recompiled the whole portalApp and redeployed it. An interesting thing I observed in weblogic.xml for sampleportal is that the jndi names are prefixed with ${APPNAME}. How does this variable translate to the real Application URI ?
I want to verify the presence of a User id in the local repository for the portal. Is this the right way to do it ?
If so what am I doing wrong ? Any input will be greatly appreciated.
Thanks,
Krishnendu

${APPNAME} should get switched the application name for JNDI binding
during deployment. Check in the console to see what's actually in the
JNDI tree (I think you can right-click on your Server in the tree).
You would probably be better off using an <ejb-ref> -- then you would
get deployment time warnings and failures if the EJB didn't deploy
correctly. If it's not there, make an <ejb-ref> entry in web.xml to
<ejb-link>p13n_ebj.jar#UserManager</ejb-link>, then use a JNDI name like
"java:comp/env/<ejb-name from web.xml>"
Also, please attach the stacktrace and any server start output to help
solving this problem.
Greg
Krishnendu Chakraborty wrote:
Hi,
In BEA portal 8.1. I am trying to call the following snippet on code inside a J2EE servlet filter intercepting any requests to URI /sampleportal.
Hashtable env = new Hashtable();
env.put(javax.naming.Context.SECURITY_PRINCIPAL, "weblogic");
env.put(javax.naming.Context.SECURITY_CREDENTIALS, "weblogic");
return new InitialContext(env);
InitialContext initContext = new InitialContext(env);
_usrManagerHome = (UserManagerHome)
initContext.lookup(ApplicationHelper.getApplicationName() + ".BEA_personalization.UserManager"); -> 1
userManager = usrManagerHome.create();
_userManager.userExists(userName);
The JNDI lookup (1) is failing. I have tried many combinations after studying the samples (CreateUserBacking.java) but nothing worked. Even recompiled the whole portalApp and redeployed it. An interesting thing I observed in weblogic.xml for sampleportal is that the jndi names are prefixed with ${APPNAME}. How does this variable translate to the real Application URI ?
I want to verify the presence of a User id in the local repository for the portal. Is this the right way to do it ?
If so what am I doing wrong ? Any input will be greatly appreciated.
Thanks,
Krishnendu

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

  • 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 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.

  • 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
    ?

  • 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.

  • Failed to lookup PortType

    Hi everyone,
    I'm new to SOA Suite and to learn it i 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:
    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+
    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

  • [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!

  • Fail to lookup the local EJB by JNDI in Managed Server

    Hi all,
    I currently in a deep problem, and can't figure out the cause of it. It just annoying me for week.
    In my app, I have binded to the local ejb to JNDI (let's say "ejb/CustomerLocal"), then the client lookup the Local EJB by the following code.
    localIc = new InitialContext();
    home = (EJBLocalHome)localIc.lookup("ejb/CustomerLocal");
    It works well as I do development in the Domain Admin Server. However, when I do the System Integration Test and deploy my app to the managed server, the app fail. It just can't do the Local EJB lookup. Following is the exception.
    javax.naming.NameNotFoundException: Unable to resolve 'ejb/CustomerLocal' Resolved ejb[Root exc
    eption is javax.naming.NameNotFoundException: Unable to resolve 'ejb.CustomerLocal' Resolved ejb
    ]; remaining name CustomerLocal'
    Does anybody know the cause of it and have solution?
    Thanks a lot

    Hi,
    Just now I replicated the same problem what you are facing. I created one managed server. When I deployed my ejb to admin server I did not get any problem. But when I deploy the same into my managed server I got Naming Exception. Because I did n/t specify Context.PROVIDER_URL. A provider URL contains bootstrap server information that the initial context factory can use to obtain an initial context. So when you deploy EJB on another server, you have to get the Naming service from that server. Hence provider URL must pointing to that server. So I included following statements before lookup my ejb in managed server.
    Properties p=new Properties ();
    p.put (Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
    p.put (Context.PROVIDER_URL,"t3://localhost: 7003");
    Context ctx=new InitialContext (p);
    FacadeHome home=(FacadeHome) ctx.lookup ("ejb/CustomerLocal");
    In my case managed server port number is 7003. Now onwards managed server (Port number 7003) will provide ‘Naming Service’, not by admin server (port number 7001), which is default.
    Note: Context.PROVIDER_URL— specifies the URL of the WebLogic Server that provides the name service. The default is t3://localhost: 7001. When you are not specified it will assume that POVIDER_URL is t3://localhost: 7001 this is nothing but your admin server in your case. However, a JNDI client may need to access a name space other than the one identified in its environment. In this case, it is necessary to explicitly set the java.naming.provider.url (provider URL) property used by the InitialContext constructor.
    I hope it helps.
    Regards,
    Kuldeep Singh.

  • Spring fails to lookup Data Source using JNDI

    Hi all I am now for configure jndi in tomcat5.5 .. my integration is like spring+hybernate+jpa
    I am getting the error is
    ERROR - ContextLoader.initWebApplicationContext(219) | Context initialization failed
    org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSource' defined in ServletContext resource [WEB-INF/xaconfig/daoJPAConfig.xml]: Invocation of init method failed; nested exception is javax.naming.NamingException: Cannot create resource instance
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1412)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
         at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:291)
         at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
         at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288)
         at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190)
         at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:546)
         at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:871)
         at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:423)
         at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:272)
         Caused by: javax.naming.NamingException: Cannot create resource instance
    my tomcat 5.5/context.xml is
    <?xml version="1.0" encoding="UTF-8"?>
    <!-- The contents of this file will be loaded for each web application --><Context>
    <!-- Default set of monitored resources -->
    <WatchedResource>WEB-INF/web.xml</WatchedResource>
         <Transaction factory="com.atomikos.icatch.jta.UserTransactionFactory"/>
    <!-- Uncomment this to disable session persistence across Tomcat restarts -->
    <!--
    <Manager pathname="" />
    -->
    <ResourceLink global="jdbc/Paymentsdb" name="jdbc/Paymentsdb" type="com.atomikos.jdbc.AtomikosDataSourceBean"/>
    </Context>
    and my tomcat5.5/server.xml is
    <?xml version="1.0" encoding="UTF-8"?>
    <Server port="8005" shutdown="SHUTDOWN">
    <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"/>
    <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"/>
    <Listener className="org.apache.catalina.storeconfig.StoreConfigLifecycleListener"/>
    <Listener className="com.atomikos.tomcat.AtomikosLifecycleListener"/>
    <GlobalNamingResources>
    <Environment name="simpleValue" type="java.lang.Integer" value="30"/>
    <Resource auth="Container" description="User database that can be updated and saved" factory="org.apache.catalina.users.MemoryUserDatabaseFactory" name="UserDatabase" pathname="conf/tomcat-users.xml" type="org.apache.catalina.UserDatabase"/>
    </GlobalNamingResources>
    <Service name="Catalina">
    <Connector acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxSpareThreads="75" maxThreads="150" minSpareThreads="25" port="8080" redirectPort="8443"/>
    <Connector enableLookups="false" port="8009" protocol="AJP/1.3" redirectPort="8443"/>
    <Engine defaultHost="localhost" name="Catalina">
         <Realm className="org.apache.catalina.realm.UserDatabaseRealm" resourceName="UserDatabase"/>
         <Host appBase="webapps" autoDeploy="true" name="localhost" unpackWARs="true" xmlNamespaceAware="false" xmlValidation="false">
    <Context docBase="com.evolvus.payments.web" path="/com.evolvus.payments.web" reloadable="true" source="org.eclipse.jst.j2ee.server:com.evolvus.payments.web">
    <Resource name="jdbc/Paymentsdb" auth="Container"
    type="com.atomikos.jdbc.AtomikosDataSourceBean"
    driverClassName="com.mysql.jdbc.jdbc2.optional.MysqlXADataSource"
    url="jdbc\:mysql\://devserver\:3306/payhub"
    username="root"
    password="root"
    maxActive="20"
    maxIdle="10"
    maxWait="20000"
    />
    </Context></Host>
    </Engine>
    </Service>
    </Server>
    and my web.xml is
    <?xml version="1.0" encoding="UTF-8"?>
    <web-app version="2.5"
         xmlns="http://java.sun.com/xml/ns/javaee"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
         <display-name>Payments</display-name>
         <context-param>
              <param-name>contextConfigLocation</param-name>
              <param-value>/WEB-INF/xaconfig/daoJPAConfig.xml</param-value>
         </context-param>
         <context-param>
         <param-name>javax.faces.CONFIG_FILES</param-name>
         <param-value>/WEB-INF/faces-config.xml</param-value>
         </context-param>
         <filter>
              <filter-name>PrimeFaces FileUpload Filter</filter-name>
              <filter-class>org.primefaces.webapp.filter.FileUploadFilter</filter-class>
         </filter>
         <filter-mapping>
              <filter-name>PrimeFaces FileUpload Filter</filter-name>
              <servlet-name>Faces Servlet</servlet-name>
         </filter-mapping>
         <context-param>
    <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
    <param-value>.xhtml</param-value>
    </context-param>
         <servlet>
              <servlet-name>Faces Servlet</servlet-name>
              <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
              <load-on-startup>1</load-on-startup>
         </servlet>
         <servlet-mapping>
              <servlet-name>Faces Servlet</servlet-name>
              <url-pattern>*.jsf</url-pattern>
         </servlet-mapping>
    <resource-ref>
    <description>PaymentsDatabase</description>
    <res-ref-name>jdbc/Paymentsdb</res-ref-name>
    <res-type>com.atomikos.jdbc.AtomikosDataSourceBean</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </web-app>
    and my daoJpaConfig i did like this
    <beans:bean id="dataSource"
              class="org.springframework.jndi.JndiObjectFactoryBean">
              <beans:property name="jndiName">
                   <beans:value>java:comp/env/jdbc/Paymentsdb</beans:value>
              </beans:property>
              </beans:bean>
                        what are the jar file i have to add in my tomcat 5.5 and webapplication ??
    plz help me i am struggling alot ..where i did mistakes      
    i am using transaction type as transaction-type="JTA" <persistence-unit name="payhub" transaction-type="JTA">

    import java.sql.*;
    import javax.sql.*;
    import javax.naming.*;
    import java.util.*;
    public class MyDataSourceLookupClient
         public final static String JNDI_FACTORY = "weblogic.jndi.WLInitialContextFactory";
         private static String serverUrl ="t3://localhost:7001";
    public static void main(String ar[])throws Exception
    InitialContext ic=null;
    try{
              Hashtable env = new Hashtable();
              env.put(Context.INITIAL_CONTEXT_FACTORY, JNDI_FACTORY);
              env.put(Context.PROVIDER_URL, serverUrl);
              ic = new InitialContext(env);
    catch(Exception e){}
    try{
    DataSource ds=ic.lookup("YourDataSourceJNDIName");
    Connection con=ds.getConnection();
    System.out.println("\n\t Got Connection: "+con);
    con.close();
    catch(Exception e)
    System.out.println("\n\n\t jack Exception => "+e);
    e.printStackTrace();
    Thanks
    Jay SenSharma
    http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)

  • Failed to lookup home for other EJB in ejbCreate()

    I am trying to lookup the home for other EJB deployed on separate weblogic server in ejbCreate() of my stateless session bean.But its not doing so and doesnt throw any exception either.Can anybody explain why?

    I am having the same problem too....I am using WL8.1 SP3.
    I am following a Service Manager pattern which works as a Service Locator instantiating remote EJBs on a different domain.
    Since I am located on Server A, I use reflection to get the EJBHome located on Server B.
    I successfully get the reference to the EJBHome successfully with my InitialContext().
    When I try to invoke the create() method of the EJBHome that I got using Reflection, I get the following exception:
    InvocationTargetException - Target is [Could not generate mx.com.inbursa.sii.estructura.corporativa.invoker.SynchronousCommandInvokerXXXXX due to the following error: weblogic.utils.AssertionError ****** ASSERTION FAILED [InvocationTargetException - Target is [NoClassDefFoundError in class com.esiglo.comun.exception.CommandException]]
    Note that I wrote it as I remember it (I will send the exact exception as soon as I can).
    It seems to me that the InvocationTargetException is generated when trying to create the EJB on Server B container, as I show it is done by reflection, but it does not recognize the CommandException class. It is strange since I made sure that the JAR which contains the CommandException class is deployed in the EAR on server B.
    Any ideas around this issue?
    Regards
    Tomas Flores

  • Search Failed - Address Lookup Corporate GAL

    Hello,
    A handful of users are randomly unable to search the corporate GAL from their iPhone (4.2 and 4.3)...  From their device, they'll open the GAL and start typing someone's name it immediately fails saying 'Search Failed'....  The user will only type 1 letter and it will fail.  It doesn't even seem the search is leaving the device because it fails instantly.
    We just upgraded to Exchange 2010 and wondering if there's some incompatibility.  if the user reboots his iPhone then they'll be able to access the GAL post reboot, but they'll run into this issue a couple days later....Any ideas as to what's causing this??
    Thanks

    for sure.
    have a look at the file called lookup_fs.html
    (its under server_root/html/yourpreferredlanguage/
    around line 27 you can see some (commented) JavaScript tags which enalbes you to add additional directories.
    Peter

  • Xorg failing ("symbol lookup error")

    Hi,
    since my last upgrade I'm unable to start Xorg properly. I'm getting this, although this message doesn't appear in /var/log/Xorg.0.log.
    X.Org X Server 1.4.2
    Release Date: 11 June 2008
    (II) Module "ddc" already built-in
    /usr/bin/Xorg: symbol lookup error: /usr/lib/xorg/modules/drivers//vesa_
    Any hints? Thank you.

    I am getting the same.  Here is the detailed error:
    (==) Using config file: "/etc/X11/xorg.conf"
    (II) Module "ddc" already built-in
    /usr/bin/xorg: symbol lookup error: /usr/lib/xorg/modules/drivers//vesa_drv.so: undefined symbol: xf86GTFMode
    The only thing I noticed in the log file is:
    (WW) VESA(0): Unable to estimate virtual size
    I can't get to the CLI...

  • After Lion Upgrade, nslookup fails (cannot lookup DNS names)

    Hi, I upgraded to Lion yesterday, which worked fine.
    Everything looks good except DNS lookup. This is essential for anything. So no Webbrowsing, no Apple Store, nothing.
    When I run "nslookup google.com" it sais host not found.
    When I run:
    nslookup
    > server 8.8.8.8 (or any DNS Server)
    www.google.com
    there is also no result.
    Pinging any Internet IP like 8.8.8.8 works like a charm.
    I had Sophos Antivirus installed. Uninstalling did not help.
    When running "Lion Recovery" (press Command and R while booting) there is Safari. Web browsing are working, so nslookup is ok in Recovery mode and i have proof that the internet link and the ISP nameservers are ok.
    Any Ideas? I'm clueless....
    Thanks
    Simon

    Tried with different WAP and they all work fine except the one I have at home. Seems to be a problem between the new Mountain Lion drivers of my Airport card MBP model A1229 and the ZTE H220N wireless router.

Maybe you are looking for