From owner-freebsd-java Mon Jun 24 13:53:15 2002 Delivered-To: freebsd-java@freebsd.org Received: from web13406.mail.yahoo.com (web13406.mail.yahoo.com [216.136.175.64]) by hub.freebsd.org (Postfix) with SMTP id 6AB5B37B403 for ; Mon, 24 Jun 2002 13:52:55 -0700 (PDT) Message-ID: <20020624205255.6854.qmail@web13406.mail.yahoo.com> Received: from [12.254.130.74] by web13406.mail.yahoo.com via HTTP; Mon, 24 Jun 2002 13:52:55 PDT Date: Mon, 24 Jun 2002 13:52:55 -0700 (PDT) From: Dan Hulme Reply-To: dan_256@yahoo.com Subject: Re: jboss3ctl To: Ernst de Haan , freebsd-java@freebsd.org In-Reply-To: <200206241158.44834.znerd@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-575564343-1024951975=:6704" Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --0-575564343-1024951975=:6704 Content-Type: text/plain; charset=us-ascii Yeah. I found out some more information. The log file says that "libhpi" couldn't be found. Here's the info I've gathered: 1). I did a clean reinstall of jboss3, which created a new daemonctl.c that had 1.3.1 as the path. 2). There is still something interesting on the execl line: the /usr/local/jdk1.3.1/bin/java is the 1st AND second argument. Taking this out didn't change anything, though. Is that standard procedure (to put the command twice)? I have seen something like that before, but I thought the second argument to execl was the first argument to the procedure being run. 3). The startup script now works fine (020.startup.sh). In fact, if I do su -m www -c "exec jboss3ctl start" It also runs fine. Additionally, I temporarily created a shell for the www user, and this account can also run the daemon w/o a problem. 4). root can run "java -jar run.jar" fine. 5). root cannot run "jboss3ctl start" successfully. This puts the error into stderr.log I mentioned above: /usr/libexec/ld-elf.so.1: Shared object "libhpi.so" not found (I have the lib in the standard place under jdk1.3.1/jre/lib/i386/green_threads) 6). jboss3ctl is user www, group www with these permissions: rwsr-sr-- Theoretically, this means it should already be running as www if I run it from any other account, right? So why does it seem to require using "su"? 7). It seems like something is wrong with my ENV, or it wouldn't be complaining about the missing lib. But the www user has no special ENV settings that I know of. When is su to www (when I created a shell), it has the same ENV as my root user. 8). I created another user, and put them in the www group. They cannot run jboss3ctl either. Hope this all helps. Thanks, Dan Ernst de Haan wrote: Hi Dan, If the jboss3 port uses JDK 1.2, then only JDK 1.2 was available when you installed the port. Run 'make clean deinstall install' to make the port use your JDK 1.3. If it can't find it, though, it will fallback to a JDK 1.2. It should work with JDK 1.2 too. Hmmm... Can you tell me what is in the JBoss 3 log file? Ernst --------------------------------- Do You Yahoo!? Sign-up for Video Highlights of 2002 FIFA World Cup --0-575564343-1024951975=:6704 Content-Type: text/html; charset=us-ascii

Yeah.  I found out some more information.  The log file says that "libhpi" couldn't be found.

Here's the info I've gathered:

1). I did a clean reinstall of jboss3, which created a new daemonctl.c that had 1.3.1 as the path.

2). There is still something interesting on the execl line: the /usr/local/jdk1.3.1/bin/java is the 1st AND second argument.  Taking this out didn't change anything, though.  Is that standard procedure (to put the command twice)?  I have seen something like that before, but I thought the second argument to execl was the first argument to the procedure being run.

3). The startup script now works fine (020.startup.sh).  In fact, if I do
      su -m www -c "exec jboss3ctl start"
     It also runs fine.  Additionally, I temporarily created a shell for the www user, and this account can also run the daemon w/o a problem.

4). root can run "java -jar run.jar" fine.

5). root cannot run "jboss3ctl start" successfully.  This puts the error into stderr.log I mentioned above:
    /usr/libexec/ld-elf.so.1: Shared object "libhpi.so" not found (I have the lib in the standard place under jdk1.3.1/jre/lib/i386/green_threads)

6). jboss3ctl is user www, group www with these permissions:

    rwsr-sr--

   Theoretically, this means it should already be running as www if I run it from any other account, right?  So why does it seem to require using "su"?

7). It seems like something is wrong with my ENV, or it wouldn't be complaining about the missing lib.  But the www user has no special ENV settings that I know of.  When is su to www (when I created a shell), it has the same ENV as my root user.

8). I created another user, and put them in the www group.  They cannot run jboss3ctl either.

Hope this all helps.

Thanks,

Dan

 

  Ernst de Haan <znerd@freebsd.org> wrote:

Hi Dan,

If the jboss3 port uses JDK 1.2, then only JDK 1.2 was available when you
installed the port. Run 'make clean deinstall install' to make the port use
your JDK 1.3. If it can't find it, though, it will fallback to a JDK 1.2.

It should work with JDK 1.2 too. Hmmm... Can you tell me what is in the JBoss
3 log file?

Ernst


Do You Yahoo!?
Sign-up for Video Highlights of 2002 FIFA World Cup --0-575564343-1024951975=:6704-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message