[jira] [Updated] (CLOUDSTACK-1489) cloudstack agent plugin classpath is missing

2013-03-02 Thread Hiroaki Kawai (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hiroaki Kawai updated CLOUDSTACK-1489:
--

Component/s: KVM

 cloudstack agent plugin classpath is missing
 

 Key: CLOUDSTACK-1489
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1489
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: pre-4.0.0, 4.0.0, 4.0.1, 4.0.2, 4.1.0, 4.2.0
 Environment: Linux kvm
Reporter: Hiroaki Kawai

 There is no place to put plugin jar files for cloudstack agent program now, 
 while management server program has default @PLUGINJAVADIR@ where plugin 
 classes will be loaded into server at startup. We will need to load a class, 
 for example when we try to use a custom libvirt.vif.driver which can be 
 configured at agent.properties.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Created] (CLOUDSTACK-1489) cloudstack agent plugin classpath is missing

2013-03-02 Thread Hiroaki Kawai (JIRA)
Hiroaki Kawai created CLOUDSTACK-1489:
-

 Summary: cloudstack agent plugin classpath is missing
 Key: CLOUDSTACK-1489
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1489
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.0.0, pre-4.0.0, 4.0.1, 4.0.2, 4.1.0, 4.2.0
 Environment: Linux kvm
Reporter: Hiroaki Kawai


There is no place to put plugin jar files for cloudstack agent program now, 
while management server program has default @PLUGINJAVADIR@ where plugin 
classes will be loaded into server at startup. We will need to load a class, 
for example when we try to use a custom libvirt.vif.driver which can be 
configured at agent.properties.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (CLOUDSTACK-1489) cloudstack agent plugin classpath is missing

2013-03-02 Thread Hiroaki Kawai (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hiroaki Kawai updated CLOUDSTACK-1489:
--

Affects Version/s: (was: 4.2.0)
   (was: 4.1.0)

 cloudstack agent plugin classpath is missing
 

 Key: CLOUDSTACK-1489
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1489
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: pre-4.0.0, 4.0.0, 4.0.1, 4.0.2
 Environment: Linux kvm
Reporter: Hiroaki Kawai

 There is no place to put plugin jar files for cloudstack agent program now, 
 while management server program has default @PLUGINJAVADIR@ where plugin 
 classes will be loaded into server at startup. We will need to load a class, 
 for example when we try to use a custom libvirt.vif.driver which can be 
 configured at agent.properties.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Created] (CLOUDSTACK-589) Juniper SRX does not depends on f5 iControl jar

2012-12-05 Thread Hiroaki Kawai (JIRA)
Hiroaki Kawai created CLOUDSTACK-589:


 Summary: Juniper SRX does not depends on f5 iControl jar
 Key: CLOUDSTACK-589
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-589
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Network Devices
Affects Versions: 4.0.0, 4.0.1, 4.1.0
Reporter: Hiroaki Kawai


In plugins / network-elements / juniper-srx / pom.xml, there's a dependency 
element which says srx requires icontrol. But the code does not use icontrol at 
all, and it is safe to remove this dependency from here.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (CLOUDSTACK-589) Juniper SRX does not depends on f5 iControl jar

