-C in jboss

HI guys,.

I use the jboss application server for my atg application

I use the following command to run the application

CD C:\jboss-eap-5.1\jboss-as\bin

run b 172.45.54.47 c default - Datg.dynamo.server.name = default | ATGLogColorizer_v1_2

What is - c means?

The argument - c is a JBoss server named. Normally when you run ATG on JBoss JBoss you create more of a name server, for example ATGProduction.

The following command starts the server ATGProduction.

Run.bat - c ATGProduction

You can see the servers defined in the directory INSTALL-Server JBOSS-here, you'll notice a default value for the directory, it is simply a server named default.

Tags: Oracle Applications

Similar Questions

JBOSS/Java

In my Foglight setup I have 8 FMS, air-conditioned and equipped with specific roles. Each of these FMS to receive data from the servers of Foglight Application running the management agent. I installed the remote host, followed through these application servers, but now I'm a bit stuck regarding remote Java/JBoss monitoring.

I think that I have installed the correct cartridge FMS, but I still need help with installation.

It's new for me and I'm much teach myself at work

Excuse me now as there may be many more questions to come...

Thanks for the info.

If you want to try to install them some agents you can install an agent manager and follow the installation process

http://en.community.Dell.com/TechCenter/performance-monitoring/Foglight-administrators/m/Admin-videos/20438467

If you want to paste (JMX) monitoring lets wait for the version 5.9.3 cartridge Java which is due soon and the upgrade.

Golan

The atg in Jboss 6.1 Oracle application deployment

Hi all
I'm up a csc application using the Oracle 11.1 ATG platform and try to deploy it using Jboss 6.1.
But I do not see any folder inside Jboss 6.1 server. Can someone help me with the steps to deploy a Jboss 6.1?
Thank you
Prasanna

Follow these steps to create the server instance and deploy ear on jboss.

https://access.redhat.com/documentation/en-us/JBoss_Operations_Network/3.1/HTML/How_to_Manage_JBoss_Servers/eap6-config.html

Peace

Shaik

JBoss EAP - 6.1 the full deployment of JIU of CRS application error

