Very strange - also the exception with the backstore. For me it looks
like a version mismatch between client and router. Could you check this,
please?
If you have done that and you are absolutely sure you use the same
version for both and you get the exception(s) again, please send me:
- which OS you use
- which SwiftMQ version you use (SwiftMQ Explorer/About)
- the error.log of the router
Jerold Paulson wrote:
>
> I have encountered two behaviours that are problematic, at least one of them
> seems like it's a bug [unless it's a 'JMS feature' I haven't come across
> before...]
> ============================================================================
> 1.
> --------------
> I hae a client that reads from a PTP queue using a message selector that is
> having a problem. (I have another client that is sending messages to that
> queue that continues to work fine).
> It had been working fine for about a day, and all of a sudden, without a
> recompile, it started getting an exception during the call to
> InitialContext.
> java.lang.VerifyError: com.swiftmq.auth.ChallengeResponseFactoryImpl
>
> This is occurring in swiftmq 1.1 AND 1.2 .
>
> This error occurs whether authentication is checked off in Navigator OR NOT.
> I've tried re-booting the SwiftMQ server and the hardware it runs on,
> without effect.
>
> Now I can't get a JNDI context from this client no matter what I try. I'm
> calling the internal JNDI implementation, not an external one.
>
> if (jndiContext == null) {
> try {
> Hashtable env = new Hashtable();
>
> env.put(Context.INITIAL_CONTEXT_FACTORY,"com.swiftmq.jndi.InitialContextFact
> oryImpl");
>
> env.put(Context.PROVIDER_URL,"smqp://username:password@queuemanageripaddress
> :4001/timeout=10000");
> jndiContext = new InitialContext(env);
> } catch (NamingException e) {
> System.err.println("Could not create JNDI context: " +e.toString());
> throw e;
> } catch (VerifyError e) {
> System.err.println("There is a Verify Error: "+e.toString());
> throw e;
> }
> return ;
> }
>
> NOTHING shows up in the JNDI trace file.
>
> Same behaviour regardless of whether I use localhost (where the queue
> manager currently resides), the queue manager's address, or 127.0.0.1 for
> the queuemanager address.
> Same behaviour occurs even when I activate authentication and pass an
> invalid password! [So the error may be occuring in the InitialContext
> method even before password checking (?)]
>
> By the way, the client that's still working, sending messages to the same
> queue, uses the same code to lookup the jndi context and returns from the
> InitialContext(env) call without error. I get an invalid password error in
> this client when I activate authentication and pass an invalid password.
> ============================================================================
> 2.
> --------------------------------------------
> When I change the username to humptydumpty (an undefined user), I get the
> following exception:
>
> javax.naming.NamingException: unable to connect, exception =
> javax.jms.JMSSecurityException: unknown user: humptydumpty
>
> This happens even when authentication is turned off! This seems like a bug.
> ============================================================================
>
> Suggestions, anyone?
>
> Thanks in advance,
> Jerold Paulson
>
> ------------------------------------------------------
> SwiftMQ developers mailing list * http://www.swiftmq.com
> To unsubscribe from this list, send an eMail to
> [EMAIL PROTECTED] and write in the body of your message:
> UNSUBSCRIBE developers <your-email-address>
> Archive: http://www.mail-archive.com/developers@mail.iit.de/
--
Andreas Mueller, [EMAIL PROTECTED], IIT GmbH, Bremen/Germany, http://www.iit.de
SwiftMQ - JMS Enterprise Messaging System, http://www.swiftmq.com
------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/developers@mail.iit.de/
