Applicability of -Dcom.sun.management.jmxremote for JMX1.2.1 + JDK1.4

In Mustang/Tiger, i can specify -Dcom.sun.management.jmxremote to indicate that I want to be able to manage JVM exposed properties remotely.
If I am writing JMX code in an environment with JDK1.4 + JMX1.2.1, does the system property work in the same manner ?
Additionally, is there a place listing all the system properties that may modify of the behaviour of a JMX managed application ? Thanks to all.
Je soutiens Sarko.

In JDK 1.4.x you will need JSR 3 + JSR 160. You will have to deploy your own RMI connector server. In order to achieve this you could mimick the out-of-the-box management agent in JDK 5. However, in JDK 1.4.x you will not see neither the PlatformMBeanServer nor the platform MBeans as these new features were introduced in JDK 5. You will be able to deploy your custom MBeans and still see them using JConsole.
Have a look at the examples in the JSR 160 bundle.
You can also have a look at the following link for more details on the out-of-the-box management agent:
http://java.sun.com/javase/6/docs/technotes/guides/management/agent.html#gdfvv
Regards,
Luis

Similar Messages

JMX - -Dcom.sun.management.jmxremote

Hello,
what make i wrong?
When i start the Oracle Application Server 10.1.3.3.0 with cmd
-> java -Dcom.sun.management.jmxremote=true -jar oc4j.jar
i can connect via jconsole to this instance. Also i can connect via java:
JMXServiceURL serviceUrl = new JMXServiceURL("service:jmx:rmi://127.0.0.1:23791/");
All is perfect !!!
But when i start the oas over opmn -> opmctl startall i can´t connect via jconsole or via java-remote Client, although i set the parameter:
<ias-component id="default_group">
<process-type id="home" module-id="OC4J" status="enabled">
<module-data>
<category id="start-parameters">
<data id="java-options" value="-server -mx1024M -ms512M -Xrs -XX:MaxPermSize=128M -XX:AppendRatio=3 -Djava.security.policy=$ORACLE_HOME/j2ee/home/config/java2.policy -Djava.awt.headless=true -Dhttp.webdir.enable=false -Dcom.sun.management.jmxremote "/>
</category>
<category id="stop-parameters">
<data id="java-options" value="-Djava.security.policy=$ORACLE_HOME/j2ee/home/config/java2.policy -Djava.awt.headless=true -Dhttp.webdir.enable=false"/>
</category>
</module-data>
<start timeout="600" retry="2"/>
<stop timeout="120"/>
<restart timeout="720" retry="2"/>
<port id="default-web-site" range="8888" protocol="ajp"/>
<port id="rmi" range="12401"/>
<port id="rmis" range="12701-12800"/>
<port id="jms" range="12601-12700"/>
<process-set id="default_group" numprocs="1"/>
</process-type>
</ias-component>
it doesn´t work. What is the problem ???
Thanks in advance for your help.
Best Regards,
Ralf

Hello,
can nobody help me?
Best Regards,
Ralf

When using -Dcom.sun.management.jmxremote.port=0

In order to bind to the next available port how can you then programmatically find out which port the agent bound do so you know which port number to use in JConsole?