I'm trying the application installation via CIM tools CRS. ATGPublishing, ATGProduction servers are in place and get below error while doing full deployment.
Details of the application: Oracle 11g, ATG 11.0 XE, Jboss EAP - 6.1
15:33:19, 869 WARN [com.arjuna.ats.jta] (RepositoryWorkerThread-1(Pre-Deployment)) ARJUNA016061: TransactionImple.enlistResource - XAResource.start returned: XAException.XAER_PROTO for < formatId = 131077 gtrid_length = 29, bqual_length = 36, tx_uid = 0:ffff7f000001:88fb79e:536df08b:d0ee, node_name = 1, branch_uid = 0:ffff7f000001:88fb7
at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1110) [ojdbc6.jar:11.2.0.2.0]
at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:240) [ojdbc6.jar:11.2.0.2.0]
at org.jboss.jca.adapters.jdbc.xa.XAManagedConnection.start(XAManagedConnection.java:259)
at org.jboss.jca.core.tx.jbossts.XAResourceWrapperImpl.start(XAResourceWrapperImpl.java:191)
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:636)
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:397)
to org.jboss.jca.core.connectionmanager.listener.TxConnectionListener$ TransactionSynchronization.enlist (TxConnectionListener.java:607)
at org.jboss.jca.core.connectionmanager.listener.TxConnectionListener.enlist(TxConnectionListener.java:265)
at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.managedConnectionReconnected(TxConnectionManagerImpl.java:467)
at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.reconnectManagedConnection(AbstractConnectionManager.java:599)
at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:467)
at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:139)
at atg.service.jdbc.SwitchingDataSource.getConnection(SwitchingDataSource.java:931) [_DAS_slib_sclasses.jar:]
at atg.adapter.gsa.GSATransaction.getConnection(GSATransaction.java:794) [_DAS_slib_sclasses.jar:]
at atg.adapter.gsa.GSAItemDescriptor.getConnection(GSAItemDescriptor.java:2745) [_DAS_slib_sclasses.jar:]
at atg.adapter.gsa.GSAItemDescriptor.addItem(GSAItemDescriptor.java:7310) [_DAS_slib_sclasses.jar:]
at atg.adapter.gsa.GSARepository.addItem(GSARepository.java:1054) [_DAS_slib_sclasses.jar:]
at atg.deployment.repository.ReferenceItemGenerator.createDummyItem(ReferenceItemGenerator.java:579) [_DAS_slib_sclasses.jar:]
at atg.deployment.repository.ReferenceItemGenerator.findDummyReferenceItem(ReferenceItemGenerator.java:657) [_DAS_slib_sclasses.jar:]
at atg.deployment.repository.ReferenceItemGenerator.generateDummyItems(ReferenceItemGenerator.java:314) [_DAS_slib_sclasses.jar:]
at atg.deployment.repository.RepositoryWorkerThread.preDeploymentPhase(RepositoryWorkerThread.java:569) [_DAS_slib_sclasses.jar:]
at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:338) [_DAS_slib_sclasses.jar:]
15:33:20, 274 ERROR [stderr] (RepositoryWorkerThread-1(Pre-Deployment)) oracle.jdbc.xa.OracleXAException
15:33:20, 275 ERROR [stderr] (RepositoryWorkerThread-1(Pre-Deployment)) to oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1110)
15:33:20, 275 ERROR [stderr] (RepositoryWorkerThread-1(Pre-Deployment)) to oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:240)
15:33:20, 275 ERROR [stderr] (RepositoryWorkerThread-1(Pre-Deployment)) to org.jboss.jca.adapters.jdbc.xa.XAManagedConnection.start(XAManagedConnection.java:259)
15:33:20, 276 ERROR [stderr] (RepositoryWorkerThread-1(Pre-Deployment)) to org.jboss.jca.core.tx.jbossts.XAResourceWrapperImpl.start(XAResourceWrapperImpl.java:191)
15:33:20, 276 ERROR [stderr] (RepositoryWorkerThread-1(Pre-Deployment)) to com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:636)
15:33:20, 276 ERROR [stderr] (RepositoryWorkerThread-1(Pre-Deployment)) to com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:397)
15:33:20, 277 ERROR [stderr] (RepositoryWorkerThread-1(Pre-Deployment)) to org.jboss.jca.core.connectionmanager.listener.TxConnectionListener$ TransactionSynchronization.enlist (TxConnectionListener.java:607)
15:33:20, 277 ERROR [stderr] (RepositoryWorkerThread-1(Pre-Deployment)) to org.jboss.jca.core.connectionmanager.listener.TxConnectionListener.enlist(TxConnectionListener.java:265)
15:33:20, 277 ERROR [stderr] (RepositoryWorkerThread-1(Pre-Deployment)) to org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.managedConnectionReconnected(TxConnectionManagerImpl.java:467)
15:33:20, 277 ERROR [stderr] (RepositoryWorkerThread-1(Pre-Deployment)) to org.jboss.jca.core.connectionmanager.AbstractConnectionManager.reconnectManagedConnection(AbstractConnectionManager.java:599)
15:33:20, 278 ERROR [stderr] (RepositoryWorkerThread-1(Pre-Deployment)) to org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:467)
15:33:20, 278 ERROR [stderr] (RepositoryWorkerThread-1(Pre-Deployment)) to org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:139)
15:33:20, 278 ERROR [stderr] (RepositoryWorkerThread-1(Pre-Deployment)) to atg.service.jdbc.SwitchingDataSource.getConnection(SwitchingDataSource.java:931)
15:33:20, 278 ERROR [stderr] (RepositoryWorkerThread-1(Pre-Deployment)) to atg.adapter.gsa.GSATransaction.getConnection(GSATransaction.java:794)
15:33:20, 279 ERROR [stderr] (RepositoryWorkerThread-1(Pre-Deployment)) to atg.adapter.gsa.GSAItemDescriptor.getConnection(GSAItemDescriptor.java:2745)
15:33:20, 279 ERROR [stderr] (RepositoryWorkerThread-1(Pre-Deployment)) to atg.adapter.gsa.GSAItemDescriptor.addItem(GSAItemDescriptor.java:7310)
15:33:20, 279 ERROR [stderr] (RepositoryWorkerThread-1(Pre-Deployment)) to atg.adapter.gsa.GSARepository.addItem(GSARepository.java:1054)
15:33:20, 279 ERROR [stderr] (RepositoryWorkerThread-1(Pre-Deployment)) to atg.deployment.repository.ReferenceItemGenerator.createDummyItem(ReferenceItemGenerator.java:579)
15:33:20, 280 ERROR [stderr] (RepositoryWorkerThread-1(Pre-Deployment)) to atg.deployment.repository.ReferenceItemGenerator.findDummyReferenceItem(ReferenceItemGenerator.java:657)
15:33:20, 280 ERROR [stderr] (RepositoryWorkerThread-1(Pre-Deployment)) to atg.deployment.repository.ReferenceItemGenerator.generateDummyItems(ReferenceItemGenerator.java:314)
15:33:20, 280 ERROR [stderr] (RepositoryWorkerThread-1(Pre-Deployment)) to atg.deployment.repository.RepositoryWorkerThread.preDeploymentPhase(RepositoryWorkerThread.java:569)
15:33:20, 280 ERROR [stderr] (RepositoryWorkerThread-1(Pre-Deployment)) to atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:338)
15:33:20, 419 ERROR [nucleusNamespace.atg.deployment.DeploymentManager] (null RepositoryWorkerThread-1(Pre-Deployment)): CONTAINER: atg.repository.RepositoryException; Source: Java.Sql.SqlException: javax.resource.ResourceException: IJ000457: Unchecked throwable in managedConnectionReconnected() cl = org.jboss.jca.core.connectionm
at atg.adapter.gsa.GSAItemDescriptor.addItem(GSAItemDescriptor.java:7393) [_DAS_slib_sclasses.jar:]
at atg.adapter.gsa.GSARepository.addItem(GSARepository.java:1054) [_DAS_slib_sclasses.jar:]
at atg.deployment.repository.ReferenceItemGenerator.createDummyItem(ReferenceItemGenerator.java:579) [_DAS_slib_sclasses.jar:]
at atg.deployment.repository.ReferenceItemGenerator.findDummyReferenceItem(ReferenceItemGenerator.java:657) [_DAS_slib_sclasses.jar:]
at atg.deployment.repository.ReferenceItemGenerator.generateDummyItems(ReferenceItemGenerator.java:314) [_DAS_slib_sclasses.jar:]
at atg.deployment.repository.RepositoryWorkerThread.preDeploymentPhase(RepositoryWorkerThread.java:569) [_DAS_slib_sclasses.jar:]
at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:338) [_DAS_slib_sclasses.jar:]
Caused by: java.sql.SQLException: javax.resource.ResourceException: IJ000457: Unchecked throwable in managedConnectionReconnected() cl=org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@3486b4aa[state=NORMAL managed connection=org.jboss.jca.adapters.jdbc.xa.XAManagedConnection@7368cd26 connection handles = 0 las
at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:147)
at atg.service.jdbc.SwitchingDataSource.getConnection(SwitchingDataSource.java:931) [_DAS_slib_sclasses.jar:]
at atg.adapter.gsa.GSATransaction.getConnection(GSATransaction.java:794) [_DAS_slib_sclasses.jar:]
at atg.adapter.gsa.GSAItemDescriptor.getConnection(GSAItemDescriptor.java:2745) [_DAS_slib_sclasses.jar:]
at atg.adapter.gsa.GSAItemDescriptor.addItem(GSAItemDescriptor.java:7310) [_DAS_slib_sclasses.jar:]
... 6 more
Caused by: javax.resource.ResourceException: IJ000457: Unchecked throwable in managedConnectionReconnected() cl=org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@3486b4aa[state=NORMAL managed connection=org.jboss.jca.adapters.jdbc.xa.XAManagedConnection@7368cd26 connection handles = 0 lastUse = trac 1399716200373
at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.reconnectManagedConnection(AbstractConnectionManager.java:604)
at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:467)
at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:139)
... more than 10
Caused by: javax.resource.ResourceException: IJ000461: could not enlist in the transaction at the entrance of meta object consciousness
at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.managedConnectionReconnected(TxConnectionManagerImpl.java:474)
at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.reconnectManagedConnection(AbstractConnectionManager.java:599)
... 12 more
Caused by: javax.transaction.SystemException: IJ000356: could not enlist: java.lang.Throwable: failed to register resource, see the previous warnings. TX = TransactionImple < ac, BasicAction: 0:ffff7f000001:88fb79e:536df08b:d0ee status: ActionStatus.ABORT_ONLY >
to org.jboss.jca.core.connectionmanager.listener.TxConnectionListener$ TransactionSynchronization.checkEnlisted (TxConnectionListener.java:572)
at org.jboss.jca.core.connectionmanager.listener.TxConnectionListener.enlist(TxConnectionListener.java:283)
at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.managedConnectionReconnected(TxConnectionManagerImpl.java:467)
... 13 more
15:33:20, 637 ERROR [nucleusNamespace.atg.deployment.DeploymentManager] (point RepositoryWorkerThread-1(Pre-Deployment)) = null case is CONTAINER: atg.repository.RepositoryException; Source: Java.Sql.SqlException: javax.resource.ResourceException: IJ000457: Unchecked throwable in managedConnectionReconnected() cl = org.jboss.jca.c
at atg.adapter.gsa.GSAItemDescriptor.addItem(GSAItemDescriptor.java:7393)
at atg.adapter.gsa.GSARepository.addItem(GSARepository.java:1054)
at atg.deployment.repository.ReferenceItemGenerator.createDummyItem(ReferenceItemGenerator.java:579)
at atg.deployment.repository.ReferenceItemGenerator.findDummyReferenceItem(ReferenceItemGenerator.java:657)
at atg.deployment.repository.ReferenceItemGenerator.generateDummyItems(ReferenceItemGenerator.java:314)
at atg.deployment.repository.RepositoryWorkerThread.preDeploymentPhase(RepositoryWorkerThread.java:569)
at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:338)
message = an error occurred during the pre-deployment phase. time = 2014-05-10 atg.deployment.DeploymentFailure@15f19d72: CONTAINER: atg.repository.RepositoryException; Source: Java.Sql.SqlException: javax.resource.ResourceException: IJ000457: Unchecked throwable in managedConnectionReconnected() cl = org.jboss.jca.core.connect
at atg.adapter.gsa.GSAItemDescriptor.addItem(GSAItemDescriptor.java:7393) [_DAS_slib_sclasses.jar:]
at atg.adapter.gsa.GSARepository.addItem(GSARepository.java:1054) [_DAS_slib_sclasses.jar:]
at atg.deployment.repository.ReferenceItemGenerator.createDummyItem(ReferenceItemGenerator.java:579) [_DAS_slib_sclasses.jar:]
at atg.deployment.repository.ReferenceItemGenerator.findDummyReferenceItem(ReferenceItemGenerator.java:657) [_DAS_slib_sclasses.jar:]
at atg.deployment.repository.ReferenceItemGenerator.generateDummyItems(ReferenceItemGenerator.java:314) [_DAS_slib_sclasses.jar:]
at atg.deployment.repository.RepositoryWorkerThread.preDeploymentPhase(RepositoryWorkerThread.java:569) [_DAS_slib_sclasses.jar:]
at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:338) [_DAS_slib_sclasses.jar:]
Caused by: java.sql.SQLException: javax.resource.ResourceException: IJ000457: Unchecked throwable in managedConnectionReconnected() cl=org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@3486b4aa[state=NORMAL managed connection=org.jboss.jca.adapters.jdbc.xa.XAManagedConnection@7368cd26 connection handles = 0 las
at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:147)
at atg.service.jdbc.SwitchingDataSource.getConnection(SwitchingDataSource.java:931) [_DAS_slib_sclasses.jar:]
at atg.adapter.gsa.GSATransaction.getConnection(GSATransaction.java:794) [_DAS_slib_sclasses.jar:]
at atg.adapter.gsa.GSAItemDescriptor.getConnection(GSAItemDescriptor.java:2745) [_DAS_slib_sclasses.jar:]
at atg.adapter.gsa.GSAItemDescriptor.addItem(GSAItemDescriptor.java:7310) [_DAS_slib_sclasses.jar:]
... 6 more
Caused by: javax.resource.ResourceException: IJ000457: Unchecked throwable in managedConnectionReconnected() cl=org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@3486b4aa[state=NORMAL managed connection=org.jboss.jca.adapters.jdbc.xa.XAManagedConnection@7368cd26 connection handles = 0 lastUse = trac 1399716200373
at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.reconnectManagedConnection(AbstractConnectionManager.java:604)
at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:467)
at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:139)
... more than 10
Caused by: javax.resource.ResourceException: IJ000461: could not enlist in the transaction at the entrance of meta object consciousness
at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.managedConnectionReconnected(TxConnectionManagerImpl.java:474)
at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.reconnectManagedConnection(AbstractConnectionManager.java:599)
... 12 more
Caused by: javax.transaction.SystemException: IJ000356: could not enlist: java.lang.Throwable: failed to register resource, see the previous warnings. TX = TransactionImple < ac, BasicAction: 0:ffff7f000001:88fb79e:536df08b:d0ee status: ActionStatus.ABORT_ONLY >
to org.jboss.jca.core.connectionmanager.listener.TxConnectionListener$ TransactionSynchronization.checkEnlisted (TxConnectionListener.java:572)
at org.jboss.jca.core.connectionmanager.listener.TxConnectionListener.enlist(TxConnectionListener.java:283)
at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.managedConnectionReconnected(TxConnectionManagerImpl.java:467)
... 13 more
15:33:21, 189 INFO [nucleusNamespace.atg.epub.DeploymentServer] (wire - 273) DEBUG DistributedDeploymentAdapter: found 1 failure messages
15:33:21, 233 INFO [nucleusNamespace.atg.epub.DeploymentServer] (wire - 273) DistributedDeploymentAdapter DEBUG: adding error message an error occurred during the pre-deployment phase. with gravity error
15:33:21, 851 INFO [nucleusNamespace.atg.epub.DeploymentServer] (main deployment :) wire DEBUG DistributedDeploymentAdapter:DeploymentListener.deploymentFailed called for deployment with ID: 300001
15:33:21, 851 INFO [nucleusNamespace.atg.epub.DeploymentServer] (main deployment :) wire DistributedDeploymentAdapter:DAFDeploymentID DEBUG: 300001 corresponds DeploymentID: 300001
15:33:21, 851 INFO [nucleusNamespace.atg.epub.DeploymentServer] (main deployment :) wire DEBUG DistributedDeploymentAdapter:DeploymentListener.deploymentFailed
15:33:21, 851 INFO [nucleusNamespace.atg.epub.DeploymentServer] (wire - 273) DEBUG DistributedDeploymentAdapter: found 1 failure messages
15:33:21, 851 INFO [nucleusNamespace.atg.epub.DeploymentServer] (wire - 273) DistributedDeploymentAdapter DEBUG: adding error message an error occurred during the pre-deployment phase. with gravity error
15:33:21, 855 INFO [nucleusNamespace.atg.epub.DeploymentServer] (wire - 273) DistributedDeploymentAdapter DEBUG: deployment failed
15:33:22, 307 ERROR [nucleusNamespace.atg.epub.DeploymentServer] (wire - 273) null: atg.deployment.common.DeploymentException: '300001' target 'Production' deployment has encountered an error of level of deployment of system during data transfer.
at atg.deployment.common.ResourceUtil.exception(ResourceUtil.java:333) [_Publishing.base_slib_sclasses.jar:]
at atg.deployment.adapter.DistributedDeploymentAdapter.deployData(DistributedDeploymentAdapter.java:1391) [_Publishing.base_slib_sclasses.jar:]
at atg.deployment.adapter.DistributedDeploymentAdapter.transferData(DistributedDeploymentAdapter.java:278) [_Publishing.base_slib_sclasses.jar:]
at atg.deployment.server.Deployment.run(Deployment.java:1960) [_Publishing.base_slib_sclasses.jar:]
at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
CTRL + C detected
Out now...
15:34:06, 769 INFO [org.apache.coyote.http11] (service MSC 1-4 thread) JBWEB003075: Coyote HTTP/1.1, hanging on: http-/0.0.0.0:8180
15:34:06, 775 INFO [org.apache.coyote.http11] (service MSC 1-4 thread) JBWEB003077: Coyote HTTP/1.1, hanging on: http-/0.0.0.0:8180
15:34:07, 405 INFO [org.jboss.as.connector.subsystems.datasources] (service MSC 1-16 thread) JBAS010409: independent data source [java: / ATGSwitchingDS_B]
15:34:07, 405 INFO [org.jboss.as.connector.subsystems.datasources] (the MSC 1-11 service thread) JBAS010409: independent data source [java: / ATGPublishingDS]
15:34:07, 405 INFO [org.jboss.as.connector.subsystems.datasources] (the MSC 1-13 service thread) JBAS010409: independent data source [java: / ATGProductionDS]
15:34:07, 405 INFO [org.jboss.as.connector.subsystems.datasources] (MSC 1-6 service thread) JBAS010409: independent data source [java: / ATGSwitchingDS_A]
15:34:07, 590 INFO [org.jboss.web] (ServerService Thread Pool - 154) JBAS018224: cancel registration of web context: /FlexUI
15:34:07, 634 INFO [org.apache.catalina.core] (the MSC 1-8 service thread) JBWEB001079: container org.apache.catalina.core.ContainerBase. [jboss.web]. [default host]. [/] has not been started
15:34:11, 070 INFO [org.jboss.as.server.deployment] (the MSC 1-3 service thread) JBAS015877: ojdbc6.jar deployment order (duration-name: ojdbc6.jar) in 4998ms
15:34:12, 078 INFO [org.jboss.web] (ServerService Thread Pool - 157) JBAS018224: cancel registration of web context: / WebUI-Preview
15:34:12, 179 INFO [org.jboss.web] (ServerService Thread Pool - 157) JBAS018224: cancel registration of web context: $fw

