[JBoss JIRA] (WFLY-3417) Accessing the EJB 3 container configuration of the web console fails
by Philippe Schaller (JIRA)
Philippe Schaller created WFLY-3417:
---------------------------------------
Summary: Accessing the EJB 3 container configuration of the web console fails
Key: WFLY-3417
URL: https://issues.jboss.org/browse/WFLY-3417
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Console
Affects Versions: 8.1.0.CR2
Environment: HAL 2.2.6.Final & 2.2.7.Final
WildFly 8.1.0.CR2 & 8.1.0.CR5
JDK 1.7.0_55
Win 7
Reporter: Philippe Schaller
Assignee: Heiko Braun
Accessing the EJB 3 container configuration of the web console returns this message:
Unknown error
Unexpected HTTP response: 500
Request
{
"address" => [("subsystem" => "threads")],
"child-type" => "thread-factory",
"operation" => "read-children-resources",
"recursive" => true
}
Response
Internal Server Error
{
"outcome" => "failed",
"failure-description" => "JBAS014883: No resource definition is registered for address [(\"subsystem\" => \"threads\")]",
"rolled-back" => true
}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBLOGGING-104) MDC Logging not appearing in server.log
by ArunPrasath Rajmohan (JIRA)
ArunPrasath Rajmohan created JBLOGGING-104:
----------------------------------------------
Summary: MDC Logging not appearing in server.log
Key: JBLOGGING-104
URL: https://issues.jboss.org/browse/JBLOGGING-104
Project: JBoss Logging
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: jboss-logging-logmanager, jboss-logging-spi
Affects Versions: 3.1.4.GA
Environment: Local
Reporter: ArunPrasath Rajmohan
Assignee: James Perkins
Hi
I am trying to log using org.jboss.logging.MDC but the log entry is not found in server.log
Steps followed:
1.Maven Dependency Used:
<dependency>
<groupId>org.jboss.logging</groupId>
<artifactId>jboss-logging</artifactId>
<version>3.1.4.GA</version>
</dependency>
2.Athe below code in the controller
org.jboss.logging.MDC.put("MDC Worked", new String("MDC Worked"));
3.Placed the jboss-logging.xml inside META-INF folder of the web application.
The content of jboss-logging.xml is as follows:
<periodic-rotating-file-handler
file-name="${jboss.server.log.dir}/server.log"
name="FILE"
autoflush="true"
append="true"
suffix=".yyyy-MM-dd">
<error-manager>
<only-once/>
</error-manager>
<formatter>
<pattern-formatter pattern="%d %-5p [%c] (%t) [%X{entry1}, %X{entry2}] %s%E%n"/>
</formatter>
</periodic-rotating-file-handler>
Problem:
There are no errors but the log entry is not found in the server.log
Regards
Arun
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (WFLY-978) CachedConnectionManager interceptor isn't applied consistently on EJB invocations
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-978?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration updated WFLY-978:
-----------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=955506, https://bugzilla.redhat.com/show_bug.cgi?id=955508, https://bugzilla.redhat.com/show_bug.cgi?id=1102469 (was: https://bugzilla.redhat.com/show_bug.cgi?id=955506, https://bugzilla.redhat.com/show_bug.cgi?id=955508)
> CachedConnectionManager interceptor isn't applied consistently on EJB invocations
> ---------------------------------------------------------------------------------
>
> Key: WFLY-978
> URL: https://issues.jboss.org/browse/WFLY-978
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: EJB
> Reporter: jaikiran pai
> Assignee: jaikiran pai
> Fix For: 8.0.0.Alpha1
>
>
> The CachedConnectionManager isn't being applied consistently on EJB invocations and the following scenario leads to a WARN from the JCA CachedConnectionManager:
> CMT MDB -> does a DB operation using a DataSource and then -> invokes a BMT SLSB -> which then does a UserTransaction.begin()
> This leads to:
> {code}
> 21:13:44,385 WARN [org.jboss.tm.usertx.UserTransactionRegistry] (Thread-1 (HornetQ-client-global-threads-9337120)) Error notifying listener org.jboss.jca.core.tx.jbossts.UserTransactionListenerImpl@2667db of userTransactionStarted: java.lang.IllegalStateException: Trying to change transaction TransactionImple < ac, BasicAction: 0:ffff7f000101:-6c404b63:51755a8b:14 status: ActionStatus.RUNNING > in enlist!
> at org.jboss.jca.core.connectionmanager.listener.TxConnectionListener.enlist(TxConnectionListener.java:219)
> at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.transactionStarted(TxConnectionManagerImpl.java:383)
> at org.jboss.jca.core.connectionmanager.ccm.CachedConnectionManagerImpl.userTransactionStarted(CachedConnectionManagerImpl.java:211)
> at org.jboss.jca.core.tx.jbossts.UserTransactionListenerImpl.userTransactionStarted(UserTransactionListenerImpl.java:52)
> at org.jboss.tm.usertx.UserTransactionRegistry.userTransactionStarted(UserTransactionRegistry.java:119)
> at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.begin(ServerVMClientUserTransaction.java:146)
> at org.jboss.as.test.integration.ejb.mdb.BMTSLSB.doSomethingWithUserTransaction(BMTSLSB.java:30) [mdb.jar:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_15]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_15]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_15]
> at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_15]
> at org.jboss.as.ee.component.ManagedReferenceMethodInterceptorFactory$ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptorFactory.java:72) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ejb3.tx.EjbBMTInterceptor.handleInvocation(EjbBMTInterceptor.java:104) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.tx.BMTInterceptor.processInvocation(BMTInterceptor.java:56) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:79) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:55) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:305) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_15]
> at org.jboss.invocation.PrivilegedInterceptor.processInvocation(PrivilegedInterceptor.java:65) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:72) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.test.integration.ejb.mdb.BMTSLSB$$$view3.doSomethingWithUserTransaction(Unknown Source) [mdb.jar:]
> at org.jboss.as.test.integration.ejb.mdb.DDBasedMDB.onMessage(DDBasedMDB.java:74) [mdb.jar:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_15]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_15]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_15]
> at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_15]
> at org.jboss.as.ee.component.ManagedReferenceMethodInterceptorFactory$ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptorFactory.java:72) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:227) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:318) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:215) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:79) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:65) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentDescription$5$1.processInvocation(MessageDrivenComponentDescription.java:204) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:55) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:305) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_15]
> at org.jboss.invocation.PrivilegedInterceptor.processInvocation(PrivilegedInterceptor.java:65) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:72) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.test.integration.ejb.mdb.DDBasedMDB$$$view2.onMessage(Unknown Source) [mdb.jar:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_15]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_15]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_15]
> at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_15]
> at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.doInvoke(MessageEndpointInvocationHandler.java:155) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:73) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.test.integration.ejb.mdb.DDBasedMDB$$$endpoint1.onMessage(Unknown Source) [mdb.jar:]
> at org.hornetq.ra.inflow.HornetQMessageHandler.onMessage(HornetQMessageHandler.java:313)
> at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1084)
> at org.hornetq.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:56)
> at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1229)
> at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_15]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_15]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_15]
> {code}
> Stuart looked into this issue and realized that the CachedConnectionManager interceptor wasn't being applied consistently on the EJB invocations.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (WFLY-3416) NPE in Undertow Extension if login module doesn't set Principal
by Josef Cacek (JIRA)
Josef Cacek created WFLY-3416:
---------------------------------
Summary: NPE in Undertow Extension if login module doesn't set Principal
Key: WFLY-3416
URL: https://issues.jboss.org/browse/WFLY-3416
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web (Undertow)
Affects Versions: 8.1.0.CR2
Reporter: Josef Cacek
Assignee: Stuart Douglas
NPE is thrown during authentication if a LoginModule doesn't set any principal to the Subject.
The problem comes from {{org.wildfly.extension.undertow.security.AccountImpl}} constructor call {{principal.getName()}}.
{code}
Caused by: java.lang.NullPointerException
at org.wildfly.extension.undertow.security.AccountImpl.<init>(AccountImpl.java:61)
at org.wildfly.extension.undertow.security.JAASIdentityManagerImpl.verifyCredential(JAASIdentityManagerImpl.java:123)
...
{code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (WFLY-3415) REST provider does not handler : in the URI properly
by Maciej Swiderski (JIRA)
[ https://issues.jboss.org/browse/WFLY-3415?page=com.atlassian.jira.plugin.... ]
Maciej Swiderski updated WFLY-3415:
-----------------------------------
Attachment: WFLY-3415-stactrace.txt
complete stack trace
> REST provider does not handler : in the URI properly
> ----------------------------------------------------
>
> Key: WFLY-3415
> URL: https://issues.jboss.org/browse/WFLY-3415
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: REST
> Affects Versions: 8.0.0.Final, 8.1.0.CR1, 8.1.0.CR2
> Reporter: Maciej Swiderski
> Assignee: Stuart Douglas
> Attachments: WFLY-3415-stactrace.txt
>
>
> REST provider does not handler : in the URI properly and fails with [org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher] (default task-1) Failed to parse request.: java.lang.IllegalArgumentException: Illegal uri template: runtime/org.jbpm:HR:1.0/process/hiring/start
> complete stack trace attached. in jbpm we use GAV (of maven deployable artifact) as an identifier of a resource and while trying to move up to Wildfly (from EAP 6.1) we encountered this issue which looks like a limitation compared to previous version. Is this done by design or is more like a bug?
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (WFLY-3415) REST provider does not handler : in the URI properly
by Maciej Swiderski (JIRA)
Maciej Swiderski created WFLY-3415:
--------------------------------------
Summary: REST provider does not handler : in the URI properly
Key: WFLY-3415
URL: https://issues.jboss.org/browse/WFLY-3415
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: REST
Affects Versions: 8.1.0.CR2, 8.1.0.CR1, 8.0.0.Final
Reporter: Maciej Swiderski
Assignee: Stuart Douglas
REST provider does not handler : in the URI properly and fails with [org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher] (default task-1) Failed to parse request.: java.lang.IllegalArgumentException: Illegal uri template: runtime/org.jbpm:HR:1.0/process/hiring/start
complete stack trace attached. in jbpm we use GAV (of maven deployable artifact) as an identifier of a resource and while trying to move up to Wildfly (from EAP 6.1) we encountered this issue which looks like a limitation compared to previous version. Is this done by design or is more like a bug?
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JGRP-1845) Null pointer exception in Samsung Q1 using 3G connection
by Denis Lamela (JIRA)
[ https://issues.jboss.org/browse/JGRP-1845?page=com.atlassian.jira.plugin.... ]
Denis Lamela commented on JGRP-1845:
------------------------------------
Hello Bela Ban, I saw your solution in the source code. Thank you.
The problem occurs in JDK 6 and 7. The stack trace is:
java.lang.NullPointerException
at java.net.NetworkInterface.getInterfaceAddresses(Unknown Source)
at org.jgroups.stack.DiagnosticsHandler.bindToInterfaces(DiagnosticsHandler.java:211)
at org.jgroups.stack.DiagnosticsHandler.start(DiagnosticsHandler.java:87)
at org.jgroups.protocols.TP.start(TP.java:1210)
at org.jgroups.protocols.TCP.start(TCP.java:82)
at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:952)
at org.jgroups.JChannel.startStack(JChannel.java:864)
at org.jgroups.JChannel._preConnect(JChannel.java:527)
at org.jgroups.JChannel.connect(JChannel.java:284)
at org.jgroups.JChannel.connect(JChannel.java:275)
> Null pointer exception in Samsung Q1 using 3G connection
> --------------------------------------------------------
>
> Key: JGRP-1845
> URL: https://issues.jboss.org/browse/JGRP-1845
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.1, 3.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.5, 3.2.6, 3.2.7, 3.2.8, 3.2.9, 3.2.10, 3.2.12, 3.2.13, 3.3, 3.3.1, 3.3.2, 3.3.3, 3.3.4, 3.3.5, 3.4, 3.4.1, 3.4.2, 3.4.3, 3.4.4
> Environment: Samsung Q1 with Windows XP Tablet Edition and 3G connection. Java 6 or Java 7.
> Reporter: Denis Lamela
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.3.6, 3.4.5, 3.5
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> Null pointer exception in method "bindToInterfaces" of class "org.jgroups.stack.DiagnosticsHandler". The exception is thrown while executing "i.getInterfaceAddresses().isEmpty()". "i.getInterfaceAddresses()" returns null.
> This bug can be fixed checking if "i.getInterfaceAddresses()" returns null.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBEE-155) Javadoc for WebSocketContainer.connectToServer mentions ServerEndpoint instead of ClientEndpoint
by Ron Šmeral (JIRA)
[ https://issues.jboss.org/browse/JBEE-155?page=com.atlassian.jira.plugin.s... ]
Ron Šmeral commented on JBEE-155:
---------------------------------
Filed upstream: https://java.net/jira/browse/WEBSOCKET_SDK-6, since the org.jboss.spec.javax.websocket API seems to be copied from there.
> Javadoc for WebSocketContainer.connectToServer mentions ServerEndpoint instead of ClientEndpoint
> ------------------------------------------------------------------------------------------------
>
> Key: JBEE-155
> URL: https://issues.jboss.org/browse/JBEE-155
> Project: JBoss JavaEE Spec APIs
> Issue Type: Bug
> Components: jboss-websocket-api
> Affects Versions: JavaEE 7 Spec APIs 1.0.0.Final
> Reporter: Ron Šmeral
> Assignee: Shelly McGowan
>
> In {{javax.websocket.WebSocketContainer}}, the javadoc for two connectToServer method signatures contains an incorrect statement:
> {{connectToServer(Object annotatedEndpointInstance, URI path)}}
> {{connectToServer(Class<?> annotatedEndpointClass, URI path)}}
> {quote}
> The supplied object must be a class decorated with the class level \{@link javax.websocket.server.*ServerEndpoint*\} annotation.
> {quote}
> which should point to {{javax.websocket.ClientEndpoint}} instead of the ServerEndpoint.
> Also, in case of {{connectToServer(Object annotatedEndpointInstance, URI path)}}, that sentence should read _...supplied object must be *an instance of* a class..._
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months