This isn't a spring jms issue or resolution... but since I asked the question... I might as well respond to it... since I found a solution.
i opened a PMR with IBM and this was their solution......
Type: Posts; User: hasdy; Keyword(s):
This isn't a spring jms issue or resolution... but since I asked the question... I might as well respond to it... since I found a solution.
i opened a PMR with IBM and this was their solution......
I've created a Message Driven Pojo and I've been able to send a message using the JMSTemplate and standard Sun JMS API.
I've now been attempting to create a WebSphere Scheduler task and the...
Reading through some forums and such.... I have come up with the following config for my jms connection factory...
<bean id="internalJmsQueueConnectionFactory"...
WebSphere 6.1.x
ActiveMQ
Spring JMS
I am attempting to send a message to an application with the following code...
Context ctx = new InitialContext();
ConnectionFactory cf1 =...
I suppose the problem is that WebSphere scheduler needs a valid JNDI to set in the destinationJNDIName.
So I guess I have to set up the jndi template in my configs.
I've taken a look at the...
New to JMS and websphere scheduling.....
I've set up my Spring JMS much like how Mark did in this tutorial.
http://www.springframework.org/node/527
<bean id="jmsConnectionFactory"...
Thanks for the reply ulsa.
I've added log4j to my project (properties and jar file). I've also added PropertyConfigurator.configure(properties) to a servlet init method.
But I'm still not...
thanks for the response:
I haven't actually set any system properties for the jvm ldap pooling.
and perhaps I'm being dense, but how do i go about turning up logging to DEBUG for that package? ...
Well, I've had reports that the application failed and the only exceptions in the log during the time frame are these Validation exceptions. I suppose it could be something else, but at this point,...
Here's the scenario:
Under my current configuration everything seems to work fine.... then the following validation exception occurs. It keeps on throwing it for a bit.... then after awhile (few...
thanks for the reply guys...
rasky, you're right, I would prefer to do a password comparison but from reading various forums, ...
With the recent addition of the pooling support in spring ldap, I was wondering if there are any plans to incorporate it with Spring Security.
Or can it already be done?
Specifically I'd like...
Thanks for your reply.....
before I read your response, I turned on testOnBorrow and it looks as though it fixed our problem.
I haven't made the other configuration changes (ie...
so would that mean I'd turn on the testOnBorrow validation config?
Thanks
Here are my ldap configs
<bean id="contextSource" class="org.springframework.ldap.pool.factory.PoolingContextSource">
<property name="contextSource" ref="contextSourceTarget"/>...
Hi,
I'm getting a similar exception
Caused by: org.springframework.ldap.CommunicationException: connection closed; nested exception is javax.naming.CommunicationException: connection closed...
I've made the configuration changes according to the documentation.
But is there something else I have to do in the code to release the connections?
Or do I just let the PoolContextSource and...
I have a requirement to search by phone number.
The format of the number in ldap is 123-123-9876.
the format of the search parameter is 2 to 10 digits (ie 12 and 1231239876).
I currently have...
Oddly enough, I wasn't using a transaction manager for my LDAP transactions. I've stepped through the transaction and it appears that you were correct in that it is probably the underlying Java LDAP...
I notice there is a ModifyAttributesOperationExecutor that calls a rollback.... does this play into the equation at some point?
Strange problem indeed....
Same JVM and the only access permission is based on the application user... which is the same for both my local and dev environment.
So I have another question ......
Hi,
Is there is a built in tracing mechanism is spring ldap? If so, how do I enable it?
Thanks
thanks for your reply...to clarify....
I am doing an update on a user....with the code mentioned previously.
And this user has a number of attributes..... phone, fax, title, manager.....etc.
...
Further findings:
So I threw a packet sniffer on the server.....
And it seems as though it does a modifyRequest with the new value of an attribute....
then it throws another modifyRequest with...
I've also tried using
DirContextOperations ctx = (DirContextOperations) ldapTemplate.lookupContext(dn);
ctx = setAttributes(ctx, user);
ldapTemplate.modifyAttributes(ctx);
Still no go.