You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@uima.apache.org by Prokopis Prokopidis <pr...@gmail.com> on 2009/12/15 21:52:06 UTC
Error on getMeta call to remote service
Hi,
I have the following timeout problem. I have deployed the
RoomNumberAnnotator Analysis Engine example from the UIMA AS 2.2.2
distribution on a linux machine with java 1.6, and I am getting getMeta
errors while trying to call the service from another machine with the same
configuration, with firewalls disabled on both machines. I am attaching the
messages I get on the client side and in the server's activemq log. If it's
any help, when calling the service from the machine on which it has been
deployed, or when reversing the service-client roles between the two
machines, everything works as in the README file.
Thanks in advance for any hints,
Prokopis
---------------------------------------------------------
$ runRemoteAsyncAE.sh tcp://sikinos.mydomain.org:61616
RoomNumberAnnotatorQueue -c
/usr/local/apache-uima-as/examples/descriptors/collection_reader/FileSystemCollectionReader.xml
Got MBeanServer Started
Error on getMeta call to remote service:
org.apache.uima.aae.error.UimaASMetaRequestTimeout
at
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl.notifyOnTimout(BaseUIMAAsynchronousEngineCommon_impl.java:1206)
at
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl$ClientRequest$1.run(BaseUIMAAsynchronousEngineCommon_impl.java:1529)
at java.util.TimerThread.mainLoop(Timer.java:534)
at java.util.TimerThread.run(Timer.java:484)
Terminating Client...
Exception in thread "main"
org.apache.uima.resource.ResourceInitializationException
at
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl.initialize(BaseUIMAAsynchronousEngine_impl.java:439)
at
org.apache.uima.examples.as.RunRemoteAsyncAE.run(RunRemoteAsyncAE.java:241)
at
org.apache.uima.examples.as.RunRemoteAsyncAE.main(RunRemoteAsyncAE.java:297)
Caused by: org.apache.uima.aae.error.UimaASMetaRequestTimeout
... 3 more
------------------------------------------------------
[localhost:61616] DEBUG WireFormatNegotiator - Sending:
WireFormatInfo { version=2, properties={CacheSize=1024, CacheEnabled=true,
SizePrefixDisabled=false, TcpNoDelayEnabled=true,
MaxInactivityDuration=30000, TightEncodingEnabled=true,
StackTraceEnabled=true}, magic=[A,c,t,i,v,e,M,Q]}
[10.1.1.210:32918] DEBUG WireFormatNegotiator - Received
WireFormat: WireFormatInfo { version=2, properties={CacheSize=1024,
CacheEnabled=true, SizePrefixDisabled=false, TcpNoDelayEnabled=true,
MaxInactivityDuration=30000, TightEncodingEnabled=true,
StackTraceEnabled=true}, magic=[A,c,t,i,v,e,M,Q]}
[10.1.1.210:32918] DEBUG WireFormatNegotiator - tcp:///
10.1.1.210:32918 before negotiation: OpenWireFormat{version=2,
cacheEnabled=false, stackTraceEnabled=false, tightEncodingEnabled=false,
sizePrefixDisabled=false}
[10.1.1.210:32918] DEBUG WireFormatNegotiator - tcp:///
10.1.1.210:32918 after negotiation: OpenWireFormat{version=2,
cacheEnabled=true, stackTraceEnabled=true, tightEncodingEnabled=true,
sizePrefixDisabled=false}
[10.1.1.210:32918] DEBUG TransportConnection - Setting up new
connection:
org.apache.activemq.broker.jmx.ManagedTransportConnection@16b6c55
[10.1.1.210:32918] DEBUG AbstractRegion - Adding consumer:
ID:anafi.mydomain.org-41122-1260898846989-1:0:-1:1
[10.1.1.210:32918] DEBUG AbstractRegion - Adding
destination: temp-queue://ID:anafi.mydomain.org-41122-1260898846989-1:0:1
[10.1.1.210:32918] DEBUG AbstractRegion - Adding consumer:
ID:anafi.mydomain.org-41122-1260898846989-1:0:2:1
[10.1.1.210:32918] DEBUG AbstractRegion - Adding
destination: topic://ActiveMQ.Advisory.Consumer.Queue.ID:
anafi.mydomain.org-41122-1260898846989-1:0:1
[10.1.1.210:32918] DEBUG Transport - Transport failed:
java.io.EOFException
java.io.EOFException
at java.io.DataInputStream.readInt(DataInputStream.java:392)
at
org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:267)
at
org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:156)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:136)
at java.lang.Thread.run(Thread.java:636)
[10.1.1.210:32918] DEBUG TransportConnection - Stopping
connection: /10.1.1.210:32918
[10.1.1.210:32918] DEBUG TransportConnection - Stopped
connection: /10.1.1.210:32918
[10.1.1.210:32918] DEBUG TransportConnection - Cleaning up
connection resources.
[10.1.1.210:32918] DEBUG AbstractRegion - Removing consumer:
ID:anafi.mydomain.org-41122-1260898846989-1:0:-1:1
[10.1.1.210:32918] DEBUG AbstractRegion - Removing consumer:
ID:anafi.mydomain.org-41122-1260898846989-1:0:2:1
[10.1.1.210:32918] DEBUG AbstractRegion - Removing
destination: temp-queue://ID:anafi.mydomain.org-41122-1260898846989-1:0:1
[10.1.1.210:32918] DEBUG AbstractRegion - Removing
destination: topic://ActiveMQ.Advisory.Consumer.Queue.ID:
anafi.mydomain.org-41122-1260898846989-1:0:1
Re: Error on getMeta call to remote service
Posted by Eddie Epstein <ea...@gmail.com>.
On Tue, Dec 15, 2009 at 3:52 PM, Prokopis Prokopidis
<pr...@gmail.com> wrote:
> If it's
> any help, when calling the service from the machine on which it has been
> deployed, or when reversing the service-client roles between the two
> machines, everything works as in the README file.
Hmmm, smells like a clock synchronization problem. In order to avoid
undeliverable messages building up on a broker, timeout settings are
used to create time-to-live properties in the JMS messages. ActiveMQ
implements time-to-live based on the client and server machine clocks.
Eddie