August 2006 - jboss-user - Jboss List Archives

[JBossCache] - Re: [TreeCacheMarshaller140] Unknown Magic Number 49

by bela＠jboss.com

OK, ic View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968352#3968352 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968352

20 years

1
0
0 / 0

[JBossWS] - Re: JBossWS response does not match WSDL message definition;

by Doug.Palmer

"jason.greene(a)jboss.com" wrote : | | What gave you this idea? In WSDL 1.1 message names are meaningless. | Did you read the spec? | | http://www.w3.org/TR/wsdl | | -Jason I guess I completely missed the point, sorry. I've just read the spec and see I got it wrong. Regards Doug View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968351#3968351 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968351

20 years

1
0
0 / 0

[JBoss Seam] - Re: Problem in deploying a Seam Project into Tomcat

by camunda

I ran into the same problems while building the war file with my own build file. But the exception only occurs if you forget to replace the properties @xxx@ in the components.xml. If I replace them with ant, everything is fine... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968350#3968350 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968350

20 years

1
0
0 / 0

[JBossCache] - Re: [TreeCacheMarshaller140] Unknown Magic Number 49

by manik.surtani＠jboss.com

Bela, looks like a JBC problem. Strings are written to the stream using the marshaller using ObjectOutputStream.writeUTF() - which has this limitation: http://java.sun.com/j2se/1.5.0/docs/api/java/io/DataOutput.html#writeUTF(... According to the documentation, this limits string lengths to 65535 bytes. Carl, are you using multi-byte Strings (accents, etc)? 32767 characters x 2 bytes per char = 65534 bytes. 32768 characters (at 2 bytes per char) will cross this limit and you will see an overflow. The fix to this problem would be NOT to use writeUTF() but to serialize the Strings themselves onto the stream, but this is less efficient. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968349#3968349 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968349

20 years

1
0
0 / 0

[Installation, Configuration & Deployment] - Re: Jboss mail-service.xml localhost, port 25

by tbottger

Something to check is that you don't have a virus scanner on this machine that is blocking port 25 from mass emails. I ran into this problem on our server and it prevented all emails from going out. Once I disabled this on this server, everything was fine. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968347#3968347 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968347

20 years

1
0
0 / 0

[JBossCache] - Re: [TreeCacheMarshaller140] Unknown Magic Number 49

by bela＠jboss.com

Manik, please let me know if this turns out to be a JGroups problem, so I could look at it. Cheers. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968346#3968346 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968346

20 years

1
0
0 / 0

[JBossWS] - Re: JBossWS response does not match WSDL message definition;

by jason.greene＠jboss.com

"Doug.Palmer" wrote : | In the generated WSDL the output messages are defined with a name INTERFACE-NAME_METHOD-NAMEResponse. | | However, when the service is invoked the message returned from the service is METHOD-NAMEResponse. | | Surely the the message names should be the same? How can we program with web services if JBossWS returns messages that don't conform to the WSDL description of those messages? | What gave you this idea? In WSDL 1.1 message names are meaningless. Did you read the spec? http://www.w3.org/TR/wsdl -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968344#3968344 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968344

20 years

1
0
0 / 0

[JBossWS] - Re: JBossWS response does not match WSDL message definition;

by Doug.Palmer

Ok, the issue is now on JIRA; http://jira.jboss.com/jira/browse/JBWS-1154. I'm guessing that you don't have an issue with it because you write code that responds to the messages you know the service will return. Instead of writing code from the WSDL. The WSDL describes the input to this service as so sending a message in <Calculator_add> tags should invoke it. However JBossWS expects tags. Similarly the service should respond with <Calculator_addResponse> tags but it actually responds with tags. Regards Doug View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968342#3968342 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968342

20 years

1
0
0 / 0

[JBossCache] - Re: [TreeCacheMarshaller140] Unknown Magic Number 49

by carlabramsson

Cool. Yeeah, did just see that there´s a 1.4.0SP2 planned now with "my" two bugs. Thanks! :-D View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968341#3968341 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968341

20 years

1
0
0 / 0

[JBossCache] - Re: Problems about updating an ArrayList in replicated TreeC

by jeyrich

We see the same exception. Trying to reproduce it, I found I can only provoke it by having a circular reference. I have created a small test case (and created JBCACHE-757 (http://jira.jboss.com/jira/browse/JBCACHE-757) for it): import org.jboss.cache.aop.PojoCache; | import org.jboss.cache.aop.annotation.PojoCacheable; | | @PojoCacheable | public class Main { | public Main reference; | | public static void main(String[] args) throws Exception { | | PojoCache cache = new PojoCache(); | cache.startService(); | | Main main = new Main(); | Main main2 = new Main(); | | main.reference = main2; | main2.reference = main; | | cache.putObject("/main",main); | | main2.reference = main; // <-- | | System.out.println("Done..."); | } | } results in: Exception in thread "main" java.lang.RuntimeException: PojoCache.putObject(): fqn: /main/reference/reference | at org.jboss.cache.aop.PojoCache.putObject(PojoCache.java:478) | at org.jboss.cache.aop.CacheInterceptor.invoke(CacheInterceptor.java:115) | at org.jboss.aop.joinpoint.FieldWriteInvocation.invokeNext(FieldWriteInvocation.java:51) | at Main.reference_w_$aop(Main.java) | at Main.main(Main.java:21) | Caused by: java.lang.IllegalStateException: AOPInstance.incrementRefCount(): source fqn: /main/reference/reference is already present. | at org.jboss.cache.aop.AOPInstance.incrementRefCount(AOPInstance.java:92) | at org.jboss.cache.aop.InternalDelegate.incrementRefCount(InternalDelegate.java:98) | at org.jboss.cache.aop.ObjectGraphHandler.incrementRefCount(ObjectGraphHandler.java:212) | at org.jboss.cache.aop.ObjectGraphHandler.setupRefCounting(ObjectGraphHandler.java:192) | at org.jboss.cache.aop.ObjectGraphHandler.objectGraphPut(ObjectGraphHandler.java:88) | at org.jboss.cache.aop.TreeCacheAopDelegate._putObject(TreeCacheAopDelegate.java:201) | at org.jboss.cache.aop.PojoCache._putObject(PojoCache.java:731) | at org.jboss.cache.aop.PojoCache.putObject(PojoCache.java:462) | ... 4 more View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968340#3968340 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968340

20 years

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 2006