websphere-7

问题 I normally handle site logout with a JSP that executes <%= session.invalidate() %> then redirects to the home page. Now I am running on WebSphere authenticating using LTPA and a SSL Certificate. Session.invalidate() does not work. Someone suggested it is because WAS is using LTPA. LTPA creates an authentication cookie (LtpaToken2) that is not cleared by session.invalidate. IBM does have a proprietary logout JSP*** I could use, but I don't want to use a vendor specific solution. Has anybody

问题 Facing issue in deploying JBPM 5.4 console server war to use oracle database. Please find below the stacktrace. [10/31/13 19:17:01:295 IST] 00000009 JPAPUnitInfo E CWWJP0015E: An error occurred in the org.hibernate.ejb.HibernatePersistence persistence provider when it attempted to create the container entity manager factory for the org.jbpm.persistence.jpa persistence unit. The following error occurred: [PersistenceUnit: org.jbpm.persistence.jpa] Unable to build EntityManagerFactory [10/31/13

问题 I'm unable to connect remotely from WebSphere Application Server with Queue Manager at WebSphere MQ. Anyhow it get connected to Queue Manager from WAS that is installed on same machine. I'm using version 7.5 of WebSphere MQ and version 7.0 of WebSphere Application Server. While attempting to connect WAS remotely to Queue Manager following error messages were logged. Error Message from WebSphere MQ: 1/30/2013 21:12:09 - Process(3624.6) User(MUSR_MQADMIN) Program(amqrmppa.exe) Host(KHILT-269)

问题 I'm unable to connect remotely from WebSphere Application Server with Queue Manager at WebSphere MQ. Anyhow it get connected to Queue Manager from WAS that is installed on same machine. I'm using version 7.5 of WebSphere MQ and version 7.0 of WebSphere Application Server. While attempting to connect WAS remotely to Queue Manager following error messages were logged. Error Message from WebSphere MQ: 1/30/2013 21:12:09 - Process(3624.6) User(MUSR_MQADMIN) Program(amqrmppa.exe) Host(KHILT-269)

问题 The JAXWS implementation within IBM WebSphere 7 and 8 appears to have some problems when it comes to soap handlers and large MTOM attachments. It appears that the entire message, including all attachment binary content, is read into memory when getMessage() is invoked on the SOAPMessageContext object. This can very easily cause the JVM to run out of available memory. @Override public boolean handleMessage(SOAPMessageContext context) { SOAPMessage soapMsg = context.getMessage(); ... } In the

问题 I have two Integer columns in the database (derby and db2). I need to divide them with each other inside a JPQL . Both columns being of type Integer return zero if remainder is a decimal number e.g 0.25 becomes 0 etc and understandably so since type is int. In SQL I could have this for example select CAST(column1 as decimal(6,2))/CAST(column2 as decimal(6,2))from Sometable; but what is JPQL equivalent . One option might be (I have not tried yet) is to have a @Transient method in the entity

问题 I have upgraded my application to Websphere 7.0 from Websphere 6.1. I am using Microsoft SQL server jdbc driver 4.0 for this application. When i use sqljdbc4.jar i get the following error when connecting to database for authentication. SystemError java.sql.SQLException: SQL Server version 8 is not supported by this driver. SQL State = 08S01, Error Code = 0 How to get rid of this. 回答1: Yes, as per the Microsoft SQL Server JDBC type 4.0 driver system requirements page: The JDBC driver supports

问题 Suppose we have a MBean that has the following attributes and operations. Attributes: name size Operations: getName() getSize() Is there a way to programmatically check for the attributes and operations? I've been working with the IBM WebSphere MBeans and their documentation isn't very good. For example, if you go to IBMs Infocenter and navigate to Network Deployment -> Reference -> Programming interfaces -> Mbean interfaces -> ThreadPool. They only have attributes listed and no operations.

问题 In the Administration COnsole of WAS 7, on the Applications > Application Types > WebSphere enterprise applications > application > EJB JNDI names section, I have a table with four columns : EJB Module (e.g. ProjectEJB.jar) EJB (e.g. BeanBO ) URI (e.g. ProjectEJB.jar, META-INF/ejb-jar.xml Target resource JNDI Name (with empty fields) Something like this : What's the jndi name of my LogWriter bean ? 回答1: Below you have table with default names. Each bean gets short and long form. You can

问题 So I'm dealing with a legacy servlet code that runs on Websphere 7 (JDK 6). Development environment setup uses Tomcat 6 (JDK 6). Why does it work on Websphere 7 and not in Tomcat 6? Is this something related to the application server? If your answer is yes for no. 2, do you have a workaround for this on Tomcat 6 (JDK 6) aside from breaking down the code or using dynamic includes? The schedule does not agree with changing static includes to dynamic includes primarily because most pages are