websphere-8

I have a JSF application that uses Mojarra 2.2.9 and is deployed on WebSphere 8.5.5.4 on clustered environement and javax.faces.STATE_SAVING_METHOD is set to client . Even though all my application beans are request scoped, sometimes when the user session is valid and the user is doing post request on a page he gets ViewExpiredException . What may be causing this issue and how can I solve it? Will changing the javax.faces.STATE_SAVING_METHOD to server solve it? If so, what is the impact of doing this on memory? Also, does this have anything to do with cluster environement and maybe there's

I am using Jersey 2 to implement JAR-RS 2.0 in an IBM WebSphere 8.5 environment. After reading this post JAX-RS Jersey 2.10 support in Websphere 8 I managed to get this working. However, is it possible to bundle the JAX-RS Jars within the WAR and deploy the application without the need to create an isolated shared library? If this is not possible, can someone please explain why this is the case? I understand the deployment time advantage of having the Jars in a library, but I would prefer to build the entire application including dependencies into a single WAR. -- EDIT -- It appears that you

Been trying to get jax-ws web service working in websphere 8.5 but no success. I have tried Java bean & war packaging, stateless ejb & jar packaging but it just does not work. I am trying to get it work with @webservice annotation. I am not generating any extra artifacts. I am letting websphere figure out during the deployment. During deployment there is no error. After deployment, I try to run wsdl in the browser to see if web service is installed successfully but I get nothing. Not sure if I am doing something wrong during the deployment or something else. Let me know if you want more info.

I have JAX-RS WS application deployed on WAS 8.0 with an empty 2.4 web.xml, class that extends 'javax.ws.rs.core.Application' and 2 resources, and it works great. I would like to deploy this application on WAS 7.0, but I'm getting: 'Error 404: SRVE0190E: File not found: /rest/source' (that's the path of the resource). How can I deploy JAX-RS application on WAS 7.0 without using Jersey or any other application-server related classes? Thanks In WAS 7 you must defined the servlet in the web.xml: <servlet> <description>JAX-RS Tools Generated - Do not modify</description> <servlet-name>JAX-RS

I'm getting the following error when trying to deploy an ear with websphere from an ant ask with jacl: [wsadmin] WASX7017E: Exception received while running file "C:\...\AppData\Local\Temp\wsant6857788060872488512jacl"; exception information: com.ibm.websphere.management.application.client.AppDeploymentException: com.ibm.websphere.management.application.client.AppDeploymentException: [Root exception is org.eclipse.jst.j2ee.commonarchivecore.internal.exception.DeploymentDescriptorLoadException: WEB-INF/web.xml] When I try to deploy the ear from the websphere console I get: The following

We deploy a web app on WAS 8.5.0.0, we're using PARENT_LAST class loader(we have to for some reason), during the startup, there're some warnings: [12/16/14 17:19:15:088 CST] 00000048 InjectionProc E CWNEN0044E: A resource reference binding could not be found for the com.sun.xml.ws.transport.tcp.servicechannel.ServiceChannelWSImpl/wsContext resource reference, defined for the MyProjectName component. [12/16/14 17:19:15:089 CST] 00000048 InjectionProc E CWNEN0044E: A resource reference binding could not be found for the com.sun.xml.ws.tx.webservice.member.coord.RegistrationRequesterPortTypeImpl

When I start the application in websphere 8.5.5 I got an error, and the application failed to start, I searched the log and got this stack trace . Do you guys have any idea ? [8/21/14 17:58:57:437 EEST] 00000001 ContainerHelp E WSVR0501E: Error creating component com.ibm.ws.runtime.component.CompositionUnitMgrImpl@a0ccb3b2 com.ibm.ws.exception.RuntimeWarning: com.ibm.ws.webcontainer.exception.WebAppNotLoadedException: Failed to load webapp: Failed to load webapp: java.lang.LinkageError: javax/servlet/jsp/JspApplicationContext.addELResolver&#40;Ljavax/el/ELResolver&#59;&#41;V at com.ibm.ws

I need to process about 250.000 documents per day with an EJB 3.1 asynchronous method in order to face an overall long time task. I do this to use more threads and process more documents concurrently. Here's an example in pseudo code: // this returns about 250.000 documents per day List<Document> documentList = Persistence.listDocumentsToProcess(); for(Document currentDocument: documentList){ //this is the asynchronous call ejbInstance.processAsynchronously(currentDocument); } Suppose I have a thread pool of size 10 and 4 core processors, my questions are: how many documents will the