Servlet failed to load on startup
Hi all,
I recently added a new servlet definition to my web.xml file, and specified a <load-on-startup> value of 1 for this servlet. Even though this works and the new servlet gets initialised properly, one of my old servlets with a <load-on-startup> value of 2 has stopped working. There were no changes to this old servlet, and it was working fine before. I get the following error from the weblogic logs. I have tried swapping the load order around but that doesn't make any difference. Any suggestions as to why this could happen?
Thanks in advance
<Nov 14, 2005 1:34:59 PM SGT> <Error> <HTTP> <BEA-101216> <Servlet: "action" failed to preload on startup in Web application: "/".
javax.servlet.ServletException
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:884)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:848)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:787)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3260)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3205)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3182)
at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:5663)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:869)
at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2022)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2063)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2592)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2515)
at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2317)
at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:608)
at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
I am running into the same error. Has anyone been able to find a solution?
thanks.
Similar Messages
-
Struts servlet failed to load on application startup
I am having problems deploying a struts application on WebLogic 8.1 SP3. I get the following error on startup.
Call com.manu.cro.online.ui.KarmaActionServlet.addMapping(ActionMapping[path=/routingPost, type=com.manu.cro.online.ui.routing.RoutingPostAction])
Pop org.apache.struts.action.ActionMapping
register('-//Apache Software Foundation//DTD Struts Configuration 1.0//EN', 'jar:file:/C:/CVS_Source/NCRO/lib/GUI/struts.jar!/org/apache/struts/resources/struts-config_1_0.dtd'
register('-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN', 'jar:file:/C:/CVS_Source/NCRO/lib/GUI/struts.jar!/org/apache/struts/resources/web-app_2_2.dtd'
register('-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN', 'jar:file:/C:/CVS_Source/NCRO/lib/GUI/struts.jar!/org/apache/struts/resources/web-app_2_3.dtd'
resolveEntity('-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN', 'http://java.sun.com/j2ee/dtds/web-app_2_2.dtd')
Resolving to alternate DTD 'jar:file:/C:/CVS_Source/NCRO/lib/GUI/struts.jar!/org/apache/struts/resources/web-app_2_2.dtd'
Call com.manu.cro.online.ui.KarmaActionServlet.addServletMapping(action/java.lang.String,*.do/java.lang.String)
<Jul 18, 2007 9:13:39 AM EDT> <Error> <HTTP> <BEA-101216> <Servlet: "action" failed to preload on startup in Web application: "cro".
javax.servlet.ServletException
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:909)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:873)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:812)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3281)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3226)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3207)
at weblogic.servlet.internal.HttpServer.preloadResources(HttpServer.java:694)
at weblogic.servlet.internal.WebService.preloadResources(WebService.java:483)
at weblogic.servlet.internal.ServletInitService.resume(ServletInitService.java:30)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
Any reason why my action servlet is not loading? Any help will be appreciated.
My web.xml file looks like the following:
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/j2ee/dtd/web-app_2_3.dtd">
<web-app>
<!-- Action Servlet Configuration -->
<servlet>
<servlet-name>action</servlet-name>
<servlet-class>com.manu.cro.online.ui.KarmaActionServlet</servlet-class>
<init-param>
<param-name>application</param-name>
<param-value>com.manu.cro.online.ApplicationResources</param-value>
</init-param>
<init-param>
<param-name>config</param-name>
<param-value>/WEB-INF/struts-config.xml</param-value>
</init-param>
<init-param>
<param-name>debug</param-name>
<param-value>2</param-value>
</init-param>
<init-param>
<param-name>detail</param-name>
<param-value>2</param-value>
</init-param>
<init-param>
<param-name>validate</param-name>
<param-value>true</param-value>
</init-param>
<load-on-startup>2</load-on-startup>
</servlet>
<!-- Action Servlet Mapping -->
<servlet-mapping>
<servlet-name>action</servlet-name>
<url-pattern>*.do</url-pattern>
</servlet-mapping>
<!-- The Usual Welcome File List -->
<welcome-file-list>
<welcome-file>jsp/online/Logon.jsp</welcome-file>
</welcome-file-list>
<!-- Struts Tag Library Descriptors -->
<taglib>
<taglib-uri>/WEB-INF/struts-bean.tld</taglib-uri>
<taglib-location>/WEB-INF/struts-bean.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/WEB-INF/struts-html.tld</taglib-uri>
<taglib-location>/WEB-INF/struts-html.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/WEB-INF/struts-logic.tld</taglib-uri>
<taglib-location>/WEB-INF/struts-logic.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/WEB-INF/struts-template.tld</taglib-uri>
<taglib-location>/WEB-INF/struts-template.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/WEB-INF/croUtils.tld</taglib-uri>
<taglib-location>/WEB-INF/croUtils.tld</taglib-location>
</taglib>
</web-app>
Thanks.
gtataThis problem has been resolved. It was a classpath issue.
-
**SOLUTION** DLLML.exe Fails to load at startup (application error)
Hello everyone!
I purchased the SB X-Fi Fatalty Champion Edition soon after release, and think this is the best card I have ever used to date. Absolutely love it, unbelievable sound.
Now a year or two ago I noticed a certain file failing to load when I started windows.
This file, DLLML.exe. To my understanding this file is used to load EAX emulation support into older games/modules (essential loads a "middle-man" file between the game's sound files/.dll's, and the hardware SPU [Sound Processing Unit, not a real acronym, but that's what I call it since GPU and CPU are similar distincti've acronyms so if you see it used anywhere, it came from me ] to allow EAX support in non-EAX enabled games), and/or to add EAX effects in your audio files using the Wave Studio app.
I've pinpointed this issue to either a Windows Update, or the Creative auto-update (which could mean it is an error caused by an installaion combination of multiple apps at once) because this issue did not arise until I did these two things (did Windows Update, then Creative Auto-Update, then restarted computer).
Now I've primarily had this issue with Windows XP x64 but I have had this issue at times with Windows XP x86 as well.
After you install the software suite, it adds an entry in your Windows Startup to load the module (Start/Run. msconfig. Startup tab. Look for STARTUP ITEM: DLLML). The entry looks like this:
WinXPx86 looks like: "C:\Program Files\Creative\Shared Files\Module Loader\DLLML.exe" RCSystem * -Startup
WinXPx64 looks like: "C:\Program Files (x86)\Creative\Shared Files\Module Loader\DLLML.exe" RCSystem * -Startup
Under most circumstances this module loads fine, but because Creative, for reasons why I have not delved into, loads some of their DLL files differently than the Windows standard, which may also be a cause of this issue (extremely unlikely, I believe it is one of the 2 things i mentioned above).
Either way, after I did those 2 things, the DLLML.exe startup entry failed to load every time.
But I fixed it.
Now what you have to do to resolve this issue, involves editing the startup entry in the Windows Registry.
If you are scared to go into it, have no idea what I am talking about, or never edited the Registry before, don't worry. If you follow these steps EXACTLY, you have nothing to fear.
I will be using default installation parameters for file pathing, so if your Operating System is installed in a different dri've letter other than C:\, then just change the letter to the one your OS is installed onto.
Capitals used for emphesis on actions to take:
-Hit the START button, then select RUN
--------If RUN is not in your start menu, you need to enable it by right-clicking and open area of your TASKBAR, select PROPERTIES. --------Click the START MENU tab, then the CUSTOMIZE button. Click the ADVANCED tab. In the START MENU ITEMS box, scroll down to the entry that says SHOW RUN. Check the checkbox to fill it. Then OK/APPLY/OK, and you should be back to the desktop. Then go to START/RUN
-type the word REGEDIT
--------This opens the Windows Registry.
--------DO NOT change ANYTHING in this other than the exact directions I specify or you may corrupt your registry or even worse, corrupt your system, which means F&R time (Format & Reinstall). Treat it like a stripper. You can look all you want but don't touch or there could be dire consequences.
--------Now the fastest way to find this is to manually navigate to the specific "key" or "entry" you need to modify. Mouse-click the +'s to navitage further into the "hi've" following these maps:
-FOR WINDOWS XP x86 USERS NAVIGATE TO: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Run
-FOR WINDOWS XP x64 USERS NAVITAGE TO: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432\Microsoft\Wind ows\CurrentVersion\Run
--------Now you are looking for a specific entry NAME called RCSYSTEM. Depending on which version you are running. They are:
-FOR WINDOWS XP x86 USERS: "C:\Program Files\Creative\Shared Files\Module Loader\DLLML.exe" RCSystem * -Startup
-FOR WINDOWS XP x64 USERS: "C:\Program Files (x86)\Creative\Shared Files\Module Loader\DLLML.exe" RCSystem * -Startup
-------Now we are going to edit the entry. What we need to do is get rid of that * (asterix) character in the name. I don't know why it is there, I'm thinking it may be a coding error. But in my WinXPx64, this was the culprit.
-Double-click the RCSYSTEM key to edit it, and edit it so it looks EXACTLY LIKE THIS (If you're paranoid about doing something bad, COPY and PASTE this line pertaining to your installed OS. KEEP IN MIND THE INSTALLATION DRIVE LETTER, CHANGE FIRST LETTER IF NESCESSARY)
-FOR WINDOWS XP x86 USERS: "C:\Program Files\Creative\Shared Files\Module Loader\DLLML.exe" RCSystem -Startup
-FOR WINDOWS XP x64 USERS: "C:\Program Files (x86)\Creative\Shared Files\Module Loader\DLLML.exe" RCSystem -Startup
-click OK button. Now it is changed.
-------And we're DONE EDITING the Registry entry!
-now go to FILE in the top-left menu, then select EXIT
-RESTART your computer
-------You should not receive the "DLLML.exe failed to load" (application error) again!!
To check to see if it loaded into your system properly (as if not getting the error message anymore was proof enough it loaded properly), when you reboot back to the desktop, do the "three-fingered salute" (ctrl-alt-delete), then select the PROCESSES tab. Click on the IMAGE NAME heading to sort it alphabetically, and look for the name (WinXPx86) DLLML.exe or (WinXPx64) DLLML.exe *32.
If you see it listed, it loaded!! CONGRATS, IT BE FIXED!!
If this did not work for you, then your system is posessed, get a priest. I don't think a witchdoctor would give your comp good vibes O_o
Hope this resolved it for you. Enjoy your EAX with Duke Nukem 3d again!
EDIT: As a side note, I also noticed that since after this fix, my computer doesn't hang after sending the restart/shutdown killsignal, so I am wondering with people having similar hanging issues, if their issue could be resolved something similar to this.
Just a thought for any admins/mods/users out there that know what they are doing that maybe wanna test that out.
Sincerely,
Jason Ostapyk
3yr degree, MCP, CCNA, A+ certified, Specialised Electrician Class M LicensedG Kudos for a brilliant finding! After a Windows Hotfix on my XP SP3, when shutting down my PC I would wait for a program and then get an error that EAX was not responding before finally shutting down. On next reboot I lost sound on my PC. After running tests, the Direct Sound test failed pointing at EAX.
This solution cured the problem. Again, kudos, job really well done!!! -
Servlet Failed to preload on Startup - WebLogic 8.1
Hi there,
I am getting the following error message when I start up my application in WebLogic.
(see below my post for execat error). I only get this when I try to run my application
as a .WAR file. If I expand the .war file and run it that way, everything works
just like it should. What is going on with it? How can I fix it?
Thanks for your help.
Joseph
####<May 10, 2004 1:48:15 PM EDT> <Error> <HTTP> <--HOSTNAME REMOVED--> <jbajin-adm>
<ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-101216>
<Servlet: "dbfrontload" failed to preload on startup in Web application: "pricing".
javax.servlet.ServletException
at weblogic.servlet.internal.ServletStubImpl.createServlet()Ljavax.servlet.Servlet;(ServletStubImpl.java:884)
at weblogic.servlet.internal.ServletStubImpl.createInstances()V(ServletStubImpl.java:848)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(Lweblogic.servlet.internal.RequestCallback;)V(ServletStubImpl.java:787)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(Ljava.lang.String;)V(WebAppServletContext.java:3252)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets()V(WebAppServletContext.java:3197)
at weblogic.servlet.internal.WebAppServletContext.preloadResources()V(WebAppServletContext.java:3174)
at weblogic.servlet.internal.WebAppServletContext.setStarted(Z)V(WebAppServletContext.java:5647)
at weblogic.servlet.internal.WebAppModule.start()V(WebAppModule.java:869)
at weblogic.j2ee.J2EEApplicationContainer.start([Lweblogic.j2ee.J2EEApplicationContainer$Component;)V(J2EEApplicationContainer.java:2022)
at weblogic.j2ee.J2EEApplicationContainer.activate([Lweblogic.management.configuration.ComponentMBean;)V(J2EEApplicationContainer.java:2063)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer()V(SlaveDeployer.java:2592)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit()V(SlaveDeployer.java:2515)
at weblogic.management.deploy.slave.SlaveDeployer$Task.commit()V(SlaveDeployer.java:2317)
at weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit()V(SlaveDeployer.java:2399)
at weblogic.management.deploy.slave.SlaveDeployer$Task.prepare()V(SlaveDeployer.java:2311)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2479)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:798)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;Z)Z(SlaveDeployer.java:507)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:465)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(Optimized
Method)
at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:170)
at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)Hi Rob,
I found you are helping others and familiar with deployment problems. I am also
struggling to resolve deployment problem on Weblogic 8.1sp2. I hope you can help
on this, here is the problem I am facing while deploying my web application.
<27-May-2004 12:00:49 o'clock BST> <Error> <HTTP> <BEA-101216> <Servlet: "action
tion: "site20pub".
javax.servlet.ServletException: org/apache/xerces/parsers/SAXParser
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubIm
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStub
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubI
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppS
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebApp
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAp
at weblogic.servlet.internal.HttpServer.preloadResources(HttpServer.java
at weblogic.servlet.internal.WebService.preloadResources(WebService.java
at weblogic.servlet.internal.ServletInitService.resume(ServletInitServic
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
at weblogic.Server.main(Server.java:32)
any help on this very much appreciated.
Thanks
Ranga
Rob Woollen <[email protected]> wrote:
It looks like your servlet's constructor or init method is throwing an
exception.
Are you perhaps using getRealPath in one of those methods? That will
return Null when you're archived, but the path when you're exploded.
-- Rob
Joseph Bajin wrote:
Hi there,
I am getting the following error message when I start up my applicationin WebLogic.
(see below my post for execat error). I only get this when I try torun my application
as a .WAR file. If I expand the .war file and run it that way, everythingworks
just like it should. What is going on with it? How can I fix it?
Thanks for your help.
Joseph
####<May 10, 2004 1:48:15 PM EDT> <Error> <HTTP> <--HOSTNAME REMOVED--><jbajin-adm>
<ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>><> <BEA-101216>
<Servlet: "dbfrontload" failed to preload on startup in Web application:"pricing".
javax.servlet.ServletException
at weblogic.servlet.internal.ServletStubImpl.createServlet()Ljavax.servlet.Servlet;(ServletStubImpl.java:884)
at weblogic.servlet.internal.ServletStubImpl.createInstances()V(ServletStubImpl.java:848)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(Lweblogic.servlet.internal.RequestCallback;)V(ServletStubImpl.java:787)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(Ljava.lang.String;)V(WebAppServletContext.java:3252)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets()V(WebAppServletContext.java:3197)
at weblogic.servlet.internal.WebAppServletContext.preloadResources()V(WebAppServletContext.java:3174)
at weblogic.servlet.internal.WebAppServletContext.setStarted(Z)V(WebAppServletContext.java:5647)
at weblogic.servlet.internal.WebAppModule.start()V(WebAppModule.java:869)
at weblogic.j2ee.J2EEApplicationContainer.start([Lweblogic.j2ee.J2EEApplicationContainer$Component;)V(J2EEApplicationContainer.java:2022)
at weblogic.j2ee.J2EEApplicationContainer.activate([Lweblogic.management.configuration.ComponentMBean;)V(J2EEApplicationContainer.java:2063)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer()V(SlaveDeployer.java:2592)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit()V(SlaveDeployer.java:2515)
at weblogic.management.deploy.slave.SlaveDeployer$Task.commit()V(SlaveDeployer.java:2317)
at weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit()V(SlaveDeployer.java:2399)
at weblogic.management.deploy.slave.SlaveDeployer$Task.prepare()V(SlaveDeployer.java:2311)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2479)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:798)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;Z)Z(SlaveDeployer.java:507)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:465)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(Optimized
Method)
at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:170)
at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(UnknownSource) -
Servlet failed to preload on startup
Hi,
I have installed and configured weblogic portal 8.1.6 and when i tried to start the server i am getting the following exceptions.
1. <Error> <HTTP> <BEA-101216> <Servlet: "AppManagerServlet" failed to preload on startup in Web application: "mit".
javax.servlet.ServletException: FRAMEWORK
2. <Error> <HTTP> <BEA-101216> <Servlet: "PortletServlet" failed to preload on startup in Web application: "mit".
javax.servlet.ServletException: com/bea/p13n/cache/internal/system/CacheConfig
etc.
Before this new version i was using weblogic Portal 8.1.3.
Please help me to solve this issue.Hi,
I have installed and configured weblogic portal 8.1.6 and when i tried to start the server i am getting the following exceptions.
1. <Error> <HTTP> <BEA-101216> <Servlet: "AppManagerServlet" failed to preload on startup in Web application: "mit".
javax.servlet.ServletException: FRAMEWORK
2. <Error> <HTTP> <BEA-101216> <Servlet: "PortletServlet" failed to preload on startup in Web application: "mit".
javax.servlet.ServletException: com/bea/p13n/cache/internal/system/CacheConfig
etc.
Before this new version i was using weblogic Portal 8.1.3.
Please help me to solve this issue. -
Active protection system fails to load on startup
I'm using a T 60 for over one year. Recently noticed missing icon after startup. Checked problem reports, noticed item stating compatibility problem. I am able to run tpshocks.exe to load program. I tried to reinstall hprotect from lenovo download site, but still doesn't load on startup. Stumped. Does anyone have any ideas. Is there a way to change compatibility mode for this app?
Thanks.AD,
If you are using Weblogic 10.3.4 then it's a bug - odiconsole throws that error. There is no issue with weblogic 10.3.3. Try with Weblogic 10.3.3 it works for us.
Regards,
Henry. -
Servlet does not load on startup
Hi Guys,
I'm tryin to load a servlet on startup ..
Tryin to follow what the doc say but i get this error
in the server logs which means that the servlet is not found
Any help wud be greatly appritiated ...
thanx
what the logs say >>>
Fri Apr 28 11:52:51 PDT 2000:<I> <WebLogicServer> Invoking T3StartupDef
StartConfigServlet weblogic.servlet.utils.ServletStartup with
{servlet=ConfigServlet}
Fri Apr 28 11:52:51 PDT 2000:<I> <WebLogicServer> T3StartupDef
StartConfigServlet weblogic.servlet.utils.ServletStartup
reports:servlet: ConfigServlet not found
Fri Apr 28 11:52:51 PDT 2000:<I> <SSLListenThread> Listening on port:
7002
Fri Apr 28 11:52:51 PDT 2000:<I> <ListenThread> Listening on port: 7001
my server configuration>>>>
weblogic.httpd.register.ConfigServlet=com.fourcharity.servlet.ConfigServlet
# Set initArgs
weblogic.httpd.initArgs.ConfigServlet=\
servletHost=10.10.10.126:7001,\
smtpHost=4charity.com,\
[email protected],\
fclogourl=http://www.4charity.com/img/donate/4c_logo.gif
# Configure the ServletStartup class to run ConfigServlet's init()
# method at startup
weblogic.system.startupClass.StartConfigServlet=weblogic.servlet.utils.ServletStartup
weblogic.system.startupArgs.StartConfigServlet=servlet=com.fourcharity.servlet.ConfigServlet
regards sanjay
www.eBusinessDesign.com
3475 Granada Ave, Apt# 319,Santa Clara, CA-95051
(1-415-2671363(o) 1-408-2492716(r) 1-877-8993286(fax))
Thanks for the reply. However, the final product is to run in Solaris,
so there should not be a problem. Thanks anyway.
Regards,
Baivab
Mettu Kumar <[email protected]> wrote:
>what problems are you facing with sp8.
>
>Baivab Mitra wrote:
>
>> Hi All!!
>>
>> Thanks beforehand for all help received to this query
>beforehand.
>>
>> We are using WL5.1 on WinNT, with SP6. Unfortunately,
>we have followed
>> all instructions as in the docs. and tried to load the
>servlet
>> on WL startup automatically. It does not work!! Checking
>the Internet,
>> we came to know the SP8 is required. Installed SP8 and
>again tried.
>> Now -- the EJBs are giving problems -- deployment.
>>
>> Please -- is there anyone who can suggest remidies to
>this? BETTER
>> if we could stick to SP6 and NOT switch to SP8.
>>
>> Thanks,
>>
>> Baivab
>
-
WLS8.1 & JSF 1.0 Final: "Faces Servlet" failed to preload
Ok, this i what I've done. Modified the samples proprties file so everythings gets build without problems with the 1.0.x taglib.
<copy todir="${build}/${example}/WEB-INF/lib" file="${jstl.jar}"/>
<copy todir="${build}/${example}/WEB-INF/lib" file="${standard.jar}"/>
<copy todir="${build}/${example}/WEB-INF/lib" file="/jakarta-taglibs-standard-1.0.5/lib/jaxen-full.jar"/>
<copy todir="${build}/${example}/WEB-INF/lib" file="/jakarta-taglibs-standard-1.0.5/lib/saxpath.jar"/>
The jst.jar, standard.jar also point to /jakarta-taglibs-standard-1.0.5/lib
I updated the web.xml for the listener
<listener>
<listener-class>com.sun.faces.config.ConfigureListener</listener-class>
</listener>
ant the web.cml validated against http://java.sun.com/dtd/web-app_2_3.dtd
If I deploy the cardemo I see:
<5/03/2004 10:28:30 PM CET> <Error> <HTTP> <BEA-101216> <Servlet: "Faces Servlet" failed to preload on startup in Web application: "jsf-cardemo".
javax.servlet.ServletException
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:884)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:848)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:787)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3252)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3197)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3174)
at weblogic.servlet.internal.HttpServer.preloadResources(HttpServer.java:688)
at weblogic.servlet.internal.WebService.preloadResources(WebService.java:483)
at weblogic.servlet.internal.ServletInitService.resume(ServletInitService.java:30)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
at weblogic.Server.main(Server.java:32)
>
5/03/2004 22:28:32 com.sun.faces.config.rules.NavigationRuleRule end
WARNING: [NavigationRuleRule]{faces-config/navigation-rule} Merge(/confirmChoices.jsp)
What am I still missing here? I really want to start using JSF!
Regards,
PeterI believe I have found the issue to the problem. The issue seems to be Weblogic is not respecting part of the Servlet 2.3 spec. It states that all ServletContextListener implementations should be called before the Servlet's init method is called. Tomcat respects this and that's why JSF works when deployed in Tomcat. Weblogic 8.1 calls this instance AFTER the Servlet's init's methods are called. This results in a NullPointerException being thrown.
You can see how the ordering changes between Weblogic and Tomcat for yourself by editing the log4j.properties file and add the following:
log4j.category.com.sun.faces.config = DEBUG, config log4j.additivity.com.sun.faces.config=false
log4j.appender.config = org.apache.log4j.ConsoleAppender log4j.appender.config.layout = org.apache.log4j.PatternLayout log4j.appender.config.layout.ConversionPattern = ...
Deploy the example application to both Weblogic and Tomcat and observe the order.
I've developed a work around for this issue. Weblogic seems to respect the <load-on-startup> element in the web.xml file. I have written a Servlet which manually loads the ServletContextListener for JSF. The code below:
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
import javax.faces.FactoryFinder;
import javax.faces.lifecycle.LifecycleFactory;
import javax.servlet.ServletConfig;
import javax.servlet.ServletContextEvent;
import javax.servlet.ServletContextListener;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
public class WeblogicHackServlet extends HttpServlet {
public static final String CONFIGURE_LISTENER_KEY = "CONFIGURE_LISTENER"; public static final transient Log logger = LogFactory.getLog(WeblogicHackServlet.class);
public void init(ServletConfig servletConfig) throws ServletException {
LifecycleFactory factory =(LifecycleFactory)
FactoryFinder.getFactory(FactoryFinder.LIFECYCLE_FACTORY);
if (factory != null)
return;
String className = servletConfig.getInitParameter(CONFIGURE_LISTENER_KEY);
if (className == null) {
logger.fatal("Did not find the init parameter " + CONFIGURE_LISTENER_KEY);
return;
try {
Class aClass = Class.forName(className);
ServletContextListener listener = (ServletContextListener)
aClass.newInstance();
listener.contextInitialized(
new ServletContextEvent(servletConfig.getServletContext()));
} catch (Exception e) {
logger.fatal("The ConfigureListener could not be triggered", e);
The web.xml file also needs to be changed to the following:
<servlet>
<servlet-name>WeblogicHackServlet</servlet-name>
<servlet-class>WeblogicHackServlet</servlet-class>
<init-param>
<param-name>CONFIGURE_LISTENER</param-name>
<param-value>com.sun.faces.config.ConfigureListener</param-value>
</init-param>
<load-on-startup> 1 </load-on-startup>
</servlet>
<servlet>
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup> 2 </load-on-startup>
</servlet>
This causes JSF to load properly. Hopefully, BEA can resolve this issue so my hack can be removed.
Thanks,
Louis Calisi
Applications Architect -
[HTTP:101216]Servlet: "jersey" failed to preload on startup in Web application:"
Hi,
i'm trying to deplay a restful webservice on a WL 10.3 with jdeveloper. As soon as i try to deploy my webservice i'm getting the follwing error :
weblogic.application.ModuleException: [HTTP:101216]Servlet: "jersey" failed to preload on startup in Web application: "name.war".
com.sun.jersey.spi.inject.Errors$ErrorMessagesException
at com.sun.jersey.spi.inject.Errors.processErrorMessages(Errors.java:170)
at com.sun.jersey.spi.inject.Errors.postProcess(Errors.java:137)
at com.sun.jersey.spi.inject.Errors.processWithErrors(Errors.java:203)
at com.sun.jersey.server.impl.application.WebApplicationImpl.initiate(WebApplicationImpl.java:702)
at com.sun.jersey.server.impl.application.WebApplicationImpl.initiate(WebApplicationImpl.java:691)
at com.sun.jersey.spi.container.servlet.ServletContainer.initiate(ServletContainer.java:438)
at com.sun.jersey.spi.container.servlet.ServletContainer$InternalWebComponent.initiate(ServletContainer.java:288)
at com.sun.jersey.spi.container.servlet.WebComponent.load(WebComponent.java:587)
at com.sun.jersey.spi.container.servlet.WebComponent.init(WebComponent.java:213)
at com.sun.jersey.spi.container.servlet.ServletContainer.init(ServletContainer.java:343)
at com.sun.jersey.spi.container.servlet.ServletContainer.init(ServletContainer.java:542)
at javax.servlet.GenericServlet.init(GenericServlet.java:242)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3154)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:54)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:54)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:637)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:54)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:164)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:69)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
:com.sun.jersey.spi.inject.Errors.ErrorMessagesException:null
What do i have to do to make it work?
Best regards.Did you deploy and target the jersey libraries to your server (these can (usually) be found in the ${WL_HOME}/common/deployable-libraries). Deploy these as shared libraries and then reference it by using the following in the weblogic.xml file:
<library-ref>
<library-name>jersey-bundle</library-name>
<specification-version>1.1.1</specification-version>
<implementation-version>1.1.5.1</implementation-version>
</library-ref>
<library-ref>
<library-name>jsr311-api</library-name>
<specification-version>1.1.1</specification-version>
<implementation-version>1.1.1</implementation-version>
</library-ref>
Version can differ in your case (you have to check this when the libraries are deployed). -
Servlet: "XYZ" failed to preload on startup in Web application
Hi,
When i deploying the WAR(serviceregistry.war) in weblogic 9.2,i am getting following errors,
[HTTP:101216]Servlet: "BasicServlet" failed to preload on startup in Web application:
"serviceregistry.war". java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:396) at
java.util.Properties.setProperty(Properties.java:128) at java.lang.System.setProperty(System.java:700) at
com.ssc.faw.controller.BasicServlet.init(BasicServlet.java:30) at
weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:276) at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at
weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:68) at
weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58) at
weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48) at
weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:504) at
weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1698) at
weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1675) at
weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1595) at
weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2734) at
weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:892) at
weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:336) at
weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at
weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at
weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) at
weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117) at
weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at
weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at
weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26) at
weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:641) at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at
weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:229) at
weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154) at
weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80) at
weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:565) at
weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104) at
weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:128) at
weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320) at
weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:815) at
weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1222) at
weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:433) at
weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161) at
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback
(DeploymentReceiverCallbackDeliverer.java:181) at
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100
(DeploymentReceiverCallbackDeliverer.java:12) at
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run
(DeploymentReceiverCallbackDeliverer.java:67) at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run
(ServerWorkManagerImpl.java:518) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at
weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Please give me some solutions
Regards,
Tamilvanan.GHi 835570,
As per Rene, the failed init process is due to the NulllPointerException. A NullPointerException is to be expected when JDK HashTable data structure is receiving a null object value for the put() operation.
Recommendations #1
- Look and review your application code >> com.ssc.faw.controller.BasicServlet.init(BasicServlet.java:30).
I can see that you are trying to initialize a java.util.Properties but you are passing a null value to the Properties Object at line 30 of your Servlet. You need to understand why.
Solution:
- Understand why you are attemtping to pass a null value to your Properties object and fix the problem
- Add try{}catch{} block along with proper logging within your custom Servlet code to gracefully handle and log any Unexpected NulllPointerException and prevent such Exception to completely abort your Servlet loading process.
Regards
P-H
http://javaeesupportpatterns.blogspot.com/
Edited by: PHCharbonneau on 12-Feb-2011 5:39 AM
Edited by: PHCharbonneau on 12-Feb-2011 5:39 AM -
[SOLVED] XOrg fails to load Nvidia driver on startup
Hi,
I'm having a fairly strange issue where XOrg is failing to load my driver when I start up my laptop. I'm using kdm, but this is causing it to fail. However, doing a simple
$sudo systemctl restart kdm
works, and everything starts up fine. When kdm is in the failed state, I see this:
$sudo systemctl status kdm
● kdm.service - K Display Manager
Loaded: loaded (/usr/lib/systemd/system/kdm.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2014-12-19 18:47:26 EST; 41s ago
Main PID: 247 (kdm)
CGroup: /system.slice/kdm.service
└─247 /usr/bin/kdm -nodaemon
Dec 19 18:47:26 laptop systemd[1]: Started K Display Manager.
Dec 19 18:47:27 laptop kdm[247]: X server died during startup
Dec 19 18:47:27 laptop kdm[247]: X server for display :0 cannot be started, session disabled
And in my XOrg log, I see:
[ 3.639]
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
[ 3.639]
X.Org X Server 1.16.2.901 (1.16.3 RC 1)
Release Date: 2014-12-09
[ 3.639] X Protocol Version 11, Revision 0
[ 3.639] Build Operating System: Linux 3.17.2-1-ARCH x86_64
[ 3.639] Current Operating System: Linux laptop 3.17.6-1-ARCH #1 SMP PREEMPT Sun Dec 7 23:43:32 UTC 2014 x86_64
[ 3.639] Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/sda1 rw initrd=../initramfs-linux.img
[ 3.639] Build Date: 10 December 2014 02:34:24PM
[ 3.639]
[ 3.639] Current version of pixman: 0.32.6
[ 3.639] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 3.639] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 3.639] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Dec 19 18:47:26 2014
[ 3.645] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 3.649] (==) No Layout section. Using the first Screen section.
[ 3.649] (==) No screen section available. Using defaults.
[ 3.649] (**) |-->Screen "Default Screen Section" (0)
[ 3.649] (**) | |-->Monitor "<default monitor>"
[ 3.650] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 3.650] (==) Automatically adding devices
[ 3.650] (==) Automatically enabling devices
[ 3.650] (==) Automatically adding GPU devices
[ 3.658] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 3.658] Entry deleted from font path.
[ 3.659] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 3.659] Entry deleted from font path.
[ 3.659] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 3.660] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 3.660] Entry deleted from font path.
[ 3.660] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 3.660] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 3.660] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 3.660] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 3.660] (II) Loader magic: 0x818d80
[ 3.660] (II) Module ABI versions:
[ 3.660] X.Org ANSI C Emulation: 0.4
[ 3.660] X.Org Video Driver: 18.0
[ 3.660] X.Org XInput driver : 21.0
[ 3.660] X.Org Server Extension : 8.0
[ 3.662] (EE) systemd-logind: failed to get session: PID 267 does not belong to any known session
[ 3.663] (--) PCI:*(0:1:0:0) 10de:11a1:1558:0371 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 3.663] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 3.664] (II) LoadModule: "glx"
[ 3.675] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 3.767] (II) Module glx: vendor="NVIDIA Corporation"
[ 3.767] compiled for 4.0.2, module version = 1.0.0
[ 3.767] Module class: X.Org Server Extension
[ 3.768] (II) NVIDIA GLX Module 343.36 Mon Dec 1 15:50:02 PST 2014
[ 3.769] (==) Matched nouveau as autoconfigured driver 0
[ 3.769] (==) Matched nv as autoconfigured driver 1
[ 3.769] (==) Matched modesetting as autoconfigured driver 2
[ 3.769] (==) Matched fbdev as autoconfigured driver 3
[ 3.769] (==) Matched vesa as autoconfigured driver 4
[ 3.769] (==) Assigned the driver to the xf86ConfigLayout
[ 3.769] (II) LoadModule: "nouveau"
[ 3.769] (WW) Warning, couldn't open module nouveau
[ 3.769] (II) UnloadModule: "nouveau"
[ 3.769] (II) Unloading nouveau
[ 3.769] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 3.769] (II) LoadModule: "nv"
[ 3.769] (WW) Warning, couldn't open module nv
[ 3.769] (II) UnloadModule: "nv"
[ 3.769] (II) Unloading nv
[ 3.769] (EE) Failed to load module "nv" (module does not exist, 0)
[ 3.769] (II) LoadModule: "modesetting"
[ 3.769] (WW) Warning, couldn't open module modesetting
[ 3.769] (II) UnloadModule: "modesetting"
[ 3.769] (II) Unloading modesetting
[ 3.769] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 3.769] (II) LoadModule: "fbdev"
[ 3.769] (WW) Warning, couldn't open module fbdev
[ 3.769] (II) UnloadModule: "fbdev"
[ 3.769] (II) Unloading fbdev
[ 3.769] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 3.769] (II) LoadModule: "vesa"
[ 3.770] (WW) Warning, couldn't open module vesa
[ 3.770] (II) UnloadModule: "vesa"
[ 3.770] (II) Unloading vesa
[ 3.770] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 3.770] (EE) No drivers available.
[ 3.770] (EE)
Fatal server error:
[ 3.770] (EE) no screens found(EE)
[ 3.770] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 3.770] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 3.770] (EE)
Which looks like it loads my nvidia driver, but then just decides not to use it for some reason... After I restart kdm, it seems to use the driver fine:
[ 78.897]
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
[ 78.897]
X.Org X Server 1.16.2.901 (1.16.3 RC 1)
Release Date: 2014-12-09
[ 78.897] X Protocol Version 11, Revision 0
[ 78.897] Build Operating System: Linux 3.17.2-1-ARCH x86_64
[ 78.897] Current Operating System: Linux laptop 3.17.6-1-ARCH #1 SMP PREEMPT Sun Dec 7 23:43:32 UTC 2014 x86_64
[ 78.897] Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/sda1 rw initrd=../initramfs-linux.img
[ 78.897] Build Date: 10 December 2014 02:34:24PM
[ 78.897]
[ 78.897] Current version of pixman: 0.32.6
[ 78.897] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 78.897] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 78.897] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Dec 19 18:48:38 2014
[ 78.897] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 78.897] (==) No Layout section. Using the first Screen section.
[ 78.897] (==) No screen section available. Using defaults.
[ 78.897] (**) |-->Screen "Default Screen Section" (0)
[ 78.897] (**) | |-->Monitor "<default monitor>"
[ 78.898] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 78.898] (==) Automatically adding devices
[ 78.898] (==) Automatically enabling devices
[ 78.898] (==) Automatically adding GPU devices
[ 78.898] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 78.898] Entry deleted from font path.
[ 78.898] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 78.898] Entry deleted from font path.
[ 78.898] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 78.898] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 78.898] Entry deleted from font path.
[ 78.898] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 78.898] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 78.898] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 78.898] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 78.898] (II) Loader magic: 0x818d80
[ 78.898] (II) Module ABI versions:
[ 78.898] X.Org ANSI C Emulation: 0.4
[ 78.898] X.Org Video Driver: 18.0
[ 78.898] X.Org XInput driver : 21.0
[ 78.898] X.Org Server Extension : 8.0
[ 78.900] (EE) systemd-logind: failed to get session: PID 542 does not belong to any known session
[ 78.900] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 78.901] (--) PCI:*(0:1:0:0) 10de:11a1:1558:0371 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 78.901] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 78.901] (II) LoadModule: "glx"
[ 78.902] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 78.913] (II) Module glx: vendor="NVIDIA Corporation"
[ 78.913] compiled for 4.0.2, module version = 1.0.0
[ 78.913] Module class: X.Org Server Extension
[ 78.913] (II) NVIDIA GLX Module 343.36 Mon Dec 1 15:50:02 PST 2014
[ 78.914] (II) Applying OutputClass "nvidia" to /dev/dri/card0
[ 78.914] loading driver: nvidia
[ 78.914] (==) Matched nvidia as autoconfigured driver 0
[ 78.914] (==) Matched nouveau as autoconfigured driver 1
[ 78.914] (==) Matched nv as autoconfigured driver 2
[ 78.914] (==) Matched nouveau as autoconfigured driver 3
[ 78.914] (==) Matched nv as autoconfigured driver 4
[ 78.914] (==) Matched modesetting as autoconfigured driver 5
[ 78.914] (==) Matched fbdev as autoconfigured driver 6
[ 78.914] (==) Matched vesa as autoconfigured driver 7
[ 78.914] (==) Assigned the driver to the xf86ConfigLayout
[ 78.914] (II) LoadModule: "nvidia"
[ 78.914] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 78.920] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 78.920] compiled for 4.0.2, module version = 1.0.0
[ 78.920] Module class: X.Org Video Driver
[ 78.920] (II) LoadModule: "nouveau"
[ 78.921] (WW) Warning, couldn't open module nouveau
[ 78.921] (II) UnloadModule: "nouveau"
[ 78.921] (II) Unloading nouveau
[ 78.921] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 78.921] (II) LoadModule: "nv"
[ 78.921] (WW) Warning, couldn't open module nv
[ 78.921] (II) UnloadModule: "nv"
[ 78.921] (II) Unloading nv
[ 78.921] (EE) Failed to load module "nv" (module does not exist, 0)
[ 78.921] (II) LoadModule: "modesetting"
[ 78.921] (WW) Warning, couldn't open module modesetting
[ 78.921] (II) UnloadModule: "modesetting"
[ 78.921] (II) Unloading modesetting
[ 78.921] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 78.921] (II) LoadModule: "fbdev"
[ 78.922] (WW) Warning, couldn't open module fbdev
[ 78.922] (II) UnloadModule: "fbdev"
[ 78.922] (II) Unloading fbdev
[ 78.922] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 78.922] (II) LoadModule: "vesa"
[ 78.922] (WW) Warning, couldn't open module vesa
[ 78.922] (II) UnloadModule: "vesa"
[ 78.922] (II) Unloading vesa
[ 78.922] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 78.922] (II) NVIDIA dlloader X Driver 343.36 Mon Dec 1 15:28:39 PST 2014
[ 78.922] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 78.922] (++) using VT number 7
[ 78.935] (II) Loading sub module "fb"
[ 78.935] (II) LoadModule: "fb"
[ 78.935] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 78.936] (II) Module fb: vendor="X.Org Foundation"
[ 78.936] compiled for 1.16.2.901, module version = 1.0.0
[ 78.936] ABI class: X.Org ANSI C Emulation, version 0.4
[ 78.936] (II) Loading sub module "wfb"
[ 78.936] (II) LoadModule: "wfb"
[ 78.936] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 78.937] (II) Module wfb: vendor="X.Org Foundation"
[ 78.937] compiled for 1.16.2.901, module version = 1.0.0
[ 78.937] ABI class: X.Org ANSI C Emulation, version 0.4
[ 78.937] (II) Loading sub module "ramdac"
[ 78.937] (II) LoadModule: "ramdac"
[ 78.937] (II) Module "ramdac" already built-in
[ 78.939] (II) NVIDIA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 78.939] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 78.939] (==) NVIDIA(0): RGB weight 888
[ 78.939] (==) NVIDIA(0): Default visual is TrueColor
[ 78.939] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 78.940] (**) NVIDIA(0): Enabling 2D acceleration
[ 79.610] (II) NVIDIA(0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 79.610] (II) NVIDIA(0): 3D Vision stereo.
[ 79.610] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20130102)
[ 79.612] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 670MX (GK104) at PCI:1:0:0 (GPU-0)
[ 79.612] (--) NVIDIA(0): Memory: 3145728 kBytes
[ 79.612] (--) NVIDIA(0): VideoBIOS: 80.04.67.00.06
[ 79.612] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 79.616] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 670MX at PCI:1:0:0
[ 79.616] (--) NVIDIA(0): Chi Mei Optoelectronics corp. (DFP-0) (boot, connected)
[ 79.616] (--) NVIDIA(0): Samsung SyncMaster (DFP-1) (connected)
[ 79.616] (--) NVIDIA(0): DFP-2
[ 79.616] (--) NVIDIA(0): DFP-3
[ 79.616] (--) NVIDIA(0): DFP-4
[ 79.616] (--) NVIDIA(0): Chi Mei Optoelectronics corp. (DFP-0): Internal LVDS
[ 79.616] (--) NVIDIA(GPU-0): Chi Mei Optoelectronics corp. (DFP-0): 330.0 MHz maximum pixel clock
[ 79.616] (--) NVIDIA(0): Samsung SyncMaster (DFP-1): Internal TMDS
[ 79.616] (--) NVIDIA(GPU-0): Samsung SyncMaster (DFP-1): 165.0 MHz maximum pixel clock
[ 79.616] (--) NVIDIA(0): DFP-2: Internal TMDS
[ 79.616] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[ 79.616] (--) NVIDIA(0): DFP-3: Internal DisplayPort
[ 79.616] (--) NVIDIA(GPU-0): DFP-3: 960.0 MHz maximum pixel clock
[ 79.616] (--) NVIDIA(0): DFP-4: Internal DisplayPort
[ 79.616] (--) NVIDIA(GPU-0): DFP-4: 960.0 MHz maximum pixel clock
[ 79.616] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 79.616] (**) NVIDIA(0): device Chi Mei Optoelectronics corp. (DFP-0) (Using EDID
[ 79.616] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
[ 79.616] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 79.616] (**) NVIDIA(0): device Samsung SyncMaster (DFP-1) (Using EDID frequencies
[ 79.616] (**) NVIDIA(0): has been enabled on all display devices.)
[ 79.618] (==) NVIDIA(0):
[ 79.618] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 79.618] (==) NVIDIA(0): will be used as the requested mode.
[ 79.618] (==) NVIDIA(0):
[ 79.619] (II) NVIDIA(0): Validated MetaModes:
[ 79.619] (II) NVIDIA(0): "DFP-0:nvidia-auto-select,DFP-1:nvidia-auto-select"
[ 79.619] (II) NVIDIA(0): Virtual screen size determined to be 3600 x 1080
[ 80.144] (--) NVIDIA(0): DPI set to (128, 130); computed from "UseEdidDpi" X config
[ 80.144] (--) NVIDIA(0): option
[ 80.144] (--) Depth 24 pixmap format is 32 bpp
[ 80.144] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 80.144] (II) NVIDIA: access.
[ 80.150] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 80.150] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 80.150] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 80.150] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 80.150] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 80.150] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 80.150] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 80.150] (II) NVIDIA(0): Config Options in the README.
[ 80.155] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select,DFP-1:nvidia-auto-select"
[ 80.532] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 80.532] (==) NVIDIA(0): Backing store enabled
[ 80.532] (==) NVIDIA(0): Silken mouse enabled
[ 80.533] (==) NVIDIA(0): DPMS enabled
[ 80.533] (II) Loading sub module "dri2"
[ 80.533] (II) LoadModule: "dri2"
[ 80.533] (II) Module "dri2" already built-in
[ 80.533] (II) NVIDIA(0): [DRI2] Setup complete
[ 80.533] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 80.533] (--) RandR disabled
[ 80.539] (II) Initializing extension GLX
[ 80.605] (II) config/udev: Adding input device Power Button (/dev/input/event14)
[ 80.605] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 80.605] (II) LoadModule: "evdev"
[ 80.606] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 80.607] (II) Module evdev: vendor="X.Org Foundation"
[ 80.607] compiled for 1.16.2, module version = 2.9.1
[ 80.607] Module class: X.Org XInput Driver
[ 80.607] ABI class: X.Org XInput driver, version 21.0
[ 80.607] (II) Using input driver 'evdev' for 'Power Button'
[ 80.607] (**) Power Button: always reports core events
[ 80.607] (**) evdev: Power Button: Device: "/dev/input/event14"
[ 80.608] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 80.608] (--) evdev: Power Button: Found keys
[ 80.608] (II) evdev: Power Button: Configuring as keyboard
[ 80.608] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input18/event14"
[ 80.608] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 80.608] (**) Option "xkb_rules" "evdev"
[ 80.608] (**) Option "xkb_model" "pc104"
[ 80.608] (**) Option "xkb_layout" "us"
[ 80.635] (II) config/udev: Adding input device Video Bus (/dev/input/event15)
[ 80.635] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 80.635] (II) Using input driver 'evdev' for 'Video Bus'
[ 80.635] (**) Video Bus: always reports core events
[ 80.635] (**) evdev: Video Bus: Device: "/dev/input/event15"
[ 80.635] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 80.635] (--) evdev: Video Bus: Found keys
[ 80.635] (II) evdev: Video Bus: Configuring as keyboard
[ 80.635] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/LNXVIDEO:00/input/input19/event15"
[ 80.635] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 80.635] (**) Option "xkb_rules" "evdev"
[ 80.635] (**) Option "xkb_model" "pc104"
[ 80.635] (**) Option "xkb_layout" "us"
[ 80.636] (II) config/udev: Adding input device Power Button (/dev/input/event13)
[ 80.636] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 80.636] (II) Using input driver 'evdev' for 'Power Button'
[ 80.636] (**) Power Button: always reports core events
[ 80.636] (**) evdev: Power Button: Device: "/dev/input/event13"
[ 80.636] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 80.636] (--) evdev: Power Button: Found keys
[ 80.636] (II) evdev: Power Button: Configuring as keyboard
[ 80.636] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input17/event13"
[ 80.636] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[ 80.636] (**) Option "xkb_rules" "evdev"
[ 80.636] (**) Option "xkb_model" "pc104"
[ 80.636] (**) Option "xkb_layout" "us"
[ 80.637] (II) config/udev: Adding input device Lid Switch (/dev/input/event11)
[ 80.637] (II) No input driver specified, ignoring this device.
[ 80.637] (II) This device may have been added with another device file.
[ 80.637] (II) config/udev: Adding input device Sleep Button (/dev/input/event12)
[ 80.637] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 80.637] (II) Using input driver 'evdev' for 'Sleep Button'
[ 80.637] (**) Sleep Button: always reports core events
[ 80.637] (**) evdev: Sleep Button: Device: "/dev/input/event12"
[ 80.637] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[ 80.637] (--) evdev: Sleep Button: Found keys
[ 80.637] (II) evdev: Sleep Button: Configuring as keyboard
[ 80.637] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input16/event12"
[ 80.637] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
[ 80.637] (**) Option "xkb_rules" "evdev"
[ 80.637] (**) Option "xkb_model" "pc104"
[ 80.637] (**) Option "xkb_layout" "us"
[ 80.638] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event18)
[ 80.638] (II) No input driver specified, ignoring this device.
[ 80.638] (II) This device may have been added with another device file.
[ 80.638] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event19)
[ 80.638] (II) No input driver specified, ignoring this device.
[ 80.638] (II) This device may have been added with another device file.
[ 80.639] (II) config/udev: Adding input device LOGITECH G110 G-keys (/dev/input/event3)
[ 80.639] (**) LOGITECH G110 G-keys: Applying InputClass "evdev keyboard catchall"
[ 80.639] (II) Using input driver 'evdev' for 'LOGITECH G110 G-keys'
[ 80.639] (**) LOGITECH G110 G-keys: always reports core events
[ 80.639] (**) evdev: LOGITECH G110 G-keys: Device: "/dev/input/event3"
[ 80.639] (--) evdev: LOGITECH G110 G-keys: Vendor 0x46d Product 0xc22b
[ 80.639] (--) evdev: LOGITECH G110 G-keys: Found keys
[ 80.639] (II) evdev: LOGITECH G110 G-keys: Configuring as keyboard
[ 80.639] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.1/3-4.1.1/3-4.1.1:1.0/0003:046D:C22B.0003/input/input7/event3"
[ 80.639] (II) XINPUT: Adding extended input device "LOGITECH G110 G-keys" (type: KEYBOARD, id 10)
[ 80.639] (**) Option "xkb_rules" "evdev"
[ 80.639] (**) Option "xkb_model" "pc104"
[ 80.639] (**) Option "xkb_layout" "us"
[ 80.639] (II) config/udev: Adding input device Gaming Keyboard G110 (/dev/input/event4)
[ 80.639] (**) Gaming Keyboard G110: Applying InputClass "evdev keyboard catchall"
[ 80.639] (II) Using input driver 'evdev' for 'Gaming Keyboard G110'
[ 80.639] (**) Gaming Keyboard G110: always reports core events
[ 80.639] (**) evdev: Gaming Keyboard G110: Device: "/dev/input/event4"
[ 80.640] (--) evdev: Gaming Keyboard G110: Vendor 0x46d Product 0xc22a
[ 80.640] (--) evdev: Gaming Keyboard G110: Found keys
[ 80.640] (II) evdev: Gaming Keyboard G110: Configuring as keyboard
[ 80.640] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.1/3-4.1.3/3-4.1.3:1.0/0003:046D:C22A.0004/input/input8/event4"
[ 80.640] (II) XINPUT: Adding extended input device "Gaming Keyboard G110" (type: KEYBOARD, id 11)
[ 80.640] (**) Option "xkb_rules" "evdev"
[ 80.640] (**) Option "xkb_model" "pc104"
[ 80.640] (**) Option "xkb_layout" "us"
[ 80.640] (II) config/udev: Adding input device Gaming Keyboard G110 (/dev/input/event5)
[ 80.640] (**) Gaming Keyboard G110: Applying InputClass "evdev keyboard catchall"
[ 80.640] (II) Using input driver 'evdev' for 'Gaming Keyboard G110'
[ 80.640] (**) Gaming Keyboard G110: always reports core events
[ 80.640] (**) evdev: Gaming Keyboard G110: Device: "/dev/input/event5"
[ 80.640] (--) evdev: Gaming Keyboard G110: Vendor 0x46d Product 0xc22a
[ 80.640] (--) evdev: Gaming Keyboard G110: Found keys
[ 80.640] (II) evdev: Gaming Keyboard G110: Configuring as keyboard
[ 80.640] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.1/3-4.1.3/3-4.1.3:1.1/0003:046D:C22A.0005/input/input9/event5"
[ 80.640] (II) XINPUT: Adding extended input device "Gaming Keyboard G110" (type: KEYBOARD, id 12)
[ 80.640] (**) Option "xkb_rules" "evdev"
[ 80.640] (**) Option "xkb_model" "pc104"
[ 80.641] (**) Option "xkb_layout" "us"
[ 80.641] (II) config/udev: Adding input device Razer Razer Lachesis (/dev/input/event1)
[ 80.641] (**) Razer Razer Lachesis: Applying InputClass "evdev pointer catchall"
[ 80.641] (II) Using input driver 'evdev' for 'Razer Razer Lachesis'
[ 80.641] (**) Razer Razer Lachesis: always reports core events
[ 80.641] (**) evdev: Razer Razer Lachesis: Device: "/dev/input/event1"
[ 80.641] (--) evdev: Razer Razer Lachesis: Vendor 0x1532 Product 0xc
[ 80.641] (--) evdev: Razer Razer Lachesis: Found 12 mouse buttons
[ 80.641] (--) evdev: Razer Razer Lachesis: Found scroll wheel(s)
[ 80.641] (--) evdev: Razer Razer Lachesis: Found relative axes
[ 80.641] (--) evdev: Razer Razer Lachesis: Found x and y relative axes
[ 80.641] (II) evdev: Razer Razer Lachesis: Configuring as mouse
[ 80.641] (II) evdev: Razer Razer Lachesis: Adding scrollwheel support
[ 80.641] (**) evdev: Razer Razer Lachesis: YAxisMapping: buttons 4 and 5
[ 80.641] (**) evdev: Razer Razer Lachesis: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 80.641] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.2/3-4.2:1.0/0003:1532:000C.0001/input/input5/event1"
[ 80.641] (II) XINPUT: Adding extended input device "Razer Razer Lachesis" (type: MOUSE, id 13)
[ 80.642] (II) evdev: Razer Razer Lachesis: initialized for relative axes.
[ 80.642] (**) Razer Razer Lachesis: (accel) keeping acceleration scheme 1
[ 80.642] (**) Razer Razer Lachesis: (accel) acceleration profile 0
[ 80.642] (**) Razer Razer Lachesis: (accel) acceleration factor: 2.000
[ 80.642] (**) Razer Razer Lachesis: (accel) acceleration threshold: 4
[ 80.642] (II) config/udev: Adding input device Razer Razer Lachesis (/dev/input/mouse0)
[ 80.642] (II) No input driver specified, ignoring this device.
[ 80.642] (II) This device may have been added with another device file.
[ 80.643] (II) config/udev: Adding input device Razer Razer Lachesis (/dev/input/event2)
[ 80.643] (**) Razer Razer Lachesis: Applying InputClass "evdev keyboard catchall"
[ 80.643] (II) Using input driver 'evdev' for 'Razer Razer Lachesis'
[ 80.643] (**) Razer Razer Lachesis: always reports core events
[ 80.643] (**) evdev: Razer Razer Lachesis: Device: "/dev/input/event2"
[ 80.643] (--) evdev: Razer Razer Lachesis: Vendor 0x1532 Product 0xc
[ 80.643] (--) evdev: Razer Razer Lachesis: Found keys
[ 80.643] (II) evdev: Razer Razer Lachesis: Configuring as keyboard
[ 80.643] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.2/3-4.2:1.1/0003:1532:000C.0002/input/input6/event2"
[ 80.643] (II) XINPUT: Adding extended input device "Razer Razer Lachesis" (type: KEYBOARD, id 14)
[ 80.643] (**) Option "xkb_rules" "evdev"
[ 80.643] (**) Option "xkb_model" "pc104"
[ 80.643] (**) Option "xkb_layout" "us"
[ 80.643] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event6)
[ 80.643] (II) No input driver specified, ignoring this device.
[ 80.643] (II) This device may have been added with another device file.
[ 80.644] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event7)
[ 80.644] (II) No input driver specified, ignoring this device.
[ 80.644] (II) This device may have been added with another device file.
[ 80.644] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event8)
[ 80.644] (II) No input driver specified, ignoring this device.
[ 80.644] (II) This device may have been added with another device file.
[ 80.644] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event9)
[ 80.644] (II) No input driver specified, ignoring this device.
[ 80.644] (II) This device may have been added with another device file.
[ 80.645] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event10)
[ 80.645] (II) No input driver specified, ignoring this device.
[ 80.645] (II) This device may have been added with another device file.
[ 80.645] (II) config/udev: Adding input device BisonCam, NB Pro (/dev/input/event17)
[ 80.645] (**) BisonCam, NB Pro: Applying InputClass "evdev keyboard catchall"
[ 80.645] (II) Using input driver 'evdev' for 'BisonCam, NB Pro'
[ 80.645] (**) BisonCam, NB Pro: always reports core events
[ 80.645] (**) evdev: BisonCam, NB Pro: Device: "/dev/input/event17"
[ 80.645] (--) evdev: BisonCam, NB Pro: Vendor 0x5986 Product 0x512
[ 80.645] (--) evdev: BisonCam, NB Pro: Found keys
[ 80.645] (II) evdev: BisonCam, NB Pro: Configuring as keyboard
[ 80.645] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/input/input23/event17"
[ 80.645] (II) XINPUT: Adding extended input device "BisonCam, NB Pro" (type: KEYBOARD, id 15)
[ 80.645] (**) Option "xkb_rules" "evdev"
[ 80.645] (**) Option "xkb_model" "pc104"
[ 80.645] (**) Option "xkb_layout" "us"
[ 80.646] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 80.646] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 80.646] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 80.646] (**) AT Translated Set 2 keyboard: always reports core events
[ 80.646] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 80.646] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 80.646] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 80.646] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 80.646] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 80.646] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 16)
[ 80.646] (**) Option "xkb_rules" "evdev"
[ 80.646] (**) Option "xkb_model" "pc104"
[ 80.646] (**) Option "xkb_layout" "us"
[ 80.646] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event20)
[ 80.646] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 80.647] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 80.647] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
[ 80.647] (II) LoadModule: "synaptics"
[ 80.647] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 80.647] (II) Module synaptics: vendor="X.Org Foundation"
[ 80.647] compiled for 1.16.0, module version = 1.8.1
[ 80.647] Module class: X.Org XInput Driver
[ 80.647] ABI class: X.Org XInput driver, version 21.0
[ 80.647] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[ 80.647] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 80.647] (**) Option "Device" "/dev/input/event20"
[ 80.756] (II) synaptics: SynPS/2 Synaptics TouchPad: found clickpad property
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5662 (res 42)
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4660 (res 47)
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left double triple
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[ 80.757] (**) Option "TapButton1" "1"
[ 80.757] (**) Option "TapButton2" "2"
[ 80.757] (**) Option "TapButton3" "3"
[ 80.757] (**) Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
[ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 80.757] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 80.810] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio2/input/input22/event20"
[ 80.810] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 17)
[ 80.810] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[ 80.810] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
[ 80.810] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.038
[ 80.810] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 80.810] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[ 80.810] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 80.810] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 80.810] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 80.811] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
[ 80.811] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
[ 80.811] (II) config/udev: Adding input device PC Speaker (/dev/input/event16)
[ 80.811] (II) No input driver specified, ignoring this device.
[ 80.811] (II) This device may have been added with another device file.
[ 88.265] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 88.265] (II) NVIDIA(GPU-0): 3D Vision stereo.
[ 88.282] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 88.282] (II) NVIDIA(GPU-0): 3D Vision stereo.
[ 88.291] (II) NVIDIA(0): Setting mode "LVDS-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, HDMI-0: 1680x1050_60_0 @1680x1050 +1920+0 {ViewPortIn=1680x1050, ViewPortOut=1680x1050+0+0}"
[ 89.221] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 89.221] (II) NVIDIA(GPU-0): 3D Vision stereo.
[ 90.639] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 90.639] (II) NVIDIA(GPU-0): 3D Vision stereo.
[ 93.745] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 93.745] (II) NVIDIA(GPU-0): 3D Vision stereo.
Notably, the following lines appear in the working case, but not the broken case:
[ 78.914] (II) Applying OutputClass "nvidia" to /dev/dri/card0
[ 78.914] loading driver: nvidia
Does anyone know what might be going on here?
Last edited by straemer (2014-12-20 13:03:58)Hmmmm, that doesn't seem to be the issue. I have a nvidia geforce gtx 670mx. The nvidia website does link me to the 340xx driver for that card, but downgrading to that version still has the same issue. I suspect the issue is in Xorg, since it seems to load the module, but then decides it doesn't have a driver to run for some reason.
-
Failed to load servlet Class: org.apache.jasper.servlet.JspServlet
I am evaluating Weblogic 12c and is stuck in deployment of an application.
My application is locally developed and is working fine in Oracle Glassfish. I have install glassfish and deploy application multiple time.
In weblogic I can deploy the application successfully and the state= Prepared while Health=OK.
When I access applicaiton from web browser, it says:
Error 503--Service Unavailable
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.4 503 Service Unavailable
The server.log is having messages similar to following:
When processing WebService module 'SHMA'. Failed to load servlet Class: org.apache.jasper.servlet.JspServlet
Ignoring: unable to load class:java.lang.ClassNotFoundException: org.apache.jasper.servlet.JspServlet at: weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)
Jun 4, 2013 5:59:36 PM com.sun.xml.ws.model.JavaMethodImpl freeze
WARNING: Input Action on WSDL operation RegisterOperation and @Action on its associated Web Method registerOperation did not match and will cause problems in dispatching the requests
Any idea about how to fix this??
Application is working fine in Glassfish 3.2
I am having RHEL6-3 x86 with JDK 1.6u45 for Bea Weblogic 12c.
ThanksProbably not the right forum. But you have the honour of being the first person to ask a specific WebLogic Server question here.
The BEA dev-2-dev site still seems to be active. Try here hunting for a category here: http://forums.bea.com/index.jspa
-steve- -
How long load-on-startup servlet stays in weblogic6.1 sp2
does anybody know how long a load-on-startup servlet exists (before
gets destroyed) in weblogic6.1 sp2. What i want is in load-on-startup
servlet, I want to schedule a java.util.Timer and when application
gets undeployed, i want to cancel that timer. if load-on-startup
servlet exists for the whole application life span then i could do
timer.cancel() on the destroy method of load-on-startup servlet.
any suggestion?
thanks in adv,
soumik
You can simply use ServletContextListener instead - that way you do not
have to worry if (or when) WebLogic decides to destroy the servlet.
soumik <[email protected]> wrote:
> does anybody know how long a load-on-startup servlet exists (before
> gets destroyed) in weblogic6.1 sp2. What i want is in load-on-startup
> servlet, I want to schedule a java.util.Timer and when application
> gets undeployed, i want to cancel that timer. if load-on-startup
> servlet exists for the whole application life span then i could do
> timer.cancel() on the destroy method of load-on-startup servlet.
> any suggestion?
> thanks in adv,
> soumik
Dimitri
-
Can't get Servlet to Load On Startup
I am trying to get a servlet to run at startup, and I have put the xml below in WEB-INF/web.xml to make this happen, but it is not working. The servlet does not run at startup.
Anybody have any idea what the problem is?
<servlet>
<servlet-name>Cocoon</servlet-name>
<servlet-class>org.apache.cocoon.Cocoon</servlet-class>
<init-param>
<param-name>properties</param-name>
<param-value>./WEB-INF/cocoon.properties</param-value>
</init-param>
<load-on-startup/>
</servlet>
<servlet-mapping>
<servlet-name>Cocoon</servlet-name>
<url-pattern>*.xml</url-pattern>
</servlet-mapping>
ALSO, The servlet in this case is the Cocoon servlet, and the reason I am trying to get it to run at startup is because in my application I am calling it from another servlet, instead of through a direct call to an *.xml file, and so it requires a direct call to Initialize the Cocoon Engine. So, if anyone knows anything about how to solve this problem, that would also be helpful.
Thanks.
Harris.
Thank you!
That worked.
Ruslan Bilorusets <[email protected]> wrote:
>Harris,
>
>Please, try to specify a value for the <load-on-startup> element. It looks like a bug in our code.
>
>So,
><load-on-startup>1</load-on-startup>
>should do the trick.
>
>Thanks,
>-ruslan
>
>harris wrote:
>
>> I am trying to get a servlet to run at startup, and I have put the xml below in WEB-INF/web.xml to make this happen, but it is not working. The servlet does not run at startup.
>>
>> Anybody have any idea what the problem is?
>>
>> <servlet>
>> <servlet-name>Cocoon</servlet-name>
>> <servlet-class>org.apache.cocoon.Cocoon</servlet-class>
>> <init-param>
>> <param-name>properties</param-name>
>> <param-value>./WEB-INF/cocoon.properties</param-value>
>> </init-param>
>> <load-on-startup/>
>> </servlet>
>> <servlet-mapping>
>> <servlet-name>Cocoon</servlet-name>
>> <url-pattern>*.xml</url-pattern>
>> </servlet-mapping>
>>
>> ALSO, The servlet in this case is the Cocoon servlet, and the reason I am trying to get it to run at startup is because in my application I am calling it from another servlet, instead of through a direct call to an *.xml file, and so it requires a direct call to Initialize the Cocoon Engine. So, if anyone knows anything about how to solve this problem, that would also be helpful.
>>
>> Thanks.
>> Harris.
>
-
Servlet: "MessageBrokerServlet" failed to preload on startup in Web application:
We are migrating from the community edition to ES edition. The application server is Oracle Weblogic running on Solaris SPARC. I have deployed all the jars from the samples lib directory i.e tomcat/webapps/lcds-samples/WEB-INF/lib/. The appication is getting built successfully.But while I am trying to login to our application it is failing.The MessageBroker is not getting initialised. It is showing the following error in the application logs
<Aug 8, 2010 6:47:05 PM EDT> <Error> <HTTP> <BEA-101216> <Servlet: "MessageBrokerServlet" failed to preload on startup in Web application: "bdcui.war".
javax.servlet.UnavailableException: flex.messaging.util.concurrent.DefaultThreadPoolExecutor.<init>(IIJLjava/util/concurrent/ TimeUnit;Ljava/util/concurrent/BlockingQueue;Ljava/util/concurrent/ThreadFactory;)V
at flex.messaging.MessageBrokerServlet.init(MessageBrokerServlet.java:170)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.jav a:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
Truncated. see log file for complete stacktrace
Please suggest on this. I need some immediate advice on the above issue since I am not able to proceed further. I have tried by adding flex.write.path in the MessageBroker servlet's init params in the web.xml file. But may be I am not giving the correct value to the param.
Any comment would be appreciated.
Thanks & regards,
Chandra.specify /WEB-INF/flex/services-config.xml in your
messagebroker servlet ..
weblogic probebly doesnt accept the relative path or your
weblogic thinks your webapp is in the wrong dir.. I had the same
problem with resin because i started my webapp from the path
/developement/servers/resin/ etc... the problem was fixed when i
used something like c:/development/servers/resin ..
i dont have any experience with weblogic
Maybe you are looking for
-
Can not open PDF Files-have windows 7 & downloaded Adobe 9.2
Can not open up any PDF files. I have a new computer with windows 7. Have dowloaded 9.2 adobe reader as well as air. It comes up as File Conversion with options of select the encoding that makes your document readable. Nothing I choose works & th
-
How to display the status of a SubVI on the front panel?
Hi, I am writing a program to control an instrument through a serial communication port. The control and communication functions are integrated in a SubVI and they work fine. In the front panel of the main VI, I want to add some indicators to display
-
Renumbering Operations on a Production Order
SAP Gurus- I have a situation where we want to insert some operations into the middle of a production order and programmatically renumber the operations to keep things in order. For example, I have operations 10, 20, 30...100, 110, 120. I need to ad
-
Embedded .htm loses functionality in Page Viewer Web Part
Hello, I have a .htm file with the entire web content folder, generated by another application, stored in a Document Library on my SharePoint site. This web page contains 3 zones (html framesets with frames): The first one containing a tree-view wher
-
Value Mapping Replication...need help.....
Hi everyone, I want to get the value mapping table filled by the value stored in my excelsheet. Would it be possible to do that without java proxy? ~Thanks Pranav