Posted by: peteinman | April 29, 2010

Publishing Error Oracle Service Bus – Workshop IDE

I’ve been working on a SOA project for a few days, and gradually adding functionality. Suddenly Workshop failed to publish with the exception below.

org.eclipse.core.runtime.CoreException: Error publishing new container for: Dev
    at com.bea.alsb.server.publish.ALSBPublishOperation.publishNewContainer(ALSBPublishOperation.java:302)
    at com.bea.alsb.server.publish.ALSBPublishOperation.execute(ALSBPublishOperation.java:150)
    at com.bea.workshop.wls.core.server.internal.WeblogicServerBehaviour.performTasks(WeblogicServerBehaviour.java:1189)
    at com.bea.workshop.wls.core.server.internal.WeblogicServerBehaviour.publishToServer(WeblogicServerBehaviour.java:744)
    at com.bea.workshop.wls.core.server.internal.WeblogicServerBehaviour.publishOnce(WeblogicServerBehaviour.java:607)
    at com.bea.workshop.wls.core.server.internal.WeblogicServerBehaviour.publish(WeblogicServerBehaviour.java:503)
    at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:887)
    at org.eclipse.wst.server.core.internal.Server.publish(Server.java:874)
    at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:72)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
org.eclipse.core.runtime.CoreException[4000]: com.bea.alsb.core.repositories.RepositoryException: Socket closed
    at com.bea.alsb.core.internal.repositories.jar.AbstractConfigRepository.init(AbstractConfigRepository.java:122)
    at com.bea.alsb.core.internal.repositories.jar.ServerConfigRepository.<init>(ServerConfigRepository.java:102)
    at com.bea.alsb.core.internal.repositories.RepositoryService.create(RepositoryService.java:155)
    at com.bea.alsb.server.publish.ALSBPublishOperation.publishNewContainer(ALSBPublishOperation.java:295)

The key part of this exception is highlighted in red.

I did raise a support case, but in the meantime, decompiled some of the classes in the stack trace to get a clue as to what was going on.

All it was doing was creating a publish session, uploading the file and publishing, so why the Socket Closed exception.

Something made me think of the maximum message size for WebLogic which by default is 10,000,000 bytes or 10MB. My project had grown to 12MB due to the addition of a couple of jar files.

I increased the maximum message size and my project now publishes.

Hope this is of help to someone.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Categories

%d bloggers like this: