August 2007 - jboss-user - Jboss List Archives

[JBoss Messaging] - Can a bridge work fine with the remote source and local targ

by jsnhsu

I create two queues on two JBoss. I call the queue locates on the JBoss along with the bridge as local queue and which is the target queue. The other one on remote JBoss is the source queue. I want to pull the messages from remote to local. However, it's not working. There is no error message in the console. It seems that the bridge is just not working. If I create another queue on local to simulate the remote one. The bridge works fine. Please advice if I configured wrong or missed something. This is the configuation of the bridge. | <mbean code="org.jboss.jms.server.bridge.BridgeService" | name="jboss.messaging:service=Bridge,name=Remote2LocalBridge" | xmbean-dd="xmdesc/Bridge-xmbean.xml"> | <depends optional-attribute-name="SourceProviderLoader">jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider,server=remoteServer</depends> | <depends optional-attribute-name="TargetProviderLoader">jboss.messaging:service=JMSProviderLoader,name=JMSProvider</depends> |  | <depends>jboss.messaging.destination:service=Queue,name=localQueue</depends> | <attribute name="SourceDestinationLookup">/queue/remoteQueue</attribute> | <attribute name="TargetDestinationLookup">/queue/localQueue</attribute> | <attribute name="SourceUsername">remoteUser</attribute> | <attribute name="SourcePassword">remotePassword</attribute> | <attribute name="TargetUsername">localUser</attribute> | <attribute name="TargetPassword">localPassword</attribute> | This is the configuration in *.ds.xml: | <connection-factories> | <mbean code="org.jboss.jms.jndi.JMSProviderLoader" | name="jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider,server=remoteServer"> | <attribute name="ProviderName">RemoteJMSProvider</attribute> | <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute> | <attribute name="FactoryRef">java:/XAConnectionFactory</attribute> | <attribute name="QueueFactoryRef">java:/XAConnectionFactory</attribute> | <attribute name="TopicFactoryRef">java:/XAConnectionFactory</attribute> | <attribute name="Properties"> | java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory | java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces | java.naming.provider.url=remoteServer:1099 | </attribute> | </mbean> | </connection-factories> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069978#4069978 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069978

18 years, 8 months

1
0
0 / 0

[JBoss jBPM] - JBpm BPEL deploy error

by peetair

Hi! I'm trying to deploy my BPEL under jboss. The example hello.bpel deployed, so the server is working. I made the .bpel with the eclipse BPEL editor. I have a wsdl and an xsd file from a webservice that i'd like to invoke from the bpel process. my bpel-definition.xml looks like this: <?xml version="1.0" encoding="UTF-8"?> <bpelDefinition location="IopUpload.bpel" xmlns="http://myns" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.iop.hu/2004 http://localhost/wsp-jaxws?xsd=1"> the ant target deploy-definition creates the .zip package but it gives error code 500. And in the jboss log: 2007-08-02 09:41:50,852 ERROR [org.jbpm.bpel.xml.ProblemHandler] IopUpload.bpel could not read process document java.lang.NullPointerException at org.jbpm.bpel.graph.def.ImportsDefinition.getMessage(ImportsDefinition.java:162) at org.jbpm.bpel.graph.def.ImportsDefinition.getMessageType(ImportsDefinition.java:260) at org.jbpm.bpel.xml.BpelReader.getMessageType(BpelReader.java:789) at org.jbpm.bpel.xml.BpelReader.getVariableType(BpelReader.java:765) at org.jbpm.bpel.xml.BpelReader.readVariable(BpelReader.java:744) at org.jbpm.bpel.xml.BpelReader.readVariables(BpelReader.java:725) at org.jbpm.bpel.xml.BpelReader.readScope(BpelReader.java:490) at org.jbpm.bpel.xml.BpelReader.read(BpelReader.java:251) at org.jbpm.bpel.xml.BpelReader.read(BpelReader.java:200) at org.jbpm.bpel.par.BpelArchiveParser.readFromArchive(BpelArchiveParser.java:48) at org.jbpm.jpdl.par.ProcessArchive.parseProcessDefinition(ProcessArchive.java:81) at org.jbpm.bpel.web.ProcessDeployServlet.doGet(ProcessDeployServlet.java:50) at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:619) 2007-08-02 09:41:50,852 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jbpm-bpel].[processDeployServlet]] Servlet.service() for servlet processDeployServlet threw exception org.jbpm.jpdl.JpdlException: [[ERROR] IopUpload.bpel could not read process document] at org.jbpm.jpdl.par.ProcessArchive.parseProcessDefinition(ProcessArchive.java:84) at org.jbpm.bpel.web.ProcessDeployServlet.doGet(ProcessDeployServlet.java:50) at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:619) I looked in the src. The null pointer comes when it tries to getMessage and go through the imports List. I use soap with attachment as input for receive in the process which is defined in the XSD file. Any ideas? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069977#4069977 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069977

18 years, 8 months

1
0
0 / 0

[Beginners Corner] - What's the difference between jboss4.2 and jboss5.0?

by xuyanning

Hi: I am researching the difference between jboss4.2 and jboss5.0, but I can't find the help document in website of jboss orgnizetion. I want to get the difference at every founction module which between jboss4.2 and jboss5.0. For exemple: jboss JTA?jboss5.0 is manage transction in cache and don't support restore transction's catastrophe, while jboss4.2 have a strong ability and support restore transction's catastrophe. I want to get the others difference include JMS, JSF, JAAS, JNDI, JSP and Servlet. I want to get the answer form source code but I am begin with jboss and don't familiar with it. Who can tell me how to study the source code and the answer between jboss4.2 and jboss5.0? Any help is greatly appreciated, I have been struggling with this for a while. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069976#4069976 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069976

18 years, 8 months

1
0
0 / 0

[EJB 3.0] - Re: service=EJB3 + is already registered

by wolfc

Check out what happened to any previous deployment. Did it clean up properly? If there is no previous deployment, create a small test case which reproduces the problem. Open a JIRA and attach the test case. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069975#4069975 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069975

18 years, 8 months

1
0
0 / 0

[JBoss Seam] - Re: pages-2.0.xsd schema - undocumented features

by thhal

How about that. The preview of the post actually expands the html entities, not just in the previewed text, but also in your entered text. Next preview (or submit) is then corrupt. This time I used the back-button after my preview. I meant to write "the undocumented <conversation> element" A related question. The <page> element can be put in a file of its own, one for each view. It seems to me like it would be desirable to perhaps have the option declare the <conversation> inline in a instead of referencing it using an attribute. That would also allow for anonymous conversations (and thus, no 'name' prepended to the conversation id). <page ...> <conversation parameter-name="..." parameter-value="..."/> </page> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069974#4069974 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069974

18 years, 8 months

1
0
0 / 0

[JBoss Seam] - Re: Disable built-In filter

by dmitriy.lapko

Thank you for answer, but I spent an hour trying to do it and didn't succeed. I added into my components.xml next line: <component name="org.jboss.seam.web.exceptionFilter" installed="false"/> It didn't work: ... | INFO 02-08 10:14:04,718 [org.jboss.seam.Component.<init>():239] Component: org.jboss.seam.web.exceptionFilter, scope: APPLICATION, type: JAVA_BEAN, class: org.jboss.seam.web.ExceptionFilter | ... | INFO 02-08 10:14:06,875 [org.jboss.seam.servlet.SeamFilter.init():95] Initializing filter: org.jboss.seam.web.exceptionFilter | ... | ERROR 02-08 10:14:08,656 [org.jboss.seam.web.ExceptionFilter.doFilter():68] handling uncaught exception | ... I tried different combinations: with defining class and without, with setting precedence level and so on. It didn't work. I checked all examples from CVS - none has install="false" property for any built-in component. So, are you sure, that I can switch off built-in component like filter? If yes, can't you post an example or link, how to do it? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069973#4069973 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069973

18 years, 8 months

1
0
0 / 0

[JBoss Messaging] - Re: JBM and JAAS Client authentication

by mskonda

I am not sure if this is related or not - I was getting the same exception! I have a test scenario: My MDB calls a Session EJB to do some work - The session EJB essentially uses the JmsXA CF to publish a message. The MDB is authenticated properly (using the <mdb-user>, however, the security-domain is not working, which is another issue!) and calls the Session EJB. The ejb creates a connection successfully with a username and password however fails with the exact problem you have when creating a session (I am not sure why it's not failing on create connection though). However, I *got* through the problem: I have changed the security domain policy for JmsXa to reflect my own application policy (the policy has been instantiated earlier during the application startup). I am not sure whether it's a wrong doing or okay doing but I have a sneaky feeling that I'm breaking something. Here's my JmsXa definition: |  | <tx-connection-factory> | <jndi-name>JmsXA</jndi-name> | <xa-transaction/> | <rar-name>jms-ra.rar</rar-name> | <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition> | <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property> | <config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/DefaultJMSProvider</config-property> | <max-pool-size>20</max-pool-size> | <security-domain-and-application>java:/MyPolicy</security-domain-and-application> |  | <depends>jboss.messaging:service=ServerPeer</depends> | </tx-connection-factory> | The modified MyPolicy is defined in login-config.xml as below: | <application-policy name="MyPolicy"> | <authentication> | <login-module code="com.my.SecureLoginModule" flag="required"> | <module-option name="username">myself</module-option> | <module-option name="password">Rqm8QqlcszYlZdf/eNDpx</module-option> | <module-option name="securePropertiesFile">secure.properties.xml</module-option> | <module-option name="managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=MyJMSDS</module-option> | </login-module> | </authentication> | </application-policy> | Bear in mind this MyPolicy is instantiated earlier during Datasource deployment! One thing I've noticed is that if I change <security-domain-and-application> in the JmsXa definition to use a new JmsXARealm (I've to modify the existing one as the existing JmsXARealm policy is using ConfiguredIdentityLoginModule) exactly same as above except the name, it doesn't work! I guess this is due to the fact that this particular policy is *not* instantiated by any other components. Hope this might rub the salt! Thanks Madhu View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069972#4069972 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069972

18 years, 8 months

1
0
0 / 0

[JBoss Portal] - can you release jboss.org 's layout and theme

by kevnlin

can you release jboss.org 's layout and theme provider download when I try jboss2.6.1 or jboss 2.6 the layout and theme on 15' monitor or 8' monitor ,the page not show on current place View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069971#4069971 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069971

18 years, 8 months

1
0
0 / 0

[Clustering/JBoss] - Re: Out of the box clustering won't work

by atomicGun

I am having this problem and wonder anyone can help me on this. I have setup 4 different cluster nodes on 4 different machines(A, B, C, D) for testing. There is this machine A cannot be detected as cluster member (i.e. A will form its own cluster) and B, C, and D can see each other. I was wondering what happened, then I realized A was actually seated on a different network switch. I tried to put A's cable to the same switch B/C/D have used and now A get detected. any idea why and how to resolve this if A has to be on the different switch? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069969#4069969 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069969

18 years, 8 months

1
0
0 / 0

[Clustering/JBoss] - Re: Failover not working InvalidClassException (Log4JLogger)

by CarstenRudat

Hi, I fixed this - I had a commons-logging-x.jar in my WEB-INF/lib. But after removing this, I get another error: WARN [TreeCache] node /JSESSION/localhost/genloop-demo/8gZM8DrZOd0IGqYY6C3Luw** not found I have two jboss-4.2.1.GA (./run.sh -c all -b ip_node1/ip_node2) running. After shutting down node1 and submitting a request, I get this error on node2. What does this "localhost" mean and how can I get a session-string that allows transparent failover? To add some information, I run a JSF-application with tomahawk and client-side saving (javax.faces.STATE_SAVING_METHOD - client). Thanks for any help to get this work. Carsten View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069965#4069965 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069965

18 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user August 2007