[JBoss AS 7 Development] - Hibernate Issue
by Phanor Coll
Phanor Coll [https://community.jboss.org/people/pcoll] created the discussion
"Hibernate Issue"
To view the discussion, visit: https://community.jboss.org/message/723650#723650
--------------------------------------------------------------
Im trying to use Hibernate 4.1 but i get this error when trying to insert:
Im I missing something?
Mar 13, 2012 11:27:54 PM org.hibernate.annotations.common.Version <clinit>
INFO: HCANN000001: Hibernate Commons Annotations {4.0.1.Final}
Mar 13, 2012 11:27:54 PM org.hibernate.Version logVersion
INFO: HHH000412: Hibernate Core {4.1.1}
Mar 13, 2012 11:27:54 PM org.hibernate.cfg.Environment <clinit>
INFO: HHH000206: hibernate.properties not found
Mar 13, 2012 11:27:54 PM org.hibernate.cfg.Environment buildBytecodeProvider
INFO: HHH000021: Bytecode provider name : javassist
Mar 13, 2012 11:27:54 PM org.hibernate.cfg.Configuration configure
INFO: HHH000043: Configuring from resource: /hibernate.cfg.xml
Mar 13, 2012 11:27:54 PM org.hibernate.cfg.Configuration getConfigurationInputStream
INFO: HHH000040: Configuration resource: /hibernate.cfg.xml
Mar 13, 2012 11:27:54 PM org.hibernate.internal.util.xml.DTDEntityResolver resolveEntity
WARN: HHH000223: Recognized obsolete hibernate namespace http://hibernate.sourceforge.net/ http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!
Mar 13, 2012 11:27:54 PM org.hibernate.cfg.Configuration doConfigure
INFO: HHH000041: Configured SessionFactory: null
Mar 13, 2012 11:27:54 PM org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl configure
INFO: HHH000402: Using Hibernate built-in connection pool (not for production use!)
Mar 13, 2012 11:27:54 PM org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl configure
INFO: HHH000115: Hibernate connection pool size: 20
Mar 13, 2012 11:27:54 PM org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl configure
INFO: HHH000006: Autocommit mode: false
Mar 13, 2012 11:27:54 PM org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl configure
INFO: HHH000401: using driver [com.mysql.jdbc.Driver] at URL [jdbc:mysql://localhost/gowidata]
Mar 13, 2012 11:27:54 PM org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl configure
INFO: HHH000046: Connection properties: {user=desarrollo, password=****}
Mar 13, 2012 11:27:55 PM org.hibernate.dialect.Dialect <init>
INFO: HHH000400: Using dialect: org.hibernate.dialect.MySQLDialect
Mar 13, 2012 11:27:55 PM org.hibernate.engine.transaction.internal.TransactionFactoryInitiator initiateService
INFO: HHH000399: Using default transaction strategy (direct JDBC transactions)
Mar 13, 2012 11:27:55 PM org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory <init>
INFO: HHH000397: Using ASTQueryTranslatorFactory
Initial SessionFactory creation failed.org.hibernate.HibernateException: Error applying BeanValidation relational constraints
Exception in thread "main" java.lang.ExceptionInInitializerError
at gowiico.utilidades.HibernateUtil.buildSessionFactory(HibernateUtil.java:24)
at gowiico.utilidades.HibernateUtil.<clinit>(HibernateUtil.java:14)
at gowiico.test.BdTest.main(BdTest.java:22)
Caused by: org.hibernate.HibernateException: Error applying BeanValidation relational constraints
at org.hibernate.cfg.beanvalidation.BeanValidationIntegrator.applyRelationalConstraints(BeanValidationIntegrator.java:219)
at org.hibernate.cfg.beanvalidation.BeanValidationIntegrator.integrate(BeanValidationIntegrator.java:126)
at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:304)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1740)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1778)
at gowiico.utilidades.HibernateUtil.buildSessionFactory(HibernateUtil.java:19)
... 2 more
Caused by: java.lang.reflect.InvocationTargetException
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.hibernate.cfg.beanvalidation.BeanValidationIntegrator.applyRelationalConstraints(BeanValidationIntegrator.java:208)
... 7 more
Caused by: java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
at org.hibernate.validator.util.LoggerFactory.make(LoggerFactory.java:29)
at org.hibernate.validator.util.Version.<clinit>(Version.java:24)
at org.hibernate.validator.engine.ConfigurationImpl.<clinit>(ConfigurationImpl.java:59)
at org.hibernate.validator.HibernateValidator.createGenericConfiguration(HibernateValidator.java:41)
at javax.validation.Validation$GenericBootstrapImpl.configure(Validation.java:269)
at javax.validation.Validation.buildDefaultValidatorFactory(Validation.java:111)
at org.hibernate.cfg.beanvalidation.TypeSafeActivator.getValidatorFactory(TypeSafeActivator.java:521)
at org.hibernate.cfg.beanvalidation.TypeSafeActivator.applyDDL(TypeSafeActivator.java:119)
... 12 more
Caused by: java.lang.ClassNotFoundException: org.slf4j.LoggerFactory
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
... 20 more
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/723650#723650]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 9 months
[JBoss Web Development] - Re: problem occurs in jboss when two wars are deployed
by Yuanjia Chi
Yuanjia Chi [https://community.jboss.org/people/jack_chi] created the discussion
"Re: problem occurs in jboss when two wars are deployed"
To view the discussion, visit: https://community.jboss.org/message/723641#723641
--------------------------------------------------------------
Thank you for your suggestion,I have cracked it already.
The reason could be like that: my war include a servlet,many threads will start when servlet init,and the servlet init as the jboss start.
the most important point is that : as threads(many threads will start when servlet init) start,they blocking many jboss inner threads。
It leads jboss http service can't be accessed normally。
So I change the servlet init configuration,many threads won't start when servlet init,It work,jboss http service can be accessed normally。
In a word,threads blocking the jboss inner threads,we must ensure jboss start completly.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/723641#723641]
Start a new discussion in JBoss Web Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 9 months
[EJB3 Development] - Unable to call SFSB from jsf.. javax.naming.NameNotFoundException
by Phanor Coll
Phanor Coll [https://community.jboss.org/people/pcoll] created the discussion
"Unable to call SFSB from jsf.. javax.naming.NameNotFoundException"
To view the discussion, visit: https://community.jboss.org/message/723542#723542
--------------------------------------------------------------
I get javax.naming.NameNotFoundException when trying to call a SFSB..here is my code:
*Interface*
@Remote
public interface UsuarioCrearCuenta {
void agregarInfoCuentaUsuario(InfoCuentaUsuario infocuentaUsuario);
void agregarInfoGeneralUsuario(InfoGeneralUsuario infogeneralUsuario);
void agregarPlanUsuario(InfoPlanUsuario infoplanUsuario);
@Remove
void crearCuenta();
@Remove
void cancelar();
}
*BEAN*
@Stateful(name="UsuarioCrearCuenta")
@Remote(UsuarioCrearCuenta.class)
public class UsuarioCrearCuentaBean implements UsuarioCrearCuenta {
private InfoCuentaUsuario infocuentausuario;
private InfoGeneralUsuario infogeneralusuario;
private InfoPlanUsuario infoplanusuario;
public UsuarioCrearCuentaBean(){}
@PostConstruct
@PostActivate
public void openConnection() {
System.out.println("se cargo UsuarioCrearCuenta - Iniciado proceso de creacion de cuenta");
}
@Override
public void agregarInfoCuentaUsuario(InfoCuentaUsuario infocuentaUsuario) {
this.infocuentausuario=infocuentaUsuario;
}
@Override
public void agregarInfoGeneralUsuario(InfoGeneralUsuario infogeneralUsuario) {
this.infogeneralusuario=infogeneralUsuario;
}
@Override
public void agregarPlanUsuario(InfoPlanUsuario infoplanUsuario) {
this.infoplanusuario=infoplanUsuario;
}
@Remove
public void cancelar() {
infogeneralusuario = null;
infocuentausuario = null;
infoplanusuario = null;
System.out.println("se cancelo la creacion de la cuenta");
}
@Remove
public void crearCuenta() {
System.out.println("se creo la cuenta");
}
@PrePassivate
@PreDestroy
public void cleanup() {
System.out.println("se elimino el session beean UsuarioCrearCuenta");
}
}
*CLIENTE*
@ManagedBean(name="creadorCuentaUsuario")
public class CrearCuenta {
private static UsuarioCrearCuenta crearcuentausuario;
public String crear(){
try {
InitialContext context=new InitialContext();
crearcuentausuario=(UsuarioCrearCuenta) context.lookup("*gowiico/buslogic/UsuarioCrearCuentaBean/remote*");
System.out.println("loading UsuarioCrearCuenta Bean");
return "steps";
} catch (NamingException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
return "steps";
}
}
*when I execute the method crear() from a JSF, I get this error:*
10:29:39,110 ERROR [stderr] (http--127.0.0.1-8080-3) javax.naming.NameNotFoundException: gowiico/buslogic/UsuarioCrearCuentaBean/remote -- service jboss.naming.context.java.gowiico.buslogic.UsuarioCrearCuentaBean.remote
10:29:39,111 ERROR [stderr] (http--127.0.0.1-8080-3) at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97)
10:29:39,111 ERROR [stderr] (http--127.0.0.1-8080-3) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177)
10:29:39,112 ERROR [stderr] (http--127.0.0.1-8080-3) at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113)
10:29:39,112 ERROR [stderr] (http--127.0.0.1-8080-3) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:213)
10:29:39,112 ERROR [stderr] (http--127.0.0.1-8080-3) at javax.naming.InitialContext.lookup(InitialContext.java:392)
10:29:39,113 ERROR [stderr] (http--127.0.0.1-8080-3) at gowiico.buslogic.CrearCuenta.crear(CrearCuenta.java:60)
10:29:39,113 ERROR [stderr] (http--127.0.0.1-8080-3) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
10:29:39,114 ERROR [stderr] (http--127.0.0.1-8080-3) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
10:29:39,114 ERROR [stderr] (http--127.0.0.1-8080-3) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
10:29:39,115 ERROR [stderr] (http--127.0.0.1-8080-3) at java.lang.reflect.Method.invoke(Method.java:597)
10:29:39,115 ERROR [stderr] (http--127.0.0.1-8080-3) at org.apache.el.parser.AstValue.invoke(AstValue.java:262)
10:29:39,115 ERROR [stderr] (http--127.0.0.1-8080-3) at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:278)
10:29:39,116 ERROR [stderr] (http--127.0.0.1-8080-3) at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105)
10:29:39,116 ERROR [stderr] (http--127.0.0.1-8080-3) at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
10:29:39,117 ERROR [stderr] (http--127.0.0.1-8080-3) at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
10:29:39,117 ERROR [stderr] (http--127.0.0.1-8080-3) at javax.faces.component.UICommand.broadcast(UICommand.java:315)
10:29:39,118 ERROR [stderr] (http--127.0.0.1-8080-3) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794)
10:29:39,118 ERROR [stderr] (http--127.0.0.1-8080-3) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259)
10:29:39,119 ERROR [stderr] (http--127.0.0.1-8080-3) at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81)
10:29:39,119 ERROR [stderr] (http--127.0.0.1-8080-3) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
10:29:39,120 ERROR [stderr] (http--127.0.0.1-8080-3) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
10:29:39,121 ERROR [stderr] (http--127.0.0.1-8080-3) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593)
10:29:39,121 ERROR [stderr] (http--127.0.0.1-8080-3) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
10:29:39,122 ERROR [stderr] (http--127.0.0.1-8080-3) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
10:29:39,123 ERROR [stderr] (http--127.0.0.1-8080-3) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
10:29:39,124 ERROR [stderr] (http--127.0.0.1-8080-3) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
10:29:39,124 ERROR [stderr] (http--127.0.0.1-8080-3) at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154)
10:29:39,125 ERROR [stderr] (http--127.0.0.1-8080-3) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
10:29:39,126 ERROR [stderr] (http--127.0.0.1-8080-3) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
10:29:39,127 ERROR [stderr] (http--127.0.0.1-8080-3) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
10:29:39,127 ERROR [stderr] (http--127.0.0.1-8080-3) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
10:29:39,128 ERROR [stderr] (http--127.0.0.1-8080-3) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
10:29:39,129 ERROR [stderr] (http--127.0.0.1-8080-3) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)
10:29:39,129 ERROR [stderr] (http--127.0.0.1-8080-3) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)
10:29:39,130 ERROR [stderr] (http--127.0.0.1-8080-3) at java.lang.Thread.run(Thread.java:662)
How can I fix this, what Im I doing wrong?? I'm using JbossAS7.1 and Jboss Developer Studio.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/723542#723542]
Start a new discussion in EJB3 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 9 months
[JBoss Transactions Development] - XTSTestingCurrentStatus
by Paul Robinson
Paul Robinson [https://community.jboss.org/people/paul.robinson] modified the document:
"XTSTestingCurrentStatus"
To view the document, visit: https://community.jboss.org/docs/DOC-17242
--------------------------------------------------------------
h1. XTS Testing
h1. Current Status and Roadmap
h1.
This Document describes the current status of the XTS tests and what technology they use. There are currently three sets of tests, Unit, Interop and recovery. Each of these is described in turn, and a list of required improvements is presented.
All improvements are targeted at Narayana 5.x unless specified otherwise.
h2. Unit tests
Each XTS component has a set of unit tests. These tests need to be ran within an instance of JBoss AS. These tests are fully automated by an Ant script ran by Hudson.
h3. Improvements
*High Priority (EAP 6.0)*
1. *Ensure AS 7 compatibility.* See issue JBTM-900 (https://issues.jboss.org/browse/JBTM-900).
2. *CI with JBossAS*. This will ensure that changes to components, we depend upon (like JbossWS), that break XTS are spotted at QE time rather than after release. (EAP 6 requirement). https://issues.jboss.org/browse/JBQA-5191 JBQA-5191
3. *Additional Testing*. XTS Demo tests JBQA-5194 (https://issues.jboss.org/browse/JBQA-5194)
*Medium Priority (Narayana 5, EAP 7)*
1. *Automate Emma and collate results*. Emma should be used to obtain coverage stats on the test run. Emma, produces individual reports per test, by default. It would be better to have these reports combined as we are concerned with the overall test coverage, rather than the coverage of each test. Ideally we would combine coverage stats over all sets of tests (unit, interop and recovery). Next step would be to improve the coverage where necessary. https://issues.jboss.org/browse/JBTM-952 JBTM-952
*Low Priority* *(**Narayana 5, EAP 7**)*
1. *Migrate to Maven*. For consistency with rest of the Narayna project. https://issues.jboss.org/browse/JBTM-945 JBTM-945
2. *Update to use Arquillian*. This would mean that that they can be ran from anywhere that can run JUnit tests, such as an IDE or maven. It would also automate the app server lifecycle and test deployment. https://issues.jboss.org/browse/JBTM-954 JBTM-954
3. *Remove home-brew SOAP stack*. In the past these tests used a mock/simple SOAP stack developed specifically for the tests. This stack is no longer used as the tests run within JBoss AS. This code is redundant and should be removed. https://issues.jboss.org/browse/JBTM-953 JBTM-953
h2. Interop Tests
We have two sets of interop tests that live in "XTS/interop". These are built with ant. They are each ran by deploying them as a war to a single JBoss instance which deploys the services needed by the test. This war also exposes a web interface that on request runs the tests and relays the results in the http response.
This process is automated by using ant to deploy the war and then making the http request and validating the response. See here in code for scripts: “XTS/localjunit/run-interop-tests.xml” and “XTS/localjunit/run-tests.xml”
h3. Improvements
*High Priority (EAP 6.0)*
1. *Ensure AS 7 compatibility.* See issue JBTM-905 (https://issues.jboss.org/browse/JBTM-905).
2. *Move into the AS test suite*. https://issues.jboss.org/browse/JBQA-5192 JBQA-5192
*Medium Priority (**Narayana 5, EAP 7**)*
1. *Automate Emma and collate results*. https://issues.jboss.org/browse/JBTM-952 JBTM-952
*Low Priority (**Narayana 5, EAP 7**)*
1. *Update to use Arquillian*. https://issues.jboss.org/browse/JBTM-955 JBTM-955 https://issues.jboss.org/browse/JBTM-956 JBTM-956
2. *Migrate to Maven*. https://issues.jboss.org/browse/JBTM-943 JBTM-943
h2. Recovery Tests
The recovery tests are the tricky ones. At the moment we have a set of test scenarios that run in a single JBoss server invoked by a remote client. There are also a set of Byteman scripts that trigger failure at certain points in a scenario. There are many different permutations of scenario and Byteman scripts that each create a particular test.
The test scenarios log their progress through the protocol and recovery. On completion of a test run, a human needs to look over the trace and check that it looks right. This process is hard to automate as the trace produced can have many valid interleavings. This is due to the asynchronous nature of the application.
These tests are automated with a bash script, but the output traces must be verified manually by a human. The other problem is that they currently run in a single JBoss server which simulates the situation where every party in the protocol is located in the same app server and crashes & recovers at the same time (not that realistic!). In order to test with multiple servers. we would need a way of combining the traces from each server when verifying the outcome of the test. This could be done by implementing a Byteman helper class, but it would not be trivial.
h3. Improvements
*High Priority (EAP 6.0)*
1. *Move into AS test suite*. The tests are unlikely to be accepted in their current form, due to the level of manual intervention required. This improvement can not be made until we have sufficiently automated the process.
2. *Ensure AS 7 compatibility.* JBTM-923 (https://issues.jboss.org/browse/JBTM-923)
3. *Automate running*. Use Arquillian to automate the tests and generate trace output for human verification. JBQA-3926 (https://issues.jboss.org/browse/JBQA-3926) JBTM-817 (https://issues.jboss.org/browse/JBTM-817)
4. *Run as part of CI.* https://issues.jboss.org/browse/JBTM-1029 JBTM-1029
*Medium priority (**Narayana 5, EAP 7**)*
1. *Automate Emma and collate results*. https://issues.jboss.org/browse/JBTM-952 JBTM-952
*Low Priority (**Narayana 5, EAP 7**)
*
1. *Migrate to Maven.* https://issues.jboss.org/browse/JBTM-944 JBTM-944*
*
2. *Automate verification*. Remove the human verification steps. https://issues.jboss.org/browse/JBTM-949 JBTM-949
3. *Multiple Server Tests*. If step 2) is successful, we could be able to build the more complex scenarios where each party runs in its own JBoss server. https://issues.jboss.org/browse/JBTM-950 JBTM-950
4. *Additional Tests*. Andrew Dinn has provided a set of additional tests for us to consider implementing. These should be considered alongside the Emma coverage data for future work. https://issues.jboss.org/browse/JBTM-951 JBTM-951
h2.
h2. Notes
* Arquillian supports multiple JBoss servers:* https://docs.jboss.org/author/display/ARQ/Multiple+Containers https://docs.jboss.org/author/display/ARQ/Multiple+Containers
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-17242]
Create a new document in JBoss Transactions Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
13 years, 9 months
[JBoss Web Development] - Fehler bei Deploying: secure not found as a child of jboss
by solna
solna [https://community.jboss.org/people/solna] created the discussion
"Fehler bei Deploying: secure not found as a child of jboss"
To view the discussion, visit: https://community.jboss.org/message/723231#723231
--------------------------------------------------------------
Hallo zusammen,
Ich habe jboss 5.1.0.GA.
Bei Deploying bekomme folgender Fehler:
org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/opt/jboss-5.1.0.GA/server/default/deploy/Anwendung.war...
.......
.......
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: secure not found as a child of jboss in unordered_sequence: webservices? resource-managers? jmx-name?...
Mein web.xml:
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="2.5"
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
<display-name>bla bla</display-name>
<description>
This is a simple web application with a source code organization
based on the recommendations of the Application Developer's Guide.
</description>
<filter>
<filter-name>springSecurityFilterChain</filter-name>
<filter-class>org.springframework.web.filter.DelegatingFilterProxy</filter-class>
</filter>
<filter-mapping>
<filter-name>springSecurityFilterChain</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
<filter>
<filter-name>encoding-filter</filter-name>
<filter-class>org.springframework.web.filter.CharacterEncodingFilter</filter-class>
<init-param>
<param-name>encoding</param-name>
<param-value>UTF-8</param-value>
</init-param>
</filter>
<servlet>
<servlet-name>
Locks
</servlet-name>
<servlet-class>
servlets.LocksServlet
</servlet-class>
</servlet>
</web-app>
Mein jboss-web.xml
<?xml version='1.0' encoding='UTF-8' ?>
<!DOCTYPE jboss-web PUBLIC
-//JBoss//DTD Web Application 5.0//EN
http://www.jboss.org/j2ee/dtd/jboss-web_5_0.dtd>
<jboss-web>
<class-loading>
<loader-repository>
com.example:archive=Anwendung.war
<loader-repository-config>java2ParentDelegation=false</loader-repository-config>
</loader-repository>
</class-loading>
<context-root>Anwendung</context-root>
</jboss-web>
Was mache ich falsch? Steht dann <secure> nicht default auf "false"?
Habe leider kein Antwort beim googeln gefunden.
Danke
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/723231#723231]
Start a new discussion in JBoss Web Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 9 months
[JBoss AS 7 Development] - is Jboss 7.1.0 Final compatible with IPv 6 ?
by fan kam thong
fan kam thong [https://community.jboss.org/people/ktfan] created the discussion
"is Jboss 7.1.0 Final compatible with IPv 6 ?"
To view the discussion, visit: https://community.jboss.org/message/722336#722336
--------------------------------------------------------------
Is Jboss 7.1.0 Final compatible with IPv 6 ?
I have followed the Admin guide https://docs.jboss.org/author/display/AS71/Interfaces+and+ports https://docs.jboss.org/author/display/AS71/Interfaces+and+ports to set up the IPv 6 support.
However I have encountered the following ERROR(s) while using the standalone.bat to start the JBoss AS.
+11:33:10,511 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC0000+
+1: Failed to start service jboss.serverManagement.controller.management.http: or+
+g.jboss.msc.service.StartException in service jboss.serverManagement.controller.+
+management.http: java.net.SocketException: Address family not supported by proto+
+col family: bind+
+ at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementSe+
+rvice.java:199) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]+
+ at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Se+
+rviceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]+
+ at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceCont+
+rollerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]+
+ at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec+
+utor.java:886) [rt.jar:1.6.0_21]+
+ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor+
+.java:908) [rt.jar:1.6.0_21]+
+ at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_21]+
+Caused by: java.net.SocketException: Address family not supported by protocol fa+
+mily: bind+
+ at sun.nio.ch.Net.bind(Native Method) [rt.jar:1.6.0_21]+
+ at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:+
+119) [rt.jar:1.6.0_21]+
+ at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [rt.+
+jar:1.6.0_21]+
+ at org.jboss.sun.net.httpserver.ServerImpl.<init>(ServerImpl.java:144)+
+ at org.jboss.sun.net.httpserver.HttpServerImpl.<init>(HttpServerImpl.jav+
+a:54)+
+ at org.jboss.sun.net.httpserver.DefaultHttpServerProvider.createHttpServ+
+er(DefaultHttpServerProvider.java:38)+
+ at org.jboss.com.sun.net.httpserver.HttpServer.create(HttpServer.java:14+
+7)+
+ at org.jboss.as.domain.http.server.ManagementHttpServer.create(Managemen+
+tHttpServer.java:143)+
+ at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementSe+
+rvice.java:164) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]+
+ ... 5 more+
+11:33:10,509 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC0000+
+1: Failed to start service jboss.remoting.server.management: org.jboss.msc.servi+
+ce.StartException in service jboss.remoting.server.management: JBAS017113: Faile+
+d to start service+
+ at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStrea+
+mServerService.java:112)+
+ at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Se+
+rviceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]+
+ at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceCont+
+rollerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]+
+ at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec+
+utor.java:886) [rt.jar:1.6.0_21]+
+ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor+
+.java:908) [rt.jar:1.6.0_21]+
+ at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_21]+
+Caused by: java.net.SocketException: Address family not supported by protocol fa+
+mily: bind+
+ at sun.nio.ch.Net.bind(Native Method) [rt.jar:1.6.0_21]+
+ at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:+
+119) [rt.jar:1.6.0_21]+
+ at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [rt.+
+jar:1.6.0_21]+
+ at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52) [rt.+
+jar:1.6.0_21]+
+ at org.xnio.nio.NioXnioWorker.createTcpServer(NioXnioWorker.java:287)+
+ at org.xnio.XnioWorker.createStreamServer(XnioWorker.java:135)+
+ at org.jboss.remoting3.remote.RemoteConnectionProvider$ProviderInterface+
+.createServer(RemoteConnectionProvider.java:209)+
+ at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStrea+
+mServerService.java:102)+
+ ... 5 more+
+11:33:10,509 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC0000+
+1: Failed to start service jboss.remoting.server.remoting-connector: org.jboss.m+
+sc.service.StartException in service jboss.remoting.server.remoting-connector: J+
+BAS017113: Failed to start service+
+ at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStrea+
+mServerService.java:112)+
+ at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Se+
+rviceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]+
+ at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceCont+
+rollerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]+
+ at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec+
+utor.java:886) [rt.jar:1.6.0_21]+
+ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor+
+.java:908) [rt.jar:1.6.0_21]+
+ at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_21]+
+Caused by: java.net.SocketException: Address family not supported by protocol fa+
+mily: bind+
+ at sun.nio.ch.Net.bind(Native Method) [rt.jar:1.6.0_21]+
+ at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:+
+119) [rt.jar:1.6.0_21]+
+ at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [rt.+
+jar:1.6.0_21]+
+ at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52) [rt.+
+jar:1.6.0_21]+
+ at org.xnio.nio.NioXnioWorker.createTcpServer(NioXnioWorker.java:287)+
+ at org.xnio.XnioWorker.createStreamServer(XnioWorker.java:135)+
+ at org.jboss.remoting3.remote.RemoteConnectionProvider$ProviderInterface+
+.createServer(RemoteConnectionProvider.java:209)+
+ at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStrea+
+mServerService.java:102)+
+ ... 5 more+
I have enabled IPv 6 address with the JVM options under my *standalone.config.bat*
*set "JAVA_OPTS=%JAVA_OPTS% -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true"*
and I have changed the interfaces under my *standalone.xml* as
+<interfaces>+
+ <interface name="management"> +
+ <inet-address value="${jboss.bind.address.management:[fe80::ed29:5b4b:37cc:d429]}"/>+
+ </interface>+
+ <interface name="public"> +
+ <inet-address value="${jboss.bind.address:[fe80::ed29:5b4b:37cc:d429]}"/>+
+ </interface>+
+ </interfaces>+
+ <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">+
+ <socket-binding name="http" port="8080"/>+
+ <socket-binding name="https" port="8443"/>+
+ <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/>+
+ <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>+
+ <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9443}"/>+
+ <socket-binding name="osgi-http" interface="management" port="8090"/>+
+ <socket-binding name="remoting" port="4447"/>+
+ <socket-binding name="txn-recovery-environment" port="4712"/>+
+ <socket-binding name="txn-status-manager" port="4713"/>+
+ <outbound-socket-binding name="mail-smtp">+
+ <remote-destination host="localhost" port="25"/>+
+ </outbound-socket-binding>+
+ </socket-binding-group>+
What other configuration I have to make changes to ? Your advice is very much appreciated. Thanks in advance.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/722336#722336]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 9 months