Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Communications Framework (ECF) » Distributed Event Admin Problems
Distributed Event Admin Problems [message #507135] Tue, 12 January 2010 04:47 Go to next message
Andrea Zoppello is currently offline Andrea Zoppello
Messages: 48
Registered: July 2009
Member
Hi all,

I'm doing some test using ECF distributed Event Admin as described here ( http://wiki.eclipse.org/Distributed_EventAdmin_Service ).

I'm trying to use the JMS ( ActiveMQ ) implementation. so i've done the following step:

1) I've downloaded and started active mq ( 5.3 )
2) Follow the instruction at eclipse wiki and installed the examples
3) Installed the jms provider from http://ecf1.osuosl.org/
4) try to run the examples.


The Problems i've are:

1) I've an initial exception when trying to run the Event Admin server ( activemq product ). This is not blocking, it seems this exception is raised but the code is working, i've see messages enqued and dequed from the AMQ console.


12-gen-2010 10.35.48 org.apache.activemq.transport.tcp.TcpTransportFactory createTransport
AVVERTENZA: path isn't a valid local location for TcpTransport to use
java.lang.NumberFormatException: For input string: "/exampleTopic"
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at org.apache.activemq.transport.tcp.TcpTransportFactory.create Transport(TcpTransportFactory.java:125)
at org.apache.activemq.transport.TransportFactory.doConnect(Tra nsportFactory.java:141)
at org.apache.activemq.transport.TransportFactory.doConnect(Tra nsportFactory.java:51)
at org.apache.activemq.transport.TransportFactory.connect(Trans portFactory.java:80)
at org.apache.activemq.ActiveMQConnectionFactory.createTranspor t(ActiveMQConnectionFactory.java:237)
at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQ Connection(ActiveMQConnectionFactory.java:252)
at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQ Connection(ActiveMQConnectionFactory.java:224)
at org.apache.activemq.ActiveMQConnectionFactory.createConnecti on(ActiveMQConnectionFactory.java:172)
at org.eclipse.ecf.provider.jms.channel.AbstractJMSChannel.setu pJMS(AbstractJMSChannel.java:167)
at org.eclipse.ecf.provider.jms.channel.AbstractJMSServerChanne l. <init>(AbstractJMSServerChannel.java:33)
at org.eclipse.ecf.provider.jms.activemq.container.ActiveMQServ erChannel. <init>(ActiveMQServerChannel.java:24)
at org.eclipse.ecf.provider.jms.activemq.container.ActiveMQJMSS erverContainer.start(ActiveMQJMSServerContainer.java:38)
at org.eclipse.ecf.internal.provider.jms.activemq.ActiveMQJMSSe rverContainerInstantiator.createInstance(ActiveMQJMSServerCo ntainerInstantiator.java:57)
at org.eclipse.ecf.core.ContainerFactory.createContainer(Contai nerFactory.java:287)
at org.eclipse.ecf.core.ContainerFactory.createContainer(Contai nerFactory.java:306)
at org.eclipse.ecf.examples.internal.eventadmin.app.AbstractEve ntAdminApplication.createConfigureAndConnectContainer(Abstra ctEventAdminApplication.java:157)
at org.eclipse.ecf.examples.internal.eventadmin.app.AbstractEve ntAdminApplication.startup(AbstractEventAdminApplication.jav a:65)
at org.eclipse.ecf.examples.internal.eventadmin.app.AbstractEve ntAdminApplication.start(AbstractEventAdminApplication.java: 105)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)


2) I've try to run two instance of the Event Admin server ( activemq product ), but this does not work because activemq is refusing my connection with this stacktrace:

