[JIRA] Created: (HUDSON-6615) NotSerializableException using Phing plugin with slaves

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] Created: (HUDSON-6615) NotSerializableException using Phing plugin with slaves

Hudson issues mailing list
NotSerializableException using Phing plugin with slaves
-------------------------------------------------------

                 Key: HUDSON-6615
                 URL: http://issues.hudson-ci.org/browse/HUDSON-6615
             Project: Hudson
          Issue Type: Bug
          Components: phing
            Reporter: mdillon
            Assignee: sogabe
         Attachments: PhingInstallation.java.diff

Some folks here at Yahoo! have used the Phing plugin in the past and ran into trouble trying to use it in a master/slave configuration. Here is the exception they were getting (this stack trace is from over a year ago):

java.io.IOException: Unable to serialize hudson.plugins.phing.PhingInstallation$1@1cb3087
        at hudson.remoting.UserRequest.serialize(UserRequest.java:126)
        at hudson.remoting.UserRequest.<init>(UserRequest.java:60)
        at hudson.remoting.Channel.call(Channel.java:475)
        at hudson.plugins.phing.PhingInstallation.getExecutable(PhingInstallation.java:72)
        at hudson.plugins.phing.PhingBuilder.perform(PhingBuilder.java:120)
        at hudson.model.Build$RunnerImpl.build(Build.java:193)
        at hudson.model.Build$RunnerImpl.doRun(Build.java:144)
        at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:272)
        at hudson.model.Run.run(Run.java:865)
        at hudson.model.Build.run(Build.java:112)
        at hudson.model.ResourceController.execute(ResourceController.java:93)
        at hudson.model.Executor.run(Executor.java:113)
Caused by: java.io.NotSerializableException: hudson.Launcher$RemoteLauncher
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156)
        at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
        at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
        at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
        at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
        at hudson.remoting.UserRequest.serialize(UserRequest.java:123)
        ... 11 more

I've attached a patch that fixes this by determining the executable name on the master before starting the remote call and removing the launcher from the callable state.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Updated: (HUDSON-6615) NotSerializableException using Phing plugin with slaves

Hudson issues mailing list

     [ http://issues.hudson-ci.org/browse/HUDSON-6615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

mdillon updated HUDSON-6615:
----------------------------

    Description:
Some folks here at Yahoo! have used the Phing plugin in the past and ran into trouble trying to use it in a master/slave configuration. Here is the exception they were getting (this stack trace is from over a year ago):

{quote}
java.io.IOException: Unable to serialize hudson.plugins.phing.PhingInstallation$1@1cb3087
        at hudson.remoting.UserRequest.serialize(UserRequest.java:126)
        at hudson.remoting.UserRequest.<init>(UserRequest.java:60)
        at hudson.remoting.Channel.call(Channel.java:475)
        at hudson.plugins.phing.PhingInstallation.getExecutable(PhingInstallation.java:72)
        at hudson.plugins.phing.PhingBuilder.perform(PhingBuilder.java:120)
        at hudson.model.Build$RunnerImpl.build(Build.java:193)
        at hudson.model.Build$RunnerImpl.doRun(Build.java:144)
        at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:272)
        at hudson.model.Run.run(Run.java:865)
        at hudson.model.Build.run(Build.java:112)
        at hudson.model.ResourceController.execute(ResourceController.java:93)
        at hudson.model.Executor.run(Executor.java:113)
Caused by: java.io.NotSerializableException: hudson.Launcher$RemoteLauncher
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156)
        at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
        at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
        at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
        at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
        at hudson.remoting.UserRequest.serialize(UserRequest.java:123)
        ... 11 more
{quote}

I've attached a patch that fixes this by determining the executable name on the master before starting the remote call and removing the launcher from the callable state.

  was:
Some folks here at Yahoo! have used the Phing plugin in the past and ran into trouble trying to use it in a master/slave configuration. Here is the exception they were getting (this stack trace is from over a year ago):

java.io.IOException: Unable to serialize hudson.plugins.phing.PhingInstallation$1@1cb3087
        at hudson.remoting.UserRequest.serialize(UserRequest.java:126)
        at hudson.remoting.UserRequest.<init>(UserRequest.java:60)
        at hudson.remoting.Channel.call(Channel.java:475)
        at hudson.plugins.phing.PhingInstallation.getExecutable(PhingInstallation.java:72)
        at hudson.plugins.phing.PhingBuilder.perform(PhingBuilder.java:120)
        at hudson.model.Build$RunnerImpl.build(Build.java:193)
        at hudson.model.Build$RunnerImpl.doRun(Build.java:144)
        at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:272)
        at hudson.model.Run.run(Run.java:865)
        at hudson.model.Build.run(Build.java:112)
        at hudson.model.ResourceController.execute(ResourceController.java:93)
        at hudson.model.Executor.run(Executor.java:113)
