[Clustering/JBoss] - JBoss 5.1.0.GA. Why difference between -b and -Djboss.bind.a
by kosulin
It looks like it is not possible to replace -b 0.0.0.0 with set of system properties passed to jvm with as -D parameters.
I prepare migration to JBoss 5.1.0.GA from JBoss 4.2.3, and while playing with run.conf.bat, found that -b command line option can not be mimicked with java system properties.
Here is what happens.
I do not set bind_addr in XML files.
When I use -b 0.0.0.0, I see what is actually expected (services listen on all interfaces, JGroups node name is properly assigned:
...
GMS: address is 147.249.124.180:3847 (cluster=Partition112)
...
18:00:17,046 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
...
But when I use -Djboss.bind.address=0.0.0.0, JGroups node name is not assigned properly. I am getting:
...
GMS: address is 0.0.0.0:4011 (cluster=Partition112)
...
10:01:29,377 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
...
The same happens when I use -Djboss.bind.address=0.0.0.0 -Dbind.address=0.0.0.0
Isn't JGroups supposed to use only -Djgroups.bind_address? Because it looks like the only way to make clustering work without XML is to use -b option.
Is this behavior expected?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233920#4233920
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4233920
17 years
[Microcontainer] - Re: Classloading vs. VFS
by ALRubinger
"jesper.pedersen" wrote : anonymous wrote :
| | Looks like the NCDFE is blocking you from doing that. Which is another issue alltogether. Due to parent>child delegation and leaking of class references, we've got to be very careful what's on the application CP, URLCL, etc.
| |
| I only have an AppCL which has my Main and is a parent to the URLCL which has all the JARs. The URLCL is passed to the ServerFactory in bootstrap.
Right, what I'm getting at is the "all the JARs" part. Take a look at how restrictive/careful we've gotta be in AS, for example:
/**
| * The default list of boot libraries. Does not include
| * the JAXP or JMX impl, users of this class should add the
| * proper libraries.
| * TODO: use vfs to list the root directory
| * http://www.jboss.org/index.html?module=bb&op=viewtopic&t=153175
| *
| * Copied from legacy bootstrap ServerLoader
| * //TODO JBAS-6920
| */
| @Deprecated
| public static final String[] DEFAULT_BOOT_LIBRARY_LIST =
| {
| // Concurrent
| "concurrent.jar",
| // Logging
| "log4j-boot.jar",
| "jboss-logging-spi.jar",
| "jboss-logging-log4j.jar",
| "jboss-logging-jdk.jar",
| "jboss-logmanager.jar",
| "jboss-logbridge.jar",
| // Common jars
| "jboss-common-core.jar",
| "jboss-xml-binding.jar",
| // Bootstrap
| "jboss-bootstrap-spi.jar",
| "jboss-bootstrap-spi-as.jar",
| "jboss-bootstrap-spi-mc.jar",
| "jboss-bootstrap-impl-base.jar",
| "jboss-bootstrap-impl-as.jar",
| "jboss-bootstrap-impl-mc.jar",
| // Microcontainer
| "javassist.jar",
| "jboss-reflect.jar",
| "jboss-mdr.jar",
| "jboss-dependency.jar",
| "jboss-kernel.jar",
| "jboss-metatype.jar",
| "jboss-managed.jar",
| // Fixme ClassLoading
| "jboss-vfs.jar",
| "jboss-classloading-spi.jar",
| "jboss-classloader.jar",
| "jboss-classloading.jar",
| "jboss-classloading-vfs.jar",
| // Fixme aop
| "jboss-aop.jar",
| "jboss-aop-mc-int.jar",
| "trove.jar",};
That's in Main. Any more/less leads to NCDFE.
"jesper.pedersen" wrote : We should make sure that impl-mc meets most of the requirements for projects using the MC as the foundation. Otherwise each project has to implement an extension to fill in the blanks.
So I suppose the question on the table is whether MCServer should init VFS automatically. While convenient, the thing there is that this isn't really MCServer's job (because it implies VFS will always be used). Opinions?
S,
ALR
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233914#4233914
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4233914
17 years
[JCA/JBoss] - "Connection is not associated with a managed connection", Ca
by spotlight2001
I moved a legacy app (jboss328SP1 hibernate 2x) to a jboss501ga.
datasource type:
<local-tx-datasource>
In my tests no errors. In production (only with a lot of users) I encountered:
| Connection is not associated with a managed connection.org.jboss.resource.adapter.jdbc.jdk6.WrappedConnectionJDK6@7cb375d0
|
interpretation: over jdbc connection, a jboss connection is wrapped
but the wrapper is empty. the original jdbc connection inside is no longer there. (according to the jboss5 source)
in the log I found more information above:
| Closing a connection for you. Please close them yourself
|
interpretation:
org.jboss.resource.connectionmanager.CachedConnectionInterceptor
this class is charged with closing connections which it thinks are no longer needed.
So what can I do? In my test-environment I am unable to reproduce these errors.
Q1) How can I reproduce such an error in my test environment.
Q2) Will these params help (postgres) against "Connection is not associated with a managed connection"?
<new-connection-sql>select 1</new-connection-sql>
<check-valid-connection-sql>select 1</check-valid-connection-sql>
<min-pool-size>5</min-pool-size>
<max-pool-size>20</max-pool-size>
<idle-timeout-minutes>10</idle-timeout-minutes>
Any ideas where to search for an answer?
I used google.
| 2009-05-28 11:13:37,414 [http-0.0.0.0-443-9] ERROR at.iqsoft.vokappl.web.action.LogonAction - Fatal error trying to obtain BIN for the card
| at.iqsoft.vokappl.service.persistence.common.PersistenceException: Query creation error
| at at.iqsoft.vokappl.service.persistence.hibernate.BinDAOHibernate.findBinByBIN(BinDAOHibernate.java:64)
| at at.iqsoft.vokappl.web.action.LogonAction.logon(LogonAction.java:172)
| at sun.reflect.GeneratedMethodAccessor295.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:270)
| at org.apache.struts.actions.DispatchAction.execute(DispatchAction.java:187)
| at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
| at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
| at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
| at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
| 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 filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:104)
| 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:601)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
| at java.lang.Thread.run(Thread.java:619)
| 2009-05-28 11:13:39,829 [http-0.0.0.0-443-9] ERROR net.sf.hibernate.transaction.JDBCTransaction - Begin failed
| java.sql.SQLException: Connection is not associated with a managed connection.org.jboss.resource.adapter.jdbc.jdk6.WrappedConnectionJDK6@7cb375d0
| at org.jboss.resource.adapter.jdbc.WrappedConnection.lock(WrappedConnection.java:81)
| at org.jboss.resource.adapter.jdbc.WrappedConnection.getAutoCommit(WrappedConnection.java:468)
| at net.sf.hibernate.transaction.JDBCTransaction.begin(JDBCTransaction.java:40)
| at net.sf.hibernate.transaction.JDBCTransactionFactory.beginTransaction(JDBCTransactionFactory.java:19)
| at net.sf.hibernate.impl.SessionImpl.beginTransaction(SessionImpl.java:2252)
| at at.iqsoft.vokappl.web.action.LogoffAction.logout(LogoffAction.java:53)
| at sun.reflect.GeneratedMethodAccessor308.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233908#4233908
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4233908
17 years
[JBoss jBPM] - Re: Fork/Join Problem
by freak182
Hello,
I end my task like this:
wfEngine.signal(wfTask.path.id, null);
wfEngine.endTask(taskInstanceId, null);
but i already solve my problem. What happened is this:
anonymous wrote : 7.7. Combining your hibernate classes
|
| In your project, you might use hibernate for your persistence. Combining your persistent classes with the jBPM persistent classes is optional. There are two major benefits when combining your hibernate persistence with jBPM's hibernate persistence:
|
| First, session, connection and transaction management become easier. By combining jBPM and your persistence into one hibernate session factory, there is one hibernate session, one jdbc connection that handles both yours and jBPM's persistence. So automatically the jBPM updates are in the same transaction as the updates to your own domain model. This can eliminates the need for using a transaction manager.
|
| Secondly, this enable you to drop your hibernatable persistent object in to the process variables without any further hassle.
|
| The easiest way to integrate your persistent classes with the jBPM persistent classes is by creating one central hibernate.cfg.xml. You can take the jBPM src/config.files/hibernate.cfg.xml as a starting point and add references to your own hibernate mapping files in there.
I perform an update to the persistence class in my domain model before it work fine. Now my question is, do i have always perform an update or any transaction in my domain model before committing the jbpm transaction? Is there a way that i dont have to perform transaction in my domain model but still jbpm will work just fine?
Thanks a lot.
Cheers.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233902#4233902
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4233902
17 years