WARN | Failed to add Connection
javax.jms.InvalidClientIDException: Broker: localhost - Client: tcp://localhost:
61616/exampleTopic already connected from /127.0.0.1:49513
at org.apache.activemq.broker.region.RegionBroker.addConnection (RegionBr
oker.java:216)
at org.apache.activemq.broker.BrokerFilter.addConnection(Broker Filter.ja
va:82)
at org.apache.activemq.broker.BrokerFilter.addConnection(Broker Filter.ja
va:82)
at org.apache.activemq.advisory.AdvisoryBroker.addConnection(Ad visoryBro
ker.java:77)
at org.apache.activemq.broker.BrokerFilter.addConnection(Broker Filter.ja
va:82)
at org.apache.activemq.broker.MutableBrokerFilter.addConnection (MutableB
rokerFilter.java:89)
at org.apache.activemq.broker.TransportConnection.processAddCon nection(T
ransportConnection.java:666)
at org.apache.activemq.broker.jmx.ManagedTransportConnection.pr ocessAddC
onnection(ManagedTransportConnection.java:83)
at org.apache.activemq.command.ConnectionInfo.visit(ConnectionI nfo.java:
134)
at org.apache.activemq.broker.TransportConnection.service(Trans portConne
ction.java:297)
at org.apache.activemq.broker.TransportConnection$1.onCommand(T ransportC
onnection.java:175)
at org.apache.activemq.transport.TransportFilter.onCommand(Tran sportFilt
er.java:68)
at org.apache.activemq.transport.WireFormatNegotiator.onCommand (WireForm
atNegotiator.java:113)
at org.apache.activemq.transport.InactivityMonitor.onCommand(In activityM
onitor.java:210)
at org.apache.activemq.transport.TransportSupport.doConsume(Tra nsportSup
port.java:84)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTran sport.jav
a:203)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransp ort.java:
185)
at java.lang.Thread.run(Thread.java:619)

This seems to be an activemq problem, but i'd like to see if anyone know how to solve.

Any thougths???


Thanks
Andrea









































































































Re: Distributed Event Admin Problems [message #507815 is a reply to message #507135] Thu, 14 January 2010 13:39 Go to previous messageGo to next message
Scott Lewis is currently offline Scott Lewis
Messages: 966
Registered: July 2009
Senior Member
Hi Andrea,

Andrea Zoppello wrote:
> Hi all,
>
> I'm doing some test using ECF distributed Event Admin as described here
> ( http://wiki.eclipse.org/Distributed_EventAdmin_Service ).
>
> I'm trying to use the JMS ( ActiveMQ ) implementation. so i've done the
> following step:
>
> 1) I've downloaded and started active mq ( 5.3 )
> 2) Follow the instruction at eclipse wiki and installed the examples
> 3) Installed the jms provider from http://ecf1.osuosl.org/
> 4) try to run the examples.
>
>
> The Problems i've are:
>
> 1) I've an initial exception when trying to run the Event Admin server (
> activemq product ). This is not blocking, it seems this exception is
> raised but the code is working, i've see messages enqued and dequed from
> the AMQ console.


Yes. This is a non-fatal bug in ActiveMQ 5.2. I've reported this bug
here: https://issues.apache.org/activemq/browse/AMQ-2256


It's possible this may be fixed in a more recent release, but I have not
yet tried out something newer than 5.2.


<stuff deleted>

