I guess it's because of the firewall in Vista. You can try it again after
turning off the firewall in Vista.
Hope it helps.
-- Yun Feng
Olakara wrote:
Hi,
I am trying to start the server on a Vista Home OS. I get the following
error:
Using GERONIMO_BASE: C:\Program Files\geronimo
I'm not sure exactly what you are trying to do but have you looked at
http://cwiki.apache.org/GMOxDOC21/configuring-application-specific-logging-with-log4j.html
to see if it would help?
thanks
david jencks
Alas, I'm using geronimo 2.0.2...
I don't feel I'm trying to do something special. I'm
There's also this:
IOException occurred while saving
attributes
java.io.IOException: Unable to rename C:\Program
Files\geronimo\var\config\config.xml to C:\Program
Files\geronimo\var\config\config.xml.bak in order to back up manageable
attribute save file
I'm guessing you have an access issue in
hello,
i have a question regarding MDBS in Geronimo 2.1.1
i bombard the server with a high amount of mdb requests, the mdbs write
tuples to a database. so although my database connection pool maximum is 20
i realize that with mdbs the pool is just utilized with 10 connections to
the database,
Are you using the default ActiveMQ RA (DefaultActiveMQConnectionFactory) to
send the JMS message? DefaultActiveMQConnectionFactory configures a single-pool
with default max-size 10. I'm not sure whether this can explain what you saw in
your scenario, but I think you can try to create a new
actually i deployed a geronimo-application.xml deployment plan,
defining the connection factory:
ext-module
connectorjms-resources/connector
external-path
xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2;
dep:groupIdorg.apache.geronimo.modules/dep:groupId
my connection factory is successfully deployed on the server and the
queue is using it as far as i can say. nevertheless, not more than 10
connections are made to the database.
does the connection factory pool size always have to be the amount of
data source connections? i already tried with 20
I think there's a setting for the mdb pool size in the activation
spec. Also it looks like the DefaultWorkManager only has 30 threads
which is pretty low but I don't see offhand how this would result in
only 10 worker threads.
thanks
david jencks
On Jul 16, 2008, at 3:38 AM, Mario Kofler
Good evening,
I've got two managed beans in a JSF 1.2 webapp. Both beans are quite
equal. I try to inject a stateless session bean (EJB3) into the managed
beans.
@EJB(name = java:comp/env/ejb/CredentialData)
private CredentialData credentialData;
In the first managed bean the EJB is injected
Kevan,
Your assumption is correct. I've moved the jms connector into my ear
deployment plan as you suggested. JMS is now happy.
I'll see if I can mock up some artifacts for you.
In the meantime, here is what I had before with jms connector as a separate
module hopefully will help you
I'm not sure why this happened, but it will be easer to debug if you can attach
your sample. :-)
-- Yun Feng
Matthias Berndt wrote:
Good evening,
I've got two managed beans in a JSF 1.2 webapp. Both beans are quite
equal. I try to inject a stateless session bean (EJB3) into the managed
11 matches
Mail list logo