Solved by adding inside the tag

Versions of JBOSS and JDK for ATG 11.0.

Hi guys,.
Could you please suggest me the required versions of JBOSS and JDK for ATG 11.0.
Thank you

Go through the following

Oracle, ATG trade Web - Application Server Configuration

Oracle ATG Commerce Web - installation of the ATG platform

Oracle, ATG Commerce - JBoss EAP Web 6

Partitions of JBoss - the FMS to create criteria

What are the rules for Foglight determine whether an instance of JBoss is part of a JBoss cluster? I have a few instances use multicast addresses because they are part of a JBoss cluster. I have an instance that is a stand-alone instance of JBoss, but Foglight is implemented as if it were part of the cluster.

Can send you a screenshot showing this behavior?

The following article will give you information on this https://support.quest.com/SolutionDetail.aspx?id=SOL59512

You can manually specify the name of partition of JBoss

In the Properties section of the file properties of the agent JavaEEDeploymentManager Agent, clone the list AgentConfigProperties and change the copy for specific JavaEE deplyoment Manager that applies to the separate system.

Check the JBossPartitionID and give it a name.

You have to restart the agent manager of JavaEEdeployment for the change to be applied.

Golan

Error in jboss

HI guys,.
I am getting error in jboss below
15:51:54, 125 Throwable WARN [JBossManagedConnectionPool] then that he was trying to get a new connection: null
org.jboss.resource.JBossResourceException: could not create a connection; -nested throwable: (org.jboss.resource.JBossResourceException: class not found for XADataSource oracle.jdbc.xa.client.OracleXADataSource; - nested throwable: (java.lang.ClassNotFoundException: oracle.jdbc.xa.client.OracleXADataSource))
at org.jboss.resource.adapter.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:465)
at org.jboss.resource.adapter.jdbc.xa.XAManagedConnectionFactory.createManagedConnection(XAManagedConnectionFactory.java:409)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:633)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:267)
to org.jboss.resource.connectionmanager.JBossManagedConnectionPool$ BasePool.getConnection (JBossManagedConnectionPool.java:622)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:404)
at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:381)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:496)
to org.jboss.resource.connectionmanager.BaseConnectionManager2$ ConnectionManagerProxy.allocateConnection (BaseConnectionManager2.java:941)
at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89)
at atg.adapter.gsa.GSARepository.initialize(GSARepository.java:5809)
at atg.adapter.gsa.GSARepository.initializeTransactionally(GSARepository.java:5747)
How do I solve this problem