You can't. Instead of writing code within your application to discover this port, you should write code that creates and configures a connector itself. If you have already worked out the -Dcom.sun.management.jmxremote.* properties that you need, then you can translate them into code as described here. If you create your RMI registry with LocateRegistry.createRegistry(0) then you're left with a similar problem because there's no way to extract the port number from the returned Registry object. Instead, you can use the createRegistry form that takes an RMIClientSocketFactory and an RMIServerSocketFactory, and in the latter you can extract the port number after creating a socket in the createServerSocket method, and for example store it in a local variable.
Alternatively you could create a ServerSocket(0), look at its port number, close it, then create a registry on that port number, looping a few times if it fails (because someone else grabbed that port in between).
This is admittedly not as easy as it should be.
Regards,
Éamonn McManus -- JMX Spec Lead -- [http://weblogs.java.net/blog/emcmanus]

Are com.sun.management.jmxremote properties standard?

I searched quickly through the most recent specs for JSR-3 (JMX 1.x) and JSR-160 (JMX Remote API) as well as the J2SE 5.0 new features descriptions, but could not find any mention of the jmxremote flags that you set in order to enable the out-of-the-box management agent for local or remote access to the JVM via JMX, e.g.
com.sun.management.jmxremote
com.sun.management.jmxremote.port
com.sun.management.jmxremote.ssl
com.sun.management.jmxremote.authenticate
Some JMX documentation is needed for the application I'm working on, and I need to know if setting these flags will work on all JVMs supporting J2SE 5.0 or Java SE 6, or if it is only guaranteed to work with Sun's implementations (JVMs).
Some web searches indicate that the properties are in use with recent version of IBM JVMs and BEA's JRockit as well, but I'd like to have it confirmed to what extent these flags are standard (e.g. if they may be considered de facto standard properties). Is there an official document defining these properties and saying which settings they are valid in?
Thanks!

The properties are not part of any formal standard, but, as you have noticed, any JVM you are likely to use will support them. So they are de facto but not de jure standard.
If you are very concerned about standards, it is always possible to replace the use of these properties with code in your application that uses only standard APIs. See <http://java.sun.com/javase/6/docs/technotes/guides/management/agent.html#gdfvv>.
Regards,
�amonn McManus

Sun Management Console doesn't support MD5 passwords?

I recently converted all our Sun systems to use MD5 passwords, using the Linux-BSD algorithm. I chose the Linux-BSD algorithm for compatibility reasons. After giving root a new password, now stored in MD5 format, I can no longer log in to the Sun Management Console (smc). I had the same problem with DB2. Switching root's password back to CRYPT fixed the issue.
Is this a known problem that Sun is working on? And how does this happen? Shouldn't the application leave authentication to the OS?
Mark

IIRC the Solaris 10 Basic admin guide talks about this issue.
alan

How to integrate a Solaris x86 server on Sun Management Center ?

Hello people,
I want to integrate a Solaris x86 server on Sun Management Center platform.
If I'm not wrong, SunMC doesn't run for Solaris x86, server and client only as console with Java.
In speat of it, I try to install Sun Management Center 3.0 Agent for Solaris x86.
It seems to be ok, install packages, but when execute es-setup script, intents to create the following directory:
/opt/SUNWsymon/base/bin/sparc-sun-solaris2.8
I supose that in this directory, SunMC will install sparc binary files
At this point, I can't follow the installation and abort it.
Can anybody give me ideas to install and integrate my solaris x86 server on SunMC ?
Thanks

Hi Hisham,
hishooooo wrote:
Dear Gents,
I have one X86 Solaris Server configured and installed to be Sun Management Center Server.
successfully i could monitor the Sun Solaris Servers after i have installed the SMC agent on them.
my problem is that i could not install the SMC agent on Red Hat Linux. as i could not find an easy document or steps to do so.
could you guide please?If you still have a copy of your SunMC media around, the same ["es-inst"|http://docs.sun.com/app/docs/doc/820-2215/command-line-1?l=en&a=view] program you use to install Solaris Agents should work on Linux as well. It autodetects OS type and will install Solaris packages or RPMs as appropriate.
Regards,
[email protected]
http://www.HalcyonInc.com

How to integrate Solaris x86 server on Sun Management Center ?

Hello people,
I want to integrate a Solaris x86 server on Sun Management Center platform.
If I'm not wrong, SunMC doesn't run for Solaris x86, server and client only as console with Java.
In speat of it, I try to install Sun Management Center 3.0 Agent for Solaris x86.
It seems to be ok, install packages, but when execute es-setup script, intents to create the following directory:
/opt/SUNWsymon/base/bin/sparc-sun-solaris2.8
I supose that in this directory, SunMC will install sparc binary files
At this point, I can't follow the installation and abort it.
Can anybody give me ideas to install and integrate my solaris x86 server on SunMC ?
Thanks

Hi
From the Unix prompt enter oemapp console(for v9.x). If you are using earlier versions it is oemapp console (for starting the console) and oemapp dbastudio(for starting dba studio)
For starting OMS enter: oemctrl start oms.
Hope this helps
sarath

Sun Management Center and Reduced Core Installs

hey all,
I just discovered the Sun Management Center and the tool looks great for the servers I need to manage. However due to security reasons all our servers are installed as Reduced Network Core installs where we then add the minimal extra packages.
At the moment I am still testing everything but I am a bit stuck here and I believe that I might be missing some packages. I can get the server to find the agent but there I cannot load any of the modules. Sniffing the traffic does seem to show that the info is sent ( a list of names I recognise as module names) but the console does not show anything and reports an error unable to load module info.
Is there a full package list that is required to run the management center server and client? The agent runs fine on my desktop but that is a full install.
I already noticed the command ping is required, but am unsure about snmp daemons. What other packages will i need to install? The manual doesn't really give any information on that and seems to start from a full install

Never mind,
The problem was in the firewall who was defragmenting packets. Once I disabled that feature the server worked fine.
Seems just ping is enough to get the installer working.

In-Band Management configuration for f5100 array from T5440 on Solaris 10

Hi All,
I am trying to configure in-band management for storagetek array Sun Storage F5100 from T5440 server on Solaris 10.
OS Installed on the server: Solaris 10 10/09
Hardware : T5440
Array : Sun Storage F5100
Sun Storage F5100 have 20 FMODs which can see from format output. But In-Band management don't work, i want to manage it by CAM.
/dev/rdsk/c2t0d0s2
/dev/rdsk/c2t1d0s2
/dev/rdsk/c2t2d0s2
/dev/rdsk/c2t3d0s2
/dev/rdsk/c2t4d0s2
/dev/rdsk/c2t5d0s2
/dev/rdsk/c2t6d0s2
/dev/rdsk/c2t7d0s2
/dev/rdsk/c2t8d0s2
/dev/rdsk/c3t0d0s2
/dev/rdsk/c3t1d0s2
/dev/rdsk/c3t2d0s2
/dev/rdsk/c3t3d0s2
/dev/rdsk/c3t4d0s2
/dev/rdsk/c3t5d0s2
/dev/rdsk/c3t6d0s2
/dev/rdsk/c3t7d0s2
/dev/rdsk/c3t8d0s2
Below are the packages i installed:
host_sw_solaris_6.6.0.11
SMagent-SOL-90.01.02.05.pkg
SMruntime-SOL-90.60.02.01.pkg
once after i installed the above packages i am getting below error
SANtricity Storage Manager Agent, Version 90.01.02.05
Built Wed May 06 06:21:07 CDT 2009
Copyright 2009 Sun Microsystems Inc. All rights reserved. Use is subject to license agreement.
Checking device /dev/rdsk/c0t2d0s2 : Skipping
Checking device /dev/rdsk/c0t3d0s2 : Skipping
Checking device /dev/rdsk/c2t0d0s2 : Skipping
Checking device /dev/rdsk/c2t1d0s2 : Skipping
Checking device /dev/rdsk/c2t2d0s2 : Skipping
Checking device /dev/rdsk/c2t3d0s2 : Skipping
Checking device /dev/rdsk/c2t4d0s2 : Skipping
Checking device /dev/rdsk/c2t5d0s2 : Skipping
Checking device /dev/rdsk/c2t6d0s2 : Skipping
Checking device /dev/rdsk/c2t7d0s2 : Skipping
Checking device /dev/rdsk/c2t8d0s2 : Skipping
Checking device /dev/rdsk/c3t0d0s2 : Skipping
Checking device /dev/rdsk/c3t1d0s2 : Skipping
Checking device /dev/rdsk/c3t2d0s2 : Skipping
Checking device /dev/rdsk/c3t3d0s2 : Skipping
Checking device /dev/rdsk/c3t4d0s2 : Skipping
Checking device /dev/rdsk/c3t5d0s2 : Skipping
Checking device /dev/rdsk/c3t6d0s2 : Skipping
Checking device /dev/rdsk/c3t7d0s2 : Skipping
Checking device /dev/rdsk/c3t8d0s2 : Skipping
The SMagent service attempted to start but terminated. Possible causes include: [1] The access volume is disabled in NVSRAM. [2] No controllers with compatible firmware were found. [3] The default logical unit number (LUN) assigned to the access volume (typically 7 or 31) is not in the range supported by the host or is already in use by the host for another device. See your storage management documentation for more details.
Jul 23 13:56:47 sol10 SMagent: The SMagent service attempted to start but terminated. Possible causes include: [1] The access volume is disabled in NVSRAM. [2] No controllers with compatible firmware were found. [3] The default logical unit number (LUN) assigned to the access volume (typically 7 or 31) is not in the range supported by the host or is already in use by the host for another device. See your storage management documentation for more details.
As per sun documentation i ran the below commands, but still i am getting above error.
# setenv LD_LIBRARY_PATH /opt/SMgr/agent
# java -classpath /opt/SMgr/agent/SMagent.jar devmgr.versioned.agent.DeviceIdentifier | grep "Volume Access"
But any output with above commands.
Any help would be really help ful.
Thanks,
gebilong

Make sure the mapping to Access Group has not been deleted.
Use the command /opt/SUNWsefms/bin/lsscs list -a array mappingYou must see samething like
Volume:Access LUN: 31mapped.via mapped.via.default.groupmapped.target.type mapped.via.default.group Permission: Read Only
...If you don't see this recreate mapping
/opt/SUNWsefms/bin/lsscs map -a array -l 31 volume Accessand restart agent
/etc/init.d/SMagent start

In-Band Management configuration for 2530 array from T5120 on Solaris 10

Hi All,
I am trying to configure in-band management for storagetek array 2530 from T5120 server on Solaris 10. I could able to connect the array from CAM software and it is showing as out-of-band. I can able to change the array name and IP address also. But when i try to configure In-Band Management i am having problems.
OS Installed on the server: Solaris 10 5/08
Hardware : T5120
Array : Storage Tek 2530
Below are the packages i installed:
SMagent-SOL-90[1].00.00.06.pkg
SMruntime-SOL-10[1].10.02.00.pkg
once after i installed the above packages i am getting below error
"SANtricity Storage Array Host Agent, Version 90.00.00.06
Built Wed May 23 09:02:26 CDT 2007
Copyright (C) 1999-2007 LSI Logic Corporation. All rights reserved.
Checking device /dev/rdsk/c1t0d0s2 : Skipping
The SMagent service attempted to start but terminated. Possible causes include: [1] The access volume is disabled in NVSRAM. [2] No controllers with compatible firmware were found. [3] The default logical unit number (LUN) assigned to the access volume (typically 7 or 31) is not in the range supported by the host or is already in use by the host for another device. See your storage management documentation for more details.
The Host Context Agent did NOT start because 0 controllers were found.
Oct 9 19:51:10 proto-hd1 SMagent: The SMagent service attempted to start but terminated. Possible causes include: [1] The access volume is disabled in NVSRAM. [2] No controllers with compatible firmware were found. [3] The default logical unit number (LUN) assigned to the access volume (typically 7 or 31) is not in the range supported by the host or is already in use by the host for another device. See your storage management documentation for more details.
Oct 9 19:51:10 proto-hd1 SMagent: The Host Context Agent did NOT start because 0 controllers were found."
As per sun documentation i ran the below commands, but still i am getting above error.
# setenv LD_LIBRARY_PATH /opt/SMgr/agent
# java -classpath /opt/SMgr/agent/SMagent.jar devmgr.versioned.agent.DeviceIdentifier | grep "Volume Access"
Any help would be really help ful.
Thanks,
Raja

Make sure the mapping to Access Group has not been deleted.
Use the command /opt/SUNWsefms/bin/lsscs list -a array mappingYou must see samething like
Volume:Access LUN: 31mapped.via mapped.via.default.groupmapped.target.type mapped.via.default.group Permission: Read Only
...If you don't see this recreate mapping
/opt/SUNWsefms/bin/lsscs map -a array -l 31 volume Accessand restart agent
/etc/init.d/SMagent start

Getting java.io.NotSerializableException: sun.management.MemoryPoolImpl

Hi,
While trying to get JVM Memory pool information of a remote computer ,am getting java.io.NotSerializableException. I used following method
ManagementFactory.getMemoryPollMXBean().
Please help me to solve these exception.
java.io.NotSerializableException: sun.management.MemoryPoolImpl
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
at java.util.ArrayList.writeObject(ArrayList.java:570)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
at com.path.systemmanager.tunnelGate.TunnelServlet.doPost(TunnelServlet.java:38)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:290)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:272)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:214)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
Thanks,
Sreejith