2012-12-05 Thread Hiroaki Kawai (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hiroaki Kawai updated CLOUDSTACK-589:
-

Attachment: srx_pom.patch

 Juniper SRX does not depends on f5 iControl jar
 ---

 Key: CLOUDSTACK-589
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-589
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Network Devices
Affects Versions: 4.0.0, 4.0.1, 4.1.0
Reporter: Hiroaki Kawai
  Labels: maven, patch
 Attachments: srx_pom.patch


 In plugins / network-elements / juniper-srx / pom.xml, there's a dependency 
 element which says srx requires icontrol. But the code does not use icontrol 
 at all, and it is safe to remove this dependency from here.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (CLOUDSTACK-487) HttpClient in multithreaded environment

2012-11-15 Thread Hiroaki Kawai (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hiroaki Kawai updated CLOUDSTACK-487:
-

Description: 
Running cloudstack with nicira nvp plugin, I got following error. It seems that 
HttpClient in servlet must use MultiThreadedHttpConnectionManager explicitly. 
Patch will be submitted in reviewboard.

2012-11-14 18:21:51,576 WARN  [commons.httpclient.SimpleHttpConnectionManager] 
(DirectAgent-62:null) SimpleHttpConnectionManager being used incorrectly.  Be
sure that HttpMethod.releaseConnection() is always called and that only one 
thread and/or method is using this connection manager at a time.
2012-11-14 18:21:52,017 WARN  [agent.manager.DirectAgentAttache] 
(DirectAgent-62:null) Seq 5-847183891: Exception Caught while executing command
java.lang.IllegalStateException: Connection is not open
at 
org.apache.commons.httpclient.HttpConnection.assertOpen(HttpConnection.java:1277)
at 
org.apache.commons.httpclient.HttpConnection.write(HttpConnection.java:974)
at 
org.apache.commons.httpclient.HttpConnection.write(HttpConnection.java:943)
at 
org.apache.commons.httpclient.HttpConnection.print(HttpConnection.java:1033)
at 
org.apache.commons.httpclient.HttpMethodBase.writeRequestHeaders(HttpMethodBase.java:2187)
at 
org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2060)
at 
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1096)
at 
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
at 
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at 
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at 
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
at 
com.cloud.network.nicira.NiciraNvpApi.executeMethod(NiciraNvpApi.java:344)
at 
com.cloud.network.nicira.NiciraNvpApi.executeDeleteObject(NiciraNvpApi.java:294)
at 
com.cloud.network.nicira.NiciraNvpApi.deleteLogicalSwitchPort(NiciraNvpApi.java:172)
at 
com.cloud.network.resource.NiciraNvpResource.executeRequest(NiciraNvpResource.java:286)
at 
com.cloud.network.resource.NiciraNvpResource.executeRequest(NiciraNvpResource.java:192)
at 
com.cloud.network.resource.NiciraNvpResource.executeRequest(NiciraNvpResource.java:172)
at 
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)


  was:
Running cloudstack with nicira nvp plugin, I got following error. It seems that 
HttpClient in servlet must use MultiThreadedHttpConnectionManager explicitly. 
Patch will be submitted in reviewboard. https://reviews.apache.org/r/8075/

2012-11-14 18:21:51,576 WARN  [commons.httpclient.SimpleHttpConnectionManager] 
(DirectAgent-62:null) SimpleHttpConnectionManager being used incorrectly.  Be
sure that HttpMethod.releaseConnection() is always called and that only one 
thread and/or method is using this connection manager at a time.
2012-11-14 18:21:52,017 WARN  [agent.manager.DirectAgentAttache] 
(DirectAgent-62:null) Seq 5-847183891: Exception Caught while executing command
java.lang.IllegalStateException: Connection is not open
at 
org.apache.commons.httpclient.HttpConnection.assertOpen(HttpConnection.java:1277)
at 
org.apache.commons.httpclient.HttpConnection.write(HttpConnection.java:974)
at 
org.apache.commons.httpclient.HttpConnection.write(HttpConnection.java:943)
at 
org.apache.commons.httpclient.HttpConnection.print(HttpConnection.java:1033)
at 
org.apache.commons.httpclient.HttpMethodBase.writeRequestHeaders(HttpMethodBase.java:2187)
at 
org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2060)
at 
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1096)
at 
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
at 
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at 

[jira] [Updated] (CLOUDSTACK-487) HttpClient in multithreaded environment

