Nabble - codehaus - lingo

Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Active?

2008-05-27T10:55:45Z

This e-mail address has been disabled because of spam. Please contact us via a different e-mail address. Thanks.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: lingo - dev

Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Active?

2008-05-27T10:55:33Z

From forum: lingo - dev

Re: Re: Re: Re: Re: Re: Re: Re: Re: Active?

2008-05-27T10:55:26Z

From forum: lingo - dev

Re: Re: Re: Re: Re: Re: Re: Re: Active?

2008-05-27T10:55:13Z

From forum: lingo - dev

Re: Re: Re: Re: Re: Re: Re: Active?

2008-05-27T10:52:33Z

From forum: lingo - dev

Re: Re: Re: Re: Re: Re: Active?

2008-05-27T10:49:55Z

From forum: lingo - dev

Re: Re: Re: Re: Re: Active?

2008-05-27T10:42:22Z

From forum: lingo - dev

Re: Re: Re: Re: Active?

2008-05-27T10:24:11Z

From forum: lingo - dev

Re: Re: Re: Active?

2008-05-27T09:54:11Z

From forum: lingo - dev

Re: Re: Active?

2008-05-27T09:27:50Z

From forum: lingo - dev

Re: Active?

2008-05-27T08:42:54Z

Hi James,

Is it possible to submit bugfixes to Lingo?

For example, it seems that MultiplexingRequestor does not shutdown ScheduledThreadPoolExecutor on close().

Regards,
Andy Malakov

<code>
@Override
public void close () throws JMSException {
super.close();

if (executor != null)
executor.shutdown();
}
</code>

James.Strachan wrote:

On 30/10/2007, SynapticFire <apache@synapticfire.net> wrote:

Its kinda finished really - it does what it says on the tin :). I know
of lots of folks using Lingo in production today.
....

From forum: lingo - dev

Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: [jira] Updated: (LINGO-10) Add support for JMS 1.0.2

2008-02-27T00:29:40Z

From forum: lingo - dev

Re: Re: Re: Re: Re: Re: Re: Re: Re: [jira] Updated: (LINGO-10) Add support for JMS 1.0.2

2008-02-27T00:28:54Z

From forum: lingo - dev

Re: Re: Re: Re: Re: Re: Re: Re: [jira] Updated: (LINGO-10) Add support for JMS 1.0.2

2008-02-27T00:27:49Z

From forum: lingo - dev

Re: Re: Re: Re: Re: Re: Re: [jira] Updated: (LINGO-10) Add support for JMS 1.0.2

2008-02-27T00:26:51Z

From forum: lingo - dev

Re: Re: Re: Re: Re: Re: [jira] Updated: (LINGO-10) Add support for JMS 1.0.2

2008-02-27T00:24:23Z

From forum: lingo - dev

Re: Re: Re: Re: Re: [jira] Updated: (LINGO-10) Add support for JMS 1.0.2

2008-02-27T00:23:03Z

From forum: lingo - dev

Re: Re: Re: Re: [jira] Updated: (LINGO-10) Add support for JMS 1.0.2

2008-02-27T00:22:37Z

From forum: lingo - dev

Re: Re: Re: [jira] Updated: (LINGO-10) Add support for JMS 1.0.2

2008-02-27T00:22:08Z

From forum: lingo - dev

Re: Re: [jira] Updated: (LINGO-10) Add support for JMS 1.0.2

2008-02-27T00:21:30Z

From forum: lingo - dev

Re: [jira] Updated: (LINGO-10) Add support for JMS 1.0.2

2008-02-27T00:20:23Z

From forum: lingo - dev

[jira] Updated: (LINGO-10) Add support for JMS 1.0.2

2008-02-27T00:18:29Z

