solved, caused by amq setting.
On Mon, Jan 4, 2010 at 8:51 PM, CdrPlum <[email protected]> wrote:
> all info:
>
>
> Fatal error: Uncaught exception 'StompException' with message 'User name or
> password is invalid.' in /home/site/public_html/extlib/Stomp/Frame.php:54
> Stack trace:
> #0 /home/site/public_html/extlib/Stomp/Frame.php(41):
> StompFrame->_init('ERROR', Array, 'java.lang.Secur...')
> #1 /home/site/public_html/extlib/Stomp.php(555):
> StompFrame->__construct('ERROR', Array, 'java.lang.Secur...')
> #2 /home/site/public_html/extlib/Stomp.php(203): Stomp->readFrame()
> #3 /home/site/public_html/lib/stompqueuemanager.php(63):
> Stomp->connect(NULL, NULL)
> #4 /home/site/public_html/lib/stompqueuemanager.php(76):
> StompQueueManager->_connect()
> #5 /home/site/public_html/lib/util.php(966):
> StompQueueManager->enqueue(Object(Notice), 'sms')
> #6 /home/site/public_html/lib/util.php(932):
> common_enqueue_notice(Object(Notice))
> #7
> /home/site/public_html/plugins/TwitterBridge/daemons/twitterstatusfetcher.php(217):
> common_broadcast_notice(Object(Notice))
> #8
> /home/site/public_html/plugins/TwitterBridge/daemons/twitterstatusfetcher.php(142):
> Tw in /home/site/public_html/extlib/Stomp/Frame.php on line 54
>
>
>
> On Mon, Jan 4, 2010 at 8:49 PM, CdrPlum <[email protected]> wrote:
>
>> solved.
>> I should use 61613 port in config file. There are two ports opened in Amq
>> setting, 61616 and 61613.
>> when I changed config to tcp://localhost:61613, the error above
>> disappeared.
>>
>> but, a new error:
>> Fatal error: Uncaught exception 'StompException' with message 'User name
>> or password is invalid.' in /home/site/public_html/extlib/Stomp/Frame.php:54
>>
>>
>>
>> On Mon, Jan 4, 2010 at 8:24 PM, CdrPlum <[email protected]> wrote:
>>
>>> These are settings in my config file:
>>> ----------------
>>> $config['queue']['subsystem'] = 'stomp';
>>> $config['queue']['stomp_server'] = 'tcp://localhost:61616';
>>> // use different queue_basename for each statusnet instance managed by
>>> the server
>>> $config['queue']['queue_basename'] = '/queue/statusnet/';
>>> -----------------
>>>
>>> are these correct? what's the queue_basename?
>>>
>>>
>>> On Mon, Jan 4, 2010 at 8:21 PM, CdrPlum <[email protected]> wrote:
>>>
>>>> here is the exported info after connection:
>>>>
>>>> INFO | Using Persistence Adapter:
>>>> AMQPersistenceAdapter(activemq-data/SERVER1)
>>>> INFO | AMQStore starting using directory: activemq-data/SERVER1
>>>> INFO | Kaha Store using data directory
>>>> activemq-data/SERVER1/kr-store/state
>>>> INFO | Active data files: []
>>>> INFO | ActiveMQ 5.3.0 JMS Message Broker (SERVER1) is starting
>>>> INFO | For help or more information please see:
>>>> http://activemq.apache.org/
>>>> INFO | Kaha Store using data directory
>>>> activemq-data/SERVER1/kr-store/data
>>>> INFO | Listening for connections at: tcp://localhost:61616
>>>> INFO | Connector tcp://localhost:61616 Started
>>>> INFO | Listening for connections at: stomp://localhost:61613
>>>> INFO | Connector stomp Started
>>>> INFO | ActiveMQ JMS Message Broker (SERVER1,
>>>> ID:jesselee.theplanet.host-49482-12626074
>>>>
>>>>
>>>> On Mon, Jan 4, 2010 at 10:12 AM, CdrPlum <[email protected]> wrote:
>>>>
>>>>> of course, I started activemq daemon.
>>>>> I viewed activemq log file, there is only one error repeated many
>>>>> times:
>>>>>
>>>>> 2010-01-04 10:08:13,392 | INFO | Database
>>>>> /opt/activemq/data/kahadb/lock is locked... waiting 10 seconds for the
>>>>> database to be unlocked. Reason: java.io.IOException: File
>>>>> '/opt/activemq/data/kahadb/lock' could not be locked. |
>>>>> org.apache.activemq.store.kahadb.MessageDatabase | main
>>>>>
>>>>>
>>>>> On Mon, Jan 4, 2010 at 2:44 AM, Federico Marani <[email protected]>wrote:
>>>>>
>>>>>> an error in stomp connect makes me think the daemon is not running...
>>>>>>
>>>>>> have you started the activemq daemon? if so, what is it logging??
>>>>>>
>>>>>>
>>>>>> 2010/1/3 CdrPlum <[email protected]>
>>>>>>
>>>>>>> I just installed activemq and start the statusnet daemons, but got
>>>>>>> this error:
>>>>>>>
>>>>>>> Fatal error: Uncaught exception 'StompException' with message
>>>>>>> 'Unexpected command: ' in /home/site/public_html/extlib/Stomp.php:210
>>>>>>> Stack trace:
>>>>>>> #0 /home/site/public_html/lib/stompqueuemanager.php(63):
>>>>>>> Stomp->connect(NULL, NULL)
>>>>>>> #1 /home/site/public_html/lib/stompqueuemanager.php(76):
>>>>>>> StompQueueManager->_connect()
>>>>>>> #2 /home/site/public_html/lib/util.php(966):
>>>>>>> StompQueueManager->enqueue(Object(Notice), 'sms')
>>>>>>> #3 /home/site/public_html/lib/util.php(932):
>>>>>>> common_enqueue_notice(Object(Notice))
>>>>>>> #4
>>>>>>> /home/site/public_html/plugins/TwitterBridge/daemons/twitterstatusfetcher.php(217):
>>>>>>> common_broadcast_notice(Object(Notice))
>>>>>>> #5
>>>>>>> /home/site/public_html/plugins/TwitterBridge/daemons/twitterstatusfetcher.php(142):
>>>>>>> TwitterStatusFetcher->getTimeline(Object(Foreign_link))
>>>>>>> #6 /home/site/public_html/lib/parallelizingdaemon.php(125):
>>>>>>> TwitterStatusFetcher->childTask(Object(Foreign_link))
>>>>>>> #7 /home/site/public_html/lib/daemon.php(158):
>>>>>>> ParallelizingDaemon->run()
>>>>>>> #8 /home/site/public_html/plugins/TwitterBridge/daemons/twitterst in
>>>>>>> /home/site/public_html/extlib/Stomp.php on line 210
>>>>>>>
>>>>>>> any ideas?
>>>>>>>
>>>>>>> thanks
>>>>>>>
>>>>>>> Jesse
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> StatusNet-dev mailing list
>>>>>>> [email protected]
>>>>>>> http://lists.status.net/mailman/listinfo/statusnet-dev
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> --------------- FM
>>>>>> Flow with whatever is happening and let your mind be free. Stay
>>>>>> centered by accepting whatever you are doing. This is the ultimate.
>>>>>> - 庄子 (Chuang Tzu)
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
_______________________________________________
StatusNet-dev mailing list
[email protected]
http://lists.status.net/mailman/listinfo/statusnet-dev