2012-11-15 Thread Hiroaki Kawai (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hiroaki Kawai updated CLOUDSTACK-487:
-

Description: 
Running cloudstack with nicira nvp plugin, I got following error. It seems that 
HttpClient in servlet must use MultiThreadedHttpConnectionManager explicitly. 
Patch will be submitted in reviewboard. https://reviews.apache.org/r/8075/

2012-11-14 18:21:51,576 WARN  [commons.httpclient.SimpleHttpConnectionManager] 
(DirectAgent-62:null) SimpleHttpConnectionManager being used incorrectly.  Be
sure that HttpMethod.releaseConnection() is always called and that only one 
thread and/or method is using this connection manager at a time.
2012-11-14 18:21:52,017 WARN  [agent.manager.DirectAgentAttache] 
(DirectAgent-62:null) Seq 5-847183891: Exception Caught while executing command
java.lang.IllegalStateException: Connection is not open
at 
org.apache.commons.httpclient.HttpConnection.assertOpen(HttpConnection.java:1277)
at 
org.apache.commons.httpclient.HttpConnection.write(HttpConnection.java:974)
at 
org.apache.commons.httpclient.HttpConnection.write(HttpConnection.java:943)
at 
org.apache.commons.httpclient.HttpConnection.print(HttpConnection.java:1033)
at 
org.apache.commons.httpclient.HttpMethodBase.writeRequestHeaders(HttpMethodBase.java:2187)
at 
org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2060)
at 
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1096)
at 
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
at 
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at 
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at 
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
at 
com.cloud.network.nicira.NiciraNvpApi.executeMethod(NiciraNvpApi.java:344)
at 
com.cloud.network.nicira.NiciraNvpApi.executeDeleteObject(NiciraNvpApi.java:294)
at 
com.cloud.network.nicira.NiciraNvpApi.deleteLogicalSwitchPort(NiciraNvpApi.java:172)
at 
com.cloud.network.resource.NiciraNvpResource.executeRequest(NiciraNvpResource.java:286)
at 
com.cloud.network.resource.NiciraNvpResource.executeRequest(NiciraNvpResource.java:192)
at 
com.cloud.network.resource.NiciraNvpResource.executeRequest(NiciraNvpResource.java:172)
at 
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)


  was:
Running cloudstack with nicira nvp plugin, I got following error. It seems that 
HttpClient in servlet must use MultiThreadedHttpConnectionManager explicitly. 
Patch will be submitted in reviewboard.

2012-11-14 18:21:51,576 WARN  [commons.httpclient.SimpleHttpConnectionManager] 
(DirectAgent-62:null) SimpleHttpConnectionManager being used incorrectly.  Be
sure that HttpMethod.releaseConnection() is always called and that only one 
thread and/or method is using this connection manager at a time.
2012-11-14 18:21:52,017 WARN  [agent.manager.DirectAgentAttache] 
(DirectAgent-62:null) Seq 5-847183891: Exception Caught while executing command
java.lang.IllegalStateException: Connection is not open
at 
org.apache.commons.httpclient.HttpConnection.assertOpen(HttpConnection.java:1277)
at 
org.apache.commons.httpclient.HttpConnection.write(HttpConnection.java:974)
at 
org.apache.commons.httpclient.HttpConnection.write(HttpConnection.java:943)
at 
org.apache.commons.httpclient.HttpConnection.print(HttpConnection.java:1033)
at 
org.apache.commons.httpclient.HttpMethodBase.writeRequestHeaders(HttpMethodBase.java:2187)
at 
org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2060)
at 
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1096)
at 
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
at 
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at 

[jira] [Created] (CLOUDSTACK-487) HttpClient in multithreaded environment

2012-11-14 Thread Hiroaki Kawai (JIRA)
Hiroaki Kawai created CLOUDSTACK-487:


 Summary: HttpClient in multithreaded environment
 Key: CLOUDSTACK-487
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-487
 Project: CloudStack
  Issue Type: Bug
  Components: Network Devices
Affects Versions: 4.0.0, 4.0.1, 4.1.0
 Environment: Nicira nvp plugin in use.
Reporter: Hiroaki Kawai


Running cloudstack with nicira nvp plugin, I got following error. It seems that 
HttpClient in servlet must use MultiThreadedHttpConnectionManager explicitly. 
Patch will be submitted in reviewboard.