I agree, it looks frustrating. Obviously the serialization process has found the non-serializable object during the traversal of the object graph, but its difficult to know where this is.
Your class looks a bit "serialization-heavy", if you don't mind me saying. I avoid serializing anything to do with swing components and stick to collections and my own classes. Do you need to serialize these? If not, mark them transient. You can do this for all of them and then reintroduce into the serialized form one at a time to see which one causes the problem (just for curiosity).
When the object is deserialized you will have to make the necessary arrangements to set up any members that you marked transient, as these will be null. You can do this is readObject, but on this subject, why are you writing out the points member explicitly? It will be written out anyway since there is nothing special about it.
I don't know how familiar you are with the serialization package but its a sharp instrument that needs respect. I would advise reading the specification, if you haven't already done so.

One Managed Bean for a set of pages

Can I have one Managed Bean (request scope) for a set of pages using Creator? Or should I have one Managed Bean for each page?
Thanks in advance,
Juan

Hi,
Please take a look at the following threads:
http://swforum.sun.com/jive/thread.jspa?forumID=123&threadID=51481
http://swforum.sun.com/jive/thread.jspa?forumID=123&threadID=54165
http://swforum.sun.com/jive/thread.jspa?forumID=123&threadID=51912
Hope this hepls
Regards,
Rk.

