On 01/07/2011 20:49, Dark Before Dawn wrote:
> Hi Pid, hi Cuck!
> thanks for your help. Your suggestions fixed the naming issues :) thank=
s!
>=20
> But the error still occurs.
>=20
> FAIL - Encountered exception javax.management.InstanceNotFoundException=
: Tomcat:type=3DDeployer,host=3Dlocalhost
The Deployer isn't in the list of MBeans visible in your JConsole
screenshot, which is probably why you can't connect to it.
I don't know why that is, but presumably the embedded code doesn't
enable it.
> I noticed an empty javax.management.ObjectName[0] Array, when browsing =
Servlet via jconsole. This could be in correlation to the exception above=
=2E
The two things are not related. The empty array refers to child objects
of the servlet (should there be any? no...), not the webapp.
p
> See screenshots for further reference.
>=20
> If this is over we definitively need to grab some beer, I am buying :)
>=20
>=20
>=20
>=20
> Am 01.07.2011 17:54, schrieb Pid:
>> On 01/07/2011 12:44, Dark Before Dawn wrote:
>>> Hi Pid,
>>> i guess the problem is that the manager-servlet's context is "mounted=
"
>>> at root and the ServletMapping points to /manager.
>>>
>>>> server.addContext("", baseDirectory);
>>>> ctx.addServletMapping("/manager/*", manager-servlet);
>>> So all relative paths will point to root
>> That's easy to change, no?
>>
>> server.addContext("/manager", baseDirectory);
>> ctx.addServletMapping("/text/*", manager-servlet);
>>
>> Note the additional '*' in the security collection:
>>
>> collection.addPattern("/text/*");
>>
>> (The role usually assigned for the text manager servlet is "manager-sc=
ript")
>>
>>
>> p
>>
>>
>>> ie:
>>>
>>> localhost/manager/html vs localhost/html
>>>
>>> I don't know what I am exactly searching for at jconsole, so here is =
a overview :)
>>> Thnx and cheers
>>> Darky
>>>
>>>
>>>
>>>
>>> Am 01.07.2011 12:46, schrieb Pid:
>>>> On 01/07/2011 10:40, Dark Before Dawn wrote:
>>>>> Hi again,
>>>>> this is realy driving me nuts for weeks :)
>>>>> FAIL - Encountered exception javax.management.InstanceNotFoundExcep=
tion:
>>>>> Tomcat:type=3DDeployer,host=3Dlocalhost
>>>> 1. Connect to your running instance with JConsole*.
>>>> 2. Examine the MBeans published by the instance.
>>>> 3. Confirm that you are connecting to the correct MBean.
>>>>
>>>>
>>>> I wouldn't expect:
>>>>
>>>> "Tomcat:type=3DDeployer,host=3Dlocalhost"
>>>>
>>>> to work.
>>>>
>>>>
>>>> p
>>>>
>>>>
>>>> * or VisualVM with the JConsole plugin enabled.
>>>>
>>
>=20
|