Re: Fetch Specifications defined in the .eomodel
Re: Fetch Specifications defined in the .eomodel
- Subject: Re: Fetch Specifications defined in the .eomodel
- From: Florijan Stamenkovic <email@hidden>
- Date: Fri, 15 Feb 2008 14:12:14 -0400
By the looks of it the connection between the client and the server
got broken. As to why that has happened or where, you gotta figure
that out.
Skimmed through the code, looks OK.
I got a Broken pipe exception some time in the past, but I totally
forgot when, where, or what I did to fix it...
On Feb 15, 2008, at 13:02, David Avendasora wrote:
Nuts, that's what I had figured out, but I'm still having problems.
But I'm not sure what's causing it. I'd hoped that I missed
something on the clientSideRequest portion of the process.
The call to the server is failing
Exception in thread "AWT-EventQueue-0"
com.webobjects.foundation.NSForwardException for
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:
92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at java.io.ByteArrayOutputStream.writeTo
(ByteArrayOutputStream.java:112)
at
com.webobjects.eodistribution.client.EOHTTPChannel._responseToMessage(
EOHTTPChannel.java:519)
at
com.webobjects.eodistribution.client.EOHTTPChannel.responseToMessage
(EOHTTPChannel.java:603)
at
com.webobjects.eodistribution.client.EODistributedObjectStore.invokeSt
atelessRemoteMethodWithKeyPath(EODistributedObjectStore.java:1099)
at
com.bestmaid.bakeryManagement.client.utility.RemoteMethodInvoker.invok
eStatelessRemoteMethodWithKeyPath(RemoteMethodInvoker.java:83)
at
com.bestmaid.bakeryManagement.client.utility.RemoteMethodInvoker.invok
eStatelessOnSession(RemoteMethodInvoker.java:99)
at
com.bestmaid.bakeryManagement.client.utility.BMRMI.getFetchSpecificati
on(BMRMI.java:49)
at
com.bestmaid.bakeryManagement.client.nutrition._NutritionElementType.f
etchUSDACalories(_NutritionElementType.java:68)
_NutritionElementType.java
I put the BMRMI.setDistributedObjectStore((EODistributedObjectStore)
EOEditingContext.defaultParentObjectStore()); call in my
BMGenericRecord that all my client-side classes extend.
It seems like it's making the trip to the server, and making it as
far as executing getFetchSpecification, but then fails and prints
the exception above.
What makes you say that? Seems to me that the stack trace stops on
the client side, just at the moment it needs to send a request to the
server. Or am I missing something?
Flor
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden