Re: [Wrapper-user] JBoss Service does not start while system boots up

[Christian M. <chr...@ta...>]

Prashant,

Which version of the Wrapper are you using?

I'm asking, because I just remembered this:

- Fix a problem in the shell script that was preventing the script
from starting the Wrapper correctly if a file or directory existed in
the current working directory which was one character in length. This
was only a problem when the delta-pack naming of the Wrapper was used.
This was easy to reproduce on AIX systems on system restart because a
"u" directory exists in the root directory by default. This had been a
problem since 3.4.0 when it was introduced as a fix to a Solaris
problem. The root cause was a missing set of quotes in the tr command.

This is in the release notes for 3.5.7, maybe it is affecting you...

Also you are saying that jboss is trying to start up. how do you know
that, if there are no log entries at any place?

Best Regards,
Christian



On Mon, Feb 21, 2011 at 7:54 PM, Prashant N <ma...@gm...> wrote:
> Hi,
>
> I have done all these steps, as stated in my previous mail. I observed
> that it does not boot up while booting, it just fails. There is no
> failed entry for JBoss in /var/log/messages.
>
> The JBoss service tries to start up at boot, but fails with no
> apparent log entries in any of the logs like messages, wrapper.log,
> boot.log and server.log
>
> Prashant
>