Thanks Stefan and Malte, That was sooo the problem as I was running the console in a different shell that had a different SEQUOIA_HOME. Feel like a bit of a clutz for missing that. Had no problems "Lifting" the new JmxURL from the 2.10.9 source so my jmx client tests are showing green bars again ;-) Thanks again Now to start playing with the total_token (as opposed to sequencer) protocol and see if the appia guys have fixed the cpu issues on low load ;-) Dave
-----Original Message-----
From: [EMAIL PROTECTED] on behalf of Stefan Lischke
Sent: Thu 6/09/2007 5:34 PM
To: Sequoia general mailing list
Cc:
Subject: Re: [Sequoia] JMX connection issues with 2.10.9
Hi Dave,
That looks like you are using a very old console. I see a "(Sequoia core
v2.10.2)" in your console.output
in >2.10.5 the JMX-URL was changed to communicate with the controller.
So this might be the problem. please look again if your sequoia-home
directory is the right (new) one
hth
Stefan
Dave Cawthorn wrote:
> Hi all,
>
> I'm trying to upgrade from 2.10.6 to 2.10.9 but im having difficulty
getting the console to connect to the controller under linux (can you believe
it works under windows no problem ;-). I'm starting the controller by using
(first exporting the SEQUOIA_HOME) controller.sh with no arguments so it uses
the default controller.xml file. I do a netstat -a to verify that something is
listening on port 1090 but the console outputs the following:
>
> [EMAIL PROTECTED] bin]# ./console.sh
> Cannot connect to the administration port of the controller. Is a
controller running at localhost:1090 ?
> Launching the Sequoia controller console
> Initializing Controller module...
> Initializing VirtualDatabase Administration module...
> Initializing SQL Console module...
> Sequoia driver (Sequoia core v2.10.2) successfully loaded.
> not connected >
>
> Im using JDK_1.5.0_12
>
> This is the /etc/hosts file
>
> # Do not remove the following line, or various programs
> # that require network functionality will fail.
> 192.168.100.50 vs01 vs01.vieosystems.com
> 127.0.0.1 localhost.localdomain localhost
> 192.168.100.51 vs02 vs02.vieosystems.com
> 192.168.100.254 vieo1
>
> and here is the output of the controller with jmx logging set to debug
>
> [EMAIL PROTECTED] bin]# ./controller.sh
> 16:53:17,557 INFO controller.core.Controller Sequoia controller
(2.10.9)
> 16:53:17,605 DEBUG controller.jmx.MBeanServer Create the MBeanServer
from Java 5
> 16:53:17,606 DEBUG controller.jmx.MBeanServer Register MBean of type
class org.continuent.sequoia.controller.management.Controller with name
sequoia:type=Controller
> 16:53:17,617 DEBUG controller.jmx.MBeanServer Total number of MBeans
registered: 19
> 16:53:17,617 INFO controller.core.Controller Loading configuration
file: /root/sequoia-2.10.9-bin/config/controller/controller.xml
> 16:53:17,699 INFO controller.core.Controller JMX is enabled
> 16:53:17,721 DEBUG controller.jmx.MBeanServer Register MBean of type
class org.continuent.sequoia.controller.monitoring.datacollector.DataCollector
with name sequoia:name=datacollector,type=datacollector
> 16:53:17,723 DEBUG controller.jmx.MBeanServer Total number of MBeans
registered: 20
> 16:53:17,723 INFO controller.core.Controller Starting JMX server on
host: 192.168.100.50
> 16:53:17,725 INFO sequoia.controller.jmx Create and start naming
service
> 16:53:17,747 INFO sequoia.controller.jmx Create JRMP adaptor
> 16:53:17,747 DEBUG sequoia.controller.jmx Set jndi name and properties
> 16:53:17,836 DEBUG controller.core.Controller JMX server started
> 16:53:17,845 INFO controller.core.Controller Waiting for connections
on 0.0.0.0:25322
> 16:53:17,845 DEBUG controller.core.Controller Backlog size is 10
connections.
> 16:53:17,853 INFO controller.core.Controller Controller started on
2007.09.06 36 at 04:53:17 PM WST
> 16:53:17,854 INFO controller.core.Controller Controller
192.168.100.50:25322 ready, listening to requests ...
>
>
>
> When I try to connect using jmx from my own code on a remote machine
I'm getting the following naming error (which implies it is actually connecting
from a remote machine but encountering a naming error)
>
> java.io.IOException: Failed to retrieve RMIServer stub:
javax.naming.NameNotFoundException: jrmp
>
> at javax.management.remote.rmi.RMIConnector.connect(Unknown Source)
>
> at javax.management.remote.JMXConnectorFactory.connect(Unknown Source)
>
> at
com.vieo.ccs.sequoia.MBeanServerConnectionFactory.getMBeanServerConnection(MBeanServerConnectionFactory.java:43)
>
> at
com.vieo.ccs.sequoia.test.MBeanConnectionFactoryTest.testExceptionHandling(MBeanConnectionFactoryTest.java:27)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>
> at java.lang.reflect.Method.invoke(Unknown Source)
>
> at junit.framework.TestCase.runTest(TestCase.java:154)
>
> at junit.framework.TestCase.runBare(TestCase.java:127)
>
> at junit.framework.TestResult$1.protect(TestResult.java:106)
>
> at junit.framework.TestResult.runProtected(TestResult.java:124)
>
> at junit.framework.TestResult.run(TestResult.java:109)
>
> at junit.framework.TestCase.run(TestCase.java:118)
>
> at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:478)
>
> at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:344)
>
> at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
>
> Caused by: javax.naming.NameNotFoundException: jrmp
>
> at com.sun.jndi.rmi.registry.RegistryContext.lookup(Unknown Source)
>
> at com.sun.jndi.rmi.registry.RegistryContext.lookup(Unknown Source)
>
> at javax.naming.InitialContext.lookup(Unknown Source)
>
> at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(Unknown
Source)
>
> at javax.management.remote.rmi.RMIConnector.findRMIServer(Unknown
Source)
>
> ... 17 more
>
> Ive also tried just about every combination of options for the
console -i options that are relevent to the machine (i've even tried to make
the server listen on other ports)
>
> Any suggestions or help would be much appriciated.
>
> Dave Cawthorn
>
>
>
>
>
>
>
>
>
>
+----------------------------------------------------------------------+
> | Z1 SecureMail Gateway Info - http://www.zertificon.com
|
>
+----------------------------------------------------------------------+
> | - Die Nachricht war weder verschluesselt noch digital
unterschrieben |
>
+----------------------------------------------------------------------+
>
>
>
------------------------------------------------------------------------
>
> _______________________________________________
> Sequoia mailing list
> [email protected]
> https://forge.continuent.org/mailman/listinfo/sequoia
--
Zertificon Solutions GmbH
Landsberger Allee 117, 10407 Berlin, Germany
GF: Herbert Nebel, Dr. Burkhard Wiegel
HRB 94059, AG Berlin-Charlottenburg
http://www.zertificon.com
https://www.globaltrustpoint.com/[EMAIL PROTECTED]
+49 (0)30-5900 300-0 (fax -99)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Z1 SecureMail" by Zertificon
...the leading server solutions for Secure & Trustable E-Mail
Try our Policy controlled S/MIME & OpenPGP & HTTPS Messaging!!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<<winmail.dat>>
_______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
