[JBoss JIRA] (WFLY-5914) JNDI view ClassNotFoundException with remote entry
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-5914?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-5914:
-----------------------------------
Component/s: JMS
Naming
> JNDI view ClassNotFoundException with remote entry
> --------------------------------------------------
>
> Key: WFLY-5914
> URL: https://issues.jboss.org/browse/WFLY-5914
> Project: WildFly
> Issue Type: Bug
> Components: JMS, Naming
> Affects Versions: 10.0.0.CR5
> Reporter: Guillermo González de Agüero
> Assignee: Jason Greene
> Attachments: domain.xml
>
>
> When a binding to a remote Artemis Topic/ConnectionFactory is created, JNDI view fails with a ClassNotFoundException. Both servers are running the "full" profile.
> I attach my domain.xml for reference porpuses. No application needs to be deployed.
> Full operation result:
> [domain@localhost:9990 /] /host=master/server=app-ins01/subsystem=naming:jndi-view()
> {
> "outcome" => "failed",
> "result" => {"java: contexts" => {
> "java:" => {
> "ConnectionFactory" => {
> "class-name" => "org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory",
> "value" => "ActiveMQConnectionFactory [serverLocator=ServerLocatorImpl [initialConnectors=[TransportConfiguration(name=in-vm, factory=org-apache-activemq-artemis-core-remoting-impl-invm-InVMConnectorFactory) ?serverId=0], discoveryGroupConfiguration=null], clientID=null, consumerWindowSize = 1048576, dupsOKBatchSize=1048576, transactionBatchSize=1048576, readOnly=false]"
> },
> "JmsXA" => {
> "class-name" => "java.lang.Object",
> "value" => "?"
> },
> "TransactionManager" => {
> "class-name" => "com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate",
> "value" => "com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate@27b3c7"
> },
> "jms" => {
> "class-name" => "javax.naming.Context",
> "children" => {"queue" => {
> "class-name" => "javax.naming.Context",
> "children" => {
> "DLQ" => {
> "class-name" => "org.apache.activemq.artemis.jms.client.ActiveMQQueue",
> "value" => "ActiveMQQueue[DLQ]"
> },
> "ExpiryQueue" => {
> "class-name" => "org.apache.activemq.artemis.jms.client.ActiveMQQueue",
> "value" => "ActiveMQQueue[ExpiryQueue]"
> }
> }
> }}
> },
> "jboss" => {
> "class-name" => "javax.naming.Context",
> "value" => "org.jboss.as.naming.WritableServiceBasedNamingStore@d2c52f"
> },
> "global" => {
> "class-name" => "javax.naming.Context",
> "value" => "org.jboss.as.naming.WritableServiceBasedNamingStore@932e80"
> },
> "ejb" => {
> "class-name" => "javax.naming.Context",
> "children" => {"mgmt" => {
> "class-name" => "javax.naming.Context",
> "children" => {"MEJB" => {
> "class-name" => "javax.management.j2ee.ManagementHome",
> "value" => "Proxy for remote EJB EJBHomeLocator for \"jsr-77/jsr-77/EJB\", view is interface javax.management.j2ee.ManagementHome, affinity is None"
> }}
> }}
> }
> },
> "java:jboss" => {
> "ORB" => {
> "class-name" => "com.sun.corba.se.impl.orb.ORBImpl",
> "value" => "com.sun.corba.se.impl.orb.ORBImpl@1306d15"
> },
> "TransactionManager" => {
> "class-name" => "com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate",
> "value" => "com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate@27b3c7"
> },
> "TransactionSynchronizationRegistry" => {
> "class-name" => "org.jboss.as.txn.service.internal.tsr.TransactionSynchronizationRegistryWrapper",
> "value" => "org.jboss.as.txn.service.internal.tsr.TransactionSynchronizationRegistryWrapper@206b4c"
> },
> "UserTransaction" => {
> "class-name" => "javax.transaction.UserTransaction",
> "value" => "UserTransaction"
> },
> "corbanaming" => {
> "class-name" => "org.omg.CosNaming._NamingContextExtStub",
> "value" => "IOR:000000000000002b49444c3a6f6d672e6f72672f436f734e616d696e672f4e616d696e67436f6e746578744578743a312e300000000000010000000000000110000102000000000a3132372e302e302e31000e3600000039afabcb00000000220000000100000001000000000000000200000008526f6f74504f4100000000074e616d696e67000000000004726f6f741400000000000005000000010000002000000000000100010000000205010001000100200001010900000001000101000000002600000002000200000000000300000014000000000000000a3132372e302e302e31000e3700000014000000080000001a00000e370000002100000050000000000000000100000000000000220000000000400000000000080606678102010101000000170401000806066781020101010000000744656661756c740000000000000000000000000000000000"
> },
> "irpoa" => {
> "class-name" => "com.sun.corba.se.impl.oa.poa.POAImpl",
> "value" => "POA[ObjectAdapterID[RootPOA/IRPOA], uniquePOAId=2, state=RUN, invocationCount=0]"
> },
> "jaas" => {
> "class-name" => "com.sun.proxy.$Proxy58",
> "value" => "java:jboss/jaas/ Context proxy"
> },
> "poa" => {
> "class-name" => "com.sun.corba.se.impl.oa.poa.POAImpl",
> "value" => "POA[ObjectAdapterID[RootPOA], uniquePOAId=0, state=RUN, invocationCount=0]"
> },
> "ee" => {
> "class-name" => "javax.naming.Context",
> "children" => {"concurrency" => {
> "class-name" => "javax.naming.Context",
> "children" => {
> "scheduler" => {
> "class-name" => "javax.naming.Context",
> "children" => {"default" => {
> "class-name" => "java.lang.Object",
> "value" => "?"
> }}
> },
> "factory" => {
> "class-name" => "javax.naming.Context",
> "children" => {"default" => {
> "class-name" => "java.lang.Object",
> "value" => "?"
> }}
> },
> "executor" => {
> "class-name" => "javax.naming.Context",
> "children" => {"default" => {
> "class-name" => "java.lang.Object",
> "value" => "?"
> }}
> },
> "context" => {
> "class-name" => "javax.naming.Context",
> "children" => {"default" => {
> "class-name" => "java.lang.Object",
> "value" => "?"
> }}
> }
> }
> }}
> },
> "infinispan" => {
> "class-name" => "javax.naming.Context",
> "children" => {"container" => {
> "class-name" => "javax.naming.Context",
> "children" => {
> "ejb" => {
> "class-name" => "org.jboss.as.clustering.infinispan.DefaultCacheContainer",
> "value" => "ejb"
> },
> "hibernate" => {
> "class-name" => "org.jboss.as.clustering.infinispan.DefaultCacheContainer",
> "value" => "hibernate"
> },
> "server" => {
> "class-name" => "org.jboss.as.clustering.infinispan.DefaultCacheContainer",
> "value" => "server"
> },
> "web" => {
> "class-name" => "org.jboss.as.clustering.infinispan.DefaultCacheContainer",
> "value" => "web"
> }
> }
> }}
> },
> "datasources" => {
> "class-name" => "javax.naming.Context",
> "children" => {"ExampleDS" => {
> "class-name" => "org.jboss.as.connector.subsystems.datasources.WildFlyDataSource",
> "value" => "org.jboss.as.connector.subsystems.datasources.WildFlyDataSource@c79ae8"
> }}
> },
> "mail" => {
> "class-name" => "javax.naming.Context",
> "children" => {"Default" => {
> "class-name" => "javax.mail.Session",
> "value" => "javax.mail.Session@1e9f277"
> }}
> },
> "clustering" => {
> "class-name" => "javax.naming.Context",
> "children" => {"registry" => {
> "class-name" => "javax.naming.Context",
> "children" => {"ejb" => {
> "class-name" => "javax.naming.Context",
> "children" => {"client-mappings" => {
> "class-name" => "org.wildfly.clustering.server.registry.CacheRegistryFactory",
> "value" => "org.wildfly.clustering.server.registry.CacheRegistryFactory@12ac291"
> }}
> }}
> }}
> }
> },
> "java:jboss/exported" => {"jms" => {
> "class-name" => "javax.naming.Context",
> "children" => {"RemoteConnectionFactory" => {
> "class-name" => "org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory",
> "value" => "ActiveMQConnectionFactory [serverLocator=ServerLocatorImpl [initialConnectors=[TransportConfiguration(name=http-connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEnabled=true&httpPpgradeEndpoint=http-acceptor&port=8190&host=127-0-0-1], discoveryGroupConfiguration=null], clientID=null, consumerWindowSize = 1048576, dupsOKBatchSize=1048576, transactionBatchSize=1048576, readOnly=false]"
> }}
> }},
> "java:global" => undefined
> }},
> "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.RuntimeException: org.jboss.naming.remote.protocol.NamingIOException: Failed to lookup [Root exception is java.io.IOException: java.lang.ClassNotFoundException: org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory from [Module \"org.jboss.as.naming:main\" from local module loader @130015a (finder: local module finder @9f0666 (roots: c:\\wildfly-10.0.0.CR5\\modules,c:\\wildfly-10.0.0.CR5\\modules\\system\\layers\\base))]]",
> "rolled-back" => true
> }
> Injection of the resources via @Resource in an application works as expected. I found this same problem where manually doing the remote lookup from application code, which I resolved adding a dependency to Artemis module in META-INF.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months
[JBoss JIRA] (WFCORE-1258) Powershell scripts should be signed
by Tomaz Cerar (JIRA)
Tomaz Cerar created WFCORE-1258:
-----------------------------------
Summary: Powershell scripts should be signed
Key: WFCORE-1258
URL: https://issues.jboss.org/browse/WFCORE-1258
Project: WildFly Core
Issue Type: Task
Components: Scripts
Affects Versions: 2.0.5.Final
Reporter: Tomaz Cerar
Assignee: Tomaz Cerar
*.ps1 scripts should be signed otherwise uses would need to run in unsigned execution mode to make it work.
Scripts should work OOTB with RemoteSigned powershell execution policy
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months
[JBoss JIRA] (WFLY-5922) Cannot exclude java.orb.api module
by John Farrelly (JIRA)
[ https://issues.jboss.org/browse/WFLY-5922?page=com.atlassian.jira.plugin.... ]
John Farrelly commented on WFLY-5922:
-------------------------------------
I also added the exclusion to my sub-deployment, but {{javax.orb.api}} was still used.
{code:xml}
<sub-deployment name="myapp-ejb3-1.0.0.jar">
<exclusions>
<module name="javax.orb.api" />
<module name="org.omg.api" />
</exclusions>
<dependencies>
<module name="org.apache.xerces" />
<module name="org.apache.xalan" />
</dependencies>
</sub-deployment>
{code}
Is there any additional debug level I could set to see if there's some transitive dependency that is pulling in {{javax.orb.api}} despite it's exclusion? I've enabled {{TRACE}} logging for {{org.jboss.modules}}, but it doesn't say why the {{javax.orb.api}} module is being included in my application.
> Cannot exclude java.orb.api module
> ----------------------------------
>
> Key: WFLY-5922
> URL: https://issues.jboss.org/browse/WFLY-5922
> Project: WildFly
> Issue Type: Bug
> Components: Class Loading
> Affects Versions: 10.0.0.CR4
> Environment: Red Hat Enterprise Linux Server release 7.1 (Maipo)
> Linux 3.10.0-229.4.2.el7.x86_64 #1 SMP Wed May 13 10:06:09 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
> java version "1.8.0_60"
> Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
> Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
> Reporter: John Farrelly
> Assignee: David Lloyd
> Priority: Blocker
>
> We use Orbacus as our CORBA implementation, and in our application we wish to use CORBA classes only from the orbacus module, and not the JDK/WildFly bundled CORBA.
> In the {{jboss-deployment-structure.xml}} file of our {{ear}} file, we have the following:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-deployment-structure>
> <ear-subdeployments-isolated>false</ear-subdeployments-isolated>
> <deployment>
> <exclusions>
> <module name="javax.orb.api" />
> <module name="org.omg.api" />
> </exclusions>
> <dependencies>
> <module name="com.ooc.orbacus" export="true"/>
> <module name="org.apache.commons.logging" export="true" />
> <module name="org.apache.commons.collections" export="true" />
> <module name="org.apache.log4j" export="true" />
> <module name="org.dom4j" export="true" />
> <module name="org.jdom" export="true" />
> <module name="javax.faces.api" slot="mojarra-2.1.23" export="true"/>
> <module name="com.sun.jsf-impl" slot="mojarra-2.1.23" export="true"/>
> <module name="org.jboss.ejb-client" export="true" />
> <module name="org.jboss.remote-naming" export="true" />
> <module name="org.jboss.remoting3" export="true" />
> <module name="org.apache.xerces" />
> <!-- dependency for richfaces -->
> <module name="com.google.guava" slot="11.0.2" export="true"/>
> </dependencies>
> </deployment>
> ...
> {code}
> However, despite excluding the {{javax.orb.api}} module, I can see that {{org.omg.PortableServer.Servant}} is loaded from that module instead of being loaded from our {{com.ooc.orbacus}} module. This causes our application to fail.
> Debugging through the jboss module loader, I can see that it considers both {{javax.orb.api}} and {{com.ooc.orbacus}} as prodivers of the {{org/omg/PortableServer}} path. I am not sure why {{javax.orb.api}} is being considered when it has been excluded in the deployment descriptor for the application.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months
[JBoss JIRA] (WFLY-5613) Fix transaction subsystem resource descriptions
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/WFLY-5613?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated WFLY-5613:
--------------------------------
Fix Version/s: 11.0.0.CR1
(was: 11.0.0.Alpha1)
> Fix transaction subsystem resource descriptions
> -----------------------------------------------
>
> Key: WFLY-5613
> URL: https://issues.jboss.org/browse/WFLY-5613
> Project: WildFly
> Issue Type: Enhancement
> Components: Transactions
> Reporter: Ondřej Chaloupka
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 11.0.0.CR1
>
> Attachments: jts-tooltip-700.DR132.png
>
>
> I would like ask for changing text in transaction configuration helper tooltip (_Need Help?
> _). First there is an issue of not having an information that jts to be fully enabled is need to set subsystem of iiop orb as well (the same issue was for 6.4.0 https://bugzilla.redhat.com/show_bug.cgi?id=995439).
> Nevertheless I would like ask for a bit more general change of the text in the help webconsole tooltip
> Current text is
> {noformat}
> Default timeout: The default timeout.
> Enable tsm status: Whether the transaction status manager (TSM) service, needed for out of process recovery, should be provided or not..
> Journal store enable async io: Whether AsyncIO should be enabled for the journal store. Default is false. The server should be restarted for this setting to take effect.
> Jts: If true this enables the Java Transaction Service.
> Node identifier: Used to set the node identifier on the core environment.
> Statistics enabled: Whether statistics should be enabled.
> Use journal store: Use the journal store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file system file per transaction log. The server should be restarted for this setting to take effect. It's alternative to jdbc based store.
> {noformat}
> {noformat}
> Process id uuid: Indicates whether the transaction manager should use a UUID based process id.
> Process id socket binding: The name of the socket binding configuration to use if the transaction manager should use a socket-based process id. Will be 'undefined' if 'process-id-uuid' is 'true'; otherwise must be set.
> Process id socket max ports: The maximum number of ports to search for an open port if the transaction manager should use a socket-based process id. If the port specified by the socket binding referenced in 'process-id-socket-binding' is occupied, the next higher port will be tried until an open port is found or the number of ports specified by this attribute have been tried. Will be 'undefined' if 'process-id-uuid' is 'true'.
> {noformat}
> {noformat}
> Socket binding: Used to reference the correct socket binding to use for the recovery environment.
> Status socket binding: Used to reference the correct socket binding to use for the transaction status manager.
> Recovery listener: Used to specify if the recovery system should listen on a network socket or not.
> {noformat}
> {noformat}
> Object store path: Denotes a relative or absolute filesystem path denoting where the transaction manager object store should store data. By default the value is treated as relative to the path denoted by the "relative-to" attribute.
> Object store relative to: References a global path configuration in the domain model, defaulting to the JBoss Application Server data directory (jboss.server.data.dir). The value of the "path" attribute will treated as relative to this path. Use an empty string to disable the default behavior and force the value of the "path" attribute to be treated as an absolute path.
> {noformat}
> {noformat}
> Use jdbc store: Use the jdbc store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file system file per transaction log. The server should be restarted for this setting to take effect. It's alternative to Horneq based store
> Jdbc action store drop table: Configure if jdbc action store should drop tables. Default is false. The server should be restarted for this setting to take effect.
> Jdbc action store table prefix: Optional prefix for table used to write transcation logs in configured jdbc action store. The server should be restarted for this setting to take effect.
> Jdbc communication store drop table: Configure if jdbc communication store should drop tables. Default is false. The server should be restarted for this setting to take effect.
> Jdbc communication store table prefix: Optional prefix for table used to write transcation logs in configured jdbc communication store. The server should be restarted for this setting to take effect.
> Jdbc state store drop table: Configure if jdbc state store should drop tables. Default is false. The server should be restarted for this setting to take effect.
> Jdbc state store table prefix: Optional prefix for table used to write transcation logs in configured jdbc state store. The server should be restarted for this setting to take effect.
> Jdbc store datasource: Jndi name of non-XA datasource used. Datasource sghould be define in datasources subsystem. The server should be restarted for this setting to take effect.
> {noformat}
> I would propose the following changes in the tooltip text
> *Attributes*
> * Default timeout
> ** The default timeout for a transaction managed by the transaction manager.
> * Enable tsm status
> ** Whether the transaction status manager (TSM) service, needed for out of process recovery, should be provided or not.
> * Journal store enable async io
> ** Whether AsyncIO should be enabled for the journal store. Default is false. For this settings being active journal natives libraries needs to be available. The server should be restarted for this setting to take effect.
> * Jts
> ** If true this enables the Java Transaction Service. Use of the JTS needs configuration in IIOP OpenJDK where Transactions parameter needs to be set to full. The server should be restarted for this setting to take effect.
> * Node identifier
> ** Used to set the node identifier on the core environment. Each server should have this identifier unique. It's an identifier which differentiates XA transactions as created by this node. The server should be restarted for this setting to take effect.
> * Statistics enabled
> ** Whether transaction statistics should be enabled. The transaction statistics could be seen in section Runtime > Monitor > Subsystems > Transactions. The server should be reloaded for this setting to take effect.
> * Use journal store
> ** Use the journal store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store creates normally one file file per transaction log. The journal one consists from one file for all the transactions. It's alternative to jdbc based store. The server should be restarted for this setting to take effect.
> *Process ID* + *Recovery*
> Add information that for settings these attributes taking effect the server needs to be reloaded.
> *Path*
> * Object store path
> ** Denotes a relative or absolute filesystem path denoting where the transaction manager object store should store data. By default the value is treated as relative to the path denoted by the "relative-to" attribute. This settings is valid when default or journal store is used. It's not used when jdbc journal store is used. The server should be reloaded for this setting to take effect.
> * Object store relative to
> ** References a global path configuration in the domain model, defaulting to the Application Server data directory (jboss.server.data.dir). The value of the "Object store path" attribute will treated as relative to this path. Use an empty string to disable the default behavior and force the value of the "Object store path" attribute to be treated as an absolute path. The server should be reloaded for this setting to take effect.
> *JDBC*
> * Use jdbc store
> ** Use the jdbc store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file file per transaction log. It's alternative to journal based store. The server should be restarted for this setting to take effect.
> * Jdbc store datasource
> ** Jndi name of non-XA datasource used. Datasource sghould be define in datasources subsystem. For this would work the non-XA datasource has to be marked as jta="false". The server should be restarted for this setting to take effect.
> ...the rest of the information is ok from my point of view
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months
[JBoss JIRA] (WFLY-5613) Fix transaction subsystem resource descriptions
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/WFLY-5613?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated WFLY-5613:
--------------------------------
Fix Version/s: 11.0.0.Alpha1
(was: 10.0.0.Final)
> Fix transaction subsystem resource descriptions
> -----------------------------------------------
>
> Key: WFLY-5613
> URL: https://issues.jboss.org/browse/WFLY-5613
> Project: WildFly
> Issue Type: Enhancement
> Components: Transactions
> Reporter: Ondřej Chaloupka
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 11.0.0.CR1
>
> Attachments: jts-tooltip-700.DR132.png
>
>
> I would like ask for changing text in transaction configuration helper tooltip (_Need Help?
> _). First there is an issue of not having an information that jts to be fully enabled is need to set subsystem of iiop orb as well (the same issue was for 6.4.0 https://bugzilla.redhat.com/show_bug.cgi?id=995439).
> Nevertheless I would like ask for a bit more general change of the text in the help webconsole tooltip
> Current text is
> {noformat}
> Default timeout: The default timeout.
> Enable tsm status: Whether the transaction status manager (TSM) service, needed for out of process recovery, should be provided or not..
> Journal store enable async io: Whether AsyncIO should be enabled for the journal store. Default is false. The server should be restarted for this setting to take effect.
> Jts: If true this enables the Java Transaction Service.
> Node identifier: Used to set the node identifier on the core environment.
> Statistics enabled: Whether statistics should be enabled.
> Use journal store: Use the journal store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file system file per transaction log. The server should be restarted for this setting to take effect. It's alternative to jdbc based store.
> {noformat}
> {noformat}
> Process id uuid: Indicates whether the transaction manager should use a UUID based process id.
> Process id socket binding: The name of the socket binding configuration to use if the transaction manager should use a socket-based process id. Will be 'undefined' if 'process-id-uuid' is 'true'; otherwise must be set.
> Process id socket max ports: The maximum number of ports to search for an open port if the transaction manager should use a socket-based process id. If the port specified by the socket binding referenced in 'process-id-socket-binding' is occupied, the next higher port will be tried until an open port is found or the number of ports specified by this attribute have been tried. Will be 'undefined' if 'process-id-uuid' is 'true'.
> {noformat}
> {noformat}
> Socket binding: Used to reference the correct socket binding to use for the recovery environment.
> Status socket binding: Used to reference the correct socket binding to use for the transaction status manager.
> Recovery listener: Used to specify if the recovery system should listen on a network socket or not.
> {noformat}
> {noformat}
> Object store path: Denotes a relative or absolute filesystem path denoting where the transaction manager object store should store data. By default the value is treated as relative to the path denoted by the "relative-to" attribute.
> Object store relative to: References a global path configuration in the domain model, defaulting to the JBoss Application Server data directory (jboss.server.data.dir). The value of the "path" attribute will treated as relative to this path. Use an empty string to disable the default behavior and force the value of the "path" attribute to be treated as an absolute path.
> {noformat}
> {noformat}
> Use jdbc store: Use the jdbc store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file system file per transaction log. The server should be restarted for this setting to take effect. It's alternative to Horneq based store
> Jdbc action store drop table: Configure if jdbc action store should drop tables. Default is false. The server should be restarted for this setting to take effect.
> Jdbc action store table prefix: Optional prefix for table used to write transcation logs in configured jdbc action store. The server should be restarted for this setting to take effect.
> Jdbc communication store drop table: Configure if jdbc communication store should drop tables. Default is false. The server should be restarted for this setting to take effect.
> Jdbc communication store table prefix: Optional prefix for table used to write transcation logs in configured jdbc communication store. The server should be restarted for this setting to take effect.
> Jdbc state store drop table: Configure if jdbc state store should drop tables. Default is false. The server should be restarted for this setting to take effect.
> Jdbc state store table prefix: Optional prefix for table used to write transcation logs in configured jdbc state store. The server should be restarted for this setting to take effect.
> Jdbc store datasource: Jndi name of non-XA datasource used. Datasource sghould be define in datasources subsystem. The server should be restarted for this setting to take effect.
> {noformat}
> I would propose the following changes in the tooltip text
> *Attributes*
> * Default timeout
> ** The default timeout for a transaction managed by the transaction manager.
> * Enable tsm status
> ** Whether the transaction status manager (TSM) service, needed for out of process recovery, should be provided or not.
> * Journal store enable async io
> ** Whether AsyncIO should be enabled for the journal store. Default is false. For this settings being active journal natives libraries needs to be available. The server should be restarted for this setting to take effect.
> * Jts
> ** If true this enables the Java Transaction Service. Use of the JTS needs configuration in IIOP OpenJDK where Transactions parameter needs to be set to full. The server should be restarted for this setting to take effect.
> * Node identifier
> ** Used to set the node identifier on the core environment. Each server should have this identifier unique. It's an identifier which differentiates XA transactions as created by this node. The server should be restarted for this setting to take effect.
> * Statistics enabled
> ** Whether transaction statistics should be enabled. The transaction statistics could be seen in section Runtime > Monitor > Subsystems > Transactions. The server should be reloaded for this setting to take effect.
> * Use journal store
> ** Use the journal store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store creates normally one file file per transaction log. The journal one consists from one file for all the transactions. It's alternative to jdbc based store. The server should be restarted for this setting to take effect.
> *Process ID* + *Recovery*
> Add information that for settings these attributes taking effect the server needs to be reloaded.
> *Path*
> * Object store path
> ** Denotes a relative or absolute filesystem path denoting where the transaction manager object store should store data. By default the value is treated as relative to the path denoted by the "relative-to" attribute. This settings is valid when default or journal store is used. It's not used when jdbc journal store is used. The server should be reloaded for this setting to take effect.
> * Object store relative to
> ** References a global path configuration in the domain model, defaulting to the Application Server data directory (jboss.server.data.dir). The value of the "Object store path" attribute will treated as relative to this path. Use an empty string to disable the default behavior and force the value of the "Object store path" attribute to be treated as an absolute path. The server should be reloaded for this setting to take effect.
> *JDBC*
> * Use jdbc store
> ** Use the jdbc store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file file per transaction log. It's alternative to journal based store. The server should be restarted for this setting to take effect.
> * Jdbc store datasource
> ** Jndi name of non-XA datasource used. Datasource sghould be define in datasources subsystem. For this would work the non-XA datasource has to be marked as jta="false". The server should be restarted for this setting to take effect.
> ...the rest of the information is ok from my point of view
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months
[JBoss JIRA] (WFLY-5919) Wildfly 10 CR5 Regression - Schema not added to query
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-5919?page=com.atlassian.jira.plugin.... ]
Scott Marlow commented on WFLY-5919:
------------------------------------
In the MySQL database, can you verify that the "config" schema, is actually as you entered it above.
> Wildfly 10 CR5 Regression - Schema not added to query
> -----------------------------------------------------
>
> Key: WFLY-5919
> URL: https://issues.jboss.org/browse/WFLY-5919
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 10.0.0.CR5
> Reporter: John Ament
> Assignee: Scott Marlow
>
> My app, working fine in Wildfly 9.0.2 now fails in 10.0.0.CR5 (it was fine in earlier CR's)
> {code}
> 2016-01-03 08:30:43,626 WARN [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (ServerService Thread Pool -- 87) SQL Error: 1046, SQLState: 3D000
> 2016-01-03 08:30:43,626 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (ServerService Thread Pool -- 87) No database selected
> 2016-01-03 08:30:43,627 INFO [org.hibernate.event.internal.DefaultLoadEventListener] (ServerService Thread Pool -- 87) HHH000327: Error performing load command : org.hibernate.exception.GenericJDBCException: could not extract ResultSet
> {code}
> I turned on query debug, and the query being generated is now skipping the schema name defined in my entity's schema (I'm using MySQL)
> The config looks like this
> {code}
> @Table(name = "types", schema = "config")
> {code}
> I have an orm.xml file, I tried removing the default schema stanza without luck.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months
[JBoss JIRA] (WFLY-5613) Fix transaction subsystem resource descriptions
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/WFLY-5613?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated WFLY-5613:
--------------------------------
Priority: Minor (was: Major)
> Fix transaction subsystem resource descriptions
> -----------------------------------------------
>
> Key: WFLY-5613
> URL: https://issues.jboss.org/browse/WFLY-5613
> Project: WildFly
> Issue Type: Enhancement
> Components: Transactions
> Reporter: Ondřej Chaloupka
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 10.0.0.Final
>
> Attachments: jts-tooltip-700.DR132.png
>
>
> I would like ask for changing text in transaction configuration helper tooltip (_Need Help?
> _). First there is an issue of not having an information that jts to be fully enabled is need to set subsystem of iiop orb as well (the same issue was for 6.4.0 https://bugzilla.redhat.com/show_bug.cgi?id=995439).
> Nevertheless I would like ask for a bit more general change of the text in the help webconsole tooltip
> Current text is
> {noformat}
> Default timeout: The default timeout.
> Enable tsm status: Whether the transaction status manager (TSM) service, needed for out of process recovery, should be provided or not..
> Journal store enable async io: Whether AsyncIO should be enabled for the journal store. Default is false. The server should be restarted for this setting to take effect.
> Jts: If true this enables the Java Transaction Service.
> Node identifier: Used to set the node identifier on the core environment.
> Statistics enabled: Whether statistics should be enabled.
> Use journal store: Use the journal store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file system file per transaction log. The server should be restarted for this setting to take effect. It's alternative to jdbc based store.
> {noformat}
> {noformat}
> Process id uuid: Indicates whether the transaction manager should use a UUID based process id.
> Process id socket binding: The name of the socket binding configuration to use if the transaction manager should use a socket-based process id. Will be 'undefined' if 'process-id-uuid' is 'true'; otherwise must be set.
> Process id socket max ports: The maximum number of ports to search for an open port if the transaction manager should use a socket-based process id. If the port specified by the socket binding referenced in 'process-id-socket-binding' is occupied, the next higher port will be tried until an open port is found or the number of ports specified by this attribute have been tried. Will be 'undefined' if 'process-id-uuid' is 'true'.
> {noformat}
> {noformat}
> Socket binding: Used to reference the correct socket binding to use for the recovery environment.
> Status socket binding: Used to reference the correct socket binding to use for the transaction status manager.
> Recovery listener: Used to specify if the recovery system should listen on a network socket or not.
> {noformat}
> {noformat}
> Object store path: Denotes a relative or absolute filesystem path denoting where the transaction manager object store should store data. By default the value is treated as relative to the path denoted by the "relative-to" attribute.
> Object store relative to: References a global path configuration in the domain model, defaulting to the JBoss Application Server data directory (jboss.server.data.dir). The value of the "path" attribute will treated as relative to this path. Use an empty string to disable the default behavior and force the value of the "path" attribute to be treated as an absolute path.
> {noformat}
> {noformat}
> Use jdbc store: Use the jdbc store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file system file per transaction log. The server should be restarted for this setting to take effect. It's alternative to Horneq based store
> Jdbc action store drop table: Configure if jdbc action store should drop tables. Default is false. The server should be restarted for this setting to take effect.
> Jdbc action store table prefix: Optional prefix for table used to write transcation logs in configured jdbc action store. The server should be restarted for this setting to take effect.
> Jdbc communication store drop table: Configure if jdbc communication store should drop tables. Default is false. The server should be restarted for this setting to take effect.
> Jdbc communication store table prefix: Optional prefix for table used to write transcation logs in configured jdbc communication store. The server should be restarted for this setting to take effect.
> Jdbc state store drop table: Configure if jdbc state store should drop tables. Default is false. The server should be restarted for this setting to take effect.
> Jdbc state store table prefix: Optional prefix for table used to write transcation logs in configured jdbc state store. The server should be restarted for this setting to take effect.
> Jdbc store datasource: Jndi name of non-XA datasource used. Datasource sghould be define in datasources subsystem. The server should be restarted for this setting to take effect.
> {noformat}
> I would propose the following changes in the tooltip text
> *Attributes*
> * Default timeout
> ** The default timeout for a transaction managed by the transaction manager.
> * Enable tsm status
> ** Whether the transaction status manager (TSM) service, needed for out of process recovery, should be provided or not.
> * Journal store enable async io
> ** Whether AsyncIO should be enabled for the journal store. Default is false. For this settings being active journal natives libraries needs to be available. The server should be restarted for this setting to take effect.
> * Jts
> ** If true this enables the Java Transaction Service. Use of the JTS needs configuration in IIOP OpenJDK where Transactions parameter needs to be set to full. The server should be restarted for this setting to take effect.
> * Node identifier
> ** Used to set the node identifier on the core environment. Each server should have this identifier unique. It's an identifier which differentiates XA transactions as created by this node. The server should be restarted for this setting to take effect.
> * Statistics enabled
> ** Whether transaction statistics should be enabled. The transaction statistics could be seen in section Runtime > Monitor > Subsystems > Transactions. The server should be reloaded for this setting to take effect.
> * Use journal store
> ** Use the journal store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store creates normally one file file per transaction log. The journal one consists from one file for all the transactions. It's alternative to jdbc based store. The server should be restarted for this setting to take effect.
> *Process ID* + *Recovery*
> Add information that for settings these attributes taking effect the server needs to be reloaded.
> *Path*
> * Object store path
> ** Denotes a relative or absolute filesystem path denoting where the transaction manager object store should store data. By default the value is treated as relative to the path denoted by the "relative-to" attribute. This settings is valid when default or journal store is used. It's not used when jdbc journal store is used. The server should be reloaded for this setting to take effect.
> * Object store relative to
> ** References a global path configuration in the domain model, defaulting to the Application Server data directory (jboss.server.data.dir). The value of the "Object store path" attribute will treated as relative to this path. Use an empty string to disable the default behavior and force the value of the "Object store path" attribute to be treated as an absolute path. The server should be reloaded for this setting to take effect.
> *JDBC*
> * Use jdbc store
> ** Use the jdbc store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file file per transaction log. It's alternative to journal based store. The server should be restarted for this setting to take effect.
> * Jdbc store datasource
> ** Jndi name of non-XA datasource used. Datasource sghould be define in datasources subsystem. For this would work the non-XA datasource has to be marked as jta="false". The server should be restarted for this setting to take effect.
> ...the rest of the information is ok from my point of view
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months
[JBoss JIRA] (WFLY-5922) Cannot exclude java.orb.api module
by John Farrelly (JIRA)
[ https://issues.jboss.org/browse/WFLY-5922?page=com.atlassian.jira.plugin.... ]
John Farrelly updated WFLY-5922:
--------------------------------
Description:
We use Orbacus as our CORBA implementation, and in our application we wish to use CORBA classes only from the orbacus module, and not the JDK/WildFly bundled CORBA.
In the {{jboss-deployment-structure.xml}} file of our {{ear}} file, we have the following:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure>
<ear-subdeployments-isolated>false</ear-subdeployments-isolated>
<deployment>
<exclusions>
<module name="javax.orb.api" />
<module name="org.omg.api" />
</exclusions>
<dependencies>
<module name="com.ooc.orbacus" export="true"/>
<module name="org.apache.commons.logging" export="true" />
<module name="org.apache.commons.collections" export="true" />
<module name="org.apache.log4j" export="true" />
<module name="org.dom4j" export="true" />
<module name="org.jdom" export="true" />
<module name="javax.faces.api" slot="mojarra-2.1.23" export="true"/>
<module name="com.sun.jsf-impl" slot="mojarra-2.1.23" export="true"/>
<module name="org.jboss.ejb-client" export="true" />
<module name="org.jboss.remote-naming" export="true" />
<module name="org.jboss.remoting3" export="true" />
<module name="org.apache.xerces" />
<!-- dependency for richfaces -->
<module name="com.google.guava" slot="11.0.2" export="true"/>
</dependencies>
</deployment>
...
{code}
However, despite excluding the {{javax.orb.api}} module, I can see that {{org.omg.PortableServer.Servant}} is loaded from that module instead of being loaded from our {{com.ooc.orbacus}} module. This causes our application to fail.
Debugging through the jboss module loader, I can see that it considers both {{javax.orb.api}} and {{com.ooc.orbacus}} as prodivers of the {{org/omg/PortableServer}} path. I am not sure why {{javax.orb.api}} is being considered when it has been excluded in the deployment descriptor for the application.
was:
We use Orbacus as our CORBA implementation, and in our application we wish to use CORBA classes only from the orbacus module, and not the JDK/WildFly bundled CORBA.
In the {{jboss-deployment-structure.xml}} file of our {{ear}} file, we have the following:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure>
<ear-subdeployments-isolated>false</ear-subdeployments-isolated>
<deployment>
<exclusions>
<!-- Make sure jacorb libraries are excluded -->
<module name="javax.orb.api" />
<module name="org.omg.api" />
</exclusions>
<dependencies>
<module name="com.ooc.orbacus" export="true"/>
<module name="org.apache.commons.logging" export="true" />
<module name="org.apache.commons.collections" export="true" />
<module name="org.apache.log4j" export="true" />
<module name="org.dom4j" export="true" />
<module name="org.jdom" export="true" />
<module name="javax.faces.api" slot="mojarra-2.1.23" export="true"/>
<module name="com.sun.jsf-impl" slot="mojarra-2.1.23" export="true"/>
<module name="org.jboss.ejb-client" export="true" />
<module name="org.jboss.remote-naming" export="true" />
<module name="org.jboss.remoting3" export="true" />
<module name="org.apache.xerces" />
<!-- dependency for richfaces -->
<module name="com.google.guava" slot="11.0.2" export="true"/>
</dependencies>
</deployment>
...
{code}
However, despite excluding the {{javax.orb.api}} module, I can see that {{org.omg.PortableServer.Servant}} is loaded from that module instead of being loaded from our {{com.ooc.orbacus}} module. This causes our application to fail.
Debugging through the jboss module loader, I can see that it considers both {{javax.orb.api}} and {{com.ooc.orbacus}} as prodivers of the {{org/omg/PortableServer}} path. I am not sure why {{javax.orb.api}} is being considered when it has been excluded in the deployment descriptor for the application.
> Cannot exclude java.orb.api module
> ----------------------------------
>
> Key: WFLY-5922
> URL: https://issues.jboss.org/browse/WFLY-5922
> Project: WildFly
> Issue Type: Bug
> Components: Class Loading
> Affects Versions: 10.0.0.CR4
> Environment: Red Hat Enterprise Linux Server release 7.1 (Maipo)
> Linux 3.10.0-229.4.2.el7.x86_64 #1 SMP Wed May 13 10:06:09 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
> java version "1.8.0_60"
> Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
> Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
> Reporter: John Farrelly
> Assignee: David Lloyd
> Priority: Blocker
>
> We use Orbacus as our CORBA implementation, and in our application we wish to use CORBA classes only from the orbacus module, and not the JDK/WildFly bundled CORBA.
> In the {{jboss-deployment-structure.xml}} file of our {{ear}} file, we have the following:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-deployment-structure>
> <ear-subdeployments-isolated>false</ear-subdeployments-isolated>
> <deployment>
> <exclusions>
> <module name="javax.orb.api" />
> <module name="org.omg.api" />
> </exclusions>
> <dependencies>
> <module name="com.ooc.orbacus" export="true"/>
> <module name="org.apache.commons.logging" export="true" />
> <module name="org.apache.commons.collections" export="true" />
> <module name="org.apache.log4j" export="true" />
> <module name="org.dom4j" export="true" />
> <module name="org.jdom" export="true" />
> <module name="javax.faces.api" slot="mojarra-2.1.23" export="true"/>
> <module name="com.sun.jsf-impl" slot="mojarra-2.1.23" export="true"/>
> <module name="org.jboss.ejb-client" export="true" />
> <module name="org.jboss.remote-naming" export="true" />
> <module name="org.jboss.remoting3" export="true" />
> <module name="org.apache.xerces" />
> <!-- dependency for richfaces -->
> <module name="com.google.guava" slot="11.0.2" export="true"/>
> </dependencies>
> </deployment>
> ...
> {code}
> However, despite excluding the {{javax.orb.api}} module, I can see that {{org.omg.PortableServer.Servant}} is loaded from that module instead of being loaded from our {{com.ooc.orbacus}} module. This causes our application to fail.
> Debugging through the jboss module loader, I can see that it considers both {{javax.orb.api}} and {{com.ooc.orbacus}} as prodivers of the {{org/omg/PortableServer}} path. I am not sure why {{javax.orb.api}} is being considered when it has been excluded in the deployment descriptor for the application.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months
[JBoss JIRA] (WFLY-5922) Cannot exclude java.orb.api module
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5922?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-5922:
-----------------------------------
With configuration provided, exclutions would only apply to "root" ear and not to all sub deployments, which is probably why you see this problem.
you will need to add <sub-deployment> with excludes for each ear module that needs excludes
> Cannot exclude java.orb.api module
> ----------------------------------
>
> Key: WFLY-5922
> URL: https://issues.jboss.org/browse/WFLY-5922
> Project: WildFly
> Issue Type: Bug
> Components: Class Loading
> Affects Versions: 10.0.0.CR4
> Environment: Red Hat Enterprise Linux Server release 7.1 (Maipo)
> Linux 3.10.0-229.4.2.el7.x86_64 #1 SMP Wed May 13 10:06:09 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
> java version "1.8.0_60"
> Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
> Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
> Reporter: John Farrelly
> Assignee: David Lloyd
> Priority: Blocker
>
> We use Orbacus as our CORBA implementation, and in our application we wish to use CORBA classes only from the orbacus module, and not the JDK/WildFly bundled CORBA.
> In the {{jboss-deployment-structure.xml}} file of our {{ear}} file, we have the following:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-deployment-structure>
> <ear-subdeployments-isolated>false</ear-subdeployments-isolated>
> <deployment>
> <exclusions>
> <module name="javax.orb.api" />
> <module name="org.omg.api" />
> </exclusions>
> <dependencies>
> <module name="com.ooc.orbacus" export="true"/>
> <module name="org.apache.commons.logging" export="true" />
> <module name="org.apache.commons.collections" export="true" />
> <module name="org.apache.log4j" export="true" />
> <module name="org.dom4j" export="true" />
> <module name="org.jdom" export="true" />
> <module name="javax.faces.api" slot="mojarra-2.1.23" export="true"/>
> <module name="com.sun.jsf-impl" slot="mojarra-2.1.23" export="true"/>
> <module name="org.jboss.ejb-client" export="true" />
> <module name="org.jboss.remote-naming" export="true" />
> <module name="org.jboss.remoting3" export="true" />
> <module name="org.apache.xerces" />
> <!-- dependency for richfaces -->
> <module name="com.google.guava" slot="11.0.2" export="true"/>
> </dependencies>
> </deployment>
> ...
> {code}
> However, despite excluding the {{javax.orb.api}} module, I can see that {{org.omg.PortableServer.Servant}} is loaded from that module instead of being loaded from our {{com.ooc.orbacus}} module. This causes our application to fail.
> Debugging through the jboss module loader, I can see that it considers both {{javax.orb.api}} and {{com.ooc.orbacus}} as prodivers of the {{org/omg/PortableServer}} path. I am not sure why {{javax.orb.api}} is being considered when it has been excluded in the deployment descriptor for the application.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months