Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
25 replies
Subscribers
9 subscribers
Views
6374 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
Ok I am upgrading from Appian 6.7.1 to 7.2 on a Windows 2008 R2 and SQL Server 2
jasonc248
over 10 years ago
Ok I am upgrading from Appian 6.7.1 to 7.2 on a Windows 2008 R2 and SQL Server 2008.
Using JBoss 6.1 and nearly done with my migration guide (just ready to fire Appian up and then work on Email Templates).
So I start the Appian engines, they are all okay.
Next I tried to start JBoss, getting a logging errors.
Attached is the boot.log file from JBoss 6.1. It appears logging is using a 7.1.1 jar which seems incorrect to me, but I don't know how to fix it.
Here is the error when trying to run the standalone.bat file
Unable to set property pattern on class org.jboss.logmanager.formatters.PatternF
ormatter: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
at java....
boot.log
OriginalPostID-110535
OriginalPostID-110535
Discussion posts and replies are publicly visible
0
jasonc248
over 10 years ago
...lang.reflect.Method.invoke(Method.java:606)
at org.jboss.logmanager.PropertyConfigurator.configureProperties(Propert
yConfigurator.java:187)
at org.jboss.logmanager.PropertyConfigurator.configureFormatter(Property
Configurator.java:360)
at org.jboss.logmanager.PropertyConfigurator.configureHandler(PropertyCo
nfigurator.java:305)
at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigura
tor.java:128)
at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigura
tor.java:86)
at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:246
)
at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:231
)
at java.util.logging.LogManager$2.run(LogManager.java:312)
at java.util.logging.LogManager$2.run(LogManager.java:310)
at java.security.AccessController.doPrivileged(Native Method)
at java.util.logging.LogManager.readPrim...
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
jasonc248
over 10 years ago
...ordialConfiguration(LogManager.j
ava:310)
at java.util.logging.LogManager.getLogManager(LogManager.java:292)
at java.util.logging.Logger.<init>(Logger.java:265)
at java.util.logging.LogManager$RootLogger.<init>(LogManager.java:1428)
at java.util.logging.LogManager$RootLogger.<init>(LogManager.java:1426)
at java.util.logging.LogManager$1.run(LogManager.java:196)
at java.security.AccessController.doPrivileged(Native Method)
at java.util.logging.LogManager.<clinit>(LogManager.java:173)
at org.jboss.modules.Main.main(Main.java:394)
Caused by: java.lang.IllegalArgumentException: Encountered an unknown format cha
racter
at org.jboss.logmanager.formatters.FormatStringParser.getSteps(FormatStr
ingParser.java:168)
at org.jboss.logmanager.formatters.PatternFormatter.setPattern(PatternFo
rmatter.java:63)
... 23 more
Thank you!
Jason
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Alok Mohare
Appian Employee
over 10 years ago
Jason, there's a parse error in the log:
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[3,1]
Message: Unexpected element '{urn:jboss:domain:1.4}server'
...
It seems like you have a misconfiguration in your standalone.xml in the urn:jboss:domain:1.4 element.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
jasonc248
over 10 years ago
Ok found a few issues going though the Configuring JBoss guide, but still getting the error. I attached the file here.
standalone.xml
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Patty Isecke
Appian Employee
over 10 years ago
Can you try moving the following below your </extensions> tag:
<system-properties>
<property name="org.apache.tomcat.util.http.Parameters.MAX_COUNT" value="5000"/>
</system-properties>
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
jasonc248
over 10 years ago
Thanks Patty, yeah that didn't change it though. Still same log error.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Patty Isecke
Appian Employee
over 10 years ago
I just tried opening your standalone.xml file in IE, and it threw this error:
This page contains the following errors:
error on line 151 at column 33: Opening and ending tag mismatch: driver line 0 and drivers
Can you double check that you have configured the driver properly:
forum.appian.com/.../Configuring_Relational_Databases
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
jasonc248
over 10 years ago
Ok so this part of the documentation is pretty confusing because I don't see datasources:1.0"> I have datasources:1.1">
So I went ahead took out the SQL Server from the 1.1, created new subsystem with 1.0 (guess that what I need to do). Still broken at the same spot, but see the xml is also still broken. I checked the tags and they look legal to me.
standalone.xml
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
jasonc248
over 10 years ago
Ok found the needle in the haystack. Fixed the standalone.xml file. I still get the same error when running the standalone.bat file though.
standalone.xml
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Patty Isecke
Appian Employee
over 10 years ago
I think you have two separate subsystems for your datasources. Can you update lines 136-155 to <subsystem xmlns="urn:jboss:domain:datasources:1.1">
<datasources>
<datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="ExampleDS" enabled="true" use-java-context="true">
<connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1</connection-url>
<driver>h2</driver>
<security>
<user-name>sa</user-name>
<password>sa</password>
</security>
</datasource>
<drivers>
<driver name="h2" module="com.h2database.h2">
<xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
</driver>
<driver module="com.microsoft.sqlserver.jdbc" name="com.microsoft.sqlserver.jdbc">
<xa-datasource-class>com.microsoft.sqlserver.jdbc.SQLServerXADataSource</xa-datasource-class>
</driver>
</drivers>
</datasources>
</subsystem>
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
>