2012-11-14 18:21:51,576 WARN  [commons.httpclient.SimpleHttpConnectionManager] 
(DirectAgent-62:null) SimpleHttpConnectionManager being used incorrectly.  Be
sure that HttpMethod.releaseConnection() is always called and that only one 
thread and/or method is using this connection manager at a time.
2012-11-14 18:21:52,017 WARN  [agent.manager.DirectAgentAttache] 
(DirectAgent-62:null) Seq 5-847183891: Exception Caught while executing command
java.lang.IllegalStateException: Connection is not open
at 
org.apache.commons.httpclient.HttpConnection.assertOpen(HttpConnection.java:1277)
at 
org.apache.commons.httpclient.HttpConnection.write(HttpConnection.java:974)
at 
org.apache.commons.httpclient.HttpConnection.write(HttpConnection.java:943)
at 
org.apache.commons.httpclient.HttpConnection.print(HttpConnection.java:1033)
at 
org.apache.commons.httpclient.HttpMethodBase.writeRequestHeaders(HttpMethodBase.java:2187)
at 
org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2060)
at 
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1096)
at 
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
at 
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at 
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at 
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
at 
com.cloud.network.nicira.NiciraNvpApi.executeMethod(NiciraNvpApi.java:344)
at 
com.cloud.network.nicira.NiciraNvpApi.executeDeleteObject(NiciraNvpApi.java:294)
at 
com.cloud.network.nicira.NiciraNvpApi.deleteLogicalSwitchPort(NiciraNvpApi.java:172)
at 
com.cloud.network.resource.NiciraNvpResource.executeRequest(NiciraNvpResource.java:286)
at 
com.cloud.network.resource.NiciraNvpResource.executeRequest(NiciraNvpResource.java:192)
at 
com.cloud.network.resource.NiciraNvpResource.executeRequest(NiciraNvpResource.java:172)
at 
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (CLOUDSTACK-487) HttpClient in multithreaded environment

2012-11-14 Thread Hiroaki Kawai (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hiroaki Kawai updated CLOUDSTACK-487:
-

Description: 
Running cloudstack with nicira nvp plugin, I got following error. It seems that 
HttpClient in servlet must use MultiThreadedHttpConnectionManager explicitly. 
Patch will be submitted in reviewboard. https://reviews.apache.org/r/8075/

2012-11-14 18:21:51,576 WARN  [commons.httpclient.SimpleHttpConnectionManager] 
(DirectAgent-62:null) SimpleHttpConnectionManager being used incorrectly.  Be
sure that HttpMethod.releaseConnection() is always called and that only one 
thread and/or method is using this connection manager at a time.
2012-11-14 18:21:52,017 WARN  [agent.manager.DirectAgentAttache] 
(DirectAgent-62:null) Seq 5-847183891: Exception Caught while executing command
java.lang.IllegalStateException: Connection is not open
at 
org.apache.commons.httpclient.HttpConnection.assertOpen(HttpConnection.java:1277)
at 
org.apache.commons.httpclient.HttpConnection.write(HttpConnection.java:974)
at 
org.apache.commons.httpclient.HttpConnection.write(HttpConnection.java:943)
at 
org.apache.commons.httpclient.HttpConnection.print(HttpConnection.java:1033)
at 
org.apache.commons.httpclient.HttpMethodBase.writeRequestHeaders(HttpMethodBase.java:2187)
at 
org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2060)
at 
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1096)
at 
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
at 
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at 
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at 
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
at 
com.cloud.network.nicira.NiciraNvpApi.executeMethod(NiciraNvpApi.java:344)
at 
com.cloud.network.nicira.NiciraNvpApi.executeDeleteObject(NiciraNvpApi.java:294)
at 
com.cloud.network.nicira.NiciraNvpApi.deleteLogicalSwitchPort(NiciraNvpApi.java:172)
at 
com.cloud.network.resource.NiciraNvpResource.executeRequest(NiciraNvpResource.java:286)
at 
com.cloud.network.resource.NiciraNvpResource.executeRequest(NiciraNvpResource.java:192)
at 
com.cloud.network.resource.NiciraNvpResource.executeRequest(NiciraNvpResource.java:172)
at 
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)


  was:
Running cloudstack with nicira nvp plugin, I got following error. It seems that 
HttpClient in servlet must use MultiThreadedHttpConnectionManager explicitly. 
Patch will be submitted in reviewboard.

2012-11-14 18:21:51,576 WARN  [commons.httpclient.SimpleHttpConnectionManager] 
(DirectAgent-62:null) SimpleHttpConnectionManager being used incorrectly.  Be
sure that HttpMethod.releaseConnection() is always called and that only one 
thread and/or method is using this connection manager at a time.
2012-11-14 18:21:52,017 WARN  [agent.manager.DirectAgentAttache] 
(DirectAgent-62:null) Seq 5-847183891: Exception Caught while executing command
java.lang.IllegalStateException: Connection is not open
at 
org.apache.commons.httpclient.HttpConnection.assertOpen(HttpConnection.java:1277)
at 
org.apache.commons.httpclient.HttpConnection.write(HttpConnection.java:974)
at 
org.apache.commons.httpclient.HttpConnection.write(HttpConnection.java:943)
at 
org.apache.commons.httpclient.HttpConnection.print(HttpConnection.java:1033)
at 
org.apache.commons.httpclient.HttpMethodBase.writeRequestHeaders(HttpMethodBase.java:2187)
at 
org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2060)
at 
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1096)
at 
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
at 
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at 