Caused by: java.io.NotSerializableException: hudson.Launcher$RemoteLauncher
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156)
        at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
        at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
        at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
        at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
        at hudson.remoting.UserRequest.serialize(UserRequest.java:123)
        ... 11 more

I've attached a patch that fixes this by determining the executable name on the master before starting the remote call and removing the launcher from the callable state.


> NotSerializableException using Phing plugin with slaves
> -------------------------------------------------------
>
>                 Key: HUDSON-6615
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6615
>             Project: Hudson
>          Issue Type: Bug
>          Components: phing
>            Reporter: mdillon
>            Assignee: sogabe
>         Attachments: PhingInstallation.java.diff
>
>
> Some folks here at Yahoo! have used the Phing plugin in the past and ran into trouble trying to use it in a master/slave configuration. Here is the exception they were getting (this stack trace is from over a year ago):
> {quote}
> java.io.IOException: Unable to serialize hudson.plugins.phing.PhingInstallation$1@1cb3087
>         at hudson.remoting.UserRequest.serialize(UserRequest.java:126)
>         at hudson.remoting.UserRequest.<init>(UserRequest.java:60)
>         at hudson.remoting.Channel.call(Channel.java:475)
>         at hudson.plugins.phing.PhingInstallation.getExecutable(PhingInstallation.java:72)
>         at hudson.plugins.phing.PhingBuilder.perform(PhingBuilder.java:120)
>         at hudson.model.Build$RunnerImpl.build(Build.java:193)
>         at hudson.model.Build$RunnerImpl.doRun(Build.java:144)
>         at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:272)
>         at hudson.model.Run.run(Run.java:865)
>         at hudson.model.Build.run(Build.java:112)
>         at hudson.model.ResourceController.execute(ResourceController.java:93)
>         at hudson.model.Executor.run(Executor.java:113)
> Caused by: java.io.NotSerializableException: hudson.Launcher$RemoteLauncher
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
>         at hudson.remoting.UserRequest.serialize(UserRequest.java:123)
>         ... 11 more
> {quote}
> I've attached a patch that fixes this by determining the executable name on the master before starting the remote call and removing the launcher from the callable state.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Resolved: (HUDSON-6615) NotSerializableException using Phing plugin with slaves

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

     [ http://issues.hudson-ci.org/browse/HUDSON-6615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

sogabe resolved HUDSON-6615.
----------------------------

    Resolution: Fixed

Thanks for patch.
Phing Plugin 0.5 has released.

> NotSerializableException using Phing plugin with slaves
> -------------------------------------------------------
>
>                 Key: HUDSON-6615
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6615
>             Project: Hudson
>          Issue Type: Bug
>          Components: phing
>            Reporter: mdillon
>            Assignee: sogabe
>         Attachments: PhingInstallation.java.diff
>
>
> Some folks here at Yahoo! have used the Phing plugin in the past and ran into trouble trying to use it in a master/slave configuration. Here is the exception they were getting (this stack trace is from over a year ago):
> {quote}
> java.io.IOException: Unable to serialize hudson.plugins.phing.PhingInstallation$1@1cb3087
>         at hudson.remoting.UserRequest.serialize(UserRequest.java:126)
>         at hudson.remoting.UserRequest.<init>(UserRequest.java:60)
>         at hudson.remoting.Channel.call(Channel.java:475)
>         at hudson.plugins.phing.PhingInstallation.getExecutable(PhingInstallation.java:72)
>         at hudson.plugins.phing.PhingBuilder.perform(PhingBuilder.java:120)
>         at hudson.model.Build$RunnerImpl.build(Build.java:193)
>         at hudson.model.Build$RunnerImpl.doRun(Build.java:144)
>         at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:272)
>         at hudson.model.Run.run(Run.java:865)
>         at hudson.model.Build.run(Build.java:112)
>         at hudson.model.ResourceController.execute(ResourceController.java:93)
>         at hudson.model.Executor.run(Executor.java:113)
> Caused by: java.io.NotSerializableException: hudson.Launcher$RemoteLauncher
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
>         at hudson.remoting.UserRequest.serialize(UserRequest.java:123)
>         ... 11 more
> {quote}
> I've attached a patch that fixes this by determining the executable name on the master before starting the remote call and removing the launcher from the callable state.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]