[JBoss JIRA] (AS7-6819) MBD @ResourceAdapter deployment issue with JCA inbound listener
by Sudip Bhowmik (JIRA)
[ https://issues.jboss.org/browse/AS7-6819?page=com.atlassian.jira.plugin.s... ]
Sudip Bhowmik updated AS7-6819:
-------------------------------
Attachment: standalone-full.xml
> MBD @ResourceAdapter deployment issue with JCA inbound listener
> ---------------------------------------------------------------
>
> Key: AS7-6819
> URL: https://issues.jboss.org/browse/AS7-6819
> Project: Application Server 7
> Issue Type: Clarification
> Components: EJB, JCA
> Affects Versions: 7.1.3.Final (EAP)
> Environment: Windows with Jboss 7.1.3 EAP version.
> Reporter: Sudip Bhowmik
> Labels: jboss
> Fix For: 7.1.3.Final (EAP)
>
> Attachments: SourceCode_MDB_JCA.rar, standalone-full.xml
>
>
> The source set is attached here with.
> =================================================
> 13:04:10,050 INFO [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS015870: Deploy of deployment "DiameterEAR-1.0.ear" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.CREATE Missing[jboss.ra.\"DiameterRAInDeploy-1.0\"]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.VIEW.\"com.infyon.DiameterRAIn.DiameterMessageListener\".MESSAGE_ENDPOINT Missing[JBAS014861: <one or more t
> ransitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.ejb3.timerService Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".moduleDeploymentRuntimeInformation Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"Diame
> terMDB-1.0.jar\".component.MessageDrivenBean.TimedObjectInvoker Missing[JBAS014861: <one or more transitive dependencies>]"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (AS7-6819) MBD @ResourceAdapter deployment issue with JCA inbound listener
by Sudip Bhowmik (JIRA)
[ https://issues.jboss.org/browse/AS7-6819?page=com.atlassian.jira.plugin.s... ]
Sudip Bhowmik updated AS7-6819:
-------------------------------
Summary: MBD @ResourceAdapter deployment issue with JCA inbound listener (was: MBD deployment issue with JCA inbound lisenter (Plz help))
Fix Version/s: 7.1.3.Final (EAP)
Description:
The source set is attached here with.
=================================================
13:04:10,050 INFO [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS015870: Deploy of deployment "DiameterEAR-1.0.ear" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.CREATE Missing[jboss.ra.\"DiameterRAInDeploy-1.0\"]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.VIEW.\"com.infyon.DiameterRAIn.DiameterMessageListener\".MESSAGE_ENDPOINT Missing[JBAS014861: <one or more t
ransitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.ejb3.timerService Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".moduleDeploymentRuntimeInformation Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"Diame
terMDB-1.0.jar\".component.MessageDrivenBean.TimedObjectInvoker Missing[JBAS014861: <one or more transitive dependencies>]"
was:
13:04:10,050 INFO [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS015870: Deploy of deployment "DiameterEAR-1.0.ear" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.CREATE Missing[jboss.ra.\"DiameterRAInDeploy-1.0\"]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.VIEW.\"com.infyon.DiameterRAIn.DiameterMessageListener\".MESSAGE_ENDPOINT Missing[JBAS014861: <one or more t
ransitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.ejb3.timerService Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".moduleDeploymentRuntimeInformation Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"Diame
terMDB-1.0.jar\".component.MessageDrivenBean.TimedObjectInvoker Missing[JBAS014861: <one or more transitive dependencies>]"
> MBD @ResourceAdapter deployment issue with JCA inbound listener
> ---------------------------------------------------------------
>
> Key: AS7-6819
> URL: https://issues.jboss.org/browse/AS7-6819
> Project: Application Server 7
> Issue Type: Clarification
> Components: EJB, JCA
> Affects Versions: 7.1.3.Final (EAP)
> Environment: Windows with Jboss 7.1.3 EAP version.
> Reporter: Sudip Bhowmik
> Labels: jboss
> Fix For: 7.1.3.Final (EAP)
>
> Attachments: SourceCode_MDB_JCA.rar
>
>
> The source set is attached here with.
> =================================================
> 13:04:10,050 INFO [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS015870: Deploy of deployment "DiameterEAR-1.0.ear" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.CREATE Missing[jboss.ra.\"DiameterRAInDeploy-1.0\"]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.VIEW.\"com.infyon.DiameterRAIn.DiameterMessageListener\".MESSAGE_ENDPOINT Missing[JBAS014861: <one or more t
> ransitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.ejb3.timerService Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".moduleDeploymentRuntimeInformation Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"Diame
> terMDB-1.0.jar\".component.MessageDrivenBean.TimedObjectInvoker Missing[JBAS014861: <one or more transitive dependencies>]"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (AS7-6819) MBD deployment issue with JCA inbound lisenter (Plz help)
by Sudip Bhowmik (JIRA)
[ https://issues.jboss.org/browse/AS7-6819?page=com.atlassian.jira.plugin.s... ]
Sudip Bhowmik updated AS7-6819:
-------------------------------
Attachment: SourceCode_MDB_JCA.rar
The complete source set attached here with.
> MBD deployment issue with JCA inbound lisenter (Plz help)
> ---------------------------------------------------------
>
> Key: AS7-6819
> URL: https://issues.jboss.org/browse/AS7-6819
> Project: Application Server 7
> Issue Type: Clarification
> Components: EJB, JCA
> Affects Versions: 7.1.3.Final (EAP)
> Environment: Windows with Jboss 7.1.3 EAP version.
> Reporter: Sudip Bhowmik
> Labels: jboss
> Attachments: SourceCode_MDB_JCA.rar
>
>
> 13:04:10,050 INFO [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS015870: Deploy of deployment "DiameterEAR-1.0.ear" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.CREATE Missing[jboss.ra.\"DiameterRAInDeploy-1.0\"]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.VIEW.\"com.infyon.DiameterRAIn.DiameterMessageListener\".MESSAGE_ENDPOINT Missing[JBAS014861: <one or more t
> ransitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.ejb3.timerService Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".moduleDeploymentRuntimeInformation Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"Diame
> terMDB-1.0.jar\".component.MessageDrivenBean.TimedObjectInvoker Missing[JBAS014861: <one or more transitive dependencies>]"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (AS7-6819) MBD deployment issue with JCA inbound lisenter (Plz help)
by Sudip Bhowmik (JIRA)
[ https://issues.jboss.org/browse/AS7-6819?page=com.atlassian.jira.plugin.s... ]
Sudip Bhowmik updated AS7-6819:
-------------------------------
Summary: MBD deployment issue with JCA inbound lisenter (Plz help) (was: Missing[JBAS014861: <one or more transitive dependencies>])
Labels: jboss (was: )
Affects Version/s: 7.1.3.Final (EAP)
Environment: Windows with Jboss 7.1.3 EAP version.
Description:
13:04:10,050 INFO [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS015870: Deploy of deployment "DiameterEAR-1.0.ear" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.CREATE Missing[jboss.ra.\"DiameterRAInDeploy-1.0\"]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.VIEW.\"com.infyon.DiameterRAIn.DiameterMessageListener\".MESSAGE_ENDPOINT Missing[JBAS014861: <one or more t
ransitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.ejb3.timerService Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".moduleDeploymentRuntimeInformation Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"Diame
terMDB-1.0.jar\".component.MessageDrivenBean.TimedObjectInvoker Missing[JBAS014861: <one or more transitive dependencies>]"
Complexity: Medium
Component/s: EJB
JCA
PLease help me to resolve this issue. I am not able to deploy MDB having a binding over inbound resource adapter.
import com.infyon.DiameterRAIn.DiameterMessageListener;
import java.util.logging.Logger;
import javax.ejb.ActivationConfigProperty;
import javax.ejb.TransactionManagement;
import javax.ejb.TransactionAttribute;
import javax.ejb.TransactionManagementType;
import javax.ejb.TransactionAttributeType;
import javax.ejb.MessageDriven;
import javax.jms.JMSException;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.jms.TextMessage;
import org.jboss.ejb3.annotation.ResourceAdapter;
@MessageDriven(
name = "MessageDrivenBean",
messageListenerInterface=DiameterMessageListener.class,
activationConfig =
{
@ActivationConfigProperty(propertyName="ServerName",propertyValue="localhost"),
@ActivationConfigProperty(propertyName="PortNumber",propertyValue="40100"),
@ActivationConfigProperty(propertyName="UserName",propertyValue="user"),
@ActivationConfigProperty(propertyName="Password",propertyValue="pwd"),
@ActivationConfigProperty(propertyName="EventPatterns",propertyValue="myPattern")
}
)
@TransactionManagement(value= TransactionManagementType.CONTAINER)
@TransactionAttribute(value= TransactionAttributeType.REQUIRED)
@ResourceAdapter("DiameterRAInDeploy-1.0.rar")
public class ReceiveGxMDB implements DiameterMessageListener
{
/** The logger */
//....
}
> MBD deployment issue with JCA inbound lisenter (Plz help)
> ---------------------------------------------------------
>
> Key: AS7-6819
> URL: https://issues.jboss.org/browse/AS7-6819
> Project: Application Server 7
> Issue Type: Clarification
> Components: EJB, JCA
> Affects Versions: 7.1.3.Final (EAP)
> Environment: Windows with Jboss 7.1.3 EAP version.
> Reporter: Sudip Bhowmik
> Labels: jboss
>
> 13:04:10,050 INFO [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS015870: Deploy of deployment "DiameterEAR-1.0.ear" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.CREATE Missing[jboss.ra.\"DiameterRAInDeploy-1.0\"]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.VIEW.\"com.infyon.DiameterRAIn.DiameterMessageListener\".MESSAGE_ENDPOINT Missing[JBAS014861: <one or more t
> ransitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.ejb3.timerService Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".moduleDeploymentRuntimeInformation Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"Diame
> terMDB-1.0.jar\".component.MessageDrivenBean.TimedObjectInvoker Missing[JBAS014861: <one or more transitive dependencies>]"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (AS7-6815) Jboss7.1.1 EJB2 Entity Finder Return NULL attribute
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/AS7-6815?page=com.atlassian.jira.plugin.s... ]
Stuart Douglas commented on AS7-6815:
-------------------------------------
Is this reproducible on EAP 6.1.0.Alpha1?
> Jboss7.1.1 EJB2 Entity Finder Return NULL attribute
> ---------------------------------------------------
>
> Key: AS7-6815
> URL: https://issues.jboss.org/browse/AS7-6815
> Project: Application Server 7
> Issue Type: Task
> Components: Application Client
> Affects Versions: 7.1.1.Final
> Environment: Windows 7, JDK1.6 , Jboss7.1.1
> Reporter: yan chiou tua
> Assignee: Stuart Douglas
> Labels: EJB2, Entity, Finder, Jboss7.1.1, NULL, Return, attribute
>
> Hi,
> I am migrating EJB2 project to Jboss7.1.1 from Jboss4.2.2 and encounter below error. Thanks and appreciated if any help or quick feedback as this is an *urgent* project migration for me. Previuosly this EJB2 project is running no problem on Jboss4.2.2 and Jboss6 (i have try on Jboss6 before go to Jboss7) which I able to get the value from entity finder.
> I have attached errors message and my code snippet as below:-
> 15:06:19,139 ERROR [org.jboss.ejb3.invocation] (http-LOCALHOST-127.0.0.1-8088-1) JBAS014134: EJB Invocation failed on component UserLogging for method public abstract com.xxx.adminData.userLogin.model.UserLoggingModel *com.xxx.adminData.userLogin.ejb.UserLogging.getModel()*: javax.ejb.EJBTransactionRolledbackException
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleInCallerTx(CMTTxInterceptor.java:139) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:204) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:306) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:190) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories$2.processInvocation(EjbExceptionTransformingInterceptorFactories.java:89) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:32) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:173) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.entity.interceptors.EntityBeanPrimaryKeyInterceptor.processInvocation(EntityBeanPrimaryKeyInterceptor.java:52) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:72) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
> at com.xxx.adminData.userLogin.ejb.UserLogging$$$view320.getModel(Unknown Source) [eportal.jar:]
> at com.xxx.adminData.userLogin.controller.SessionControllerEJB.addUserLogging(SessionControllerEJB.java:71) [eportal.jar:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_03]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_03]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_03]
> at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_03]
> at org.jboss.as.ee.component.ManagedReferenceMethodInterceptorFactory$ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptorFactory.java:72) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:36) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:202) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:306) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:190) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories$2.processInvocation(EjbExceptionTransformingInterceptorFactories.java:89) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:32) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:173) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:72) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
> at com.xxx.adminData.userLogin.controller.SessionController$$$view324.addUserLogging(Unknown Source) [eportal.jar:]
> at com.xxx.adminData.userLogin.controller.UserLoginControllerEJB.login(UserLoginControllerEJB.java:158) [eportal.jar:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_03]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_03]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_03]
> at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_03]
> at org.jboss.as.ee.component.ManagedReferenceMethodInterceptorFactory$ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptorFactory.java:72) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:36) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:228) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:304) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:190) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories$2.processInvocation(EjbExceptionTransformingInterceptorFactories.java:89) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:32) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:173) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:72) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
> at com.xxx.adminData.userLogin.controller.UserLoginController$$$view341.login(Unknown Source) [eportal.jar:]
> at com.xxx.adminApp.web.login.LoginHelper.login(LoginHelper.java:157) [eportal.jar:]
> at org.apache.jsp.WEB_002dINF.jsp.common.loginAction_jsp._jspService(loginAction_jsp.java:80)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
> at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369)
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
> at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:840)
> at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:622)
> at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:560)
> at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:488)
> at org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:238) [org.springframework.web.servlet-3.0.5.RELEASE.jar:3.0.5.RELEASE]
> at org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:250) [org.springframework.web.servlet-3.0.5.RELEASE.jar:3.0.5.RELEASE]
> at org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1047) [org.springframework.web.servlet-3.0.5.RELEASE.jar:3.0.5.RELEASE]
> at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:817) [org.springframework.web.servlet-3.0.5.RELEASE.jar:3.0.5.RELEASE]
> at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:719) [org.springframework.web.servlet-3.0.5.RELEASE.jar:3.0.5.RELEASE]
> at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:644) [org.springframework.web.servlet-3.0.5.RELEASE.jar:3.0.5.RELEASE]
> at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:560) [org.springframework.web.servlet-3.0.5.RELEASE.jar:3.0.5.RELEASE]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
> at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:840)
> at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:622)
> at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:560)
> at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:488)
> at com.xxx.adminApp.web.URLRequestFilter.doFilter(URLRequestFilter.java:255) [eportal.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
> at com.xxx.adminApp.web.CompressionFilter.doFilter(CompressionFilter.java:248) [eportal.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
> at com.xxx.adminApp.web.XSSFilter.doFilter(XSSFilter.java:52) [eportal.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
> at org.jboss.modcluster.container.jbossweb.JBossWebContext$RequestListenerValve.event(JBossWebContext.java:67)
> at org.jboss.modcluster.container.jbossweb.JBossWebContext$RequestListenerValve.invoke(JBossWebContext.java:48)
> at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)
> at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_03]
> *Caused by: java.lang.NullPointerException*
> at org.jboss.as.ejb3.component.entity.entitycache.ReferenceCountingEntityCache$CacheEntry.access$000(ReferenceCountingEntityCache.java:146) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.ejb3.component.entity.entitycache.ReferenceCountingEntityCache.get(ReferenceCountingEntityCache.java:70) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.ejb3.component.entity.interceptors.EntityBeanAssociatingInterceptor.processInvocation(EntityBeanAssociatingInterceptor.java:61) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:202) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> ... 160 more
> +standalone-full-ha.xml on data source configuration part+
> <datasource jndi-name="java:/xxDS" pool-name="xxDS" enabled="true" use-java-context="true">
> ...
> </datasource>
> <driver name="sqlserver" module="com.microsoft.sqlserver">
> <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
> <xa-datasource-class>com.microsoft.sqlserver.jdbc.SQLServerXADataSource</xa-datasource-class>
> </driver>
> +ejb-jar.xml+
> <?xml version="1.0" encoding="UTF-8"?>
> <ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:ejb="http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd" version="3.1">
> <enterprise-beans>
> <session>
> <description>Session Controller</description>
> <ejb-name>SessionController</ejb-name>
> <local-home>com.xxx.adminData.userLogin.controller.SessionControllerHome</local-home>
> <local>com.xxx.adminData.userLogin.controller.SessionController</local>
> <ejb-class>com.xxx.adminData.userLogin.controller.SessionControllerEJB</ejb-class>
> <session-type>Stateless</session-type>
> <transaction-type>Container</transaction-type>
> <ejb-local-ref>
> <ejb-ref-name>adminData/ejb/UserLogging</ejb-ref-name>
> <ejb-ref-type>Entity</ejb-ref-type>
> <local-home>com.xxx.adminData.userLogin.ejb.UserLoggingHome</local-home>
> <local>com.xxx.adminData.userLogin.ejb.UserLogging</local>
> <ejb-link>UserLogging</ejb-link>
> </ejb-local-ref>
> </session>
> <entity>
> <description>User Logging</description>
> <ejb-name>UserLogging</ejb-name>
> <local-home>com.xxx.adminData.userLogin.ejb.UserLoggingHome</local-home>
> <local>com.xxx.adminData.userLogin.ejb.UserLogging</local>
> <ejb-class>com.xxx.adminData.userLogin.ejb.UserLoggingEJB</ejb-class>
> <persistence-type>Container</persistence-type>
> <prim-key-class>com.xxx.adminData.userLogin.ejb.UserLoggingPK</prim-key-class>
> <reentrant>true</reentrant>
> <cmp-version>2.x</cmp-version>
> <abstract-schema-name>USER_LOGGING</abstract-schema-name>
> <cmp-field>
> <field-name>loggingId</field-name>
> </cmp-field>
> <cmp-field>
> <field-name>userId</field-name>
> </cmp-field>
> <cmp-field>
> <field-name>organizationId</field-name>
> </cmp-field>
> <cmp-field>
> <field-name>loginTimeStamp</field-name>
> </cmp-field>
> <cmp-field>
> <field-name>logoutTimeStamp</field-name>
> </cmp-field>
> <cmp-field>
> <field-name>systemTypeId</field-name>
> </cmp-field>
> <cmp-field>
> <field-name>systemId</field-name>
> </cmp-field>
> <query>
> <query-method>
> <method-name>findCurrentUserLogin</method-name>
> <method-params>
> <method-param>java.lang.String</method-param>
> </method-params>
> </query-method>
> <ejb-ql>select OBJECT(e) from USER_LOGGING e where e.userId = ?1 and e.logoutTimeStamp = e.loginTimeStamp</ejb-ql>
> </query>
> </entity>
> </enterprise-beans>
> </ejb-jar>
> +jbosscmp-jdbc.xml+
> <?xml version="1.0" encoding="UTF-8"?>
> <jbosscmp-jdbc>
> <defaults>
> <datasource>java:/xxDS</datasource>
> </defaults>
> <enterprise-beans>
> <entity>
> <ejb-name>UserLogging</ejb-name>
> <table-name>USER_LOGGING</table-name>
> <create-table>false</create-table>
> <remove-table>false</remove-table>
> <cmp-field>
> <field-name>loggingId</field-name>
> <column-name>loggingId</column-name>
> <jdbc-type>VARCHAR</jdbc-type>
> <sql-type>VARCHAR(35)</sql-type>
> </cmp-field>
> <cmp-field>
> <field-name>userId</field-name>
> <column-name>userId</column-name>
> <jdbc-type>VARCHAR</jdbc-type>
> <sql-type>VARCHAR(20)</sql-type>
> </cmp-field>
> <cmp-field>
> <field-name>organizationId</field-name>
> <column-name>organizationId</column-name>
> <jdbc-type>VARCHAR</jdbc-type>
> <sql-type>VARCHAR(26)</sql-type>
> </cmp-field>
> <cmp-field>
> <field-name>loginTimeStamp</field-name>
> <column-name>loginTimeStamp</column-name>
> </cmp-field>
> <cmp-field>
> <field-name>logoutTimeStamp</field-name>
> <column-name>logoutTimeStamp</column-name>
> </cmp-field>
> <cmp-field>
> <field-name>systemTypeId</field-name>
> <column-name>systemTypeId</column-name>
> </cmp-field>
> <cmp-field>
> <field-name>systemId</field-name>
> <column-name>systemId</column-name>
> </cmp-field>
> </entity>
> </enterprise-beans>
> </jbosscmp-jdbc>
> +SessionControllerEJB.java+
> public String addUserLogging(UserLoginModel model){
> InitialContext initial = new InitialContext();
> UserLoggingHome userLoggingHome = (UserLoggingHome) PortableRemoteObject.narrow(initial.lookup("java:app/xxx/UserLogging!com.xxx.adminData.userLogin.ejb.UserLoggingHome"),
> UserLoggingHome.class);
> UserLogging userlogging = *userLoggingHome.findCurrentUserLogin(model.getUserId())*;
> }
> +UserLogging.java+
> public interface UserLogging extends EJBLocalObject {
> public UserLoggingModel getModel();
> public String getLoggingId();
> public void setLoggingId(String loggingId);
> ...
> }
> +UserLoggingHome.java+
> public interface UserLoggingHome extends EJBLocalHome {
> public UserLogging findCurrentUserLogin(String user) throws FinderException;
> ...
> }
> +UserLoggingEJB.java+
> public abstract class UserLoggingEJB implements EntityBean {
> private EntityContext ctx;
> public String loggingId;
> public String userId;
> public String organizationId;
> public Timestamp loginTimeStamp;
> public Timestamp logoutTimeStamp;
> public long systemTypeId;
> public long systemId;
> public abstract String getLoggingId();
> public abstract void setLoggingId(String loggingId);
> public UserLoggingModel getModel() {
> UserLoggingModel userLoggingModel = new UserLoggingModel(getLoggingId(), getUserId(), getOrganizationId(), getLoginTimeStamp(),
> getLogoutTimeStamp());
> return userLoggingModel;
> }
> ...
> }
> Thanks in advanced!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (AS7-6818) Allow socket-binding-group-refType to override default-interface
by Todd Trimmer (JIRA)
[ https://issues.jboss.org/browse/AS7-6818?page=com.atlassian.jira.plugin.s... ]
Todd Trimmer updated AS7-6818:
------------------------------
Description:
I want all the host controllers in my domain to use the same socket-binding-group. However, each host controller can have multiple servers, each with its own IP, but each IP still reuses the same port number (yet still a unique IP+port combo). The problem is that the socket-binding-group-refType will not let me override the @default-interface value from the referent socket-binding-group. I am forced to create a second, equally verbose, socket-binding-group exactly like the first group in every way, except for the @default-interface. I wish to avoid this. My particular scenario cannot rely on @port-offset because my hardware load-balancer needs all nodes in the same pool to use the same ports.
Under my proposal, the host.xml could thus more easily be written like this:
...
<interfaces>
<interface name="public">
<inet-address value="10.10.10.1" />
</interface>
<interface name="public-two">
<inet-address value="10.10.10.2" />
</interface>
</interfaces>
...
<servers>
<server name="server-one" group="prod-server-group" auto-start="true">
<jvm name="jvm6g" />
</server>
<server name="server-two" group="prod-server-group" auto-start="false">
<jvm name="jvm2g" />
<socket-binding-group ref="standard-sockets" default-interface="public-two" />
</server>
</servers>
...
This alleviates the burden of having to define a second socket-binding-group in domain.xml and maintaining the same set of socket-binding definitions in two places.
was:
I want all the host controllers in my domain to use the same socket-binding-group. However, each host controller can have multiple servers, each with its own IP, but each IP still reuses the same port number (yet still a unique IP+port combo). The problem is that the socket-binding-group-refType will not let me override the @default-interface value from the referent socket-binding-group. I am forced to create a second, equally verbose, socket-binding-group exactly like the first group in every way, except for the @default-interface. I wish to avoid this. My particular scenario cannot rely on @port-offset because my hardware load-balancer needs all nodes in the same pool to use the same ports.
This could be easily solved if the socket-binding-group-refType could have a @default-interface attribute to override the socket-binding-group[@default-interface] it references.
The host.xml could thus look like this:
...
<interfaces>
<interface name="public">
<inet-address value="10.10.10.1" />
</interface>
<interface name="public-two">
<inet-address value="10.10.10.2" />
</interface>
</interfaces>
...
<servers>
<server name="server-one" group="prod-server-group" auto-start="true">
<jvm name="jvm6g" />
</server>
<server name="server-two" group="@prod-server-group" auto-start="false">
<jvm name="jvm2g" />
<socket-binding-group ref="standard-sockets" default-interface="public-two" />
</server>
</servers>
...
This alleviates the burden of having to define a second socket-binding-group in domain.xml and maintaining the same set of socket-binding definitions in two places.
> Allow socket-binding-group-refType to override default-interface
> ----------------------------------------------------------------
>
> Key: AS7-6818
> URL: https://issues.jboss.org/browse/AS7-6818
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Domain Management
> Affects Versions: 7.1.1.Final
> Reporter: Todd Trimmer
> Assignee: Brian Stansberry
> Priority: Optional
> Labels: configuration, domain, host-controller
>
> I want all the host controllers in my domain to use the same socket-binding-group. However, each host controller can have multiple servers, each with its own IP, but each IP still reuses the same port number (yet still a unique IP+port combo). The problem is that the socket-binding-group-refType will not let me override the @default-interface value from the referent socket-binding-group. I am forced to create a second, equally verbose, socket-binding-group exactly like the first group in every way, except for the @default-interface. I wish to avoid this. My particular scenario cannot rely on @port-offset because my hardware load-balancer needs all nodes in the same pool to use the same ports.
> Under my proposal, the host.xml could thus more easily be written like this:
> ...
> <interfaces>
> <interface name="public">
> <inet-address value="10.10.10.1" />
> </interface>
> <interface name="public-two">
> <inet-address value="10.10.10.2" />
> </interface>
> </interfaces>
> ...
> <servers>
> <server name="server-one" group="prod-server-group" auto-start="true">
> <jvm name="jvm6g" />
> </server>
> <server name="server-two" group="prod-server-group" auto-start="false">
> <jvm name="jvm2g" />
> <socket-binding-group ref="standard-sockets" default-interface="public-two" />
> </server>
> </servers>
> ...
> This alleviates the burden of having to define a second socket-binding-group in domain.xml and maintaining the same set of socket-binding definitions in two places.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (AS7-6818) Allow socket-binding-group-refType to override default-interface
by Todd Trimmer (JIRA)
Todd Trimmer created AS7-6818:
---------------------------------
Summary: Allow socket-binding-group-refType to override default-interface
Key: AS7-6818
URL: https://issues.jboss.org/browse/AS7-6818
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.1.Final
Reporter: Todd Trimmer
Assignee: Brian Stansberry
Priority: Optional
I want all the host controllers in my domain to use the same socket-binding-group. However, each host controller can have multiple servers, each with its own IP, but each IP still reuses the same port number (yet still a unique IP+port combo). The problem is that the socket-binding-group-refType will not let me override the @default-interface value from the referent socket-binding-group. I am forced to create a second, equally verbose, socket-binding-group exactly like the first group in every way, except for the @default-interface. I wish to avoid this. My particular scenario cannot rely on @port-offset because my hardware load-balancer needs all nodes in the same pool to use the same ports.
This could be easily solved if the socket-binding-group-refType could have a @default-interface attribute to override the socket-binding-group[@default-interface] it references.
The host.xml could thus look like this:
...
<interfaces>
<interface name="public">
<inet-address value="10.10.10.1" />
</interface>
<interface name="public-two">
<inet-address value="10.10.10.2" />
</interface>
</interfaces>
...
<servers>
<server name="server-one" group="prod-server-group" auto-start="true">
<jvm name="jvm6g" />
</server>
<server name="server-two" group="@prod-server-group" auto-start="false">
<jvm name="jvm2g" />
<socket-binding-group ref="standard-sockets" default-interface="public-two" />
</server>
</servers>
...
This alleviates the burden of having to define a second socket-binding-group in domain.xml and maintaining the same set of socket-binding definitions in two places.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (AS7-6761) Deployment replace causes invalid state in DUP
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6761?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-6761:
----------------------------------------------
Stuart Douglas <sdouglas(a)redhat.com> made a comment on [bug 924562|https://bugzilla.redhat.com/show_bug.cgi?id=924562]
This is resolved for non-OSGi deployments. I think we should resolve this issue and create a new one for the OSGi problems, as the OSGi issue is not so much caused by dependency changes but rather by explicit start/stop operations on the bundle.
> Deployment replace causes invalid state in DUP
> ----------------------------------------------
>
> Key: AS7-6761
> URL: https://issues.jboss.org/browse/AS7-6761
> Project: Application Server 7
> Issue Type: Bug
> Components: Server
> Reporter: Thomas Diesler
> Assignee: Stuart Douglas
> Attachments: v200.jar, v201.jar, webapp-v200.war
>
>
> Webapp A depends on deployment B. Replacing B causes NPE in JPAInterceptorProcessor
> {code}
> 12:52:05,712 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "v200.jar" (runtime-name: "v200.jar")
> 12:52:05,889 INFO [org.jboss.as.server] (XNIO-1 task-8) JBAS018559: Deployed "v200.jar" (runtime-name : "v200.jar")
> 12:52:37,207 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "webapp-v200.war" (runtime-name: "webapp-v200.war")
> 12:52:37,349 INFO [org.jboss.web] (ServerService Thread Pool -- 52) JBAS018210: Register web context: /webapp-v200
> 12:52:37,436 INFO [org.jboss.as.server] (XNIO-1 task-3) JBAS018559: Deployed "webapp-v200.war" (runtime-name : "webapp-v200.war")
> 12:53:20,252 INFO [org.jboss.web] (ServerService Thread Pool -- 57) JBAS018224: Unregister web context: /webapp-v200
> 12:53:20,272 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment v200.jar (runtime-name: v200.jar) in 25ms
> 12:53:20,274 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "v200.jar" (runtime-name: "v200.jar")
> 12:53:20,293 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."webapp-v200.war".FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit."webapp-v200.war".FIRST_MODULE_USE: JBAS018733: Failed to process phase FIRST_MODULE_USE of deployment "webapp-v200.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1972) [jboss-msc-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1905) [jboss-msc-1.1.1.Final.jar:1.1.1.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
> Caused by: java.lang.NullPointerException
> at org.jboss.as.jpa.processor.JPAInterceptorProcessor.deploy(JPAInterceptorProcessor.java:52)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> ... 5 more
> {code}
> What might be happening here is that replacing B causes ModuleB to go down. Phase FIRST_MODULE_USE of A depends on ModuleB, which causes a call to undeploy() on the DUPs for A. When ModuleB becomes available again, deploy() is called on the DUPs for A again. Possibly because of the cleanup phase, necessary state is lost and we see a NPE.
> AFAICS, this is a variation of the feature request that DUPs support multiple calls to deploy/undeploy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month