[JBoss JIRA] (WFLY-2645) SFSB containing injected DataSource fails to passivate/serialize
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-2645?page=com.atlassian.jira.plugin.... ]
Paul Ferraro commented on WFLY-2645:
------------------------------------
[~jesper.pedersen] No - this is a WF bug. If this can be addressed within the context of ironjacamar, great - but please open a separate jira and link it here. IMO, this is more appropriate addressed by the connector subsystem, which should use a serializable proxy to the DataSource from ironjacamar. This is what we do for other EE resources.
> SFSB containing injected DataSource fails to passivate/serialize
> ----------------------------------------------------------------
>
> Key: WFLY-2645
> URL: https://issues.jboss.org/browse/WFLY-2645
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JCA
> Affects Versions: 8.0.0.Beta1
> Reporter: Paul Ferraro
> Assignee: Stefano Maestri
> Priority: Critical
>
> See JBPAPP6-1762 for details.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (WFLY-2679) Jdbc cache store couldn't read databaseType property
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-2679?page=com.atlassian.jira.plugin.... ]
Paul Ferraro updated WFLY-2679:
-------------------------------
Fix Version/s: 8.0.0.Final
> Jdbc cache store couldn't read databaseType property
> ----------------------------------------------------
>
> Key: WFLY-2679
> URL: https://issues.jboss.org/browse/WFLY-2679
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Clustering
> Affects Versions: 8.0.0.Beta1
> Environment: WildFly 8.0.0.Beta2-SNAPSHOT (from 2013-12-16
> Reporter: Tomas Remes
> Assignee: Paul Ferraro
> Fix For: 8.0.0.Final
>
>
> If you want use some driver, which type is not recognizable by Infinispan (e.g. jtds driver), then you are asked to specify your DB type via "databaseType" property in your cache store configuration. But when you specify it, you'll get following exception:
> {noformat}
> org.infinispan.commons.CacheConfigurationException: Couldn't find a setter named [setDatabaseType] which takes a single parameter, for parameter databaseType on class [class org.infinispan.persistence.jdbc.configuration.JdbcBinaryStoreConfigurationBuilder]
> at org.infinispan.configuration.parsing.XmlConfigHelper.setValues(XmlConfigHelper.java:450)
> at org.infinispan.configuration.cache.AbstractStoreConfigurationBuilder.withProperties(AbstractStoreConfigurationBuilder.java:91)
> at org.infinispan.configuration.cache.AbstractStoreConfigurationBuilder.withProperties(AbstractStoreConfigurationBuilder.java:9)
> at org.jboss.as.clustering.infinispan.subsystem.CacheAdd.processModelNode(CacheAdd.java:542)
> at org.jboss.as.clustering.infinispan.subsystem.ClusteredCacheAdd.processModelNode(ClusteredCacheAdd.java:69)
> at org.jboss.as.clustering.infinispan.subsystem.SharedStateCacheAdd.processModelNode(SharedStateCacheAdd.java:50)
> at org.jboss.as.clustering.infinispan.subsystem.DistributedCacheAdd.processModelNode(DistributedCacheAdd.java:90)
> at org.jboss.as.clustering.infinispan.subsystem.CacheAdd.installRuntimeServices(CacheAdd.java:205)
> at org.jboss.as.clustering.infinispan.subsystem.CacheAdd.performRuntime(CacheAdd.java:179)
> at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:75) [wildfly-controller-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:591) [wildfly-controller-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:469) [wildfly-controller-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:273) [wildfly-controller-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:268) [wildfly-controller-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]
> at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:343) [wildfly-controller-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (WFLY-334) HA Singleton deployer for applications
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-334?page=com.atlassian.jira.plugin.s... ]
Paul Ferraro updated WFLY-334:
------------------------------
Comment: was deleted
(was: Good day,
I am on leave and will return to the office on Monday, 6 January 2014. For any urgent matters log a support ticket with support(a)nha.co.za or at telephone 0860142536.
Kind Regards
Nico Schlebusch
The e-mail and attachments are confidential and intended only for selected recipients. If you have received it in error, you may not in any way disclose or rely on the contents. You
may not keep, copy or distribute the e-mail. Should you receive it, immediately notify the sender of the error and delete the e-mail. Also note that this form of communication is
not secure, it can be intercepted, and may not necessarily be free of errors and viruses in spite of reasonable efforts to secure this medium.
)
> HA Singleton deployer for applications
> --------------------------------------
>
> Key: WFLY-334
> URL: https://issues.jboss.org/browse/WFLY-334
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Clustering, Domain Management
> Reporter: Wolf-Dieter Fink
> Assignee: Paul Ferraro
> Labels: deployers, hasingleton
> Fix For: 8.0.0.Final
>
>
> A HASingleton deployer should be provided in standalone and domain mode.
> To be able to migrate such singleton applications from former AS versions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (WFLY-334) HA Singleton deployer for applications
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-334?page=com.atlassian.jira.plugin.s... ]
Paul Ferraro updated WFLY-334:
------------------------------
Comment: was deleted
(was: Sehr geehrte Damen und Herren, von Montag, den 23.12.2013, bis einschließlich Freitag, den 10.01.2014, bin ich nicht im Hause. In dringenden Fällen wenden Sie sich bitte an Heiner Tittelbach (IT 271) oder Bernd Kirchgäßner (IT 221). Ihre Mail wird nicht automatisch weitergeleitet. Mit freundlichen Grüßen Jochen Riedlinger
)
> HA Singleton deployer for applications
> --------------------------------------
>
> Key: WFLY-334
> URL: https://issues.jboss.org/browse/WFLY-334
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Clustering, Domain Management
> Reporter: Wolf-Dieter Fink
> Assignee: Paul Ferraro
> Labels: deployers, hasingleton
> Fix For: 8.0.0.Final
>
>
> A HASingleton deployer should be provided in standalone and domain mode.
> To be able to migrate such singleton applications from former AS versions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (WFLY-2679) Jdbc cache store couldn't read databaseType property
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-2679?page=com.atlassian.jira.plugin.... ]
Paul Ferraro commented on WFLY-2679:
------------------------------------
databaseType is not a property of the jdbc cache stores, but a property of the "TableManipulation" configuration bean. We should expose this as an explicit attribute.
> Jdbc cache store couldn't read databaseType property
> ----------------------------------------------------
>
> Key: WFLY-2679
> URL: https://issues.jboss.org/browse/WFLY-2679
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Clustering
> Affects Versions: 8.0.0.Beta1
> Environment: WildFly 8.0.0.Beta2-SNAPSHOT (from 2013-12-16
> Reporter: Tomas Remes
> Assignee: Paul Ferraro
>
> If you want use some driver, which type is not recognizable by Infinispan (e.g. jtds driver), then you are asked to specify your DB type via "databaseType" property in your cache store configuration. But when you specify it, you'll get following exception:
> {noformat}
> org.infinispan.commons.CacheConfigurationException: Couldn't find a setter named [setDatabaseType] which takes a single parameter, for parameter databaseType on class [class org.infinispan.persistence.jdbc.configuration.JdbcBinaryStoreConfigurationBuilder]
> at org.infinispan.configuration.parsing.XmlConfigHelper.setValues(XmlConfigHelper.java:450)
> at org.infinispan.configuration.cache.AbstractStoreConfigurationBuilder.withProperties(AbstractStoreConfigurationBuilder.java:91)
> at org.infinispan.configuration.cache.AbstractStoreConfigurationBuilder.withProperties(AbstractStoreConfigurationBuilder.java:9)
> at org.jboss.as.clustering.infinispan.subsystem.CacheAdd.processModelNode(CacheAdd.java:542)
> at org.jboss.as.clustering.infinispan.subsystem.ClusteredCacheAdd.processModelNode(ClusteredCacheAdd.java:69)
> at org.jboss.as.clustering.infinispan.subsystem.SharedStateCacheAdd.processModelNode(SharedStateCacheAdd.java:50)
> at org.jboss.as.clustering.infinispan.subsystem.DistributedCacheAdd.processModelNode(DistributedCacheAdd.java:90)
> at org.jboss.as.clustering.infinispan.subsystem.CacheAdd.installRuntimeServices(CacheAdd.java:205)
> at org.jboss.as.clustering.infinispan.subsystem.CacheAdd.performRuntime(CacheAdd.java:179)
> at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:75) [wildfly-controller-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:591) [wildfly-controller-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:469) [wildfly-controller-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:273) [wildfly-controller-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:268) [wildfly-controller-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]
> at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:343) [wildfly-controller-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (WFLY-2680) java:comp/DefaultDataSource doesn't work in persistence.xml
by arjan tijms (JIRA)
[ https://issues.jboss.org/browse/WFLY-2680?page=com.atlassian.jira.plugin.... ]
arjan tijms commented on WFLY-2680:
-----------------------------------
{quote}The reason why this does not work is because java:comp is scoped to a component{quote}
You're right, and this is perhaps a somewhat unfortunate choice. Perhaps {{java:app}} of even {{java:global}} would have been the better choice. I've always thought of {{java:comp}} to be a somewhat peculiar space anyway, as the entire web module counts as one component, but every single EJB bean is a component as well. With the EJB model being slowly retrofitted towards a set of CDI extensions and interceptors it's not clear to me what the long term usage of this name space will be anyway.
I guess {{java:comp}} was chosen so it can be more easily re-mapped to another data source on a per component basis, but not sure if that's worth the hassle.
Note that all the other default resources, like the JMS connection factory and executor service and such are also in {{java:comp}}.
{quote}We can probably just hack something in to make this work though, as it would be more user friendly.{quote}
That would be really great! I'll try to address this issue with the EG and ask for some clarification.
> java:comp/DefaultDataSource doesn't work in persistence.xml
> -----------------------------------------------------------
>
> Key: WFLY-2680
> URL: https://issues.jboss.org/browse/WFLY-2680
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: EE, JPA / Hibernate
> Affects Versions: 8.0.0.CR1
> Reporter: arjan tijms
> Assignee: David Lloyd
> Labels: javaee7, jdbc
>
> Having a persistence.xml with the following content fails the deployment on WildFly 8 CR1:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <persistence version="2.1" xmlns="http://xmlns.jcp.org/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd">
>
> <persistence-unit name="testPU">
> <jta-data-source>java:comp/DefaultDataSource</jta-data-source>
> </persistence-unit>
> </persistence>
> {code}
> It results in the following error:
> {noformat}
> 13:51:40,367 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "dynamic-named-query.war")]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"dynamic-named-query.war#testPU\".__FIRST_PHASE__ is missing [jboss.naming.context.java.module.dynamic-named-query.dynamic-named-query.DefaultDataSource]"]}
> {noformat}
> When I proposed the feature for the default data source over at the Java EE JIRA (https://java.net/jira/browse/JAVAEE_SPEC-4) I intended this to work. In the description I hinted that the standard JNDI name would be the standard alternative for {{java:jboss/datasources/ExampleDS}} on JBoss. The latter indeed does work in {{persistence.xml}} using WildFly 8 CR1.
> Omitting the {{jta-data-source}} element altogether *does* work, which is great. However, I foresee a lot of users tripping over this in the future and just giving up the idea of using a default data source, especially since the error message is very cryptic for new developers.
> In GlassFish 4 using {{java:comp/DefaultDataSource}} in {{persistence.xml}} does work.
> See also WFLY-2027 and WFLY-2158
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (JBASM-38) shutdown the second time throw stack trace to the console
by Shelly McGowan (JIRA)
[ https://issues.jboss.org/browse/JBASM-38?page=com.atlassian.jira.plugin.s... ]
Shelly McGowan commented on JBASM-38:
-------------------------------------
this may be related to the changes as seen in https://issues.jboss.org/browse/JBAS-7818 which impacted shutdown.
See:
https://issues.jboss.org/browse/JBAS-7889
specifically:
https://community.jboss.org/wiki/StartAndStopTheJBossApplicationServer
> shutdown the second time throw stack trace to the console
> ---------------------------------------------------------
>
> Key: JBASM-38
> URL: https://issues.jboss.org/browse/JBASM-38
> Project: JBoss AS Server Manager
> Issue Type: Enhancement
> Environment: JBossAS 6.0.0.Final "Neo", Windows 7
> Reporter: Larry Chan
> Assignee: Shelly McGowan
> Priority: Minor
>
> I'm filing for my coworker who doesn't have an account here.
> shutdown.bat -o 16.89.22.157
> Exception in thread "main" java.io.IOException: Failed to retrieve RMIServer stu
> b: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectE
> xception: Connection refused to host: 16.89.22.157; nested exception is:
> java.net.ConnectException: Connection refused: connect]
> at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:33
> 8)
> at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFacto
> ry.java:248)
> at org.jboss.Shutdown.main(Shutdown.java:235)
> Caused by: javax.naming.ServiceUnavailableException [Root exception is java.rmi.
> ConnectException: Connection refused to host: 16.89.22.157; nested exception is:
> java.net.ConnectException: Connection refused: connect]
> at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java
> :101)
> at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.j
> ava:185)
> at javax.naming.InitialContext.lookup(InitialContext.java:392)
> at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnect
> or.java:1886)
> at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.j
> ava:1856)
> at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:25
> 7)
> ... 2 more
> Caused by: java.rmi.ConnectException: Connection refused to host: 16.89.22.157;
> nested exception is:
> java.net.ConnectException: Connection refused: connect
> at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601)
> at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198
> )
> at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
> at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322)
> at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
> at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java
> :97)
> ... 7 more
> Caused by: java.net.ConnectException: Connection refused: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
> at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
> at java.net.Socket.connect(Socket.java:529)
> at java.net.Socket.connect(Socket.java:478)
> at java.net.Socket.<init>(Socket.java:375)
> at java.net.Socket.<init>(Socket.java:189)
> at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirect
> SocketFactory.java:22)
> at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMaster
> SocketFactory.java:128)
> at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595)
> ... 12 more
> Press any key to continue . . .
> EXPECTED BEHAVIOR:
> It is better and more standard just output message of "already shutdown".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (JBASM-39) How to set Jboss proxy configuration ?
by Shelly McGowan (JIRA)
[ https://issues.jboss.org/browse/JBASM-39?page=com.atlassian.jira.plugin.s... ]
Shelly McGowan commented on JBASM-39:
-------------------------------------
Please move your question to the JBoss user forums.
> How to set Jboss proxy configuration ?
> --------------------------------------
>
> Key: JBASM-39
> URL: https://issues.jboss.org/browse/JBASM-39
> Project: JBoss AS Server Manager
> Issue Type: Task
> Environment: windows 7
> Reporter: nandan kumar
> Assignee: Shelly McGowan
> Labels: jboss
>
> i have to use jboss as a proxy server.But my main application is running in mongrel server(ruby on rails based web server).please let me know how can i configure if request is coming from http://localhost:3000/.Jboss needs to capture this request from proxy listener.
> Currently i am setting below mentioned configuration in server.xml in this location jboss-5.1.0.GA\jboss-5.1.0.GA\server\default\deploy\jbossweb.sar
> <Connector port="8080" proxyName="localhost" proxyPort="3000"/>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (JBASM-42) How to configure classpath in JBoss 7.1.0
by Shelly McGowan (JIRA)
[ https://issues.jboss.org/browse/JBASM-42?page=com.atlassian.jira.plugin.s... ]
Shelly McGowan commented on JBASM-42:
-------------------------------------
See:
https://docs.jboss.org/author/display/AS71/Class+Loading+in+AS7
> How to configure classpath in JBoss 7.1.0
> -----------------------------------------
>
> Key: JBASM-42
> URL: https://issues.jboss.org/browse/JBASM-42
> Project: JBoss AS Server Manager
> Issue Type: Task
> Reporter: Sethu Raman
> Assignee: Shelly McGowan
> Priority: Blocker
>
> How to configure/map the application classpath for loading property/related xml files. I tried by placing the classpath folder inside WEB-INF\classes and mapped an external location and point that in standalone.bat "set CLASSPATH = D:\jboss-7.1.0.Final\domain\property-repos"
> None of them works. It throws the below exception on server start up:
> ERROR [org.jboss.as.web.deployment.jsf.JsfManagedBeanProcessor] JBAS018211: Could not load JSF managed bean class:
> com.dnb.rmp.nautilus.trinidad.tree.ComponentEditorHandler
> ERROR [org.jboss.as.web.deployment.jsf.JsfManagedBeanProcessor] JBAS018211: Could not load JSF managed bean class: com.dnb.rmp.nautilus.faces.model.UILookAndFeelManager
> 15:17:27,683 ERROR [org.apache.catalina.core.ApplicationContext] StandardWrapper.Throwable: java.lang.IllegalArgumentException: InputStream cannot be null
> Note: This was happening while migrating our application from Jboss 4.2 to Jboss 7.1.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (JBASM-43) jsch object can not be created
by Shelly McGowan (JIRA)
[ https://issues.jboss.org/browse/JBASM-43?page=com.atlassian.jira.plugin.s... ]
Shelly McGowan commented on JBASM-43:
-------------------------------------
This issue appears to have been filed in the wrong JIRA category. Is there a forum post that is related to your issue which describes in more detail the problem you are reporting here?
> jsch object can not be created
> ------------------------------
>
> Key: JBASM-43
> URL: https://issues.jboss.org/browse/JBASM-43
> Project: JBoss AS Server Manager
> Issue Type: Bug
> Reporter: ali ahmed
> Assignee: Shelly McGowan
> Labels: jsch
>
> create a singleton ejb that contains a scheduler method which tries to create Jsch object (to create a session to list directories). the debug hangs and no exception is thrown.
> tried using of jsch-0.1.40 and jsch-0.1.50 and same result
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months