[JBossCache] - Invalid stream header and other problems
by teknokrat
I have a cluster og two jboss nodes, version 4.0.4GA. They are configured for clustered single sign on. I have set up hibernate to use the TreeCache MBean using PESSIMISTIC locking. Everything work OK as long as the cache mode is LOCAL, but as soon as I set the cache mode to REPL_SYNC/ASYNC I get
2006-12-08 15:34:15,844 WARN [org.jboss.ha.framework.interfaces.HAPartition.nvp:] failed unserializing message buffer (msg=[dst: 228.1.2.3:45566, src: shlnvp01:1626 (2 headers), size = 125 bytes])
| java.io.StreamCorruptedException: invalid stream header
| at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:764)
| at java.io.ObjectInputStream.<init>(ObjectInputStream.java:277)
| at org.jboss.invocation.MarshalledValueInputStream.<init>(MarshalledValueInputStream.java:74)
| at org.jboss.ha.framework.server.HAPartitionImpl.objectFromByteBuffer(HAPartitionImpl.java:155)
| at org.jboss.ha.framework.server.HAPartitionImpl.handle(HAPartitionImpl.java:1071)
| at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:615)
| at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:512)
| at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:326)
| at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.handleUp(MessageDispatcher.java:722)
| at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.access$300(MessageDispatcher.java:554)
| at org.jgroups.blocks.MessageDispatcher$1.run(MessageDispatcher.java:691)
| at java.lang.Thread.run(Thread.java:595)
|
|
|
I have also set jgroups.marshalling.compatible=true to no avail.
I haven't got a clue where to go now or whats actually happening. All other values are on their default values.
thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992273#3992273
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992273
19 years, 4 months
[JBossWS] - CLOSE_WAIT and socket.close() issue
by tgoepferd
Hello,
JBoss_4_0_4_GA date=200605151000
Red Hat Linux 2.6.9-42.ELsmp (i386)
JVM Version: 1.5.0_07-b03 (Sun Microsystems Inc.)
I have a servlet which receives a query and then needs to make a web services query to an external host. Once that host completes processing my query, it calls my web service with the result.
I am having 2 issues when I a client of the external host and I am using the JBoss web services libraries:
1)Overtime, the number of TCP connections in the CLOSE_WAIT state rises until around 1000 and then the processing begins to fail. With the axis library, it has been known for a few years that this issue occurs and the solution in axis has been to call socket.close(). Is there a way to instruct the jboss libraries to close the connection after each call? Or, is there some work around that others have found?
2) At the TCP level, there are times when the initial 3-way handshake takes many seconds because the ACK from the remote host is not received. After about 3 seconds, the SYN is resent. That is much too long for my application. According to Red Hat support, there is not an OS setting that will change that. They say it has to be done within the application. Therefore, it would have to be a change to the jboss libraries that control teh socket connection. Is there a JBoss configuration parameter to change it? Is there any other work around?
I know there is a lot of expertise on this forum, so any help would be greatly appreciated.
Thanks,
Todd Goepferd
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992272#3992272
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992272
19 years, 4 months
[JBoss Seam] - Re: selectItems+ajax4jsf
by gllambi
I test it without the selectItem tag and the same exception is thrown
I'm using seam1.1.0CR2, jboss 4.0.5 with the ejb profile and ajax4jsf-1.0.3 with jsp, not facelets. Also I'am usign my-faces-1.1.4
Here I put the config files component.xml, faces-config.xml and web.xml
| <components>
|
| <component name="org.jboss.seam.core.init">
| <property name="debug">true</property>
| <property name="jndiPattern">seam-validacion/#{ejbName}/local</property>
| <property name="myFacesLifecycleBug">false</property>
| </component>
|
| <component class="org.jboss.seam.core.Microcontainer"
| installed="false" />
|
| <component name="em" class="org.jboss.seam.core.ManagedPersistenceContext">
| <property name="persistenceUnitJndiName">java:/selectItemsEntityManagerFactory</property>
| </component>
|
| <component class="org.jboss.seam.selectitems.SelectItemsConfig">
| <property name="persistenceUnitJndiName">java:/selectItemsEntityManagerFactory</property>
| </component>
|
| </components>
|
| <?xml version="1.0"?>
| <!DOCTYPE faces-config PUBLIC "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.0//EN"
| "http://java.sun.com/dtd/web-facesconfig_1_0.dtd">
| <faces-config>
| <navigation-rule>
| <from-view-id>/view/registro_temp.jsp</from-view-id>
| <navigation-case>
| <from-outcome>exito</from-outcome>
| <to-view-id>/view/ok.jsp</to-view-id>
| </navigation-case>
| </navigation-rule>
| <lifecycle>
| <phase-listener>org.jboss.seam.jsf.SeamPhaseListener</phase-listener>
| </lifecycle>
| </faces-config>
|
| <?xml version="1.0" encoding="UTF-8"?>
|
| <web-app version="2.5"
| xmlns="http://java.sun.com/xml/ns/javaee"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
|
| <!-- Ajax4jsf (must come first!) -->
|
| <filter>
| <display-name>Ajax4jsf Filter</display-name>
| <filter-name>ajax4jsf</filter-name>
| <filter-class>org.ajax4jsf.Filter</filter-class>
| </filter>
|
| <filter-mapping>
| <filter-name>ajax4jsf</filter-name>
| <url-pattern>*.seam</url-pattern>
| </filter-mapping>
|
| <context-param>
| <param-name>org.ajax4jsf.VIEW_HANDLERS</param-name>
| <param-value>org.jboss.seam.ui.facelet.SeamFaceletViewHandler</param-value>
| </context-param>
|
| <!-- Seam -->
|
| <listener>
| <listener-class>org.jboss.seam.servlet.SeamListener</listener-class>
| </listener>
|
| <!-- Propagate conversations across redirects -->
| <filter>
| <filter-name>Seam Redirect Filter</filter-name>
| <filter-class>org.jboss.seam.servlet.SeamRedirectFilter</filter-class>
| </filter>
|
| <filter-mapping>
| <filter-name>Seam Redirect Filter</filter-name>
| <url-pattern>*.seam</url-pattern>
| </filter-mapping>
|
| <filter>
| <filter-name>Seam Exception Filter</filter-name>
| <filter-class>org.jboss.seam.servlet.SeamExceptionFilter</filter-class>
| </filter>
|
| <filter-mapping>
| <filter-name>Seam Exception Filter</filter-name>
| <url-pattern>*.seam</url-pattern>
| </filter-mapping>
|
| <!-- JSF -->
|
| <context-param>
| <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
| <param-value>client</param-value>
| </context-param>
|
| <servlet>
| <servlet-name>Faces Servlet</servlet-name>
| <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
| <load-on-startup>1</load-on-startup>
| </servlet>
|
| <!-- Faces Servlet Mapping -->
| <servlet-mapping>
| <servlet-name>Faces Servlet</servlet-name>
| <url-pattern>*.seam</url-pattern>
| </servlet-mapping>
|
| <!-- MyFaces -->
| <listener>
| <listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class>
| </listener>
|
| <!-- JSF RI -->
| <!--
| <listener>
| <listener-class>com.sun.faces.config.ConfigureListener</listener-class>
| </listener>
| -->
| </web-app>
|
Thanks,
Guzmán
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992260#3992260
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992260
19 years, 4 months