October 2007 - jboss-dev-forums - Jboss List Archives

[Design of JBoss/Tomcat Integration] - Re: Programmatic configuration of jvmRoute

by jfrederic.clere＠jboss.com

Don't forget that we have actually no ways to forward this information to mod_jk/mod_proxy so changing the jvmRoute programmaticaly requires complex modifications there too. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099147#4099147 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4099147

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Problems getting WS into ESB

by thomas.diesler＠jboss.com

I updated the deploy target in the 2.0.1.SP2 tag. You should see | [tdiesler@tddell jbossws-native-2.0.1.SP2]$ ant deploy-jboss42 | ... | deploy-jboss421: | [copy] Copying 1 file to /home/tdiesler/svn/jbossas/tags/JBoss_4_2_1_GA/build/output/jboss-4.2.1.GA/server/default/lib | [copy] Copying 1 file to /home/tdiesler/svn/jbossas/tags/JBoss_4_2_1_GA/build/output/jboss-4.2.1.GA/client | | ... | | BUILD SUCCESSFUL | Total time: 7 seconds | The binaries are not affected View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099144#4099144 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4099144

17 years, 4 months

1
0
0 / 0

[Design of POJO Server] - Re: AppClientDeployer

by scott.stark＠jboss.org

I have the new metadata wired to the old model and this is flowing through to the client injection handlers, and I see the container being passed to the kernel to be started, but its not starting. It seems the dependencies are not being statisifed, but I don't see any error being generated. Because the client container is not being started the remote client is not seeing its enc and fails. Don't know if how the Ejb3ClientDeployer is registering the bean is bypassing the completion check. I'll look at it tomorrow. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099138#4099138 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4099138

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Problems getting WS into ESB

by thomas.diesler＠jboss.com

Ok, in that case I verify the deploy-jboss42 target against AS4.2.1 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099137#4099137 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4099137

17 years, 4 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Thread-Safety problems GeneratedClassAdvisor

by flavia.rainone＠jboss.com

Jason, thanks for the input. Both issues you have raised are already fixed in the trunk. :) Unfortunately, none of them issues are the cause of bug JBAOP-480. What is happening is that a thread is trying to generate a joinpoint class for a joinpoint whose info interceptor chain is null. Here is how this happens: in an if-statement, thread 1 checks that the info object of joinpoint A contains a non-empty interceptor chain; thread 1 is preempted by thread2; thread2 removes the last interceptor bound to joinpoint A, recreating a new info field for joinnpoint A with a null interceptor chain; thread1 resumes, generating code to intercept joinpoint A, without being aware that its info contains now a null interceptor chain. To avoid that, all I should do is to synchronize the thread on the joinpoint itself. This, added to some synchronization I have put on JoinPointInfo (I haven't commited this part since, alone, it is not a solution to anything), would do the trick. But the problem is which object should be picked for the synchronization on the joinpoint? If we generated only one joinpoint info during all the JBoss AOP execution, this info would be a no-brain choice. However, since a new info is created at every rebuildInterceptors execution, we have no such object. The interesting part is that I was already going to propose a change in this structure before Jason reported this concurrency isse :). My change would allow us to solve this problem easily, as well as bug JBAOP-380. Kabir, I'll let you know a more detailed picture of this new approach tomorrow morning. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099117#4099117 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4099117

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Problems getting WS into ESB

by Kevin.Conner＠jboss.com

"thomas.diesler(a)jboss.com" wrote : anonymous wrote : | | I still don't know whether the SP2 release includes this fix or not, you owe me an answer on that one ;) | | | | Yes it does. | Thank you :) "thomas.diesler(a)jboss.com" wrote : #2 we use the AS4.2.1 binary relase Yes, we use the binary. "thomas.diesler(a)jboss.com" wrote : In both cases installing jbossws-2.0.1.SP2 is not trivial because the AS container integration has moved to Branch_4_2 after the AS4.2.1 release. Which is the issue Trevor is finding. I am assuming that 'after the AS4.2.1 release' means 'AS4.2.2 and later', is this correct? "thomas.diesler(a)jboss.com" wrote : Please show me exactly how you attempted to install jbossws-2.0.1.SP2 from that I can probably see how it should be done properly. I believe Trevor is using your installation scripts to handle this aspect. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099113#4099113 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4099113

17 years, 4 months

1
0
0 / 0

[Design of POJO Server] - Re: Microcontainer 2.0.0.Beta5

by scott.stark＠jboss.org

Its working fine. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099082#4099082 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4099082

17 years, 4 months

1
0
0 / 0

[Design of POJO Server] - Re: Microcontainer 2.0.0.Beta5

by scott.stark＠jboss.org

I'll validate the changes, but doubt this error is related. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099076#4099076 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4099076

17 years, 4 months

1
0
0 / 0

[Design of POJO Server] - Re: Microcontainer 2.0.0.Beta5

by alesj

"alesj" wrote : | Going over my changes, they should only affect ProfileService code. | But let me know if something is broken due to MC_beta5 changes. :-( btw: I was able to run the AS5_trunk w/o any problems yesterday with my MC_beta5 changes already applied. This bind issue only popped after I updated the trunk today. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099073#4099073 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4099073

17 years, 4 months

1
0
0 / 0

[Design of POJO Server] - Re: Microcontainer 2.0.0.Beta5

by alesj

I'm now getting this - in all 4 configurations: | 01:17:20,416 ERROR [Naming] Could not start on port 1099 | java.net.BindException: Address already in use: JVM_Bind | at java.net.PlainSocketImpl.socketBind(Native Method) | But I _did_ commit my changes anyway. In order for you and Thomas to resolve the bug that Adrian fixed with JBMICROCONT-212 + applying new AOP/CL changes Kabir did. Going over my changes, they should only affect ProfileService code. But let me know if something is broken due to MC_beta5 changes. :-( View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099072#4099072 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4099072

17 years, 4 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-dev-forums October 2007