>
>
> 2) I've try to run two instance of the Event Admin server ( activemq
> product ), but this does not work because activemq is refusing my
> connection with this stacktrace:
>
> WARN | Failed to add Connection
> javax.jms.InvalidClientIDException: Broker: localhost - Client:
> tcp://localhost:
> 61616/exampleTopic already connected from /127.0.0.1:49513
> at org.apache.activemq.broker.region.RegionBroker.addConnection
> (RegionBr
> oker.java:216)
> at org.apache.activemq.broker.BrokerFilter.addConnection(Broker
> Filter.ja
> va:82)
> at org.apache.activemq.broker.BrokerFilter.addConnection(Broker
> Filter.ja
> va:82)
> at org.apache.activemq.advisory.AdvisoryBroker.addConnection(Ad
> visoryBro
> ker.java:77)
> at org.apache.activemq.broker.BrokerFilter.addConnection(Broker
> Filter.ja
> va:82)
> at org.apache.activemq.broker.MutableBrokerFilter.addConnection
> (MutableB
> rokerFilter.java:89)
> at org.apache.activemq.broker.TransportConnection.processAddCon
> nection(T
> ransportConnection.java:666)
> at org.apache.activemq.broker.jmx.ManagedTransportConnection.pr
> ocessAddC
> onnection(ManagedTransportConnection.java:83)
> at org.apache.activemq.command.ConnectionInfo.visit(ConnectionI
> nfo.java:
> 134)
> at org.apache.activemq.broker.TransportConnection.service(Trans
> portConne
> ction.java:297)
> at org.apache.activemq.broker.TransportConnection$1.onCommand(T
> ransportC
> onnection.java:175)
> at org.apache.activemq.transport.TransportFilter.onCommand(Tran
> sportFilt
> er.java:68)
> at org.apache.activemq.transport.WireFormatNegotiator.onCommand
> (WireForm
> atNegotiator.java:113)
> at org.apache.activemq.transport.InactivityMonitor.onCommand(In
> activityM
> onitor.java:210)
> at org.apache.activemq.transport.TransportSupport.doConsume(Tra
> nsportSup
> port.java:84)
> at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTran
> sport.jav
> a:203)
> at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransp
> ort.java:
> 185)
> at java.lang.Thread.run(Thread.java:619)
>
> This seems to be an activemq problem, but i'd like to see if anyone know
> how to solve.


