You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hivemind.apache.org by Hugo Palma <hu...@gmail.com> on 2007/04/13 17:33:09 UTC
JMX in weblogic 8
Hi all,
i'm trying to use hivemind-jmx in weblogic 8.
I'm getting the following error below when i try to register the
NamingServiceMBean. It seems to me that it's trying to create another rmi
server.
The question is, why doesn't it connect to the existing server instead of
trying to register a new one ?
Also, weblogic 8 JMX implementation is version 1.0. Could that be the cause
?
java.rmi.server.ExportException: internal error: ObjID already in use
at sun.rmi.transport.ObjectTable.putTarget(ObjectTable.java:168)
at sun.rmi.transport.Transport.exportObject(Transport.java:69)
at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java
:190)
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java
:145)
at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92)
at sun.rmi.registry.RegistryImpl. (RegistryImpl.java:78)
at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java
:164)
at org.apache.hivemind.management.mbeans.NamingService.start(
NamingService.java:80)
... 56 more
Thanks,
Hugo
Re: JMX in weblogic 8
Posted by Hugo Palma <hu...@gmail.com>.
Right now i'm just trying to find them using MC4J JMX console......
On 4/14/07, Achim Hügen <ac...@gmx.de> wrote:
>
> Actually, there is no success logging, so the registration
> probably was successful.
> How do you access the mbeans?
>
> Achim
>
> Am Fri, 13 Apr 2007 19:42:09 +0200 schrieb Hugo Palma
> <hu...@gmail.com>:
>
> > me again :o)
> >
> > I found this log from MBeanRegistry:
> >
> > "Trying to register MBean hivemind:id=LogManagementMBean,module=
> > hivemind.management.log4j,type=service"
> >
> > although i get no success log after this.
> >
> >
> >
> > On 4/13/07, Hugo Palma <hu...@gmail.com> wrote:
> >>
> >> i also can't find any logs made by the LogManagementMBean. Is there any
> >> way i can know if it gets registered ?
> >>
> >> On 4/13/07, Hugo Palma < hugo.m.palma@gmail.com> wrote:
> >> >
> >> > Not quite :o)
> >> >
> >> > I don't get any errors logged but i also don't see any new MBean
> >> > registered.
> >> > Here's my hivemodule:
> >> >
> >> > <contribution configuration-id="hivemind.EagerLoad">
> >> > <load service-id=" hivemind.management.MBeanRegistry"/>
> >> > </contribution>
> >> >
> >> > <contribution configuration-id="hivemind.management.MBeans">
> >> > <mbean service-id="
> >> > hivemind.management.connector.JMXConnectorServerMBean "
> >> > start-method="start"/>
> >> > <mbean
> >> service-id="hivemind.management.log4j.LogManagementMBean
> >> > "/>
> >> > </contribution>
> >> >
> >> > <contribution configuration-id="
> >> > hivemind.management.log4j.ManagedLog4jLoggers ">
> >> > <logger name="*"/>
> >> > </contribution>
> >> >
> >> > Any ideas ? again.....
> >> >
> >> > Thanks,
> >> >
> >> > Hugo
> >> >
> >> > On 4/13/07, Hugo Palma <hu...@gmail.com> wrote:
> >> > >
> >> > > That was it....
> >> > > Thanks
> >> > >
> >> > > On 4/13/07, Achim Hügen < achim.huegen@gmx.de> wrote:
> >> > > >
> >> > > > Hugo,
> >> > > >
> >> > > > the rmi registry probably gets created because you have these
> >> lines
> >> > > > in
> >> > > > your descriptor:
> >> > > >
> >> > > > <contribution configuration-id="hivemind.management.MBeans">
> >> > > > <mbean service-id="
> >> > > > hivemind.management.connector.NamingServiceMBean"
> >> > > > start-method="start" />
> >> > > > </contribution>
> >> > > >
> >> > > > Just leave the NamingServiceMBean out of the config and the
> >> running
> >> > > > rmi
> >> > > > registry should be used.
> >> > > >
> >> > > > There might be problems with jmx 1.0 when the MBeanServerFactory
> >> is
> >> > > > located or created
> >> > > > and I don't expect the jsr 160 connectors to work, but just give
> >> it
> >> > > > a try.
> >> > > >
> >> > > > Achim
> >> > > >
> >> > > > Hugo Palma schrieb:
> >> > > > > Hi all,
> >> > > > >
> >> > > > > i'm trying to use hivemind-jmx in weblogic 8.
> >> > > > > I'm getting the following error below when i try to register
> the
> >> > > > > NamingServiceMBean. It seems to me that it's trying to create
> >> > > > another
> >> > > > > rmi server.
> >> > > > > The question is, why doesn't it connect to the existing server
> >> > > > instead
> >> > > > > of trying to register a new one ?
> >> > > > >
> >> > > > > Also, weblogic 8 JMX implementation is version 1.0. Could that
> >> be
> >> > > > the
> >> > > > > cause ?
> >> > > > >
> >> > > > > java.rmi.server.ExportException : internal error: ObjID already
> >> in
> >> > > > use
> >> > > > > at sun.rmi.transport.ObjectTable.putTarget(ObjectTable.java
> >> > > > :168)
> >> > > > > at sun.rmi.transport.Transport.exportObject (Transport.java
> >> > > > :69)
> >> > > > > at sun.rmi.transport.tcp.TCPTransport.exportObject
> >> > > > > (TCPTransport.java:190)
> >> > > > > at
> >> > > > > sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java
> >> > > > :382)
> >> > > > > at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
> >> > > > > at sun.rmi.server.UnicastServerRef.exportObject
> >> > > > > (UnicastServerRef.java:145)
> >> > > > > at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java
> >> :92)
> >> > > > > at sun.rmi.registry.RegistryImpl. (RegistryImpl.java:78)
> >> > > > > at
> >> > > > > java.rmi.registry.LocateRegistry.createRegistry(
> >> > > > LocateRegistry.java :164)
> >> > > > > at
> >> > > > > org.apache.hivemind.management.mbeans.NamingService.start (
> >> > > > NamingService.java:80)
> >> > > > > ... 56 more
> >> > > > >
> >> > > > >
> >> > > > > Thanks,
> >> > > > >
> >> > > > > Hugo
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
>
>
>
Re: JMX in weblogic 8
Posted by Hugo Palma <hu...@gmail.com>.
phew, finally got this working......
In order to get this to work i had to provide my own MBeanServerFactory
implementation. My guess is that as weblogic JMX server is 1.0 the default
implementation was returning the wrong server instance. Anyway, in my
implementation all i have to do is get the correct server instance from the
server JNDI tree.
And that's it, everything works fine now....
Thanks Achim for all the tips....
On 4/14/07, Achim Hügen <ac...@gmx.de> wrote:
>
> Actually, there is no success logging, so the registration
> probably was successful.
> How do you access the mbeans?
>
> Achim
>
> Am Fri, 13 Apr 2007 19:42:09 +0200 schrieb Hugo Palma
> <hu...@gmail.com>:
>
> > me again :o)
> >
> > I found this log from MBeanRegistry:
> >
> > "Trying to register MBean hivemind:id=LogManagementMBean,module=
> > hivemind.management.log4j,type=service"
> >
> > although i get no success log after this.
> >
> >
> >
> > On 4/13/07, Hugo Palma <hu...@gmail.com> wrote:
> >>
> >> i also can't find any logs made by the LogManagementMBean. Is there any
> >> way i can know if it gets registered ?
> >>
> >> On 4/13/07, Hugo Palma < hugo.m.palma@gmail.com> wrote:
> >> >
> >> > Not quite :o)
> >> >
> >> > I don't get any errors logged but i also don't see any new MBean
> >> > registered.
> >> > Here's my hivemodule:
> >> >
> >> > <contribution configuration-id="hivemind.EagerLoad">
> >> > <load service-id=" hivemind.management.MBeanRegistry"/>
> >> > </contribution>
> >> >
> >> > <contribution configuration-id="hivemind.management.MBeans">
> >> > <mbean service-id="
> >> > hivemind.management.connector.JMXConnectorServerMBean "
> >> > start-method="start"/>
> >> > <mbean
> >> service-id="hivemind.management.log4j.LogManagementMBean
> >> > "/>
> >> > </contribution>
> >> >
> >> > <contribution configuration-id="
> >> > hivemind.management.log4j.ManagedLog4jLoggers ">
> >> > <logger name="*"/>
> >> > </contribution>
> >> >
> >> > Any ideas ? again.....
> >> >
> >> > Thanks,
> >> >
> >> > Hugo
> >> >
> >> > On 4/13/07, Hugo Palma <hu...@gmail.com> wrote:
> >> > >
> >> > > That was it....
> >> > > Thanks
> >> > >
> >> > > On 4/13/07, Achim Hügen < achim.huegen@gmx.de> wrote:
> >> > > >
> >> > > > Hugo,
> >> > > >
> >> > > > the rmi registry probably gets created because you have these
> >> lines
> >> > > > in
> >> > > > your descriptor:
> >> > > >
> >> > > > <contribution configuration-id="hivemind.management.MBeans">
> >> > > > <mbean service-id="
> >> > > > hivemind.management.connector.NamingServiceMBean"
> >> > > > start-method="start" />
> >> > > > </contribution>
> >> > > >
> >> > > > Just leave the NamingServiceMBean out of the config and the
> >> running
> >> > > > rmi
> >> > > > registry should be used.
> >> > > >
> >> > > > There might be problems with jmx 1.0 when the MBeanServerFactory
> >> is
> >> > > > located or created
> >> > > > and I don't expect the jsr 160 connectors to work, but just give
> >> it
> >> > > > a try.
> >> > > >
> >> > > > Achim
> >> > > >
> >> > > > Hugo Palma schrieb:
> >> > > > > Hi all,
> >> > > > >
> >> > > > > i'm trying to use hivemind-jmx in weblogic 8.
> >> > > > > I'm getting the following error below when i try to register
> the
> >> > > > > NamingServiceMBean. It seems to me that it's trying to create
> >> > > > another
> >> > > > > rmi server.
> >> > > > > The question is, why doesn't it connect to the existing server
> >> > > > instead
> >> > > > > of trying to register a new one ?
> >> > > > >
> >> > > > > Also, weblogic 8 JMX implementation is version 1.0. Could that
> >> be
> >> > > > the
> >> > > > > cause ?
> >> > > > >
> >> > > > > java.rmi.server.ExportException : internal error: ObjID already
> >> in
> >> > > > use
> >> > > > > at sun.rmi.transport.ObjectTable.putTarget(ObjectTable.java
> >> > > > :168)
> >> > > > > at sun.rmi.transport.Transport.exportObject (Transport.java
> >> > > > :69)
> >> > > > > at sun.rmi.transport.tcp.TCPTransport.exportObject
> >> > > > > (TCPTransport.java:190)
> >> > > > > at
> >> > > > > sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java
> >> > > > :382)
> >> > > > > at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
> >> > > > > at sun.rmi.server.UnicastServerRef.exportObject
> >> > > > > (UnicastServerRef.java:145)
> >> > > > > at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java
> >> :92)
> >> > > > > at sun.rmi.registry.RegistryImpl. (RegistryImpl.java:78)
> >> > > > > at
> >> > > > > java.rmi.registry.LocateRegistry.createRegistry(
> >> > > > LocateRegistry.java :164)
> >> > > > > at
> >> > > > > org.apache.hivemind.management.mbeans.NamingService.start (
> >> > > > NamingService.java:80)
> >> > > > > ... 56 more
> >> > > > >
> >> > > > >
> >> > > > > Thanks,
> >> > > > >
> >> > > > > Hugo
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
>
>
>
Re: JMX in weblogic 8
Posted by Achim Hügen <ac...@gmx.de>.
Actually, there is no success logging, so the registration
probably was successful.
How do you access the mbeans?
Achim
Am Fri, 13 Apr 2007 19:42:09 +0200 schrieb Hugo Palma
<hu...@gmail.com>:
> me again :o)
>
> I found this log from MBeanRegistry:
>
> "Trying to register MBean hivemind:id=LogManagementMBean,module=
> hivemind.management.log4j,type=service"
>
> although i get no success log after this.
>
>
>
> On 4/13/07, Hugo Palma <hu...@gmail.com> wrote:
>>
>> i also can't find any logs made by the LogManagementMBean. Is there any
>> way i can know if it gets registered ?
>>
>> On 4/13/07, Hugo Palma < hugo.m.palma@gmail.com> wrote:
>> >
>> > Not quite :o)
>> >
>> > I don't get any errors logged but i also don't see any new MBean
>> > registered.
>> > Here's my hivemodule:
>> >
>> > <contribution configuration-id="hivemind.EagerLoad">
>> > <load service-id=" hivemind.management.MBeanRegistry"/>
>> > </contribution>
>> >
>> > <contribution configuration-id="hivemind.management.MBeans">
>> > <mbean service-id="
>> > hivemind.management.connector.JMXConnectorServerMBean "
>> > start-method="start"/>
>> > <mbean
>> service-id="hivemind.management.log4j.LogManagementMBean
>> > "/>
>> > </contribution>
>> >
>> > <contribution configuration-id="
>> > hivemind.management.log4j.ManagedLog4jLoggers ">
>> > <logger name="*"/>
>> > </contribution>
>> >
>> > Any ideas ? again.....
>> >
>> > Thanks,
>> >
>> > Hugo
>> >
>> > On 4/13/07, Hugo Palma <hu...@gmail.com> wrote:
>> > >
>> > > That was it....
>> > > Thanks
>> > >
>> > > On 4/13/07, Achim Hügen < achim.huegen@gmx.de> wrote:
>> > > >
>> > > > Hugo,
>> > > >
>> > > > the rmi registry probably gets created because you have these
>> lines
>> > > > in
>> > > > your descriptor:
>> > > >
>> > > > <contribution configuration-id="hivemind.management.MBeans">
>> > > > <mbean service-id="
>> > > > hivemind.management.connector.NamingServiceMBean"
>> > > > start-method="start" />
>> > > > </contribution>
>> > > >
>> > > > Just leave the NamingServiceMBean out of the config and the
>> running
>> > > > rmi
>> > > > registry should be used.
>> > > >
>> > > > There might be problems with jmx 1.0 when the MBeanServerFactory
>> is
>> > > > located or created
>> > > > and I don't expect the jsr 160 connectors to work, but just give
>> it
>> > > > a try.
>> > > >
>> > > > Achim
>> > > >
>> > > > Hugo Palma schrieb:
>> > > > > Hi all,
>> > > > >
>> > > > > i'm trying to use hivemind-jmx in weblogic 8.
>> > > > > I'm getting the following error below when i try to register the
>> > > > > NamingServiceMBean. It seems to me that it's trying to create
>> > > > another
>> > > > > rmi server.
>> > > > > The question is, why doesn't it connect to the existing server
>> > > > instead
>> > > > > of trying to register a new one ?
>> > > > >
>> > > > > Also, weblogic 8 JMX implementation is version 1.0. Could that
>> be
>> > > > the
>> > > > > cause ?
>> > > > >
>> > > > > java.rmi.server.ExportException : internal error: ObjID already
>> in
>> > > > use
>> > > > > at sun.rmi.transport.ObjectTable.putTarget(ObjectTable.java
>> > > > :168)
>> > > > > at sun.rmi.transport.Transport.exportObject (Transport.java
>> > > > :69)
>> > > > > at sun.rmi.transport.tcp.TCPTransport.exportObject
>> > > > > (TCPTransport.java:190)
>> > > > > at
>> > > > > sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java
>> > > > :382)
>> > > > > at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
>> > > > > at sun.rmi.server.UnicastServerRef.exportObject
>> > > > > (UnicastServerRef.java:145)
>> > > > > at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java
>> :92)
>> > > > > at sun.rmi.registry.RegistryImpl. (RegistryImpl.java:78)
>> > > > > at
>> > > > > java.rmi.registry.LocateRegistry.createRegistry(
>> > > > LocateRegistry.java :164)
>> > > > > at
>> > > > > org.apache.hivemind.management.mbeans.NamingService.start (
>> > > > NamingService.java:80)
>> > > > > ... 56 more
>> > > > >
>> > > > >
>> > > > > Thanks,
>> > > > >
>> > > > > Hugo
>> > > >
>> > > >
>> > >
>> >
>>
Re: JMX in weblogic 8
Posted by Hugo Palma <hu...@gmail.com>.
me again :o)
I found this log from MBeanRegistry:
"Trying to register MBean hivemind:id=LogManagementMBean,module=
hivemind.management.log4j,type=service"
although i get no success log after this.
On 4/13/07, Hugo Palma <hu...@gmail.com> wrote:
>
> i also can't find any logs made by the LogManagementMBean. Is there any
> way i can know if it gets registered ?
>
> On 4/13/07, Hugo Palma < hugo.m.palma@gmail.com> wrote:
> >
> > Not quite :o)
> >
> > I don't get any errors logged but i also don't see any new MBean
> > registered.
> > Here's my hivemodule:
> >
> > <contribution configuration-id="hivemind.EagerLoad">
> > <load service-id=" hivemind.management.MBeanRegistry"/>
> > </contribution>
> >
> > <contribution configuration-id="hivemind.management.MBeans">
> > <mbean service-id="
> > hivemind.management.connector.JMXConnectorServerMBean "
> > start-method="start"/>
> > <mbean service-id="hivemind.management.log4j.LogManagementMBean
> > "/>
> > </contribution>
> >
> > <contribution configuration-id="
> > hivemind.management.log4j.ManagedLog4jLoggers ">
> > <logger name="*"/>
> > </contribution>
> >
> > Any ideas ? again.....
> >
> > Thanks,
> >
> > Hugo
> >
> > On 4/13/07, Hugo Palma <hu...@gmail.com> wrote:
> > >
> > > That was it....
> > > Thanks
> > >
> > > On 4/13/07, Achim Hügen < achim.huegen@gmx.de> wrote:
> > > >
> > > > Hugo,
> > > >
> > > > the rmi registry probably gets created because you have these lines
> > > > in
> > > > your descriptor:
> > > >
> > > > <contribution configuration-id="hivemind.management.MBeans">
> > > > <mbean service-id="
> > > > hivemind.management.connector.NamingServiceMBean"
> > > > start-method="start" />
> > > > </contribution>
> > > >
> > > > Just leave the NamingServiceMBean out of the config and the running
> > > > rmi
> > > > registry should be used.
> > > >
> > > > There might be problems with jmx 1.0 when the MBeanServerFactory is
> > > > located or created
> > > > and I don't expect the jsr 160 connectors to work, but just give it
> > > > a try.
> > > >
> > > > Achim
> > > >
> > > > Hugo Palma schrieb:
> > > > > Hi all,
> > > > >
> > > > > i'm trying to use hivemind-jmx in weblogic 8.
> > > > > I'm getting the following error below when i try to register the
> > > > > NamingServiceMBean. It seems to me that it's trying to create
> > > > another
> > > > > rmi server.
> > > > > The question is, why doesn't it connect to the existing server
> > > > instead
> > > > > of trying to register a new one ?
> > > > >
> > > > > Also, weblogic 8 JMX implementation is version 1.0. Could that be
> > > > the
> > > > > cause ?
> > > > >
> > > > > java.rmi.server.ExportException : internal error: ObjID already in
> > > > use
> > > > > at sun.rmi.transport.ObjectTable.putTarget(ObjectTable.java
> > > > :168)
> > > > > at sun.rmi.transport.Transport.exportObject (Transport.java
> > > > :69)
> > > > > at sun.rmi.transport.tcp.TCPTransport.exportObject
> > > > > (TCPTransport.java:190)
> > > > > at
> > > > > sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java
> > > > :382)
> > > > > at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
> > > > > at sun.rmi.server.UnicastServerRef.exportObject
> > > > > (UnicastServerRef.java:145)
> > > > > at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java :92)
> > > > > at sun.rmi.registry.RegistryImpl. (RegistryImpl.java:78)
> > > > > at
> > > > > java.rmi.registry.LocateRegistry.createRegistry(
> > > > LocateRegistry.java :164)
> > > > > at
> > > > > org.apache.hivemind.management.mbeans.NamingService.start (
> > > > NamingService.java:80)
> > > > > ... 56 more
> > > > >
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Hugo
> > > >
> > > >
> > >
> >
>
Re: JMX in weblogic 8
Posted by Hugo Palma <hu...@gmail.com>.
i also can't find any logs made by the LogManagementMBean. Is there any way
i can know if it gets registered ?
On 4/13/07, Hugo Palma <hu...@gmail.com> wrote:
>
> Not quite :o)
>
> I don't get any errors logged but i also don't see any new MBean
> registered.
> Here's my hivemodule:
>
> <contribution configuration-id="hivemind.EagerLoad">
> <load service-id=" hivemind.management.MBeanRegistry"/>
> </contribution>
>
> <contribution configuration-id="hivemind.management.MBeans">
> <mbean service-id="
> hivemind.management.connector.JMXConnectorServerMBean "
> start-method="start"/>
> <mbean service-id="hivemind.management.log4j.LogManagementMBean"/>
> </contribution>
>
> <contribution configuration-id="
> hivemind.management.log4j.ManagedLog4jLoggers ">
> <logger name="*"/>
> </contribution>
>
> Any ideas ? again.....
>
> Thanks,
>
> Hugo
>
> On 4/13/07, Hugo Palma <hu...@gmail.com> wrote:
> >
> > That was it....
> > Thanks
> >
> > On 4/13/07, Achim Hügen < achim.huegen@gmx.de> wrote:
> > >
> > > Hugo,
> > >
> > > the rmi registry probably gets created because you have these lines in
> > > your descriptor:
> > >
> > > <contribution configuration-id="hivemind.management.MBeans">
> > > <mbean service-id="
> > > hivemind.management.connector.NamingServiceMBean"
> > > start-method="start" />
> > > </contribution>
> > >
> > > Just leave the NamingServiceMBean out of the config and the running
> > > rmi
> > > registry should be used.
> > >
> > > There might be problems with jmx 1.0 when the MBeanServerFactory is
> > > located or created
> > > and I don't expect the jsr 160 connectors to work, but just give it a
> > > try.
> > >
> > > Achim
> > >
> > > Hugo Palma schrieb:
> > > > Hi all,
> > > >
> > > > i'm trying to use hivemind-jmx in weblogic 8.
> > > > I'm getting the following error below when i try to register the
> > > > NamingServiceMBean. It seems to me that it's trying to create
> > > another
> > > > rmi server.
> > > > The question is, why doesn't it connect to the existing server
> > > instead
> > > > of trying to register a new one ?
> > > >
> > > > Also, weblogic 8 JMX implementation is version 1.0. Could that be
> > > the
> > > > cause ?
> > > >
> > > > java.rmi.server.ExportException : internal error: ObjID already in
> > > use
> > > > at sun.rmi.transport.ObjectTable.putTarget(ObjectTable.java:168)
> > > > at sun.rmi.transport.Transport.exportObject (Transport.java:69)
> > > > at sun.rmi.transport.tcp.TCPTransport.exportObject
> > > > (TCPTransport.java:190)
> > > > at
> > > > sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
> > > > at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
> > > > at sun.rmi.server.UnicastServerRef.exportObject
> > > > (UnicastServerRef.java:145)
> > > > at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java :92)
> > > > at sun.rmi.registry.RegistryImpl. (RegistryImpl.java:78)
> > > > at
> > > > java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:164)
> > > > at
> > > > org.apache.hivemind.management.mbeans.NamingService.start (
> > > NamingService.java:80)
> > > > ... 56 more
> > > >
> > > >
> > > > Thanks,
> > > >
> > > > Hugo
> > >
> > >
> >
>
Re: JMX in weblogic 8
Posted by Hugo Palma <hu...@gmail.com>.
Not quite :o)
I don't get any errors logged but i also don't see any new MBean registered.
Here's my hivemodule:
<contribution configuration-id="hivemind.EagerLoad">
<load service-id="hivemind.management.MBeanRegistry"/>
</contribution>
<contribution configuration-id="hivemind.management.MBeans">
<mbean service-id="
hivemind.management.connector.JMXConnectorServerMBean"
start-method="start"/>
<mbean service-id="hivemind.management.log4j.LogManagementMBean"/>
</contribution>
<contribution configuration-id="
hivemind.management.log4j.ManagedLog4jLoggers">
<logger name="*"/>
</contribution>
Any ideas ? again.....
Thanks,
Hugo
On 4/13/07, Hugo Palma <hu...@gmail.com> wrote:
>
> That was it....
> Thanks
>
> On 4/13/07, Achim Hügen <ac...@gmx.de> wrote:
> >
> > Hugo,
> >
> > the rmi registry probably gets created because you have these lines in
> > your descriptor:
> >
> > <contribution configuration-id="hivemind.management.MBeans">
> > <mbean service-id=" hivemind.management.connector.NamingServiceMBean"
> > start-method="start" />
> > </contribution>
> >
> > Just leave the NamingServiceMBean out of the config and the running rmi
> > registry should be used.
> >
> > There might be problems with jmx 1.0 when the MBeanServerFactory is
> > located or created
> > and I don't expect the jsr 160 connectors to work, but just give it a
> > try.
> >
> > Achim
> >
> > Hugo Palma schrieb:
> > > Hi all,
> > >
> > > i'm trying to use hivemind-jmx in weblogic 8.
> > > I'm getting the following error below when i try to register the
> > > NamingServiceMBean. It seems to me that it's trying to create another
> > > rmi server.
> > > The question is, why doesn't it connect to the existing server instead
> > > of trying to register a new one ?
> > >
> > > Also, weblogic 8 JMX implementation is version 1.0. Could that be the
> > > cause ?
> > >
> > > java.rmi.server.ExportException : internal error: ObjID already in use
> > > at sun.rmi.transport.ObjectTable.putTarget(ObjectTable.java:168)
> > > at sun.rmi.transport.Transport.exportObject (Transport.java:69)
> > > at sun.rmi.transport.tcp.TCPTransport.exportObject
> > > (TCPTransport.java:190)
> > > at
> > > sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
> > > at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
> > > at sun.rmi.server.UnicastServerRef.exportObject
> > > (UnicastServerRef.java:145)
> > > at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java :92)
> > > at sun.rmi.registry.RegistryImpl. (RegistryImpl.java:78)
> > > at
> > > java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:164)
> > > at
> > > org.apache.hivemind.management.mbeans.NamingService.start (
> > NamingService.java:80)
> > > ... 56 more
> > >
> > >
> > > Thanks,
> > >
> > > Hugo
> >
> >
>
Re: JMX in weblogic 8
Posted by Hugo Palma <hu...@gmail.com>.
That was it....
Thanks
On 4/13/07, Achim Hügen <ac...@gmx.de> wrote:
>
> Hugo,
>
> the rmi registry probably gets created because you have these lines in
> your descriptor:
>
> <contribution configuration-id="hivemind.management.MBeans">
> <mbean service-id="hivemind.management.connector.NamingServiceMBean"
> start-method="start" />
> </contribution>
>
> Just leave the NamingServiceMBean out of the config and the running rmi
> registry should be used.
>
> There might be problems with jmx 1.0 when the MBeanServerFactory is
> located or created
> and I don't expect the jsr 160 connectors to work, but just give it a try.
>
> Achim
>
> Hugo Palma schrieb:
> > Hi all,
> >
> > i'm trying to use hivemind-jmx in weblogic 8.
> > I'm getting the following error below when i try to register the
> > NamingServiceMBean. It seems to me that it's trying to create another
> > rmi server.
> > The question is, why doesn't it connect to the existing server instead
> > of trying to register a new one ?
> >
> > Also, weblogic 8 JMX implementation is version 1.0. Could that be the
> > cause ?
> >
> > java.rmi.server.ExportException : internal error: ObjID already in use
> > at sun.rmi.transport.ObjectTable.putTarget(ObjectTable.java:168)
> > at sun.rmi.transport.Transport.exportObject(Transport.java:69)
> > at sun.rmi.transport.tcp.TCPTransport.exportObject
> > (TCPTransport.java:190)
> > at
> > sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
> > at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
> > at sun.rmi.server.UnicastServerRef.exportObject
> > (UnicastServerRef.java:145)
> > at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92)
> > at sun.rmi.registry.RegistryImpl. (RegistryImpl.java:78)
> > at
> > java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:164)
> > at
> > org.apache.hivemind.management.mbeans.NamingService.start(
> NamingService.java:80)
> > ... 56 more
> >
> >
> > Thanks,
> >
> > Hugo
>
>
Re: JMX in weblogic 8
Posted by Achim Hügen <ac...@gmx.de>.
Hugo,
the rmi registry probably gets created because you have these lines in
your descriptor:
<contribution configuration-id="hivemind.management.MBeans">
<mbean service-id="hivemind.management.connector.NamingServiceMBean"
start-method="start" />
</contribution>
Just leave the NamingServiceMBean out of the config and the running rmi
registry should be used.
There might be problems with jmx 1.0 when the MBeanServerFactory is
located or created
and I don't expect the jsr 160 connectors to work, but just give it a try.
Achim
Hugo Palma schrieb:
> Hi all,
>
> i'm trying to use hivemind-jmx in weblogic 8.
> I'm getting the following error below when i try to register the
> NamingServiceMBean. It seems to me that it's trying to create another
> rmi server.
> The question is, why doesn't it connect to the existing server instead
> of trying to register a new one ?
>
> Also, weblogic 8 JMX implementation is version 1.0. Could that be the
> cause ?
>
> java.rmi.server.ExportException : internal error: ObjID already in use
> at sun.rmi.transport.ObjectTable.putTarget(ObjectTable.java:168)
> at sun.rmi.transport.Transport.exportObject(Transport.java:69)
> at sun.rmi.transport.tcp.TCPTransport.exportObject
> (TCPTransport.java:190)
> at
> sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
> at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
> at sun.rmi.server.UnicastServerRef.exportObject
> (UnicastServerRef.java:145)
> at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92)
> at sun.rmi.registry.RegistryImpl. (RegistryImpl.java:78)
> at
> java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java :164)
> at
> org.apache.hivemind.management.mbeans.NamingService.start(NamingService.java:80)
> ... 56 more
>
>
> Thanks,
>
> Hugo