March 2009 - jboss-user - Jboss List Archives

[JBoss Messaging] - Re: Client connection timeout

by jbabad

Thanks. We are using the EAP version. Now I have tried the JBM 1.4.0SP3_CP7 - and replaced the jboss-messaging and jboss-messaging-client jars in the profile's lib directory (i.e. /server/messaging/lib ) Now what I'm seeing is that the second JBoss instance in the cluster is throwing out theses errors every few seconds: | 13:00:52,324 ERROR [GroupMember] Caught Exception in Receiver | java.lang.NullPointerException | at java.io.ByteArrayInputStream.<init>(ByteArrayInputStream.java:89) | at org.jboss.messaging.core.impl.postoffice.GroupMember.readRequest(GroupMember.java:354) | at org.jboss.messaging.core.impl.postoffice.GroupMember.access$1400(GroupMember.java:55) | at org.jboss.messaging.core.impl.postoffice.GroupMember$DataReceiver.receive(GroupMember.java:581) | at org.jgroups.JChannel.up(JChannel.java:1101) | at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:382) | at org.jgroups.stack.ProtocolStack.receiveUpEvent(ProtocolStack.java:398) | at org.jgroups.stack.Protocol.passUp(Protocol.java:520) | at org.jgroups.protocols.pbcast.GMS.up(GMS.java:768) | at org.jgroups.stack.UpHandler.run(Protocol.java:60) | 13:00:52,324 ERROR [UpHandler] UpHandler (GMS) caught exception | java.lang.IllegalStateException | at java.io.ByteArrayInputStream.<init>(ByteArrayInputStream.java:89) | at org.jboss.messaging.core.impl.postoffice.GroupMember.readRequest(GroupMember.java:354) | at org.jboss.messaging.core.impl.postoffice.GroupMember.access$1400(GroupMember.java:55) | at org.jboss.messaging.core.impl.postoffice.GroupMember$DataReceiver.receive(GroupMember.java:581) | at org.jgroups.JChannel.up(JChannel.java:1101) | at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:382) | at org.jgroups.stack.ProtocolStack.receiveUpEvent(ProtocolStack.java:398) | at org.jgroups.stack.Protocol.passUp(Protocol.java:520) | at org.jgroups.protocols.pbcast.GMS.up(GMS.java:768) | at org.jgroups.stack.UpHandler.run(Protocol.java:60) | | Any thoughts on this one? I'm going to try the CP05 patch to see if there's any difference.. Thanks. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215714#4215714 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215714

15 years, 10 months

1
0
0 / 0

[JBoss jBPM] - Event Classes Not Cached - 3.3.1GA

by bradsdavis

I notice a lot of logs around Byte Array on transitions. In the default configuration, are the event classes cached? It looks like it reassembles them per transition. Additionally, it doesnt do this with a subselect or join pattern, which seems to leads to n+1 selects. Is there a way to enable caching over events? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215710#4215710 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215710

15 years, 10 months

1
0
0 / 0

[JBoss Portal] - NPE in PortletManagementHandler.getPortletProperties

by cpage

Hi, I use JBoss 4.2.3 + JBossPortal 2.6.6 (with WSRP). In an admin portlet i add a property to an instance with InstanceDefinition.setProperties(PropertyChange[]) so this property is not defined in the portlet preferences. In another admin portlet, when i want to read this new property, i have a NullPointerException in getPortletProperties from PortletManagementHandler. I look in the sources and the NPE is in this code (prefInfo is null) : Map.Entry entry = (Map.Entry)entries.next(); | key = (String)entry.getKey(); | value = (Value)entry.getValue(); | prefInfo = info.getPreferences().getPreference(key); | displayName = prefInfo.getDisplayName(); Something i made is wrong or it is a bug ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215708#4215708 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215708

15 years, 10 months

1
0
0 / 0

[JBossWS] - Re: Specify WS-Security Handler using JEE standards

by vdurbha

