[JBoss AS7 Development] - Hacking on AS7
by Bruno Georges
Bruno Georges [http://community.jboss.org/people/bgeorges] modified the document:
"Hacking on AS7"
To view the document, visit: http://community.jboss.org/docs/DOC-15596
--------------------------------------------------------------
h4. 1. Create a github account
http://github.com http://github.com
h4. 2. Fork jboss-as into your account
http://github.com/jbossas/jboss-as http://github.com/jbossas/jboss-as
h4. 3. Clone your newly forked copy onto your local workspace
$ git clone git@github.com:[your user]/jboss-as.git
Initialized empty Git repository in /devel/jboss-as/.git/
remote: Counting objects: 2444, done.
remote: Compressing objects: 100% (705/705), done.
remote: Total 2444 (delta 938), reused 2444 (delta 938)
Receiving objects: 100% (2444/2444), 1.71 MiB | 205 KiB/s, done.
Resolving deltas: 100% (938/938), done.
$ cd jboss-as
h4. 4. Add a remote ref to upstream, for pulling future updates
git remote add upstream git://github.com/jbossas/jboss-as.git
h4. 5. Use maven (via build.sh) (make sure you use maven 3)
$ ./build.sh install
.....
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] JBoss Application Server: BOM ..................... SUCCESS [1.834s]
[INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [0.022s]
[INFO] JBoss Application Server: Domain Core ............. SUCCESS [3.051s]
[INFO] JBoss Application Server: Server Manager .......... SUCCESS [0.204s]
[INFO] JBoss Application Server: Server .................. SUCCESS [0.283s]
[INFO] JBoss Application Server: Domain Controller ....... SUCCESS [0.084s]
[INFO] JBoss Application Server: Process Manager ......... SUCCESS [0.314s]
[INFO] JBoss Application Server: Remoting ................ SUCCESS [0.390s]
[INFO] JBoss Application Server: Build ................... SUCCESS [5.696s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
h4. 6. Pulling later updates from upstream
$ git pull --rebase upstream master
>From git://github.com/jbossas/jboss-as
* branch master -> FETCH_HEAD
Updating 3382570..1fa25df
Fast-forward
{parent => bom}/pom.xml | 70 ++++----------
build/pom.xml | 13 +--
domain/pom.xml | 10 ++
.../src/main/resources/examples/host-example.xml | 2 +-
.../resources/examples/jboss-domain-example.xml | 28 +++---
.../main/resources/schema/jboss-domain-common.xsd | 12 +--
.../main/resources/schema/jboss-domain-host.xsd | 2 +-
domain/src/main/resources/schema/jboss-domain.xsd | 17 ++--
pom.xml | 100 ++++++++++++++++++--
process-manager/pom.xml | 3 +-
10 files changed, 156 insertions(+), 101 deletions(-)
rename {parent => bom}/pom.xml (85%)
*(--rebase will automatically put move commits, if you have any, on top of the latest master, you can leave it off if you do not)*
h4. 7. Pushing pulled updates (or local commits if you aren't using topic branches) to your private github repo (origin)
$ git push
Counting objects: 192, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (44/44), done.
Writing objects: 100% (100/100), 10.67 KiB, done.
Total 100 (delta 47), reused 100 (delta 47)
To git@github.com:[your user]/jboss-as.git
3382570..1fa25df master -> master
*You might need to say -f to force the changes. Read the note on 12 though before you do it.*
h4. 8. Discuss your planned changes (if you want feedback)
* On the forums - http://community.jboss.org/en/jbossas/dev/jboss_as7_development http://community.jboss.org/en/jbossas/dev/jboss_as7_development
* On IRC - irc://irc.freenode.org/jboss-as7 or https://webchat.freenode.net/?channels=jboss-as7 (http://webchat.freenode.net/?channels=jboss-as7)
h4. 9. Make sure there is a JIRA somewhere for the enhancement/fix
http://jira.jboss.org http://jira.jboss.org
h4. 10. Create a simple topic branch to isolate that work (just a recommendation)
git checkout -b my_cool_feature
h6. Note: See tips section for how to use a nice git prompt for tracking what branch you are in!
h6. 11. Make the changes and commit one or more times (Don't forget to push)
git commit -m 'JBAS-XXXX Frunubucate the Fromungulator'
git commit -m 'JBAS-YYYY Tripple Performance of Fromungulation'
git push my_cool_feature
+Note that git push references the branch you are pushing and defaults to master, *not your working branch*.+
h4. 12. Rebase your branch against the latest master (applies your patches on top of master)
git fetch upstream
git rebase -i upstream/master
# if you have conflicts fix them and rerun rebase
# The -f, forces the push, alters history, see note below
git push -f my_cool_feature
The -i triggers an interactive update which also allows you to combine commits, alter commit messages etc. It's a good idea to make the commit log very nice for external consumption. Note that this alters history, which while great for making a clean patch, is unfriendly to anyone who has forked your branch. Therefore you want to make sure that you either work in a branch that you don't share, or if you do share it, tell them you are about to end the branch.
h4. 13. Get your changes merged into upstream
1. Make sure your repo is in sync with other unrelated changes in upstream before requesting your changes be merged into upstream by repeating step 12.
2. Email a pull request to mailto:jbossas-pull-requests@lists.jboss.org jbossas-pull-requests(a)lists.jboss.org (if I haven't subscribed the list, do it https://lists.jboss.org/mailman/listinfo/jbossas-pull-requests here) with a link to your repo, a description of the changes, and who reviewed (if any)
3. After review a maintainer will merge your patch, update/resolve issues by request, and reply when complete
4. Don't forget to switch back to master and pull the updates1. git checkout master
git pull upstream master
h4. Appendix A. Adding a new external dependency
1. Edit pom.xml and add a property of the form "version.groupId.artifactId" which contains the Maven version of the dependency. Add your dependency to the <dependencyManagement> section, and use the property for the version. If your new dependency has any transitive dependencies, be sure to <exclude> them (or if possible, update the project so that all its dependencies are of *provided* scope).
2. Add your dependency to any AS modules that require it, but only with group/artifact.
3. Edit build/pom.xml and add your dependency with only group/artifact.
4. Create a directory in build/src/modules corresponding to the *module's* name (which will differ from the Maven group/artifact name; look at other modules to get a feel for the naming scheme), with a version of "main", like this: "build/src/modules/org/jboss/foo/main".
5. Create a module.xml file inside the "main" directory. Use a module.xml from another similar module as a template.
6. Edit build/build.xml and add a <module-def> element. The name listed in the <module-def> element corresponds to the *module* name. The group/artifact listed in the nested maven-resource element(s) refer to the *Maven* group/artifact name.
7. *Important:* Make sure you did not introduce any transitive dependencies by using "mvn dependency:tree". If you did, be sure to add <exclusion>s for each of them to your dependency as described above.
Please be sure to preserve the alphabetical ordering of all POMs and the build.xml file.
h4. Appendix B. Adding a new AS submodule
1. Create the directory corresponding to the submodule and add it to the root pom.xml file. The convention is to leave off the "jboss-as-" portion, so "jboss-as-remoting" becomes "remoting".
2. Create a POM for your submodule (use another submodule as a template). Make sure all dependencies you specify do *not* include a version. The group ID should be "org.jboss.as", and the artifact ID should begin with "jboss-as-" and there should be a proper <name> for the new module.
3. Add the new submodule to the top section of the <dependencyManagement> of the top-level pom.xml. The version should be set to "${project.version}". This section is sorted alphabetically by artifact name so please preserve that ordering.
4. Add your submodule dependency to any AS modules that require it, but only with group/artifact.
5. Edit build/pom.xml and add the new submodule with only group/artifact.
6. Create a directory in build/src/modules corresponding to the submodule, with a version of "main", like this: "build/src/modules/org/jboss/as/new-subsystem/main".
7. Create a module.xml file inside the "main" directory. Use a module.xml from another subsystem as a template.
8. Edit build/build.xml and add a <module-def> element for the subsystem. Use the module name and Maven coordinates from steps 6 and 2 respectively. Use another submodule as a template.
Please be sure to preserve the alphabetical ordering of all POMs and the build.xml file.
h4. Tips & Tricks!
h4. Creating a Git status prompt in your terminal
This makes it easy to not forget what branch you are working in and quickly tell if you have changes. The following will adjust the PS1 on unix (or cygwin on Windows). Note that it assumes a compiled version of git, which is also the case for the OSX packages. If you are using the bundled rpm version, change the completion path to "/etc/bash.completion.d/git"
GIT_COMPLETION_PATH="/usr/local/git/contrib/completion/git-completion.bash"
if [ -f "$GIT_COMPLETION_PATH" ]; then
GIT_PS1_SHOWDIRTYSTATE=true
. "$GIT_COMPLETION_PATH"
ADD_PS1='$(__git_ps1)'
fi
if [[ ${EUID} == 0 ]] ; then
PS1="\[\033[01;31m\]\h\[\033[01;34m\] \w\[\033[33m\]$ADD_PS1\[\033[34m\] \$\[\033[00m\] "
else
PS1="\[\033[01;32m\]\u@\h\[\033[01;34m\] \w\[\033[33m\]$ADD_PS1\[\033[34m\] \$\[\033[00m\] "
fi
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-15596]
Create a new document in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
13 years, 6 months
[JBoss AS7 Development] - Standalone client API
by Kabir Khan
Kabir Khan [http://community.jboss.org/people/kabir.khan%40jboss.com] created the discussion
"Standalone client API"
To view the discussion, visit: http://community.jboss.org/message/567278#567278
--------------------------------------------------------------
> [19:17] bstansberry: ok. emuckenhuber, might as well listen in on this chat with kkhan. this may very well be a task that can be divided up
>
> [19:18] bstansberry: kkhan, emuckenhuber: there are a number of pieces
>
> [19:19] bstansberry: first, a standalone server needs to be able to open a socket for management requests
>
> [19:19] bstansberry: my thinking is to re-use the <management/> element from the domain.xml config to configure that socket
>
> [19:20] kkhan: What exactly is <management/> in domain?
>
> [19:20] kkhan: I mean I've seen it, but don't know exactly what it is for
>
> [19:20] bstansberry: sorry, in host.xml
>
> [19:21] bstansberry: it basically configures the socket the SM uses for listening for requests from the DC
>
> [19:22] kkhan: ok
>
> [19:23] bstansberry: in the domain-client module there is a DomainClientImpl class that connects to the DC to send requests using a protocol
>
> [19:24] bstansberry: we'll need a similar set of classes that send requests to a standalone server using a similar protocol
>
> [19:24] kkhan: in standalone-client or something
>
> [19:25] bstansberry: yeah, we need to discuss that part in a sec, but basically, yes
>
> [19:26] bstansberry: in the server-manager module, the o.j.a.server.manager.management package there are some classes that show how the DC handles requests that come in on its management socket
>
> [19:26] bstansberry: a standalone server would want to use something very similar
>
> [19:28] bstansberry: kkhan: I'm thinking for M1 at least, let's just keep it simple. Copy and paste stuff and get this working; don't worry too much about code duplication between this standalone case and the DC case
>
> [19:28] kkhan: ok, makes sense
>
> [19:29] dmlloyd: ServerController is meant to be the standalone equivalent of DomainController
>
> [19:29] dmlloyd: someday
>
> [19:29] bstansberry: ok
>
> [19:31] kkhan: bstansberry: I think that has given me enough info to start looking at things
>
> [19:32] bstansberry: cool
> [19:17] bstansberry: ok. emuckenhuber, might as well listen in on this chat with kkhan. this may very well be a task that can be divided up
> [19:18] bstansberry: kkhan, emuckenhuber: there are a number of pieces
> [19:19] bstansberry: first, a standalone server needs to be able to open a socket for management requests
> [19:19] bstansberry: my thinking is to re-use the <management/> element from the domain.xml config to configure that socket
> [19:20] kkhan: What exactly is <management/> in domain?
> [19:20] kkhan: I mean I've seen it, but don't know exactly what it is for
> [19:20] bstansberry: sorry, in host.xml
> [19:21] bstansberry: it basically configures the socket the SM uses for listening for requests from the DC
> [19:22] kkhan: ok
> [19:23] bstansberry: in the domain-client module there is a DomainClientImpl class that connects to the DC to send requests using a protocol
> [19:24] bstansberry: we'll need a similar set of classes that send requests to a standalone server using a similar protocol
> [19:24] kkhan: in standalone-client or something
> [19:25] bstansberry: yeah, we need to discuss that part in a sec, but basically, yes
> [19:26] bstansberry: in the server-manager module, the o.j.a.server.manager.management package there are some classes that show how the DC handles requests that come in on its management socket
> [19:26] bstansberry: a standalone server would want to use something very similar
> [19:28] bstansberry: kkhan: I'm thinking for M1 at least, let's just keep it simple. Copy and paste stuff and get this working; don't worry too much about code duplication between this standalone case and the DC case
> [19:28] kkhan: ok, makes sense
> [19:29] dmlloyd: ServerController is meant to be the standalone equivalent of DomainController
> [19:29] dmlloyd: someday
> [19:29] bstansberry: ok
> [19:31] kkhan: bstansberry: I think that has given me enough info to start looking at things
> [19:32] bstansberry: cool
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/567278#567278]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 6 months
[JBoss AS7 Development] - AS 7 demos
by Kabir Khan
Kabir Khan [http://community.jboss.org/people/kabir.khan%40jboss.com] created the discussion
"AS 7 demos"
To view the discussion, visit: http://community.jboss.org/message/567221#567221
--------------------------------------------------------------
I have started a demos project, which can be found in upstream.
It currently contains the following examples
-sar
-managedbean
-serviceloader
-messaging
To run an example, make sure AS7 is running and then
cd demos
mvn install -Dexample=sar
A few issues I came across when working on this are:
*Deployment*
-Deployment to domain/deployments does not work, have to do standalone
-Deleting .deployed archive still leaves it hanging around in standalone.xml. To undeploy need to delete from standalone.xml's deployments
-.DS_Store gets picked up as a deployment
-Slightly annoying having to specify the full module path in user deployments, not very user friendly? Will get worse when there are more modules.
-BeanWithSimpleInjected.simple is sometimes null
-ServiceLoader example no longer picks up services
-I am currently just copying to the deployments/ directory, what is the status on the deployment API?
-Deployment to domain/deployments does not work, have to copy to standalone/deployments
-Deleting .deployed archive still leaves it hanging around in standalone.xml. To undeploy need to delete from standalone.xml's deployments
-.DS_Store (on OS X) gets picked up as a deployment
*Module Dependencies*
-It is slightly annoying having to specify the full module path in user deployments, not very user friendly? This will get worse when there are more modules in the server.
*Examples*
The 'sar' and 'messaging' examples work fine, but there are some problems with the others.
For the 'managedbean' example, there is
public class BeanWithSimpleInjected {
private final Logger log = Logger.getLogger(BeanWithSimpleInjected.class);
@Resource
private SimpleManagedBean simple;
...
Sometimes the simple field is null, other times it is injected as expected. I added the functionality to have an @AroundInvoke method on the bean class itself.
The 'serviceloader' example used to work fine in my development branch but following a rebase against upstream the service loader no longer finds the services.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/567221#567221]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 6 months
[JBoss Web Development] - jboss cluster + session replication + j_security_check
by Ronald Arias
Ronald Arias [http://community.jboss.org/people/ronald.arias] created the discussion
"jboss cluster + session replication + j_security_check"
To view the discussion, visit: http://community.jboss.org/message/567199#567199
--------------------------------------------------------------
Hello everyone,
I'm trying to modify org.apache.catalina.authenticator.FormAuthenticator.java for allow session replication across a cluster when using Form Based authentication.
The problem is, ClusteredSingleSignOn has an issue when Form Based authentication is used. This stores the authenticate related session in a map which is not replicated across the cluster. I'm trying to resolve this issue by forcing the replication across the cluster in the file mentioned above but i still don't get it.
My question is, how can i force replication in that file? or what is the function which i have to call to explicit replicate session to other nodes?
I DO NOT want to use sticky sessions in my load_balancer because i will lose my cluster aproachs. I need to replicate session across the cluster when using form based authentication.
I use jboss 4.2.1. I'll apreciate any help.
Thanks.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/567199#567199]
Start a new discussion in JBoss Web Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 6 months
[EJB 3.0 Development] - achieving sub transaction
by Kannan S
Kannan S [http://community.jboss.org/people/techy_kans] created the discussion
"achieving sub transaction"
To view the discussion, visit: http://community.jboss.org/message/567017#567017
--------------------------------------------------------------
Hi all
We have a unique problem in our application. We have got five to six EAR files out of which two ear files interact with the database and one EAR file is a MDB listener. Lets say one of our db interacting EAR files, which is ejb module, is, Business.EAR The following is the main way the business is implemented.
The bean name is BusinessProcessorBean.java for which we have interceptor called PreProcessingInterceptor. The following is the code in PreProcessingInterceptor.
public class PreProcessingInterceptor{
@AroundInvoke
public void doPreProcessing(){
try{
1. do some db operations
2. InvocationContext.proceed() - call the bean
}catch(Exception exp){
System.out.println("Exception "+exp);
}finally{
PostProcessingInterceptor ppi = new PostProcessingInterceptor();
3.ppi.doPostProcessing();
}
}
}
Now we have got a problem in which there may be an exception at the end of point 1 or at the end of point 3. We want to have atleast half transaction in DB so that we can get some data from the database. I came to know that we can do nested transaction . Our bean is container managed. How do i change it to bean manage so that i can re write the java code some thing like
public class PreProcessingInterceptor{
@AroundInvoke
public void doPreProcessing(){
try{
a. transaction.begin();
1. do some db operations
b. transaction.commit();
2. InvocationContext.proceed() - call the bean
}catch(Exception exp){
System.out.println("Exception "+exp);
}finally{
PostProcessingInterceptor ppi = new PostProcessingInterceptor();
c. transaction.begin();
3.ppi.doPostProcessing();
d. transaction.commit();
}
}
}
Please guide me so that our application saves data atleast in a few tables rather than not updating any tables.
Regards
Kannan.S
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/567017#567017]
Start a new discussion in EJB 3.0 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 6 months
[JBoss Messaging Development] - Failed to invoke
by wangdu gyalpo
wangdu gyalpo [http://community.jboss.org/people/wgyalpo] created the discussion
"Failed to invoke"
To view the discussion, visit: http://community.jboss.org/message/566742#566742
--------------------------------------------------------------
Hi there,
I have developed a prototype of a system for handling scores of light-weight requests using jboss queue and mdb consumer. The mdb processes the messages and is the place where the reply is created and sent to another queue from which a standalone jboss messaging consumer (this is also the same where the requests are generated) recieves and hands it further to the client. the version i am using is JBoss 5.1.0 GA.
Everythings works fine, creating connections, sessions etc. even the messages are send and recieved correctly. However, sometimes, once in a while, in the middle of messages passing, the jboss messaging crashes with the following error log:
org.jboss.jms.exception.MessagingJMSException: Failed to invoke at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:271) at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:205) at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:160) at org.jboss.jms.client.delegate.ClientSessionDelegate.org$jboss$jms$client$delegate$ClientSessionDelegate$send$aop(ClientSessionDelegate.java:499) at org.jboss.jms.client.delegate.ClientSessionDelegate$send_6145266547759487588.invokeTarget(ClientSessionDelegate$send_6145266547759487588.java) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111) at org.jboss.jms.client.container.SessionAspect.handleSend(SessionAspect.java:661) at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect_z_handleSend_16032330.invoke(SessionAspect_z_handleSend_16032330.java) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.jms.client.delegate.ClientSessionDelegate.send(ClientSessionDelegate.java) at org.jboss.jms.client.container.ProducerAspect.handleSend(ProducerAspect.java:269) at org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect_z_handleSend_16032330.invoke(ProducerAspect_z_handleSend_16032330.java) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.jms.client.delegate.ClientProducerDelegate.send(ClientProducerDelegate.java) at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:164) at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:207) at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:145) at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:136) at wangdu.intern.jms.JMSRequestMessageProducer.sendMessage(JMSRequestMessageProducer.java:71) at wangdu.intern.jms.JMSRequestMessageProducer.setJMSMessage(JMSRequestMessageProducer.java:112) at wangdu.intern.xmlrpcserver.Calculator.add(Calculator.java:39) at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.xmlrpc.server.ReflectiveXmlRpcHandler.invoke(ReflectiveXmlRpcHandler.java:115) at org.apache.xmlrpc.server.ReflectiveXmlRpcHandler.execute(ReflectiveXmlRpcHandler.java:106) at org.apache.xmlrpc.server.XmlRpcServerWorker.execute(XmlRpcServerWorker.java:46) at org.apache.xmlrpc.server.XmlRpcServer.execute(XmlRpcServer.java:86) at org.apache.xmlrpc.server.XmlRpcStreamServer.execute(XmlRpcStreamServer.java:200) at org.apache.xmlrpc.webserver.Connection.run(Connection.java:208) at org.apache.xmlrpc.util.ThreadPool$Poolable$1.run(ThreadPool.java:68)Caused by: java.lang.RuntimeException: java.lang.InterruptedException at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:768) at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:426) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:165) at org.jboss.remoting.Client.invoke(Client.java:1724) at org.jboss.remoting.Client.invoke(Client.java:629) at org.jboss.remoting.Client.invoke(Client.java:617) at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189) ... 38 moreCaused by: java.lang.InterruptedException at EDU.oswego.cs.dl.util.concurrent.Semaphore.attempt(Semaphore.java:120) at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:1048) at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:762) ... 44 more
It looks to me that the error is due to some error in handling the threads. It would be nice if any of you could give me pointer or if you had similar problems to let me know how have you addressed it.
thanks!
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/566742#566742]
Start a new discussion in JBoss Messaging Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 6 months
[JBoss Tools Development] - Tools 3.2 import of maven web projects adding files and directories
by Jay Balunas
Jay Balunas [http://community.jboss.org/people/jbalunas%40redhat.com] created the discussion
"Tools 3.2 import of maven web projects adding files and directories"
To view the discussion, visit: http://community.jboss.org/message/566538#566538
--------------------------------------------------------------
Hi Guys,
I upgraded to the latest milestone of 3.2, and imported a clean checkout of the richfaces project using m2eclipse. Everything seemed to go ok, until I checked modified files.
It looks like the import ( even with build automatically turned off updated the RichFaces examples:
? ui/input/api/src/main/java/META-INF
? ui/input/ui/src/main/java/META-INF
? ui/output/api/src/main/java/META-INF
? ui/output/ui/src/main/java/META-INF
? ui/dist/richfaces-components-api/META-INF
? ui/dist/richfaces-components-ui/META-INF
? ui/common/api/src/main/java/META-INF
? ui/common/ui/src/main/java/META-INF
? ui/core/api/src/main/java/META-INF
? ui/misc/ui/src/main/java/META-INF
? ui/iteration/api/src/main/java/META-INF
? ui/iteration/ui/src/main/java/META-INF
? examples/input-demo/src/main/webapp/WEB-INF/lib
M examples/input-demo/src/main/webapp/WEB-INF/web.xml
? examples/richfaces-showcase/src/main/webapp/META-INF
M examples/richfaces-showcase/src/main/webapp/WEB-INF/web.xml
? examples/output-demo/src/main/webapp/WEB-INF/lib
M examples/output-demo/src/main/webapp/WEB-INF/web.xml
M examples/repeater-demo/src/main/webapp/WEB-INF/web.xml
? examples/core-demo/src/main/webapp/META-INF
? examples/core-demo/src/main/webapp/WEB-INF/lib
M examples/core-demo/src/main/webapp/WEB-INF/web.xml
? ui/input/api/src/main/java/META-INF
I'll add what the differences are in another post.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/566538#566538]
Start a new discussion in JBoss Tools Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 6 months