You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Rich Stephens <rs...@sumglobaltech.com> on 2009/08/27 16:50:21 UTC
Errors starting qman WSDM
I'm attempting to use qman WSDM with a qpid-0.5 c++ broker. However, the
admin.jsp page just shows as a blank page, and when I look at the qman.log
file, I see:
2009-08-27 10:42:08,183 ERROR [QManAdapterCapability] <QMAN-100023> : Unable
to build WS artifacts.
org.apache.qpid.management.wsdm.capabilities.ArtifactsNotAvailableException:
org.apache.qpid.management.wsdm.capabilities.BuilderException:
javassist.CannotCompileException: by java.lang.LinkageError: loader
(instance of org/mortbay/jetty/webapp/WebAppClassLoader): attempted
duplicate class definition for name:
"org/apache/qpid/management/wsdm/capabilities/exchange"
The only information I have been able to find so far about this error is at
http://cwiki.apache.org/qpid/qman-error-messages.html, which says: "Using
QMan administration console enable a fine level for WS-DM adapter log. You
should see detailed information about the lifecycle of each managed
resources including generated artifacts." -- well, since I can't use the
admin console at all, this is of course of no help.
Anyone familiar with this error and how I can get the WSDM stuff going?
Thanks,
Rich S.
--
View this message in context: http://n2.nabble.com/Errors-starting-qman-WSDM-tp3526824p3526824.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: Errors starting qman WSDM
Posted by gkolten <ge...@troika.ru>.
Has this been solved ?
I am having the same problem. Exactly as described, but on win xp.
when opening http://localhost:8079/console.jsp getting a blank page.
Appreciate your help
--
View this message in context: http://apache-qpid-users.2158936.n2.nabble.com/Errors-starting-qman-WSDM-tp3526824p5481175.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: Errors starting qman WSDM
Posted by Andrea Gazzarini <ag...@apache.org>.
Any news about this topic?
Andrea
On 8/27/09, Andrea Gazzarini <a....@gmail.com> wrote:
> Yes, you're absolutely right.
>
> I see in your log that the hostname is not localhost but ubuntu so try this
> :
>
> http://ubuntu:8080/qman/console.jsp
>
> Let me know
>
> Regards,
> Andrea
>
>
> 2009/8/27 Rich Stephens <rs...@sumglobaltech.com>
>
>>
>>
>>
>> Andrea Gazzarini-2 wrote:
>> >
>> > Your web server is running on 8080 , not 8079 (this is the admin port)
>> >
>> > Regards
>> > Andrea
>> >
>>
>> I get nothing at all on 8080. Fail to connect at all -- I assume that
>> all
>> I
>> have to do is run qman-wsdm-start.sh, correct? I don't have to have a
>> separate web server running other than what jetty provides in the qman
>> manager stuff?
>>
>> Rich
>> --
>> View this message in context:
>> http://n2.nabble.com/Errors-starting-qman-WSDM-tp3526824p3529160.html
>> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project: http://qpid.apache.org
>> Use/Interact: mailto:users-subscribe@qpid.apache.org
>>
>>
>
--
Sent from my mobile device
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: Errors starting qman WSDM
Posted by Andrea Gazzarini <a....@gmail.com>.
Yes, you're absolutely right.
I see in your log that the hostname is not localhost but ubuntu so try this
:
http://ubuntu:8080/qman/console.jsp
Let me know
Regards,
Andrea
2009/8/27 Rich Stephens <rs...@sumglobaltech.com>
>
>
>
> Andrea Gazzarini-2 wrote:
> >
> > Your web server is running on 8080 , not 8079 (this is the admin port)
> >
> > Regards
> > Andrea
> >
>
> I get nothing at all on 8080. Fail to connect at all -- I assume that all
> I
> have to do is run qman-wsdm-start.sh, correct? I don't have to have a
> separate web server running other than what jetty provides in the qman
> manager stuff?
>
> Rich
> --
> View this message in context:
> http://n2.nabble.com/Errors-starting-qman-WSDM-tp3526824p3529160.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
>
Re: Errors starting qman WSDM
Posted by Rich Stephens <rs...@sumglobaltech.com>.
Andrea Gazzarini-2 wrote:
>
> Your web server is running on 8080 , not 8079 (this is the admin port)
>
> Regards
> Andrea
>
I get nothing at all on 8080. Fail to connect at all -- I assume that all I
have to do is run qman-wsdm-start.sh, correct? I don't have to have a
separate web server running other than what jetty provides in the qman
manager stuff?
Rich
--
View this message in context: http://n2.nabble.com/Errors-starting-qman-WSDM-tp3526824p3529160.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: Errors starting qman WSDM
Posted by Andrea Gazzarini <ag...@apache.org>.
Your web server is running on 8080 , not 8079 (this is the admin port)
Regards
Andrea
On 8/27/09, Andrea Gazzarini <ag...@apache.org> wrote:
> Just half an hour...I'll try to do that... Maybe i remember a wrong url
>
> On 8/27/09, Rich Stephens <rs...@sumglobaltech.com> wrote:
>>
>>
>>
>> Andrea Gazzarini-2 wrote:
>>>
>>> No the url should be
>>> http://host:port/qman/console.jsp
>>>
>>
>> I get a blank page on http://localhost:8079/qman/console.jsp also...
>>
>>
>> --
>> View this message in context:
>> http://n2.nabble.com/Errors-starting-qman-WSDM-tp3526824p3528896.html
>> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project: http://qpid.apache.org
>> Use/Interact: mailto:users-subscribe@qpid.apache.org
>>
>>
>
> --
> Sent from my mobile device
>
--
Sent from my mobile device
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: Errors starting qman WSDM
Posted by Andrea Gazzarini <ag...@apache.org>.
Just half an hour...I'll try to do that... Maybe i remember a wrong url
On 8/27/09, Rich Stephens <rs...@sumglobaltech.com> wrote:
>
>
>
> Andrea Gazzarini-2 wrote:
>>
>> No the url should be
>> http://host:port/qman/console.jsp
>>
>
> I get a blank page on http://localhost:8079/qman/console.jsp also...
>
>
> --
> View this message in context:
> http://n2.nabble.com/Errors-starting-qman-WSDM-tp3526824p3528896.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
>
--
Sent from my mobile device
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: Errors starting qman WSDM
Posted by Rich Stephens <rs...@sumglobaltech.com>.
Andrea Gazzarini-2 wrote:
>
> No the url should be
> http://host:port/qman/console.jsp
>
I get a blank page on http://localhost:8079/qman/console.jsp also...
--
View this message in context: http://n2.nabble.com/Errors-starting-qman-WSDM-tp3526824p3528896.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: Errors starting qman WSDM
Posted by Andrea Gazzarini <ag...@apache.org>.
No the url should be
http://host:port/qman/console.jsp
On 8/27/09, Rich Stephens <rs...@sumglobaltech.com> wrote:
>
> Well, i commented out the broker link in the qman config file, and qman
> appears to have started up without incident, however, I am still not seeing
> anything when I try to hit the admin page. No apparent errors in either the
> qman log or the server log.
>
> I am attempting to hit it with a browser on the local machine using the
> following url: http://localhost:8079/qman/admin.jsp
>
> Is that not the correct url?
>
> WITH the qman broker connect commented out in the config, here are the
> complete logs:
>
> qman:
>
> 2009-08-27 11:41:47,117 INFO [QMan] <QMAN-000001> : Starting Q-Man...
> 2009-08-27 11:41:47,117 INFO [QMan] <QMAN-000002> : Reading Q-Man
> configuration...
> 2009-08-27 11:41:47,173 INFO [QMan] <QMAN-000023> : Q-Man service is now
> available on MBeanServer.
> 2009-08-27 11:41:47,207 INFO [Configuration] <QMAN-000006> : Access Mode
> mapping : code = 1 associated to Read-Create
> 2009-08-27 11:41:47,207 INFO [Configuration] <QMAN-000006> : Access Mode
> mapping : code = 2 associated to Read-Write
> 2009-08-27 11:41:47,207 INFO [Configuration] <QMAN-000006> : Access Mode
> mapping : code = 3 associated to Read-Only
> 2009-08-27 11:41:47,208 INFO [Configuration] <QMAN-000005> : Type mapping :
> code = 1 associated to org.apache.qpid.management.domain.model.type.Uint8
> (wraps java.lang.Short) (validator class is
> org.apache.qpid.management.domain.model.QpidProperty$NumberValidator)
> 2009-08-27 11:41:47,208 INFO [Configuration] <QMAN-000005> : Type mapping :
> code = 2 associated to org.apache.qpid.management.domain.model.type.Uint16
> (wraps java.lang.Integer) (validator class is
> org.apache.qpid.management.domain.model.QpidProperty$NumberValidator)
> 2009-08-27 11:41:47,208 INFO [Configuration] <QMAN-000005> : Type mapping :
> code = 3 associated to org.apache.qpid.management.domain.model.type.Uint32
> (wraps java.lang.Long) (validator class is
> org.apache.qpid.management.domain.model.QpidProperty$NumberValidator)
> 2009-08-27 11:41:47,209 INFO [Configuration] <QMAN-000005> : Type mapping :
> code = 4 associated to org.apache.qpid.management.domain.model.type.Uint64
> (wraps java.lang.Long) (validator class is
> org.apache.qpid.management.domain.model.QpidProperty$NumberValidator)
> 2009-08-27 11:41:47,209 INFO [Configuration] <QMAN-000005> : Type mapping :
> code = 6 associated to org.apache.qpid.management.domain.model.type.Str8
> (wraps java.lang.String) (validator class is
> org.apache.qpid.management.domain.model.QpidProperty$StringValidator)
> 2009-08-27 11:41:47,210 INFO [Configuration] <QMAN-000005> : Type mapping :
> code = 7 associated to org.apache.qpid.management.domain.model.type.Str16
> (wraps java.lang.String) (validator class is
> org.apache.qpid.management.domain.model.QpidProperty$StringValidator)
> 2009-08-27 11:41:47,210 INFO [Configuration] <QMAN-000005> : Type mapping :
> code = 8 associated to org.apache.qpid.management.domain.model.type.AbsTime
> (wraps java.lang.Long) (validator class is not configured for this type.)
> 2009-08-27 11:41:47,210 INFO [Configuration] <QMAN-000005> : Type mapping :
> code = 9 associated to
> org.apache.qpid.management.domain.model.type.DeltaTime (wraps
> java.lang.Long) (validator class is not configured for this type.)
> 2009-08-27 11:41:47,210 INFO [Configuration] <QMAN-000005> : Type mapping :
> code = 10 associated to
> org.apache.qpid.management.domain.model.type.ObjectReference (wraps [B)
> (validator class is not configured for this type.)
> 2009-08-27 11:41:47,211 INFO [Configuration] <QMAN-000005> : Type mapping :
> code = 11 associated to org.apache.qpid.management.domain.model.type.Boolean
> (wraps java.lang.Boolean) (validator class is not configured for this type.)
> 2009-08-27 11:41:47,212 INFO [Configuration] <QMAN-000005> : Type mapping :
> code = 14 associated to org.apache.qpid.management.domain.model.type.Uuid
> (wraps java.util.UUID) (validator class is not configured for this type.)
> 2009-08-27 11:41:47,212 INFO [Configuration] <QMAN-000005> : Type mapping :
> code = 15 associated to org.apache.qpid.management.domain.model.type.Map
> (wraps java.util.Map) (validator class is not configured for this type.)
> 2009-08-27 11:41:47,213 INFO [Configuration] <QMAN-000035> : Work Manager
> thread pool size : 5
> 2009-08-27 11:41:47,213 INFO [Configuration] <QMAN-000036> : Work Manager
> thread pool max size : 15
> 2009-08-27 11:41:47,214 INFO [Configuration] <QMAN-000035> : Work Manager
> keep alive time : 5000
> 2009-08-27 11:41:47,216 INFO [Configuration] <QMAN-000007> : Management
> Queue Message Handler Mapping : opcode = i associated with
> org.apache.qpid.management.domain.handler.impl.InstrumentationMessageHandler
> 2009-08-27 11:41:47,217 INFO [Configuration] <QMAN-000007> : Management
> Queue Message Handler Mapping : opcode = c associated with
> org.apache.qpid.management.domain.handler.impl.ConfigurationMessageHandler
> 2009-08-27 11:41:47,217 INFO [Configuration] <QMAN-000007> : Management
> Queue Message Handler Mapping : opcode = e associated with
> org.apache.qpid.management.domain.handler.impl.EventContentMessageHandler
> 2009-08-27 11:41:47,218 INFO [Configuration] <QMAN-000007> : Management
> Queue Message Handler Mapping : opcode = h associated with
> org.apache.qpid.management.domain.handler.impl.HeartBeatIndicationMessageHandler
> 2009-08-27 11:41:47,220 INFO [Configuration] <QMAN-000008> : Method-Reply
> Queue Message Handler Mapping : opcode = m associated with
> org.apache.qpid.management.domain.handler.impl.MethodResponseMessageHandler
> 2009-08-27 11:41:47,222 INFO [Configuration] <QMAN-000008> : Method-Reply
> Queue Message Handler Mapping : opcode = s associated with
> org.apache.qpid.management.domain.handler.impl.SchemaResponseMessageHandler
> 2009-08-27 11:41:47,226 INFO [QMan] <QMAN-000019> : Q-Man open for
> e-business.
> 2009-08-27 11:41:47,346 INFO [ConnectQManToBroker] <QMAN-000022> : Q-Man
> has no configured broker : in order to connect with a running one use Q-Man
> Administration interface.
> 2009-08-27 11:41:47,363 INFO [WSDMAdapterEnvironment] <QMAN-000029> :
> Default URI will be set to http://ubuntu:8080/qman/services/adapter
> 2009-08-27 11:41:48,464 INFO [QManAdapterCapability] <QMAN-000032> : Events
> lifecycle topic has been created with name
> {http://amqp.apache.org/qpid/management/qman}ObjectsLifeCycleTopic
> 2009-08-27 11:41:48,464 INFO [QManAdapterCapability] <QMAN-000033> :
> Objects lifecycle topic has been created with name
> {http://amqp.apache.org/qpid/management/qman}ObjectsLifeCycleTopic
> 2009-08-27 11:41:48,464 INFO [QManAdapterCapability] <QMAN-000034> :
> Unclassified object types lifecycle topic has been created with name
> {http://amqp.apache.org/qpid/management/qman}ObjectsLifeCycleTopic
> 2009-08-27 11:41:48,466 INFO [QManAdapterCapability] <QMAN-000028> : Qpid
> emulator not found. Test notifications are disabled.
>
> server log:
>
> 2009-08-27 11:41:46,309 INFO [log] Logging to
> org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via
> org.mortbay.log.Slf4jLog
> 2009-08-27 11:41:46,583 INFO [log] jetty-6.1.14
> 2009-08-27 11:41:46,754 WARN [log] Unknown realm: default
> 2009-08-27 11:41:48,504 INFO [log] Started
> SelectChannelConnector@ubuntu:8080
>
>
>
>
>
> --
> View this message in context:
> http://n2.nabble.com/Errors-starting-qman-WSDM-tp3526824p3528542.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
>
--
Sent from my mobile device
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: Errors starting qman WSDM
Posted by Rich Stephens <rs...@sumglobaltech.com>.
Well, i commented out the broker link in the qman config file, and qman
appears to have started up without incident, however, I am still not seeing
anything when I try to hit the admin page. No apparent errors in either the
qman log or the server log.
I am attempting to hit it with a browser on the local machine using the
following url: http://localhost:8079/qman/admin.jsp
Is that not the correct url?
WITH the qman broker connect commented out in the config, here are the
complete logs:
qman:
2009-08-27 11:41:47,117 INFO [QMan] <QMAN-000001> : Starting Q-Man...
2009-08-27 11:41:47,117 INFO [QMan] <QMAN-000002> : Reading Q-Man
configuration...
2009-08-27 11:41:47,173 INFO [QMan] <QMAN-000023> : Q-Man service is now
available on MBeanServer.
2009-08-27 11:41:47,207 INFO [Configuration] <QMAN-000006> : Access Mode
mapping : code = 1 associated to Read-Create
2009-08-27 11:41:47,207 INFO [Configuration] <QMAN-000006> : Access Mode
mapping : code = 2 associated to Read-Write
2009-08-27 11:41:47,207 INFO [Configuration] <QMAN-000006> : Access Mode
mapping : code = 3 associated to Read-Only
2009-08-27 11:41:47,208 INFO [Configuration] <QMAN-000005> : Type mapping :
code = 1 associated to org.apache.qpid.management.domain.model.type.Uint8
(wraps java.lang.Short) (validator class is
org.apache.qpid.management.domain.model.QpidProperty$NumberValidator)
2009-08-27 11:41:47,208 INFO [Configuration] <QMAN-000005> : Type mapping :
code = 2 associated to org.apache.qpid.management.domain.model.type.Uint16
(wraps java.lang.Integer) (validator class is
org.apache.qpid.management.domain.model.QpidProperty$NumberValidator)
2009-08-27 11:41:47,208 INFO [Configuration] <QMAN-000005> : Type mapping :
code = 3 associated to org.apache.qpid.management.domain.model.type.Uint32
(wraps java.lang.Long) (validator class is
org.apache.qpid.management.domain.model.QpidProperty$NumberValidator)
2009-08-27 11:41:47,209 INFO [Configuration] <QMAN-000005> : Type mapping :
code = 4 associated to org.apache.qpid.management.domain.model.type.Uint64
(wraps java.lang.Long) (validator class is
org.apache.qpid.management.domain.model.QpidProperty$NumberValidator)
2009-08-27 11:41:47,209 INFO [Configuration] <QMAN-000005> : Type mapping :
code = 6 associated to org.apache.qpid.management.domain.model.type.Str8
(wraps java.lang.String) (validator class is
org.apache.qpid.management.domain.model.QpidProperty$StringValidator)
2009-08-27 11:41:47,210 INFO [Configuration] <QMAN-000005> : Type mapping :
code = 7 associated to org.apache.qpid.management.domain.model.type.Str16
(wraps java.lang.String) (validator class is
org.apache.qpid.management.domain.model.QpidProperty$StringValidator)
2009-08-27 11:41:47,210 INFO [Configuration] <QMAN-000005> : Type mapping :
code = 8 associated to org.apache.qpid.management.domain.model.type.AbsTime
(wraps java.lang.Long) (validator class is not configured for this type.)
2009-08-27 11:41:47,210 INFO [Configuration] <QMAN-000005> : Type mapping :
code = 9 associated to
org.apache.qpid.management.domain.model.type.DeltaTime (wraps
java.lang.Long) (validator class is not configured for this type.)
2009-08-27 11:41:47,210 INFO [Configuration] <QMAN-000005> : Type mapping :
code = 10 associated to
org.apache.qpid.management.domain.model.type.ObjectReference (wraps [B)
(validator class is not configured for this type.)
2009-08-27 11:41:47,211 INFO [Configuration] <QMAN-000005> : Type mapping :
code = 11 associated to org.apache.qpid.management.domain.model.type.Boolean
(wraps java.lang.Boolean) (validator class is not configured for this type.)
2009-08-27 11:41:47,212 INFO [Configuration] <QMAN-000005> : Type mapping :
code = 14 associated to org.apache.qpid.management.domain.model.type.Uuid
(wraps java.util.UUID) (validator class is not configured for this type.)
2009-08-27 11:41:47,212 INFO [Configuration] <QMAN-000005> : Type mapping :
code = 15 associated to org.apache.qpid.management.domain.model.type.Map
(wraps java.util.Map) (validator class is not configured for this type.)
2009-08-27 11:41:47,213 INFO [Configuration] <QMAN-000035> : Work Manager
thread pool size : 5
2009-08-27 11:41:47,213 INFO [Configuration] <QMAN-000036> : Work Manager
thread pool max size : 15
2009-08-27 11:41:47,214 INFO [Configuration] <QMAN-000035> : Work Manager
keep alive time : 5000
2009-08-27 11:41:47,216 INFO [Configuration] <QMAN-000007> : Management
Queue Message Handler Mapping : opcode = i associated with
org.apache.qpid.management.domain.handler.impl.InstrumentationMessageHandler
2009-08-27 11:41:47,217 INFO [Configuration] <QMAN-000007> : Management
Queue Message Handler Mapping : opcode = c associated with
org.apache.qpid.management.domain.handler.impl.ConfigurationMessageHandler
2009-08-27 11:41:47,217 INFO [Configuration] <QMAN-000007> : Management
Queue Message Handler Mapping : opcode = e associated with
org.apache.qpid.management.domain.handler.impl.EventContentMessageHandler
2009-08-27 11:41:47,218 INFO [Configuration] <QMAN-000007> : Management
Queue Message Handler Mapping : opcode = h associated with
org.apache.qpid.management.domain.handler.impl.HeartBeatIndicationMessageHandler
2009-08-27 11:41:47,220 INFO [Configuration] <QMAN-000008> : Method-Reply
Queue Message Handler Mapping : opcode = m associated with
org.apache.qpid.management.domain.handler.impl.MethodResponseMessageHandler
2009-08-27 11:41:47,222 INFO [Configuration] <QMAN-000008> : Method-Reply
Queue Message Handler Mapping : opcode = s associated with
org.apache.qpid.management.domain.handler.impl.SchemaResponseMessageHandler
2009-08-27 11:41:47,226 INFO [QMan] <QMAN-000019> : Q-Man open for
e-business.
2009-08-27 11:41:47,346 INFO [ConnectQManToBroker] <QMAN-000022> : Q-Man
has no configured broker : in order to connect with a running one use Q-Man
Administration interface.
2009-08-27 11:41:47,363 INFO [WSDMAdapterEnvironment] <QMAN-000029> :
Default URI will be set to http://ubuntu:8080/qman/services/adapter
2009-08-27 11:41:48,464 INFO [QManAdapterCapability] <QMAN-000032> : Events
lifecycle topic has been created with name
{http://amqp.apache.org/qpid/management/qman}ObjectsLifeCycleTopic
2009-08-27 11:41:48,464 INFO [QManAdapterCapability] <QMAN-000033> :
Objects lifecycle topic has been created with name
{http://amqp.apache.org/qpid/management/qman}ObjectsLifeCycleTopic
2009-08-27 11:41:48,464 INFO [QManAdapterCapability] <QMAN-000034> :
Unclassified object types lifecycle topic has been created with name
{http://amqp.apache.org/qpid/management/qman}ObjectsLifeCycleTopic
2009-08-27 11:41:48,466 INFO [QManAdapterCapability] <QMAN-000028> : Qpid
emulator not found. Test notifications are disabled.
server log:
2009-08-27 11:41:46,309 INFO [log] Logging to
org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via
org.mortbay.log.Slf4jLog
2009-08-27 11:41:46,583 INFO [log] jetty-6.1.14
2009-08-27 11:41:46,754 WARN [log] Unknown realm: default
2009-08-27 11:41:48,504 INFO [log] Started
SelectChannelConnector@ubuntu:8080
--
View this message in context: http://n2.nabble.com/Errors-starting-qman-WSDM-tp3526824p3528542.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: Errors starting qman WSDM
Posted by Andrea Gazzarini <ag...@apache.org>.
Another way, (just to be sure that all activity is logged)
- stop QMan
- edit $QMAN_HOME/cnf/log4j.xml
- change level for the following categories from INFO to DEBUG
<!-- Category for QMan module -->
<category name="org.apache.qpid.management">
<priority value="INFO" />
<appender-ref ref="QMAN_LOG" />
</category>
<category name="org.apache.qpid.qman.debug.XmlDebugger">
<priority value="INFO" />
<appender-ref ref="MESSAGES_LOG" />
</category>
<category name="org.apache.qpid.qman.debug.WsdlDebugger">
<priority value="INFO" />
<appender-ref ref="MESSAGES_LOG" />
</category>
<root>
<priority value="ERROR" />
</root>
- restart QMan (without modifying your qman-config.xml)
- post the qman.log
Regards,
Andrea
2009/8/27 Andrea Gazzarini <ag...@apache.org>
> Otherwise please post the current complete stack trace...
>
> "2009-08-27 10:42:08,183 ERROR [QManAdapterCapability] <QMAN-100023> :
> Unable
> to build WS artifacts.
>
> org.apache.qpid.management.wsdm.capabilities.ArtifactsNotAvailableException:
> org.apache.qpid.management.wsdm.capabilities.BuilderException:
> javassist.CannotCompileException: by java.lang.LinkageError: loader
> (instance of org/mortbay/jetty/webapp/WebAppClassLoader): attempted
> duplicate class definition for name:
> "org/apache/qpid/management/wsdm/capabilities/exchange""
> I believe there should be something else...
>
> 2009/8/27 Andrea Gazzarini <ag...@apache.org>
>
> Hi Rich,
>> Probably you are starting qman using a config file with a broker
>> connection data... Qman at startup tries to connect with the broker
>> and you immediately get that error.
>> I believe that an error like that shouldn't invalidate the console (it
>> has nothing to do with that) so this is a first problem that i'm
>> seèing.
>> Now concerning the underlying problem you should :
>>
>> - stop qman
>> - comment broker connection data on qman-config.xml.
>> - start qman
>> - change log level of wsdm bùilder on the console
>> - reconnect with the broker using console
>> - post the log
>>
>> Regards
>> Andrea
>>
>> On 8/27/09, Rich Stephens <rs...@sumglobaltech.com> wrote:
>> >
>> > I'm attempting to use qman WSDM with a qpid-0.5 c++ broker. However,
>> the
>> > admin.jsp page just shows as a blank page, and when I look at the
>> qman.log
>> > file, I see:
>> >
>> > 2009-08-27 10:42:08,183 ERROR [QManAdapterCapability] <QMAN-100023> :
>> Unable
>> > to build WS artifacts.
>> >
>> org.apache.qpid.management.wsdm.capabilities.ArtifactsNotAvailableException:
>> > org.apache.qpid.management.wsdm.capabilities.BuilderException:
>> > javassist.CannotCompileException: by java.lang.LinkageError: loader
>> > (instance of org/mortbay/jetty/webapp/WebAppClassLoader): attempted
>> > duplicate class definition for name:
>> > "org/apache/qpid/management/wsdm/capabilities/exchange"
>> >
>> > The only information I have been able to find so far about this error is
>> at
>> > http://cwiki.apache.org/qpid/qman-error-messages.html, which says:
>> "Using
>> > QMan administration console enable a fine level for WS-DM adapter log.
>> You
>> > should see detailed information about the lifecycle of each managed
>> > resources including generated artifacts." -- well, since I can't use the
>> > admin console at all, this is of course of no help.
>> >
>> > Anyone familiar with this error and how I can get the WSDM stuff going?
>> >
>> > Thanks,
>> > Rich S.
>> > --
>> > View this message in context:
>> > http://n2.nabble.com/Errors-starting-qman-WSDM-tp3526824p3526824.html
>> > Sent from the Apache Qpid users mailing list archive at Nabble.com.
>> >
>> > ---------------------------------------------------------------------
>> > Apache Qpid - AMQP Messaging Implementation
>> > Project: http://qpid.apache.org
>> > Use/Interact: mailto:users-subscribe@qpid.apache.org
>> >
>> >
>>
>> --
>> Sent from my mobile device
>>
>
>
Re: Errors starting qman WSDM
Posted by Andrea Gazzarini <ag...@apache.org>.
Otherwise please post the current complete stack trace...
"2009-08-27 10:42:08,183 ERROR [QManAdapterCapability] <QMAN-100023> :
Unable
to build WS artifacts.
org.apache.qpid.management.wsdm.capabilities.ArtifactsNotAvailableException:
org.apache.qpid.management.wsdm.capabilities.BuilderException:
javassist.CannotCompileException: by java.lang.LinkageError: loader
(instance of org/mortbay/jetty/webapp/WebAppClassLoader): attempted
duplicate class definition for name:
"org/apache/qpid/management/wsdm/capabilities/exchange""
I believe there should be something else...
2009/8/27 Andrea Gazzarini <ag...@apache.org>
> Hi Rich,
> Probably you are starting qman using a config file with a broker
> connection data... Qman at startup tries to connect with the broker
> and you immediately get that error.
> I believe that an error like that shouldn't invalidate the console (it
> has nothing to do with that) so this is a first problem that i'm
> seèing.
> Now concerning the underlying problem you should :
>
> - stop qman
> - comment broker connection data on qman-config.xml.
> - start qman
> - change log level of wsdm bùilder on the console
> - reconnect with the broker using console
> - post the log
>
> Regards
> Andrea
>
> On 8/27/09, Rich Stephens <rs...@sumglobaltech.com> wrote:
> >
> > I'm attempting to use qman WSDM with a qpid-0.5 c++ broker. However, the
> > admin.jsp page just shows as a blank page, and when I look at the
> qman.log
> > file, I see:
> >
> > 2009-08-27 10:42:08,183 ERROR [QManAdapterCapability] <QMAN-100023> :
> Unable
> > to build WS artifacts.
> >
> org.apache.qpid.management.wsdm.capabilities.ArtifactsNotAvailableException:
> > org.apache.qpid.management.wsdm.capabilities.BuilderException:
> > javassist.CannotCompileException: by java.lang.LinkageError: loader
> > (instance of org/mortbay/jetty/webapp/WebAppClassLoader): attempted
> > duplicate class definition for name:
> > "org/apache/qpid/management/wsdm/capabilities/exchange"
> >
> > The only information I have been able to find so far about this error is
> at
> > http://cwiki.apache.org/qpid/qman-error-messages.html, which says:
> "Using
> > QMan administration console enable a fine level for WS-DM adapter log.
> You
> > should see detailed information about the lifecycle of each managed
> > resources including generated artifacts." -- well, since I can't use the
> > admin console at all, this is of course of no help.
> >
> > Anyone familiar with this error and how I can get the WSDM stuff going?
> >
> > Thanks,
> > Rich S.
> > --
> > View this message in context:
> > http://n2.nabble.com/Errors-starting-qman-WSDM-tp3526824p3526824.html
> > Sent from the Apache Qpid users mailing list archive at Nabble.com.
> >
> > ---------------------------------------------------------------------
> > Apache Qpid - AMQP Messaging Implementation
> > Project: http://qpid.apache.org
> > Use/Interact: mailto:users-subscribe@qpid.apache.org
> >
> >
>
> --
> Sent from my mobile device
>
Re: Errors starting qman WSDM
Posted by Andrea Gazzarini <ag...@apache.org>.
Hi Rich,
Probably you are starting qman using a config file with a broker
connection data... Qman at startup tries to connect with the broker
and you immediately get that error.
I believe that an error like that shouldn't invalidate the console (it
has nothing to do with that) so this is a first problem that i'm
seèing.
Now concerning the underlying problem you should :
- stop qman
- comment broker connection data on qman-config.xml.
- start qman
- change log level of wsdm bùilder on the console
- reconnect with the broker using console
- post the log
Regards
Andrea
On 8/27/09, Rich Stephens <rs...@sumglobaltech.com> wrote:
>
> I'm attempting to use qman WSDM with a qpid-0.5 c++ broker. However, the
> admin.jsp page just shows as a blank page, and when I look at the qman.log
> file, I see:
>
> 2009-08-27 10:42:08,183 ERROR [QManAdapterCapability] <QMAN-100023> : Unable
> to build WS artifacts.
> org.apache.qpid.management.wsdm.capabilities.ArtifactsNotAvailableException:
> org.apache.qpid.management.wsdm.capabilities.BuilderException:
> javassist.CannotCompileException: by java.lang.LinkageError: loader
> (instance of org/mortbay/jetty/webapp/WebAppClassLoader): attempted
> duplicate class definition for name:
> "org/apache/qpid/management/wsdm/capabilities/exchange"
>
> The only information I have been able to find so far about this error is at
> http://cwiki.apache.org/qpid/qman-error-messages.html, which says: "Using
> QMan administration console enable a fine level for WS-DM adapter log. You
> should see detailed information about the lifecycle of each managed
> resources including generated artifacts." -- well, since I can't use the
> admin console at all, this is of course of no help.
>
> Anyone familiar with this error and how I can get the WSDM stuff going?
>
> Thanks,
> Rich S.
> --
> View this message in context:
> http://n2.nabble.com/Errors-starting-qman-WSDM-tp3526824p3526824.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
>
--
Sent from my mobile device
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org