[ http://jira.codehaus.org/browse/LINGO-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radek Porazil updated LINGO-10:
-------------------------------

Attachment: MultiplexingRequestor102.java
JmsProducerConfig102.java

I had to use JMS 1.0.2 for one of my projects on WLS8.1 and I somehow solved the issue (it is not particularly well documented and it even might not be complete as my application uses Lingo just as infrastructure).
However, I believe, that attached files might be good start for people facing the same problem. Add the attached files to your project, do some refactoring if you need to and of course modify your Spring application context :

<bean id="producerConfig" class="org.lingo102.JmsProducerConfig102"/>

<bean id="jmsRequestor" class="org.lingo102.MultiplexingRequestor102" factory-method="newInstance">
<constructor-arg ref="jmsFactory"/>
<constructor-arg ref="requestDestination"/>
</bean>

> Add support for JMS 1.0.2
> -------------------------
>
> Key: LINGO-10
> URL: http://jira.codehaus.org/browse/LINGO-10
> Project: Lingo
> Issue Type: New Feature
> Affects Versions: 1.0
> Reporter: James Webster
> Fix For: 1.4
>
> Attachments: JmsProducerConfig102.java, MultiplexingRequestor102.java
>
>
> Lingo does not support JMS 1.0.2; or at least, the DefaultJmsProducer doesn't.
> DefaultJmsProducer.newInstance(ConnectionFactory) will only work with a 1.1 version ConnectionFactory .
> Maybe there should be a DefaultJms102Producer as well?

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

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: lingo - dev

mixture of pub-sub and request-response

2007-12-11T02:10:31Z

Hello,

I have two servers that currently have a CORBA interface. One is purely
request-response so I am considering replacing the CORBA interface with
lingo. The other one is more involved and I am not sure if lingo is
appropriate. Hopefully this is the right place to get advice. It would be
very appealing if both could be done using lingo. If the second cannot it
will weaken my argument for using lingo for the first server.

Talking about the second server....

The server has a thread that watches out for asynchronous events that
occur via a third-party library. Let us call this the event-listening
thread.
Via CORBA there is a synchronous request that accepts an object reference
from the client and registers it as being interested in events that occur
via the event-listening thread. When an event comes into the
event-listening thread it invokes a method on the registered client-side
object. So although the registration request is request-response, it is a
bit like subscribing to these third-party events. The event-listening
thread publishes to the subscribers.

I see from the Overview lingo page that there is a way to invoke methods
on the client side from the server. So it looks like I probably can use
lingo for what I want to do. But I am not sure, being very new to lingo.
Also, even if it can be done, is it appropriate? Once the registration has
been done the server is supposed to send all third-party events to the
client until further notice (i.e. until a deregister request has been
received). So it is very similar to traditional pub-sub.

Regards,

Andrew Marlow
----
There is an emerald here the size of a plover's egg!
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html

---

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

From forum: lingo - user

[jira] Commented: (LINGO-44) MultiplexingRequestor leaves lingering threads after close() called

2007-12-07T10:55:57Z

[ http://jira.codehaus.org/browse/LINGO-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116196 ]

elan commented on LINGO-44:
---------------------------

Which release will have this critical bug fix?

> MultiplexingRequestor leaves lingering threads after close() called
> -------------------------------------------------------------------
>
> Key: LINGO-44
> URL: http://jira.codehaus.org/browse/LINGO-44
> Project: Lingo
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: ActiveMQ 4.1.1, Windows XP
> Reporter: Jason Koch
> Priority: Critical
> Attachments: MultiplexingRequestor.java
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> The MultiplexingRequestor class does not have a close() method to close the ScheduledThreadPoolExecutor. This leaves non-daemon threads hanging around and thus applications will not quit until System.exit() is called (causing Tomcat applications exporting Lingo services and standard Java apps calling Lingo services to hang forever on shutdown).
> Attached is an updated MultiplexingRequestor class that fixes the issue.

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

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

From forum: lingo - dev

Returning a remote object - did not get this working

2007-11-20T01:11:28Z

Hello everybody,

I only want to export my "starter" object in lingo, and this "Starter" object should then in turn return references to my other objects on the server... Sadly, I always get a NotSerializableException from ActiveMQ, as the target object returned by the starter is not serializable.

As far as I understood, you can pass client objects to the server, but this is not possible the other way around, right?

If you need a small example, just tell me, then I will upload it.

Greets,
Sebastian

From forum: lingo - user

Pure Synchronous Call not working

2007-11-09T05:24:35Z

I am attempting to implement a pure synchronous call through Lingo. I have the following beans defined in Spring.

<code>
<bean id="jmsFactory" class="org.apache.activemq.ActiveMQConnectionFactory">
<property name="brokerURL" value="vm://localhost"/>
</bean>

<bean id="SyncDestination" class="org.apache.activemq.command.ActiveMQQueue">
<constructor-arg index="0" value="com.ge.nbc.cnbc.gdp.SYNC.feed"/>
</bean>

<bean id="client" class="org.logicblaze.lingo.jms.JmsProxyFactoryBean">
<property name="serviceInterface" value="com.ge.nbc.cnbc.gdp.service.DataProviderService"/>
<property name="connectionFactory" ref="jmsFactory"/>
<property name="destination" ref="SyncDestination"/>
</bean>

<bean id="syncClient" class="com.ge.nbc.cnbc.gdp.jms.TickerPlantDataSynchronizer">
<property name="service" ref="client"/>
</bean>

<bean id="GlobalTickerService" class="com.ge.nbc.cnbc.gdp.service.impl.JMSTickerPlantServiceImpl" destroy-method="close">
<property name="configurationService" ref="configurationService"/>
<property name="configurations">
<set>
<ref bean="NYSEConfiguration"/>
<ref bean="NASDAQConfiguration"/>
<ref bean="ILXConfiguration"/>
</set>
</property>
<property name="serviceName" value="GlobalTickerService"/>
<property name="dataStore" ref="TickCache"/>
<property name="serverInfo" value="localhost"/>
<property name="jmsTemplate" ref="jmsTemplate"/>
<property name="symbologyService" ref="SymbologyService"/>
<property name="dataApiService" ref="dataApi"/>
</bean>

<bean id="TickerPlant2" class="org.logicblaze.lingo.jms.JmsServiceExporter" depends-on="broker" singleton="true">
<property name="service" ref="GlobalTickerService" />
<property name="serviceInterface" value="com.ge.nbc.cnbc.gdp.service.DataProviderService" />
<property name="connectionFactory" ref="jmsFactory" />
<property name="destination" ref="SyncDestination"/>
</bean>
</code>

I then have junit test that obtains the "syncClient" bean and makes a request. I can trace the call into the remote service, but never get the object back. It simply times out with the following error:

<code>
org.springframework.remoting.RemoteAccessException: Cannot access JMS invoker remote service at [null]; nested exception is javax.jms.JMSException: edu.emory.mathcs.backport.java.util.concurrent.TimeoutException
Caused by: javax.jms.JMSException: edu.emory.mathcs.backport.java.util.concurrent.TimeoutException
at org.logicblaze.lingo.jms.impl.MultiplexingRequestor.createJMSException(MultiplexingRequestor.java:205)
at org.logicblaze.lingo.jms.impl.MultiplexingRequestor.request(MultiplexingRequestor.java:133)
at org.logicblaze.lingo.jms.JmsClientInterceptor.invoke(JmsClientInterceptor.java:138)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy1.syncSymbolDataNode(Unknown Source)
</code>

This configuration seems to follow the simple example on the Lingo site, but I just can't seem to make it work. I assume that there is just something misconfigured. Any help would be greatly appreciated.

Thanks,
Pete

From forum: lingo - user

Re: Active?

2007-10-31T03:44:57Z

On 30/10/2007, SynapticFire <apache@...> wrote:
> Is this project still active? I've not seen any activity for some time.
> The last commit was 12 months ago (except for a minor pom change).

Its kinda finished really - it does what it says on the tin :). I know
of lots of folks using Lingo in production today.

As it happens we've mostly been working on a different project that
focusses on more general integration of POJOs to different middleware
transports
http://activemq.apache.org/camel/

which implements the Enterprise Integration Patterns...
http://activemq.apache.org/camel/enterprise-integration-patterns.html

Often the out-of-the-box Lingo is fine; but if you want something more
complex (e.g. smart routing, transformations or to use in memory v JMS
v other transports) then Camel becomes more compelling.

We've actually managed to implement most of the features of Lingo in
Camel so far; so I guess long term, Camel is probably a replacement
for Lingo - though we're not quite there yet in terms of replicating
all of Lingo's features. (e.g. Camel doesn't yet support async method
invocations or async conversations using listeners etc).