There can be only one manager/server process associated with a given JMS
topic (in this case, the server being started is using the default
uri/topic...which is tcp://localhost:61616/exampleTopic

So if you want to create/start/run more than one server, all you need to
do is create/specify/use another topic...e.g.:

tcp://localhost:61616/myTopic

In the example server (i.e. the one in
org.eclipse.ecf.examples.remoteservices.hello.host), their is a command
line argument...e.g.:

-containerId tcp://localhost:61616/myTopic

that allows the server containerId to be specified on the command line
along with the container *type*...i.e.

-containerType ecf.jms.activemq.tcp.manager

If you look in the product configuration file:

/org.eclipse.ecf.examples.remoteservices.hello.host/products /Hello
Service Host (activemq).product

You will see that these Program Arguments are listed (on the Launching
tab of the product configuration editor):

-containerType ecf.jms.activemq.tcp.manager
-containerId tcp://localhost:61616/exampleTopic

You can/could easily just create a new product file, copied from the
existing one, and change the command line arguments to be (e.g.)

-containerType ecf.jms.activemq.tcp.manager
-containerId tcp://localhost:61616/myTopic


Or, you can have a completely different/new application (i.e. not this
HelloHostApplication, and specify the containerType and containerId any
way you like (via properties file, as program arguments, hardcoded into
the app, etc).

Scott
Re: Distributed Event Admin Problems [message #507863 is a reply to message #507815] Thu, 14 January 2010 16:51 Go to previous message
Scott Lewis is currently offline Scott Lewis
Messages: 966
Registered: July 2009
Senior Member
Hi Andrea,

My apologies...I made a mistake in assuming that you were/are working
with the remoteservices host/consumer examples...as you said, you are
clearly working with the distributed event admin, and hopefully/probably
with the project: org.eclipse.ecf.examples.eventadmin.app.

My description of the parameters was assuming the use of the wrong
project then...I'm sorry about that.

Happily the EventAdminManagerApplication does *also* have the same
containerType and containerId Program Arguments...so you should be able
to specify the second topic in the same way...i.e.

-containerType ecf.jms.activemq.tcp.manager
-containerId tcp://localhost:61616/myTopic

Please let me know if this doesn't work out for whatever reason.

Also, you might consider joining the ECF mailing list and we could have
this discussion there...and the rest of the community can/could benefit
from the discussion. Thanks...the ecf-dev mailing list can be joined
by going here: http://dev.eclipse.org/mhonarc/lists/ecf-dev

Thanks,

Scott


Scott Lewis wrote:
> Hi Andrea,
>
> Andrea Zoppello wrote:
>> Hi all,
>>
>> I'm doing some test using ECF distributed Event Admin as described
>> here ( http://wiki.eclipse.org/Distributed_EventAdmin_Service ).
>>
>> I'm trying to use the JMS ( ActiveMQ ) implementation. so i've done
>> the following step:
>>
>> 1) I've downloaded and started active mq ( 5.3 )
>> 2) Follow the instruction at eclipse wiki and installed the examples
>> 3) Installed the jms provider from http://ecf1.osuosl.org/
>> 4) try to run the examples.
>>
>>
>> The Problems i've are:
>>
>> 1) I've an initial exception when trying to run the Event Admin server
>> ( activemq product ). This is not blocking, it seems this exception is
>> raised but the code is working, i've see messages enqued and dequed
>> from the AMQ console.
>
>
> Yes. This is a non-fatal bug in ActiveMQ 5.2. I've reported this bug
> here: https://issues.apache.org/activemq/browse/AMQ-2256
>
>
> It's possible this may be fixed in a more recent release, but I have not
> yet tried out something newer than 5.2.
>
>
> <stuff deleted>
>
>>
>>
>> 2) I've try to run two instance of the Event Admin server ( activemq
>> product ), but this does not work because activemq is refusing my
>> connection with this stacktrace:
>>
>> WARN | Failed to add Connection
>> javax.jms.InvalidClientIDException: Broker: localhost - Client:
>> tcp://localhost:
>> 61616/exampleTopic already connected from /127.0.0.1:49513
>> at
>> org.apache.activemq.broker.region.RegionBroker.addConnection (RegionBr
>> oker.java:216)
>> at
>> org.apache.activemq.broker.BrokerFilter.addConnection(Broker Filter.ja
>> va:82)
>> at
>> org.apache.activemq.broker.BrokerFilter.addConnection(Broker Filter.ja
>> va:82)
>> at
>> org.apache.activemq.advisory.AdvisoryBroker.addConnection(Ad visoryBro
>> ker.java:77)
>> at
>> org.apache.activemq.broker.BrokerFilter.addConnection(Broker Filter.ja
>> va:82)
>> at
>> org.apache.activemq.broker.MutableBrokerFilter.addConnection (MutableB
>> rokerFilter.java:89)
>> at
>> org.apache.activemq.broker.TransportConnection.processAddCon nection(T
>> ransportConnection.java:666)
>> at
>> org.apache.activemq.broker.jmx.ManagedTransportConnection.pr ocessAddC
>> onnection(ManagedTransportConnection.java:83)
>> at
>> org.apache.activemq.command.ConnectionInfo.visit(ConnectionI nfo.java:
>> 134)
>> at
>> org.apache.activemq.broker.TransportConnection.service(Trans portConne
>> ction.java:297)
>> at
>> org.apache.activemq.broker.TransportConnection$1.onCommand(T ransportC
>> onnection.java:175)
>> at
>> org.apache.activemq.transport.TransportFilter.onCommand(Tran sportFilt
>> er.java:68)
>> at
>> org.apache.activemq.transport.WireFormatNegotiator.onCommand (WireForm
>> atNegotiator.java:113)
>> at
>> org.apache.activemq.transport.InactivityMonitor.onCommand(In activityM
>> onitor.java:210)
>> at
>> org.apache.activemq.transport.TransportSupport.doConsume(Tra nsportSup
>> port.java:84)
>> at
>> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTran sport.jav
>> a:203)
>> at
>> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransp ort.java:
>> 185)
>> at java.lang.Thread.run(Thread.java:619)
>>
>> This seems to be an activemq problem, but i'd like to see if anyone
>> know how to solve.
>
>
> There can be only one manager/server process associated with a given JMS
> topic (in this case, the server being started is using the default
> uri/topic...which is tcp://localhost:61616/exampleTopic
>
> So if you want to create/start/run more than one server, all you need to
> do is create/specify/use another topic...e.g.:
>
> tcp://localhost:61616/myTopic
>
> In the example server (i.e. the one in
> org.eclipse.ecf.examples.remoteservices.hello.host), their is a command
> line argument...e.g.:
>
> -containerId tcp://localhost:61616/myTopic
>
> that allows the server containerId to be specified on the command line
> along with the container *type*...i.e.
>
> -containerType ecf.jms.activemq.tcp.manager
>
> If you look in the product configuration file:
>
> /org.eclipse.ecf.examples.remoteservices.hello.host/products /Hello
> Service Host (activemq).product
>
> You will see that these Program Arguments are listed (on the Launching
> tab of the product configuration editor):
>
> -containerType ecf.jms.activemq.tcp.manager
> -containerId tcp://localhost:61616/exampleTopic
>
> You can/could easily just create a new product file, copied from the
> existing one, and change the command line arguments to be (e.g.)
>
> -containerType ecf.jms.activemq.tcp.manager
> -containerId tcp://localhost:61616/myTopic
>
>
> Or, you can have a completely different/new application (i.e. not this
> HelloHostApplication, and specify the containerType and containerId any
> way you like (via properties file, as program arguments, hardcoded into
> the app, etc).
>
> Scott
Re: Distributed Event Admin Problems [message #624992 is a reply to message #507815] Thu, 14 January 2010 16:51 Go to previous message
Scott Lewis is currently offline Scott Lewis
Messages: 966
Registered: July 2009
Senior Member
Hi Andrea,

My apologies...I made a mistake in assuming that you were/are working
with the remoteservices host/consumer examples...as you said, you are
clearly working with the distributed event admin, and hopefully/probably
with the project: org.eclipse.ecf.examples.eventadmin.app.

My description of the parameters was assuming the use of the wrong
project then...I'm sorry about that.

Happily the EventAdminManagerApplication does *also* have the same
containerType and containerId Program Arguments...so you should be able
to specify the second topic in the same way...i.e.

-containerType ecf.jms.activemq.tcp.manager
-containerId tcp://localhost:61616/myTopic

Please let me know if this doesn't work out for whatever reason.

Also, you might consider joining the ECF mailing list and we could have
this discussion there...and the rest of the community can/could benefit
from the discussion. Thanks...the ecf-dev mailing list can be joined
by going here: http://dev.eclipse.org/mhonarc/lists/ecf-dev

Thanks,

Scott


Scott Lewis wrote:
> Hi Andrea,
>
> Andrea Zoppello wrote:
>> Hi all,
>>
>> I'm doing some test using ECF distributed Event Admin as described
>> here ( http://wiki.eclipse.org/Distributed_EventAdmin_Service ).
>>
>> I'm trying to use the JMS ( ActiveMQ ) implementation. so i've done
>> the following step:
>>
>> 1) I've downloaded and started active mq ( 5.3 )
>> 2) Follow the instruction at eclipse wiki and installed the examples
>> 3) Installed the jms provider from http://ecf1.osuosl.org/
>> 4) try to run the examples.
>>
>>
>> The Problems i've are:
>>
>> 1) I've an initial exception when trying to run the Event Admin server
>> ( activemq product ). This is not blocking, it seems this exception is
>> raised but the code is working, i've see messages enqued and dequed
>> from the AMQ console.
>
>
> Yes. This is a non-fatal bug in ActiveMQ 5.2. I've reported this bug
> here: https://issues.apache.org/activemq/browse/AMQ-2256
>
>
> It's possible this may be fixed in a more recent release, but I have not
> yet tried out something newer than 5.2.
>
>
> <stuff deleted>
>
>>
>>
>> 2) I've try to run two instance of the Event Admin server ( activemq
>> product ), but this does not work because activemq is refusing my
>> connection with this stacktrace:
>>
>> WARN | Failed to add Connection
>> javax.jms.InvalidClientIDException: Broker: localhost - Client:
>> tcp://localhost:
>> 61616/exampleTopic already connected from /127.0.0.1:49513
>> at
>> org.apache.activemq.broker.region.RegionBroker.addConnection (RegionBr
>> oker.java:216)
>> at
>> org.apache.activemq.broker.BrokerFilter.addConnection(Broker Filter.ja
>> va:82)
>> at
>> org.apache.activemq.broker.BrokerFilter.addConnection(Broker Filter.ja
>> va:82)
>> at
>> org.apache.activemq.advisory.AdvisoryBroker.addConnection(Ad visoryBro
>> ker.java:77)
>> at
>> org.apache.activemq.broker.BrokerFilter.addConnection(Broker Filter.ja
>> va:82)
>> at
>> org.apache.activemq.broker.MutableBrokerFilter.addConnection (MutableB
>> rokerFilter.java:89)
>> at
>> org.apache.activemq.broker.TransportConnection.processAddCon nection(T
>> ransportConnection.java:666)
>> at
>> org.apache.activemq.broker.jmx.ManagedTransportConnection.pr ocessAddC
>> onnection(ManagedTransportConnection.java:83)
>> at
>> org.apache.activemq.command.ConnectionInfo.visit(ConnectionI nfo.java:
>> 134)
>> at
>> org.apache.activemq.broker.TransportConnection.service(Trans portConne
>> ction.java:297)
>> at
>> org.apache.activemq.broker.TransportConnection$1.onCommand(T ransportC
>> onnection.java:175)
>> at
>> org.apache.activemq.transport.TransportFilter.onCommand(Tran sportFilt
>> er.java:68)
>> at
>> org.apache.activemq.transport.WireFormatNegotiator.onCommand (WireForm
>> atNegotiator.java:113)
>> at
>> org.apache.activemq.transport.InactivityMonitor.onCommand(In activityM
>> onitor.java:210)
>> at
>> org.apache.activemq.transport.TransportSupport.doConsume(Tra nsportSup
>> port.java:84)
>> at
>> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTran sport.jav
>> a:203)
>> at
>> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransp ort.java:
>> 185)
>> at java.lang.Thread.run(Thread.java:619)
>>
>> This seems to be an activemq problem, but i'd like to see if anyone
>> know how to solve.
>
>
> There can be only one manager/server process associated with a given JMS
> topic (in this case, the server being started is using the default
> uri/topic...which is tcp://localhost:61616/exampleTopic
>
> So if you want to create/start/run more than one server, all you need to
> do is create/specify/use another topic...e.g.:
>
> tcp://localhost:61616/myTopic
>
> In the example server (i.e. the one in
> org.eclipse.ecf.examples.remoteservices.hello.host), their is a command
> line argument...e.g.:
>
> -containerId tcp://localhost:61616/myTopic
>
> that allows the server containerId to be specified on the command line
> along with the container *type*...i.e.
>
> -containerType ecf.jms.activemq.tcp.manager
>
> If you look in the product configuration file:
>
> /org.eclipse.ecf.examples.remoteservices.hello.host/products /Hello
> Service Host (activemq).product
>
> You will see that these Program Arguments are listed (on the Launching
> tab of the product configuration editor):
>
> -containerType ecf.jms.activemq.tcp.manager
> -containerId tcp://localhost:61616/exampleTopic
>
> You can/could easily just create a new product file, copied from the
> existing one, and change the command line arguments to be (e.g.)
>
> -containerType ecf.jms.activemq.tcp.manager
> -containerId tcp://localhost:61616/myTopic
>
>
> Or, you can have a completely different/new application (i.e. not this
> HelloHostApplication, and specify the containerType and containerId any
> way you like (via properties file, as program arguments, hardcoded into
> the app, etc).
>
> Scott
Previous Topic:Distributed Event Admin Problems
Next Topic:ECF Rest: Bug 297239 (requestEntity)
Goto Forum:
  


Current Time: Fri Aug 01 07:54:03 EDT 2014

Powered by FUDForum. Page generated in 0.02263 seconds