Which says the rmi stub is bound to 1.1.1.21 (could be 1.2.11.21 and
the mail is munging the address?). If this is not the sandbox host
address, then it needs to be overriden using the java.rmi.server.hostname
system property. This need to be looked into further as the --host
value should be
Unfortunately, you can't use this kind of key generation with
insert-after-ejb-post-create.
[ 784322 ] INSERT after ejbPostCreate
http://sourceforge.net/tracker/?func=detailaid=784322group_id=22866atid=381174
By the spec (and current implementation), the primary key should be set
in ejbCreate
Hi, is there a best practice to run a RMI server into Jboss? I'm thinking of
realizing a RMI application to manager an email server, and would like to
run it into Jboss as a service. Any suggestion as what shall I do?
Thanks,
Marco
---
On Friday 05 December 2003 06:09, [EMAIL PROTECTED] wrote:
Brian, this problem occurs only when it is running under Linux. When we
changed our glib from glibc-2.3.2-4.80.6 to glibc-2.3.2-4.80.8 at RedHat 8
using up2date -u the problem got worse.
I looked at
Brian Wallis wrote:
Does this always happen on the same system or on more than one. You can see
these sort of errors if you have a memory or other hardware problem. One good
test for memory related issues is to compile a linux kernel, that usually
gets a sig11 if you have any marginal memory
I changed the IP addresses frequently when testing this and might have reported the
wrong one in the previous email. Anyay, we are running JBoss on XP and W2K and same
issue appears on both. We narrowed this problem down to where it appears when using
JNDI properties in a new InitialContext.
Running multiple instances and netstat shows a 1098 and 1099 listener on each
host so that looks good. One caveat is that running the same configuration twice
generates complains about the DefaultDS. That is reasonable but it should be noted. So
the only outstanding problem is the use
