Hi,
I am using TomEE to host high loaded app and at some point found with
VisualVM there is a bottleneck when there is a lot of concurrent requests
(about 400-600 req/sec) - almost all CPU time is occupied by
TaskQueue.poll() calls and general response latency becomes very slow.
I tried APR/Nio c
Any comments on this? Issue is easily reproduced when posting jms message.
--
View this message in context:
http://openejb.979440.n4.nabble.com/ActiveMQ-1-5-1-issue-with-an-ActiveMQ-embedded-broker-tp4658482p4658557.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Hi,
Seems that there is an issue on latest TomEE 1.5.1-SNAPSHOT when using
ActiveMQ embedded broker.
However on 1.5 everything is perfect.
When posting to a topic, message reaches the destination, but container
throws following exception:
Exception in thread "ActiveMQ VMTransport: vm://localhost
Thanks for the support.
I tried TomEE 1.5-SNAPSHOT with Tomcat pool and faced the same behavior.
It's remarkable that JDBC 3/4 drivers behave a bit differently. While JDBC4
was hanging after connection pool exceeded, with JDBC3 I received exceptions
on DBCP that connection can't be leased from poo
Basically Postgres is not used much - we use Membase to cache everything in
RAM but few operations are still DB dependant. Usually there are about 50-70
connections active according to what Postgres says.
--
View this message in context:
http://openejb.979440.n4.nabble.com/tomee-xml-configurati
Hm.
Here is DataSource configuration in TomEE
JdbcDriver = org.postgresql.Driver
JdbcUrl = jdbc:postgresql://localhost:5432/datasource
UserName = user
Password = password
InitialSize = 20
MaxActive = 200
ValidationQuery = SELECT 1
JtaManaged = true
Here is datasource retirieva
Here is my stateless container configuration
AccessTimeout = 5 seconds
MaxSize = 100
MinSize = 1
StrictPooling = false
MaxAge = 0 hours
IdleTimeout = 0 minutes
--
View this message in context:
http://openejb.979440.n4.nabble.com/tomee-xml-configuration-for-high-load-tp4657577p465
Hello,
I have a question on tomee.xml configuration for highly loaded system.
In my application all business logic is implemented in stateless EJB
components. When load starts to grow, particular components stop responding
to client requests, however others do fine and container continues working
We also used manual specification port and other options, however found that
if we specify as you did - "JAVA_OPTS="-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8787" " we have
some strange Tomcat crashes on shutdown.
We found that adding "jpda" startup option works much better
Hello,
What code hot swap/deploy capabilities are available in OpenEJB/TomEE?
I am interested in a scenario where I point TomEE to exploded EAR folder
where EJB class files are updated by IDE or whatever and dynamically hot
swapped into container.
There are 3rd party plugins like JRebel, but it
After a lot of investigation I've found a problem here on forum. I was using
TomEE v1.0 with ActiveMQ client jar v5.5.1 which has some bug or whatever.
Everything works smoothly with latest Tomee v1.1 build.
There are no exceptions, however I am periodically checking logs for any
kind of related pr
I have added more logging and found that container occasionally issues
following Exception when it sends JMS message.
What the problem might be? I am creating connection in @PostConstruct method
and then reusing it when posting messages (Session/Producers are created per
send operations and not sha
We thought of network issue as well but it also reproduces in the case when
TomEE and ActiveMQ are on the same host.
For us it also seems like a kind of hibernation, when 1-st message awakes
some hibernated component and then it becomes alive again but first message
gets lost.
--
View this mess
Not exactly.
System is running all the time. When users are doing some particular actions
we use to send JMS messages and everything works fine in 99.9% of cases.
After off hours (absolutely no activity at all for about 4-6 hours from the
users) where the are no requests and hence JMS invocati
Hello,
I am facing a strange behavior with MDB's that are listening on topics.
After long application inactive time (in other words - system is not used
overnight (3-4 hours)) first JMS message send to the topic NEVER reaches
destination (I have couple of MDBs listening on the topic and neither of
Thanks for pointing to that jira entry. Adding ?daemon=true to the uri fixed
the problem.
Now TomEE stops fine without need to stop ActiveMQ first. Also during
deploy/redeploy process there are no issues with jsp and servlets which was
the case in 1.0.0 version.
Thanks a lot for the support!
Rega
I sent it my previous post (Jul 26, 2012; 12:02pm) with a link - looks like
system rejected it.
Dump could be found here - http:// sharetext.org /EPGC (without spaces)
--
View this message in context:
http://openejb.979440.n4.nabble.com/DuplicateDeploymentIdException-when-deploying-ear-with-app
Is there any news on this? Should I have to sent more related info?
Thanks.
--
View this message in context:
http://openejb.979440.n4.nabble.com/DuplicateDeploymentIdException-when-deploying-ear-with-application-xml-tp4655362p4656621.html
Sent from the OpenEJB User mailing list archive at Nabb
1. Not sure I understood what do you mean. But we can't run ActiveMQ under
TomEE, we are running separate ActiveMQ cluster
2. Upgrade of ActiveMQ to 5.6.0 haven't helped. Same hang occurs on
application undeploy/TomEE shutdown
--
View this message in context:
http://openejb.979440.n4.nabble.com
I was keep trying to figure out why TomEE hangs on undeploy/shutdown for me
(and that doesnt happen for you) and looks like I have found the reason.
When I have active MDBs listening on queues/topics TomEE doesn't stop until
ActiveMQ is shut down.
Here is a test application where there are either
I did use folder name when wrote you previous message instead of ear name but
it didn't work as described.
Using relative path being outside of the $TOMEE_HOME doesn't work as well -
it can't find deployed application:
$TOMEE_HOME/bin/tomee.sh undeploy apps/BMM-0.0.2-SNAPSHOT
undeploying apps/B
Thanks, that worked great.
--
View this message in context:
http://openejb.979440.n4.nabble.com/OpenEJB-remote-ejbd-provider-in-TomEE-tp4655799p4655866.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Sorry for not responding for quite long time on this.
Yes, you are right, you need to use tomee.sh for that to reproduce the
issue.
Exact steps are:
1. Deploy application
MBP-Almos:testear2 tomee.sh deploy /tmp/eartest-0.0.1-SNAPSHOT.ear
2. Check jsp page/servlet
MBP-Almos:testear2 wget http:
Hi,
I need to expose my EJB beans for the remote calls. What's the best way of
doing that?
What I've been doing I tried adding ejbd.properties to $TOMEE_HOME/conf.d/
server = org.apache.openejb.server.ejbd.EjbServer
bind= 127.0.0.1
port= 4201
threads = 200
disabled = fal
Just discovered one more issue though ;).
I have an EAR which is periodically gets deployed to TomEE from Jenkins.
EAR consists WAR with JSP/Servlets and JAR with EJB components. First deploy
goes always fine but after that issues start to appear.
Here is a steps for reproduction for a problems
Yes, latest code on trunk works fine in the mentioned regards. Thanks.
Is arquillian-tomee-remote it expected to appear on maven repositories? If
yes which ones as it's not very handy to keep local custom built stuff.
--
View this message in context:
http://openejb.979440.n4.nabble.com/Arquillia
Also playing with arquillian.xml options gave following results:
after I specified appWorkingDir there I got DuplicateDeploymentIdException
however there were no applications deployed that contain same EJB
identifiers:
/Volumes/Work/java/tomee-remote/apps
14.06.2012 11:17:26 org.apache.catalina.
Thanks, that worked fine.
--
View this message in context:
http://openejb.979440.n4.nabble.com/DuplicateDeploymentIdException-when-deploying-ear-with-application-xml-tp4655362p4655604.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Hi,
I tried to use arquillian remote adapter to test my application but it
fails.
Frankly speaking embedded fails as well but now I need to have remote
working
Here is exception on "mvn test"
INFO:
RemoteInitialContextCreated{providerUri=http://localhost:8080/tomee/ejb}
org.apache.openejb.NoSuc
Hi,
Since I moved my EAR to apps/ folder everything was working great except hot
deployment in that folder.
I tried to:
1. simple EAR overwriting
2. using deploy tool bin/tomee.sh
3. googling a lot on some configuration options to add to the
conf/tomee.conf
Neither have given any satisfactory res
Thanks for the support. Moving EAR to apps/ helped - everything works great
and no exceptions are thrown.
--
View this message in context:
http://openejb.979440.n4.nabble.com/DuplicateDeploymentIdException-when-deploying-ear-with-application-xml-tp4655362p4655434.html
Sent from the OpenEJB User m
Hi,
Thanks for your response.
I've prepared test package with maven build script.
Link to download: http://www.4shared.com/zip/TGDORA0u/testear.html
To package ear firstly setup environment variable DEPLOY_PATH where ear will
be created and then run "mvn package".
It fails on Tomee 1.0 with the
Hello,
I am facing strange following problem when using application.xml in my EAR
file.
1. I am using maven to build EAR which contains JAR with EJB components and
one web application WAR
2. Maven automatically creates application.xml in the META-INF of my EAR
3. When deploying EAR on TomEE+ 1.0
33 matches
Mail list logo
