![]() ![]() The Glassfish-MQ JMS bridge is done with GENERICJMSRA as the Oracle documentation describes it. The JSSE layer in Glassfish seems to be initialized properly, as other functions of the program use the keys in it. tIntProperty(WMQConstants.JMS_IBM_CHARACTER_SET, 1208) MessageProducer producer = session.createProducer(outQueue) īytesMessage outMessage = session.createBytesMessage() Queue outQueue = (Queue)ctx.lookup(“OUTQ") Session = connection.createSession(transacted, Session.SESSION_TRANSACTED) tProperty( "", "changeit") Ĭonnection connection = factory.createConnection() MQQueueConnectionFactory factory = (MQQueueConnectionFactory)ctx.lookup(“QMGR_T2") environment = new () Įnvironment.put(Context.PROVIDER_URL, url) Įnvironment.put(Context.INITIAL_CONTEXT_FACTORY, icf) Ĭontext ctx = new InitialDirContext(environment) ![]() String url = "file:/C:/Users/u200089/Tools/bindings/QMGR_T2" bindings file, and it is able to connect to the qm perfectly. To prove it, I wrote a simple program (skipping the Glassfish app server) that uses the key/trust stores of the glassfish-program, uses the same. However, I believe that I have correct trust/keystores and channel/bindings file definitions. When we want to securize the channel, we are not able to get a working connection. It can connect to a qmgr with a non-ssl client channel, and operates well. We have an application in Glassfish which uses JMS messaging. We've been trying to solve a connection problem. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |