One difference between the cases when the connection does and doesn't work is that I
think when it does work, in the destination JVM there is a QueueReceiver and
MessageListener for the destination queue, and when it doesn't work there isn't a
receiver/listener.
View the original post :
http:/
We're using JBoss 3.2.3 on Windows 2000, with the default Hypersonic SQL persistence.
We are trying to get UIL2 to work as the IL for connections to remote destinations
(just queues, in our case). So we form connections to remote queues using
"UIL2ConnectionFactory", and to local ones with the r
Yes, we definitely need to change the port number.
The question is, is there a way to pick a fixed port number that will basically never
have conflicts.
I'm running on a Windows 2000 system. We had been using port 1099 for JNDI, but it
seems that sometimes, some other process has grabbed that p
Actually, most of the time it seems the process using port 1099 has something to do
with CIFS (Windows network filesystem) access to mapped network drives. But thanks for
the suggestion.
This problem must come up often on Win2K systems. Is there a recommended solution?
View the original post :
We run JBoss 3.2.3 on Windows 2000 systems, and at startup we often have a fatal error
due to a port number conflict betweenJBoss' JNDI and other processes that are
temporarily using that same port number. Up to now we have used just the default JNDI
port of 1099. I am thinking to try to avoid t
I did some experimentation with JBoss 3.2.3 to try to get an MDB in one JBoss server
instance to read messages out of a remote queue, i.e. one located in a different
server instance. In jboss.xml, I used the JNDI name of the remote queue, like so:
|
| jnp://remotehost:1099/queu
Thanks for the tip, Adrian. It turns out the problem was with our jboss.xml CMP
descriptor. We had mistakenly defined a CMP entity bean with no fields. JBoss 3.0.7
had no problem with that, but deployment in 3.2.3 failed with a null pointer
exception. Seems like the kind of thing that should eit
I noticed that for JBoss-specific EJB deployment, there is a new jboss_3_2.dtd for the
jboss.xml files. There appear to be a lot of changes in this DTD from 3.0 to 3.2.
To run on JBoss 3.2.x, is it required for all EJB's to use the new 3.2 DTD? Or is
there backward compatibility if an EJB uses
I noticed that for JBoss-specific EJB deployment, there is a new jboss_3_2.dtd for the
jboss.xml files. There appear to be a lot of changes in this DTD from 3.0 to 3.2.
To run on JBoss 3.2.x, is it required for all EJB's to use the new 3.2 DTD? Or is
there backward compatibility if an EJB uses
I'm trying to upgrade my JBoss from 3.0.6 to 3.2.3, and having
problems with a few (but not all) of our EJB's. I'm using the
MS SQLSERVER2000 datasource, with JBoss and the database running
on the same Windows 2000 host.
I am beginning to think that something in the EJB implementation has
changed,
10 matches
Mail list logo
