I have been trying to implement a basic JMSAppender
uisng JBoss 3.2.0 and my client simply freezes when
trying to create a topic connection.
My log4j appender looks like this:
<appender name="JMS"
class="org.apache.log4j.net.JMSAppender">
<param name="InitialContextFactoryName"
value="org.jnp.interfaces.NamingContextFactory"/>
<param name="ProviderURL"
value="jnp://par1cluster2:1099"/>
<param name="URLPkgPrefixes"
value="org.jboss.naming:org.jnp.interfaces"/>
<param name="TopicConnectionFactoryBindingName"
value="UIL2ConnectionFactory"/>
<param name="TopicBindingName"
value="topic/testTopic"/>
<param name="UserName" value="guest"/>
<param name="Password" value="guest"/>
<param name="LocationInfo" value="true"/>
<param name="Threshold" value="INFO"/>
</appender>
The log4j with debug enabled looks like this:
Configuring Log4J
Using:http://localhost:8080/flt-log4j-jms.xml
log4j: Trying to find [log4j.xml] using context
classloader [EMAIL PROTECTED]
log4j: Trying to find [log4j.xml] using
[EMAIL PROTECTED] class loader.
log4j: Trying to find [log4j.xml] using
ClassLoader.getSystemResource().
log4j: Trying to find [log4j.properties] using context
classloader [EMAIL PROTECTED]
log4j: Using URL
[jar:file:/C:/jboss-3.2.0_tomcat-4.1.24/client/jbossall-client.jar!/log4j.properties]
for automatic log4j configuration.
log4j: Reading configuration from URL
jar:file:/C:/jboss-3.2.0_tomcat-4.1.24/client/jbossall-client.jar!/log4j.properties
log4j: Parsing for [root] with value=[ERROR, stdout].
log4j: Level token is [ERROR].
log4j: Category root set to ERROR
log4j: Parsing appender named "stdout".
log4j: Parsing layout options for "stdout".
log4j: Setting property [conversionPattern] to [%5p
[%t] (%F:%L) - %m%n].
log4j: End of parsing for "stdout".
log4j: Parsed "stdout" options.
log4j: Finished configuring.
log4j: System property is :null
log4j: Standard DocumentBuilderFactory search
succeded.
log4j: DocumentBuilderFactory is:
org.apache.crimson.jaxp.DocumentBuilderFactoryImpl
log4j: URL to log4j.dtd is
[jar:file:/C:/Jakarta/jakarta-log4j-1.2.7/dist/lib/log4j-1.2.7.jar!/org/apache/log4j/xml/log4j.dtd].
log4j: debug attribute= "null".
log4j: Ignoring debug attribute.
log4j: Threshold ="null".
log4j: Level value for root is [DEBUG].
log4j: root level set to DEBUG
log4j: Class name: [org.apache.log4j.net.JMSAppender]
log4j: Setting property [initialContextFactoryName] to
[org.jnp.interfaces.NamingContextFactory].
log4j: Setting property [providerURL] to
[jnp://par1cluster2:1099].
log4j: Setting property [URLPkgPrefixes] to
[org.jboss.naming:org.jnp.interfaces].
log4j: Setting property
[topicConnectionFactoryBindingName] to
[UIL2ConnectionFactory].
log4j: Setting property [topicBindingName] to
[topic/testTopic].
log4j: Setting property [userName] to [guest].
log4j: Setting property [password] to [guest].
log4j: Setting property [locationInfo] to [true].
log4j: Setting property [threshold] to [INFO].
log4j: Getting initial context.
log4j: Looking up [UIL2ConnectionFactory]
log4j:WARN No appenders could be found for logger
(org.jboss.mq.referenceable.SpyConnectionFactoryObjectFactory).
log4j:WARN Please initialize the log4j system
properly.
log4j: About to create TopicConnection.
It never completes creating a topic connection.
I put org.jboss.mq under debug on the server. When the
request is issued for a connection, the logs says:
2003-09-05 07:15:54,111 DEBUG
[org.jboss.mq.il.uil2.SocketManager] Begin
ReadTask.run
2003-09-05 07:15:54,111 DEBUG
[org.jboss.mq.il.uil2.SocketManager] Begin
WriteTask.run
2003-09-05 07:15:54,111 DEBUG
[org.jboss.mq.il.uil2.SocketManager] Created
ObjectOutputStream
Once the client freezes, I have waited for a few
minutes and then killed the client. Once I kill the
client, the server MQ log says:
2003-09-05 07:18:58,619 ERROR
[org.jboss.mq.il.uil2.SocketManager] Failed to create
ObjectInputStream
java.net.SocketException: Connection reset
at
java.net.SocketInputStream.read(SocketInputStream.java:168)
at
java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at
java.io.BufferedInputStream.read1(BufferedInputStream.java:222)
at
java.io.BufferedInputStream.read(BufferedInputStream.java:277)
at
org.jboss.util.stream.NotifyingBufferedInputStream.read(NotifyingBufferedInputStream.java:77)
at
java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2150)
at
java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2163)
at
java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2634)
at
java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:734)
at
java.io.ObjectInputStream.<init>(ObjectInputStream.java:253)
at
org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:265)
at java.lang.Thread.run(Thread.java:536)
I have also tried the same test with 3.2.1, 3.2.2RC2
and 3.2.2RC3 and the results are the same.
It's really wierd because this is a really simple
example, so I started wondering if it was
envornmental, but we have a client in the same
environment using P2P JMS with no issues at all.
Any help would be appreciated.
Cheers.
//Nicholas
=====
Nicholas Whitehead
Home: (973) 377 9335
Cell: (201) 615 2716
[EMAIL PROTECTED]
Get Your News From The Crowbar: http://crowbar.dnsalias.com:443/crowbar/
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
