[JBoss JIRA] (JBWEB-224) No injection in AsyncListener in AS 7.1
by arjan tijms (JIRA)
arjan tijms created JBWEB-224:
---------------------------------
Summary: No injection in AsyncListener in AS 7.1
Key: JBWEB-224
URL: https://issues.jboss.org/browse/JBWEB-224
Project: JBoss Web
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: arjan tijms
Assignee: Remy Maucherat
Using JBoss AS 7.1CRb I have defined the following Servlet AsyncListener:
{code}
@ManagedBean
public class AsyncServletListener implements AsyncListener {
@Inject
private AsyncBean asyncBean;
@Override
public void onStartAsync(AsyncEvent event) throws IOException {
System.out.println("onStartAsync");
}
@Override
public void onComplete(AsyncEvent event) throws IOException {
System.out.println("onComplete");
}
@Override
public void onError(AsyncEvent event) throws IOException {
System.out.println("onError");
}
@Override
public void onTimeout(AsyncEvent event) throws IOException {
System.out.println("onTimeout");
}
}
{code}
I registered this listener on an AsyncContext as follows:
{code}
AsyncContext asyncContext = request.startAsync();
asyncContext.addListener(asyncContext.createListener(AsyncServletListener.class));
{code}
The listener is called correctly, but there's no injection happening. Everything is inside a single war and the mandatory empty beans.xml has been created. JBoss AS is indeed starting up CDI ("Starting weld service" appears in the logs).
If I run the same code in GlassFish, injection does happen.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (JBAS-9463) error : java.lang.reflect.InvocationTargetException java.sql.SQLException: Unsupported feature
by bantraj kandi (Created) (JIRA)
error : java.lang.reflect.InvocationTargetException java.sql.SQLException: Unsupported feature
----------------------------------------------------------------------------------------------
Key: JBAS-9463
URL: https://issues.jboss.org/browse/JBAS-9463
Project: Application Server 3, 4, 5 and 6
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Other
Affects Versions: JBossAS-5.1.0.GA
Environment: JBoss 5.1eap
Reporter: bantraj kandi
Priority: Critical
2011-12-23 18:18:44,406 INFO [org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider] (main) Using provided datasource
2011-12-23 18:18:45,703 INFO [org.hibernate.cfg.SettingsFactory] (main) RDBMS: Oracle, version: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, Data Mining and Real Application Testing options
2011-12-23 18:18:45,703 INFO [org.hibernate.cfg.SettingsFactory] (main) JDBC driver: Oracle JDBC driver, version: 9.2.0.1.0
2011-12-23 18:18:45,828 INFO [org.hibernate.dialect.Dialect] (main) Using dialect: org.hibernate.dialect.Oracle9iDialect
2011-12-23 18:18:45,875 INFO [org.hibernate.engine.jdbc.JdbcSupportLoader] (main) Disabling contextual LOB creation as createClob() method threw error : java.lang.reflect.InvocationTargetException
2011-12-23 18:18:45,875 WARN [org.hibernate.cfg.SettingsFactory] (main) Could not obtain connection metadata
java.sql.SQLException: Unsupported feature
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)
at oracle.jdbc.dbaccess.DBError.throwUnsupportedFeatureSqlException(DBError.java:689)
at oracle.jdbc.OracleDatabaseMetaData.supportsGetGeneratedKeys(OracleDatabaseMetaData.java:4180)
at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:125)
at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2119)
at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2115)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1339)
at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:867)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:670)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:133)
at org.jboss.jpa.deployment.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:301)
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.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)
at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:243)
at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:111)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:72)
at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221)
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42)
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:778)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:543)
at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:125)
at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:52)
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1193)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1225)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:778)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:543)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
at org.jboss.Main.boot(Main.java:221)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:619)
2011-12-23 18:18:45,890 INFO [org.hibernate.transaction.TransactionFactoryFactory] (main) Transaction strategy: org.hibernate.transaction.JDBCTransactionFactory
2011-12-23 18:18:45,890 INFO [org.hibernate.transaction.TransactionManagerLookupFactory] (main) instantiating TransactionManagerLookup: org.hibernate.transaction.JBossTransactionManagerLookup
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (JBLOGGING-76) JBoss 4.3, server.log is not logging any log messages after restart
by shiva ram (Created) (JIRA)
JBoss 4.3, server.log is not logging any log messages after restart
-------------------------------------------------------------------
Key: JBLOGGING-76
URL: https://issues.jboss.org/browse/JBLOGGING-76
Project: JBoss Logging
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jboss-logging-log4j
Affects Versions: 3.0.0.GA
Environment: Linux
Reporter: shiva ram
Assignee: David Lloyd
Hi,
We r running jboss 4.3 on linux, its a development box, issue is the application logs are not getting updated from many days and server.log is not getting updated after restart. while restarting we r getting following error in server.log
and after server start, nothing is updating in server.log after the last line of this message. (nothing is being logged anywhere, but all things r running fine, applications are accessible)
SERVER.LOG:
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss:service=WebService
State: FAILED
Reason: java.lang.Exception: Port 8083 already in use.
I Depend On:
jboss.system:service=ThreadPool
Depends On Me:
jboss.ejb:service=EJBDeployer
ObjectName: jboss.cache:service=EJB3SFSBClusteredCache
State: FAILED
Reason: org.jgroups.ChannelException: failed to start protocol stack
ObjectName: jboss.messaging:service=Connector,transport=bisocket
State: FAILED
Reason: java.net.BindException: Cannot assign requested address
Depends On Me:
jboss.messaging.connectionfactory:service=ConnectionFactory
jboss.messaging.connectionfactory:service=ClusteredConnectionFactory
jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory
jboss.messaging:service=ServerPeer
ObjectName: jboss:service=invoker,type=jrmp
State: FAILED
Reason: java.rmi.server.ExportException: Port already in use: 4444; nested exception is:
java.net.BindException: Cannot assign requested address
I Depend On:
jboss:service=TransactionManager
Depends On Me:
jboss.jmx:type=adaptor,name=Invoker,protocol=jrmp,service=proxyFactory
jboss.jca:service=DataSourceBinding,name=jdbc/globalVista
ObjectName: jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3
State: FAILED
Reason: java.net.BindException: Cannot assign requested address
I Depend On:
jboss.aop:service=AspectDeployer
ObjectName: jboss:service=Naming
State: FAILED
Reason: java.rmi.server.ExportException: Port already in use: 1098; nested exception is:
java.net.BindException: Cannot assign requested address
I Depend On:
jboss.system:service=ThreadPool
jboss:service=NamingBeanImpl
Depends On Me:
jboss.cache:service=TomcatClusteringCache
jboss:service=MYAPPLICATION10
jboss:service=HASessionState
jboss:service=invoker,type=jrmpha
jboss:service=invoker,type=pooledha
jboss.cache:service=EJB3EntityTreeCache
jboss.jmx:type=adaptor,name=Invoker,protocol=jrmp,service=proxyFactory
jboss.jmx:alias=jmx/rmi/RMIAdaptor
jboss:service=Mail
ObjectName: jboss.remoting:service=Connector,transport=socket
State: FAILED
Reason: java.net.BindException: Cannot assign requested address
I Depend On:
jboss.remoting:service=NetworkRegistry
Depends On Me:
jboss:service=invoker,type=unified
jboss:service=invoker,type=unifiedha
ObjectName: jboss:service=invoker,type=pooled
State: FAILED
Reason: java.lang.Exception: Port 4445 is already in use
I Depend On:
jboss:service=TransactionManager
at org.jboss.deployment.MainDeployer.checkIncompleteDeployments(MainDeployer.java:1385)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:785)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:513)
at java.lang.Thread.run(Thread.java:619)
INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.3.0.GA_CP07 (build: SVNTag=JBPAPP_4_3_0_GA_CP07 date=200911251949)] Started in 17s:402ms
-----------------------------------
There are many transactions going on the applications yet nothing is being logged. Can anyone know of why this is happening
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (JBAS-9466) Failed to handle message: java.lang.IllegalStateException: Cannot find binding for jms.queue
by Dileep Kumar (Created) (JIRA)
Failed to handle message: java.lang.IllegalStateException: Cannot find binding for jms.queue
--------------------------------------------------------------------------------------------
Key: JBAS-9466
URL: https://issues.jboss.org/browse/JBAS-9466
Project: Application Server 3, 4, 5 and 6
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Dileep Kumar
18:05:43,376 ERROR [org.hornetq.core.server.cluster.impl.ClusterConnectionImpl] Failed to handle message: java.lang.IllegalStateException: Cannot find binding for jms.queue.PUSHALERT4c279241-267b-11e1-af4c-f04da208cf14
at org.hornetq.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.doConsumerCreated(ClusterConnectionImpl.java:774) [:6.0.0.Final]
at org.hornetq.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.onMessage(ClusterConnectionImpl.java:568) [:6.0.0.Final]
at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:822) [:6.0.0.Final]
at org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:46) [:6.0.0.Final]
at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:940) [:6.0.0.Final]
at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100) [:6.0.0.Final]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (JBRULES-3349) Not possible to use Janino to compile templates
by Adar Dembo (JIRA)
Adar Dembo created JBRULES-3349:
-----------------------------------
Summary: Not possible to use Janino to compile templates
Key: JBRULES-3349
URL: https://issues.jboss.org/browse/JBRULES-3349
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-compiler
Affects Versions: 5.3.1.Final
Reporter: Adar Dembo
Assignee: Mark Proctor
I've got the following code in my program:
{code}
Properties props = new Properties();
props.setProperty("drools.dialect.java.compiler", "JANINO");
config = KnowledgeBuilderFactory.newKnowledgeBuilderConfiguration(props);
KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder(config);
{code}
The resulting KnowledgeBuilder compiles rules using the Janino compiler, which is important for me because I have an old JDT dependency that may not be updated.
Now I'm trying to compile templates, and I've got the following code, based on the Drools documentation:
{code}
ObjectDataCompiler converter = new ObjectDataCompiler();
InputStream templateStream = this.getClass().getResourceAsStream("Templates.drl");
String compiledTemplate = converter.compile(clusters, templateStream);
Reader compiledRules = new StringReader(compiledTemplate);
...
kbuilder.add(ResourceFactory.newReaderResource(compiledRules), ResourceType.DRL);
{code}
Unfortunately, I see the [familiar JDT error|https://community.jboss.org/wiki/RulesTomcat] in converter.compile(), indicating that Janino is not being used for template compilation. I've spent a bit of time going through the source code and I don't see a way to do this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (AS7-3114) Make the console optional
by Carlo de Wolf (Created) (JIRA)
Make the console optional
-------------------------
Key: AS7-3114
URL: https://issues.jboss.org/browse/AS7-3114
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.Beta1b
Reporter: Carlo de Wolf
Assignee: Brian Stansberry
Currently when booting without a console module you get the following error:
{noformat}
13:32:30,936 ERROR [org.jboss.msc.service.fail] MSC00001: Failed to start service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Failed to start serverManagement socket
at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:204) [jboss-as-server-7.1.0.CR1-SNAPSHOT.jar:]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.7.0_b147-icedtea]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.7.0_b147-icedtea]
at java.lang.Thread.run(Thread.java:722) [:1.7.0_b147-icedtea]
Caused by: java.io.IOException: Unable to load resource handler
at org.jboss.as.domain.http.server.ManagementHttpServer.create(ManagementHttpServer.java:177)
at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:169) [jboss-as-server-7.1.0.CR1-SNAPSHOT.jar:]
... 5 more
Caused by: org.jboss.modules.ModuleNotFoundException: Module org.jboss.as.console:main is not found in local module loader @5e5ad035 (roots: /home/carlo/work/jboss-as/build/target/jboss-as-7.1.0.CR1-SNAPSHOT/modules)
at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:126)
at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:265)
at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:212)
at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94)
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:194)
at org.jboss.as.domain.http.server.ResourceHandler.getClassLoader(ResourceHandler.java:324)
at org.jboss.as.domain.http.server.ConsoleMode$ConsoleHandler.<init>(ConsoleMode.java:99)
at org.jboss.as.domain.http.server.ConsoleMode$1.createConsoleHandler(ConsoleMode.java:43)
at org.jboss.as.domain.http.server.ManagementHttpServer.create(ManagementHttpServer.java:175)
... 6 more
{noformat}
It would be better to run in ConsoleMode.NO_CONSOLE if that module is not available.
(Possibly with a friendly user message.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (AS7-3128) Arquillian doesn't wait for the process to really end, causes problems like "port in use".
by Shelly McGowan (JIRA)
[ https://issues.jboss.org/browse/AS7-3128?page=com.atlassian.jira.plugin.s... ]
Shelly McGowan updated AS7-3128:
--------------------------------
Labels: arq_qe_blocker (was: )
> Arquillian doesn't wait for the process to really end, causes problems like "port in use".
> ------------------------------------------------------------------------------------------
>
> Key: AS7-3128
> URL: https://issues.jboss.org/browse/AS7-3128
> Project: Application Server 7
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 7.1.0.CR1
> Reporter: Ondrej Zizka
> Assignee: Aslak Knutsen
> Priority: Blocker
> Labels: arq_qe_blocker
>
> (05:54:09) dmlloyd: when running with JDWP enabled on the client or server, I occasionally get bind exceptions due to address in use
> (05:54:25) dmlloyd: which means that tests are running into each other without waiting for termination of the previous one
> (05:54:35) dmlloyd: which may also be causing other issues
> (05:56:04) ozizka: dmlloyd: Yes, lbarrerio observed similar problem too,
> (05:56:47) ozizka: And that's arq's issue too - there's no way to get around this currently AFAIK. Or is there?
> (05:57:05) ozizka: Perhaps "manually" wait in @AfterClass or such
> (05:57:07) dmlloyd: yeah, it can wait for the child process to terminate
> (05:57:07) ozizka: which is ugly
> (05:57:14) dmlloyd: I mean arq should
> (05:59:17) ozizka: dmlloyd: Do you have it somewhere on hudson?
> (05:59:24) ozizka: dmlloyd: It never happened to me actually
> (05:59:49) ozizka: Send me a log if you have one handy
> (06:01:35) dmlloyd: ozizka: no, try running with this command though:
> {code}
> mvn -DallTests install -Djpda -Dsurefire.jpda.args=-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n \
> -Dmaven.surefire.debug="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005"
> {code}
> (06:13:56) ozizka: dmlloyd: That's on linux?
> (06:14:03) dmlloyd: yes
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (AS7-3042) IPv6: Invalid redirect to Admin console (wrong IP address)
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/AS7-3042?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse updated AS7-3042:
----------------------------------
Fix Version/s: Open To Community
(was: 7.1.0.Final)
Assignee: (was: Darran Lofthouse)
I am postponing this issue for the moment.
The behaviour of the /console context on port 8080 is supposed to be a simple redirect so that out of the box users that connect to 8080 (Most likely out of habit as that is where previous AS management was performed) can be redirected to the admin console on it's dedicated port.
This re-direct however is not intended to be covering every network topology that can be imagined, once a server is moving beyond the initial set up these welcome pages should be switched off and administrators connect directly to the port hosting the admin console.
For this issue one address has been bound to an IPV6 format of the loopback address and the other address to the IPV4 equivalent - really once an administrator has reached this point they are beyond trying to work out where the admin console is accessible from - also we need to be very careful regarding the information returned from port 8080 as we should not be revealing information about the internal network over this connection as we can not actually verify the remote client has access - this is why the check is limited to verifying the same network interface is being used and relying on a best efforts redirect.
> IPv6: Invalid redirect to Admin console (wrong IP address)
> ----------------------------------------------------------
>
> Key: AS7-3042
> URL: https://issues.jboss.org/browse/AS7-3042
> Project: Application Server 7
> Issue Type: Bug
> Components: Console, Web
> Affects Versions: 7.1.0.Beta1b
> Reporter: Pavel Janousek
> Fix For: Open To Community
>
>
> This issue is some derivation from AS7-3040. Lets imagine starting server like this:
> {code}./standalone.sh -Djava.net.preferIPv4Stack=false -Djboss.bind.address=::1{code}
> So by default the admin/management is bound to _::ffff:127.0.0.1:9990_ and _::ffff:127.0.0.1:9999_, but it isn't accessible from Web WelcomePage at _::1:8080_ because the URL is specified as: {code}<a href="/console">{code} and so the next request is http://[::1]:8080/console which redirect requester to http://[::1]:9990, but there isn't any console because it is here - http://[::ffff:127.0.0.1]:9990.
> This is not good as it could lead to integration issues between components (X trying to connect to Y on ::1; Y listening on ::ffff:127.0.0.1).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months