Just a bit more info... I wrote a quick standalone program (i.e. not running
inside weblogic - just using weblogic as the JMS server) that logs a couple
messages to the JMSAppender. After a few runs of this program, I get the
same deaf JMSSink symptom.
At this point, I'm still suspecting it's a weblogic JMS issue. Anyone have
experiences with weblogic's JMS? I'm using weblogic 5.1.
Thanks again,
-Scott
> -----Original Message-----
> From: L. Scott Emmons [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 07, 2001 12:46 PM
> To: [EMAIL PROTECTED]
> Subject: Problems with JMS
>
>
> I'm having some problems using JMSAppender/JMSSink in a J2EE
> environment
> (weblogic). JMSSink receives the first message sent, however
> goes deaf and
> receives no more messages after the first. On the weblogic
> error log I get
> errors like:
>
> [TopicSessionState] :
> ObjectMessageID:N1,org.apache.log4j.spi.LoggingEvent@31475e]:
> REQUEST TIMED
> OUT,weblogic.jms.common.TimeoutException: Request Timed Out
>
> If I restart JMSSink, it will work for a few messages, then
> once again stop
> receiving them. The weblogic console shows messages published
> to the topic,
> but never received by a subcriber.
>
> I've experimented with non_persistent messages (modifying
> JMSSink to not be
> durable), and with persistent messages - similar results in
> both cases.
>
> I was hoping somebody had some ideas what to look for. My
> logging sources
> are both EJBs and Servlets.
>
> Logging using log4j.FileAppender to Stdout (weblogic error
> log) works just
> fine - all messages get logged.
>
> Thanks for any help anyone can provide,
> -Scott
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
