Ok, sounds like for sure log messages are reaching the RemoteLoggerServiceImpl class.
You can attach a debugger like this: http://wiki.apache.org/tomcat/FAQ/Developing <http://wiki.apache.org/tomcat/FAQ/Developing>Are you also deploying your log4j.jar in WEB-INF/lib/ ? Can you test a Log.fatal() message? - log4j defaults to logging DEBUG and higher (i.e. TRACE messages are ignored; DEBUG, INFO, WARN, ERROR, FATAL are logged) - java.util.logging defaults to logging INFO and higher (i.e. in java.util.logging terms, FINEST, FINER, FINE, CONFIG are ignored; INFO, WARNING, SEVERE are logged) Can you, in your own servlet, or a modified version of RemoteLoggerServiceImpl add you own log4j messages? Logger logger = Logger.getLogger("gwt-log"); logger.debug("test"); On Thu, Nov 4, 2010 at 9:57 AM, cpitzner <[email protected]> wrote: > I'm not sure how to do that, since it works fine running in hosted > mode? Unless I am missing a more general debugging strategy here. > > And yes, there are no 404s. I changed the servlet configuration in > web.xml to confirm I had the right project name, and generated 404s > when it was wrong. > > On Nov 2, 6:06 pm, Fred Sauer <[email protected]> wrote: > > Sounds like you've already done a lot of debugging. > > > > I'd set a breakpoint in the apache / tomcat configuration inside the > > RemoteLoggerServiceImpl > > servlet and see where that leads you. I assume the Apache/Tomcat logs > > confirm that the RPCs are coming in and being handled, i.e. they're not > > serving 404s or anything like that. > > > > Fred > > > > > > > > > > > > > > > > > > > > On Mon, Nov 1, 2010 at 8:53 PM, cpitzner <[email protected]> wrote: > > > I have RemoteLogger working when I run locally in hosted mode. GWT > > > 2.0.4 and gwt-log 3.0.3. > > > > > Client messages show in my console window, and the RPC copies are > > > written to the 'server' log file like this: > > > > > com.allen_sauer.gwt.log.server.ServerLogImplLog4J.log > > > (ServerLogImplLog4J.java:72) : "message" > > > > > When I deploy the same code to a apache / tomcat server, the RPC > > > messages are never logged. > > > > > Running in hosted mode, I can see the post calls to /[module name]/gwt- > > > log POST successfully, so I am fairly confident I have the servlet > > > configured properly. I am running log4j. Calls through gwt-log on > > > the server sections of my app are getting logged successfully, so I am > > > confident that gwt-log is installed properly. > > > > > What else can or should I be doing to debug? > > > > > web.xml: > > > > > <servlet> > > > <servlet-name>gwt-log-remote-logger-servlet</servlet-name> > > > <servlet- > > > class>com.allen_sauer.gwt.log.server.RemoteLoggerServiceImpl</servlet- > > > class> > > > </servlet> > > > <servlet-mapping> > > > <servlet-name>gwt-log-remote-logger-servlet</servlet-name> > > > <url-pattern>/[module name]/gwt-log</url-pattern> > > > </servlet-mapping> > > > > > *.gwt.xml: > > > > > <!--GWT Logging third party module--> > > > <!-- For development a default of `DEBUG` is recommended --> > > > <inherits name="com.allen_sauer.gwt.log.gwt-log-DEBUG"/> > > > > > <!--this pops up an interactive debugging screen if not disabled-- > > > > > <set-property name="log_DivLogger" value="DISABLED" /> > > > > > <!-- Remote Debugging for user on a server--> > > > <!-- This is the version for 3.0.3 --> > > > <inherits name="com.allen_sauer.gwt.log.gwt-log-RemoteLogger" /> > > > > > <!--3.0.1 version > > > <set-property name="log_RemoteLogger" value="ENABLED" /> > > > --> > > > <set-configuration-property name="log_url" value="/[module name]/ > > > gwt-log" /> > > > <set-configuration-property name="log_pattern" > > > value="[%d{ISO8601}] - [%p] - %C.%M (%F:%L) : %m\r\n" /> > > > > > Code: > > > > > Imported the Log class. > > > Added the following to the applicaiton > > > > > public void onModuleLoad() { > > > Log.setCurrentLogLevel(Log.getLowestLogLevel()); > > > Log.setUncaughtExceptionHandler(); > > > ... > > > > > Calls to Log.debug, Log.info, Log.warn and Log.error are all not > > > getting displayed. > > > > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "gwt-log" group. > > > To post to this group, send email to [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]<gwt-log%[email protected]> > <gwt-log%[email protected]<gwt-log%[email protected]>> > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/gwt-log?hl=en. > > > > -- > > Fred Sauer > > Developer Advocate > > Google Inc. > > 1600 Amphitheatre Parkway > > Mountain View, CA 94043 > > [email protected] > > -- > You received this message because you are subscribed to the Google Groups > "gwt-log" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<gwt-log%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/gwt-log?hl=en. > > -- Fred Sauer Developer Advocate Google Inc. 1600 Amphitheatre Parkway Mountain View, CA 94043 [email protected] -- You received this message because you are subscribed to the Google Groups "gwt-log" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/gwt-log?hl=en.
