Re: singleton initializing twice? (1.6.0-stable)

got it but knowing 1.7.2 has the same issue helps to identify if we need to solve an unidentified issue or a fixed issue with potentially a workwround. Romain Manni-Bucau @rmannibucau | Blog | Github

Embedded broker is not connecting full duplex to external broker

Hey guys, I have the following embedded broker configuration: BrokerXmlConfig = broker:(vm://tomee1,network:static:(tcp://external-activemq-instance:61616)?duplex=true)?persistent=truebrokerName=tomee1 ServerUrl = vm://tomee1 datasource = When I look on the console for

Re: singleton initializing twice? (1.6.0-stable)

Hi Leo, can you quickly check it on 1.7.2 before digging into 1.6.0 bugs? I know we enhanced a bit this area (singleton) so can be fixed. Romain Manni-Bucau @rmannibucau | Blog | Github |

Re: singleton initializing twice? (1.6.0-stable)

I am sorry, 1.6.0 is in production here. :-( [] Leo On Mon, Sep 28, 2015 at 4:38 PM, Romain Manni-Bucau wrote: > Hi Leo, > > can you quickly check it on 1.7.2 before digging into 1.6.0 bugs? I know we > enhanced a bit this area (singleton) so can be fixed. > > >

singleton initializing twice? (1.6.0-stable)

Hi I have a singleton that initialized my own scheduler. Please don't ask me why do I need another schedule, since TomEE already provides one by default. Actually, I need this because since the JavaEE spec is not clear about how the timers must be hadled when they're persistent, I had to do

Re: singleton initializing twice? (1.6.0-stable)

On Mon, Sep 28, 2015 at 3:55 PM, Romain Manni-Bucau wrote: > got it but knowing 1.7.2 has the same issue helps to identify if we need to > solve an unidentified issue or a fixed issue with potentially a workwround. > > hmmm, i've been using tomee 1.7.2 (in production) ever

Re: Connect to external (non ActiveMQ) JMS server

It almost works. I had to specify ProviderIntegrationMode = jndi in the Resource block like this because broker url in the connection properties is ignored (and it always tries to connect to localhost) UserName = brCentral Password = brCentral ProviderIntegrationMode =

Re: Embedded broker is not connecting full duplex to external broker

DiscoveryNetworkConnector has it but it is not set properly by AMQ factory Romain Manni-Bucau @rmannibucau | Blog | Github | LinkedIn | Tomitriber

Re: Embedded broker is not connecting full duplex to external broker

Hmm... does *anyone* have this working? We can't get messages to flow at all between the embedded broker and the "normal" external broker. Trying to find a workaround, I was looking through

Re: singleton initializing twice? (1.6.0-stable)

My apologies, I did not see that behavior. On Mon, Sep 28, 2015 at 4:15 PM, Howard W. Smith, Jr. < smithh032...@gmail.com> wrote: > > > On Mon, Sep 28, 2015 at 3:55 PM, Romain Manni-Bucau > wrote: > >> got it but knowing 1.7.2 has the same issue helps to identify if we

BoxFuse

Hi mates, I have been working with Axel Fontaine for the support of Apache TomEE in BoxFuse. You can read more here: https://boxfuse.com/docs/payloads/tomee.html I think it could be interesting to add this on TomEE page so users know the existence of this technology but also that it Apache TomEE

Re: Scaling MDBs beyond default 10 limit

How would you configure NIO for MDB? I do plan on stress testing, but I want to make sure I understand the configuration. Is there a 1 to 1 relationship with Default\ JMS\ Resource\ Adapter.ThreadPoolSize and Default\ MDB\ Container.InstanceLimit? On Mon, Sep 28, 2015 at 10:29 AM, Romain

Re: Scaling MDBs beyond default 10 limit

OK, yea, it's not real clear where configuration preference go (i.e. system.properties or tomee.xml). My goal is to have 100 messages processing simultaneously for each MDB. I could have 5 or 10 distinct beans that need to handle up to 100 messages each simultaneously. In case of 10 beans with 100

Re: ClassNotFoundException for my servlet class?

I finally got some linux boxes set up for testing, so I am not using cygwin anymore, and I still get the same exception. Class is defined like this: package com.comcast.dollee.ws; ... @WebService public class Dollee { I am trying to convert this application from WebLogic (where it runs fine)

Re: Scaling MDBs beyond default 10 limit

Le 28 sept. 2015 07:24, "Steve Goldsmith" a écrit : > > OK, yea, it's not real clear where configuration preference go (i.e. > system.properties or tomee.xml). My goal is to have 100 messages processing > simultaneously for each MDB. I could have 5 or 10 distinct beans that need

Re: Scaling MDBs beyond default 10 limit

Le 28 sept. 2015 07:36, "Steve Goldsmith" a écrit : > > How would you configure NIO for MDB? I do plan on stress testing, but I > want to make sure I understand the configuration. Is there a 1 to 1 > relationship with Default\ JMS\ Resource\ Adapter.ThreadPoolSize and > Default\

Re: Connect to external (non ActiveMQ) JMS server

Figured out the how to use ConnectionFactoryProperties (capital first letter for property name and no spaces), so no jndi is requitred: ConnectionFactoryProperties = ConnectionURLs=tcp://dev.test:10400,DefaultUser=user1,DefaultPassword=passw1 Can send messages now, trying to set up MDB in

Re: Embedded broker is not connecting full duplex to external broker

seems duplex is ignored on SimpleDiscoveryAgent and not set on DiscoveryNetworkConnector with AMQ default factory. see org.apache.activemq.transport.discovery.simple.SimpleDiscoveryAgentFactory#doCreateDiscoveryAgent probably something to ask amq guys Romain Manni-Bucau @rmannibucau

Re: Connect to external (non ActiveMQ) JMS server

can you check the logs about MySonicAdapter and ResourceAdapter (Default JMS Resource Adapter)? You should see which one is used in the logs normally Romain Manni-Bucau @rmannibucau | Blog | Github

Re: org.apache.openejb.client.Client.processRequest swallows IOException

Thank you. -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/org-apache-openejb-client-Client-processRequest-swallows-IOException-tp4672072p4676341.html Sent from the TomEE Users mailing list archive at Nabble.com.