After trying various options, I finally figured out a way to write a completely generic client by removing the StubExt dependency. This was achieved by using the @HandlerChain annotation on the Service class. This may also work if we use the annotation on the SEI. And then I defined the handler in an xml and referred to it in the annotation as follows: @HandlerChain(file="HelloWorldHandlerChain.xml") But the server side endpoint still does not work if I use @HandlerChain annotation instead of @EndpointConfig to set the security handler. After digging into the source code of JBossWS and the log files for a few hours, I understood that for the WS-Security handler to work correctly, it has to be configured as a POST Handler type. When I used @HandlerChain annotation, it is configured as ENDPOINT Handler type. I was not able to find anyway to specify the type of handler in a standard way. So for now, I'm guessing there is no escape from the @EndpointConfig proprietary annotation. Can someone please confirm the same? I would love to hear that I"m wrong with this because it is not a good idea to fill the source code with proprietary stuff. Doing this in a JBoss specific configuration file will be more cleaner as the code can then easily migrated to a different server without changes to source code. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215707#4215707 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215707

15 years, 10 months

1
0
0 / 0

[JBoss jBPM] - NullPointerException in procins.jsf

by rogerio.baldini

Hi, I am getting this error below in jbpm-console in URL: http://localhost:9090/jbpm-console/app/procins.jsf?id=97 JBoss AS 4.2.3.GA and JBPM 3.3.1. | java.lang.NullPointerException | java.lang.String.compareTo(String.java:1168) | java.lang.String.compareTo(String.java:92) | org.jboss.gravel.data.action.SortActionListener$ELComparator.compare(SortActionListener.java:144) | java.util.Arrays.mergeSort(Arrays.java:1270) | java.util.Arrays.sort(Arrays.java:1210) | java.util.Collections.sort(Collections.java:159) | org.jboss.gravel.data.action.SortActionListener.processAction(SortActionListener.java:91) | javax.faces.event.ActionEvent.processListener(ActionEvent.java:88) | javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:771) | javax.faces.component.UICommand.broadcast(UICommand.java:372) | org.jboss.gravel.action.handler.ResponseActionsHandler.onComponentPopulated(ResponseActionsHandler.java:24) | com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:180) | com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47) | com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:314) | com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169) | com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47) | com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:314) | com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169) | org.jboss.gravel.common.handler.CollectionHandler.applyNextHandler(CollectionHandler.java:155) | com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169) | com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47) | com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:314) | com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169) | com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47) | org.jboss.gravel.action.handler.CheckRoleHandler.apply(CheckRoleHandler.java:128) | com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:314) | com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169) | com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49) | com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25) | com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:248) | com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:294) | com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:273) | com.sun.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:140) | com.sun.facelets.tag.ui.DecorateHandler.apply(DecorateHandler.java:105) | com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47) | com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:314) | com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169) | com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47) | com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:314) | com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169) | com.sun.facelets.tag.ui.DefineHandler.applyDefinition(DefineHandler.java:64) | com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:131) | com.sun.facelets.impl.DefaultFaceletContext$TemplateManager.apply(DefaultFaceletContext.java:337) | com.sun.facelets.impl.DefaultFaceletContext.includeDefinition(DefaultFaceletContext.java:307) | com.sun.facelets.tag.ui.InsertHandler.apply(InsertHandler.java:68) | com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47) | com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49) | com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47) | com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25) | com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:248) | com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:294) | com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:273) | com.sun.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:140) | com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:113) | com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49) | com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25) | com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:248) | com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:294) | com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:273) | com.sun.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:140) | com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:113) | com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49) | com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25) | com.sun.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:95) | com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:524) | com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:567) | javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:189) | com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:109) | com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) | com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) | javax.faces.webapp.FacesServlet.service(FacesServlet.java:266) | org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | Can anybody help me ? Thanks Rogerio View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215706#4215706 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215706

15 years, 10 months

1
0
0 / 0

[JBoss Messaging] - Re: jms communications in the same jvm in the client side

by gaohoward

Hi, can you give more details about what kind of communications that the two clients make? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215705#4215705 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215705

15 years, 10 months

1
0
0 / 0

[JBossWS] - Handler execution order in handler chain

by Sancheski

Hi, I have defined three handlers in a handler chain as follows: | <?xml version="1.0" encoding="UTF-8"?> | | <handler-chains xmlns="http://java.sun.com/xml/ns/javaee" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns1="http://org.jboss.ws/jaxws/handlerscope" | xsi:schemaLocation="http://java.sun.com/xml/ns/javaee javaee_web_services_1_2.xsd"> | | <handler-chain> | <handler> | <handler-name>Handler 1</handler-name> | <handler-class> | test.HandlerOne | </handler-class> | </handler> | <handler> | <handler-name>Handler 2</handler-name> | <handler-class> | test.HandlerTwo | </handler-class> | </handler> | <handler> | <handler-name>Handler 3</handler-name> | <handler-class> | test.HandlerThree | </handler-class> | </handler> | </handler-chain> | | </handler-chains> | I thought that the handler execution order was going to be: handler 1, handler 2 and handler 3. But what really happened was that handlers were executed in reverse order, that is: Handler 3, handler 2, and handler 1. My handlers implement javax.xml.ws.handler.soap.SOAPHandler and I am using jbossws 3.0.4.GA. How can I set the handler execution order ? Are handlers in handler chain executed in reverse order as they are defined in the handler definition? Thanks in advance, David Sancho View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215702#4215702 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215702

15 years, 10 months

1
0
0 / 0

[JBoss AOP] - Re: Using AOP to mock out dependecies for unit-test

by stale.pedersen＠jboss.org

hi, ive tested the code you provided and i get a classcastexception too. ill take a closer look and let you know what find. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215699#4215699 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215699

15 years, 10 months

1
0
0 / 0

[JBoss Tools (users)] - JBoss Server View: "Error: no label provider for R/"

by xmedeko

Hi, I've just installed a JBossAS plugin ( Version: 2.0.0.CR2-R200901280154) by software update from (http://download.jboss.org/jbosstools/updates/development) into the Eclipse 3.4.2 (Build id: M20090211-1700). I have added path to a JBoss 4.2.3 and 5.0.1 in the Preferences-> ?When I open the JBoss Server View, I see nothing. Just the tooltip says: "Error: no label provider for R/". I have tried to install the JBossAS plugin from http://download.jboss.org/jbosstools/updates/nightly/3.0.x/, I've tried to uninstall it and install again, but all the time same result. What's wrong? Should I install something else beside JBossAS plugin (missing dependency)? Thanks Andy View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215698#4215698 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215698

15 years, 10 months

1
0
0 / 0

[JBoss Cache: Core Edition] - Architecture Advice: Exactly One Cache Instance Per Node

by mraccola

Would appreciate some advice on the best way to accomplish the following requirement. Current Architecture We are using JBoss Cache 1.4.1 SP9. We have an EAR file with one Web module (WAR). We deploy this application on both WebSphere and JBoss. So we include the JBoss Cache JAR file inside the WAR's WEB-INF/lib directory. In the case of WebSphere we also include the JBoss Cache dependencies (jboss-common.jar, etc). We set the class loader order so the Web module class loader is first. Our TreeCache configuration file is deployed to a folder outside the deployed app and this folder is added to the server's classpath using a vendor-specific mechanism. The end result is exactly one cache instance per application instance. The cache instances are configured to communicate with each other using REPL_SYNC. Target Architecture We are coming out with a new version of the app which includes multiple Web modules (WARs) in the same EAR. All the Web modules need the same cache contents. If we retain the existing architecture this will multiply the number of cache instances. This is undesirable because (a) each cache instance will require memory, (b) all cache instances need to stay in sync, multiplying the network traffic, (c) each cache instance will need its own configuration file, especially for TCP-based replication. What we want is a way to instantiate one cache instance for the entire JVM and register it so it can be accessed by JNDI or JMX. Then each Web module can just lookup the cache. This must work on both WebSphere and JBoss (and in the future WebLogic). We would strip all JBoss JARs from the WAR/EAR and deploy them to the server. Then the server would need to be instructed to create a cache instance as the server comes up and register it. We would have lookup code to get a handle on the cache instance when the Web module(s) came up. We would also upgrade to JBoss Cache 3.x at the same time so we didn't have to deal with conflicts in JBoss system libraries and the versions embedded in the app server (javax.management classes for example). I think it is fairly easy on JBoss AS. There are instructions for deploying a cache instance to JMX. This should create one instance per node. However, I am not sure if this is recommended on other app servers. We are thinking we can use the WAS Extended MBean Provider feature, http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/co.... Any advice on whether this is recommended or any tips to get it going? I would be happy to write up a Wiki article if we do get it working on WebSphere. The current Wiki articles on the topic on the JBoss Cache community site aren't very comprehensive. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215697#4215697 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215697

15 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user March 2009