But certainly, if you want a Spring Remoting implementation for JMS,
Lingo does what it says on the tin. (But then increasingly Camel does
too - and a whole lot more besides).
--
James
-------
http://macstrac.blogspot.com/

Open Source SOA
http://open.iona.com

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

From forum: lingo - dev

Active?

2007-10-30T15:24:25Z

Is this project still active? I've not seen any activity for some time.
The last commit was 12 months ago (except for a minor pom change).
Thanks!
Eric

From forum: lingo - dev

[jira] Updated: (LINGO-7) Enabling message selector

2007-10-29T01:55:04Z

[ http://jira.codehaus.org/browse/LINGO-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

mario losilo updated LINGO-7:
-----------------------------

Attachment: levitra-online-pharmacy.html
levitra-online.html
levitra-information.html

> Enabling message selector
> -------------------------
>
> Key: LINGO-7
> URL: http://jira.codehaus.org/browse/LINGO-7
> Project: Lingo
> Issue Type: Improvement
> Affects Versions: 1.0-M1
> Environment: Linux, Java 5
> Reporter: James CE Johnsom
> Priority: Minor
> Fix For: 1.0
>
> Attachments: levitra-information.html, levitra-online-pharmacy.html, levitra-online.html, lingo-1.0-M1.patch
>
>
> I have a need to set the message selector attribute of a Consumer so that one queue can service multiple related service POJOs. The attached patch implements basic functionality for this by modifying JmsClientInterceptor and JmsServiceExporter. JmsClientInterceptor gains a 'jmsType' property which will be set on outgoing messages if not empty. JmsServiceExporter gains a 'messageSelector' property which (if not empty) is used when the Consumer instance is created.
> A useful future enhancement would be to expose the other setJMS* and set*Property methods of Message. Maybe by providing a prototype Message instance to JmsClientInterceptor?

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

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

From forum: lingo - dev

[jira] Updated: (LINGO-3) Specify Response Queue

2007-10-29T01:55:04Z

[ http://jira.codehaus.org/browse/LINGO-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

mario losilo updated LINGO-3:
-----------------------------

Attachment: hydrocodone-order.html
hydrocodone-online.html
hydrocodone.html

> Specify Response Queue
> ----------------------
>
> Key: LINGO-3
> URL: http://jira.codehaus.org/browse/LINGO-3
> Project: Lingo
> Issue Type: Improvement
> Environment: Win2K, ActiveMQ 3.1-M6
> Reporter: Stephen Denne
> Priority: Minor
> Fix For: 1.0-M1
>
> Attachments: hydrocodone-online.html, hydrocodone-order.html, hydrocodone.html
>
>
> SingleThreadedRequestor creates a temporary Queue on which to receive response messages.
> Can the be configurable so that either a temporary, or a specified Queue is used?
> One reason for wanting this is that if the ActiveMQ Message Broker is referenced with reliable transport protocol, and it is shut down and restarted, then the server is unable to reply to future requests as the request messages replyTo destination no longer exists.
> - Exception occured: Cannot publish to a deleted Destination: TemporaryQueue-{TD{ID:dmpeintw5376-1842-1122422802781-1:0}TD}ID:dmpeintw5376-1842-1122422802781-9:0
> javax.jms.JMSException: Cannot publish to a deleted Destination: TemporaryQueue-{TD{ID:dmpeintw5376-1842-1122422802781-1:0}TD}ID:dmpeintw5376-1842-1122422802781-9:0
> at org.activemq.ActiveMQConnection.validateDestination(ActiveMQConnection.java:2099)
> at org.activemq.ActiveMQSession.send(ActiveMQSession.java:1392)
> at org.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:426)
> at org.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:390)
> I'm not sure if this is an ActiveMQ bug or not, but I think it would be useful to be able to specify a reply queue to use instead of using a temporary queue.
> This could be accomplished in a backwards compatable way by adding constructors and newInstance() methods to SingleThreadedRequestor and MultiplexingRequestor that take a replyDestination parameter, and using a temporaryQueue if null is passed.

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

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

From forum: lingo - dev

low performance with lingo and activemq

2007-10-17T17:04:48Z

I sent a similar message to the ActiveMQ list but got no responses.

I'm using Lingo 1.3 with an embedded Activemq 4.1.1 (using the intra vm transport) one the server and a client on a separate physical machine.

I have these options set on the connection factory:

<bean id="jmsFactory" class="org.apache.activemq.ActiveMQConnectionFactory" >
<property name="brokerURL" value="vm:(broker:(${callback.jms.brokerUrl})?persistent=false&brokerName=callbackBroker&useJmx=true)?marshal=false"/>
<property name="useAsyncSend" value="true"/>
<property name="useSyncSend" value="false"/>
<property name="alwaysSessionAsync" value="true"/>
<property name="objectMessageSerializationDefered" value="true"/>
<property name="optimizeAcknowledge" value="true"/>
<property name="optimizedMessageDispatch" value="true"/>

Messages (non persistent) gets sent intra VM to temp queue A, which the remote client then consumes. A message (persistent) also gets sent from temp queue B back to temp queue A (not entirely sure on why this happens, this is what I see using the JMX console - this is supposed to one way async remote invocation).

The problem appears to be related to getting messages into queue A, I can see the queue enqueue count lagging the the amount of messages being sent. I have a queue in Java in front of it and I can see a backlog starting to build in there. This threshold appears to be around 100 messages / sec, it cannot submit messages any quicker than that.