[jira] [Updated] (CLOUDSTACK-423) During VM migration on KVM, VifDriver.unplug is not called.

2012-10-29 Thread Hiroaki Kawai (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hiroaki Kawai updated CLOUDSTACK-423:
-

Summary: During VM migration on KVM, VifDriver.unplug is not called.  (was: 
During VM migration with KVM, VifDriver.unplug is not called.)

 During VM migration on KVM, VifDriver.unplug is not called.
 ---

 Key: CLOUDSTACK-423
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-423
 Project: CloudStack
  Issue Type: Bug
  Components: KVM
Affects Versions: 4.0.0, 4.1.0
 Environment: Reproducable on CentOS 6.3
Reporter: Hiroaki Kawai
  Labels: patch

 VifDriver.unplug must be called in MigrateCommand which hooks VM migration in 
 source host, because plug will be called in PrepareForMigration in 
 destination host. But current LibvirtComputingResources lacks that operation.
 Patch will be submitted in reviewboard.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Created] (CLOUDSTACK-423) During VM migration with KVM, VifDriver.unplug is not called.

2012-10-29 Thread Hiroaki Kawai (JIRA)
Hiroaki Kawai created CLOUDSTACK-423:


 Summary: During VM migration with KVM, VifDriver.unplug is not 
called.
 Key: CLOUDSTACK-423
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-423
 Project: CloudStack
  Issue Type: Bug
  Components: KVM
Affects Versions: 4.0.0, 4.1.0
 Environment: Reproducable on CentOS 6.3
Reporter: Hiroaki Kawai


VifDriver.unplug must be called in MigrateCommand which hooks VM migration in 
source host, because plug will be called in PrepareForMigration in destination 
host. But current LibvirtComputingResources lacks that operation.

Patch will be submitted in reviewboard.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (CLOUDSTACK-423) During VM migration on KVM, VifDriver.unplug is not called.