Hello

the error is:

; (- nested throwable: (java.lang.ClassNotFoundException: oracle.jdbc.xa.client.OracleXADataSource))

You must make sure that the Oracle JDBC jar file is on the JBoss classpath. You add the jar file to the JBoss server lib directory.

adding connectivity alternatives jmx (i.e. 7 JBoss)

JBoss 7 (Wildfly) does not expose a normal JMX/RMI port. Instead, they exhibit a communication protocol to remote jmx on their management port (usually 9999).
What is the best way to add the required classes for JMC so that a connection string like the following will work?
Service: jmx:remoting - jmx: / / < hostname >: < management port >

I managed to connect by creating a coded hard - Xbootclasspath/a entry in jmc.ini based on the extended classpath that generates jconsole.bat of JBoss. (Easily pasteable copy in Windows if you set @echo = on in the bat file).

My jmc.ini now looks like this (for JBoss EAP 6.1, note that the necessary jar versions and their locations are different between the different versions, you need to get from jconsole.bat to be sure of doing things).

Also note that the location of the Xbootclasspath-/ in the jmc.ini is important, it must be sub - vmargs. And that the syntax requires a colon ':' post - Xbootclasspath/a, a space character will not work, it was new for me because I hadn't used this option before.

-Start

.. / lib/missioncontrol/plugins/org. Eclipse.Equinox.launcher_1.3.0.v20120522 - 1813.jar

