SSL monitoring
Hey guys,.
I'm looking for an agent this SSL certificate expiration monitoring? Someone at - it something already done they can share?
I wonder if this is possible only with openssl Verify order
If I read this right http://www.madboa.com/geek/openssl/#verify-standard
If it seems that the command returns ok if all is well and a mistake for a certificate expired.
The result can be sent to Foglight but it is probably possible also with the execution of the command and send the results to a log file and then just have logfilter monitoring agent log file and send the notification on errors.
Golan
PS I also see this site with scripts that may be able to give the number of days and then just sent this info to Foglight with a script agent http://www.glenscott.net/2011/12/09/checking-ssl-certificate-expiry-date-and-issuer-an-openssl-wrapper-in-bash/
Tags: Dell Tech
Similar Questions
-
Whit SSL Node Manager comunication problem
Hello, I have a problem whit node Manager (SSL protocol).
My configuration is:
HOST A (contains the administration server and managed_server1)
The HOST B (contain managed_ server2 in the cluster managed_server1 of Pentecost)
When I startup scrip to HOST B starManagedWebLogic.sh managed_server2 Pentecost all right (. / startManagedWebLogic managed_server2 http://HOST A: 7001). But I can not start the managed_server2 in the Administration Console (HOST A) (using the associated Manager node of Pentecost a suitable machine).
For the server managed_server2, the Associate Manager node machine computer2 is not accessible.
All selected servers are currently in a State that is not compatible with this operation or are not associated with a Node Manager running or you are not authorized to perform the requested action. No action will be taken.
I find the following:
javax.net.ssl.SSLKeyException: security alert: 090482BAD_CERTIFICATE received from server1.das.cites - 46.34.5.15. Check the peer to determine why it rejected the certificate chain (trust CA configuration, check the host name). Debugging SSL monitoring may be necessary to determine the exact reason that the certificate was rejected.
When I go into the Administration Console to:
Machine-> Computer1-> monitoring:
Status: available
Version: 10.3
Machine-> computer2-> monitoring:
Status: Inactive
Description of the problem: javax.net.ssl.SSLKeyException
Version: (not available)
How I can solve this problem. Thanks for any response.Try to start the server with the property weblogic:
-Dweblogic.security.SSL.ignoreHostnameVerification = true.
Please also enable debugging for details indicators:
-Dweblogic.security.SSL.verbose = true
-Dssl.debug = true
-Dweblogic.StdoutDebugEnabled = trueThank you.
-
Errors with Nodemanager BAD_CERTIFICATE / BEA-090477
Hello
I have a new installation of weblogic on a new machine. I can't get Nodemanager to work.
The machine (red hat linux) has its normal 10.99.x.xxx of IP address and its IP address of loopback 127.0.0.1 in hosts as follows
cat/etc/host
# Do not remove the next line, or various programs
# requiring a network functionality will fail.
127.0.0.1 my_server_name.company.ie my-server-name localhost.localdomain localhost
: 1 localhost6.localdomain6 localhost6
In the console of WL I configure my-server-name of the computer with the address of node Manager listen = localhost.
I have Admin Server address blank, the listening being 7001 port ssl port 7002 listen.
I have a server managed with listening also empty address. listening port 8001's listening ssl port 7002.
Managed server has been added to the machine.
When I start the node Manager it tells me:
< screw the socket listener started on port 5556 >
Which is what I expected.
However, when I try and run a command through nodemanager, i.e. start managed server I get errors on the SSL handshake.
< 11 September 2009 13:40:06 > < WARNING > < Eception exception in Server Manager: javax.net.ssl.SSLKeyException: [Security: 090482] BAD_CERTIFICATE alert was received from my_server_name.company.ie - 127.0.0.1. Check the peer to determine why it rejected the certificate chain (trust CA configuration, check the host name). Debugging SSL monitoring may be necessary to determine the exact reason that the certificate was rejected. >
javax.net.ssl.SSLKeyException: [Security: 090482] BAD_CERTIFICATE alert was received from my_server_name.company.ie - 127.0.0.1. Check the peer to determine why it rejected the certificate chain (trust CA configuration, check the host name). Debugging SSL monitoring may be necessary to determine the exact reason that the certificate was rejected.
I can't understand this. I have the exact same setup on another machine and nodemanager works very well.
Can anyone help.
Published by: tradtshirt on Sep / 11/2009 06:04
Published by: tradtshirt on January 13, 2010 07:17Default node Manager uses the identity of demo WebLogic keystore. The key file is generated at installation time by using the CertGen utility. The generated private key uses the common name (cn) solved by Java. The Oracle documentation says that there may be problems on some platforms (not just server name, FQDN,...).
In your case the common name (cn) of the private key is not the expected server name.
You can either disable check (Java option - Dweblogic.security.SSL.ignoreHostnameVerification = true) host name or create a private key with the correct common name.
We had the same problem and it was resolved by recreating the file of demo key with another common name.
JAVA_HOME = / opt/weblogic/jdk160_14
WL_HOME=/opt/WebLogic/wlserver_10.3
PATH = $JAVA_HOME/bin: $PATH
export PATH. $WL_HOME/server/bin/setWLSEnv.sh
Java utils. CertGen - cn YOURSERVER. DOMAIN.COM - keyfilepass DemoIdentityPassPhrase - certfile mycert - keyfile mykey
Java utils. ImportPrivateKey - keystore DemoIdentity.jks - storepass DemoIdentityKeyStorePassPhrase - keyfile mykey.pem - keyfilepass DemoIdentityPassPhrase - certfile mycert.pem - alias demoidentity
Copy the newly created identity demo key store of $WL_HOME/server/lib.
-
Hi all
I had a problem with my customer site, some analyzed server are SSL error very high rate. It can go to 95% + that almost all of those transactions cannot be retrieved later in FxV well, some other quite normal. After discussion with the customer, know that they just upgrade their 32-bit Windows to 64-bit Web server. And they remove the entry of these servers in server monitor FxM and back again. But it does not help. Any idea, people?
Thank you
Asun
Hey Joe,
This is the screenshot of alarm showing the SSL error rate.
If these servers are the servers that have just improved 32 bit - 64 bit. But there are 4 servers do not encounter the same problem not been updated too...
Thank you
Asun
-
Monitor a rest call via FxM - request for advice
Hi all
Greetings of the day... and I need expert advice.
There is a requirement of FxM monitor a call is made by Oracle Enterprise Manager. The App_team confirms that this call transmitted via one of the F5 who listens to FxM device.
I have configured the following and yet you do NOT see any success. I simulate a part of traffic.
- appeal of rest - v1 / https://service.qa.com:443 / monitorauthenticate
- host name of the server - configured in FxM
- SSL - FxM uploaded key
Which returns the url is a token. I've attached a screenshot of the same thing. Could you please shed some light... and thank you very much for your time.
Kind regards
Arun
On the device of FxM have you checked the list of resources - Pages and Hits of. * monitorauthenticate.*
David Mendoza
-
Monitoring VPN connection attempts
I would like to be able to use the syslog messages that are detached from the ASA to monitor VPN connection attempts (successful or not). Looking at the posts system there are several codes that relate to this.
I wonder if anyone has a good way to use syslog to do this? There are some codes that can be used for this information?
Thank you.
You can set the ASA to send syslog messages when the user connects and disconnects. There are a few types of 'remote access' as IPsec VPN, webvpn / without client anyconnect/ssl vpn client that you can follow.
If you are using Clientless SSL VPN syslogs usually begin with 716xxx. For example the syslog for connect is 716001 and disconnect is 716002. There is a list of other Clientless VPN SSL related messages here. You can view the specific contents of each journal here:
http://www.Cisco.com/en/us/docs/security/ASA/asa80/system/message/logmsg
http://www.Cisco.com/en/us/docs/security/ASA/asa80/system/message/logmsgs.html#wp4776913
If you use SSL VPN Client (SVC1.x, AnyConnect 2.x) syslogs usually begin with 722xxx. For example, the syslog for connect is 722022 and disconnect is 722023. There is a list of other customer VPN SSL related posts here
http://www.Cisco.com/en/us/docs/security/ASA/asa80/system/message/logmsg
http://www.Cisco.com/en/us/docs/security/ASA/asa80/system/message/logmsgs.html#wp4778697
If you use the IPSec VPN client, you can follow a success to connect with 713119 (indicates the phase 1 completed), 713049 (indicates the complete Phase2) and disconnect with 113019. There is a syslog ipsec additional 713049 that you can follow for ipsec.
http://www.Cisco.com/en/us/docs/security/ASA/asa80/system/message/logmsgs.html#wp4775678
http://www.Cisco.com/en/us/docs/security/ASA/asa80/system/message/logmsgs.html#wp4775412 http://www.Cisco.com/en/US/docs/Security/ASA/asa80/System/message/logmsg
http://www.Cisco.com/en/us/docs/security/ASA/asa80/system/message/logmsgs.html#wp4769539
Here are some other notes to keep in mind:
-You can tell that the logging levels you currently have on the command line ASA with 'show log '.
-Newspapers that you send to a syslog server are controlled with the commands "Logging Trap". For example 'logging trap information' (level 6) or "trap alerts logging" (level 1)
-You can tell what level of severity (i.e., alerts, critical, errors, warnings, notifications, informational, debug) each one connects through this link. As you can see by checking the link, those follow-up sign in or out as I've mentioned above are usually information (sev 6)):
http://www.Cisco.com/en/us/docs/security/ASA/asa80/system/message/logsev
http://www.Cisco.com/en/us/docs/security/ASA/asa80/system/message/logsevp.html
-If you want to create a specific subset of the syslogs to send to a specific device, you can do it with a class or a list of logging:
http://www.Cisco.com/en/us/docs/security/ASA/asa80/configuration/guide/m
For example (class log):
http://www.Cisco.com/en/us/docs/security/ASA/asa80/configuration/guide/m
http://www.Cisco.com/en/us/docs/security/ASA/asa80/configuration/guide/monitor.html#wp1065253
class check vpnc informational FRT
For example (list of logging):
http://www.Cisco.com/en/us/docs/security/ASA/asa80/configuration/guide/monitor.html#wp1065512
log list mylist message 722022
log list mylist message 722023
logging trap mylist
Don't forget to evaluate the positions that helped you and to mark it as resolved if you question has been answered.
-heather
-
JRockit - process monitor JRockit java
Hello everyone, we have installed in our environment (Windows Server 2008R2) that uses the Java JRockit of Weblogic Platform. I came across the question where I cannot follow the process (connect to JVM) java through the JRMC (JRockit Mission Control) as the java process runs user SYSTEM account. This is why it does not appear as a local JVM. If I run it via my account I can monitor fine. Can anyone suggest how to monitor the process of java which was run on the SYSTEM account. I can't log in as the SYSTEM the server tho. Thank you, Viktor Ozerov
In my view, your only option is to add some flags of the jvm to WLS to enable the agent remote jmx.
Something like
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port = 7091
-Dcom.sun.management.jmxremote.ssl = false
-Dcom.sun.management.jmxremote.authenticate = false
-
Hello
So, Ive recently rolled out an 8 node vRops enviromnemt and finally had the time to ask the authority of internal certification signed SSL Certs, I created them, convert their PEM format, downloaded 1 cert, had look ok, then did the 2nd node, verified and it looked ok, I then checked the node 1, who pointed out a mistake and said there the same SSL certificate as the crux of the 2nd.
Now I need to check that documentation does not seem to say that and not see anything on the web it is clear either.
VROps is the SSL certificate of the same SSL certifiate for each node for an enviromnemt?
If so what I need to create a single SSL certificate and a subjectAltName for each node intot he asks cert.
which means that I have put an article like this in my openssl.cnf
[v3_req]
subjectAltName = @alt_names
[alt_names]
DNS.1 = vropsnode1.internal.domain
DNS.2 = vropsnode2.internal.domain
DNS.3 = vropsnode3.internal.domain
DNS.4 = vropsnode4.internal.domain
DNS.5 = vropsnode5.internal.domain
DNS.6 = vropsnode6.internal.domain
DNS.7 = vropsnode7.internal.domain
DNS.8 = vropsnode8.internal.domain
IP.1 = 192.168.1.1
IP.2 = 192.168.1.2
IP.3 = 192.168.1.3
IP.4 = 192.168.1.4
IP.5 = 192.168.1.5
IP.6 = 192.168.1.6
IP.7 = 192.168.1.7
IP.8 = 192.168.1.8
see you soon
John
The documentation is really poor in this area. but I got this VMware"one certificate will be used by the web server on all nodes, so to do the certificate must be valid for all nodes. One way to get there is with multiple subject Alternative Name (SAN) entries". So looks like im on the right track.
Which is kind of weird, but works as that said, when you look at the certs ssl free signed that they have different names vc-ops-slice-1, vc-ops-slice-2 etc. but then you download an SSL certificate cert of the same is on all nodes.
Update: Ive had an SSL certificate generated with the subjectAltName as in the example above with the full domain name and IPs for each node in the cluster and created the imported and appropriate to this PEM file, it works and the certificate is valid on all the nodes, this is the solution.
Also of the impact, that is the question that vRops Government itself to vCenter with the IP address and not FQDN, the SSL certificate needs the IP address, but in my case it causes also connectivity issues in browsers because of our proxy settings, so it must be considered if his need...
- vRealize extension of Operations Manager is saved using the IP address instead of the DNS name
By default, vRealize Operations Manager saves its extension with vCenter using the IP address of Operations Manager and not the DNS name vRealize. Users who click on open vRealize Operations Manager tab monitor vCenter open a URL based on the Operations Manager IP address vRealize and not the DNS name.
Workaround: To allow the registration of the name vRealize Operations Manager with the DNS name extension, follow these steps:- On each node of the cluster of Operations Manager vRealize, follow these steps:
- Starting the console, open the following file in a text editor.
$ALIVE_BASE/user/conf/configuration.properties - Add the following line to the properties.
extensionUseDNS = true
Note: You can go back to using the IP address by changing the property to false. - Save and close configuration.properties.
- Starting the console, open the following file in a text editor.
- Connect to the Operations Manager vRealize management interface and restart the cluster.
- On each node of the cluster of Operations Manager vRealize, follow these steps:
John
- vRealize extension of Operations Manager is saved using the IP address instead of the DNS name
-
O11n Plugin Maven Orchestrator package: import-package SSL Handshake error
I try to use the maven for VCO plugin creation plugin and I get SSL errors when you try to synchronize all of VCO to the local files. It is a standard installation of the device to VCO 6.0.2. I tried all the stuff that I can get:
I put the - Dmaven.wagon.http.ssl.insecure = true Dmaven.wagon.http.ssl.allowall = true
I created a file of keys to the VCO ssl key and he passed as the truststore -Djavax .net .ssl .trustStore = keystore.pks - Djavax .net .ssl .trustStorePassword = 123qwe x
I turned on debugging and outputs verbose
Nothing seems to work, thoughts or ideas is appreciated.
Thank you
Tim
Here is an example of newspaper, very similar regardless of the options passed.
o11n MVN-paquet : import-package-DserverUrl=vcoadmin:[email protected]:8281-Djavax.net.debug=all-Dmaven.wagon.http.ssl.insecure=true-Dmaven.wagon.http.ssl.allowall=true-Dsun.security.ssl.allowUnsafeRenegotiation=true-Djavax.net.ssl.trustStore=keystore.pks-Djavax.net.ssl.trustStorePassword=test123 -X
Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; 2014-12 - 14 T 12: 29:23 - 05:00)
House of Maven: /usr/local/Cellar/maven/3.2.5/libexec
Java version: 1.6.0_65, name of seller: Apple Inc..
House of Java: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: 'mac os x', version: "10.10.3," arch: "x86_64" family: "mac"
[INFO] Error stacktraces are turned on.
[DEBUG] Read the global settings of /usr/local/Cellar/maven/3.2.5/libexec/conf/settings.xml
[DEBUG] Read /Users/tperry/.m2/settings.xml user settings
[DEBUG] Using local repository at /Users/tperry/.m2/repository
[DEBUG] With the help of Manager EnhancedLocalRepositoryManager with priority 10.0 for /Users/tperry/.m2/repository
[INFO] Analysis of projects...
[DEBUG] Statistics collection of dependency: {ConflictMarker.analyzeTime = 1, ConflictMarker.markTime = 0, ConflictMarker.nodeCount = 211, ConflictIdSorter.graphTime = 1, ConflictIdSorter.topsortTime = 1, ConflictIdSorter.conflictIdCount = 63, ConflictIdSorter.conflictIdCycleCount = 0, ConflictResolver.totalTime = 11, ConflictResolver.conflictItemCount = 145, DefaultDependencyCollector.collectTime = 327, DefaultDependencyCollector.transformTime = 16}
[DEBUG] com.vmware.o11n.mojo.pkg:maven - o11n-package - plugin:jar:6.0.2:
[DEBUG] com.vmware.o11n.tool:o11ntool - internal: pot: 6.0.2: compile
[DEBUG] dom4j:dom4j:jar:1.6.1: compile
[DEBUG] xml - apis: xml - apis: jar: 1.0.b2: compile
[DEBUG] org.apache.maven:maven - plugin-api: jar: 2.0: compile
[DEBUG] org.apache.maven:maven - project: pot: 2.0.6: compile
[DEBUG] org.apache.maven:maven - settings: pot: 2.0.6: compile
[DEBUG] org.apache.maven:maven - jar: profile: 2.0.6: compile
[DEBUG] org.apache.maven:maven - model: pot: 2.0.6: compile
[DEBUG] org.apache.maven:maven - artifact-Manager: pot: 2.0.6: compile
[DEBUG] org.apache.maven:maven - repository - metadata:jar:2.0.6: compile
[DEBUG] org.apache.maven:maven - plugin-registry: pot: 2.0.6: compile
[DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1:compile
[DEBUG] junit:junit:jar:4.11:test
[DEBUG] org.hamcrest:hamcrest - core: jar: 1.3:test
[DEBUG] classworlds:classworlds:jar:1.1 - alpha-2: compile
[DEBUG] org.apache.maven:maven - artifact: pot: 2.0.6: compile
[DEBUG] org.apache.maven:maven - archiver: pot: 2.2: compile
[DEBUG] org.codehaus.plexus:plexus - archiver: jar: 1.0 - alpha-7: compile
[DEBUG] org.codehaus.plexus:plexus - utils:jar:1.5.7: compile
[DEBUG] org.apache.maven.shared:maven - filtering: jar: 1.0 - beta-2: compile
[DEBUG] org.apache.maven:maven - monitor: pot: 2.0.6: compile
[DEBUG] org.codehaus.plexus:plexus - interpolation: pot: 1.6: compiles
[DEBUG] org.codehaus.plexus:plexus - compiler-api: jar: 1.8.1: compile
[DEBUG] log4j:log4j:jar:1.2.17:runtime
[DEBUG] commons-io: commons-io: pot: 2.4: compile
[DEBUG] commons-lang: commons-lang: pot: 2.5: compile
[DEBUG] com.vmware.o11n:o11n - util:jar:6.0.2: compile
[DEBUG] org.bouncycastle:bcprov - jdk15on:jar:1.50: compile
[DEBUG] org.bouncycastle:bcpkix - jdk15on:jar:1.50: compile
[DEBUG] com.rubiconproject.oss:jchronic:jar:0.2.6: compile
[DEBUG] net.sf.ehcache:ehcache - core: jar: 2.6.2: compile
[DEBUG] ognl:ognl:jar:2.6.9: compile
[DEBUG] org.codehaus.woodstox:stax2 - api: jar: 3.0.1: compile
[DEBUG] stax:stax - api: jar: 1.0.1: compile
[DEBUG] org.codehaus.woodstox:woodstox - core - asl:jar:4.0.5: compile
[DEBUG] org.slf4j:slf4j - api: jar: 1.6.6: compile
[DEBUG] org.slf4j:slf4j - log4j12:jar:1.6.6: compile
[DEBUG] Commons-codec: commons-codec: pot: 1.8: compile
[DEBUG] org.apache.httpcomponents:httpclient:jar:4.3.5: compile
[DEBUG] Commons-Logging: commons-logging: pot: 1.1.1: compile
[DEBUG] org.apache.httpcomponents:httpcore:jar:4.3.2: compile
[DEBUG] com.vmware.o11n:o11n - model: pot: 6.0.2: compile
[DEBUG] com.vmware.o11n:o11n - security: pot: 6.0.2: compile
[DEBUG] org.springframework:spring - context: pot: 4.0.2.RELEASE: compile
[DEBUG] org.springframework:spring - aop:jar:4.0.2.RELEASE: compile
[DEBUG] org.springframework:spring - expression: pot: 4.0.2.RELEASE: compile
Org.springframework.Security:spring [DEBUG] - security-core: jar: 3.2.3.RELEASE: compile
[DEBUG] aopalliance:aopalliance:jar:1.0: compile
[DEBUG] antlr:antlr:jar:2.7.6: compile
[DEBUG] org.springframework:spring - web: pot: 4.0.2.RELEASE: compile
[DEBUG] org.springframework:spring - beans: pot: 4.0.2.RELEASE: compile
[DEBUG] org.springframework:spring - core: jar: 4.0.2.RELEASE: compile
[DEBUG] org.apache.geronimo.specs:geronimo - jms_1.1_spec:jar:1.1: compile
[DEBUG] com.vmware.o11n:o11n - modelejb-client: pot: 6.0.2: compile
[DEBUG] com.vmware.o11n:o11n - scriptingmodel:jar:6.0.2: compile
[DEBUG] org.mozilla:rhino:jar:1.7R4: compile
[DEBUG] commons-collections: commons-collections: pot: 3.2.1: compile
[DEBUG] com.vmware.o11n:o11n - j2eeutil:jar:6.0.2: compile
[DEBUG] com.vmware.o11n:o11n - sdkapi:jar:6.0.2: compile
[DEBUG] org.hornetq:hornetq - jms-client: pot: 2.2.5.Final:runtime
[DEBUG] org.hornetq:hornetq - client-core: jar: 2.2.5.Final:runtime
[DEBUG] org.jboss.netty:netty:jar:3.2.5.Final:runtime
[DEBUG] Created the new Kingdom maven.api class
[DEBUG] Importation of foreign packages in the Kingdom maven.api class
[DEBUG] Imported: org.apache.maven.wagon.events < plexus.core
[DEBUG] Imported: org.eclipse.aether.impl < plexus.core
[DEBUG] Imported: org.apache.maven.exception < plexus.core
[DEBUG] Imported: org.codehaus.plexus.util.xml.Xpp3Dom < plexus.core
[DEBUG] Imported: org.eclipse.aether.version < plexus.core
[DEBUG] Imported: org.eclipse.aether.metadata < plexus.core
[DEBUG] Imported: javax.enterprise.util. * < plexus.core
[DEBUG] Imported: org.eclipse.aether.collection < plexus.core
[DEBUG] Imported: org.apache.maven.monitor < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.repository < plexus.core
[DEBUG] Imported: org.apache.maven.repository < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.resource < plexus.core
[DEBUG] Imported: org.codehaus.plexus.logging < plexus.core
[DEBUG] Imported: org.apache.maven.profiles < plexus.core
[DEBUG] Imported: org.apache.maven.classrealm < plexus.core
[DEBUG] Imported: org.apache.maven.execution.scope < plexus.core
[DEBUG] Imported: org.eclipse.aether.artifact < plexus.core
[DEBUG] Imported: org.apache.maven.execution < plexus.core
[DEBUG] Imported: org.apache.maven.reporting < plexus.core
[DEBUG] Imported: org.apache.maven.usability < plexus.core
[DEBUG] Imported: org.codehaus.plexus.container < plexus.core
[DEBUG] Imported: org.codehaus.plexus.component < plexus.core
[DEBUG] Imported: org.eclipse.aether.transfer < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.authentication < plexus.core
[DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlSerializer < plexus.core
[DEBUG] Imported: org.apache.maven.lifecycle < plexus.core
[DEBUG] Imported: org.eclipse.aether. * < plexus.core
[DEBUG] Imported: org.eclipse.aether.graph < plexus.core
[DEBUG] Imported: org.codehaus.plexus.classworlds < plexus.core
[DEBUG] Imported: org.eclipse.aether.internal.impl < plexus.core
[DEBUG] Imported: org.eclipse.aether.repository < plexus.core
[DEBUG] Imported: org.eclipse.aether.resolution < plexus.core
[DEBUG] Imported: javax.inject. * < plexus.core
[DEBUG] Imported: org.apache.maven.settings < plexus.core
[DEBUG] Imported: org.codehaus.classworlds < plexus.core
[DEBUG] Imported: org.apache.maven.wagon. * < plexus.core
[DEBUG] Imported: org.apache.maven.toolchain < plexus.core
[DEBUG] Imported: org.eclipse.aether.spi < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.observers < plexus.core
[DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParserException < plexus.core
[DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser < plexus.core
[DEBUG] Imported: org.apache.maven.configuration < plexus.core
[DEBUG] Imported: org.apache.maven.cli < plexus.core
[DEBUG] Imported: org.codehaus.plexus.context < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.authorization < plexus.core
[DEBUG] Imported: org.apache.maven.project < plexus.core
[DEBUG] Imported: org.eclipse.aether.installation < plexus.core
[DEBUG] Imported: org.eclipse.aether.deployment < plexus.core
[DEBUG] Imported: org.codehaus.plexus.lifecycle < plexus.core
[DEBUG] Imported: org.apache.maven.rtinfo < plexus.core
[DEBUG] Imported: org.codehaus.plexus.configuration < plexus.core
[DEBUG] Imported: org.apache.maven.artifact < plexus.core
[DEBUG] Imported: org.apache.maven.model < plexus.core
[DEBUG] Imported: org.slf4j. * < plexus.core
[DEBUG] Imported: javax.enterprise.inject. * < plexus.core
[DEBUG] Imported: org.apache.maven. * < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.proxy < plexus.core
[DEBUG] Imported: org.apache.maven.plugin < plexus.core
[DEBUG] Imported: org.codehaus.plexus. * < plexus.core
[DEBUG] Imported: org.codehaus.plexus.personality < plexus.core
[DEBUG] Filling of class maven.api Kingdom
[DEBUG] Created the new class field extension > com.vmware.o11n.mojo.pkg:maven - o11n-package - plugin:6.0.2
[DEBUG] Importation of foreign packages in class domain extension > com.vmware.o11n.mojo.pkg:maven - o11n-package - plugin:6.0.2
[DEBUG] Imported: maven.api
[DEBUG] Fill class domain extension > com.vmware.o11n.mojo.pkg:maven - o11n-package - plugin:6.0.2
[DEBUG] Included: com.vmware.o11n.mojo.pkg:maven - o11n-package - plugin:jar:6.0.2
[DEBUG] Included: com.vmware.o11n.tool:o11ntool - inner: jar: 6.0.2
[DEBUG] Included: dom4j:dom4j:jar:1.6.1
[DEBUG] Included: xml - apis: xml - apis: jar: 1.0.b2
[DEBUG] Included: org.apache.maven:maven - archiver: jar: 2.2
[DEBUG] Included: org.codehaus.plexus:plexus - archiver: jar: 1.0 - alpha-7
[DEBUG] Included: org.codehaus.plexus:plexus - utils:jar:1.5.7
[DEBUG] Included: org.apache.maven.shared:maven - filtering: jar: 1.0 - beta-2
[DEBUG] Included: org.codehaus.plexus:plexus - interpolation: jar: 1.6
[DEBUG] Included: org.codehaus.plexus:plexus - compiler-api: jar: 1.8.1
[DEBUG] Included: log4j:log4j:jar:1.2.17
[DEBUG] Included: commons-io: commons-io: jar: 2.4
[DEBUG] Included: commons-lang: commons-lang: jar: 2.5
[DEBUG] Included: com.vmware.o11n:o11n - util:jar:6.0.2
[DEBUG] Included: org.bouncycastle:bcprov - jdk15on:jar:1.50
[DEBUG] Included: org.bouncycastle:bcpkix - jdk15on:jar:1.50
[DEBUG] Included: com.rubiconproject.oss:jchronic:jar:0.2.6
[DEBUG] Included: net.sf.ehcache:ehcache - base: jar: 2.6.2
[DEBUG] Included: ognl:ognl:jar:2.6.9
[DEBUG] Included: org.codehaus.woodstox:stax2 - api: jar: 3.0.1
[DEBUG] Included: stax:stax - api: jar: 1.0.1
[DEBUG] Included: org.codehaus.woodstox:woodstox - core - asl:jar:4.0.5
[DEBUG] Included: org.slf4j:slf4j - api: jar: 1.6.6
[DEBUG] Included: org.slf4j:slf4j - log4j12:jar:1.6.6
[DEBUG] Included: Commons-codec: commons-codec: jar: 1.8
[DEBUG] Included: org.apache.httpcomponents:httpclient:jar:4.3.5
[DEBUG] Included: Commons-Logging: commons-logging: jar: 1.1.1
[DEBUG] Included: org.apache.httpcomponents:httpcore:jar:4.3.2
[DEBUG] Included: com.vmware.o11n:o11n - model: jar: 6.0.2
[DEBUG] Included: com.vmware.o11n:o11n - security: jar: 6.0.2
[DEBUG] Included: org.springframework:spring - context: pot: 4.0.2.RELEASE
[DEBUG] Included: org.springframework:spring - aop:jar:4.0.2.RELEASE
[DEBUG] Included: org.springframework:spring - expression: pot: 4.0.2.RELEASE
[DEBUG] Included: org.springframework.security:spring - security-core: jar: 3.2.3.RELEASE
[DEBUG] Included: aopalliance:aopalliance:jar:1.0
[DEBUG] Included: antlr:antlr:jar:2.7.6
[DEBUG] Included: org.springframework:spring - web: pot: 4.0.2.RELEASE
[DEBUG] Included: org.springframework:spring - beans: pot: 4.0.2.RELEASE
[DEBUG] Included: org.springframework:spring - base: pot: 4.0.2.RELEASE
[DEBUG] Included: org.apache.geronimo.specs:geronimo - jms_1.1_spec:jar:1.1
[DEBUG] Included: com.vmware.o11n:o11n - modelejb-client: jar: 6.0.2
[DEBUG] Included: com.vmware.o11n:o11n - scriptingmodel:jar:6.0.2
[DEBUG] Included: org.mozilla:rhino:jar:1.7R4
[DEBUG] Included: commons-collections: commons-collections: jar: 3.2.1
[DEBUG] Included: com.vmware.o11n:o11n - j2eeutil:jar:6.0.2
[DEBUG] Included: com.vmware.o11n:o11n - sdkapi:jar:6.0.2
[DEBUG] Included: org.hornetq:hornetq - jms-client: pot: 2.2.5.Final
[DEBUG] Included: org.hornetq:hornetq - basic-client: pot: 2.2.5.Final
[DEBUG] Included: org.jboss.netty:netty:jar:3.2.5.Final
[DEBUG] Kingdoms of extension for the project sovlabs:o11nplugin - sovlabs-package: package: 6.0.2.1: [ClassRealm [extension > com.vmware.o11n.mojo.pkg:maven - o11n-package - plugin:6.0.2, parent: sun.misc.Launcher$AppClassLoader@7987aeca]]
[DEBUG] Created the new project of Kingdom of class > sovlabs:o11nplugin - sovlabs-package: 6.0.2.1
[DEBUG] Kingdom of settlement project classes > sovlabs:o11nplugin - sovlabs-package: 6.0.2.1
[DEBUG] Looking for ClassRealm package wrapping cycle mappings [project > sovlabs:o11nplugin - sovlabs-package: 6.0.2.1, parent: ClassRealm [maven.api, parent: null]]
[DEBUG] Kingdoms of extension for the project sovlabs:sovlabs:pom:6.0.2.1: (none)
[DEBUG] Rising maps of cycle for pom in packaging of ClassRealm [plexus.core, parent: null]
[DEBUG] Fix the plugin version for org.apache.maven.plugins:maven - install-plugin
[DEBUG] Found no metadata org.apache.maven.plugins:maven-install-plugin/maven-metadata.xml in local (/ Users/tperry/.m2/repository)
[DEBUG] unable to find org.apache.maven.plugins:maven-install-plugin/maven-metadata.xml in http://192.168.159.131:8280 / vco-repo has been cached in the local repository, resolution will not be returned until added by archetype update interval is elapsed or are forced to update
[DEBUG] Query remote ignored for the org.apache.maven.plugins:maven-install-plugin/maven-metadata.xml metadata updates cached locally.
Resolved [DEBUG] version of the plugin for org.apache.maven.plugins:maven - install-plugin repository 2.5.2 (https://repo.maven.apache.org/maven2, by default, releases)
[DEBUG] Fix the plugin version for org.apache.maven.plugins:maven - deploy-plugin
[DEBUG] Found no metadata org.apache.maven.plugins:maven-deploy-plugin/maven-metadata.xml in local (/ Users/tperry/.m2/repository)
[DEBUG] unable to find org.apache.maven.plugins:maven-deploy-plugin/maven-metadata.xml in http://192.168.159.131:8280 / vco-repo has been cached in the local repository, resolution will not be returned until added by archetype update interval is elapsed or are forced to update
[DEBUG] Query remote ignored for the org.apache.maven.plugins:maven-deploy-plugin/maven-metadata.xml metadata updates cached locally.
Resolved [DEBUG] version of the plugin for org.apache.maven.plugins:maven - deploy-plugin for 2.8.2 of the repository (https://repo.maven.apache.org/maven2, by default, releases)
[DEBUG] Adjust the plugin version of compiler - org.apache.maven.plugins:maven - plugin
[DEBUG] Found no metadata org.apache.maven.plugins:maven-compiler-plugin/maven-metadata.xml in local (/ Users/tperry/.m2/repository)
[DEBUG] unable to find org.apache.maven.plugins:maven-compiler-plugin/maven-metadata.xml in http://192.168.159.131:8280 / vco-repo has been cached in the local repository, resolution will not be returned until added by archetype update interval is elapsed or are forced to update
[DEBUG] Query remote ignored for the org.apache.maven.plugins:maven-compiler-plugin/maven-metadata.xml metadata updates cached locally.
Resolved [DEBUG] version of the plugin for org.apache.maven.plugins:maven - compiler-plugin repository 3.3 (https://repo.maven.apache.org/maven2, by default, releases)
[DEBUG] Adjust the plugin prefix o11n-package of [org.apache.maven.plugins, org.codehaus.mojo]
[DEBUG] Plugin solved the prefix o11n-package com.vmware.o11n.mojo.pkg:maven - o11n-package-plugin sovlabs:o11nplugin POM-sovlabs-package: package: 6.0.2.1
[DEBUG] = REACTOR MANUFACTURING PLAN =.
[DEBUG] Project: sovlabs:o11nplugin - sovlabs-package: package: 6.0.2.1
[DEBUG] Tasks: [o11n-package: import-package]
[DEBUG] Style: aggregation
[DEBUG] =======================================================================
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building o11nplugin-sovlabs-Pack 6.0.2.1
[INFO] ------------------------------------------------------------------------
[DEBUG] Adjust the plugin prefix o11n-package of [org.apache.maven.plugins, org.codehaus.mojo]
[DEBUG] Plugin solved the prefix o11n-package com.vmware.o11n.mojo.pkg:maven - o11n-package-plugin sovlabs:o11nplugin POM-sovlabs-package: package: 6.0.2.1
[DEBUG] Default life cycle - > [validate, initiate, generate-sources, process-sources, generate resources, resources process, compiling, process-classes, generate-test-sources, process-test-sources, generate-test-resources and process-test-resources, test-compile, process-test-classes, test, prepare package, package, pre-integration-test, integration test, post-integration-test, check, install, deploy]
[DEBUG] Own lifecycle-> [pre clean, clean, clean post]
[DEBUG] Life cycle of the site-> [prior to the site, site, site of the post and deploy site]
[DEBUG] = GENERATION OF PROJECT PLAN.
[DEBUG] Project: sovlabs:o11nplugin - sovlabs-package: 6.0.2.1
[DEBUG] [Addictions (to collect):]
[DEBUG] [Dependencies (resolve):]
[DEBUG] repositories (dependencies): [added by archetype (http://192.168.159.131:8280 / vco-repo, by default, the versions + snapshots), Central (https://repo.maven.apache.org/maven2, by default, release)]
[DEBUG] repositories (plugins): [added by archetype (http://192.168.159.131:8280 / vco-repo, by default, the versions + snapshots), Central (https://repo.maven.apache.org/maven2, by default, release)]
[DEBUG] -----------------------------------------------------------------------
[DEBUG] Objective: com.vmware.o11n.mojo.pkg:maven - o11n-package - plugin:6.0.2:import - package (by default-cli)
[DEBUG] Style: regular
[DEBUG] Configuration: <? XML version = "1.0" encoding = "UTF-8"? >
< configuration >
< allPackages-default = "false" >$ {allPackages} < / allPackages >
< exportHistory-default = "true" >$ {exportHistory} < / exportHistory >
< ignoreServerCertificate-default = "true" >$ {ignoreServerCertificate} < / ignoreServerCertificate >
sovlabs < packageName > < / packageName >
< project >$ {project} < / project >
< projectName-default = "${project.artifactId}" >$ {projectName} < / ProjectName >
< ServerURI >$ {ServerURI} < / serverUrl >
< targetDirectory >$ {basedir} < / targetDirectory >
< / configuration >
[DEBUG] =======================================================================
[INFO]
[Info]---Maven-o11n-Paquet-plugin:6.0.2:import-Paquet (by default-cli) @ o11nplugin-sovlabs-package-
[DEBUG] Statistics collection of dependency: {ConflictMarker.analyzeTime = 1, ConflictMarker.markTime = 0, ConflictMarker.nodeCount = 211, ConflictIdSorter.graphTime = 1, ConflictIdSorter.topsortTime = 0, ConflictIdSorter.conflictIdCount = 63, ConflictIdSorter.conflictIdCycleCount = 0, ConflictResolver.totalTime = 10, ConflictResolver.conflictItemCount = 145, DefaultDependencyCollector.collectTime = 20, DefaultDependencyCollector.transformTime = 12}
[DEBUG] com.vmware.o11n.mojo.pkg:maven - o11n-package - plugin:jar:6.0.2:
[DEBUG] com.vmware.o11n.tool:o11ntool - internal: pot: 6.0.2: compile
[DEBUG] dom4j:dom4j:jar:1.6.1: compile
[DEBUG] xml - apis: xml - apis: jar: 1.0.b2: compile
[DEBUG] org.apache.maven:maven - plugin-api: jar: 2.0: compile
[DEBUG] org.apache.maven:maven - project: pot: 2.0.6: compile
[DEBUG] org.apache.maven:maven - settings: pot: 2.0.6: compile
[DEBUG] org.apache.maven:maven - jar: profile: 2.0.6: compile
[DEBUG] org.apache.maven:maven - model: pot: 2.0.6: compile
[DEBUG] org.apache.maven:maven - artifact-Manager: pot: 2.0.6: compile
[DEBUG] org.apache.maven:maven - repository - metadata:jar:2.0.6: compile
[DEBUG] org.apache.maven:maven - plugin-registry: pot: 2.0.6: compile
[DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1:compile
[DEBUG] junit:junit:jar:4.11:test
[DEBUG] org.hamcrest:hamcrest - core: jar: 1.3:test
[DEBUG] classworlds:classworlds:jar:1.1 - alpha-2: compile
[DEBUG] org.apache.maven:maven - artifact: pot: 2.0.6: compile
[DEBUG] org.apache.maven:maven - archiver: pot: 2.2: compile
[DEBUG] org.codehaus.plexus:plexus - archiver: jar: 1.0 - alpha-7: compile
[DEBUG] org.codehaus.plexus:plexus - utils:jar:1.5.7: compile
[DEBUG] org.apache.maven.shared:maven - filtering: jar: 1.0 - beta-2: compile
[DEBUG] org.apache.maven:maven - monitor: pot: 2.0.6: compile
[DEBUG] org.codehaus.plexus:plexus - interpolation: pot: 1.6: compiles
[DEBUG] org.codehaus.plexus:plexus - compiler-api: jar: 1.8.1: compile
[DEBUG] log4j:log4j:jar:1.2.17:runtime
[DEBUG] commons-io: commons-io: pot: 2.4: compile
[DEBUG] commons-lang: commons-lang: pot: 2.5: compile
[DEBUG] com.vmware.o11n:o11n - util:jar:6.0.2: compile
[DEBUG] org.bouncycastle:bcprov - jdk15on:jar:1.50: compile
[DEBUG] org.bouncycastle:bcpkix - jdk15on:jar:1.50: compile
[DEBUG] com.rubiconproject.oss:jchronic:jar:0.2.6: compile
[DEBUG] net.sf.ehcache:ehcache - core: jar: 2.6.2: compile
[DEBUG] ognl:ognl:jar:2.6.9: compile
[DEBUG] org.codehaus.woodstox:stax2 - api: jar: 3.0.1: compile
[DEBUG] stax:stax - api: jar: 1.0.1: compile
[DEBUG] org.codehaus.woodstox:woodstox - core - asl:jar:4.0.5: compile
[DEBUG] org.slf4j:slf4j - api: jar: 1.6.6: compile
[DEBUG] org.slf4j:slf4j - log4j12:jar:1.6.6: compile
[DEBUG] Commons-codec: commons-codec: pot: 1.8: compile
[DEBUG] org.apache.httpcomponents:httpclient:jar:4.3.5: compile
[DEBUG] Commons-Logging: commons-logging: pot: 1.1.1: compile
[DEBUG] org.apache.httpcomponents:httpcore:jar:4.3.2: compile
[DEBUG] com.vmware.o11n:o11n - model: pot: 6.0.2: compile
[DEBUG] com.vmware.o11n:o11n - security: pot: 6.0.2: compile
[DEBUG] org.springframework:spring - context: pot: 4.0.2.RELEASE: compile
[DEBUG] org.springframework:spring - aop:jar:4.0.2.RELEASE: compile
[DEBUG] org.springframework:spring - expression: pot: 4.0.2.RELEASE: compile
Org.springframework.Security:spring [DEBUG] - security-core: jar: 3.2.3.RELEASE: compile
[DEBUG] aopalliance:aopalliance:jar:1.0: compile
[DEBUG] antlr:antlr:jar:2.7.6: compile
[DEBUG] org.springframework:spring - web: pot: 4.0.2.RELEASE: compile
[DEBUG] org.springframework:spring - beans: pot: 4.0.2.RELEASE: compile
[DEBUG] org.springframework:spring - core: jar: 4.0.2.RELEASE: compile
[DEBUG] org.apache.geronimo.specs:geronimo - jms_1.1_spec:jar:1.1: compile
[DEBUG] com.vmware.o11n:o11n - modelejb-client: pot: 6.0.2: compile
[DEBUG] com.vmware.o11n:o11n - scriptingmodel:jar:6.0.2: compile
[DEBUG] org.mozilla:rhino:jar:1.7R4: compile
[DEBUG] commons-collections: commons-collections: pot: 3.2.1: compile
[DEBUG] com.vmware.o11n:o11n - j2eeutil:jar:6.0.2: compile
[DEBUG] com.vmware.o11n:o11n - sdkapi:jar:6.0.2: compile
[DEBUG] org.hornetq:hornetq - jms-client: pot: 2.2.5.Final:runtime
[DEBUG] org.hornetq:hornetq - client-core: jar: 2.2.5.Final:runtime
[DEBUG] org.jboss.netty:netty:jar:3.2.5.Final:runtime
[DEBUG] Created the new plugin of Kingdom of class > com.vmware.o11n.mojo.pkg:maven - o11n-package - plugin:6.0.2
[DEBUG] Importation of foreign packages in the Kingdom plugin class > com.vmware.o11n.mojo.pkg:maven - o11n-package - plugin:6.0.2
[DEBUG] Imported: < project > sovlabs:o11nplugin - sovlabs-package: 6.0.2.1
[DEBUG] Filling of class Kingdom plugin > com.vmware.o11n.mojo.pkg:maven - o11n-package - plugin:6.0.2
[DEBUG] Included: com.vmware.o11n.mojo.pkg:maven - o11n-package - plugin:jar:6.0.2
[DEBUG] Included: com.vmware.o11n.tool:o11ntool - inner: jar: 6.0.2
[DEBUG] Included: dom4j:dom4j:jar:1.6.1
[DEBUG] Included: xml - apis: xml - apis: jar: 1.0.b2
[DEBUG] Included: org.apache.maven:maven - archiver: jar: 2.2
[DEBUG] Included: org.codehaus.plexus:plexus - archiver: jar: 1.0 - alpha-7
[DEBUG] Included: org.codehaus.plexus:plexus - utils:jar:1.5.7
[DEBUG] Included: org.apache.maven.shared:maven - filtering: jar: 1.0 - beta-2
[DEBUG] Included: org.codehaus.plexus:plexus - interpolation: jar: 1.6
[DEBUG] Included: org.codehaus.plexus:plexus - compiler-api: jar: 1.8.1
[DEBUG] Included: log4j:log4j:jar:1.2.17
[DEBUG] Included: commons-io: commons-io: jar: 2.4
[DEBUG] Included: commons-lang: commons-lang: jar: 2.5
[DEBUG] Included: com.vmware.o11n:o11n - util:jar:6.0.2
[DEBUG] Included: org.bouncycastle:bcprov - jdk15on:jar:1.50
[DEBUG] Included: org.bouncycastle:bcpkix - jdk15on:jar:1.50
[DEBUG] Included: com.rubiconproject.oss:jchronic:jar:0.2.6
[DEBUG] Included: net.sf.ehcache:ehcache - base: jar: 2.6.2
[DEBUG] Included: ognl:ognl:jar:2.6.9
[DEBUG] Included: org.codehaus.woodstox:stax2 - api: jar: 3.0.1
[DEBUG] Included: stax:stax - api: jar: 1.0.1
[DEBUG] Included: org.codehaus.woodstox:woodstox - core - asl:jar:4.0.5
[DEBUG] Included: org.slf4j:slf4j - api: jar: 1.6.6
[DEBUG] Included: org.slf4j:slf4j - log4j12:jar:1.6.6
[DEBUG] Included: Commons-codec: commons-codec: jar: 1.8
[DEBUG] Included: org.apache.httpcomponents:httpclient:jar:4.3.5
[DEBUG] Included: Commons-Logging: commons-logging: jar: 1.1.1
[DEBUG] Included: org.apache.httpcomponents:httpcore:jar:4.3.2
[DEBUG] Included: com.vmware.o11n:o11n - model: jar: 6.0.2
[DEBUG] Included: com.vmware.o11n:o11n - security: jar: 6.0.2
[DEBUG] Included: org.springframework:spring - context: pot: 4.0.2.RELEASE
[DEBUG] Included: org.springframework:spring - aop:jar:4.0.2.RELEASE
[DEBUG] Included: org.springframework:spring - expression: pot: 4.0.2.RELEASE
[DEBUG] Included: org.springframework.security:spring - security-core: jar: 3.2.3.RELEASE
[DEBUG] Included: aopalliance:aopalliance:jar:1.0
[DEBUG] Included: antlr:antlr:jar:2.7.6
[DEBUG] Included: org.springframework:spring - web: pot: 4.0.2.RELEASE
[DEBUG] Included: org.springframework:spring - beans: pot: 4.0.2.RELEASE
[DEBUG] Included: org.springframework:spring - base: pot: 4.0.2.RELEASE
[DEBUG] Included: org.apache.geronimo.specs:geronimo - jms_1.1_spec:jar:1.1
[DEBUG] Included: com.vmware.o11n:o11n - modelejb-client: jar: 6.0.2
[DEBUG] Included: com.vmware.o11n:o11n - scriptingmodel:jar:6.0.2
[DEBUG] Included: org.mozilla:rhino:jar:1.7R4
[DEBUG] Included: commons-collections: commons-collections: jar: 3.2.1
[DEBUG] Included: com.vmware.o11n:o11n - j2eeutil:jar:6.0.2
[DEBUG] Included: com.vmware.o11n:o11n - sdkapi:jar:6.0.2
[DEBUG] Included: org.hornetq:hornetq - jms-client: pot: 2.2.5.Final
[DEBUG] Included: org.hornetq:hornetq - basic-client: pot: 2.2.5.Final
[DEBUG] Included: org.jboss.netty:netty:jar:3.2.5.Final
[DEBUG] Excluded: org.apache.maven:maven - plugin-api: jar: 2.0
[DEBUG] Excluded: org.apache.maven:maven - project: jar: 2.0.6
[DEBUG] Excluded: org.apache.maven:maven - settings: jar: 2.0.6
[DEBUG] Excluded: org.apache.maven:maven - view profile: jar: 2.0.6
[DEBUG] Excluded: org.apache.maven:maven - model: jar: 2.0.6
[DEBUG] Excluded: org.apache.maven:maven - artifact-Manager: jar: 2.0.6
[DEBUG] Excluded: org.apache.maven:maven - repository - metadata:jar:2.0.6
[DEBUG] Excluded: org.apache.maven:maven - plugin-registry: jar: 2.0.6
[DEBUG] Excluded: org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1
[DEBUG] Excluded: junit:junit:jar:4.11
[DEBUG] Excluded: org.hamcrest:hamcrest - core: jar: 1.3
[DEBUG] Excluded: classworlds:classworlds:jar:1.1 - alpha-2
[DEBUG] Excluded: org.apache.maven:maven - artifact: jar: 2.0.6
[DEBUG] Excluded: org.apache.maven:maven - monitor: jar: 2.0.6
[DEBUG] Configuration of mojo com.vmware.o11n.mojo.pkg:maven - o11n-package - plugin:6.0.2:import - Kingdom ClassRealm plugin package [plugin > com.vmware.o11n.mojo.pkg:maven - o11n-package - plugin:6.0.2, parent: sun.misc.Launcher$AppClassLoader@7987aeca]
[DEBUG] Mojo configuration ' com.vmware.o11n.mojo.pkg:maven - o11n-package - plugin:6.0.2:import - package "with base-> Configurator
[DEBUG] (f) allPackages = false
[DEBUG] (f) exportHistory = true
[DEBUG] (f) ignoreServerCertificate = true
[DEBUG] (f) packageName = sovlabs
[DEBUG] (f) = MavenProject project: sovlabs:o11nplugin - sovlabs-package: 6.0.2.1 @ /Users/tperry/development/java/sovlabs/o11nplugin-sovlabs-package/pom.xml
[DEBUG] (f) projectName = o11nplugin-sovlabs-package
[DEBUG] (f) serverUrl = vcoadmin:[email protected]:8281
[DEBUG] (f) targetDirectory = / Users/tperry/development/java/sovlabs/o11nplugin-sovlabs-package
[DEBUG] - configuration - end
o11nplugin-sovlabs-package
true
[DEBUG] Connection to server VMO: 192.168.159.130:8281
[DEBUG] Create Session
trustStore is: keystore.pks
trustStore type is: jks
trustStore provider is:
init truststore
adding that cert trust:
Subject: CN = localhost.sovsystems.com, OR = VMware, O = VMware, C = US
Issuer: CN = localhost.sovsystems.com, OR = VMware, O = VMware, C = US
Algorithm: RSA; Serial number: 0x14e0c0cf436
Valid from Thursday, June 18 09:40:52 EDT 2015 until Monday, June 16 at 09:40:52 EDT 2025
adding that cert trust:
Subject: CN = localhost.localdom, OR = VMware, O = VMware, C = US
Issuer: CN = localhost.localdom, OR = VMware, O = VMware, C = US
Algorithm: RSA; Serial number: 0x14e1acfbd66
Valid from 21 June to 06:28:18 EDT Sun 2015 until Thursday, June 19 at 06:28:18 EDT 2025
trigger the seeding of SecureRandom
done seeding SecureRandom
log4j: WARN no appenders could be found for logger (org.apache.http.impl.conn.BasicClientConnectionManager).
log4j: WARN Please initialize log4j correctly system.
log4j: WARN see http://logging.Apache.org/log4j/1.2/FAQ.html#noconfig for more information.
principal, setSoTimeout (0) called
Allow the dangerous renegotiation: true
Allow legacy Hello messages: true
Is the first handshake: true
Is secure renegotiation: false
% No session caching client
ClientHello, TLSv1
RandomCookie: GMT: 1418206677 bytes = {70, 53, 184, 192, 171, 103, 63, 205, 239, 130, 185, 55, 52, 10, 142, 255, 182, 157, 75, 73, 218, 99, 55, 109, 97, 21, 99, 190}
Session ID: {}
Cipher suites: [SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5, SSL_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA TLS_EMPTY_RENEGOTIATION_INFO_SCSV]
Compression methods: {0}
***
[write] MD5 and SHA1 hashes: len = 81
0000: 01 00 00 4 03 01 55 88 1 46 35 67 AB C0 B8 D5... M... U.... F5... g
0010: 3F CD 82 37 34 8 0A FF B9 EF B6 4B 9 D 49 DA 63?... 74... KI.c
0020: 37 6 61 15 63 BE 00 00 26 00 04 00 05 00 00... &... 7ma.c 2F /.
0030: 35 00 33 00 39 00 32 00 38 00 0 A 00 16 00 13 00 5.3.9.2.8...
0040: 09 00 15 00 12 00 03 00 08 00 14 00 11 00 FF 01...
0050: 00 .
hand WRITING: TLSv1 Handshake, length = 81
[write] MD5 and SHA1 hashes: len = 110
0000: 01 03 01 00 45 00 00 00 20 00 00 04 01 00 80 00... E... .......
0010: 00 05 00 00 00 00 35 00 00 33 00 00 39 00 00 2F... /... 5.3.9.
0020: 32 00 00 38 00 00 0 A 07 00 C0 00 00 16 00 00 13 2.8...
0030: 00 00 09 06 00 40 00 00 15 00 00 12 00 00 03 02... @...
0040: 00 80 00 00 08 00 00 14 00 00 11 00 00 FF 55 88... U.
0050: 1ST 46 35 67 AB C0 B8 D5 3F CD 82 37 34 0A B9 EF... F5... g?... 74.
0060: 8 FF B6 9 D 4B 49 DA 63 37 6 D 61 15 63 OR... KI.c7ma.c.
hand WRITING: message of SSLv2 client hello, length = 110
[Raw write]: length = 112
0000: 6 80 01 03 01 00 45 00 00 00 20 00 00 04 01 00. n... E... .....
0010: 80 00 00 05 00 00 00 00 35 00 00 33 00 00 39 2F... /... 5.3.9
0020: 00 00 32 00 00 38 00 00 0 A 07 00 00 00 16 00 C0... 2..8..........
0030: 00 13 00 00 09 06 00 40 00 00 15 00 00 12 00 00... @...
0040: 03 02 00 80 00 00 08 00 00 14 00 00 11 00 00 FF...
0050:55 88 1 46 35 67 AB C0 B8 D5 3F CD EF B9 37 U 82... F5... g?... 7
0060: 0 34A 8 FF B6 9 d 4 b 49 DA 63 37 6 D 61 15 63 EITHER 4... KI.c7ma.c.
[First reading]: length = 5
0000: 15 03 01 00 02...
[First reading]: length = 2
0000: 02 28 . (
main, READ: alert TLSv1, length = 2
principal, RECV TLSv1 ALERT: handshake_failure fatal.
principal, called closeSocket()
principal, exception handling: javax.net.ssl.SSLHandshakeException: received fatal alert: handshake_failure
principal, called close()
closeInternal (true) main, called
[WARNING] Ignored exceptions.
javax.net.ssl.SSLHandshakeException: received fatal alert: handshake_failure
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:136)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:1822)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1004)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1188)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1215)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1199)
at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:535)
at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:304)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
at ch.dunes.model.client.VcoEndpointLocator.tryHardAndLocateEndpoint(VcoEndpointLocator.java:44)
at com.vmware.o11n.model.support.proxy.RemoteHttpVSOFactoryInvocationHandler.getServiceUrl(RemoteHttpVSOFactoryInvocationHandler.java:308)
at com.vmware.o11n.model.support.proxy.RemoteHttpVSOFactoryInvocationHandler.init(RemoteHttpVSOFactoryInvocationHandler.java:242)
at com.vmware.o11n.tools.client.VSOTrustAllFactoryClient.initHandler(VSOTrustAllFactoryClient.java:47)
at ch.dunes.model.client.VSOFactoryClient.connectRemoteProxy(VSOFactoryClient.java:224)
at ch.dunes.model.client.VSOFactoryClient.connect(VSOFactoryClient.java:302)
at ch.dunes.model.client.VSOFactoryClient.connect(VSOFactoryClient.java:262)
at ch.dunes.model.client.VSOFactoryClient.connect(VSOFactoryClient.java:269)
at com.vmware.o11n.mojo.pkg.ImportPackageMojo.connectVCOServer(ImportPackageMojo.java:205)
at com.vmware.o11n.mojo.pkg.ImportPackageMojo.execute(ImportPackageMojo.java:130)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
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 org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
trustStore is: keystore.pks
trustStore type is: jks
trustStore provider is:
init truststore
adding that cert trust:
Subject: CN = localhost.sovsystems.com, OR = VMware, O = VMware, C = US
Issuer: CN = localhost.sovsystems.com, OR = VMware, O = VMware, C = US
Algorithm: RSA; Serial number: 0x14e0c0cf436
Valid from Thursday, June 18 09:40:52 EDT 2015 until Monday, June 16 at 09:40:52 EDT 2025
adding that cert trust:
Subject: CN = localhost.localdom, OR = VMware, O = VMware, C = US
Issuer: CN = localhost.localdom, OR = VMware, O = VMware, C = US
Algorithm: RSA; Serial number: 0x14e1acfbd66
Valid from 21 June to 06:28:18 EDT Sun 2015 until Thursday, June 19 at 06:28:18 EDT 2025
trigger the seeding of SecureRandom
done seeding SecureRandom
trigger the seeding of SecureRandom
done seeding SecureRandom
principal, setSoTimeout (0) called
Allow the dangerous renegotiation: true
Allow legacy Hello messages: true
Is the first handshake: true
Is secure renegotiation: false
% No session caching client
ClientHello, TLSv1
RandomCookie: GMT: 1418206677 bytes = {5, 153, 124, 38, 128, 81, 162, 210, 153, 175, 228, 69, 197, 151, 238, 200, 164, 180, 214, 141, 25, 106, 189, 152, 128, 170, 31, 196}
Session ID: {}
Cipher suites: [SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5, SSL_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA TLS_EMPTY_RENEGOTIATION_INFO_SCSV]
Compression methods: {0}
***
[write] MD5 and SHA1 hashes: len = 81
0000: 01 00 00 4 03 01 55 88 1 05 99 7 26 80 51 D5... M... U... &. Q
0010: A2 D2 99 AF 45 C5 97 EA A4 B4 D6 8 D C8 E4 6 TO 19... E.........j
0020: 98 BD 80 AA 1F 00 00 26 00 04 00 05 00 00 2F C4... &... /.
0030: 35 00 33 00 39 00 32 00 38 00 0 A 00 16 00 13 00 5.3.9.2.8...
0040: 09 00 15 00 12 00 03 00 08 00 14 00 11 00 FF 01...
0050: 00 .
hand WRITING: TLSv1 Handshake, length = 81
[write] MD5 and SHA1 hashes: len = 110
0000: 01 03 01 00 45 00 00 00 20 00 00 04 01 00 80 00... E... .......
0010: 00 05 00 00 00 00 35 00 00 33 00 00 39 00 00 2F... /... 5.3.9.
0020: 32 00 00 38 00 00 0 A 07 00 C0 00 00 16 00 00 13 2.8...
0030: 00 00 09 06 00 40 00 00 15 00 00 12 00 00 03 02... @...
0040: 00 80 00 00 08 00 00 14 00 00 11 00 00 FF 55 88... U.
0050: 1ST D5 05 99 7 26 80 51 A2 D2 99 AF E4 C5 97 45... &. Q..... E...
0060: EE C8 A4 B4 D6 8 D 19 6a BD 98 80 AA 1F C4... j...
hand WRITING: message of SSLv2 client hello, length = 110
[Raw write]: length = 112
0000: 6 80 01 03 01 00 45 00 00 00 20 00 00 04 01 00. n... E... .....
0010: 80 00 00 05 00 00 00 00 35 00 00 33 00 00 39 2F... /... 5.3.9
0020: 00 00 32 00 00 38 00 00 0 A 07 00 00 00 16 00 C0... 2..8..........
0030: 00 13 00 00 09 06 00 40 00 00 15 00 00 12 00 00... @...
0040: 03 02 00 80 00 00 08 00 00 14 00 00 11 00 00 FF...
0050:55 88 1st D5 05 99 7 26 80 51 A2 D2 99 AF E4 45 u... &. Q..... E
0060: C5 97 EE C8 A4 B4 D6 8 D 19 6a BD 98 80 AA 1F C4... j...
[First reading]: length = 5
0000: 15 03 01 00 02...
[First reading]: length = 2
0000: 02 28 . (
main, READ: alert TLSv1, length = 2
principal, RECV TLSv1 ALERT: handshake_failure fatal.
principal, called closeSocket()
principal, exception handling: javax.net.ssl.SSLHandshakeException: received fatal alert: handshake_failure
principal, called close()
closeInternal (true) main, called
[ERROR] Org.springframework.remoting.RemoteAccessException: couldn't access HTTP calling remote service to [https://192.168.159.130:8281 https://192.168.159.130: 8281/vco]; nested exception is javax.net.ssl.SSLHandshakeException: received fatal alert: handshake_failure
Org.springframework.remoting.RemoteAccessException [DEBUG]: could not access HTTP calling remote service to [https://192.168.159.130:8281 https://192.168.159.130: 8281/vco]; nested exception is javax.net.ssl.SSLHandshakeException: received fatal alert: handshake_failure
ch.dunes.util.DunesServerException: org.springframework.remoting.RemoteAccessException: could not access HTTP calling remote service to [https://192.168.159.130:8281 https://192.168.159.130: 8281/vco]; nested exception is javax.net.ssl.SSLHandshakeException: received fatal alert: handshake_failure
at ch.dunes.model.client.VSOFactoryClient.connectRemoteProxy(VSOFactoryClient.java:244)
at ch.dunes.model.client.VSOFactoryClient.connect(VSOFactoryClient.java:302)
at ch.dunes.model.client.VSOFactoryClient.connect(VSOFactoryClient.java:262)
at ch.dunes.model.client.VSOFactoryClient.connect(VSOFactoryClient.java:269)
at com.vmware.o11n.mojo.pkg.ImportPackageMojo.connectVCOServer(ImportPackageMojo.java:205)
at com.vmware.o11n.mojo.pkg.ImportPackageMojo.execute(ImportPackageMojo.java:130)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
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 org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.springframework.remoting.RemoteAccessException: could not access HTTP calling remote service to [https://192.168.159.130:8281 https://192.168.159.130: 8281/vco]; nested exception is javax.net.ssl.SSLHandshakeException: received fatal alert: handshake_failure
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.convertHttpInvokerAccessException(HttpInvokerClientInterceptor.java:216)
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.invoke(HttpInvokerClientInterceptor.java:147)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207)
to com.sun.proxy. $Proxy21.authenticate (unknown Source)
at com.vmware.o11n.model.support.proxy.RemoteHttpVSOFactoryInvocationHandler.connect(RemoteHttpVSOFactoryInvocationHandler.java:106)
at ch.dunes.model.client.VSOAccessPointAwareFactoryClient.connectWithToken(VSOAccessPointAwareFactoryClient.java:31)
at ch.dunes.model.client.VSOFactoryClient.connectRemoteProxy(VSOFactoryClient.java:225)
... more than 26
Caused by: javax.net.ssl.SSLHandshakeException: received fatal alert: handshake_failure
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:136)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:1822)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1004)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1188)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1215)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1199)
at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:535)
at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:304)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
at org.springframework.remoting.httpinvoker.HttpComponentsHttpInvokerRequestExecutor.executeHttpPost(HttpComponentsHttpInvokerRequestExecutor.java:213)
at org.springframework.remoting.httpinvoker.HttpComponentsHttpInvokerRequestExecutor.doExecuteRequest(HttpComponentsHttpInvokerRequestExecutor.java:147)
at org.springframework.remoting.httpinvoker.AbstractHttpInvokerRequestExecutor.executeRequest(AbstractHttpInvokerRequestExecutor.java:138)
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.executeRequest(HttpInvokerClientInterceptor.java:194)
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.executeRequest(HttpInvokerClientInterceptor.java:176)
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.invoke(HttpInvokerClientInterceptor.java:144)
... 32 more
[DEBUG] Disconnect from the server
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.072 s
[INFO] Finished in: 2015-06 - 22 T 10: 42:29 - 04:00
[INFO] Final memory: 8 M / 81 M
[INFO] ------------------------------------------------------------------------
Finalizer called close()
Finalizer, call closeInternal (true)
Finalizer called close()
Finalizer, call closeInternal (true)
[ERROR] cannot run the purpose com.vmware.o11n.mojo.pkg:maven - o11n-package - plugin:6.0.2:import - package (by default-cli) on the project o11nplugin-sovlabs-package: unable to connect to the server by using the url "[vcoadmin:[email protected]:8281]": org.springframework.remoting.RemoteAccessException: could not access HTTP calling remote service to [https://192.168.159.130:8281 https://192.168.159.130: 8281/vco]; nested exception is javax.net.ssl.SSLHandshakeException: received fatal alert: handshake_failure--> [help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: cannot run the purpose com.vmware.o11n.mojo.pkg:maven - o11n-package - plugin:6.0.2:import - package (by default-cli) on the project o11nplugin-sovlabs-package: unable to connect to the server by using the url "[vcoadmin:[email protected]:8281]".
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
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 org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: unable to connect to the server by using the url "[vcoadmin:[email protected]:8281]".
at com.vmware.o11n.mojo.pkg.ImportPackageMojo.connectVCOServer(ImportPackageMojo.java:211)
at com.vmware.o11n.mojo.pkg.ImportPackageMojo.execute(ImportPackageMojo.java:130)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
Caused by: ch.dunes.util.DunesServerException: org.springframework.remoting.RemoteAccessException: could not access HTTP calling remote service to [https://192.168.159.130:8281 https://192.168.159.130: 8281/vco]; nested exception is javax.net.ssl.SSLHandshakeException: received fatal alert: handshake_failure
at ch.dunes.model.client.VSOFactoryClient.connectRemoteProxy(VSOFactoryClient.java:244)
at ch.dunes.model.client.VSOFactoryClient.connect(VSOFactoryClient.java:302)
at ch.dunes.model.client.VSOFactoryClient.connect(VSOFactoryClient.java:262)
at ch.dunes.model.client.VSOFactoryClient.connect(VSOFactoryClient.java:269)
at com.vmware.o11n.mojo.pkg.ImportPackageMojo.connectVCOServer(ImportPackageMojo.java:205)
... more than 22
Caused by: org.springframework.remoting.RemoteAccessException: could not access HTTP calling remote service to [https://192.168.159.130:8281 https://192.168.159.130: 8281/vco]; nested exception is javax.net.ssl.SSLHandshakeException: received fatal alert: handshake_failure
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.convertHttpInvokerAccessException(HttpInvokerClientInterceptor.java:216)
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.invoke(HttpInvokerClientInterceptor.java:147)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207)
to com.sun.proxy. $Proxy21.authenticate (unknown Source)
at com.vmware.o11n.model.support.proxy.RemoteHttpVSOFactoryInvocationHandler.connect(RemoteHttpVSOFactoryInvocationHandler.java:106)
at ch.dunes.model.client.VSOAccessPointAwareFactoryClient.connectWithToken(VSOAccessPointAwareFactoryClient.java:31)
at ch.dunes.model.client.VSOFactoryClient.connectRemoteProxy(VSOFactoryClient.java:225)
... more than 26
Caused by: javax.net.ssl.SSLHandshakeException: received fatal alert: handshake_failure
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:136)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:1822)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1004)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1188)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1215)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1199)
at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:535)
at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:304)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
at org.springframework.remoting.httpinvoker.HttpComponentsHttpInvokerRequestExecutor.executeHttpPost(HttpComponentsHttpInvokerRequestExecutor.java:213)
at org.springframework.remoting.httpinvoker.HttpComponentsHttpInvokerRequestExecutor.doExecuteRequest(HttpComponentsHttpInvokerRequestExecutor.java:147)
at org.springframework.remoting.httpinvoker.AbstractHttpInvokerRequestExecutor.executeRequest(AbstractHttpInvokerRequestExecutor.java:138)
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.executeRequest(HttpInvokerClientInterceptor.java:194)
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.executeRequest(HttpInvokerClientInterceptor.java:176)
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.invoke(HttpInvokerClientInterceptor.java:144)
... 32 more
[ERROR]
[ERROR]
[ERROR] For more information about errors and possible solutions, please read the following articles:
[ERROR] [help 1] http://cwiki.Apache.org/Confluence/display/Maven/MojoExecutionException
Cessna:o11nplugin - sovlabs-package tperry$
Hi Tim,.
Of the handshake could be caused by your customer send message hello SSLv2 client while vRO 6.x server supports TLS only.
The debug output, it seems that you use Java 1.6u65. I suggest to try with a recent version of Java 1.7 (AFAIK, SSLv2 client hello is removed from the list of client protocol by default for Java 1.7).
-
My Department has recently installed CF11 on a new server redhat. I can not monitor working properly. I activated the surveillance and profiling and Monitoring Server. I can get the monitor to launch and am able to connect. However, it shows not all applications at all. In addition, any changes I make in the monitor (for example tracking alerts or # last to list jobs that are more than # seconds) without saving. Any thoughts? I was able to define alert configurations via the API, but they are not "seems to work.
After a lot of headbanging, I realized that 'impossible to invoke CFCS' error is the result of trying to run the monitor via the SSL protocol. I added - Dcoldfusion.disablejsafe = true in the file next and restarted CF. If I run the monitor of the https://srv-webdev-01/administrator/, it opens the URL for the monitor as http://srv-webdev-01:5500/CFIDE/administrator/monitor/launch-monitor.html. Then he tells me that I'm disconnected from the CF server and makes me authenticate. When I do the start buttons are missing. If I have http://srv-webdev-01/administrator connection and start the monitor, it works. Once I'm connected to the administrator under http and https, I can launch the monitor with success.
Is it possible to only have to authenticate over https?
-
Problem with JMS via the SSL protocol in clustered environment
Hello
We run Weblogic 11 g Cluster (area) which consists of admin server and two managed server MS1, MS2.
LIKE and run it on the computer 1, MS1 MS2 runs on machine 2. Both machines have two network interfaces, a public used for client connections and an intern for cluster communication, monitoring etc. The default channel of each Weblogic Server is listening on the internal network interface, and Moreover we have two channels (for http and t3 Protocol) configured to the public interface.
The two managed servers are JMS provider and there is a JMS Module myModule in the field with the following JMS resources: custom connection factory myConnFactory (Load Balancing active = true = false server affinity, target: entire cluster JMS) and myQueue, which is a uniform distributed queue (targets: MS1, MS2). The queue is accessed by its logical JNDI name, but she is stuck on each managed server.
JMS communication flows normally through t3 dedicated listening on the public interface. However, a new external client will send messages to myQueue and communication must be encrypted for security reasons. For this reason, we have implemented SSL. Instead activate a DefaultSecure channel, we left 'SSL listen Port active' = false (as the default channel would be linked to the internal network interface) and created a new channel T3SChannel t3s Protocol on the public interface for incoming client connections.
The customer creates a t3s connection to the cluster (through T3SChannel) and gets the factory connections and the queue, use the JNDI ( source) search. The JMS connection is in real-time with MS1. If we want to create two consumers for this queue, the consumer of fist is created the MS1 and the second will be created on MS2 (thanks to active balancing). However, the creation of the second consumer fails with an exception (it is thrown on the client):
java.rmi.ConnectException: no valid port known for: "DefaultSecure [t3s]: t3s (t3s): mserver1 - internal .company .com: 56213:null:-1 ';" No router available at destination
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:464)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:396)
at weblogic.rjvm.RJVMImpl.ensureConnectionEstablished(RJVMImpl.java:303)
at weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:347)
at weblogic.rjvm.RJVMImpl.getRequestStreamInternal(RJVMImpl.java:610)
... 18 more
We were told that the exception can be avoided with t3s < default protocol > - < / default protocol > element (default is t3) added to the config.XML in the Weblogic domain. If we configure t3s as default protocol, we also need to activate the DefaultSecure channel on each server and then everything works and the customer is able to correctly create consumers.
However, as a side effect, the entire cluster on weblogic.rjvm communication layer and then by t3s. We do not want that because internal cluster communications are set enough with other methods and it will have impact on the notable performance in the production environment. In principle, it should be possible to enable the external client to connect to the JMS provider via the channel new, safe, without affecting the existing internal communication in the cluster (which should be a black box for the customer).
My question: is it possible to run the example described without defining the default protocol to t3s?
Thanks for the reply.My question: is it possible to run the example described without defining the default protocol to t3s?
Thanks for the very clear problem description. I checked with our customer support guru and I'm sure that the answer to your question is no, I think you have encountered a known problem and have already struck with the recommended workaround.
That said, you can be able to avoid at least partially the problem by setting "server-affinity = true" on your CF. as you probably well know, affinity = false encourages consumer and producer traffic to route customer, on its server host connection, then possibly on a "second leap" to another server in the cluster. It looks like the attempt of an implicit downgrade of a secure request origin SSL in the first bond on a channel not secure in this second jump is to throw the exception.
HTH,
Tom
-
Arguments for command line for sample ViSDK "VITop' of performance monitoring
HI people,
I tried to get the samples to monitor performance Java works. 'PrintCounters' and 'Basics' work very well, but I had no luck with "VITop.
Does anyone know what is expected in the unit - central and -memory arguments? I tried passing values 'key' for CPU counters and mem spat for example PrintCounters, but that has not worked. I tried descripive names spat on the 'Basics', but that no longer works.
My basic command line is:
* java - Djavax .net .ssl .trustStore = [keystore]
com.vmware.samples.performance.VITop - host -username
-password -url -"Use of the processor (on average)" cpu - memory
"Use of memory (on average)."
I tried:
-cpu 1 - 512 memory
and other variations.
Any help most appreciated,
See you soon
Gary
The 'cpu' and 'memory' parameters expect the list of correspondents under respective groups of counters separated by commas.
http://www.VMware.com/support/developer/VC-SDK/visdk2xpubs/ReferenceGuide/CPU.html
http://www.VMware.com/support/developer/VC-SDK/visdk2xpubs/ReferenceGuide/mem.html
So, an example of the command to run the example will be:
Run.bat com.vmware.samples.performance.VITop - url < url > - < username > username - password password <>- < Home >-'use of UC, ready'-'use' mem, granted
I hope this helps.
Neha
-
How to configure JRockitMS to a managed server monitor Urgent please
How to set up the Mission of Rockit J control for a managed server monitor Urgent pleaseJAVA_OPTIONS = "${JAVA_OPTIONS} {JAVA_PROPERTIES} - Dfile.encoding = ISO8859_1 - Xmanagement: ssl = false, authenticate = false, autodiscovery = true, port = 6008 - Dwlw.iterativeDev = ${iterativeDevFlag} - Dwlw.testConsole = ${testConsoleFlag} - Dweblogic.security.SSL.ignoreHostnameVerification = true - Dwlw.logErrorsToConsole = ${logErrorsToConsoleFlag}" "
Add this tag to your managed server startup script and the go to the console command j rockit mission of the bin folder. / jrmc console opens and you can see listening 6008 port to the server run on the left side and then you can monitor leaks.
Please let me know if you have any questions.
Thank you
Vivek
-
Need help to find an adapter for a third-party monitor
Hi all! I find myself in need of a little guidance, and I hope that someone out there will have a quick n easy for me...
I have a Mid-2011 27 'iMac. which has two ports Thunderbolt It is taken with a Wacom tablet that I use constantly, and the other is made by an external hard drive to a solid state, which has a built-in cable to Thunderbolt (no way to hang it on a different port). I also have a 27 "HP monitor that is currently connected via an HDMI USB adapter.
The problem is that the HP monitor is actual "jiggy" - the USB does not seem fast enough to deal with requests for the monitor. It is almost unusable. I know I should run it via a HDMI adapter Thunderbolt, but as I have already mentioned the two my Thunderbolt ports are already in use.
Someone at - it ideas? I need sort of three to two ports Thunderbolt hooks, but I can't seem to find anything for less than $300 that would work. (I am illiterate when it comes to the different cables, adapters, ports, etc., so I hope someone can point me in the right direction by using short words... Most of the products that I travel through list specifications that me Chicane).
The monitor has two HDMIs and a VGA port, and my iMac has a Firewire 800 port, if that helps at all...
2011 iMac have only 1 Thunderbolt port and there is no such thing as a Mid-2011, you must have an iMac of year later, if it has 2 ports Thunderbolt. All the 27 "iMacs, from 2012 to 2015 the current have 2 ports Thunderbolt.
-
MBP: monitor detected but no image except by VGA
I have a MBP of Mid 2012 running latest El Capitan.
When I connect to an external monitor, it is detected correctly in views (exact name, resolution, etc.), but the monitor doesn't detect any image from the portable computer. I tried the DVI - D and DisplayPort with various cables and monitors with the same result, but a picture appears if I connect to VGA. It started in the past week.
The built-in display does not work normally.
Looks like a hardware failure in the computer DisplayPort connector laptop, as the pins are worn or something?
Any other ideas?
Hi johngirvin,
Thank you for using communities Support from Apple. Sorry to hear that you had these display problems with your MacBook Pro. Looks like you've been on the right track trying to solve this problem. If you continue to have problems, you can find the additional steps described in the following article useful, up to and including contacting Apple Support if necessary:
Get help with graphical problems on the external displays connected to your Mac - Apple Support
Concerning
Maybe you are looking for
-
Chapter page numbering problem
AFTE 200 pages, chapter of Pages.app numbering begins to turn: instead of going 5.2.6 it again 1 and does not change even if I change the numbering of 'Start at last' to ' start to...» » I deleted & re-inserted chapter / section a dozen times now, do
-
How can I comment on this forum since my cliq xt?
The usual browser won't let me do it. I tried to search for a question or a response similar but had no luck. Thank you very much for your answers. : )
-
Error - 646, while trying to install KB977304.
Any attempt KB977304 installation. Install fails error 646, been round on Help FAQ sites and this is the second time that I have followed the links on this forum. Tried deleting download malicious malware it freezes also. Don't know what a manual dow
-
Could not remove Microsoft office Cick-to-run 2010 (Beta)
I tried several times to remove it. Bought office 2010 year last but was unable to install it because I can't delete this!
-
When I press the camera button nothing happens. How to activate the camera button to open the camera application?