WebSphere Application Server: Invitation to Participate in IBM Log Analytics Open Beta Program
Author: dmcclure Message: The IBM Log Analytics (https://www.ibm.com/developerworks/servicemanagement/bsm/log/index.html) product team is pleased to announce the start of the open beta program for the new IBM Log Analytics (https://www.ibm.com/developerworks/servicemanagement/bsm/log/index.html) product to be released later this year. This is the first ever open beta for the IBM Log Analytics offering and we're looking for broad participation from application developers, support engineers and WebSphere subject matter experts like those participating in this forum. We hope to leverage your expertise and experience during this open beta to both provide you an early look into the capabilities while also offering you the opportunity to provide feedback on product capabilities and features, our WebSphere Insight Pack as well as ask questions which will help us further refine the product and our direction to suit the needs of the WebSphere community. When problems are reported with applications running on WebSphere Application Server, most often we hear about an SME's need to look at SystemOut, SystemError and trace log files as starting points for problem validation, isolation and resolution. As you are very aware, manual analysis of gigabytes worth of WebSphere logs plus system, network, storage and other logs is laborious and time consuming. IBM Log Analytics (https://www.ibm.com/developerworks/servicemanagement/bsm/log/index.html) can help WebSphere SMEs to iteratively drill down and search through massive amount of logs files to quickly find the root cause of the problems. IBM Log Analytics (https://www.ibm.com/developerworks/servicemanagement/bsm/log/index.html) is designed to index, search and analyse application, middleware and infrastructure data generated by your systems, middleware and business applications. While support for all log sources and types will be provided, the solution will feature in depth, prepackaged domain insights into Websphere and DB2 log sources, further accelerating value for application developers, application support and middleware subject matter experts. The first milestone driver available today includes the following highlights: * Advanced search and text analytics technology from IBM's Big Data platform - Big Insights * Intuitive user interface and design enabling easy free form search and directed search interactions * Search logs using configured and discovered patterns such as stack traces, class/thread IDs and error codes to quickly identify and repair issues * Quickly visualize application error type distribution across thousands of log records * Fast installation, typically installs in less than 10 minutes We challenge you to present us with creative scenarios and use cases where IBM Log Analytics (https://www.ibm.com/developerworks/servicemanagement/bsm/log/index.html) technologies can be applied in your application and middleware environments! Please visit our webpage (https://www.ibm.com/developerworks/servicemanagement/bsm/log/index.html), wiki and forum for more information and click on the download icon to participate. Thank you! Doug McClure e: dmccl...@us.ibm.com IBM Log Analytics (https://www.ibm.com/developerworks/servicemanagement/bsm/log/index.html) Product Team To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14961756 Unsubscribe via the binocular icon on the web
WebSphere Application Server: CDI ContextListener only get activated if WEB-INF/beans.xml is available
Author: struberg Message: Hi! I've an application which uses CDI. But CDI injection only works in WAS (8.0.0.1 and 8.0.0.5) when I add WEB-INF/beans.xml. Funnily CDI proxies get injected, but the ContextsService doesn't start the proper ThreadLocals, thus we get a ContextNotActiveException for e.g. ApplicationScoped. This is not sync with the CDI and EE umpbrella spec. CDI should be enabled when a single CDI user bean gets discovered. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14961389 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Need help in setting J2C activation specifications using ws_ant?
Author: bpaskin Message: Hi, I usually use Jython to deploy applications, so I am not an expert on this subject, but there is a parameter that you can specify for the Act Spec call, activationSpecJndiName=jndi/NAME You can also use the options=your options to define all the bidnings you need. On the other side, you could include the bindings in the EJB jar file and then there would be no need to specify them during deployment. Regards, Brian To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14915957 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Need help in setting J2C activation specifications using ws_ant?
Author:
Nikhil_IBM
Message:
Hi All,
I am new to ws_ant script of websphere. I am using Ws_ant.bat for installing
EAR to my local machine. While installing I am using below mention code of
ws_ant:
*?xml version=1.0?*
*lt;project name=project default=wsInstallApp basedir=.gt;*
*lt;descriptiongt;*
*Script for listing installed apps.*
*Example run from:
/opt/IBM/SDP70/runtimes/base_v61/profiles/AppSrv01/bin*
*lt;/descriptiongt;*
*lt;property name=was_homevalue=${to.Stringwas_home}gt;*
*lt;/propertygt;*
*lt;echo message=${was_home}/gt;*
*lt;path id=was.runtimegt;*
*lt;fileset dir=${was_home}/libgt;*
*lt;include name=**/*.jar /gt;*
*lt;/filesetgt;*
*lt;fileset dir=${was_home}/pluginsgt;*
*lt;include name=**/*.jar /gt;*
*lt;/filesetgt;*
*lt;/pathgt;*
*lt;property name=was_cp value=${to.Stringwas.runtime}gt;*
*lt;/propertygt;*
*lt;property environment=envgt;*
*lt;/propertygt;*
*lt;echo message=${was_cp}/gt;*
*lt;target name=wsInstallAppgt;*
*lt;taskdef name=wsInstallApp
classname=com.ibm.websphere.ant.tasks.InstallApplication
classpath=${was_cp} /gt;*
*lt;wsInstallApp*
*wasHome=${was_home}*
*ear=${mywebappear}*
* user=${was.user}*
* password=${was.password} /gt;*
*lt;/targetgt;*
*lt;/projectgt;*
I need help (code) for specifing J2C activation specification properties during
installation of EAR on server. I am using JDBC adapter for connectivity.
Please let me know how to assing J2C activation specification properties while
installing the EAR or modifying adapter properties post installation of EAR.
To respond to this post, please click the following link:
http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14915408
Unsubscribe via the binocular icon on the web
WebSphere Application Server: changing activation spec sessions
Author: 1J7H_MichaĆ_Grzelak Message: Hello. We've recently migrated our WebSphere Process Server and WebSphere Business Monitor from V6.1 to Business Process Manager V8 and WebSphere MQ from 6.0 to 7.1. In WPS V6.1 we used Listener Ports as a message listener service and we could dynamically change its' maximum sessions count simply by changing the Maximum sessions and restarting the listener. Now each process with MDB uses Activation specification and we cant change its maximum sessions count without restarting the apptarget server. Even after restarting activ spec (online) by wsadmin script, the number of opened channel instances on WebSphere MQ doesn't change. Is there any way to dynamically change the Maximum server sessions parameter of the Activation specifications? To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14909763 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Questions regarding Subscription and Support? Visit an SS Rep Page !!!!!
Author: WWarren Message: Please visit my IBM Rep Page for links to Subscription and Support related topics. www.ibm.com/myrep/warrenw To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14906187 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Message Driven Bean and Activation Spec
Author: Bomber.83 Message: Hello stephan thanks for your attention, i'll try to explain the context. I have a cluster of three servers, i configured one Activation Spec and one Queue at the cluster scope. The definition of AS have the property Stop endpoint if message delivery fails set to TRUE , and Number of sequential delivery failures before suspending endpoint set to 10. To simulate the behavior in case of error, i put a broken message on the queue, this (as i wrote my code) causes a rollback. My problem is that after ten attempts to insert message, is stoppend only the endpoint on the server1, while server2 an server3 continue to try to insert the message broken and do roll back continuously. I wish that any endpoint after ten sequential attempts is stopped and not just one. Perhaps i'm missing something to configure. Can you help me? Thanks To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14895762 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Message Driven Bean and Activation Spec
Author: SJC Message: As I explained previously, you have three endpoints. And each endpoint will interpret the configuration separately. So I'd expect server1 to try 10 times and then stop, then server2 to try 10 times and then stop, and finally server3 to try 10 times and then stop. If server2 and server3 really do process continuously (for ever) then something is not working correctly and you'll need to open a PMR. But we've only talked about the JMS Queue and Activation Specification configuration that is used to control each endpoint. The other thing to look at is the configuration of the messaging system itself. There are options you can configure on the Queue which will define what the messaging system should do when message delivery fails. This is the real Service Integration Bus Queue or the MQ Queue (not the JMS Queue definition which refers to it). For example the SIBus Queue has maxFailedDeliveries and exceptionDestination settings. /Stephen To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14895893 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Message Driven Bean and Activation Spec
Author: Bomber.83 Message: Hello Stephen, I get messages from a MQ queue, I went to check the configuration of the queue on the MQ server everything seems correct, I do not think it's a configuration problem MQ because the endpoints are created by each member of the cluster as you told me (i can see and manage the three endpoint on the admin console at runtime). The fact that it blocks (after ten retries) only one endpoint makes me think that is a issue WAS side. I will try to open a PMR. Thank you for the help. Leo To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14895929 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Message Driven Bean and Activation Spec
Author: Bomber.83 Message: Hello everyone, I want to ask a question about an application MDB 3.0 on WAS 7. I deploy an MDB in a cluster of 3 servers, the MDB reads messages from a Activation Specification created at cluster that is connected to a queue it also configured at the cluster. Message delivery works fine, but I wanted to focus on a property of the activation specification: Stop endpoint if message delivery fails which I set to true. If delivery of a message fails, the endpoint is stopped only one of the three servers in the cluster (the one where the deployment manager resides) while the other two continue to roll endless. Does anyone know the reason for this behavior and can help me? thanks ... To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14895290 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Message Driven Bean and Activation Spec
Author: SJC Message: You have three endpoints(^1), one in each of your application servers. Each message will be delivered to one of the endpoints. When an endpoint encounters an error and message delivery fails, that endpoint will be stopped (because you've set the ActSpec setting to true) and the message will rollback onto the Queue. Depending on other settings the failed message may then be sent to one of the other endpoints, or it may be sent to an exception destination (dead-letter queue), or the messaging system may suspend delivery of all messages from that queue. I can't be sure I understand what you mean by the other two continue to roll endless. If you mean they continue to process messages then that's correct behaviour (as described above). If you mean they continuously log errors then that might also be correct, but you'll need to supply some more information (starting with what error string is logged) to clarify things. What are you doing to effect or simulate the delivery failure? When message delivery is working, do you see messages being processed by each of the three app servers in turn? Hope that helps. /Stephen ^1 Configuring the Activation Specification and the JMS Queue at the cluster scope is almost certainly the right thing to do, because this makes a single definition of these objects available to each of the app servers in the cluster. However putting these definitions at cluster scope doesn't mean there's only one endpoint. Each server in the cluster creates its own local in-memory object from this definition. There will always be a local object in each server (JVM) irrespective of whether you configure a separate definition at each of the servers, or just the one at cluster scope, or just the one at cell scope. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14895431 Unsubscribe via the binocular icon on the web
WebSphere Application Server: WebSphere6 ActivationSpec.meajmsact
Author: IonutC Message: I am trying to replicate a production environment for Maximo 6 for testing purposes. The original WebSphere is 6.0 and the new one is 6.1. I can successfuly load the ear file, but when I try to start it I get an error. I replicated all the settings from the original server but I clouldn't make it work. 6/14/12 12:02:29:327 EEST 0028 MBeanHelper E Could not invoke an operation on object: WebSphere:name=ApplicationManager,process=server1,platform=dynamicproxy,node=RPBMXMTSRVNode01,version=6.1.0.0,type=ApplicationManager,mbeanIdentifier=ApplicationManager,cell=RPBMXMTSRVNode01Cell,spec=1.0 because of an mbean exception: com.ibm.ws.exception.RuntimeWarning: javax.resource.ResourceException: Failed to lookup ActivationSpec.meajmsact Can anyone provide an example on how to create that spec ? To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14838342 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Kerberos authentication: WWSS7212E Cannot verify security context token ...
Author: gas Message: Hi, Verify with this redbook, if your policy and bindings are configured correctly on both sides. http://www.redbooks.ibm.com/abstracts/sg247771.html?Open see chapter 11. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14838410 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Kerberos authentication: WWSS7212E Cannot verify security context token ...
Author:
Henk-Jan
Message:
We're trying to configure an application using Kerberos authentication.
Invoking the service fails with the following error message:
security.wssecurity.WSSContextImpl.s02:
com.ibm.websphere.security.WSSecurityException: Exception
org.apache.axis2.AxisFault: CWWSS6521E: The Login failed because of an
exception: javax.security.auth.login.LoginException: CWWSS7212E: Cannot verify
security context token using the reference information from the derived key
token element ocurred while running action:
com.ibm.ws.wssecurity.handler.WSSecurityConsumerHandler$1@37fa37fa
We're using WAS version 7.0.0.19 and a WCF client to access the service.
Analysing the logfile, we conclude:
- the specified keytab file is being found and used (SPN
HTTP/rs6sv303.office01.internalcorp@office01.internalcorp.net)
- the kerberos user identity is correctly determined (eo30021)
However, there are some strange error messages we cannot explain:
6/13/12 15:21:06:958 CEST 002d TokenHolder
setInboundTokenToContext(TGSAuthToken newtoken, MessageContext messageContext)
Entry
6/13/12 15:21:06:958 CEST 002d TokenHolder 3 The operation context is
NULL!!!
and
6/13/12 15:21:06:993 CEST 002d DKTConsumeLog initialize(Subject subject,
CallbackHandler handler, Map sharedState, Map options) Entry
6/13/12 15:21:06:993 CEST 002d WSSAuditServi
isEventRequired(WSSAuditService.WSSAuditEventType eventTypeSECURITY_AUTHN,
WSSAuditService.WSSAuditOutcome out
comeSUCCESS, Maplt;Object, Objectgt; context) Entry
6/13/12 15:21:06:993 CEST 002d WSSAuditServi 3 Usage error, context
should not be null
6/13/12 15:21:06:993 CEST 002d WSSAuditServi isRequired returns: false
Exit
Can anybody point me into a direction where I should look for a solution for
this error message?
Thanks,
Henk-Jan.
The logfile contains much more information which I won't include right away,
but I think this part is the most relevant part:
6/13/12 15:21:06:941 CEST 002d KRBSPNList KRBSPNList() Entry
6/13/12 15:21:06:941 CEST 002d KRBSPNList loadProvSPN() Entry
6/13/12 15:21:06:941 CEST 002d KRBSPNList getKeyTabEntries() Entry
6/13/12 15:21:06:942 CEST 002d KRBSPNList3 Obtained KeyTab Instance
6/13/12 15:21:06:942 CEST 002d KRBSPNList3 kverno 4 spn
HTTP/rs6sv303.office01.internalcorp@office01.internalcorp.net
6/13/12 15:21:06:944 CEST 002d KRBSPN KRBSPN() Entry
6/13/12 15:21:06:944 CEST 002d KRBSPN KRBSPN() Exit
6/13/12 15:21:06:944 CEST 002d KRBSPN setSPN(name, realm) Entry
6/13/12 15:21:06:944 CEST 002d KRBSPN setSPN(name, realm) Exit
6/13/12 15:21:06:944 CEST 002d KRBSPN KRBSPN() Entry
6/13/12 15:21:06:944 CEST 002d KRBSPN KRBSPN() Exit
6/13/12 15:21:06:944 CEST 002d KRBSPNList3 Custom SPN added to
listhttp://HTTP/rs6sv303.OFFICE01.INTERNALCORP.NET
6/13/12 15:21:06:944 CEST 002d KRBSPNList getKeyTabEntries() Exit
6/13/12 15:21:06:945 CEST 002d KRBSPNList loadProvSPN() Exit
6/13/12 15:21:06:945 CEST 002d KRBSPNList KRBSPNList() Exit
6/13/12 15:21:06:945 CEST 002d KRB5Util
isSubKeyEncTypeSupported()... Entry
6/13/12 15:21:06:946 CEST 002d KRB5Util 3 CONTEXT_SUB_KEY_ENC: 23
6/13/12 15:21:06:946 CEST 002d KRB5Util 3 CONTEXT_SUB_KEY_ENC:
java.lang.Integer
6/13/12 15:21:06:946 CEST 002d KRB5Util 3 Current Kerberos subkey
encryption type value: 23
6/13/12 15:21:06:946 CEST 002d KRB5Util 3 Current Kerberos subkey
encryption type: rc4-hmac
6/13/12 15:21:06:946 CEST 002d KRB5Util 3 Kerberos encryption type:
rc4-hmac is tolerated.
6/13/12 15:21:06:946 CEST 002d KRB5Util 3 Supported Kerberos sub key
encryption type in Web services security: aes128-cts-hmac-sha1-96 ,
aes256-cts-hmac-
sha1-96, des3-cbc-sha1
6/13/12 15:21:06:946 CEST 002d KRB5Util
isSubKeyEncTypeSupported()... Exit
6/13/12 15:21:06:947 CEST 002d KRBConsumeLog 3 Key of type: [B with
encryption type: java.lang.Integer from token as follows...^M
: 4d091fe9 3ef84da8 69487b05 910d8fd8M... .M. iH{.
0010:
6/13/12 15:21:06:947 CEST 002d KRBConsumeLog 3 Request token processed OK
6/13/12 15:21:06:947 CEST 002d KRBConsumeLog 3 getAuthenticatedUsername:
WebSphere Security principal = eo30021
6/13/12 15:21:06:947 CEST 002d KRBConsumeLog 3 Kerberos client principal:
eo30021
6/13/12 15:21:06:949 CEST 002d CacheableToke CacheableTokenCacheImpl
Entry
6/13/12 15:21:06:950 CEST 002d CacheableToke CacheableTokenCacheImpl Exit
6/13/12 15:21:06:950 CEST 002d WSSecurityFac 3 factory key =
com.ibm.ws.wssecurity.platform.cacheableTokenCache
6/13/12 15:21:06:950 CEST 002d WSSecurityFac 3 factory impl class =
com.ibm.ws.wssecurity.platform.websphere.auth.CacheableTokenCacheImpl
6/13/12 15:21:06:950 CEST 002d CacheableToke
WebSphere Application Server: Re: JMS Binding export message retry with activation specification
Author: Radhika.k Message: Hi, The retry is working when configured in the system bus sca/lt;lt;module namegt;. However, I am not able to configure both retry count and retry interval. Can you please let me know how to configure both. In mediation module, I can use the JMSXDeliveryCount, but count is not getting incremented after 2. If I manually change it in mediation module, the failed message is requeued with orginal message. Any thoughts will be helpful. Regards, Radhika To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14829953 Unsubscribe via the binocular icon on the web
WebSphere Application Server: JMS Binding export message retry with activation specication
Author: Radhika.k Message: Hi, I have a queue configured with Maximum failed redeliveries set as 3. I have a mediation module with export as JMS Binding which reads the message from the configured queue. The mediation module then uses the message and routes it to appropriate destination. For sake of testing instead of invoking the target webservice I put the fail primitive so that message will be rollbacked to the queue. In this way I aim to test the configured Maximum failed redeliveries. The behaviour I noticed was not as expected as the message was tried to deliver 6 times which seems it does not really adhere to the configuration. The JMSDeliveryCount is not getting incremented for each retry. After first attempt it increments to 2 and then stays 2 for rest of the retries. I tried to manipulate in the module but the behaviour is not changed. Hence wanted to know if the retries are possible only with listener port or it also possible with activiation specification. Regards, Radhika To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14827655 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: JMS Activation specifications, WMQ and app-packaging
Author: ranjitp Message: Stumbled upon this link http://www-01.ibm.com/support/docview.wss?rs=171uid=swg1IZ76343;. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14820259 Unsubscribe via the binocular icon on the web
WebSphere Application Server: JMS Activation specifications, WMQ and app-packaging
Author: ranjitp Message: Our enterprise app which used SIBus route for internal messaging, was asked to be changed to work with MDB using WebSphere MQ(external messaging requirement had also come up). This application uses ejb-2.1, and is now deployed on WAS-7.0.0.23, and is configured to use JMS-Activation to work with the WMQ destination. Our customer initially did not have the WMQ infrastructure, so with the WAS configuration(JMS-Activation) done(JMS Resources) for our app, the app wouldn't start as the JMS Activation enabling failed. To correct this, we had suggested using WAS_EndpointInitialState(value as INACTIVE) JMS Activation custom property referring http://www.ibm.com/developerworks/websphere/library/techarticles/1104_madgula/1104_madgula.html?ca=drs. Are there other ways to help protect the app deployed from failing to start up, because the JMS destination(WMQ) is unavailable, that is, ways to make the app independent(with respect to app start) of the JMS resources it use? In Messaging Listener Port based WAS configuration, it had the Maximum number of retries option, what is its equivalent in JMS Activation specification, that is, how message sending failure is to be handled? To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14819127 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: WebSphere MQ - EJB3.x MDB application using Activation Specs?!
Author:
Pournima
Message:
I am using EJB 3 MDB, websphere MQ V5.3and RAD V8 combination,have defined
activation specification.I am sending one message in request MQ(REQUEST_QUEUE)
then it is heating DB get some data and putting this response in another queue
(RESPONSE_QUEUE),i am trying to read this RESPONCE_QUEUE through java code but
getting time out exception as below.Code of send and receive is also attached
below.
*Is this version related issue of web sphere MQ (As I am using MQ-V5.3)? OR Am
I missing some code in java? OR Any setting in RAD8 server required?*
001e TimeoutManage I WTRN0006W: Transaction
01368307B81900060C169F2488E5D793A026BBCB5982901AB3984096B231C22001368307B81900060C169F2488E5D793A026BBCB5982901AB3984096B231C221
has timed out after 120 seconds.
4/5/12 20:35:02:968 IST 001e TimeoutManage I WTRN0124I: When the timeout
occurred the thread with which the transaction is, or was most recently,
associated was ThreadWebContainer : 0,5,main. The stack trace of this thread
when the timeout occurred was:
java.net.SocketInputStream.socketRead0(Native Method)
java.net.SocketInputStream.read(SocketInputStream.java:140)
com.ibm.mq.jmqi.remote.internal.RemoteTCPConnection.receive(RemoteTCPConnection.java:1419)
com.ibm.mq.jmqi.remote.internal.RemoteHconn.receiveBuffer(RemoteHconn.java:1365)
com.ibm.mq.jmqi.remote.internal.RemoteHconn.receiveOneTSH(RemoteHconn.java:1329)
com.ibm.mq.jmqi.remote.internal.RemoteHconn.receive1stGetReplyTSH(RemoteHconn.java:1820)
com.ibm.mq.jmqi.remote.internal.RemoteFAP.jmqiGetMessageWithProps(RemoteFAP.java:7883)
com.ibm.mq.jmqi.remote.internal.RemoteFAP.MQGET(RemoteFAP.java:7652)
com.ibm.msg.client.wmq.v6.base.internal.MQSESSION.MQGET(MQSESSION.java:1009)
com.ibm.msg.client.wmq.v6.base.internal.MQQueue.getMsg2Int(MQQueue.java:1353)
com.ibm.msg.client.wmq.v6.base.internal.MQQueue.getMsg2(MQQueue.java:994)
com.ibm.msg.client.wmq.v6.jms.internal.MQMessageConsumer.getMessage(MQMessageConsumer.java:2751)
com.ibm.msg.client.wmq.v6.jms.internal.MQMessageConsumer.receiveInternal(MQMessageConsumer.java:4622)
com.ibm.msg.client.wmq.v6.jms.internal.MQMessageConsumer.receive(MQMessageConsumer.java:4091)
com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl.receiveInboundMessage(JmsMessageConsumerImpl.java:780)
com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl.receive(JmsMessageConsumerImpl.java:348)
com.ibm.mq.jms.MQMessageConsumer.receive(MQMessageConsumer.java:228)
com.ibm.ejs.jms.JMSMessageConsumerHandle.receive(JMSMessageConsumerHandle.java:445)
com.hbcbsnj.odmf.app.client.DocumentSearchManagerBean.receiveMessage(DocumentSearchManagerBean.java:209)
com.hbcbsnj.odmf.app.client.DocumentSearchManagerBean.sendReceive(DocumentSearchManagerBean.java:143)
*Code of send method :*
private String sendMessage(QueueSession session, String requestMessageString)
throws Exception {
QueueSender sender = null;
Queue queue = null;
InitialContext initialContext = new InitialContext();
try {
queue = (Queue)
initialContext.lookup(ApplicationProperties.EOB_REQUEST_Q);
sender = session.createSender(queue);
sender.setDeliveryMode(DeliveryMode.NON_PERSISTENT);
TextMessage message = session.createTextMessage();
message.setJMSMessageID(MESSAGE_ID);
message.setText(requestMessageString);
sender.send(message);
String messageID = message.getJMSMessageID();
return messageID;
} catch (JMSException e) {
throw e;
} finally {
if (sender != null) {
sender.close();
}
}
}
*code of receive method :*
private String receiveMessage(QueueSession session, String messageSelector)
throws Exception {
QueueReceiver receiver = null;
InitialContext initialContext = new InitialContext();
Queue queue = null;
try {
messageSelector = new StringBuffer().append(JMSCorrelationID =
\').append(messageSelector).append(\').toString();
queue = (Queue)
initialContext.lookup(ODMFApplicationProperties.EOB_REQUEST_Q);
receiver = session.createReceiver(queue, messageSelector);
TextMessage msg = (TextMessage) receiver.receive(); // Getting
time out exception here
String returnString = msg.getText();
return returnString;
}catch (JMSException e) {
throw e;
} finally {
if (receiver != null) {
receiver.close();
}
}
}
To respond to this post, please click the following link:
WebSphere Application Server: Re: WebSphere MQ - EJB3.x MDB application using Activation Specs?!
Author: bkail Message: Your problem looks unrelated to the problem reported in this 2.5 year old thread. I recommend starting a fresh thread: http://www.ibm.com/developerworks/forums/forum.jspa?forumID=266 To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14813675 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: java.lang.VerifyError on JAX-WS AXIS2 webservice WEBSPHERE 6.1 deployment
Author: FrancescoMonari Message: Working on this problem and looking around the source code of the libaries it comes out that the error occurs in JAXBContext newIstance method once enabled the trace log on class loader is shown as the javax.xml.datatype.DatatypeConstants class is loaded from PARENT because it's not found in the WAR module and this gives the java.lang.VerifyError adding in the war lib the following jars xml-apis.jar xercesImpl.jar xalan.jar solves the problem To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14789524 Unsubscribe via the binocular icon on the web
WebSphere Application Server: java.lang.VerifyError on JAX-WS AXIS2 webservice WEBSPHERE 6.1 deployment
Author: FrancescoMonari Message: I'm trying to deploy a web service based on jax ws axis2 on websphere 6.1. It works properly in tomcat 5.5 I've been following the steps described in the axis2 online documentation available at this link http://axis.apache.org/axis2/java/core/docs/app_server.html THe service seems to deploy properly (no message errors in System out) and the return the wsdl file when requested. I'm also able to engage a module on web service for logging purposes. The problem comes out when invoking the service from a client: it returns a WebFault Stacktrace on the server is as follow 10/02/12 16.58.59:861 CET 001e FactoryRegist E org.apache.axis2.jaxws.registry.FactoryRegistry null java.lang.VerifyError at com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl.(RuntimeBuiltinLeafInfoImpl.java:224) at java.lang.J9VMInternals.initializeImpl(Native Method) at java.lang.J9VMInternals.initialize(J9VMInternals.java:194) at com.sun.xml.bind.v2.model.impl.RuntimeTypeInfoSetImpl.(RuntimeTypeInfoSetImpl.java:61) at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.createTypeInfoSet(RuntimeModelBuilder.java:127) at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.createTypeInfoSet(RuntimeModelBuilder.java:79) at com.sun.xml.bind.v2.model.impl.ModelBuilder.(ModelBuilder.java:152) at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.(RuntimeModelBuilder.java:87) at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:422) at com.sun.xml.bind.v2.runtime.JAXBContextImpl.(JAXBContextImpl.java:286) at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139) at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:117) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:214) at javax.xml.bind.ContextFinder.find(ContextFinder.java:375) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:522) at org.apache.axis2.jaxws.addressing.factory.impl.JAXWSEndpointReferenceFactoryImpl$1.run(JAXWSEndpointReferenceFactoryImpl.java:61) at org.apache.axis2.java.security.AccessController.doPrivileged(AccessController.java:132) at org.apache.axis2.jaxws.addressing.factory.impl.JAXWSEndpointReferenceFactoryImpl.(JAXWSEndpointReferenceFactoryImpl.java:56) at org.apache.axis2.jaxws.registry.FactoryRegistry.init(FactoryRegistry.java:122) at org.apache.axis2.jaxws.registry.FactoryRegistry.(FactoryRegistry.java:97) at java.lang.J9VMInternals.initializeImpl(Native Method) at java.lang.J9VMInternals.initialize(J9VMInternals.java:194) at org.apache.axis2.jaxws.message.util.MessageUtils.getMessageFromMessageContext(MessageUtils.java:145) at org.apache.axis2.jaxws.core.MessageContext.(MessageContext.java:120) at org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessageReceiver.java:124) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146) at wgs.v3.servlet.JetAxisServlet.doPost(JetAxisServlet.java:30) at javax.servlet.http.HttpServlet.service(HttpServlet.java:763) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1096) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:570) at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478) at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3444) at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:267) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:815) at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1466) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:119) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:387) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:267) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113) at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165) at
WebSphere Application Server: Axis2 1.5 With Spring Causing java.lang.VerifyError: JVMVRFY013
Author: sjunejo Message: Hi, I am using axis2 (1.5) to host my web services. I am using spring framework for dependency injection to instantiate some classes. I managed to start axis2 after setting up parent-last class loading policy for my axis web module as stated on following link (known issue); After all this I am getting following exception upon listing the service installed only (I can see axis2 index page, I can list services but as soon as I click any service for its WSDL I get following); 10/11/11 22:35:42:483 GMT 0027 webappI com.ibm.ws.webcontainer.webapp.WebGroupImpl WebGroup SRVE0169I: Loading Web Module: Apache-Axis2. 10/11/11 22:35:42:501 GMT 0027 WASSessionCor I SessionContextRegistry getSessionContext SESN0176I: Will create a new session context for application key default_host/axi s2 10/11/11 22:35:42:621 GMT 0027 FfdcProvider I com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:\IBM\WebSphere7\AppServer\profiles\App Srv01\logs\ffdc\server1_6d026d02_11.11.10_22.35.42.61837911.txt com.ibm.ws.webcontainer.servlet.ServletWrapperImpl 272 10/11/11 22:35:43:765 GMT 0027 SystemOut O INFO Deploying module: addressing-1.5.5 - file:/C:/IBM/WebSphere7/AppServer/profiles/AppSrv01/installedApps/hmll1010336N ode01Cell/axis2_war.ear/axis2.war/WEB-INF/modules/addressing-1.5.5.mar 10/11/11 22:35:43:787 GMT 0027 SystemOut O INFO Deploying module: jaxws-1.5.5 - file:/C:/IBM/WebSphere7/AppServer/profiles/AppSrv01/installedApps/hmll1010336Node01 Cell/axis2_war.ear/axis2.war/WEB-INF/modules/axis2-jaxws-mar-1.5.5.mar 10/11/11 22:35:43:806 GMT 0027 SystemOut O INFO Deploying module: metadataExchange-1.5.5 - file:/C:/IBM/WebSphere7/AppServer/profiles/AppSrv01/installedApps/hmll10 10336Node01Cell/axis2_war.ear/axis2.war/WEB-INF/modules/mex-1.5.5.mar 10/11/11 22:35:43:815 GMT 0027 SystemOut O INFO Deploying module: mtompolicy-1.5.5 - file:/C:/IBM/WebSphere7/AppServer/profiles/AppSrv01/installedApps/hmll1010336N ode01Cell/axis2_war.ear/axis2.war/WEB-INF/modules/mtompolicy-1.5.5.mar 10/11/11 22:35:43:829 GMT 0027 SystemOut O INFO Deploying module: ping-1.5.5 - file:/C:/IBM/WebSphere7/AppServer/profiles/AppSrv01/installedApps/hmll1010336Node01C ell/axis2_war.ear/axis2.war/WEB-INF/modules/ping-1.5.5.mar 10/11/11 22:35:43:837 GMT 0027 SystemOut O INFO Deploying module: script-1.5.5 - file:/C:/IBM/WebSphere7/AppServer/profiles/AppSrv01/installedApps/hmll1010336Node0 1Cell/axis2_war.ear/axis2.war/WEB-INF/modules/scripting-1.5.5.mar 10/11/11 22:35:43:848 GMT 0027 SystemOut O INFO Deploying module: soapmonitor-1.5.5 - file:/C:/IBM/WebSphere7/AppServer/profiles/AppSrv01/installedApps/hmll1010336 Node01Cell/axis2_war.ear/axis2.war/WEB-INF/modules/soapmonitor-1.5.5.mar 10/11/11 22:35:43:876 GMT 0027 SystemOut O INFO Deploying module: addressing-1.5.5 - file:/C:/IBM/WebSphere7/AppServer/profiles/AppSrv01/installedApps/hmll1010336N ode01Cell/axis2_war.ear/axis2.war/WEB-INF/lib/addressing-1.5.5.jar 10/11/11 22:35:43:885 GMT 0027 SystemOut O INFO Deploying module: jaxws-1.5.5 - file:/C:/IBM/WebSphere7/AppServer/profiles/AppSrv01/installedApps/hmll1010336Node01 Cell/axis2_war.ear/axis2.war/WEB-INF/lib/axis2-jaxws-mar-1.5.5.jar 10/11/11 22:35:43:893 GMT 0027 SystemOut O INFO Deploying module: mtompolicy-1.5.5 - file:/C:/IBM/WebSphere7/AppServer/profiles/AppSrv01/installedApps/hmll1010336N ode01Cell/axis2_war.ear/axis2.war/WEB-INF/lib/mtompolicy-1.5.5.jar 10/11/11 22:35:43:902 GMT 0027 SystemOut O INFO Deploying module: ping-1.5.5 - file:/C:/IBM/WebSphere7/AppServer/profiles/AppSrv01/installedApps/hmll1010336Node01C ell/axis2_war.ear/axis2.war/WEB-INF/lib/ping-1.5.5.jar 10/11/11 22:35:43:910 GMT 0027 SystemOut O INFO Deploying module: script-1.5.5 - file:/C:/IBM/WebSphere7/AppServer/profiles/AppSrv01/installedApps/hmll1010336Node0 1Cell/axis2_war.ear/axis2.war/WEB-INF/lib/scripting-1.5.5.jar 10/11/11 22:35:43:919 GMT 0027 SystemOut O INFO Deploying module: soapmonitor-1.5.5 - file:/C:/IBM/WebSphere7/AppServer/profiles/AppSrv01/installedApps/hmll1010336 Node01Cell/axis2_war.ear/axis2.war/WEB-INF/lib/soapmonitor-1.5.5.jar 10/11/11 22:35:44:467 GMT 0027 SystemOut O INFO Refreshing org.springframework.context.support.ClassPathXmlApplicationContext@16cb16cb: display name [org.springfra mework.context.support.ClassPathXmlApplicationContext@16cb16cb]; startup date Thu Nov 10 22:35:44 GMT 2011; root of context hierarchy 10/11/11 22:35:44:525 GMT 0027 SystemOut O INFO Loading XML bean definitions from class path resource http://customerServiceContext.xml 10/11/11 22:35:44:723 GMT 0027 SystemOut O INFO Deploying Web service: t24-CustomerService-jws.aar - file:/C:/IBM/WebSphere7/AppServer/profiles/AppSrv01/installedA pps/hmll1010336Node01Cell/axis2_war.ear/axis2.war/WEB-INF/services/t24-CustomerService-jws.aar
WebSphere Application Server: Re: Sudden pausing of MQ Activations spec listeners
Author: MANT Message: Matt, I am not able to find the code that you sent in the logs somehow. The reason we have the timeout for MDB for the batch jobs set as -1 because the message consumption from the MDB is triggering an execution of multiple stateless session beans. We did not configure the datasource as XA, it is single phase, so for the MDB not to timeout for the complete execution of the batch process the MDB transaction timeout is -1 but individual stateless session beans have the default transaction timeout set. IT is working well for a long time but the pausing of activation specs is a recently occurring issue..not sure what could be the cause of itis it possible to check using java APIs to see if the activation specs are paused or not? and start them if they are stopped? Is there a way to get an alert atleast if the activation spec listeners are stopped. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14675700 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Sudden pausing of MQ Activations spec listeners
Author: mamwl1 Message: Hi, That is definitely the correct message code to be searching for when WMQ activation specs are pausing them selves automatically. Perhaps your logs are wrapping before you have a chance to search for the code. You can check endpoint status and restart them if needed but that doesn't sound like the right approach. If you are going to end up writing a load of monitoring code you might as well increase the number of sequential errors that the activation spec will tolerate before pausing, it will give the same effect. Regardless I think you still need to get to the bottom of the reason for the pause in the first place rather than work around it. You can use the following MBean to establish the status of an endpoint: http://publib.boulder.ibm.com/infocenter/wasinfo/fep/index.jsp?topic=/com.ibm.websphere.javadoc.doc/web/mbeanDocs/J2CMessageEndpoint.html. I haven't seen any mechanism for getting alerts in this area, but I only had a quick look. Regards, Matt. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14675765 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Sudden pausing of MQ Activations spec listeners
Author: mamwl1 Message: Hi, It is generally a very bad idea to have long running transactions. Certainly something that runs a single transaction for hours is very bad. If you are actually doing transactional work then the work will get undone anyway as a result of the transaction timing out. Which means you have just wasted all your time. Additionally transactions hold numerous locks in databases etc so long running ones result in resource constraints. Do you need to do your batch work in a transaction? If you post your logs it might give me some clues as to why the pause occurred. Regards, Matt. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14674722 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Sudden pausing of MQ Activations spec listeners
Author: MANT Message: Hi Matt, Although we are running batch jobs using the MDB, it is not a single transactions. It is bunch of transactions after the message is consumed, to avoid the MDB transaction timeout, we have specified the MDB in the ibm-ejb-ext.xml file with transaction timeout as -1 so the MDB does not timeout. What logs would you require? the problem is we actually do not know if the activation specs are stopping because of the batch process or something else. Is there a constant string that I can search in the log which can indicate a point in time when the listeners are paused? To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14674808 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Sudden pausing of MQ Activations spec listeners
Author: mamwl1 Message: Hi, Try looking for this in your system out logs: CWWMQ0007W. You must have had a transaction timeout in place as you showed me a transaction timeout message! When you say you set the timeout in the ibm-ejb-ext.xml file I presume you are talking about the component transaction timeout. I don't think a value of -1 is supported as that would imply an infinite transaction timeout which is not good. As an aside I assume you have logic which deals with your batch processing half way through? Otherwise you will end up processing the first half of the batch again. Regards, Matt. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14674819 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Extracting X.509 with IBM CC Verification Tool for SSL/TLS Webcast Sep 6
Author: josephlam Message: You are invited to attend a webcast on the topic of Extracting X.509 Public Certificates with IBM Connection and Configuration Verification Tool for SSL/TLS. On 6 September 2011 at 11:00 AM EDT, a WebSphere Support Technical Exchange presentation on Extracting X.509 Public Certificates with IBM Connection and Configuration Verification Tool for SSL/TLS will be delivered by Jinwoo Hwang, a subject matter expert. An open question and answer session will follow the presentation. This session provides an overview of the IBM Connection and Configuration Verification Tool for SSL/TLS and explains how to extract X.509 public certificates from a server over the Secure Sockets Layer (SSL) and the Transport Layer Security (TLS) protocol, and import them into a client's keystore. Level of Difficulty: Beginner Plan to join the meeting 10 minutes early. Presentations typically last for 30-45 minutes followed by a question and answer session. For more information and details on how to participate in this and other free WebSphere Support Technical Exchanges click here (http://www-01.ibm.com/software/websphere/support/supp_tech.html). Date: September 6, 2011 Time: 11:00 AM EDT For dial-in numbers and web conferencing information, please visit: http://www-01.ibm.com/software/websphere/support/TE/techex_U111693Y42341C59.html We look forward to your participation in this webcast session! To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14674925 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Sudden pausing of MQ Activations spec listeners
Author: mamwl1 Message: Hi, The hung thread is caused by your application code taking a while to do a socket read to sybase. That results in the transaction under which the code is running timing out which gives the message which you attached. A transaction timeout would probably be sufficient to drive the pause logic if I remember correctly. I would advice you establish why your application is taking longer to run than the transaction timeout which by default is 2 minutes. If you think that the amount of time taken is reasonable then you need to increase the transaction timeout. For the moment you are probably best leaving pausing enabled but you might want to consider whether you pause straight away or allow a small number of failures. This can be configured under the check box I mentioned earlier. As an aside what version of WAS are you on and can you send me the line from your system out log which has the following message key: WMSG1703I. It indicates the version of WMQ resource adapter that is in use. Regards, Matt. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14674142 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Sudden pausing of MQ Activations spec listeners
Author: MANT Message: Matt, I am running 7.0.0.13 version of WAS with JPA 2.0 feature pack as we are using IBM OpenJPA implementation at the persistence layer... checkout the version that you asked for.. 8/17/11 12:14:32:829 EDT 000a JMSRegistrati I WMSG1703I: RAR implementation version 7.0.1.3-k701-103-100812 To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14674223 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Sudden pausing of MQ Activations spec listeners
Author: mamwl1 Message: Hi, So you are at a reasonable level of the WMQ resource adapter. On that basis I would advise you to establish why your read was taking a long time and popping the transaction timeout. It may be that the answer is to increase the time out but I wouldn't advise that unless you have any other choice. Regards, Matt. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14674242 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Sudden pausing of MQ Activations spec listeners
Author: MANT Message: Matt, I also came across this thread, do I have to upgrade the server version? would the checkbox that you are talking about will really help? http://www-01.ibm.com/support/docview.wss?uid=swg1IZ52152 To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14674250 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Sudden pausing of MQ Activations spec listeners
Author: mamwl1 Message: Hi, If it is a problem with a thread pool it isn't the one used by WMQ. The bottom of that stack trace would be the same for any thread doing WMQ activation spec work. The important point is that the MDB is taking more than 120 seconds to do its processing. This is either because something has gone wrong at the other end of the socket OR it could be that your app runs slow enough that the transaction timeout occurred during the read. Do you get a timeout for every request or just when under load? If it is under load you need to find out where your app is spending its time and go from there. Regards, Matt. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14674276 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Sudden pausing of MQ Activations spec listeners
Author: mamwl1 Message: Hi, That fix is in WMQ 7.0.1.0 and you are at 7.0.1.3 so you should already have it. Regards, Matt. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14674278 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Sudden pausing of MQ Activations spec listeners
Author: MANT Message: Matt, Thanks again, We are using MDB to trigger the batch processing on the application server, do you think its a bad design in doing that? What we are doing is, running a shell script that puts a message on a queue, MDB consumes it and starts the processing on the application server, now since it is a batch job it obviously takes longer than 120 seconds for the transaction to be processed. Some botch jobs run for hours...could that cause the activation spec to pause? probably the transaction is still running on the application server but the MDB transaction Timeout already reached?? regards To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14674296 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Sudden pausing of MQ Activations spec listeners
Author: MANT Message: Matt, Thanks again, We are using MDB to trigger the batch processing on the application server, do you think its a bad design in doing that? What we are doing is, running a shell script that puts a message on a queue, MDB consumes it and starts the processing on the application server, now since it is a batch job it obviously takes longer than 120 seconds for the transaction to be processed. Some botch jobs run for hours...could that cause the activation spec to pause? probably the transaction is still running on the application server but the MDB transaction Timeout already reached?? regards To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14674300 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Sudden pausing of MQ Activations spec listeners
Author: mamwl1 Message: Hi, I think it would be better to investigate the reason for the pausing in the first place as that implies something going wrong somewhere which should be fixed rather than ignored. There should be an indication of that in the logs. I would also be interested in the stack trace of the hung threads if you can provide it. You can disable the pausing if you wish. It is a check box called Stop endpoint if message delivery fails on the advanced panel of MQ activation specs. Regards, Matt. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14673278 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Sudden pausing of MQ Activations spec listeners
Author: MANT Message: Thanks Matt for your response, what could be the potential causes that result in pausing of the activation specs? In the advanced section I don't see the checkbox, unless this is not available on the RAD version of websphere app server. I am on 7.0.0.13 with JPS2.0 feature pack. Check the attached, sample thread To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14673288 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Sudden pausing of MQ Activations spec listeners
Author: MANT Message: Matt, my bad, I found the checkbox on the advanced properties when I created the activation specs of type Websphere MQ instead of Default JMS I was using Default JMS on my local and using message transportation using BUS instead of MQ. Also verified that it is actually checked in the production region, but the question would be if I uncheck that would it resolve the issue or still I would have to find out the cause why it is getting paused? what is causing it to get paused...I think I should find that out first..let me know if you have any pointers... regards, MANT To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14673296 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Delete confirmation appears twice
Author: NehalJ Message: When deleting an item on the form, the delete confirmation appears twice and could delete another item. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14640444 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: start and stop message endpoint for ActivationSpec
Author: mamwl1 Message: Hi, Assuming you are using the WMQ messaging provider you go to the relevant activation spec and click on the advanced properties tab. Down the bottom there is a stop endpoint if message delivery fails check box. Un-tick that, save and restart the relevant servers. See the attached image. Be warned that this means that poisoned messages will get repeatedly delivered until they are DLQ'd. So it might be worth increasing the pause threshold to say 10 rather than disabling it completely. Regards, Matt. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14628042 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Exception thrown : java.lang.VerifyError: javax/xml/bind/JAXBElement.lt;initgt;
Author: Darren.Armatrading Message: chandu$ wrote:while deploying my ear in websphere 6.1 in windows system it is working fine, but same ear file when i am deployinh in Unix, i am getting the below error,8/3/10 3:48:33:251 MST 002c ServletWrappe E CWSRV0068E: Uncaught exception thrown in one of the service methods of the servlet: ActionServlet. Exception thrown : java.lang.VerifyError: javax/xml/bind/JAXBElement.lt;INITgt;(Ljavax/xml/namespace/QName;Ljava/lang/Class;Ljava/lang/Class;Ljava/lang/Object;)Vat com.wsip.ObjectFactory.createAuthorizeGCAGXMLMessage(ObjectFactory.java:313)at com.utils.xml.CommonMarshalingUtility.convertObjectToGNSXML(CommonMarshalingUtility.java:142)at com.utils.xml.GNSXmlUtility.createXML(TestXmlUtility.java:140) There is already web services pack in both windows and unix alsoplease help me ASAPThanks in advance..!!You can give a more complete description of your needs, It is better for the answer. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14596425 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: EJB Activation Error after EJB Timeout
Author: RBS8_Amitesh_Sharma Message: Hi QAS, Thankyou very for the reply. I have below EJB spec reference from O'Reilly Enterprise JavaBeans, 3.0 5th Edition ebook lt;lt; When an EJB server needs to conserve resources, it can evict stateful session beans from memory. When a bean is evicted, its conversational state is serialized to secondary storage. *When a client invokes a method on the EJB object, a new stateful session bean instance is instantiated and populated with the state from the initial bean.* Since a stateful bean class does not have to be serializable, the exact mechanism for activating and passivating stateful beans is up to the vendor. gt; I am using EJB 3.0 Stateful Beans And as per above spec WAS should return a new instance to the same Client with prev state(Even if the Client was idle for some time). And the application should not throw exception/or App state should not get destroyed. If application state would start getting destroyed. And there's no way out to even extend the EJB3 (Feature Pack) timeout. I think there's no use of having EJB3 support on WAS 6.1) It's looking like a Web Sphere specification implementation mismatch/problem. Please confirm if my understanding is correct. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14592111 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: EJB Activation Error after EJB Timeout
Author: gas Message: Hi, These are two different things. Bean state is passivated when it is not in transaction, based on activation policy (see bkail response in your other post). Timeout is used by the container to detect 'abandoned' beans that should be removed. You are hitting that one. Your bean is inactive longer than 10 minutes, so removed. Unfortunately you can not change it in the FEP EJB 3.0, see limitations on this page: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.ejbfep.multiplatform.doc/info/ae/ae/rejb_limitationsejbfp.html If you need longer timeout you can: - migrate to WAS v7, where this setting is supported - http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.express.doc/info/exp/ae/cejb_bindingsejbfp.html - switch to use EJB 2.1, where you can override it per bean - introduce a heartbeat in the app, that will call bean once a few minutes. It is very strange that you are hitting this timeout, as it means that client has not called the bean for very long time. SFSBs usually act as Facade to the application, so they should be limited in number and called quite often. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14592117 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: EJB Activation Error after EJB Timeout
Author: gas Message: Hi, This is ok, according to the spec. After the timeout bean instance is removed, no matter if it has clients. From the EJB spec: While the instance is in the passivated state, the container may remove the session object after the expiration of a timeout speciïŹed by the Deployer. All object references and handles for the session object become invalid. If a client attempts to invoke the session object, the container will throw the java.rmi.NoSuchObjectException. If 10 minutes is too short for you, you can change this setting via deployment descriptor: http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compassproduct=was-express-disttopic=rprf_ejbcontainer To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14591475 Unsubscribe via the binocular icon on the web
WebSphere Application Server: EJB Activation Error after EJB Timeout
Author: RBS8_Amitesh_Sharma Message: Dear All, I am facing an issue in invoking an EJB3 Stateful Bean, after it has been removed by the WebSphere container after 10 mins. Scenario: 1)Call EJB from UI Processing. 2)After 10 mins of inactivity Stateful EJB Times Out 3)Call EJB from UI Processing - Here Now the as WebSphere Container has removed the bean, it should provide me a new instance with the previous state saved(Of removed EJB) in the secondary storage according to the EJB3 Specification. Instead on Activation It is throwing the EJB Removed or Timed Out Error. Plz help. We are primarly using EJBs in our project. This issue has become a shopstopper for the project. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14591183 Unsubscribe via the binocular icon on the web
WebSphere Application Server: EJB Activation Error after EJB Timeout
Author: RBS8_Amitesh_Sharma Message: Dear All, I am facing an issue in invoking an EJB3 Stateful Bean, after it has been removed by the WebSphere container after 10 mins. Scenario: 1)Call EJB from UI Processing. 2)After 10 mins of inactivity Stateful EJB Times Out 3)Call EJB from UI Processing - Here Now the as WebSphere Container has removed the bean, it should provide me a new instance with the previous state saved(Of removed EJB) in the secondary storage according to the EJB3 Specification. Instead on Activation It is throwing the EJB Removed or Timed Out Error. Plz help. We are primarly using EJBs in our project. This issue has become a shopstopper for the project. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14591184 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: NON-ASF in activation specification
Author: mamwl1 Message: Hi Neha, OK. So for the time being I am afraid you will have to stick with listener ports based on your requirements. I would note that NON-ASF doesn't guarantee strict message ordering as transaction recovery can happen asynchronously at server start up - or indeed while the server is already up, in case of a connectivity issue with WMQ - which can result in out of order messages. Regards, Matt. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14581540 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: NON-ASF in activation specification
Author: mamwl1 Message: Hi Neha, Because of how non-ASF mode works it would have to be added to each activation spec provider for example the default messaging provider)separately. I am guessing you are asking for this on the WMQ messaging provider? If so it might be worth you bringing this up with your IBM representative so we can log a feature request - it will come through to me, or one of my colleagues. I would note that various customers have asked for this function, but IBM guidelines mean I can't say whether we will implement it or not or provide any sort of timeline. Can you tell me why you want non-ASF activation specs? It might be possible to get the behavior you require without non-ASF mode being available. Regards, Matt. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14579990 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: NON-ASF in activation specification
Author: _neha_d Message: Matt, thanks for your reply. Following are reasons to choose NON-ASF 1) strict ordering and 2) higher throughput We have been using NON-ASF using listener ports with Maximum sessions = 1 Maximum messages = 1 to 'get' msgs in exactly same order as 'put', if we rollback a 'get' we want to re-get the exact same message, thats how our retry mechanism works. We are trying to migrate to activation spec. Thanks for your help. |\||) /** In the face of ambiguity, refuse the temptation to guess */ To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14580257 Unsubscribe via the binocular icon on the web
WebSphere Application Server: NON-ASF in activation specification
Author: _neha_d Message: is it possible to have non-asf mode using activation spec. Thanks. -nd /** In the face of ambiguity, refuse the temptation to guess */ To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14579758 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: start and stop message endpoint for ActivationSpec
Author: mamwl1 Message: Hi, You can also tune your activation spec via the panels so it never pauses, or only pauses after a specified number of sequential failures. The default is to pause after the first failure which is what you are seeing. Cheers, Matt. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14574419 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: start and stop message endpoint for ActivationSpec
Author: rookie-0d50ef77d725 Message: Thanks. I found it here (in Runtime tab) Enterprise Applications MyQReaderEAP Manage message endpoints To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14574688 Unsubscribe via the binocular icon on the web
WebSphere Application Server: activation specification
Author: rookie-0d50ef77d725 Message: we have been using listener ports for years and trying to see how same configration can be set using activation spec. 1- is it good idea to use activation spec without using SIB? 2- each activation spec (for WebSphere MQ Resource Adapter at least) requires to set host,port,channel,qmgr and it doesnt use connection factory like listener ports used to? 3- 'Maximum server sessions' in activation spec is similar (mostly same) as 'Maximum sessions' in listener ports? 4- what equivalent of listener ports 'Maximum messages' in activaton spec, and how max msgs apply on activaton spec? 5- 'Number of sequential delivery failures before suspending endpoint' in activation spec is same as 'Maximum retries' in listener ports? 6- how about non-ASF mode in activaton spec, does that apply to activaton spec? is there a document how activaton spec reads msg from queue like following for listener port? http://www.ibm.com/developerworks/websphere/library/techarticles/0611_titheridge/0611_titheridge.html 7- in clustered env all the cluster member's MDB instance will get msg from activaton spec (activaton spec is defined at cell level), is it possible to control what cluster meber should receive message. In listener ports we use to control it by stopping 'listener ports' on specific cluster members? only reason we have to use 'activation spec' is, company thinks IBM will stop support for listener ports and will pull it out from WAS, however I've seen contradictory comments https://www.ibm.com/developerworks/mydeveloperworks/blogs/woolf/entry/rad_6_listener_port_vs?lang=en but hey we got to do what we get paid for ;) Thanks for you help. Rookie To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14574693 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: start and stop message endpoint for ActivationSpec
Author: gas Message: Hi, In WAS v7 you can do it either through admin console: http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.nd.doc/info/ae/ae/tjn_mdb_0001_Ex1.html or wsadmin script: http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.soafep.multiplatform.doc/info/ae/ae/txml_7msgend.html To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14574275 Unsubscribe via the binocular icon on the web
WebSphere Application Server: start and stop message endpoint for ActivationSpec
Author: rookie-0d50ef77d725 Message: how do we start and stop message endpoint for ActivationSpec (using MQ provider), like we could do for listeners ports. if message endpoint is stopped how can we start it again-- 012d ActivationSpe I J2CA0524I: The Message Endpoint for ActivationSpec eis/testq1 (com.ibm.mq.connector.inbound.ActivationSpecImpl) and MDB Application TestEAP#TestEJB.jar#TestJMSReader is deactivated. 012d SibMessageW [:] CWWMQ0007W: The message endpoint TestEAP#TestEJB.jar#TestJMSReader has been paused by the system. Message delivery failed to the endpoint more than 0 times. The last attempted delivery failed with the following error: javax.jms.TransactionRolledBackException: Thanks. Rookie To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14574099 Unsubscribe via the binocular icon on the web
WebSphere Application Server: How to activate WSDM ?
Author: VQKF_Florian_Werner Message: Hello, I'm currently evaluating the WSDM feature but can't get it to work. After enabling WSDM through wsadmin (Link:http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.base.doc/info/aes/ae/txml_7wsdm.html) I expected the given URLs to deliver a WSDL file: Link:http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.base.doc/info/aes/ae/rwbs_reswsdm.html Instead the request is aborted with a HTTP 404 file not found exception. I'd like to realize this functionality: Link:http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/twbs_wsdmresmonitor.html Since the article is flagged as deprecated I wonder if this corresponding one is still valid: Link:http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.base.doc/info/aes/ae/rwbs_reswsdm.html Furthermore the WSDM feature is listed as deprecated here: Link:http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/rmig_depfeat.html How could I possibly create a WSDM client that polls metrics via WSDM as described in the mentioned article: Link:http://www.ibm.com/developerworks/websphere/library/techarticles/0802_chang/0802_chang.html Do I have to configure something else besides the wsadmin task? Perhaps activate the WSDM application WebSphereWSDM.ear inside the Integrated Solution Console? ..or another system app? Thanks, Florian To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14555069 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: How to activate WSDM ?
Author: VQKF_Florian_Werner Message: Hello again, I discovered my mistake: I expected the WSDL to appear under the port for Web Applications (Portname: WC_defaulthost - default: 9080). In fact the WSDM management application uses the admin/management port as used by the Integrated Solution Console (Portname: WC_adminhost - default: 9060). Therefore you get the WSDL for e.g. the initial service-group from http://lt;hostnamegt;:9060/websphere-management/services/service-group?wsdl http://lt;hostnamegt;:9060/websphere-management/services/service-group/WEB-INF/classes/wsdl/WS-ServiceGroup-1_2.wsdl Greetings, Florian To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14555078 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Oracle driver property SetFloatAndDoubleUseBinary not activatable WAS 6.1
Author: BerndSG Message: Update: We found the solution! You can define connection properties on the Websphere datasource (in the ear deployment descriptor, Deployment tab, Resource properties for the respective data source above) as follows: name: connectionProperties type: java.lang.String value: SetFloatAndDoubleUseBinary=true enables this and binary_double typed attributes work also with large numbers ( 1e125). Good luck! Regards, Bernd PS: Thanks, Patrick! =:-) To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14543198 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Oracle driver property SetFloatAndDoubleUseBinary not activatable WAS 6.1
Author: BerndSG Message: Hello, I'm trying to activate the Oracle driver property SetFloatAndDoubleUseBinary in WAS 6.1 but it does not work, whatever we try. We need to have this enabled because we use the Oracle data type binary_double, and not having this property set leads to errors like this: Internal Error: Overflow Exception trying to bind 1.0E160 Setting it as a custom property on the datasource does not work. this generates a warning while testing the connection as follows: 10/14/10 20:03:10:208 CEST 0035 DSConfigurati W DSRA8200W: DataSource Configuration: DSRA8020E: Warning: The property 'SetFloatAndDoubleUseBinary' does not exist on the DataSource class oracle.jdbc.pool.OracleConnectionPoolDataSource. 10/14/10 20:03:13:162 CEST 0035 DSConfigurati I DSRA8203I: Database product name : Oracle 10/14/10 20:03:13:162 CEST 0035 DSConfigurati I DSRA8204I: Database product version : Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production With the Partitioning, Real Application Clusters, OLAP, Data Mining and Real Application Testing options 10/14/10 20:03:13:162 CEST 0035 DSConfigurati I DSRA8205I: JDBC driver name : Oracle JDBC driver 10/14/10 20:03:13:162 CEST 0035 DSConfigurati I DSRA8206I: JDBC driver version : 11.2.0.1.0 10/14/10 20:03:13:193 CEST 0035 DSConfigurati I DSRA8030I: Successfully connected to DataSource, with 1 warnings. I've written some tests to check whether this attribute works at all, using basic JDBC API, see attached Java code. The question is how to get this activated within Websphere Application Server 6.1. Any ideas or solutions to that? Many thanks in advance! Regards, Bernd To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14542631 Unsubscribe via the binocular icon on the web
WebSphere Application Server: not receiving topic subscriptions on all nodes in a cluster
Author: kim.nel...@ca.com Message: We have attempted to create the configuration represented in Figure 5 of the document at: http://publib.boulder.ibm.com/infocenter/wasinfo/fep/index.jsp?topic=/com.ibm.websphere.pmc.nd.multiplatform.doc/concepts/cjn_mdb_endpt_overview.html So, we have one cluster which contains the application server nodes and a second cluster which contains the message engine. The activation spec for each MDB on each application server node contains a target of the message engine on the second cluster. It is clear that our configuration is not complete, since we are published the subscription on one node but never receiving it on the others. I turned on WAS topic tracing and note that the publish entry is as follows: 8/30/10 16:03:57:627 CDT 0037 JmsTopicPubli publish(Message) [:] Entry 8/30/10 16:03:57:627 CDT 0037 JmsTopicPubli 3 [:] message : JMSMessage class: jms_map JMSType: null JMSDeliveryMode: 2 JMSExpiration:0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: -1 JMSCorrelationID: null JMSDestination: null JMSReplyTo: null JMSRedelivered: false MessageFormat: 1.0 env: 2 Source: 31eaec17-c65896ff-261be8e5-db8c56b Command: flushaztype objecttype: PROVISIONING ROLE aztype: Ownership These nulls don't look very nice and I am hoping that they might yield a clue about what is wrong with our configuration. I would really appreciate some help on this subject. Thanks very much To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14526735 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Hypervisor V7 Standalone Deployment, Activation and Troubleshooting Aug 18
Author: josephlam Message: You are invited to attend a webcast on the topic of WebSphere Application Server Hypervisor V7 Standalone Deployment, Activation and Troubleshooting. On 18 August 2010 at 11:00 AM EDT, a WebSphere Support Technical Exchange presentation on WebSphere Application Server Hypervisor V7 Standalone Deployment, Activation and Troubleshooting will be delivered by Ganesan Karuppaiah and Robert Boretti, subject matter experts. An open question and answer session will follow the presentation. WebSphere Application Server Hypervisor Edition contains the SLES Linux OS and WebSphere Application Server which are pre-configured for runtime, making initial setup fast and easy. This session focuses on the deployment, activation and troubleshooting of WAS Hypervisior Edition. Level of Difficulty: Intermediate Plan to join the meeting 10 minutes early. Presentations typically last for 30-45 minutes followed by a question and answer session. For more information and details on how to participate in this and other free WebSphere Support Technical Exchanges click here (http://www.ibm.com/software/websphere/support/supp_tech.html). Date: August 18, 2010 Time: 11:00 AM EDT For dial-in numbers and web conferencing information, please visit: http://www-01.ibm.com/software/websphere/support/TE/techex_F660427O32940H34.html We look forward to your participation in this webcast session! To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14495135 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Exception thrown : java.lang.VerifyError: javax/xml/bind/JAXBElement.lt;initgt;
Author: chandu$ Message: while deploying my ear in websphere 6.1 in windows system it is working fine, but same ear file when i am deployinh in Unix, i am getting the below error, 8/3/10 3:48:33:251 MST 002c ServletWrappe E CWSRV0068E: Uncaught exception thrown in one of the service methods of the servlet: ActionServlet. Exception thrown : java.lang.VerifyError: javax/xml/bind/JAXBElement.lt;initgt;(Ljavax/xml/namespace/QName;Ljava/lang/Class;Ljava/lang/Class;Ljava/lang/Object;)V at com.wsip.ObjectFactory.createAuthorizeGCAGXMLMessage(ObjectFactory.java:313) at com.utils.xml.CommonMarshalingUtility.convertObjectToGNSXML(CommonMarshalingUtility.java:142) at com.utils.xml.GNSXmlUtility.createXML(TestXmlUtility.java:140) There is already web services pack in both windows and unix also please help me ASAP Thanks in advance..!! To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14493692 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: How to get the JMX notification that an MDB activator stopped in a SLSB?
Author: denisF Message: Lalit, The reference you give is for WAS v5 As stated in the WAS v7 infocenter, a JMX notification is emit by the JCA MBean : After msg1 is unhidden for the fourth time, rolled back and rehidden, the Sequential failed message threshold is reached and the MDB stops automatically. A JMX notification is emitted by the JCA MBean and a log entry alerts the system administrator that the MDB has stopped. For example, look here: http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.pmc.express.doc/tasks/tjn_mdb_0001_Ex4.html I'm wondering if it is a security problem, the principal running the code lacking the rights to see the notification To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14489302 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: How to get the JMX notification that an MDB activator stopped in a SLSB?
Author: Lalit_Agarwalla Message: The JCAMessageEndpoint MBean does not explicitly emit any notification about state change. Rather, it logs an Info message using RAS Logging service whenever there is a state transition. The RAS Logging service automatically circulates JMX notification for each Info message it is given. Hence, the client needs to listen for Info messages on RAS Logging service as explained at the link given below. http://www.ibm.com/developerworks/websphere/techjournal/0304_lauzon/lauzon.html You will need to use the RasLoggigService mbean to get notifications: something like ObjectName queryMBean = new ObjectName(WebSphere:type=RasLoggingService,process=server1,*); We can filter the notification up to some extent, still there are too many notifications generated. NotificationFilterSupport filter = new NotificationFilterSupport(); filter.enableType(NotificationConstants.TYPE_RAS_WARNING); adminClient.addNotificationListener(rasMBean, listener, filter, null); This filter show only the WARNING logging entries. Still there will be too many notifications. This is an ugly way for a simple requirement. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14488110 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Error: com/sun/faces/util/Util.verifyFactories
Author: SanjeevSinha Message: Hi , I am also facing the same issue.trying to deploy axis but with EJB deployment it is failing. Without EJB deployment it is working fine.Same is working with WAS 6.1 *** ERROR ***: Wed Jul 07 20:38:48 GMT+05:30 2010 Error loading nested archive: axis2.war *** ERROR ***: Wed Jul 07 20:38:48 GMT+05:30 2010 java.lang.NullPointerException org.eclipse.core.commands.ExecutionException: at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.importEar(BatchExtension.java:1095) at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.runEarDeploy(BatchExtension.java:354) at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.access$1(BatchExtension.java:349) at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension$RunDeploy.run(BatchExtension.java:332) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1782) at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension$RunDeploy.execute(BatchExtension.java:297) at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.run(BatchExtension.java:260) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:574) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:195) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) at com.ibm.etools.ejbdeploy.batch.impl.BootLoaderLoader.run(BootLoaderLoader.java:484) at com.ibm.etools.ejbdeploy.batch.impl.BatchDeploy.execute(BatchDeploy.java:100) at com.ibm.etools.ejbdeploy.EJBDeploy.execute(EJBDeploy.java:104) at com.ibm.etools.ejbdeploy.EJBDeploy.main(EJBDeploy.java:334) Jul 7, 2010 8:38:48 PM com.ibm.etools.ejbdeploy.logging.Logger logInfo INFO: project name is smcfs.ear Jul 7, 2010 8:38:49 PM com.ibm.etools.ejbdeploy.logging.Logger logInfo INFO: source path is /data/Lowes/WebSphere/profiles/AppSrv02/wstemp/117481/upload/smcfs.ear An unexpected exception was thrown. Halting execution. Shutting down workbench. Error importing: . com.ibm.etools.ejbdeploy.EJBDeploymentException (Error importing: .) org.eclipse.core.commands.ExecutionException: at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.importEar(BatchExtension.java:1095) at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.runEarDeploy(BatchExtension.java:354) at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.access$1(BatchExtension.java:349) at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension$RunDeploy.run(BatchExtension.java:332) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1782) at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension$RunDeploy.execute(BatchExtension.java:297) at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.run(BatchExtension.java:260) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:574) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:195) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) at com.ibm.etools.ejbdeploy.batch.impl.BootLoaderLoader.run(BootLoaderLoader.java:484) at
WebSphere Application Server: Re: Resource assignmen type javax.activation.DataSource
Author: Feral Message: Thanks nikhilpen i have two scope of i have javax.SQL.DataSource and javax.activation.DataSource Scope i can find all my DataSource in SQL but i dont find it on activation.DataSource To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14482936 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Resource assignmen type javax.activation.DataSource
Author: Feral Message: I have an application which is deployed on WAS 5.1 While deploying the same application on WAS 6.1.0.31 i do receive this message ADMA0115W: Resource assignment of name BillingDS and type javax.activation.DataSource, with JNDI name jdbc/BillingDS is not found within scope of module berkelysne with URI berkelysne.war,WEB-INF/web.xml deployed to target WebSphere:cell=WASDRNetwork,node=WASDR,server=berkelycare_sne. How do i resolve it ? To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14482666 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Resource assignmen type javax.activation.DataSource
Author: nikhilpen Message: The datasource is at a scope that is not visible to you application. Check the scope of the datasource. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14482760 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: How to get the JMX notification that an MDB activator stopped in a SLSB?
Author: Sadhana Message: Hi - Did you manage to find a solution to this issue ? Sadhana To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14479877 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: How to get the JMX notification that an MDB activator stopped in a SLSB?
Author: denisF Message: Unfortunately not yet.. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14480150 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: WAS 7 Network Deployment fails in Installation Verification
Author: Akash Bharti Message: That sound to be a strange problem. My say is Open a PMR Thanks Akash To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14478763 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: WAS 7 Network Deployment fails in Installation Verification
Author: K2Dev Message: Case CLOSED. I tried to install WAS 6.1 instead, but it failed with the same error. Still lsof nor netstat could not show anything using the port that caused the problem. I scrapped the Red Hat installation, and used another, which I knew worked with WAS. Both installed from same Red Hat media, but the latter one did not have RHN, so no errata or updates after the installation. And it works. Only different that I can think is the updates... But seems very strange. The port was not in use! But now I have a working system, I just hope it stays that way when the machine is connected to RHN some day... To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14478253 Unsubscribe via the binocular icon on the web
WebSphere Application Server: How to get the JMX notification that an MDB activator stopped in a SLSB?
Author:
denisF
Message:
In the infocenter, in section Example 4: Automatically stopping an MDB when no
exception destination is specified, it is stated that when an MDB activator is
stopped, A JMX notification is emitted by the JCA MBean and a log entry alerts
the system administrator that the MDB has stopped
When this happend we see in the log the following message:
ActivationSpe I J2CA0524I: The Message Endpoint for ActivationSpec
jms/act/tp_commandes (com.ibm.ws.sib.api.jmsra.impl.JmsJcaActivationSpecImpl)
and MDB Application
TitulairesPermis#TitulairesPermisEJB.jar#TestConsumerControleurImpl is
deactivated.
Fine.
Now we want to write a stateless session been with a method that will catch the
JMX notification when this event arises
Here is the code :
@Stateless
public class TestJMXImpl extends AbstractControleur implements TestJMX,
NotificationListener, Serializable {
private static final long serialVersionUID = 1L;
public void init() {
System.out.println(init);
AdminService as = AdminServiceFactory.getAdminService();
try {
ObjectName queryName = new
ObjectName(WebSphere:*,type=J2CMessageEndpoint);
Setlt;ObjectNamegt; s = as.queryNames(queryName, null);
for (ObjectName objectName : s) {
System.out.println(name= +
objectName.getCanonicalKeyPropertyListString());
as.addNotificationListener(objectName, this, null, null);
}
} catch (...) {
...
}
}
public void handleNotification(Notification n, Object handback) {
System.out.println(* Notification received at + new Date().toString());
}
}
We call the init method and the MBean if found :
name=ActivationSpec=jms/act/tp_commandes,J2CResourceAdapter=SIB JMS Resource
Adapter,J2EEApplication=TitulairesPermis,J2EEServer=server1,MessageDrivenBean=TitulairesPermis#TitulairesPermisEJB.jar#TestConsumerControleurImpl,Server=server1,cell=pt6704Node01Cell,j2eeType=JCAMessageEndpoint,mbeanIdentifier=cells/pt6704Node01Cell/nodes/pt6704Node01/servers/server1/resources.xml#J2CResourceAdapter_1223569418301#TitulairesPermis#TitulairesPermisEJB.jar#TestConsumerControleurImpl_J2CMessageEndpoint,name=TitulairesPermis#TitulairesPermisEJB.jar#TestConsumerControleurImpl_J2CMessageEndpoint,node=pt6704Node01,platform=dynamicproxy,process=server1,spec=1.0,type=J2CMessageEndpoint,version=7.0.0.9
but the handleNotification() method is never called if we pause/resume the
activator
Nothing in the logs, nothing in FFDC...
Any idea?
To respond to this post, please click the following link:
http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14475441
Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: WAS 7 Network Deployment fails in Installation Verification
Author: BrettS741 Message: You can quickly go into the config and change the 8880 port to something else and attempt to start the server again. This would rule out if it's a problem with something using that port truely or not. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14464584 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: WAS 7 Network Deployment fails in Installation Verification
Author: K2Dev Message: Indeed. I was just about to write about that. I changed it to 8881, and the error stays the same, only the port number changes in the error message. I also emptied all temp files # rm -rf /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/wstemp/* # rm -rf /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/temp/* # rm -rf /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/temp/* I was also told to empty tranlog folder, but there is no such folder or file. Really strange. # cat /etc/issue Red Hat Enterprise Linux Server release 5.5 (Tikanga) Has anyone managed to install WAS 7 in this version of Red Hat? To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14464606 Unsubscribe via the binocular icon on the web
WebSphere Application Server: WAS 7 Network Deployment fails in Installation Verification
Author: K2Dev Message: My setup is a follows: * Debian Lenny Linux (amd64) as a Host OS for VMware 2.0 Server. * Red Hat EL 5.5 (amd64) as a Client OS, VMware tools installed. * All libraries installed to Red Hat according to http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.installation.nd.doc/info/ae/ae/tins_linuxsetup.html * WebSphere 7.0 installed with packages that come with Tivoli Identity Manager 5.1 Download Director: C1G35ML.tar.gz C1G36ML.tar.gz C1G35ML.tar.gz C1G35ML.tar.gz extracted to one folder: WAS, the other jars in another folder: WASSUP. WAS installs similarly no matter from which folder I start launcher.sh (I have installed it 5 times now ;)) First Steps Output - Installation Verification: - Server name is:server1 Profile name is:AppSrv01 Profile home is:/opt/IBM/WebSphere/AppServer/profiles/AppSrv01 Profile type is:default Cell name is:everestNode01Cell Node name is:everestNode01 Current encoding is:UTF-8 Start running the following command:/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin/startServer.sh server1 -profileName AppSrv01 ADMU0116I: Tool information is being logged in file /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/startServer.log ADMU0128I: Starting tool with the AppSrv01 profile ADMU3100I: Reading configuration for server: server1 ADMU3028I: Conflict detected on port 8880. Likely causes: a) An instance of the server server1 is already running b) some other process is using port 8880 ADMU3027E: An instance of the server may already be running: server1 ADMU0111E: Program exiting with error: com.ibm.websphere.management.exception.AdminException: ADMU3027E: An instance of the server may already be running: server1 ADMU1211I: To obtain a full trace of the failure, use the -trace option. ADMU0211I: Error details may be seen in the file: /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/startServer.log IVTL0075I: The Installation Verification Tool verification failed. - I am 100% sure that there is nothing listening in port 8880. I have rebooted, and reinstalled WAS now 5 times, done VMWare snapshot reverts and all. One thing sticks to my eye: it does not talk about port 9080, I have seen Installation Verification lists when Googling, and there has been that port mentioned before the Start-part begins. Additional info: /opt/IBM/WebSphere/AppServer/logs/install/log.txt: No errors logged /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/wsadmin.traceout: No errors logged I updated the UpdateInstaller to latest, and installed latest Fix Pack 9 to WebSphere, but nothing changes. /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/startServer.log follows: - Start Display Current Environment Host Operating System is Linux, version 2.6.18-194.el5 Java version = JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr7-20100219_54097 (JIT enabled, AOT enabled) J9VM - 20100219_054097 JIT - r9_20091123_13891 GC - 20100216_AA, Java Compiler = j9jit24, Java VM name = IBM J9 VM was.install.root = /opt/IBM/WebSphere/AppServer user.install.root = /opt/IBM/WebSphere/AppServer/profiles/AppSrv01 Java Home = /opt/IBM/WebSphere/AppServer/java/jre ws.ext.dirs = /opt/IBM/WebSphere/AppServer/java/lib:/opt/IBM/WebSphere/AppServer/classes:/opt/IBM/WebSphere/AppServer/lib:/opt/IBM/WebSphere/AppServer/installedChannels:/opt/IBM/WebSphere/AppServer/lib/ext:/opt/IBM/WebSphere/AppServer/web/help:/opt/IBM/WebSphere/AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime Classpath = /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/properties:/opt/IBM/WebSphere/AppServer/properties:/opt/IBM/WebSphere/AppServer/lib/startup.jar:/opt/IBM/WebSphere/AppServer/lib/bootstrap.jar:/opt/IBM/WebSphere/AppServer/lib/lmproxy.jar:/opt/IBM/WebSphere/AppServer/lib/urlprotocols.jar:/opt/IBM/WebSphere/AppServer/java/lib/tools.jar Java Library path = /opt/IBM/WebSphere/AppServer/java/jre/lib/amd64/default:/opt/IBM/WebSphere/AppServer/java/jre/lib/amd64:/opt/IBM/WebSphere/AppServer/bin::/usr/lib Current trace specification = *=info * End Display Current Environment * 5/6/10 16:53:46:973 EEST ManagerAdmin I TRAS0017I: The startup trace state is *=info. 5/6/10 16:53:47:214 EEST AdminTool A ADMU0128I: Starting tool with the AppSrv01 profile 5/6/10 16:53:47:218 EEST AdminTool A ADMU3100I: Reading configuration for server: server1 5/6/10 16:53:47:684 EEST AdminTool A ADMU3028I: Conflict detected on port 8880. Likely causes: a) An instance of the server server1 is already running b) some other process is using port 8880 5/6/10 16:53:47:699 EEST AdminTool A ADMU3027E: An instance of the server may already be running: server1 5/6/10 16:53:47:701 EEST WsServerLaunc E ADMU3002E: Exception attempting to process
WebSphere Application Server: Re: WAS 7 Network Deployment fails in Installation Verification
Author: K2Dev Message: Correct list of installation files: C1G35ML.tar.gz C1G36ML.tar.gz C1G37ML.tar.gz To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14464187 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: WAS 7 Network Deployment fails in Installation Verification
Author: K2Dev Message: startServer.sh server1 -trace and startServer.log with trace now attached to this message. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14464189 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: WAS 7 Network Deployment fails in Installation Verification
Author: K2Dev Message: Current installation mode: Application Server Admin Security: No To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14464191 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: WAS 7 Network Deployment fails in Installation Verification
Author: ericdu Message: Looks server1 is up running. Can you check ps -ef | grep server? and lsof | grep 8880 To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14464204 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: WAS 7 Network Deployment fails in Installation Verification
Author: K2Dev Message: r...@everest ~# ps -ef | grep server root 3040 1 0 15:23 ?00:00:00 /usr/bin/hidd --server root 3436 1 0 15:23 ?00:00:00 /usr/libexec/gam_server root 3552 1 0 15:24 ?00:00:00 /usr/libexec/bonobo-activation-server --ac-activate --ior-output-fd=16 root 4783 17347 0 17:43 pts/200:00:00 grep server r...@everest ~# lsof | grep 8880 auditd 2339 root txt REG 253,0 1630643888071 /sbin/auditd audispd2341 root txt REG 253,0887363888069 /sbin/audispd pam_times 3610 root txt REG 253,0141123888093 /sbin/pam_timestamp_check No problems here. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14464196 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: WAS 7 Network Deployment fails in Installation Verification
Author: Sunit Message: Pls check netstat -an | grep 8880 Do you have any ports reserved in /etc/services? - Sunit To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14464339 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: WAS 7 Network Deployment fails in Installation Verification
Author: K2Dev Message: Pls check netstat -an | grep 8880 This should not give much more info compared to the lsof method tried earlier, but here is goes: - r...@everest ~# netstat -an | grep 8880 r...@everest ~# - Ports reserved in /etc/services? AFAIK those do not *reserve* anything, they just*descrive ports. But. - # grep -w 8880 /etc/services r...@everest ~# grep -w 8880 /etc/services cddbp-alt 8880/tcp# CDDBP cddbp-alt 8880/udp# CDDBP - After commenting out those lines in services: - r...@everest ~# /opt/IBM/WebSphere/AppServer/bin/startServer.sh server1 ADMU0116I: Tool information is being logged in file /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/startServer.log ADMU0128I: Starting tool with the AppSrv01 profile ADMU3100I: Reading configuration for server: server1 ADMU3028I: Conflict detected on port 8880. Likely causes: a) An instance of the server server1 is already running b) some other process is using port 8880 ADMU3027E: An instance of the server may already be running: server1 ADMU0111E: Program exiting with error: com.ibm.websphere.management.exception.AdminException: ADMU3027E: An instance of the server may already be running: server1 ADMU1211I: To obtain a full trace of the failure, use the -trace option. ADMU0211I: Error details may be seen in the file: /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/startServer.log - Thanks for help, but no joy :( To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14464360 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: WAS 7 Network Deployment fails in Installation Verification
Author: K2Dev Message: Like something launched the SOAP service twice in WAS, and the error comes from that. But the trace did not show anything like that. This is really strange. The 8880 port is for SOAP. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14464364 Unsubscribe via the binocular icon on the web
WebSphere Application Server: how to activate Garbage Colletcor
Author: 90NE12345678 Message: Hi all Can any help me to activate garbage collector on WAS 6.1 Thank you in advance Regards To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14462736 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: how to activate Garbage Colletcor
Author: Sunit Message: Garbage collector always runs in JVM, there no manual start/stop for GC. If you want to see the log of when GC executes, etc then look for verbose GC. - Sunit To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14462844 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: how to activate Garbage Colletcor
Author: 90NE12345678 Message: Ok thank you so much To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14462889 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Server hangs at starting activation specifications.
Author: mamwl1 Message: Hi Mikael. Can you tell me a bit more about your scenario please? What version (including fix packs) of WAS are you using and on which platform. Also which version of WMQ are you using and which platform. I see that you mentioned queues, is that queue based pub/sub messaging or point to point? Regarding your question, there is no way of setting a 'start-up state' for an activation specification. I don't think changing start up ordering will help either. Can you also provide a stack trace for your hung thread please. Cheers, Matt. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14413859 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Server hangs at starting activation specifications.
Author: Hamnedalen Message: I have problem to start one of my application that uses activation specifications to MQ queues. The problems seems to be that the activation specifications starts, but the part or the application that should handle the messeges coming on the queues isn't started, and the whole server hangs. If I wait a while, the messeges ot detected threads hangs comes into the SystemOut.log. Do any of you know if, and how, you can start the app with the activation specifications disabled, or if you can change the start order, so the activation specifications are started at the end of the application. Regards /Mikael. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14413318 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Activation Spec + MQ : How to stop on failure?
Author: p_jain Message: I guess WAS 7.0 stop MDB on failure if under activation spect setting, Stop endpoint if message delivery fails is checked. Not sure if this is what you looking for. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14347490 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Activation Spec + MQ : How to stop on failure?
Author: mamwl1 Message: Hi Mike. The ability for a WMQ activation spec to pause on transaction rollback was not added until WAS 7.0.0.5. Throwing a runtime exception in onMessage should have the desired effect though. Exactly which level of WAS are you running with? My advice would be to move to 7.0.0.7 which should be available shortly. Cheers, Matt. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14340749 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Activation Spec + MQ : How to stop on failure?
Author: Mike.Finn Message: Matt, I was afraid that was going to be the answer! We are currently on 7.0.0.3. Upgrading to 5 or 7 may not be possible in our timeframe, but it sounds like we may not have a choice, since listener port + EJB3 fix is in 7.0.0.5 as well. Thanks for the info. Mike To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14340782 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Re: Start Application When Message Endpoint Activation Fails
Author: mamwl1 Message: Hi. The WebSphere MQ messaging provider doesn't have that capability, and as far as I (and my colleagues) are aware neither does WAS. Regards, Matt. To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14340177 Unsubscribe via the binocular icon on the web
WebSphere Application Server: Activation Spec + MQ : How to stop on failure?
Author: Mike.Finn Message: WAS 7, with WMQ (6.x) based Activation Spec. I have an MDB connected to the AS and want to stop the listener for it on a programmatically detected failure (by setting rollback or unchecked exception), but I have not been able to make this work. It seems I can either get the messages to system exception queue, but that's about it. We need to preserve order and I can't have some messages in the sys exc queue and the MDB start working again (connecting to another system) and processing messages without the 'failed' messages first. I know this is possible with a listener port, but there is an open issue with WAS requiring 7.0.0.5 upgrade (EJB3 MDB w/ 'deprecated' listener port), which is not an option for us at this point. http://www-01.ibm.com/support/docview.wss?rs=180uid=swg1PK86005 Has anyone gotten this to work? Thanks, Mike To respond to this post, please click the following link: http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14340557 Unsubscribe via the binocular icon on the web