-launcher.library

.. / lib/missioncontrol/plugins/org. Eclipse.Equinox.Launcher.Win32.Win32.x86_1.1.200.v20120913 - 144807

-vm

./javaw.exe

-vmargs

-Xbootclasspath/a:[JBoss-home]/modules/system/layers/base/org/JBoss/Remoting-JMX/main/Remoting-JMX-1.1.0.final-RedHat-1.jar; [JBoss-home]/modules/system/layers/base/org/JBoss/remoting3/main/JBoss-Remoting-3.2.16.GA-RedHat-1.jar; [JBoss-home]/modules/system/layers/base/org/JBoss/logging/main/JBoss-logging-3.1.2.GA-RedHat-1.jar; [JBoss-home]/modules/system/layers/base/org/JBoss/xnio/main/xnio-API-3.0.7.GA-RedHat-1.jar; [JBoss-home]/modules/system/layers/base/org/JBoss/xnio/NIO/main/xnio-NIO-3.0.7.GA-RedHat-1.jar; [JBoss-home]/modules/system/layers/base/org/JBoss/SASL/main/JBoss-SASL-1.0.3.final-RedHat-1.jar; [JBoss-home]/modules/system/layers/base/org/JBoss/marshalling/main/JBoss-marshalling-1.3.15.GA-RedHat-1-BZ-965901.jar; [JBoss-home]/modules/system/layers/base/org/JBoss/marshalling/main/JBoss-marshalling-1.3.16.GA-RedHat-1-BZ-987256.jar; [JBoss-home]/modules/system/layers/base/org/JBoss/marshalling/main/JBoss-marshalling-1.3.16.GA-RedHat-1.jar; [JBoss-home]/modules/system/layers/base/org/JBoss/marshalling/River/main/JBoss-marshalling-River-1.3.16.GA-RedHat-1.jar; [JBoss-home]/modules/system/layers/base/org/JBoss/as/CLI/main/JBoss-as-CLI-7.2.0.final-RedHat-8.jar; [jboss-home]/modules/system/layers/base/org/jboss/staxmapper/main/staxmapper-1.1.0.Final-redhat-2.jar; [JBoss-home]/modules/system/layers/base/org/JBoss/as/Protocol/main/JBoss-as-Protocol-7.2.0.final-RedHat-8.jar; [JBoss-home]/modules/system/layers/base/org/JBoss/DMR/main/JBoss-DMR-1.1.6.final-RedHat-1.jar; [JBoss-home]/modules/system/layers/base/org/JBoss/as/controller-client/main/JBoss-as-controller-client-7.2.0.final-RedHat-8.jar; [JBoss-home]/modules/system/layers/base/org/JBoss/threads/main/JBoss-threads-2.1.0.final-RedHat-1.jar

