Hi,

Sorry, I brought a double confusion:
1. Seems like the extra file for xsd issue was added after 3.0-M2 in META-INF. 2. Even with that extra file, I now remember I got a clear exception stating the activemqcore xsd was not reachable. In you case, you don't have such an exception.

If you start james from the bin folder with "./james start", you can have a look in the wrapper.log file (in bin folder) which may contain more information on the issue. Also, you can run in foreground with "./run.sh" and see if more message is shown.

Tks,

Eric


On 15/03/2011 21:21, Something Something wrote:
Hmm... I am a bit confused:

When I hit the URL for the XSD you provided, I see something like... Abort slow consumers..... It doesn't show XSD. There shouldn't be any firewall issue on my end.

Also, there's only one file in conf/META-INF/persistence.xml

Does the activemq-core-5.4.1.xsd go in there?


On Tue, Mar 15, 2011 at 10:51 AM, Eric Charles <[email protected] <mailto:[email protected]>> wrote:

    I had the same issue this morning trying to start james, it
    remained hanging after 1 line in the log
    I think this is related to this discussion:
    http://comments.gmane.org/gmane.comp.jakarta.james.user/16930

    It occurs when spring framework used by james can't get the some
    XSD from the internet.
    We thought it was fixed cause we added a special file in META-INF.
    Can you try to get
    http://activemq.apache.org/schema/core/activemq-core-5.4.1.xsd
    from your server and retry to start when you're sure the xsd is
    reachable ?

    Tks again,
    - Eric


    On 15/03/2011 18:20, Something Something wrote:
    ping localhost gives this...

    PING localhost (127.0.0.1): 56 data bytes
    64 bytes from 127.0.0.1 <http://127.0.0.1>: icmp_seq=0 ttl=64
    time=0.052 ms
    64 bytes from 127.0.0.1 <http://127.0.0.1>: icmp_seq=1 ttl=64
    time=0.076 ms
    64 bytes from 127.0.0.1 <http://127.0.0.1>: icmp_seq=2 ttl=64
    time=0.053 ms
    64 bytes from 127.0.0.1 <http://127.0.0.1>: icmp_seq=3 ttl=64
    time=0.108 ms
    64 bytes from 127.0.0.1 <http://127.0.0.1>: icmp_seq=4 ttl=64
    time=0.060 ms


    So I deleted all log files and tried again.  Now I don't see
    anything in any log files except james-server.log which has only
    1 line:

    INFO  10:17:06,633 |
    org.apache.james.container.spring.JamesServerApplicationContext |
    Refreshing
    org.apache.james.container.spring.JamesServerApplicationContext@194835fb:
    startup date [Tue Mar 15 10:17:06 PDT 2011]; root of context
    hierarchy

    Please help.


    On Tue, Mar 15, 2011 at 9:27 AM, Eric Charles <[email protected]
    <mailto:[email protected]>> wrote:

        Hi,
        Yes, is seems that the name localhost is not defined in your
        host file.
        Try 'ping localhost' in the console, it should return
        127.0.0.1 (or an ipv6 equivalent).
        Once this is fixed, you can try to launch james and get
        success (or another error message...).
        Tks,
        Eric



        On 15/03/2011 17:21, Something Something wrote:

            The only error message I see is in domainlist.log.
            INFO  21:16:25,225 | james.domainlist | Set autodetect
            to: true
            INFO  21:16:25,226 | james.domainlist | Set autodetectIP
            to: true
            INFO  21:16:25,232 | james.domainlist | Bean
             org.apache.james.domainlist.xml.XMLDomainList started.
            INFO  21:16:25,389 | james.domainlist | Local host is:
            192.168.1.3
            ERROR 21:16:25,515 | james.domainlist | Cannot get IP
            address(es) for localhost
            INFO  21:20:13,701 | james.domainlist | Set autodetect
            to: true
            INFO  21:20:13,702 | james.domainlist | Set autodetectIP
            to: true
            INFO  21:20:13,709 | james.domainlist | Bean
             org.apache.james.domainlist.xml.XMLDomainList started.
            INFO  21:20:13,788 | james.domainlist | Local host is:
            192.168.1.3
            ERROR 21:20:13,809 | james.domainlist | Cannot get IP
            address(es) for localhost

            Could this be the problem?


            On Tue, Mar 15, 2011 at 9:17 AM, Something Something
            <[email protected]
            <mailto:[email protected]>
            <mailto:[email protected]
            <mailto:[email protected]>>> wrote:

               Getting message... "The connection to 6243 did not
            succeed".

               After I start James I see this when I run jps

               6304 WrapperSimpleApp

               Within less than 30 seconds this process dies!  Hmm...
            I will look
               at logs.. but any ideas?  Thanks again for your help.



               On Tue, Mar 15, 2011 at 7:14 AM, Eric Charles
            <[email protected] <mailto:[email protected]>
            <mailto:[email protected] <mailto:[email protected]>>> wrote:

                   Hi,
                   No telnet in 3.0-2 if I remember well.
                   james-cli is still a work in-progress and is not
            operational
                   in 3.0-M2.

                   To manage via JMX, launch jconsole command is your
            shell box,
                   connect to the james process, and go to the MBeans
            tab.
                   You should have methods available to create
            domains, users,...

                   Tks,
                   - Eric


                   On 15/03/2011 14:50, Something Something wrote:

                       No stacktrace in james-server.log.  Where else
                should I look?

                       I am using
                james-server-container-spring-3.0-M2.  No, telnet
                       for this, right?

                       I read in one of the previous emails from
                Norman... " All the
                       management stuff need to get done via JMX or
                james-cli"

                       What's james-cli?  I promise I will research,
                but any
                       notes/tips about starting JMX or james-cli
                quickly?  Thanks
                       for help.


                       On Tue, Mar 15, 2011 at 12:51 AM, Eric Charles
                <[email protected] <mailto:[email protected]>
                <mailto:[email protected] <mailto:[email protected]>>> wrote:

                           Hi,
                           Which version are you using?
                           If you use the snapshot, telnet is no more
                available and
                           you can manage james via JMX.
                           Eric


                           On 15/03/2011 07:19, Norman Maurer wrote:

                               When you say James dies what does this
                mean ? Any
                               stacktrace ?

                               I use osx as development platform
                without a problem...

                               Bye,
                               Norman


                               2011/3/15 Something
                               Something<[email protected]
                <mailto:[email protected]>
                <mailto:[email protected]
                <mailto:[email protected]>>>


                                   Has anyone tried starting James on
                Mac for
                                   development purposes?  Is Mac a
                                   supported platform?

                                   It's not working for me.  I am
                using James 3.0.M2

                                   When I do:

                                   ./james start

                                   It seems to start.  I see no
                errors in the log.
                                    But when I do:

                                   telnet localhost 4555

                                   I get this:

                                   Trying ::1...
                                   telnet: connect to address ::1:
                Connection refused
                                   Trying fe80::1...
                                   telnet: connect to address
                fe80::1: Connection
                                   refused
                                   Trying 127.0.0.1...
                                   telnet: connect to address 127.0.0.1
                <http://127.0.0.1>: Connection refused

                                   telnet: Unable to connect to
                remote host

                &  James dies.

                                   Any ideas?



---------------------------------------------------------------------
                           To unsubscribe, e-mail:
                [email protected]
                <mailto:[email protected]>
                <mailto:[email protected]
                <mailto:[email protected]>>

                           For additional commands, e-mail:
                [email protected]
                <mailto:[email protected]>
                <mailto:[email protected]
                <mailto:[email protected]>>










Reply via email to