2012-10-29 Thread Hiroaki Kawai (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hiroaki Kawai updated CLOUDSTACK-423:
-

Description: 
VifDriver.unplug must be called in MigrateCommand which hooks VM migration in 
source host, because plug will be called in PrepareForMigration in destination 
host. But current LibvirtComputingResources lacks that operation.

Patch will be submitted in reviewboard : https://reviews.apache.org/r/7761/

  was:
VifDriver.unplug must be called in MigrateCommand which hooks VM migration in 
source host, because plug will be called in PrepareForMigration in destination 
host. But current LibvirtComputingResources lacks that operation.

Patch will be submitted in reviewboard.


 During VM migration on KVM, VifDriver.unplug is not called.
 ---

 Key: CLOUDSTACK-423
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-423
 Project: CloudStack
  Issue Type: Bug
  Components: KVM
Affects Versions: 4.0.0, 4.1.0
 Environment: Reproducable on CentOS 6.3
Reporter: Hiroaki Kawai
  Labels: patch

 VifDriver.unplug must be called in MigrateCommand which hooks VM migration in 
 source host, because plug will be called in PrepareForMigration in 
 destination host. But current LibvirtComputingResources lacks that operation.
 Patch will be submitted in reviewboard : https://reviews.apache.org/r/7761/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CLOUDSTACK-120) Failed to deploy Router with KVM hyperviosor [ Can't find the mapping of guest os: Debian GNU/Linux 5.0 (32-bit)]

2012-09-18 Thread Hiroaki Kawai (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13457707#comment-13457707
 ] 

Hiroaki Kawai commented on CLOUDSTACK-120:
--

This is not fixed in 4.0 branch.

 Failed to deploy Router with KVM hyperviosor [  Can't find the mapping of 
 guest os: Debian GNU/Linux 5.0 (32-bit)]
 --

 Key: CLOUDSTACK-120
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-120
 Project: CloudStack
  Issue Type: Bug
  Components: KVM, Management Server
Affects Versions: pre-4.0.0
Reporter: Sailaja Mada
Assignee: edison su
Priority: Blocker
 Fix For: pre-4.0.0

 Attachments: agent.log, api-server.log, management-server.log


 Steps:
 1. Setup Management server 
 2. Setup KVM host with Cloudstack Agent installed 
 3. Setup Basic Zone with SG service offering 
 4. After having all the system VM's running , tried to deploy the first 
 instance 
 Observation :
 First Instance deployment failed as the router failed start .
 MS Error log :
 2012-09-17 15:10:27,255 DEBUG 
 [network.router.VirtualNetworkApplianceManagerImpl] 
 (RouterStatusMonitor-1:null) Found 0 routers.
 2012-09-17 15:10:31,882 DEBUG [agent.transport.Request] 
 (AgentManager-Handler-14:null) Seq 3-1151271005: Processing:  { Ans: , 
 MgmtId: 55487956346259, via: 3, Ver: v1, Flags: 110, 
 [{StartAnswer:{vm:{id:4,name:r-4-VM,type:DomainRouter,cpus:1,speed:500,minRam:134217728,maxRam:134217728,arch:x86_64,os:Debian
  GNU/Linux 5.0 (32-bit),bootArgs: template=domP name=r-4-VM 
 eth0ip=10.102.125.188 eth0mask=255.255.255.0 gateway=10.102.125.1 
 domain=cs1cloud.internal dhcprange=10.102.125.1 eth1ip=169.254.1.202 
 eth1mask=255.255.0.0 type=dhcpsrvr disable_rp_filter=true 
 dns1=10.103.128.15,rebootOnCrash:false,enableHA:true,limitCpuUse:false,vncPassword:fa3d755b18ba1297,params:{},uuid:6e5680fa-14b1-447d-9024-1bed9cb59268,disks:[{id:4,name:/cloudstack/sailaja/pri1/,mountPoint:0614e5e3-77ce-46da-b356-4e528752aa9d,path:0614e5e3-77ce-46da-b356-4e528752aa9d,size:725811200,type:ROOT,storagePoolType:NetworkFilesystem,storagePoolUuid:e95f2598-5038-3ceb-a326-5309b3295012,deviceId:0}],nics:[{deviceId:0,networkRateMbps:200,defaultNic:true,uuid:a6b006af-039e-4a00-bdeb-97ac623fb56e,ip:10.102.125.188,netmask:255.255.255.0,gateway:10.102.125.1,mac:06:bb:c4:00:00:09,dns1:10.103.128.15,broadcastType:Native,type:Guest,broadcastUri:vlan://untagged,isolationUri:ec2://untagged,isSecurityGroupEnabled:false},{deviceId:1,networkRateMbps:-1,defaultNic:false,uuid:e694c359-0609-42b6-872b-f2191ee20241,ip:169.254.1.202,netmask:255.255.0.0,gateway:169.254.0.1,mac:0e:00:a9:fe:01:ca,broadcastType:LinkLocal,type:Control,isSecurityGroupEnabled:false}]},result:true,wait:0}},{check.CheckSshAnswer:{result:true,wait:0}},{GetDomRVersionAnswer:{result:false,details:GetDomRVersionCmd
  failed,wait:0}},{Answer:{result:false,details:Stopped by previous 
 failure,wait:0}}] }
 2012-09-17 15:10:31,882 DEBUG [agent.transport.Request] 
 (Job-Executor-8:job-8) Seq 3-1151271005: Received:  { Ans: , MgmtId: 
 55487956346259, via: 3, Ver: v1, Flags: 110, { StartAnswer, CheckSshAnswer, 
 GetDomRVersionAnswer, Answer } }
 2012-09-17 15:10:31,884 DEBUG [agent.manager.AgentAttache] 
 (AgentManager-Handler-14:null) Seq 3-1151271005: No more commands found
 2012-09-17 15:10:31,888 WARN  
 [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-8:job-8) 
 Unable to get the template/scripts version of router r-4-VM due to: 
 GetDomRVersionCmd failed
 2012-09-17 15:10:31,888 INFO  [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-8:job-8) The guru did not like the answers so stopping 
 VM[DomainRouter|r-4-VM]
 2012-09-17 15:10:31,890 DEBUG [agent.transport.Request] 
 (Job-Executor-8:job-8) Seq 3-1151271010: Sending  { Cmd , MgmtId: 
 55487956346259, via: 3, Ver: v1, Flags: 100111, 
 [{StopCommand:{isProxy:false,vmName:r-4-VM,wait:0}}] }
 Cloud Agent Error log :
 2012-09-17 15:44:06,178 DEBUG [kvm.resource.KVMGuestOsMapper] 
 (agentRequest-Handler-5:null) Can't find the mapping of guest os: Debian 
 GNU/Linux 5.0 (32-bit)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CLOUDSTACK-78) Cloudstack Agent installation failed with jsvc package dependancy error

2012-09-12 Thread Hiroaki Kawai (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13453847#comment-13453847
 ] 

Hiroaki Kawai commented on CLOUDSTACK-78:
-

Please try typing:
yum install jsvc
and/or
yum install jakarta-commons-daemon-jsvc

 Cloudstack Agent installation failed with jsvc package dependancy error 
 

 Key: CLOUDSTACK-78
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-78
 Project: CloudStack
  Issue Type: Bug
  Components: Install and Setup
Affects Versions: pre-4.0.0
Reporter: Sailaja Mada
Assignee: David Nalley
Priority: Critical
 Fix For: pre-4.0.0


 Steps:
 1. Tried installing Agent with KVM host .  
 Observation : Cloudstack Agent installation failed with jsvc package 
 dependancy error 
 Details : 
 M) Install the Management Server
 A) Install the Agent
 B) Install BareMetal Agent
 S) Install the Usage Monitor
 D) Install the database server
 Q) Quit
  A
 Installing the Agent...
 Loaded plugins: product-id, security, subscription-manager
 Updating certificate-based repositories.
 cloud-temp
   
   | 2.6 kB 00:00 ...
 cloud-temp/primary_db 
   
   |  10 kB 00:00 ...
 rhel  
   
   | 4.0 kB 00:00 ...
 Setting up Install Process
 No package cloud-premium available.
 Resolving Dependencies
 -- Running transaction check
 --- Package cloud-agent.x86_64 0:4.0.59-0.59.el6.4.0 will be installed
 -- Processing Dependency: cloud-utils = 4.0.59 for package: 
 cloud-agent-4.0.59-0.59.el6.4.0.x86_64
 -- Processing Dependency: cloud-python = 4.0.59 for package: 
 cloud-agent-4.0.59-0.59.el6.4.0.x86_64
 -- Processing Dependency: cloud-deps = 4.0.59 for package: 
 cloud-agent-4.0.59-0.59.el6.4.0.x86_64
 -- Processing Dependency: cloud-core = 4.0.59 for package: 
 cloud-agent-4.0.59-0.59.el6.4.0.x86_64
 -- Processing Dependency: cloud-agent-scripts = 4.0.59 for package: 
 cloud-agent-4.0.59-0.59.el6.4.0.x86_64
 -- Processing Dependency: cloud-agent-libs = 4.0.59 for package: 
 cloud-agent-4.0.59-0.59.el6.4.0.x86_64
 -- Processing Dependency: jsvc for package: 
 cloud-agent-4.0.59-0.59.el6.4.0.x86_64
 -- Processing Dependency: jna for package: 
 cloud-agent-4.0.59-0.59.el6.4.0.x86_64
 -- Running transaction check
 --- Package cloud-agent.x86_64 0:4.0.59-0.59.el6.4.0 will be installed
 -- Processing Dependency: jsvc for package: 
 cloud-agent-4.0.59-0.59.el6.4.0.x86_64
 --- Package cloud-agent-libs.x86_64 0:4.0.59-0.59.el6.4.0 will be installed
 --- Package cloud-agent-scripts.x86_64 0:4.0.59-0.59.el6.4.0 will be 
 installed
 --- Package cloud-core.x86_64 0:4.0.59-0.59.el6.4.0 will be installed
 --- Package cloud-deps.x86_64 0:4.0.59-0.59.el6.4.0 will be installed
 --- Package cloud-python.x86_64 0:4.0.59-0.59.el6.4.0 will be installed
 --- Package cloud-utils.x86_64 0:4.0.59-0.59.el6.4.0 will be installed
 --- Package jna.x86_64 0:3.2.4-2.el6 will be installed
 -- Finished Dependency Resolution
 Error: Package: cloud-agent-4.0.59-0.59.el6.4.0.x86_64 (cloud-temp)