-XX: + UseG1GC

-XX: + UnlockCommercialFeatures

-XX: + FlightRecorder

-Djava .net .preferIPv4Stack = true

And of course, to connect to JMC, you will need to select 'Custom JMX service URL' and enter the URL after the way that JBoss, service: jmx:remoting - jmx: / /:

How can we consider jsp changes without deployment in jboss EAP - version 5.1.2

Hi Experts,
I use version 5.1.2 - EAP-jboss as server applications for ATG 10.1.2 application.
If I change the names of labels or all small changes in JSP pages, the changes do not think in application.
View the changes that I need to reboot the server so only I'm able to see these changes.
with difficult deployment I want to see the changes.
In jboss EAP - 5.1.0 this problem isn't here, we can learn jsp changes without restarting the server.
Can you please help me to overcome this problem.
Thank you and best regards,
Murali.Ch

Make the following changes in you web.xml under /jboss/Server//deployers/jbossweb.deployer/web.xml

Under,

jsp org.apache.jasper.servlet.JspServlet

Add the following

development true modificationTestInterval 0

This will recompile your jsp on the fly.

Just make sure that this feature is only enabled for development environments and you turn it off in PRODUCTION.

I hope this helps!

~ Yvan

JBoss.mq:service = MessageCache is not registered
Greetings,

CentOS fresh install with JBoss 4.0.5, HQ Agent 4.0.3. Everything has been discovered late, not to mention that JBoss. Even if it comes in resources-server, it displays an error:

The configuration has not been set for this resource due to: invalid configuration: error recovery value: metric not found [jboss.mq:service=MessageCache:CacheHits:java.naming.provider.url=jnp%3A//127.0.0.1%3A1099,java.naming.security.principal=***,java.naming.security.credentials=***]: javax.management.InstanceNotFoundException: jboss.mq:service = MessageCache is not registered.

I can't update the credentials for the JMX console via the web interface, it continues to run above error at home.

Does anyone have an idea what causes this? I have a little more with JBoss 4.x servers where I don't have this problem. (jboss installation is identical on all servers).

I looked around for "MessageCache is not registered" and similar variations, can not really find something useful that would help me to get back on the right track. I don't really know if the problem is with the Hyperic Agent, JBoss, something else?

Thank you

Post edited by: uniwiz
Hello

Try the following steps:

Go to the Administration tab-> default Configuration monitoring
Do scroll to JBoss 4.x and disable metric collection for JMS Message Cache according to the Manual:

http://support.Hyperic.com/display/doc/monitoring+defaults+configuration

Then try to set up the configuration of the resource.

See you soon,.
Mirko

picked up on JBoss do not automatically receive the agent installation
I installed the server hq 4.0 and agent and I have a jboss Server 5 current running on the target computer.
usually when I start the agent, it will automatically detect that jboss is running on the target, but this time it didn't.

no idea why?
is jboss 5 supported by automatic discovery?
How can I get that it will automatically record (id rather not add jboss manually)

Thank you
mast

Post edited by: cronos4d
Hello

Yes, in HQ 4.2, it is supported. It could be argued by 4.1, I don't remember when it was introduced. However, I know that it is available in 4.2.

Going Old School - ADF 10g on JBoss 7

Hi all
Yes, I know it is not supported. Yes, I know it's old. Yes, I know you're wondering why. Because there was a voice from above, "moving our ADF 10g to JBoss applications! Such are the ways of the senior management.
Now it's the epic of the week 4 and I reached a major obstacle. For some reason any (I think) is not generated javascript code associated with the components of 10g. The components are rendered, but not compressed and command buttons would order. I can start JBoss and the app without errors, but when I insert a page in Internet Explorer, I get many javascript such as these errors:
```
The value of the property '_checkUnload' is null or undefined, not a Function object.
The value of the property '_defaultTZ' is null or undefined, not a Function object.
Error: The value of the property '_submitFormCheck' is null or undefined, not a Function object.
```
Maybe it's a class file missing?
```
adf-controller.jar
adf-faces-api.jar
adf-faces-impl.jar
adfbinding.jar
adfcm.jar
adfm.jar
adfmtl.jar
adfmweb.jar
adfshare.jar
adfui.jar
bc4jct.jar
bc4jctejb.jar
bc4jdomorcl.jar
bc4jimdomains.jar
bc4jmt.jar
bc4jmtejb.jar
collections.jar
commons-beanutils.jar
commons-collections.jar
commons-digester.jar
commons-lang.jar
commons-logging.jar
dms.jar
eclipselink.jar
iText-5.0.5.jar
jsf-api_1-1.jar
jsf-impl_1-1.jar
ojdbc14.jar
ojdbc14dms.jar
orai18n-mapping.jar
org.eclipse.persistence.asm.jar
org.eclipse.persistence.core.jar
poi.jar
print.txt
runtime12.jar
translator.jar
xml.jar
xmlparserv2.jar
```
I'm a bit at a loss. Any ideas?
Last week I tried to migrate only the entire application to 11g Trinidad components, but it turns out that counting does not work the same way in 11g as he did in 10g for the whole application is radically different. In addition, it seems that the app was applied as well, custom appearance which is also different in 11g. So I thought best to see if I could get work 10g.
Using the latest version of JDev (11.1.2.4), but the import of old libraries of 10g in my project.

Hi Shay. Thank you for your response. I had a little previously used this document.

Turns out in my web.xml file, I need to put the version = "2.4" in the section. That triggers JBoss to use the correct version of the JSP (I think). Previously, I had 2.5 in there, what components of 10 GB ADF are not compatible with.

* Edit * while that may have something to do with it, I also had two version of the adf faces - impl.jar. One had underscores in the 10_1_3_x removed from the files. Otherwise, JDeveloper would not compile the program. However, it also caused the previous problem. So I have two sets of jars, one for compiling and one for the deployment.

Support for JBOSS 4.3
the last supported Version for JBOSS at HQ at the moment is 4.2.
When is it possible to monitor JBOSS 4.3?

Thanks for a response
Rasmus
I don't think that we had the chance to take a look at JBoss 4.3 again.
Have you tried to create a JBoss 4.2 Server and configure it manually
for your 4.3 JBoss see if it works at all?

Charles

JCA on JBoss
Hello

I took several days, setting up connection between jboss and tuxedo by jca, but I only have TPENOENT.

Here's my configuration files

RA. XML

+ <? XML version = "1.0" encoding = "UTF-8"? > +.
+ < xmlns = "http://java.sun.com/xml/ns/j2ee" + connector
xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance".
xsi: schemaLocation = "http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd".
version = "1.5" >
+ JCA Tuxedo adapter < display name > < / name >.
+ Oracle < vendor name > - < / vendor name > +.
+ Tuxedo < eis-type > < / eis-type > +.
+ resourceadapter < version > 11gR 1 (11.1.1.2.1) < / resourceadapter-version > +.
+ < license > +.
+ license < description > Tuxedo salt < / description >.
+ license-required > < false < / license-required > +.
+ < / license > +.
+ < resourceadapter > +.
+ > class resourceadapter < com.oracle.tuxedo.adapter.TuxedoResourceAdapter < / resourceadapter class > +.
+ < config-property > +.
+ traceLevel < config-property-name > < / config-property-name > +.
+ java.lang.String < config-property-type > < / config-property-type > +.
+ < config-property-value > 80000 < / config-property-value > +.
+ < / config-property > +.
+ < config-property > +.
+ < config-property-name > xaAffinity < / config-property-name > +.
+ java.lang.String < config-property-type > < / config-property-type > +.
+ < config-property-value > true < / config-property-value > +.
+ < / config-property > +.
+ < config-property > +.
+ dmconfig < config-property-name > < / config-property-name > +.
+ java.lang.String < config-property-type > < / config-property-type > +.
+ < config-property-value > /export/home/jboss/jboss/standalone/configuration/dmconfig.xml < / config-property-value > +.
+ < / config-property > +.
+ < outgoing resourceadapter - > +.
+ connection < definition > +.
+ class < managedconnectionfactory > com.oracle.tuxedo.adapter.spi.TuxedoManagedConnectionFactory < / managedconnectionfactory-class > +.
+ > connectionfactory interface < javax.resource.cci.ConnectionFactory < / connectionfactory interface > +.
+ com.oracle.tuxedo.adapter.cci.TuxedoConnectionFactory < connectionfactory-impl-class > < / connectionfactory-impl-class > +.
+ connection < interface > javax.resource.cci.Connection < / interfaces > +.
+ connection < impl-class > com.oracle.tuxedo.adapter.cci.TuxedoJCAConnection < / connection-impl-class > +.
+ < / connection-definition > +.
+ < transaction-support > LocalTransaction < / transaction-support > +.
+ < authentication mechanism - > +.
+ BasicPassword <-authentication mechanism-type > < / type of authentication mechanism > +.
+ > interface credential < javax.resource.spi.security.PasswordCredential < / credential-interface > +.
+ < / authentication mechanism > +.
+ fake > helps reauthentication < < / re-authentication-support > +.
+ < / outgoing-resourceadapter > +.
+ < / resourceadapter > +.
+ < / connector > +.

Dmconfig. XML

+ <? XML version = "1.0" encoding = "UTF-8"? > < TuxedoConnector > +.
+ < name LocalAccessPoint = "JDOM" > +.
+ < AccessPointId > JDOM1 < / AccessPointId > +.
+ < NetworkAddress > //maqueta2:5001 < / NetworkAddress > +.
+ < / LocalAccessPoint > +.
+ < name RemoteAccessPoint = "TDOM" > +.
+ < AccessPointId > TDOM1 < / AccessPointId > +.
+ < NetworkAddress > //maqueta2:5000 < / NetworkAddress > +.
+ < / RemoteAccessPoint > +.
+ < SessionProfile name = "profile_1" > +.
+ < security > NO < / security > +.
+ < period > 30000 < / period > +.
+ < interoperate > false < / interfonctionnent > +.
+ < ConnectionPolicy > ON_STARTUP < / ConnectionPolicy > +.
+ local < ACLPolicy > < / ACLPolicy > +.
+ local < CredentialPolicy > < / CredentialPolicy > +.
+ < > 60 RetryInterval < / RetryInterval > +.
+ < MaxRetries > 1000 < / MaxRetries > +.
+ < CompressionLimit > 1000000 < / CompressionLimit > +.
+ < KeepAlive > 100000 < / KeepAlive > +.
+ < KeepAliveWait > 200000 < / KeepAliveWait > +.
+ < / SessionProfile > +.
+ < name of session = "session_1" > +.
+ JDOM < LocalAccessPointName > < / LocalAccessPointName > +.
+ TDOM < RemoteAccessPointName > < / RemoteAccessPointName > +.
+ < Nom_de_profil > profile_1 < / ProfileName > +.
+ < / session > +.
+ < / TuxedoConnector > +.

standalone. XML

....
+ < subsystem xmlns = "urn: jboss:domain:resource - adapters: 1.1" > +.
+ < resource adapters > +.
+ < adapter resources - > +.
+ < archive > +.
com.oracle.tuxedo.TuxedoAdapter.rar
+ < / archive > +.
+ < transaction-support > LocalTransaction < / transaction-support > +.
+ < connection-definitions > +.
+ < class-name = "com.oracle.tuxedo.adapter.spi.TuxedoManagedConnectionFactory" - name = jndi connection-definition "" java: / ist/TuxedoConnectionFactory "enabled ="true"use-java-context = 'false' pool-name =" java: jboss/ist/TuxedoConnectionFactory "/ > +"
+ < / connection-definitions > +.
+ < / adapter resources > +.
+ < / resource adapters > +.
+ < / subsystem > +.
...

Dmconfig

* DM_RESOURCES +.
+#+
VERSION = U22
+#+
* DM_LOCAL_DOMAINS +.
+#+
TDOM GWGRP = GRUPO3
TYPE = TDOMAIN
NETWORKID = "TDOM1."
PERIOD = 60
DMTLOGDEV = "/ appl/sf/tux/logs/DMTLOG.
DMTLOGNAME = DMTLOG
SECURITY = NONE
+#+
* DM_REMOTE_DOMAINS +.
+#+
TYPE = TDOMAIN JDOM
NETWORKID = "JDOM1."
+#+

* DM_TDOMAIN +.
+#+
TDOM NWADDR = "//maqueta2:5000".
JDOM NWADDR = "//maqueta2:5001".
* DM_LOCAL_SERVICES +.
TOUPPER

It's the connection in ULOG:

174335.maqueta2! GWTDOMAIN.26860.4.0: LIBGWT_CAT:1128: INFO: accepted connection of the field (networkid = < JDOM1 >)

and the jboss:

17:59:57, 618 INFO [org.jboss.as.connector.deployers.RaXmlDeployer] (service MSC 1-32 thread) IJ020002: deployed: file:/export/home/jboss/jboss-eap-6.1/standalone/tmp/vfs/tempd94ea707efb676cf/com.oracle.tuxedo.TuxedoAdapter.rar-f7058dab3d57d6b6/contents/
17:59:57, 626 INFO [org.jboss.as.connector.deployment] (the MSC 1-55 service thread) JBAS010401: JCA ConnectionFactory enlazado [java: / ist/TuxedoConnectionFactory]
17:59:57, 758 INFO [org.jboss.as.server] (HttpManagementService-NET - 1) JBAS018559: Implementado "com.oracle.tuxedo.TuxedoAdapter.rar" (name-DURATION: 'com.oracle.tuxedo.TuxedoAdapter.rar')
17:59:58, 144 INFO [stdout] (by default-NET - 2) < kills Jun 04 17:59:58 CEST 2013 > < Debug > < WTC > < BEA-180072 > < +++ / tplle/crypFinishOne/send_key (16) +++ >
17:59:58, 147 INFO [stdout] (by default-NET - 2) < kills Jun 04 17:59:58 CEST 2013 > < Debug > < WTC > < BEA-180113 > < 0 C F3 E2 49 51 93 2F A5 92 48 07 1 7F F4 92 A3... IQ? ?? H...??. >
17:59:58, 149 INFO [stdout] (by default-NET - 2) < kills Jun 04 17:59:58 CEST 2013 > < Debug > < WTC > < BEA-180073 > < +++ END +++ >
17:59:58, 151 INFO [stdout] (by default-NET - 2) < kills Jun 04 17:59:58 CEST 2013 > < Debug > < WTC > < BEA-180072 > < +++ / tplle/crypFinishOne/recv_key (16) +++ >
17:59:58, 153 INFO [stdout] (by default-NET - 2) < kills Jun 04 17:59:58 CEST 2013 > < Debug > < WTC > < BEA-180113 > < A5 DA EF 93 BE 79 E7 80 51 37 47 F5 77 C1 C0 AF? ?? y.? Q7G.w.. ? >
17:59:58, 154 INFO [stdout] (by default-NET - 2) < kills Jun 04 17:59:58 CEST 2013 > < Debug > < WTC > < BEA-180073 > < +++ END +++ >
17:59:58, 178 INFO [com.oracle.tuxedo.utils.TuxedoLogger] (by default-NET - 2) makes the connection to the remote domain TDOM1.

But when I prove the service, the only thing I get is TPENOENT

18:01:11, 888 ERROR [stderr] (http-/0.0.0.0:8080-1) TPENOENT (6): 0:0:TPED_MINVAL (0): QMNONE (0): 0:There no resources imported with name TOUPPER is configured!

I don't know what else to do!

Thanks in advance
I solved the problem with the TPENOENT.

All the configuration was ok, the problem came from libraries outside smoking. I put them in the package of the ear and not as global libraries in jboss (in the form of plug-ins).

For some reason any if you don't resolve the dependencies of your servlet, ejb... of these libraries, you are out of the context of smoking.

control - jboss DO NOT start stop button
Servers > jboss 4.0 on the HYPERIC server - for its own built in jboss, I try to use the CONTROL to a fast STOP action button... I have the screen shows a progress icon
This movement, but he never runs... If I click on the actions of CONTROL on the dashboard it says could NOT

Dashboard, it also says:

Control not supported for HQ JBoss 4.x...

IM using 3.0 V296 opensource. IF this function suppose to work, or is is NOT supported because its hyperic's JBOSS servers. ???
Im just trying to see HOW and WHAT can I use this CONTROL for.
> HQ will be able to stop or restart its own internal
> JBoss server or is this part of the bug?

HQ behaves correctly: it prevents you from stopping and starting his own server JBoss internal. We want it to work this way so that users do not inadvertently in the foot.

The only thing that could be interpreted as a bug, it's that when the action fails it doesn't clearly tells you why it failed. In a perfect world, the error message would be more informative, but it is not a bug in high priority right now.

-Noah-

-C in jboss

Similar Questions

Maybe you are looking for