Kevan Miller wrote:
On Sep 11, 2007, at 4:13 PM, David Blevins wrote:
The exception you should have gotten was:
- - - - - - - -
Jar Failed validaton: pprsrv-ejb-1.2.jar
FAIL - YourBeanName - Invalid PostConstruct arguments:
construct(InvocationContext)
- - - - - - - -
Just added this
It works for me on trunk, both changing from the admin console and
editing var/security/users.properties. Can you provide more details
about exactly what you did? No matter what you did to the security
realm it is not going to affect geronimo startup: the properties
files aren't read
Hi,
I have connected to websphere mq 6.0 (local) from servicemix deployed on
Geronimo 1.1.1 . There are no issues in that. But the moment I am trying to
connect to the websphere mq on the network, I am not able to do that, it is
throwing an error.
javax.jms.JMSException: MQJMS2005: failed
Hi, I cannot recreate this either. Changing password from either
console or users.properties file works for me too. I saw some JIRA
related to starting server in Eclipse... Are you doing the start inside
of Eclipse?
Lin
yjz wrote:
There are two ways to change user's password from
Hi,
I am using JOSSO to supply the single sing-on capability. But, JOSSO only
support Tomcat and JBoss. As Geronimo is built on top of Tomcat, I think I
can config the JOSSO agent in Geronimo 1.1.1 which is similar to Tomcat.
Unfortunately, I found that the Geronimo 1.1.1 configuration is very
Ok, so first off I want to apologize if this is kind of a newbie question,
but we are making the migration from Tomcat to Geronimo, and I am having a
hard time moving some of our application's logging. We have written a
custom log4j appender that utilizes both our custom jar, and 3x 3rd party
Hi,
The scenario is more like this.
I am having the j2ee application client on Geronimo 1.1.1 server, which needs
to talk to the websphere mq sitting on other machine. The websphere mq ip needs
to be somewhere mentioned/defined in the j2ee application client container.
There are similar issues