Requires: jsvc
  You could try using --skip-broken to work around the problem
  You could try running: rpm -Va --nofiles --nodigest
 Done
 Expected Results :  Installation should go thru with out any issues. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CLOUDSTACK-78) Cloudstack Agent installation failed with jsvc package dependancy error

2012-09-11 Thread Hiroaki Kawai (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13453056#comment-13453056
 ] 

Hiroaki Kawai commented on CLOUDSTACK-78:
-

What is the distribution you were using when you got this error. Red hat, 
fedora, centos 5 or 6, Ubuntu, or something other?

 Cloudstack Agent installation failed with jsvc package dependancy error 
 

 Key: CLOUDSTACK-78
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-78
 Project: CloudStack
  Issue Type: Bug
  Components: Install and Setup
Affects Versions: pre-4.0.0
Reporter: Sailaja Mada
Assignee: edison su
Priority: Critical

 Steps:
 1. Tried installing Agent with KVM host .  
 Observation : Cloudstack Agent installation failed with jsvc package 
 dependancy error 
 Details : 
 M) Install the Management Server
 A) Install the Agent
 B) Install BareMetal Agent
 S) Install the Usage Monitor
 D) Install the database server
 Q) Quit
  A
 Installing the Agent...
 Loaded plugins: product-id, security, subscription-manager
 Updating certificate-based repositories.
 cloud-temp
   
   | 2.6 kB 00:00 ...
 cloud-temp/primary_db 
   
   |  10 kB 00:00 ...
 rhel  
   
   | 4.0 kB 00:00 ...
 Setting up Install Process
 No package cloud-premium available.
 Resolving Dependencies
 -- Running transaction check
 --- Package cloud-agent.x86_64 0:4.0.59-0.59.el6.4.0 will be installed
 -- Processing Dependency: cloud-utils = 4.0.59 for package: 
 cloud-agent-4.0.59-0.59.el6.4.0.x86_64
 -- Processing Dependency: cloud-python = 4.0.59 for package: 
 cloud-agent-4.0.59-0.59.el6.4.0.x86_64
 -- Processing Dependency: cloud-deps = 4.0.59 for package: 
 cloud-agent-4.0.59-0.59.el6.4.0.x86_64
 -- Processing Dependency: cloud-core = 4.0.59 for package: 
 cloud-agent-4.0.59-0.59.el6.4.0.x86_64
 -- Processing Dependency: cloud-agent-scripts = 4.0.59 for package: 
 cloud-agent-4.0.59-0.59.el6.4.0.x86_64
 -- Processing Dependency: cloud-agent-libs = 4.0.59 for package: 
 cloud-agent-4.0.59-0.59.el6.4.0.x86_64
 -- Processing Dependency: jsvc for package: 
 cloud-agent-4.0.59-0.59.el6.4.0.x86_64
 -- Processing Dependency: jna for package: 
 cloud-agent-4.0.59-0.59.el6.4.0.x86_64
 -- Running transaction check
 --- Package cloud-agent.x86_64 0:4.0.59-0.59.el6.4.0 will be installed
 -- Processing Dependency: jsvc for package: 
 cloud-agent-4.0.59-0.59.el6.4.0.x86_64
 --- Package cloud-agent-libs.x86_64 0:4.0.59-0.59.el6.4.0 will be installed
 --- Package cloud-agent-scripts.x86_64 0:4.0.59-0.59.el6.4.0 will be 
 installed
 --- Package cloud-core.x86_64 0:4.0.59-0.59.el6.4.0 will be installed
 --- Package cloud-deps.x86_64 0:4.0.59-0.59.el6.4.0 will be installed
 --- Package cloud-python.x86_64 0:4.0.59-0.59.el6.4.0 will be installed
 --- Package cloud-utils.x86_64 0:4.0.59-0.59.el6.4.0 will be installed
 --- Package jna.x86_64 0:3.2.4-2.el6 will be installed
 -- Finished Dependency Resolution
 Error: Package: cloud-agent-4.0.59-0.59.el6.4.0.x86_64 (cloud-temp)
Requires: jsvc
  You could try using --skip-broken to work around the problem
  You could try running: rpm -Va --nofiles --nodigest
 Done
 Expected Results :  Installation should go thru with out any issues. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira