[JBoss Tools] - How to define multiple jboss 7 server instances based on the standalone folder using eclipse juno and jboss tools 4.0
by Marc Gagnon
Marc Gagnon [https://community.jboss.org/people/MarcGagnonPincourt] modified the document:
"How to define multiple jboss 7 server instances based on the standalone folder using eclipse juno and jboss tools 4.0"
To view the document, visit: https://community.jboss.org/docs/DOC-48321
--------------------------------------------------------------
How to define multiple jboss 7 server instances based on the standalone folder using eclipse juno and jboss tools 4.0
I posted this in the general Jboss 7 discussion and then realized I could write it as a document...
Assume you are developping applications on your PC...
You might want to do deploy multiple instances when you need to deploy two applications, each one having different configuration.
Another reason might be that you have two applications that must be running but one of these will be stopped and restarted often while the other one could stay up. If the application which could stay up takes a while to deploy, you definitely prefer to run it in a different server instance.
It is true that we can deploy all applications in the same JBoss instance.
But sometimes, we need to isolate a specific instance with specific configuration files.
In previous versions of the JBoss server, all we had to do was to copy “server/default” to “server/foo” + provide an offset for ports.
In eclipse, the jboss plugin has to be updated.
See: http://www.eclipse.org/forums/index.php?t=msg&goto=489439 http://www.eclipse.org/forums/index.php?t=msg&goto=489439
Or: http://stackoverflow.com/questions/173487/problems-with-shutting-down-jbo... http://stackoverflow.com/questions/173487/problems-with-shutting-down-jbo...
Now, different JBoss version, different problem...
Let’s say we have this situation with application “foo” and “bar”.
Let’s say also that you want to use the basic standalone server configuration.
I will assume you are running eclipse on a windows PC with JBoss-7.1.1.Final.
Assume also that the JBoss home is C:\tools\jboss\jboss-as-7.1.1.Final
Steps to create a server instance for “foo” and control it from the command line and from eclipse:
1-From the JBoss 7 home directory, copy “standalone” to “foo”.
The goal is to leave “standalone” unmodified and work on a copy.
That way, you keep your golden master available as a base for other server instances you might need.
Of course, you could also keep a copy elsewhere.
I prefer to keep “standalone” untouched and create as many copies as necessary but this is a personal preference.
2-Update foo/standalone.xml to specify the port offset to use right in the standalone.xml configuration file like this:
...
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:10000}">
<socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/>
...
This example uses 10000 so that the resulting HTTP port will be “18080”.
Do not replace with “port-offset="10000"” : that will not work.
Believe me, we tried many combinations and this is the only way to make it work properly.
This seems to be related to the way the JBoss tools plugin works.
If you simply need to start the server from the command line, you’re done:
C:\tools\jboss-as-7.1.1.Final\bin>standalone.bat -Djboss.server.base.dir=../foo -Dorg.jboss.boot.log.file=c:\tools\jboss\jboss-as-7.1.1.Final\foo\log\boot.log -Dlogging.configuration=c:\tools\jboss\jboss-as-7.1.1.Final\foo\configuration\logging.properties
3-In eclipse, go to Window / Preferences / Server / Runtime Environments / Add
Create a runtime environment “JBoss 7.1 Runtime foo”.
The configuration file must be a relative path like this: ..\..\foo\configuration\standalone.xml
The JBoss tools eclipse seems to expect files to be in the default “standalone” folder.
4-In the server view, right click New / Server
Select JBoss Community / JBoss AS 7.1 with the runtime created at step 3.
5-In the server view, double click on the server created at step 4 (or press F3) to open the parameter editor.
In section “Server Ports”, uncheck “Detect from Local Runtime” and specify offset 10000.
Again, we spent some time checking and unchecking these options and the only way to make it work is to override only this field.
Click on the “Deployment” tab to see deployment default settings.
Select “Use a custom deploy folder” and edit the directory fields.
Replace “standalone/deployments” by “foo/deployments”.
Replace “standalone/tmp” by “foo/tmp”.
6-In the server’s parameter editor, go back to the overview, General Information, click “Open launch configuration”.
First, uncheck “Always update arguments related to the runtime”.
The “Program arguments” should look like this:
-mp "C:/tools/jboss/jboss-as-7.1.1.Final/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b 0.0.0.0 --server-config=..\..\foo\configuration\standalone.xml
You may use whatever parameters you need, the important thing for our setup is to specify the server configuration file relative to the default “standalone” path.
The VM arguments now:
-server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=C:/tools/jboss/jboss-as-7.1.1.Final/foo/log/boot.log" "-Dlogging.configuration=file:/C:/tools/jboss/jboss-as-7.1.1.Final/foo/configuration/logging.properties" "-Djboss.home.dir=C:/tools/jboss/jboss-as-7.1.1.Final" "-Djboss.server.base.dir=C:\tools\jboss\jboss-as-7.1.1.Final\foo"
Again, you may have to adjust these parameters to your needs.
The important thing is to define the following:
Boot log file : -Dorg.jboss.boot.log.file=<path to boot file>
Logging configuration file: -Dlogging.configuration=<URL to log file configuration>
Base directory: -Djboss.server.base.dir=<Instance path>
7-Try to start and stop the server, look at the output to make sure the ports have the expected offset.
Make sure everything works:
Open a browser on “localhost:18080”, then open the administrative console.
In the “Runtime” section, click “Configuration” and “Environment Properties”.
Look at, say, “catalina.home” : it should be “C:\tools\jboss\jboss-as-7.1.1.Final\foo\tmp”.
That’s it!
Like I mentioned, some paths seems to be, somehow, hard coded as “standalone/...”.
This is probably because copying “standalone” like we did with “server/default” is not a use case planned for JBoss 7.
I hope that some JBoss developpers will be able to elaborate on this.
In the mean time, maybe this post could be edited and added to https://docs.jboss.org/author/display/AS71/Starting+JBoss+AS+from+Eclipse... https://docs.jboss.org/author/display/AS71/Starting+JBoss+AS+from+Eclipse...
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-48321]
Create a new document in JBoss Tools at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
12 years, 10 months
[Datasource Configuration] - How to configure MySQL Database with Jboss Portal Bundle 2.7.4 in wondows Platform
by hira magin
hira magin [https://community.jboss.org/people/vaibhavnigam] created the discussion
"How to configure MySQL Database with Jboss Portal Bundle 2.7.4 in wondows Platform"
To view the discussion, visit: https://community.jboss.org/message/798205#798205
--------------------------------------------------------------
How to configure MySQL Database with Jboss Portal Bundle 2.7.4 in wondows Platform
Any One Can Help me . I am new in jboss portal I follow this step to configure database with jboss portal but it gives ERROR
h3. JBOSS Portal Installation
h1. Chapter 1. Download
Download JBoss portal from http://www.jboss.org/jbossportal/download/index.html.
Package: JBoss Portal + JBoss AS 4.2.3
Direct download link: http://downloads.sourceforge.net/jboss/jboss-portal-2.7.2-bundled.zip
Chapter 2. Installation
h2. 2.1 Folder structure (προτεινόμενη)
Extract jboss-portal-2.7.2-bundled.zip to a desired folder (for example C:\server\jboss). Το τελικό path του portal είναι C:\server\jboss\jboss-portal-2.7.2-bundled\jboss-portal-2.7.2
h2. 2.2 Database
Δημιουργούμε μια βάση δεδομένων (for example jboss).
+All database tables will be created for you at runtime.+
h2. 2.3 JDBC connector
Download MySQL JDBC connector from http://dev.mysql.com/downloads/connector/j/5.1.html
Το αρχείο mysql-connector-java-5.1.7-bin.jar πρέπει να τοποθετηθεί στο path $JBOSS_HOME/server/default/lib (C:\server\jboss\jboss-portal-2.7.2-bundled\jboss-portal-2.7.2\server\default\lib)
h2. 2.4 JBoss and MySQL Configuration
1. Copy C:\server\jboss\jboss-portal-2.7.2-bundled\jboss-portal-2.7.2\setup\portal-mysql5-ds.xml (for PHP5) to C:\server\jboss\jboss-portal-2.7.2-bundled\jboss-portal-2.7.2\server\default\deploy
2. Copy C:\server\jboss\jboss-portal-2.7.2-bundled\jboss-portal-2.7.2\docs\examples\jca\mysql-ds.xml to C:\server\jboss\jboss-portal-2.7.2-bundled\jboss-portal-2.7.2\server\default\deploy
3. Rename C:\server\jboss\jboss-portal-2.7.2-bundled\jboss-portal-2.7.2\server\default\deploy\portal-hsqldb-ds.xml to portal-hsqldb-ds.xml-rename (ώστε να διαβαστούν το αντίστοιχο mysql)
4. Rename C:\server\jboss\jboss-portal-2.7.2-bundled\jboss-portal-2.7.2\server\default\deploy\hsqldb-ds.xml to hsqldb-ds.xml-rename (ώστε να διαβαστούν το αντίστοιχο mysql)
h2. 2.5 Configure portal-mysql5-ds.xml and mysql-ds.xml
Τροποποίηση αυτών των αρχείων για τη σωστή σύνδεση στη βάση δεδομένων (XAMMP),
1. portal-mysql5-ds.xml: Replace PortalDS
jdbc:mysql://localhost:3306/jbossportal?useServerPrepStmts=false&jdbcCompliantTruncation=false
com.mysql.jdbc.Driver
portal
portalpassword with PortalDS
jdbc:mysql://localhost/jboss?useServerPrepStmts=false&jdbcCompliantTruncation=false
com.mysql.jdbc.Driver
root
2. mysql-ds.xml: Replace
MySqlDS
jdbc:mysql://mysql-hostname:3306/jbossdb
com.mysql.jdbc.Driver
x
y
with
MySqlDS
jdbc:mysql://localhost/jboss
com.mysql.jdbc.Driver
root
h2. 2.6 Deploy JBoss portal
Run from console C:\server\jboss\jboss-portal-2.7.2-bundled\jboss-portal-2.7.2\bin\run.bat -b 0.0.0.0
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/798205#798205]
Start a new discussion in Datasource Configuration at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 10 months
[JBoss Messaging] - Cannot insert duplicate key in object 'dbo.JBM_ID_CACHE'.
by Patricia Mitchell
Patricia Mitchell [https://community.jboss.org/people/pmitchell4] created the discussion
"Cannot insert duplicate key in object 'dbo.JBM_ID_CACHE'."
To view the discussion, visit: https://community.jboss.org/message/798178#798178
--------------------------------------------------------------
We are using JBoss 5.1.0.GA and are receiving the following error frequently in production. We have 2 JBoss instances connecting to the same SQL Server
database. The only way we have been able to resolve this issue is to delete the records in the JBM_ID_CACHE table.
2013-02-12 16:04:31,500 WARN [org.jboss.messaging.core.impl.JDBCSupport] Trying again after a pause
2013-02-12 16:04:31,729 WARN [org.jboss.messaging.core.impl.JDBCSupport] SQLException caught, SQLState 23000 code:2627- assuming deadlock detected, try:21
java.sql.SQLException: [DataDirect][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint 'PK__JBM_ID_C__009CB91350C6C558'. Cannot insert duplicate key in object 'dbo.JBM_ID_CACHE'.
at com.ddtek.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.ddtek.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.ddtek.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
at com.ddtek.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
at com.ddtek.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown Source)
at com.ddtek.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
at com.ddtek.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unknown Source)
at com.ddtek.jdbc.base.BaseStatement.commonTransitionToState(Unknown Source)
at com.ddtek.jdbc.base.BaseStatement.postImplExecute(Unknown Source)
at com.ddtek.jdbc.base.BasePreparedStatement.postImplExecute(Unknown Source)
at com.ddtek.jdbc.base.BaseStatement.commonExecute(Unknown Source)
at com.ddtek.jdbc.base.BaseStatement.executeUpdateInternal(Unknown Source)
at com.ddtek.jdbc.base.BasePreparedStatement.executeUpdate(Unknown Source)
at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:365)
at org.jboss.messaging.core.impl.JDBCPersistenceManager.cacheID(JDBCPersistenceManager.java:1637)
at org.jboss.messaging.core.impl.JDBCPersistenceManager$1AddReferenceRunner.doTransaction(JDBCPersistenceManager.java:1370)
at org.jboss.messaging.core.impl.JDBCSupport$JDBCTxRunner2.execute(JDBCSupport.java:474)
at org.jboss.messaging.core.impl.JDBCSupport$JDBCTxRunner2.executeWithRetry(JDBCSupport.java:512)
at org.jboss.messaging.core.impl.JDBCPersistenceManager.addReference(JDBCPersistenceManager.java:1408)
at org.jboss.messaging.core.impl.ChannelSupport.handle(ChannelSupport.java:227)
at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.routeInternal(MessagingPostOffice.java:2222)
at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.route(MessagingPostOffice.java:509)
at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendMessage(ServerConnectionEndpoint.java:755)
at org.jboss.jms.server.endpoint.ServerSessionEndpoint.send(ServerSessionEndpoint.java:399)
at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$send$aop(SessionAdvised.java:87)
at org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeTarget(SessionAdvised$send_7280680627620114891.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
at org.jboss.jms.server.container.SecurityAspect.handleSend(SecurityAspect.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:122)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.server.endpoint.advised.SessionAdvised.send(SessionAdvised.java)
at org.jboss.jms.wireformat.SessionSendRequest.serverInvoke(SessionSendRequest.java:95)
at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
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)
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_3721413.invoke(SessionAspect_z_handleSend_3721413.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_3721413.invoke(ProducerAspect_z_handleSend_3721413.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 com.dwsolutions.pta.ejb.services.mailmanager.MailManagerBean.sendMail(MailManagerBean.java:159)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:122)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
at org.jboss.ejb3.EJBContainerInvocationWrapper.invokeNext(EJBContainerInvocationWrapper.java:69)
at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.invoke(InterceptorSequencer.java:73)
at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:59)
at sun.reflect.GeneratedMethodAccessor2507.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.aop.advice.PerJoinpointAdvice.invoke(PerJoinpointAdvice.java:174)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.fillMethod(InvocationContextInterceptor.java:72)
at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_fillMethod_3721413.invoke(InvocationContextInterceptor_z_fillMethod_3721413.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.setup(InvocationContextInterceptor.java:88)
at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_setup_3721413.invoke(InvocationContextInterceptor_z_setup_3721413.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:56)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:68)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:190)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:186)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:176)
at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:216)
at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:207)
at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:164)
at $Proxy519.sendMail(Unknown Source)
at com.dwsolutions.pta.web.action.AccessPersonAction.sendPasswordResetEmail(AccessPersonAction.java:2050)
at com.dwsolutions.pta.web.action.AccessPersonAction.resetPassword(AccessPersonAction.java:1370)
at com.dwsolutions.pta.web.action.AccessPersonAction.execute(AccessPersonAction.java:178)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:425)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:228)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:462)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.owasp.csrfguard.CsrfGuardFilter.doFilter(CsrfGuardFilter.java:58)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.dwsolutions.pta.filter.ESAPIFilter.doFilter(ESAPIFilter.java:228)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.dwsolutions.pta.filter.CheckLogonFilter.doFilter(CheckLogonFilter.java:108)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.dwsolutions.pta.filter.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:37)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:662)
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/798178#798178]
Start a new discussion in JBoss Messaging at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 10 months
[jBPM] - Cluster Simulation with jbpm-console failing
by Anindya Saha
Anindya Saha [https://community.jboss.org/people/anindyas79] created the discussion
"Cluster Simulation with jbpm-console failing"
To view the discussion, visit: https://community.jboss.org/message/798089#798089
--------------------------------------------------------------
Hello
I am trying to simulate a cluster deployement by setting up two 5.4 jbpm-console applications (the default provided by the framework) on two different jboss 7.1.1 instances, one running at port 8080 and the other at 8180. Also I am not connecting to the guvnor but loading the process definitions from the local file system. I have configured to run the HornetQ based human task server in one of the nodes.
My idea is to run the sample evaluation process over two nodes. I would start the process on one node and the subsequent users can log in to any of the nodes to complete their respective activity.
However, I am facing an issue, whenever on the first node I log in with user id krisv and start the process and complete krisv's task, now if I want to log in as john/mary in the second node I get this exception
2013-02-18 04:14:04,191 [ERROR] The bus was disconnected by the server<br/>Additional details:<br/> Reason: There is no queue associated with this session.
I understand that this is due to the rest call to the jbpm-gwt-console-server.war... How can I simulate a cluster or multi-node deployment with the framework provided applications. Any help from the community would be really helpful.
Regards
Anindya
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/798089#798089]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 10 months
