voyent
AHS and WebSphere Configuration  XML
Forum Index -> Async HTTP Server
Author Message
ankilpatel001

Joined: 12/Nov/2008 00:00:00
Messages: 11
Offline


Hello,

The environment, we're using, is:

IBM WAS V6.1.0.17
IBM IHS
Async HTTP Server

The "async-http-server.war" was deployed on the cluster.

The Systemout.log for the cluster is giving following error:

[11/12/08 10:03:55:156 EST] 00000029 SibMessage I [Name of Bus:#######Bus] CWSIS1588I: The file store has started successfully.
[11/12/08 10:03:58:292 EST] 0000002f WebContainer A SRVE0161I: IBM WebSphere Application Server - Web Container. Copyright IBM Corp. 1998-2006
[11/12/08 10:03:58:310 EST] 0000002f WebContainer A SRVE0162I: Servlet Specification Level: 2.4
[11/12/08 10:03:58:327 EST] 0000002f WebContainer A SRVE0163I: Supported JSP Specification Level: 2.0
[11/12/08 10:03:59:201 EST] 0000002f WebContainer A SRVE0239I: Extension Factory [class com.ibm.ws.webcontainer.extension.ExtHandshakeVHostExtensionFactory] was registered successfully.
[11/12/08 10:03:59:205 EST] 0000002f WebContainer A SRVE0240I: Extension Factory [class com.ibm.ws.webcontainer.extension.ExtHandshakeVHostExtensionFactory] has been associated with patterns [VH:_WS_EH* ].
[11/12/08 10:04:05:849 EST] 0000002e ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC opened incident stream file /opt/WebSphere/AppServer/profiles/%%%%%test-004/logs/ffdc/#####_TESTA_c1_0000002e_08.11.12_10.04.05_0.txt
[11/12/08 10:04:05:889 EST] 0000002e ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file /opt/WebSphere/AppServer/profiles/%%%%%test-004/logs/ffdc/#####_TESTA_c1_0000002e_08.11.12_10.04.05_0.txt
[11/12/08 10:04:05:903 EST] 0000002e JPAPUnitInfo E CWWJP0009E: The server cannot create an EntityManangerFactory factory for the JPATopLinkProductOperationalPU persistent unit from the oracle.toplink.essentials.PersistenceProvider provider in jar:file:/opt/WebSphere/AppServer/profiles/%%%%%test-004/installedApps/WAS6TEST%%%%%001/#####_TESTAProductNavigationEAR.ear/ProductNavigation.war/WEB-INF/lib/jpatoplinkproductoperational.jar!/ module.
[11/12/08 10:04:06:149 EST] 0000002f WebGroup A SRVE0169I: Loading Web Module: Async Server.
[11/12/08 10:04:08:657 EST] 00000029 SibMessage I [#####Bus:#####_TESTA.000-#####Bus] CWSIP0212I: Messaging engine #####_TESTA.000-#####Bus on bus #####Bus is starting to reconcile the WCCM destination and link configuration.
[11/12/08 10:04:08:890 EST] 0000002f ContextEventR I com.icesoft.faces.util.event.servlet.ContextEventRepeater contextInitialized Asynchronous HTTP Service available: true
[11/12/08 10:04:09:006 EST] 00000029 SibMessage I [#####Bus:#####_TESTA.000-#####Bus] CWSIP0213I: Messaging engine #####_TESTA.000-#####Bus on bus #####Bus has finished reconciling the WCCM destination and link configuration.
[11/12/08 10:04:09:067 EST] 0000002f JMSAdapter I com.icesoft.net.messaging.jms.JMSAdapter <init> Messaging Properties (web.xml): jboss.properties
[11/12/08 10:04:09:412 EST] 00000029 SibMessage I [#####Bus:#####_TESTA.000-#####Bus] CWSID0016I: Messaging engine #####_TESTA.000-#####Bus is in state Started.
[11/12/08 10:04:09:528 EST] 0000002f JMSAdapter I com.icesoft.net.messaging.jms.JMSAdapter initialize Trying JMS Environment:
java.naming.provider.url = localhost:1099
java.naming.factory.initial = org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs = org.jboss.naming:org.jnp.interfaces

[11/12/08 10:04:09:556 EST] 0000002f JMSAdapter E com.icesoft.net.messaging.jms.JMSAdapter initialize Failed JMS Environment: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory
[11/12/08 10:04:09:559 EST] 0000002f MessagingCont E com.icesoft.faces.util.event.servlet.MessagingContextEventPublisher setUpMessageServiceClient

Failed to subscribe to topic: icefacesContextEventTopic
Exception message: javax.naming.NoInitialContextException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory [Root exception is java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory]
Exception cause: javax.naming.NoInitialContextException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory [Root exception is java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory]

The icefaces-ahs.jar is included in the deployment, but the JMS topics are not
configured correctly on the application server. If you intended to use the
Asynchronous HTTP Server (AHS), please refer to the ICEfaces Developer's Guide
for instructions on how to configure the JMS topics on the application server.
If you did not intend to use AHS, please remove the icefaces-ahs.jar from your
deployment and try again.

[11/12/08 10:04:09:850 EST] 0000002f JMSAdapter I com.icesoft.net.messaging.jms.JMSAdapter <init> Messaging Properties (web.xml): jboss.properties
[11/12/08 10:04:10:275 EST] 0000002f JMSAdapter I com.icesoft.net.messaging.jms.JMSAdapter initialize Trying JMS Environment:
java.naming.provider.url = localhost:1099
java.naming.factory.initial = org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs = org.jboss.naming:org.jnp.interfaces

[11/12/08 10:04:10:281 EST] 0000002f JMSAdapter E com.icesoft.net.messaging.jms.JMSAdapter initialize Failed JMS Environment: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory
[11/12/08 10:04:10:282 EST] 0000002f MessageServic E com.icesoft.faces.async.common.messaging.MessageService subscribe

Failed to subscribe to topic: icefacesContextEventTopic
Exception message: javax.naming.NoInitialContextException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory [Root exception is java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory]
Exception cause: javax.naming.NoInitialContextException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory [Root exception is java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory]

The icefaces-ahs.jar is included in the deployment, but the JMS topics are not
configured correctly on the application server. If you intended to use the
Asynchronous HTTP Server (AHS), please refer to the ICEfaces Developer's Guide
for instructions on how to configure the JMS topics on the application server.
If you did not intend to use AHS, please remove the icefaces-ahs.jar from your
deployment and try again.

[11/12/08 10:04:10:781 EST] 0000002f JMSAdapter I com.icesoft.net.messaging.jms.JMSAdapter initialize Trying JMS Environment:
java.naming.provider.url = localhost:1099
java.naming.factory.initial = org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs = org.jboss.naming:org.jnp.interfaces

[11/12/08 10:04:10:805 EST] 0000002f JMSAdapter E com.icesoft.net.messaging.jms.JMSAdapter initialize Failed JMS Environment: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory
[11/12/08 10:04:10:808 EST] 0000002f MessageServic E com.icesoft.faces.async.common.messaging.MessageService subscribe

Failed to subscribe to topic: icefacesResponseTopic
Exception message: javax.naming.NoInitialContextException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory [Root exception is java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory]
Exception cause: javax.naming.NoInitialContextException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory [Root exception is java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory]

The icefaces-ahs.jar is included in the deployment, but the JMS topics are not
configured correctly on the application server. If you intended to use the
Asynchronous HTTP Server (AHS), please refer to the ICEfaces Developer's Guide
for instructions on how to configure the JMS topics on the application server.
If you did not intend to use AHS, please remove the icefaces-ahs.jar from your
deployment and try again.




Please suggest any solution. Please let me know if you need more info.

Thanks in advance,

-ankil
deryk.sinotte


Joined: 26/Oct/2004 00:00:00
Messages: 1008
Offline


Have you configured the JMS Topics and ConnectionFactory for WebSphere as outlined in the Developer's Guide?

Deryk Sinotte
Team Lead
ICEsoft Technologies, Inc.
ankilpatel001

Joined: 12/Nov/2008 00:00:00
Messages: 11
Offline


Yes, we have configured the JMS Topics and ConnectionFactory for WebSphere.

But the problem, I learned from the logs, is we haven't configured the "web.xml" of "async-http-server.war" for WebSphere. So, we have modified the "web.xml" for WebSphere and redeployed the "async-http-server.war". And this time the only error we are getting it pasted below.


[11/12/08 15:14:05:041 EST] 00000029 JPAPUnitInfo E CWWJP0009E: The server cannot create an EntityManangerFactory factory for the JPATopLinkProductOperationalPU persistent unit from the oracle.toplink.essentials.PersistenceProvider provider in jar:file:/opt/WebSphere/AppServer/profiles/####test-004/installedApps/WAS6TEST####001/@@@@@@@@.ear/@@@@@@@@.war/WEB-INF/lib/jpatoplinkproductoperational.jar!/ module.


Please help us out. Let me know if need any info.

Thanks in advance,

-ankil
ankilpatel001

Joined: 12/Nov/2008 00:00:00
Messages: 11
Offline


.
ankilpatel001

Joined: 12/Nov/2008 00:00:00
Messages: 11
Offline


.
ankilpatel001

Joined: 12/Nov/2008 00:00:00
Messages: 11
Offline


.
deryk.sinotte


Joined: 26/Oct/2004 00:00:00
Messages: 1008
Offline


I was about to post the following when I saw that you already figured that part out. The error you are seeing now doesn't look related to ICEfaces.

-----

What version of ICEfaces are you using? The other thing that you'll likely have to do is specify which properties file AHS and you application should use. Right now, from your log, it appears to be looking for JBoss:

Code:
 [11/12/08 10:04:09:528 EST] 0000002f JMSAdapter I com.icesoft.net.messaging.jms.JMSAdapter initialize Trying JMS Environment:
 java.naming.provider.url = localhost:1099
 java.naming.factory.initial = org.jnp.interfaces.NamingContextFactory
 java.naming.factory.url.pkgs = org.jboss.naming:org.jnp.interfaces
 


There is a section in the Developer's Guide called Configuring the JMS Provider and it explains how to set the configuration property for your server (WebSphere in a cluster):

Code:
<context-param> 
     <param-name>com.icesoft.net.messaging.properties</param-name> 
     <param-value>websphere_ha.properties</param-value> 
 </context-param>


This parameter needs to be set in both the async-http-server.war and your application .war so that they use the correct JMS settings for finding the ConnectionFactory and JMS Topics via JNDI.

Deryk Sinotte
Team Lead
ICEsoft Technologies, Inc.
ankilpatel001

Joined: 12/Nov/2008 00:00:00
Messages: 11
Offline


Thanks for the reply.

Let me talk to the developers about the recent error.

Thanks again,
-ankil
ankilpatel001

Joined: 12/Nov/2008 00:00:00
Messages: 11
Offline


I've deployed "auctionMonitor.war" in my WebSphere cluster.
It's in the same environment:
IBM WAS V6.1.0.17
IBM IHS
Async HTTP Server

When I hit the url, in the SystemOut.log, we are getting:

URL: http://######.#####.com/auctionMonitor/index.jsp



Logs:

[11/13/08 12:55:36:169 EST] 00000057 ServletWrappe I SRVE0242I: [######AauctionMonitor_war] [/auctionMonitor] [/index.jsp]: Initialization successful.
[11/13/08 12:55:36:293 EST] 00000057 AsyncServerDe I com.icesoft.faces.webapp.http.core.AsyncServerDetector <init> Asynchronous HTTP Service available: false
[11/13/08 12:55:36:296 EST] 00000057 AsyncServerDe I com.icesoft.faces.webapp.http.core.AsyncServerDetector <init> Adapting to Send Updated Views environment.
[11/13/08 12:55:36:351 EST] 00000057 EnvironmentAd I com.icesoft.faces.webapp.http.servlet.EnvironmentAdaptingServlet <init> GlassFish ARP available: false
[11/13/08 12:55:36:354 EST] 00000057 EnvironmentAd I com.icesoft.faces.webapp.http.servlet.EnvironmentAdaptingServlet <init> Jetty ARP available: false
[11/13/08 12:55:36:357 EST] 00000057 EnvironmentAd I com.icesoft.faces.webapp.http.servlet.EnvironmentAdaptingServlet <init> Adapting to Thread Blocking environment
[11/13/08 12:55:40:398 EST] 00000057 RenderHub I com.icesoft.faces.async.render.RenderHub createScheduledService scheduled render service created:
core pool size : 5
[11/13/08 12:55:41:426 EST] 00000058 RenderHub I com.icesoft.faces.async.render.RenderHub createCoreService core render service created:
core pool size : 10
max pool size : 15
keep alive time: 300000



Does these logs look good? The developer team is reporting that "Ajax Push" is not working. Can you suggest anything from this logs?

Please let me know if you need additional info.


Thanks in advance,

-ankil
ankilpatel001

Joined: 12/Nov/2008 00:00:00
Messages: 11
Offline


Some new entries in the log:

[11/13/08 13:44:36:740 EST] 0000005e ServletWrappe E SRVE0068E: Uncaught exception thrown in one of the service methods of the servlet: Blocking Servlet. Exception thrown : java.lang.IllegalStateException: Session not active
at com.ibm.ws.webcontainer.httpsession.SessionData.getLastAccessedTime(SessionData.java:424)
at com.ibm.ws.webcontainer.httpsession.HttpSessionFacade.getLastAccessedTime(HttpSessionFacade.java:84)
at com.icesoft.faces.webapp.http.servlet.SessionDispatcher$Monitor.<init>(SessionDispatcher.java:238)
at com.icesoft.faces.webapp.http.servlet.SessionDispatcher$Monitor.<init>(SessionDispatcher.java:232)
at com.icesoft.faces.webapp.http.servlet.SessionDispatcher.notifySessionInitialized(SessionDispatcher.java:110)
at com.icesoft.faces.webapp.http.servlet.SessionDispatcher.notifyIfNew(SessionDispatcher.java:63)
at com.icesoft.faces.webapp.http.servlet.SessionDispatcher.service(SessionDispatcher.java:52)
at com.icesoft.faces.webapp.http.servlet.PathDispatcher$Matcher.serviceOnMatch(PathDispatcher.java:52)
at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:29)
at com.icesoft.faces.webapp.http.servlet.MainServlet.service(MainServlet.java:82)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.icesoft.faces.webapp.xmlhttp.BlockingServlet.service(BlockingServlet.java:46)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1076)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:550)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:486)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:90)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:744)
at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1455)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:115)
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.HttpICLReadCallback.complete(HttpICLReadCallback.java:102)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)

[11/13/08 13:44:36:782 EST] 0000005e ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC opened incident stream file /######.txt
[11/13/08 13:44:36:888 EST] 0000005e ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file /######.txt
[11/13/08 13:44:36:937 EST] 0000005e LocalTranCoor E WLTC0017E: Resources rolled back due to setRollbackOnly() being called.
[11/13/08 13:44:36:960 EST] 0000005e WebApp E [Servlet Error]-[Blocking Servlet]: java.lang.IllegalStateException: Session not active
at com.ibm.ws.webcontainer.httpsession.SessionData.getLastAccessedTime(SessionData.java:424)
at com.ibm.ws.webcontainer.httpsession.HttpSessionFacade.getLastAccessedTime(HttpSessionFacade.java:84)
at com.icesoft.faces.webapp.http.servlet.SessionDispatcher$Monitor.<init>(SessionDispatcher.java:238)
at com.icesoft.faces.webapp.http.servlet.SessionDispatcher$Monitor.<init>(SessionDispatcher.java:232)
at com.icesoft.faces.webapp.http.servlet.SessionDispatcher.notifySessionInitialized(SessionDispatcher.java:110)
at com.icesoft.faces.webapp.http.servlet.SessionDispatcher.notifyIfNew(SessionDispatcher.java:63)
at com.icesoft.faces.webapp.http.servlet.SessionDispatcher.service(SessionDispatcher.java:52)
at com.icesoft.faces.webapp.http.servlet.PathDispatcher$Matcher.serviceOnMatch(PathDispatcher.java:52)
at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:29)
at com.icesoft.faces.webapp.http.servlet.MainServlet.service(MainServlet.java:82)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.icesoft.faces.webapp.xmlhttp.BlockingServlet.service(BlockingServlet.java:46)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1076)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:550)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:486)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:90)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:744)
at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1455)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:115)
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.HttpICLReadCallback.complete(HttpICLReadCallback.java:102)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)

[11/13/08 13:44:51:742 EST] 0000006f SessionDispat E com.icesoft.faces.webapp.http.servlet.SessionDispatcher notifySessionShutdown java.lang.IllegalStateException
[11/13/08 13:44:51:745 EST] 0000006f SessionDispat I com.icesoft.faces.webapp.http.servlet.SessionDispatcher notifySessionShutdown Session already invalidated.
jack.van.ooststroom


Joined: 26/Oct/2004 00:00:00
Messages: 223
Offline


Hi Ankil,

The following snippet from your logs looks concerning:
[11/13/08 12:55:36:293 EST] 00000057 AsyncServerDe I com.icesoft.faces.webapp.http.core.AsyncServerDetector <init> Asynchronous HTTP Service available: false 
Is the icefaces-ahs.jar included in your AuctionMonitor deployment? Please make sure the websphere.properties (in case of a standalone server) or websphere_ha.properties (in case of a cluster) is defined in the AuctionMonitor's web.xml as well.

Regards,

Jack van Ooststroom
Senior Developer
ICEsoft Technologies, Inc.
[Email]
jack.van.ooststroom


Joined: 26/Oct/2004 00:00:00
Messages: 223
Offline


The other two stack traces you included make me wonder how your cluster configuration is setup. Please note that when deploying ICEfaces applications in a clustered environment session affinity is mandatory.

Regards,
Jack...

Jack van Ooststroom
Senior Developer
ICEsoft Technologies, Inc.
[Email]
ankilpatel001

Joined: 12/Nov/2008 00:00:00
Messages: 11
Offline


Hello Jack,

Thanks for the reply.

My problem was solved by changing the "context root" for "async-http-server.war" and "auctionMonitor.war".

The Ajax Push is working for "auctionMonitor.war".

Thanks again,

-ankil
 
Forum Index -> Async HTTP Server
Go to:   
Powered by JForum 2.1.7ice © JForum Team