Dynamically setting manager name for trap

As per the SEA documentation, trap destinations are specified through master agent configuration file and need to be set before starting master agent.
We want add more managers dynamically i.e. after master and subagent are started and communicating with one manager.
Does snmpdx provide any MIB variable to "set" the manager name? Is there any other alternative such as command line parameter or API to set the manager name?
Thanks
Dhananjay

Hi,
This feature is not supported in SEA. All the configuration should be done before starting master agent.
To register the subagent, you can use any of the following two methods.
* Static method : The master agent reads agent resource files. This resource
file contains an entry for each subagent.
* Dynamic method : The master agent receives the information from the subagents. The subagent sends a SET request containing the MIB objects needed to register with the Master Agent, through the use of the registration API.
Using SEA, there is no way you can add the managers dynamically for traps.
I suggest you may have look on new product from SUN i.e SunMC( Sun Management Center) which has lot of new features.
HTH.
Thanks,
Santosh

Sun management software

Hi,
we are looking at sun management software and noticed that it costs about $300+ per client.
what is an alternative to this which is less expensive or free?
what are you other admins doing?
thanks,
~jv

I, too, have been trying to sort out the options and tools for supporting Solaris 9 and 10.
This maybe behond the scope of your question but here is some of what I've uncovered in the last couple of years:
The class Intermediate System Administration (SA 239) has you download the recommended patch cluster and install using ./install_cluster. This works but you will not know which patches will be installed until after the fact. So this process does not support preparing for any changes made by the patches.
The only other process that I have used involve using a non Sun script - pca from http://www.par.univie.ac.at/solaris/pca/intro.html This perl script has many options but the "pretend" option makes it easy to determine which patches will be installed and what revision of the patch is currently installed.
Here are some of the sources I use to try an keep up with patches and other technical details of supporting Solaris
If you have a SunSolve account you can subscribe to email alerts at:
http://sunsolve.sun.com/search/editSubscribedDocuments.do
There are 6 "collections" of "New Documents". I receive a single daily email. The email contains a numbered list (with URLs) for each collection that has New Documents. The collections are:
BUG             (includes bug number and very short description URL)
INFODOC         (includes short description, the INFODOC number is imbedded in the URL)
PATCH           (includes patch number short description/title and URL)
SRDB            (Symptoms and Resolutions - includes short description and URL)
SUNALERT        (including short description and URL)
TROUBLESHOOTING (including short description and URL)Another source for patch information is the SUNSOLVE[SM] PATCH CLUB report (sign up at https://subscriptions.sun.com/subscription_center/ecomm.jsp). This a weekly email with four main sections. The first section has one line for each new patch with a short title/description. The second section has an entry for each patch with more details (includes keywords, synopsis, Solaris Release, bugid's fixed and other details) - but no URLs. The thrid section is a list of Withdrawn patches. The fourth section has an entry for each withdrawn patch that includes reason and recommendation details.
SUN(SM) ALERT WEEKLY SUMMARY REPORT is another source. This one covers "critical hardware and software issues". It includes the Sun Alert ID and URL. Sign up is at the same URL as the Patch Club report above.
have good weekend,
Glen

Deployer Installation: Failed to validate Release Management Server for Team Foundation Server 2013

Attempting to install the deployer on a machine and getting the below error. Not sure what that means, out of turn error or what actually occurs at this step, validating release management server, during the configuration piece. The user,
that we set for the service was validated fine. The user is an service account in the TFS RM Server, is an admin on the local box as well.
I am able to get into the TFS RM Server through the client just fine. I can hit the TFS RM UI just fine as well.
Curious what would not allow the deployer to complete as mentioned below.
Any help is appreciated.
I, 2013/12/16, 14:46:26.521, Validated account to use as identity for Release Management Services.
I, 2013/12/16, 14:46:26.521, Validating Release Management Server for Team Foundation Server 2013...
E, 2013/12/16, 14:46:30.905, Received Exception : Microsoft.TeamFoundation.Release.CommonConfiguration.ConfigurationException: Failed to validate Release Management Server for Team Foundation Server 2013.
at Microsoft.TeamFoundation.Release.CommonConfiguration.DeployerConfigurationManager.ValidateServerUrl()
at Microsoft.TeamFoundation.Release.CommonConfiguration.DeployerConfigurationManager.ValidateAndConfigure(DeployerConfigUpdatePack updatePack, DelegateStatusUpdate statusListener)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
I, 2013/12/16, 14:46:30.905, Work completed for GetConfiguration() call : got out of turn error
E, 2013/12/16, 14:46:30.905, Failed to validate Release Management Server for Team Foundation Server 2013.

Hi Kpdn,
Thanks for your post.
All your participation and support are very important to build such harmonious/ pleasant / learning environment for MSDN community.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Applicability of -Dcom.sun.management.jmxremote for JMX1.2.1 + JDK1.4

Similar Messages

Maybe you are looking for