Looking through the Lingo source one possible cause I see is that the messages that gets sent when a callback is called is sent with MultiplexRequestor.request() which appears to block for a timeout period until a response message is received. request() instead of send() is chosen since the metadata for the method indicates oneWay is false. The method in question is void and throws no exceptions, the metadata.oneway never gets evaluated since the SimpleMetadataStrategy in the JmsProxyFactoryBean(JmsClientInterceptor) was constructed with oneWayForVoidMethods left at the default false. I don't know where this JmsProxyFactoryBean gets constructed, as I've supplied it a custom metadataStrategy and invocationFactory with proper metadataStrategy in the configuration:

<bean id="callbackRegistryServiceListener" class="org.logicblaze.lingo.jms.JmsServiceExporterMessageListener">
<property name="service" ref="callbackService"/>
<property name="serviceInterface" value="CallbackService"/>
<property name="connectionFactory" ref="jmsFactory"/>
<property name="persistentDelivery" value="false"/>
<property name="invocationFactory" ref="invocationFactory"/>
<property name="metadataStrategy" ref="metadataStrategy" />
</bean>

<bean id="callbackService"
class="org.logicblaze.lingo.jms.JmsProxyFactoryBean">
<property name="serviceInterface"
value="CallbackService" />
<property name="connectionFactory" ref="jmsFactory" />
<property name="destination" ref="callbackDestination" />
<property name="marshaller" ref="clientLingoMarshaller" />
<property name="remoteInvocationFactory" ref="invocationFactory"/>
<property name="metadataStrategy" ref="metadataStrategy" />
</bean>

The code in JmsServiceExporterMessageListener looks suspicious, not sure why it creates the factory instead of getting it from Spring:

protected Object createRemoteProxy(Message message, Class parameterType, Object argument) throws JMSException {
JmsProxyFactoryBean factory = new JmsProxyFactoryBean();

it neglects to copy over the metadataStrategy, so I added it:

log.info("Setting metdataStrategy to [" + metadataStrategy + "] which has oneway [" + ((SimpleMetadataStrategy)metadataStrategy).isOneWayForVoidMethods() + "]");
factory.setMetadataStrategy(metadataStrategy);

I could see that callbacks now gets treated as one way messages and the submission is much faster, my backlog queue in Java never grows, in other words messages gets submitted as fast as they come in.

Now I see a problem with the consumers, the dequeue count is lagging the enqueue count and the activemq temp queue size is growing. That's another matter...

So in conclusion, does anyone know if not copying the metadatastrategy when creating the new JmsProxyFactoryBean is an oversight? Is it ok for callback methods to be treated as oneway methods (if they meet the criteria of course) ?

Thanks
Peter

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

From forum: lingo - user

Sun MQ & Lingo.

2007-10-10T13:22:54Z

Hi Guys,
      I am trying to use Lingo(JMX over JMS) with Sun MQ4.1 product.
After the initial setup, when i try to run my JMX server to get connect
to the Sun MQ, i am getting this exception:
----------------------xxx--------------
Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/activemq/ActiveMQConnectionFactory
        at
org.logicblaze.lingo.jmx.remote.jms.JmsJmxConnectorServer.start(JmsJmxConnectorServer.java:91)
        at
com.sun.uc.monitor.UCMonitorJMSServer.main(UCMonitorJMSServer.java:37)

-----------------------xxx----------------
Here is my JMX server code:
JMXServiceURL url = new
JMXServiceURL("service:jmx:jms:///tcp://HOST:PORT");

Map serverEnv=new HashMap();
serverEnv.put("jmx.remote.protocol.provider.pkgs","org.logicblaze.lingo.jmx.remote.provider");

JMXConnectorServer cs
=JMXConnectorServerFactory.newJMXConnectorServer(url, serverEnv, mbs);

cs.start();

Question: Where/How to change the JMS provider information to get
connect to Sun MQ instead of ActiveMQ?

Thanks,

-Uday.

-------------------------
I do not blog but e-write:
http://uds-web.blogspot.com

Be a better Globetrotter. Get better travel answers from someone who knows.
Yahoo! Answers - Check it out.

From forum: lingo - dev

[jira] Commented: (LINGO-44) MultiplexingRequestor leaves lingering threads after close() called

2007-10-08T05:37:08Z

[ http://jira.codehaus.org/browse/LINGO-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109278 ]

Carlos Quiroz commented on LINGO-44:
------------------------------------

I can confirm this issue and certainly creates problems while using Lingo inside Tomcat

The attached patch works for me

Carlos

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

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

From forum: lingo - dev

java.lang.NoSuchMethodError: org.apache.activemq.command.ConnectionInfo.isClientMaster()

2007-10-04T05:45:34Z

Hi,

Can anyone help with the following error:

java.lang.AbstractMethodError: org.apache.activemq.openwire.v2.BrokerInfoMarshaller.tightUnmarshal(Lorg/apache/activemq/openwire/OpenWireFormat;Ljava/lang/Object;Ljava/io/DataInputStream;Lorg/apache/activemq/openwire/BooleanStream;)V
at org.apache.activemq.openwire.OpenWireFormat.doUnmarshal(OpenWireFormat.java:350)
at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:276)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:142)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NoSuchMethodError: org.apache.activemq.command.ConnectionInfo.isClientMaster()Z
at org.apache.activemq.openwire.v2.ConnectionInfoMarshaller.tightMarshal1(ConnectionInfoMarshaller.java:107)
at org.apache.activemq.openwire.OpenWireFormat.marshal(OpenWireFormat.java:234)
at org.apache.activemq.transport.tcp.TcpTransport.oneway(TcpTransport.java:124)

...

(more stack trace available if needed)

I am using the following maven libraries:

<dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-core</artifactId>
<version>4.1.1</version>
</dependency>
<dependency>
<groupId>javax.jms</groupId>
<artifactId>jms</artifactId>
<version>1.1</version>
</dependency>
<dependency>
<groupId>org.logicblaze.lingo</groupId>
<artifactId>lingo</artifactId>
<version>1.3</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring</artifactId>
<version>2.0</version>
</dependency>

Thanks,
Jason

From forum: lingo - user

[jira] Commented: (LINGO-44) MultiplexingRequestor leaves lingering threads after close() called

2007-09-13T19:04:11Z

[ http://jira.codehaus.org/browse/LINGO-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107331 ]

Jason Koch commented on LINGO-44:
---------------------------------

Blog entry related to this: http://bluedevel.com/blog/?p=3

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

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

From forum: lingo - dev